System information

In Satellite 6, this information is stored in Content Hosts. Instead of "system", Satellite 6 uses the term
"host" to refer to any machine that is registered to it. Part of the transition process maps Satellite 5
System Profiles to Satellite 6 Content Hosts. A Satellite 6 host is created when an actual system re-
registers to Satellite 6 with the consumer ID of the Content Host.
Transitioning system profiles is the last step in the transition process prior to actually transitioning
your Satellite 5 systems to Satellite 6. You can transition system profiles as part of the hammer
i mpo rt al l command, or by specifically importing them, using the hammer i mpo rt al l --
enti ti es co ntent-ho st command.
Bu ilding t h e System Prof ile Tran sit ion RPM File
Before you can transition your Satellite 5 systems to Satellite 6, you need to build the required RPM
file. The hammer i mpo rt al l command displays instructions on how to do this, tailored to your
specific environment, after you have successfully transitioned system profiles to content hosts.
After you have successfully transitioned your system profiles to content hosts, you should see output
similar to the following:
Examp le 3.14 . Examp le In st ru ction s fo r Build in g a Syst em Pro f ile Tran sit ion RPM File
To build the system-profile-transition rpm, run:
cd /root/rpm-working-dir/SPECS & &
rpmbuild -ba --define "_topdir /root/rpm-working-dir" system-profile-
transition-myhost.example.com-1410140956-0.0.1.spec
Then find your system-profile-transition-myhost.example.com-1410140956
package in /root/rpm-working-dir/RPMS/noarch/ directory.
Report a bug
3.7.10. T ransit ioning Syst ems
This section covers background information, prerequisites, and assumptions that must be addressed
prior to transitioning your client systems. It also covers the actual process for transitioning your
Satellite 5 client systems to Satellite 6 client hosts. This process is primarily aimed at customers who
have numerous systems currently registered to a Satellite 5 server.
The system transition process aims to achieve the following goals:
Ensure that each Satellite 5 client is registered to a new Satellite 6 instance, with as much of the
existing Satellite 5 setup maintained as possible.
Help customers stay in compliance with their Red Hat Enterprise Linux usage. The process
removes the Satellite 5 entitlements used by a given system when that system is registered to
Satellite 6.
Report a bug
3.7 .1 0 .1 . Pre re quisit e s
Before you begin the system transition process, ensure that you have each of the following:
An existing, up-to-date Satellite 5.6 server. In this example, this system is called "SAT5.6".
Red Hat Sat ellit e 6 .0 T ransit ion G uid e
38