3.7.8. Transitioning Configuration Channels to Puppet Modules
- Generate Puppet modules for each Satellite 5 configuration channel.
- Map any Satellite 5 macros in the configuration files to whatever Puppet facts are found.
- Build the modules.
- Create a Satellite 6 repository for each configuration channel, and a product to hold those repositories.
- Upload the built Puppet modules into Satellite 6.
Table 3.1. Mapping of Satellite 5 Macros to Satellite 6 (Puppet) Facts
|
Satellite 5 Macro
|
Puppet Fact
|
|---|---|
|
rhn.system.sid
|
None
|
| rhn.system.profile_name | None |
| rhn.system.description | None |
| rhn.system.hostname | FQDN or host name |
| rhn.system.ip_address | ipaddress |
| rhn.system.custom_info(key_name) | None |
| rhn.system.net_interface.ip_address(eth_device) | ipaddress_{NETWORK INTERFACE} |
| rhn.system.net_interface.netmask(eth_device) | netmask_{NETWORK INTERFACE} |
| rhn.system.net_interface.broadcast(eth_device) | None |
| rhn.system.net_interface.hardware_address(eth_device) | macaddress_{NETWORK INTERFACE} |
| rhn.system.net_interface.driver_module(eth_device) | None |
The following example illustrates a simple use case for transitioning configuration channels to Puppet modules.
Example 3.13. Transitioning Configuration Channels and Files to Puppet Modules
# hammer import config-file --csv-file /tmp/exports/config-files-latest.csv Writing converted files Building and uploading puppet modules Summary Created 1 puppet file. Created 1 puppet module.

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.