Chef Service

Overview

Guidelines

The following table identifies the terminology used when associating a Chef service.

Chef ServiceAssociated Terminology
Repository DependencyServer
Service AssociationClient
Configuration  ReferenceRecipes

The Chef Server is available as a repository type. See Artifact Repository for a complete list of available types for repositories.

Workload Manager does not allow you to provision or manage the Chef Servers either directly or indirectly. Be sure to pre-configure these servers before adding either as repositories in Workload Manager.

The service script installs, configures, starts, and stops the Chef Client. Each service requires the information to setup the Chef Client and configure the Chef Recipe and environment name.

General Settings

Properties

Description

Minimum Number of NodesDefault = 1. The minimum number of nodes within each tier in use to ensure manual or automatic scaling.
Maximum Number of NodesDefault = 2. The maximum number of nodes within each tier in use to ensure manual or automatic scaling.

Chef Server

Required. The configured repository dependency for the Chef server.

Chef Organization

Required. The organization to which this Chef Server belongs.

Chef Recipe

Required. Identifies the configuration reference for this service.

Chef Environment

Required. The service script invokes the Chef Client and registers itself to the selected Chef Server.

To associate the Chef repository (when you Project and Phase Management) with the Workload Manager deployment environment, use the %DEP_ENV_NAME% macro. When a user provides this macro, the macro is replaced with the environment name dynamically at runtime. When users configure the environment, they have the option to provide additional granular parameters to complete this configuration. See Pre-Defined Parameters and Using Parameters for additional context.

Clustering Support

See Service Administration Custom Service Clustering for details on using parameters that are required to allow a Chef-defined tier to scale.

Remaining Sections

See Understand Application Tier Properties.

See Applications Using Puppet and Chef for additional details.


Back to: OOB Application Services

  • No labels
© 2017-2019 Cisco Systems, Inc. All rights reserved