Chapter 3. Transitioning from Satellite 5 to 6
- Satisfy requirements: this phase consists of ensuring that all transition prerequisites are satisfied. Failure to meet these requirements might result in an incomplete or failed transition.
- Preparation: this phase consists primarily of preparing the Satellite 6 system to receive data from the existing Satellite 5 system.
- Transition: this phase consists of exporting the data from the existing Satellite 5 system, transferring that data to the Satellite 6 system, and then tuning the configuration to suit your deployment.
3.1. The Transitioning Strategy
In a passive transition scenario, the workloads remain on Satellite 5. This strategy is most appropriate if your Satellite deployment is complex and involves significant integration with other applications via APIs or other processes. In this case, Red Hat Satellite 6 is deployed to manage only new workloads and projects, whereas Red Hat Satellite 5 is maintained in order to manage existing workloads until they are retired. Satellite 5 data models may or may not be transitioned to Satellite 6. A passive transition gives administrators the most freedom to reconsider their infrastructure with the least possibility of any disruption to services.
In an active transition scenario, all workloads are moved to Satellite 6. The object of this strategy is to decommission Satellite 5 after translating the Satellite 5 data models to Satellite 6 and registering systems to the new Satellite. All new workloads and projects are targeted for management by Satellite 6. An active transition allows data models to remain somewhat similar and familiar with all workloads appropriately migrated to the new Red Hat Satellite. The originating Satellite 5 is then free to be transitioned into an archived state and shut down.