Procedure 3.1. Creating a Custom Product

1. Login to your Red Hat Satellite 6 server.
2. Navigate to Content → Products.
3. Click + New Product.
4. Provide your custom product with a Name. In this example, use MyProduct as the name.
5. The Label field automatically populates with a label based on the Name.
6. Provide a GPG Key, Sync Plan, and a Description if required. For our example, leave those fields blank.
7. Click Save.

Procedure 3.2. Creating a Custom Puppet Repository

1. On the Products page, click on the custom product created previously (MyProduct).
2. Navigate to the Repositories subtab.
3. Click Create Repository.
4. Provide the repository with a Name. This example uses the name MyRepo.
5. The Label field automatically populates with a label based on the Name.
6. Select puppet as the repository Type.
7. Leave the URL field blank. This field is used for remote repositories, but in our case Satellite 6 creates its own repository.
8. Click Save.

1. Click the Name of the newly created repository.
2. In the Upload Puppet Module section, click Browse and select the mymodule archive.
3. Click Upload.

1. On the Products page, click on the custom product containing the module to remove.
2. Click the Name of the repository containing the module to remove.
3. Click Manage Puppet Modules. The screen displays a list of Puppet modules contained within the repository.
4. Select the modules to remove.
5. Click Remove Puppet Modules.

Procedure 3.3. Publishing Git Repository to a Local Directory

1. Create a directory on the Satellite server to synchronize the modules.

   # mkdir /modules
   # chmod 755 /modules
   

2. Run the pulp-puppet-module-builder and checkout the Git repository.

   # pulp-puppet-module-builder --output-dir=/modules --url=git@mygitserver.com:mymodules.git --branch=develop
   

   This checks out the develop branch of the Git repository from git@mygitserver.com:mymodules.git and publishes the modules to /modules.

Procedure 3.4. Publishing Git Repository to a Web Server

1. Create a directory on the web server to synchronize the modules.

   # mkdir /var/www/html/modules
   # chmod 755 /var/www/html/modules/
   

2. Run the pulp-puppet-module-builder and checkout the Git repository.

   # pulp-puppet-module-builder --output-dir=/var/www/html/modules/ --url=git@mygitserver.com:mymodules.git --branch=develop
   

   This checks out the develop branch of the Git repository from git@mygitserver.com:mymodules.git and publishes the modules to /modules.

Procedure 3.5. Creating a Repository for Puppet Modules from Git

1. On the Products page, click on the custom product created previously (MyProduct).
2. Navigate to the Repositories subtab.
3. Click Create Repository.
4. Provide the repository with a Name. This example uses the name MyGitRepo.
5. The Label field automatically populates with a label based on the Name.
6. Select puppet as the repository Type.
7. In the URL field, set the location you defined earlier. For example, local directories on the Satellite 6 server use the file:// protocol:

   file:///modules
   

   A remote repository uses the http:// protocol:

   http://webserver.example.com/modules/
   

8. Click Save.
9. Click Sync Now to synchronize the repository.

Procedure 3.6. Publishing a Content View

1. Navigate to Content → Content Views.
2. Click + Create New View.
3. Provide your view with a Name. In this example, we use MyView as the name.
4. The Label field automatically populates with a label based on the Name.
5. Make sure Composite View is not selected.
6. Click Save.
7. Select the Name of your newly created view.
8. Navigate to Content → Repositories.
9. Add the required Red Hat Enterprise Linux repositories, including a base Red Hat Enterprise Linux Server RPM collection and a Red Hat Satellite Tools RPM collection for the same version. The Tools RPM collection contains the packages to set up our remote Puppet configuration on provisioned systems.
10. Navigate to Puppet Modules.
11. Click + Add New Module.
12. Scroll to your module and click Select a Version.
13. Scroll to the module version Use Latest and click Select Version.
14. Our module is now a part of the content view. Navigate to Versions to publish and promote a new version of the content view.
15. Click Publish New Version. On the Publish New Version page, click Save. This publishes the content view with our module.
16. Scroll to the new version of our view and click Promote. Choose a lifecycle environment and click Promote Version. This makes the view a part of the chosen lifecycle environment.

1. Navigate to Configure → Smart variables.
2. A table appears listing all smart variables from the classes in your Puppet modules. Click on the httpd_port variable.
3. The options for the smart variable appears. To allow overriding this variable during provisioning, select the Override option.
4. Selecting the Override option allows us to change the Parameter type and Default value. This is useful if we aim to globally change this value for all future configurations.
   The following parameter types are available:

   String

   The value is interpreted as a plain text string. For example, if your smart variable sets the hostname, the value is interpreted as a string:

   myhost.example.com
   

   Boolean

   The value is interpreted and validated as a true or false value. Examples include:

   True
   true
   1
   

   Integer

   The value is interpreted and validated as an integer value. Examples include:

   8120
   -8120
   

   Real

   The value is interpreted and validated as a real number value. Examples include:

   8120
   -8120
   8.12
   

   Array

   The value is interpreted and validated as a JSON or YAML array. For example:

   ["Monday","Tuesday","Wednesday","Thursday","Friday"]
   

   Hash

   The value is interpreted and validated as a JSON or YAML hash map. For example:

   {"Weekdays": ["Monday","Tuesday","Wednesday","Thursday","Friday"], "Weekend": ["Saturday","Sunday"]}
   

   YAML

   The value is interpreted and validated as a YAML file. For example:

   email:
     delivery_method: smtp
     smtp_settings:
       address: smtp.example.com
       port: 25
       domain: example.com
       authentication: none
   

   JSON

   The value is interpreted and validated as a JSON file. For example:

   {
     "email":[
       {
         "delivery_method": "smtp"
         "smtp_settings": [
           {
             "address": "smtp.example.com",
             "port": 25,
             "domain": "example.com",
             "authentication": "none"
           }
         ]
       }
     ]
   }
   

   For this example, leave the default as 8120.
5. Selecting the Override option also exposes Optional Input Validator, which provides validation for the overridden value. For example, we can include a regular expression to make sure httpd_port is a numerical value. For our example, leave this section blank.
6. Selecting the Override option also exposes Override Value For Specific Hosts, which defines a hierarchical order of system facts and a set of matcher-value combinations. The matcher-value combinations determine the right parameter to use depending on an evaluation of the system facts. For our example, leave this section with the default settings.
7. Click Submit.

Procedure 5.1. Applying Configuration on Clients During Provisioning

1. Navigate to Hosts → New host.
2. Click the Host tab. Enter a Name for the host and choose the organization and location for the system. Choose the Lifecycle Environment and its promoted Content View. This defines the Puppet environment to use for the configuration. Also choose a Puppet CA and Puppet Master from the Capsule Settings. The chosen capsule acts as the server that controls the configuration and communicates with the agent on the new host.
3. Click the Puppet Classes tab and from the Available Classes section choose the Puppet classes that contain the configuration to apply. In our example, choose:
   • mymodule
   • mymodule:httpd
   • mymodule:app
4. Choose the necessary options from the Network and Operating System tabs. These options depend on your own Satellite 6 infrastructure. Make sure the Provisioning templates option includes the Satellite Kickstart Default kickstart template. This template contains installation commands for the Puppet agent on the new host.
5. Click the Parameters tab and provide any custom overrides to our Puppet class parameters. For example, modify the httpd_port from the mymodule to set your own custom port.
6. After completing all provisioning options, click Submit.

Procedure 5.2. To Install and Enable the Puppet Agent:

1. Open a terminal console and log in as root.
2. Install the Puppet agent:

   # yum install puppet
   

3. Configure the puppet agent to start at boot:
   • On Red Hat Enterprise Linux 6:

     # chkconfig puppet on

   • On Red Hat Enterprise Linux 7:

     # systemctl enable puppet

Procedure 5.3. Configuring the Puppet Agent

1. Configure the Puppet agent by changing the /etc/puppet/puppet.conf file:

   # vi /etc/puppet/puppet.conf
   

   [main]
       # The Puppet log directory.
       # The default value is '$vardir/log'.
       logdir = /var/log/puppet
   
       # Where Puppet PID files are kept.
       # The default value is '$vardir/run'.
       rundir = /var/run/puppet
   
       # Where SSL certificates are kept.
       # The default value is '$confdir/ssl'.
       ssldir = $vardir/ssl
   
   [agent]
       # The file in which puppetd stores a list of the classes
       # associated with the retrieved configuratiion.  Can be loaded in
       # the separate ``puppet`` executable using the ``--loadclasses``
       # option.
       # The default value is '$confdir/classes.txt'.
       classfile = $vardir/classes.txt
       pluginsync = true
       report = true
       ignoreschedules = true
       daemon = false
       ca_server = satellite.example.com
       server = satellite.example.com
       environment = KT_Example_Org_Library_RHEL6Server_3
   
       # Where puppetd caches the local configuration.  An
       # extension indicating the cache format is added automatically.
       # The default value is '$confdir/localconfig'.
       localconfig = $vardir/localconfig
   

   Important

   Set the environment parameter to the host's Puppet environment from the Satellite server. The Puppet environment label contains the organization label, lifecycle environment, content view name, and the content view ID. To see a list of Puppet environments in the Satellite 6 web UI, navigate to Configure → Environments.
2. Run the Puppet agent on the host:

   # puppet agent -t --server satellite.example.com

3. Sign the SSL certificate for the puppet client through the Satellite Server web interface:
   1. Log in to the Satellite Server through the web interface.
   2. Select Infrastructure → Capsules.
   3. Click Certificates to the right of the required host.
   4. Click Sign.
   5. Rerun the puppet agent command:

      # puppet agent -t --server satellite.example.com