Add a Configuration Manager

As a Release Manager or other type of Administrator, you can use the Configuration Management function to create current releases. This function provides smooth integration with a growing catalog of infrastructure configuration management solutions, such as Chef, Puppet, CFEngine, or Salt.
ra55
As a Release Manager or other type of Administrator, you can use the
Configuration Management
function to create current releases. This function provides smooth integration with a growing catalog of infrastructure configuration management solutions, such as Chef, Puppet, CFEngine, or Salt.
You can use this option to ensure that all release management deployment servers are baselined before you start your release deployment. This baseline, or profile, has objects that meet specified requirements. For example, all servers must have the correct version of Tomcat, or all of the firewalls must be open.
The basic flow to add a Configuration Manager starts in the
Administration
tab, under
Configuration Manager
. Start with a
Configuration Manager
type, such as Chef or Puppet, and add a new server and the requisite information.
Chef
Follow these steps:
  1. As a prerequisite, install a 
    Nolio Release Automation
     agent on the Chef workstation.
  2. In Release Operations Center, go to
    Administration
    and select
    Configuration Management
    .
  3. From the
    Configuration Management
    screen, select
    Chef
    as the
    Configuration Manager
    type.
  4. Click
    +Add New Server
    .
  5. From the
    Config Chef Server
    window, provide the required information in the following fields:
    • Chef Workstation
      The Chef environment includes the Chef workstation, server, and nodes. Use the work station to perform operations such as create and update a recipe.The workstation and nodes connect to the Chef server. 
      Note:
      The drop-down field searches and lists the active, connected agents based on your input. Ensure that the selected agent is running on the Chef Workstation.
    • Repository Location
      Identifies the path to the workstation repository. The repository stores data objects such as recipes, roles, and environments. One Chef workstation can point to multiple Chef servers. The workstation repository identifies which Chef server the workstation points to.
    • Knife Location
       Provides the path to the Knife command executable.The Knife tool bridges a local Chef repository and a Chef server.
      Note:
      Place the knife.rb file in the .chef/ sub-directory under the chef-repo directory. Validation fails if the knife.rb file is in a different directory path. Ensure that the user where the agent is running has read and write access to the chef-repo directory.
  6. To verify the connectivity between the workstation and the Chef server, click
    Validate
    . The validation action verifies the existence and paths of the repository and Knife executable. During validation, the knife.rb file within the repository is parsed to determine which Chef server the repository points to.
    Note:
    When you register your Chef server for the first time, the
    read-only Chef Server
    and
    Chef Organization
    fields display upon validation.
  7. Click
    Save
    The new server is listed in the Chef Server pane. From this list, servers can be edited and deleted. To edit servers, change the values, for example in the Knife location or repeat validation fields, and click save.
    Note:
     The system allows for the addition of multiple Chef servers.
  8. (optional) Use the supported Chef Enterprise version to define and add organizations to the list. 
    Example:
    You can set Chef server ca.com to represent org 1, and RA Chef server ca.com for org 2.
Puppet
Follow these steps:
  1. As a prerequisite, install a 
    Nolio Release Automation
     agent on the Puppet Master Server and Puppet Agent.
  2. In Release Operations Center, go to
    Administration
    and select
    Configuration Management
    .
  3. From the
    Configuration Management
    screen, select
    Puppet
    as the
    Configuration Manager
    type.
  4. Click
    +Add New Server
    .
  5. From the
    Add Puppet Master Server
    window:
    • Click the drop-down list and select an available agent on which the Puppet Master is installed.
    • Enter the full path of the puppet executable. The execution of Puppet commands in this specified location reduces security vulnerabilities.
    • Enter the location of the configuration directory of the Puppet Master Server. 
      Before you validate connectivity, ensure that the puppet executable is in the specified location. After you validate, only update the *.pp files in confdir.
  6. To verify the connectivity between the agent and the Puppet Master Server, click
    Validate
    . Upon validation, the
    Save
    button activates.
  7. Click
    Save
    .
    The Puppet Master Server is registered into the system. This server lists in the
    Puppet Master Server
    pane with a status of
    Connected
    . Optionally, from this list, you can delete a server.