System information

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.
The following table describes the current mapping between Satellite 5 substitution macros and
Puppet facts.
T ab le 3.1. Map p ing o f Sat ellit e 5 Macros to Sat ellite 6 ( Pup p et ) Fact s
Satellit e 5 Macro Pu p p et 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_devi
ce)
None
T ran sit io n ing Co n f igu rat io n Ch ann els to Pu p p et Mod u les
The following example illustrates a simple use case for transitioning configuration channels to
Puppet modules.
Examp le 3.13. T ran sitio n ing Co n f igu rat io n Ch ann els an d Files to Pu p p et Mod u les
# 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.
Report a bug
3.7.9. T ransit ioning Syst em Profiles t o Cont ent Hosts
Red Hat Satellite 5 uses System Profiles to store information about the systems (machines) that are
registered to it. This includes the operating system version and a list of all packages that are
installed on each system. This applies to both bare-metal and virtual machines.
⁠Chapt er 3. T ransit ioning fro m Sat ellit e 5 t o 6
37