// removed jquery ui css and js

Puppet Service

Overview

Guidelines

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

Puppet ServiceAssociated Terminology
Repository DependencyMaster
Service AssociationAgent
Configuration  ReferenceManifests

The Puppet Master is available as a repository type. See Share Artifact Repositories for a complete list of available types for repositories.

The CloudCenter platform does not provision or manage the Puppet Master either directly or indirectly. These servers must be pre-configured before adding either as repositories in CloudCenter.

The service script installs, configures, starts, and stops the Puppet Agent. Each service requires the information to setup the Puppet Agent and configure the Puppet role 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.

Puppet Servers

Required. Select the configured Puppet server repository (for example, Puppet Master).

Puppet Role

Required. Configure the application using the configured Puppet role.

Puppet Environment

Required. The service script leverages the function of Puppet Agent to configure the environment and deploy the application.

To associate the Puppet repository (when you Manage Projects and Phases) with the CloudCenter 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 CloudCenter-Defined Parameters and Using Parameters for additional context.

Agent Run Interval

Required. Identifies the frequency at which the service script must leverage the function of Puppet Agent when deploying the application.

Remaining Sections

See Service Properties.

See Model Applications Using Puppet and Chef for additional details.

  • No labels
© 2017 Cisco Systems