3.5. Preparing for the Transition
- A fully-functional Satellite 5.6 or 5.7 instance exists.
- Satellite 6 has been correctly installed on a new machine.
- Direct connectivity between the Satellite 5 and Satellite 6 instances cannot be guaranteed.
- The Satellite 6 instance contains a manifest that enables access to the same content that the Satellite 5 instance accesses, for the same number of client machines.
- The Satellite 6 instance has already synchronized the desired Red Hat content. The transition tools make every attempt not to copy Red Hat content from Satellite 5 to Satellite 6.
- The export tools execute on the Satellite 5 system. This is necessary to allow direct access to the Satellite 5 database, repositories, and existing tools such as
- The import tools execute on the Satellite 6 system, for similar reasons.
- The result of importing Satellite 5 data is not a perfectly-configured Satellite 6 instance. The goal is to alleviate as much set-up as reasonably possible, given the differences in data-models and functionality between Satellite 5 and 6.
3.5.1. Preparing the Satellite 5 Server for Transition
Install the latest spacewalk-reports and spacewalk-utils packages from the Satellite 5.6 or 5.7 channel.
# yum install spacewalk-reports spacewalk-utils
spacewalk-reportcommand to confirm the addition of these new reports.
spacewalk-exporttools. You can also use these reports for general, day-to-day reporting.
Ensure your Satellite 5 server is subscribed to the RHN Tools channel. This channel provides the latest updates to the subscription-manager and python-rhsm packages, which are required to install the
# yum install subscription-manager python-rhsm
3.5.2. Preparing the Satellite 6 Server for Transition
yum install rubygem-hammer_cli_importto install it from the Satellite 6 repositories.
# hammer import --help Usage: hammer import [OPTIONS] SUBCOMMAND [ARG] ...