Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
TetraWiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
GSTN - Satelite As Build Document
(section)
Page
Discussion
English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
===== 1.13. Operations Management ===== ====== 1.13.1. Operation Management β RHEL Configuration Management ====== Operations Management in case of RHEL is referred to as configuration management . This is managed by the puppet Module of Redhat Satellite. Puppet is a tool for applying and managing system configurations. Puppet collects system information, or facts, and uses this information to create a customized system configuration using a set of modules. These modules contain parameters, conditional arguments, actions, and templates. Puppet is used as either a local system command line tool or in a client-server relationship where the server acts as the Puppet master and applies configuration to multiple client systems using a Puppet agent. This provides a way to automatically configure newly provisioned systems, either individually or simultaneously to create a specific infrastructure. ====== 1.13.2. Puppet's configuration management overview ====== Puppet uses the following workflow to apply configuration to a system. Collect facts about each system. These facts can include hardware, operating systems, package versions, and other information. The Puppet agent on each system collects this information and sends it to the Puppet master. The Puppet master generates a custom configuration for each system and sends it to the Puppet agent. This custom configuration is called a catalog. The Puppet agent applies the configuration to the system. The Puppet agent sends a report back to the Puppet master that indicates the changes applied and if any changes were unsuccessful. Third-party applications can collect these reports using Puppet's API. ====== 1.13.3. Configuration Methodology ====== 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. ====== 1.13.4. Configuration Suggested parameter for RHEL ====== {| style="border-spacing:0;width:3.404cm;" |- style="background-color:#ffff00;border:0.5pt solid #000000;padding:0.051cm;" || puppet Modules |- style="border:0.5pt solid #000000;padding:0.051cm;" || Password Ageing |- style="border:0.5pt solid #000000;padding:0.051cm;" || Firewall |- style="border:0.5pt solid #000000;padding:0.051cm;" || NTP |- style="border:0.5pt solid #000000;padding:0.051cm;" || Apache |- style="border:0.5pt solid #000000;padding:0.051cm;" || Mysql |- style="border:0.5pt solid #000000;padding:0.051cm;" || Selinux |- style="border:0.5pt solid #000000;padding:0.051cm;" || PostgreSQL |- style="border:0.5pt solid #000000;padding:0.051cm;" || sysctl |- style="border:0.5pt solid #000000;padding:0.051cm;" || Timezone |- style="border:0.5pt solid #000000;padding:0.051cm;" || LVM |- style="border:0.5pt solid #000000;padding:0.051cm;" || SUDO |- style="border:0.5pt solid #000000;padding:0.051cm;" || Ssh |- style="border:0.5pt solid #000000;padding:0.051cm;" || rsyslog |- style="border:0.5pt solid #000000;padding:0.051cm;" || dns |- style="border:0.5pt solid #000000;padding:0.051cm;" || dhcp |- style="border:0.5pt solid #000000;padding:0.051cm;" || snmp |- style="border:0.5pt solid #000000;padding:0.051cm;" || accounts |- style="border:0.5pt solid #000000;padding:0.051cm;" || postfix |- style="border:0.5pt solid #000000;padding:0.051cm;" || Crons |- style="border:0.5pt solid #000000;padding:0.051cm;" || Mongodb |- style="border:0.5pt solid #000000;padding:0.051cm;" || Bind |- style="border:0.5pt solid #000000;padding:0.051cm;" || Timezone |- style="border:0.5pt solid #000000;padding:0.051cm;" || JDK7 |- style="border:0.5pt solid #000000;padding:0.051cm;" || nfs |- style="border:0.5pt solid #000000;padding:0.051cm;" || Openstack |- |} ====== 1.13.5. Reports ====== Puppet generates a report each time it applies configuration. Provisioned hosts send this report to the Red Hat Satellite 6 server. View these reports on the hosts details page Each report shows the status of each Puppet resource and its configuration applied to the host.
Summary:
Please note that all contributions to TetraWiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
TetraWiki:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)