Show Table of Contents
1.2. Using Puppet on Satellite 6
Satellite 6 uses Puppet in several ways:
- Satellite 6 imports Puppet modules used to define the system configuration. This includes control over module versions and their environments.
- Satellite 6 imports sets of parameters, also known as Puppet class parameters, from Puppet modules. Users can accept the default values from Puppet classes or provide their own at a global or system-specific level.
- Satellite 6 triggers the execution of Puppet between the master and the respective agents on each system. Puppet runs can occur either:
- Automatically, such as after the provisioning process completes or as a daemon that checks and manages the machine's configuration over its lifecycle.
- Manually, such as needing to trigger an immediate Puppet run.
- Satellite 6 collects reports from Puppet after the configuration workflow completes. This helps with auditing and archiving system configuration over long term periods.
These functions provide an easy way for users to control system configuration aspects of the application lifecycle using Puppet.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.