Red Hat Satellite 6 Red Hat Satellite 6 Beta Transition ... · In an active transition, the object is to decommission Satellite 5 after translating Satellite 5 data models to Satellite

Clifford Perry Grant Gainey

Red Hat Satellite 6Red Hat Satellite 6 BetaTransition Tooling

Red Hat Satellite 5.6 to 6.0 Beta Transition Tooling GuideEdition 1

Red Hat Satellite 6 Red Hat Satellite 6 Beta Transition Tooling

Red Hat Satellite 5.6 to 6.0 Beta Transition Tooling GuideEdition 1

Cliffo rd PerryRed Hat [email protected]

Grant GaineyRed Hat [email protected]

Legal Notice

Copyright © 2014 Red Hat, Inc.

This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 UnportedLicense. If you distribute this document, or a modified version of it, you must provide attribution to RedHat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must beremoved.

Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section4d of CC-BY-SA to the fullest extent permitted by applicable law.

Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo,and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.

Linux ® is the registered trademark of Linus Torvalds in the United States and other countries.

Java ® is a registered trademark of Oracle and/or its affiliates.

XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United Statesand/or other countries.

MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and othercountries.

Node.js ® is an official trademark of Joyent. Red Hat Software Collections is not formally related to orendorsed by the official Joyent Node.js open source or commercial project.

The OpenStack ® Word Mark and OpenStack Logo are either registered trademarks/service marks ortrademarks/service marks of the OpenStack Foundation, in the United States and other countries andare used with the OpenStack Foundation's permission. We are not affiliated with, endorsed orsponsored by the OpenStack Foundation, or the OpenStack community.

All other trademarks are the property of their respective owners.

Abstract

How to transition and recreate existing Satellite 5.6 data in your Satellite 6.0 Beta

http://creativecommons.org/licenses/by-sa/3.0/

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table of Contents

Chapter 1. Introduction1.1. Introduction and Goals1.1.1. Introduction1.1.2. Strategy1.1.3. Goals

Chapter 2. Frequently Asked Questions2.1. How to contact Red Hat2.2. Is it an in-place upgrade or do I need to install Satellite 6 Beta onto a new RHEL Serverinstance?2.3. Which version of Satellite 5.x is supported for the transition?2.4. Which versions of RHEL will Satellite 5 and Satellite 6 support as client systems?2.5. Give me the quick version, how will customers transition from Satellite 5 to 6?2.6. My Satellite server is disconnected, will this tooling work?2.7. Can I rerun this tooling/process multiple times?2.8. Can the Satellite 6.0 Beta be used for production?2.9. Is it safe to run the exporter tooling on my production Satellite 5.6 system?

Chapter 3. Transit ion Tooling Use Cases Summary3.1. Transition Tooling Use Case Summary for Satellite 6.0 Beta

Chapter 4 . Transit ion Tooling Details4.1. Assumptions4.2. Overview4.3. Satellite 5.6 Preparation4.4. Satellite 6.0 Beta Preparation4.5. How to Export from Satellite 5.64.6. How to Import to Satellite 6 Beta4.6.1. Organizations4.6.2. Users4.6.3. Manifest activation4.6.4. External Yum Repositories4.6.5. Enable Red Hat Repositories4.6.6. Import Custom & Cloned Custom Channels as Content Views4.6.7. Import System Groups to Host Collections4.6.8. Import Activation Keys

4.7. Next steps

Revision History

Index

22222

33

33333333

55

666677889

10101112131314

15

15

Table of Contents

1

Chapter 1. Introduction

1.1. Introduction and Goals

1.1.1. Introduction

Over a span of 12 years (since 2002), Red Hat Satellite grew from a ambitious “on-premise update” service into the very popular robust systems management productthat it is today. In that spirit, at the forefront of leading edge open source technologies, Red Hat is taking another bold step forward with the introduction of the Red HatSatellite 6 Beta. But Red Hat Satellite 6 will not merely be an upgrade. It represents a leap to the most advanced available technologies today positioning Satellite as thepremier mechanism to manage workloads for the next decade, embracing modern models of bare-metal, virtual, and cloud-based management. Because Red HatSatellite 6 is a top-to-bottom technology update to the Red Hat Satellite family, the transition is just that ... a transition, and not a traditional upgrade. The intent of thispaper is to help prepare you for making this transition, if and when Red Hat Satellite 6 becomes available later in 2014.

1.1.2. Strategy

With a transition versus an upgrade in mind, there will be several strategies to go from Satellite 5 to Satellite 6. Essentially there are two. Both involve standing upSatellite 6 architecture next to your Satellite 5 architecture. The two strategies:

1. Passive Transition – Legacy workloads remain on Satellite 5

This strategy is most appropriate if your Satellite deployment is complex with 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 theyare retired. Satellite 5 data models may or may not be transitioned from Satellite 5 to Satellite 6. A passive transition gives administrators the most freedom to re-think /re-envision their infrastructure with the least possibility of any disruption of services.

2. Active Transition – Move all workloads to Satellite 6

In an active transition, the object is to decommission Satellite 5 after translating Satellite 5 data models to Satellite 6 and re-registering systems to the new Satellite. Allnew workloads and projects, of course, 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 originatingSatellite 5 is then freed to be transitioned into an archived state and shut down. Transitioned and done!

1.1.3. Goals

The goal of this guide is to provide an overview of the Active Transition use-case and to use the Transition Tools being created to ease customer transitions frominstalled Satellite 5.6 instances to new Satellite 6 instances. This guide is specifically covering the tooling available for the Satellite 6 Beta release. With the release ofSatellite 6.0 Beta we are providing a work-in-progress snapshot in time of functionality of tooling we plan to provide for GA.

Further information on Satellite 6.0 Beta Server can be found within Red Hat Customer Portal documentation, including an Overview Transition Guide which provides anoverview of differences between Satellite 5 and 6.


2

Chapter 2. Frequently Asked Questions

2.1. How to contact Red HatIf you have questions about the Satellite 6.0 Beta program please review the main Satellite 6.0 Beta documents for details. Please contact Red Hat Support ifassistance is required with the 6.0 Beta program. We welcome feedback on your experiences with the Transition Tooling. Bugzillas for any aspect of Transitions canbe reported here:

https://bugzilla.redhat.com/enter_bug.cgi?product=Red%20Hat%20Satellite%206&component=Transitions

2.2. Is it an in-place upgrade or do I need to install Satellite 6 Beta onto a new RHEL Server instance?The underlying technologies between Satellite 5 and 6 are significantly different so the in-place upgrade process (such as for versions 4.x->5.x or 5.x->5.y) does notapply for version 5->6. The Satellite 6 Beta will need to be installed on a new server as part of the side-by-side transition process. Hence, we call this a transitionprocess and not an upgrade process.

2.3. Which version of Satellite 5.x is supported for the transition?The transition path begins with Satellite 5.6. So for customers running a previous version of Satellite they will need to first upgrade to version 5.6.

Upon future release of Satellite 5.7, we will also support that version as a platform for moving from Satellite 5 to 6.

Upon future release of Satellite 6.1, 6.2, etc. - we will also support those versions as a platform for moving too, from Satellite 5.

NOTE If you plan a more passive transition process the prior Satellite version does not matter. A passive transition process is more of an adoption process wherelegacy workloads remain on Satellite 5 and new workloads are freshly modelled on Satellite 6 as if it is treated as new infrastructure for your RHEL SystemsManagement needs.

2.4. Which versions of RHEL will Satellite 5 and Satellite 6 support as client systems?At time of Satellite 6.0 Beta the following is true. The matrix is unlikely to change between Beta and GA of Satellite 6.0.

Satellite 5.6 supports clients of RHEL versions 4, 5, 6, and 7.

Satellite 6 supports clients of RHEL versions 5.7 and newer, 6.1 and newer, and 7.0 and newer

Satellite 6 does not support clients of version RHEL 4.

2.5. Give me the quick version, how will customers transition from Satellite 5 to 6?Install Satellite 6 Beta, activate with a Manifest and sync RHEL content from CDN

Review documentation, learn and understand the basics of the new Satellite 6 product, including new concepts, such as environments.

Back up the new Satellite 6 Beta server, including databases before using the Transition Tooling.

As root on Satellite 5.6 run the exporter command line tool.

Copy the resulting data onto Satellite 6.

As root on Satellite 6 Beta, run the hammer importer command line tools.

Validate and test resulting Satellite 6 Beta system for a subset of end to end functionality and use-cases of importance for customer corresponding to the data-types transitioned from Satellite 5.6 to 6 Beta.

NOTE: Since not all of the concepts can be translated between Satellite 5 and 6, some manual steps will also need to be taken to fully populate the newly installedSatellite 6 server.

2.6. My Satellite server is disconnected, will this tooling work?Yes, the transition tooling is designed such that a disconnected environment is assumed, and neither Satellite 5 nor 6 can directly communicate to each other or theinternet in general.

2.7. Can I rerun this tooling/process multiple times?Yes, the tooling created is designed to be idempotent. It will allow you to reuse the tooling to create Satellite 6 data and preserve previous information over successiveruns of the tooling. We aim to do this by using a small datafile on the Satellite 6 server to preserve the history of previous runs and know what has already beenimported.

2.8. Can the Satellite 6.0 Beta be used for production?No, the Beta is not for production usage and there is no supported upgrade path from Satellite 6 Beta to GA. As such any systems that are migrated to a Satellite 6Beta Server would be for testing purposes only and not production use. We expect all Satellite 6.0 Beta Server instances to be decommissioned at the end of the betacycle.

2.9. Is it safe to run the exporter tooling on my production Satellite 5.6 system?

Chapter 2. Frequently Asked Questions

3

https://bugzilla.redhat.com/enter_bug.cgi?product=Red Hat Satellite 6&component=Transitions

Yes, assuming that you run the tooling with sufficient disk space. Disk space will vary, from 20MB to a few Gig, depending on total amount of non-Red Hat content isstored on the Satellite within /var/satellite/redhat/ and being selected for exporting by the tooling. When exporting custom or cloned channels, we look for non-Red Hatcontent associated with the channels, to copy into the export archive. Other than some short term CPU and memory consumption, the tooling just performs read-onlyfile-system, and SQL queries on the database to gather data, write the resulting data to files on disk and create a tar archive of the data.


4

Chapter 3. Transition Tooling Use Cases Summary

3.1. Transition Tooling Use Case Summary for Satellite 6.0 BetaFor Red Hat Satellite 6 Beta our existing customers can use the transition tooling processes to complete a subset of use-cases and provide us feedback. Within thissection we will provide a summary of functional use-cases supplied with the Beta program for Satellite 6.

Recreate Satellite 5 Organizations as Satellite 6 Organizations

Allowing to flatten multiple Satellite 5 Organizations into a single new Organization within Satellite 6

Recreate Satellite 5 Users as Satellite 6 Users within correct Organizations

Map Satellite 5 Satellite and Organization Administrator roles to the Satellite 6 Administrator role.

Recreate Satellite 5 System Groups to Satellite 6 Host Collections

Recreate external yum repo definitions from Satellite 5 to 6

Identify synchronized Red Hat channels from Satellite 5 and enable corresponding Satellite 6 Red Hat repositories

Recreate Satellite 5 custom channels as Satellite 6 content views

Recreate Satellite 5 cloned from custom channels as Satellite 6 content views

Recreate Satellite 5 Activation Keys as Satellite 6 Activation Keys

Transition Tooling Beta Excluded Use Cases

The tooling provided within the beta program is not 100% feature complete and currently excludes:

The ability to reregister existing systems from Satellite 5 to Satellite 6.The ability to create content views based on Satellite 5 cloned from Red Hat channels.The ability to recreate Satellite 5 kickstart scripts to Satellite 6 provisioning snippetsThe ability to recreate Configuration channel files as Puppet Modules.

Chapter 3. Transition Tooling Use Cases Summary

5

Chapter 4. Transition Tooling Details

4.1. AssumptionsThe assumptions made during the Satellite 6 Beta for the transition tooling are:

There is an existing Satellite 5.6 instance

Satellite 6 Beta has been installed on a new machine.

Direct connectivity between the Satellite 5 and Satellite 6 instances cannot be guaranteed.

The Satellite 6 instance has already been given a manifest enabling access to the same content that the Satellite 5 instance accesses, for the same number ofclient machines.

The Satellite 6 Beta instance has already synchronized desired Red Hat content. (Transition Tooling will try very hard to not copy Red Hat content from Satellite 5to Satellite 6)

Export tools execute on the Satellite 5 system. This is necessary in order to allow direct access to Satellite 5's database, repositories, and existing tools likespacewalk-report.

Import tools execute on the Satellite 6 Beta 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 thedifferences in data-models and functionality between Satellite 5 and 6.

4.2. OverviewTo prepare for transition, the basic work-flow is:

1. Install Satellite 6.0 Beta Server

2. Import an appropriate manifest into the Satellite 6 instance

3. Synchronize Red Hat content into the Satellite 6 instance.

At this point, the Satellite 6 instance is ready to accept transition data. The transition work-flow is

1. Export entities (meta-data and content) from an installed Satellite 5.6 system, with tools executing on the Satellite 5 machine.

2. Deliver export-data to the Satellite 6 instance, via means such as scp or transfer via USB.

3. Import content from the Satellite 5 data, using tools executing on the Satellite 6 instance.

4. Satellite 6 configuration is then tuned to match the customer's use-cases.

On the export-side, much of the work of extracting information is accomplished via the existing spacewalk-report tool; several new reports have been added. There arealso two new tools:

1. spacewalk-channel-export: Exports channel data and meta-data, beyond that available at a report-level

2. spacewalk-export: Primary tool which wraps up the various tool-execution needed to export the data that can be transferred, and packages all the results up inone dataset ready to be transported to the Satellite 6 system.

On the import-side, import-tooling is based on a plug-in for the hammer-cli tool. This plug-in understands the Satellite 5 export data format and will access the Satellite6 instance over its public API.

The import tooling tracks which Satellite 5 entities have been mapped to which created Satellite 6 entities. This allows the import tooling to be executed multiple times;each execution will only create entities that have not already been seen.

Transition Tooling RPMs

1. Ensure RPMs are on Satellite 5.6 and 6.0 Beta. Details are below.2. Please note that by default the RPMs used for Transition Tooling are not installed for Satellite 6.0 Beta. You will need to install these before proceeding.

4.3. Satellite 5.6 PreparationInstall the newest spacewalk-report & spacewalk-utils RPMs from the Satellite 5.6 channel.

yum update spacewalk-report spacewalk-utils

Installation of the new spacewalk-report package will provide additional new reports which are used by the transition tooling:

activation-keys

custom-channels

kickstart-scripts

repositories

You can run the spacewalk-report command line to confirm the addition of these new reports.

Installation of the new spacewalk-utils package will provide two new additional command line tools, which are used for the transition tooling:

/usr/bin/spacewalk-export


6

/usr/bin/spacewalk-export-channels

Satellite 5.6 Export RPMs

1. The new spacewalk-report RPM is fully supported by Red Hat and provides additional reports which are used by the spacewalk-export tooling, but canalso be used in general by customers.

2. The new spacewalk-utils RPM contains Technology Preview tools, spacewalk-export, spacewalk-channel-export - which are released into the Satellite5.6 channel for usage by any customers wishing to test the transition tooling process as part of their Satellite 6.0 Beta testing. We will release updatedand fully supported spacewalk-export, spacewalk-channel-export tooling with Satellite 6 GA.

4.4. Satellite 6.0 Beta PreparationMount the Satellite 6.0 Beta ISO and then

yum localinstall /path/to/ISO/RPMS/rubygem-hammer_cli_import-*

You can run the following command to confirm that it was successfully installed:

# hammer import --helpUsage: hammer import [OPTIONS] SUBCOMMAND [ARG] ...

4.5. How to Export from Satellite 5.6Exporting from Satellite 5

You can run the export while Satellite 5 is running. However, data added during the export process may not arrive on the Satellite 6 instance in a consistentstate.

The expected work flow on the Satellite Server 5.6 is to use the spacewalk-export tooling as a wrapper to:

1. Export Organizations and Users using spacewalk-report users

2. Export System Groups using spacewalk-report groups

3. Export Repositories using spacewalk-report repositories

4. Export Custom Channels using spacewalk-report custom-channels

5. Export Cloned Channel meta-data using spacewalk-export-channel

6. Export Activation Keys using spacewalk-report activation-keys

Running the exports directly on the 5.6 Satellite allows complete access to the spacewalk-export functionality (including limiting the data exported, using spacewalk-report's --where and --like functionality). However, if the goal is transport everything we can (or at most limit by-organization), we can use the spacewalk-export tool tomanage the process for us.

spacewalk-export will tell you what entities it knows how to extract for you

# spacewalk-export --list-entitiesINFO: Currently-supported entities include:INFO: channels : Custom/cloned channels and repositories for all organizationsINFO: system-groups : System-groups for all organizationsINFO: activation-keys : Activation keysINFO: repositories : Defined repositoriesINFO: users : Users and Organizations#

spacewalk-export can limit by entity:

spacewalk-export --entities users,repositories

And/or by organization:

spacewalk-export --select-orgs=

By default, it will store all exports into ~/spacewalk-export-dir/exports, and by default it will package up everything exported into the file ~/spacewalk-export-dir/spacewalk_export.tar.gz. Both of these are under user control:

spacewalk-export --export-dir=

spacewalk-export --export-package=

If you are OK with the defaults, let spacewalk-export do everything - a typical export session looks like:

# spacewalk-exportINFO: Processing channels...Processing organization: GLOBAL SUPPORT SERVI RED HAT, INC. * channel: clone-rhel-x86_64-server-5 with: 15778 packages * channel: clone-rhel-x86_64-server-6 with: 12157 packages * channel: clone-rhel-x86_64-server-optional-6 with: 6931 packages * channel: clone-rhel-x86_64-server-supplementary-5 with: 1672 packages


7

* channel: clone-rhn-tools-rhel-x86_64-server-5 with: 557 packages * channel: clone-rhn-tools-rhel-x86_64-server-6 with: 122 packages * channel: custom-clone-client-puppet-rhel5-server-x86_64 with: 7 packages * channel: custom-clone-client-puppet-rhel6-server-x86_64 with: 8 packages * channel: custom-clone-master-puppet-rhel6-server-x86_64 with: 18 packages * channel: epel-puppet-rhel6-server-x86_64 with: 8 packages * channel: puppet-rhel5-server-x86_64 with: 409 packages * channel: puppet-rhel6-server-x86_64 with: 373 packagesINFO: Processing system-groups...INFO: Processing activation-keys...INFO: Processing repositories...INFO: Processing users...INFO: Export-file created at /root/spacewalk-export-dir/spacewalk_export.tar.gz#

The file /root/spacewalk-export-dir/spacewalk_export.tar.gz can now be transferred to the Satellite 6 Beta instance, ready for the next step.

4.6. How to Import to Satellite 6 BetaThe spacewalk_export.tar.gz archive is now on your Satellite 6 Beta instance.

Location of Export on Satellite 6 Beta

We strongly recommend to place the spacewalk_export.tar.gz file within /tmp/ on your Satellite 6 Beta system.

Ensure you have sufficient disk space to extract the archive within /tmp/Extract the spacewalk_exports.tar.gz archive in /tmp/ and point the hammer import commands to this directory locationIn the end you will have /tmp/exports/ with all the exported data, ready to use to import and recreate within your Satellite 6 Beta serverWe set up and use local disk mirrors to import data from the archive into Satellite 6 for content, so if /tmp/ cannot be used, ensure that the location used hasread access access by the pulp service.For pulp, ensure that the Apache group has read access to the /tmp/exports/ directory, and if need be use commands:

1. chgrp -R apache /tmp/exports/2. chmod 0750 /tmp/exports/ /tmp/exports/CHANNELS/

Once the data exported from Satellite 5 is available on the Satellite 6 system, it is ready to be imported. The expected work flow on the import side is:

1. Import Organizations

2. Import Users

3. Activate Manifests into each new Organization

4. Import Repositories

5. Run Repository Discovery, enable & sync

6. Import Custom Channels & Cloned Custom Channels as Content Views

7. Import System Groups to Host Collections

8. Import Activation Keys

When importing, order matters! Since entities are owned by Organizations in Satellite 5, you have to import Organizations before Users, for example. If we assumethere is a set of Satellite 5 export-files available, importing them by hand would like like this:

# hammer shell

Welcome to the hammer interactive shell

Type 'help' for usage information Command completion is disabled on ruby < 1.9 due to compatibility problems.hammer> import organization --csv-file=<FILE>hammer> import user --csv-file=<FILE>

Or, if the Satellite 5 data has all been stored under /tmp/exports (the result, for example, of unpacking the output of spacewalk-export...), then the user could import it allwith

# hammer shell

hammer> import all dir --dry-runIMPORT organizations FROM /tmp/exports/users.csvIMPORT users FROM /tmp/exports/users.csvhammer> import dir

Hammer import ordering and options

For the Satellite 6 Beta the all option for hammer import is not fully functional and so not being covered in detail within this guide. Instead we will walk youthrough each step in order to successfully complete the recreation of all data available within the version of the tooling provided for the Beta program. Pleasefollow the next sections in order for complete end to end recreation of data into your Satellite 6 Beta server.

4.6.1. Organizations


8

To import Organizations, use the users.csv file and recreate the Satellite 5.6 organizations listed within it. You can use the hammer interactive shell, as shown below ordirectly from the command line, hammer import organization --csv-file /tmp/exports/users.csv. Below is an example session of what this import session can looklike.

# hammer shellWelcome to the hammer interactive shellType 'help' for usage informationCommand completion is disabled on ruby < 1.9 due to compatibility problems.hammer> hammer> import organization --helpUsage: import organization [OPTIONS]

Options: --csv-file FILE_NAME CSV file --delete Delete entities from CSV file Default: false --into-org-id ORG_ID Import all organizations into one specified by id --recover RECOVER Recover strategy, can be: rename (default), map, none Default: :rename -h, --help print helphammer> import organization --csv-file /tmp/exports/users.csvCreating new organization: RED HAT SATELLITE ENGINEERINGOrganization [1->3] already imported.Organization [1->3] already imported.Organization [1->3] already imported.Organization [1->3] already imported.Organization [1->3] already imported.Organization [1->3] already imported.Creating new organization: Sec eng Dept.Organization [2->4] already imported.Creating new organization: QA Creating new organization: SecurityOrganization [5->6] already imported.Creating new organization: JBoss QAOrganization [26->7] already imported.Organization [26->7] already imported.Organization [26->7] already imported.hammer>

Use the command line hammer organization list command to list the Organizations within Satellite 6, alternatively login to the WebUI of Satellite 6.0 Beta.

hammer> organization list---|-------------------------------|-------------------------------|-------------------------------------------------------------ID | NAME | LABEL | DESCRIPTION ---|-------------------------------|-------------------------------|-------------------------------------------------------------1 | ACME_Corporation | ACME_Corporation | ACME_Corporation Organization 7 | JBoss QA | JBoss_QA | Imported 'JBoss QA' organization from Red Hat Satellite 5 5 | QA | QA | Imported 'QA' organization from Red Hat Satellite 5 3 | RED HAT SATELLITE ENGINEERING | RED_HAT_SATELLITE_ENGINEERING | Imported 'RED HAT SATELLITE ENGINEERING' organization from..4 | Sec eng Dept. | Sec_eng_Dept_ | Imported 'Sec eng Dept.' organization from Red Hat Satelli.. 6 | Security | Security | Imported 'Security' organization from Red Hat Satellite 5 ---|-------------------------------|-------------------------------|-------------------------------------------------------------hammer>

Hammer Import Organization Notes

We create Organizations based on the Organizations listed in the user file.We will map the Satellite 5 organization id to a newly created Satellite 6 organization id, this is seen by "[2->4]", "[26->7]" above. This data is stored in asimple data fileIf you wish to delete specific entries the import tooling has --delete for many items, which is preferable to use.If for some reason, you wanted to delete all of the mappings, the data file is within ~/data/.If we had wanted to flatten all of these Satellite 5 organizations into a single organization within Satellite 6, we would have passed the "--into-org-id" option.We have a log file of hammer commands within /root/.foreman/historyWe have a log file of errors from hammer within /root/.foreman/log/hammer.log

4.6.2. Users

To import Users, use the users.csv file and recreate the Satellite 5.6 users associated with each Satellite 5 Organization. Because user passwords cannot be copiedover from Satellite 5 to 6, we will generate a new random password for each user created. This is saved within a .csv file, which as the administrator you can use toparse and send notifications to each user listed with their new password. You can use the hammer interactive shell, as shown below or directly from the command line,hammer import users --cvs-file /tmp/exports/users.csv --new-passwords /path/to/new/user/passwords.csv. Below is an example session of what thisimport session can look like.

hammer> import user --helpUsage: import user [OPTIONS]

Options: --csv-file FILE_NAME CSV file --delete Delete entities from CSV file Default: false --merge-users Merge pre-created users (except admin) Default: false --new-passwords FILE_NAME Output for new passwords --recover RECOVER Recover strategy, can be: rename (default), map, none Default: :rename --role-mapping FILE_NAME Mapping of Satellite-5 role names to Satellite-6 defined roles Default: "/etc/hammer/cli.modules.d/role_map.yml"


9

-h, --help print helphammer> import user --csv-file /tmp/exports/users.csv --new-passwords /root/new-user-passwords.csvCreating new user: sat5_adminCreating new user: auser1Creating new user: auser2

To show the users were created, login to the WebUI and go under Administer -> Users. Alternatively use the hammer command line as shown below

# hammer user list----|----------|--------------------------|----------------------------ID | LOGIN | NAME | EMAIL ----|----------|--------------------------|----------------------------5 | auser1 | A User1 | [email protected] 4 | auser2 | A User2 | [email protected] 1 | admin | Admin User | [email protected]

# hammer user list --search sat5_admin---|------------|---------|------------------ID | LOGIN | NAME | EMAIL ---|------------|---------|------------------3 | sat5_admin | Hat Red | [email protected]|------------|---------|------------------#

The password file for the users will look similar to this:

# head new-user-passwords.csv mail,login,[email protected],sat5_admin,[email protected],auser1,[email protected],auser2,auser2_rsgywazf#

Hammer Import User Note

By default Satellite 6 creates an admin user as the initial Administrator. It is common for Satellite 5 customers to also create a generic admin user, as such, if wedetect a Satellite 5 admin user, we will recreate them as sat5_admin.

4.6.3. Manifest activation

Before proceeding we need to activate a Manifest into the new Organization(s) for which you want to populate content and other data within.

Please review the main Satellite 6 Beta documentation but you will want to generate a Manifest from within the Red Hat Customer Portal and then need to activate aManifest for the imported Organization. To activate the new Manifest you need to

Login to the Satellite 6 WebUI as an Administrator user

Select the Organization from the top left Organization selector

Go to Content -> Red Hat Subscriptions

Within the Upload New Manifest box, browse local disk, select and then upload.

DONE

Repeat for each organization of interest for your usage during the Satellite 6 Beta testing of the Transition Tooling.

4.6.4. External Yum Repositories

We next want to recreate all non-Red Hat yum repositories that Satellite 5.6 was aware off as new external yum repositories for Satellite 6 to import content from.

We need to import the content, we can either do this by passing the --synchronize option to initiate the repo-sync in the background, or we can use --wait to run in theforeground and wait for it to complete, before proceeding to the next repo. If you do not pass either flag, you can import them manually using the WebUI or hammercommands.

# hammer import repository --helpUsage: hammer import repository [OPTIONS]

Options: --csv-file FILE_NAME CSV file --delete Delete entities from CSV file Default: false --recover RECOVER Recover strategy, can be: rename (default), map, none Default: :rename --synchronize Synchronize imported repositories Default: false --wait Wait for repository synchronization to finish Default: false -h, --help print help# # hammer import repository --csv-file /tmp/exports/repositories.csv --synchronizeCreating new product: PUPPETLABS.COMCreating new repository: puppet-rhel6-server-x86_64Sync started!Product [1PUPPETLABS.COM->116] already imported.Creating new repository: puppet-deps-rhel6-server-x86_64Sync started!Product [1PUPPETLABS.COM->116] already imported.Creating new repository: puppet-rhel5-server-x86_64Sync started!


10

Product [1PUPPETLABS.COM->116] already imported.Creating new repository: puppet-deps-rhel5-server-x86_64Sync started!Creating new product: FEDORAPROJECT.ORGCreating new repository: epel-rhel6-server-x86_64Sync started!#

You can view the resulting products and repos within the Satellite 6 WebUI by going to Content -> Products for the Organization in question. Or using the hammercommand:

# hammer organization list---|------------------------------------|------------------------------------|------------------------------------------------------------------------ID | NAME | LABEL | DESCRIPTION ---|------------------------------------|------------------------------------|------------------------------------------------------------------------1 | ACME_Corporation | ACME_Corporation | ACME_Corporation Organization 3 | GLOBAL SUPPORT SERVI RED HAT, INC. | GLOBAL_SUPPORT_SERVI_RED_HAT__INC_ | Imported 'GLOBAL SUPPORT SERVI RED HAT, INC.' organization from Red ...---|------------------------------------|------------------------------------|------------------------------------------------------------------------## hammer product list --organization-id 3 ---|----------------------------------------------------------------------------------|------------------------------------|--------------|-----------ID | NAME | ORGANIZATION | REPOSITORIES | SYNC STATE---|----------------------------------------------------------------------------------|------------------------------------|--------------|-----------32 | Red Hat Enterprise Linux High Performance Networking for RHEL for IBM POWER -... | GLOBAL SUPPORT SERVI RED HAT, INC. | 0 | not_synced35 | Red Hat Enterprise Linux 7 High Availability High Touch Beta | GLOBAL SUPPORT SERVI RED HAT, INC. | 0 | not_synced

This command by default just enables the repositories. We do not automatically sync the content. We recommend to have the content imported before proceeding.

Passing the --synchronize command line option will automatically schedule in the background the import of the repos from the CDN

Passing the --wait command line option will automatically sync each repository, waiting for it to complete, before proceeding to the next repo

4.6.5. Enable Red Hat Repositories

Satellite 5 and 6 have different methods of grouping RPMs and presenting them. Within Satellite 5 all RPMs are placed into Channels which you clone and manage thecontent within. The Red Hat Channels are sync'd from RHN into Satellite 5 using satellite-sync. Within Satellite 6 everything is a yum repository (repo) and you filterwhat content from that repository is exposed to the systems being managed by Satellite 6. The Red Hat repos are sync'd off the Red Hat Content Delivery Network(CDN). Please see the Satellite 6 Beta documentation for more details. Due to these differences it can be confusing to know if you have imported all relevant Red Hatcontent into your Satellite 6 instance. We recommend to have imported the Red Hat content off CDN into Satellite 6 that equates to previously sync'd Satellite 5channels. This ensures that your Red Hat Enterprise Linux systems have access to the same content as they did within Satellite 5. We have provided an option withinhammer import on Satellite 6 to review your Satellite 5 channels and enable corresponding repos in Satellite 6. This section guides you through that process todiscover and then enable the appropriate Red Hat repos. As with the importing of 3rd party repositories in the previous step, we provide --wait and --synchronizeoptions for initiating the importing of Red Hat content automatically, which needs to be completed before moving to the next step.

# hammer import repository-enable --helpUsage: hammer import repository-enable [OPTIONS]

Options: --csv-file FILE_NAME CSV file --delete Delete entities from CSV file Default: false --dry-run Only show the repositories that would be enabled Default: false --recover RECOVER Recover strategy, can be: rename (default), map, none Default: :rename --repository-map FILE_NAME JSON file mapping channel-labels to repository information Default: "/usr/lib/ruby/gems/1.8/gems/hammer_cli_import-0.6.4/lib/hammer_cli_import/../../channel_data_pretty.json" --synchronize Synchronize imported repositories Default: false --wait Wait for repository synchronization to finish Default: false -h, --help print help#

# hammer import repository-enable --csv-file /tmp/exports/channels.csv --synchronizeOnly repositories available to IMPORTED organizations will be enabled!Organization ACME_Corporation...Organization GLOBAL_SUPPORT_SERVI_RED_HAT__INC_...Enabling /content/dist/rhel/server/5/5Server/x86_64/os/Packages for channel rhel-x86_64-server-5Sync started!Enabling /content/dist/rhel/server/5/5Server/x86_64/supplementary/os/Packages for channel rhel-x86_64-server-supplementary-5Sync started!Enabling /content/dist/rhel/server/6/6Server/x86_64/rhn-tools/os/Packages for channel rhn-tools-rhel-x86_64-server-6Sync started!Enabling /content/dist/rhel/server/6/6Server/x86_64/optional/os/Packages for channel rhel-x86_64-server-optional-6Sync started!Enabling /content/dist/rhel/server/6/6Server/x86_64/os/Packages for channel rhel-x86_64-server-6Sync started!Enabling /content/dist/rhel/server/5/5Server/x86_64/rhn-tools/os/Packages for channel rhn-tools-rhel-x86_64-server-5Sync started!#


11

Hammer Import Repository Enable Notes

Only repositories available to imported organizations will be enabled. We will not touch Organizations not known to the transition tooling.This command by default just enables the repositories. We do not automatically sync the content. We recommend to have the content imported beforeproceeding.Passing the --synchronize command line option will automatically schedule in the background the import of the repos from the CDNPassing the --wait command line option will automatically sync each repository, waiting for it to complete, before proceeding to the next repo

4.6.6. Import Custom & Cloned Custom Channels as Content Views

Within Satellite 5 you create cloned channels to restrict to a subset of Red Hat supplied channels and RPMs. For custom content you will put the content into customchannels, typically child channels to a cloned channel. Within Satellite 6 for both Red Hat and non-Red Hat content you keep the content in a repository and thenprovide a filtered view of that to the systems. This filtered view is called a content view. Within this step we are going to recreate your Satellite 5 custom and clonedcustom channels as content views. This should provide an near equivalent set of content to systems in the Satellite 6 Beta as was available within Satellite 5.6.

# hammer import content-view --helpUsage: hammer import content-view [OPTIONS]

Options: --csv-file FILE_NAME CSV file --delete Delete entities from CSV file Default: false --dir DIR Export directory --filter Filter content-views for package names present in Sat5 channel Default: false --recover RECOVER Recover strategy, can be: rename (default), map, none Default: :rename --synchronize Synchronize imported repositories Default: false --wait Wait for repository synchronization to finish Default: false -h, --help print help

# # hammer import content-view --csv-file /tmp/exports/CHANNELS/export.csv --dir /tmp/exports/CHANNELSCreating new product: Local-repositoriesCreating new local_repository: Local repository for clone-rhel-x86_64-server-5No such content_view: 101Repository Local_repository_for_clone-rhel-x86_64-server-5 is not (fully) synchronized. Retry once synchronization has completed.Product [1Local-repositories->118] already imported.Creating new local_repository: Local repository for clone-rhel-x86_64-server-6No such content_view: 102Product [1Local-repositories->118] already imported.Creating new local_repository: Local repository for custom-clone-master-puppet-rhel6-server-x86_64Repository Local_repository_for_custom-clone-master-puppet-rhel6-server-x86_64 is not (fully) synchronized. Retry once synchronization has completed.Product [1Local-repositories->118] already imported.Creating new local_repository: Local repository for epel-puppet-rhel6-server-x86_64Repository Local_repository_for_epel-puppet-rhel6-server-x86_64 is not (fully) synchronized. Retry once synchronization has completed.### hammer import content-view --csv-file /tmp/exports/CHANNELS/export.csv --synchronizeProduct [1Local-repositories->118] already imported.Local_repository [1117->12] already imported.Sync started!No such content_view: 101Repository Local_repository_for_clone-rhel-x86_64-server-5 is not (fully) synchronized. Retry once synchronization has completed.Product [1Local-repositories->118] already imported.Local_repository [1113->13] already imported.Sync started!No such content_view: 102Repository Local_repository_for_clone-rhel-x86_64-server-6 is not (fully) synchronized. Retry once synchronization has completed.Product [1Local-repositories->118] already imported.Local_repository [1115->14] already imported.Sync started!Repository Local_repository_for_custom-clone-master-puppet-rhel6-server-x86_64 is not (fully) synchronized. Retry once synchronization has completed.Product [1Local-repositories->118] already imported.Local_repository [1125->21] already imported.Sync started!### hammer import content-view --csv-file /tmp/exports/CHANNELS/export.csv --dir /tmp/exports/CHANNELS --synchronizeProduct [1Local-repositories->98] already imported.Local_repository [1117->12] already imported.No such content_view: 101Creating new content_view: Clone of Red Hat Enterprise Linux (v. 5 for 64-bit x86_64)Product [1Local-repositories->98] already imported.Local_repository [1113->13] already imported.No such content_view: 102Creating new content_view: Clone of Red Hat Enterprise Linux Server (v. 6 for 64-bit x86_64)Product [1Local-repositories->98] already imported.Local_repository [1115->14] already imported.No such content_view: 103Creating new content_view: Clone of RHEL Server Optional (v. 6 64-bit x86_64)


12

Hammer Import Content View Notes

You can view the status of importing content via the WebUI by logging in as an Administrator and selecting the correct Organization then Content -> SyncStatus.Additionally you can see the newly created Content Views within the Organization by going to Content -> Content Views.As seen above you may need to run the command with synchronize a couple of times once previous steps have completed, before seeing the content viewbeing generated.

4.6.7. Import System Groups to Host Collections

Satellite 5 allows you to group systems within one or more System Groups. With Satellite 6 the same concept is available but called Host Collections. We will recreatethe Satellite 5.6 System Groups within Satellite 6 as Host Collections by using the host-collection option for hammer import. The example below shows the basic usage.

# hammer import host-collection --helpUsage: hammer import host-collection [OPTIONS]

Options: --csv-file FILE_NAME CSV file --delete Delete entities from CSV file Default: false --recover RECOVER Recover strategy, can be: rename (default), map, none Default: :rename -h, --help print help

# hammer import host-collection --csv-file /tmp/exports/system-groups.csv Creating new host_collection: devCreating new host_collection: testCreating new host_collection: prodCreating new host_collection: eastCreating new host_collection: westCreating new host_collection: dbsCreating new host_collection: webCreating new host_collection: apps#

You can use the hammer command hammer host-collection list --organization-id 3 to see the resulting activation keys have been recreated [changingorganization id with the correct one for your system]. Alternatively you can see the activation keys within the WebUI as an Administrator within the Organization, underHosts -> Host Collections.

4.6.8. Import Activation Keys

Activation Keys in both Satellite 5 and 6 serve almost identical purposes, they are used by the command line tooling to register and subscribe a system to Satellite.They have different properties such as System Groups, Channel entitlements and System Entitlements (Provisioning, Monitoring) within Satellite 5, compared toContent Views and Host Collections within Satellite 6. Building on the previous steps to recreate Satellite 5.6 data-types we can now associate those pieces whenrecreating Activation Keys within Satellite 6 Beta. The tooling is very simple and just requires pointing to the activation-keys.csv file from the export directory.

# hammer import activation-key --helpUsage: hammer import activation-key [OPTIONS]

Options: --csv-file FILE_NAME CSV file --delete Delete entities from CSV file Default: false --recover RECOVER Recover strategy, can be: rename (default), map, none Default: :rename -h, --help print help

## hammer import activation-key --csv-file /tmp/exports/activation-keys.csv Activation key usage_limit: unlimitedCreating new activation_key: 1-rhel5-puppet Associating activation key [1] with host collections [2] Activation key usage_limit: unlimitedCreating new activation_key: 1-rhel6-puppet Associating activation key [2] with host collections [1]Creating new ak_content_view: ak_1 Publishing content view: 15 Associating activation key [1] with content view [15]Updating activation_key with id: 1Creating new ak_content_view: ak_2 Publishing content view: 16 Associating activation key [2] with content view [16]Updating activation_key with id: 2#

As an Administrator for the Organization of interest you can use the WebUI to see Activation Keys by going to Content -> Activation Keys. Alternatively you can use thehammer command * hammer activation-key list --organization-id 3* to list the activation keys and their basic properties [changing organization id with the correct one foryour system].

# hammer activation-key list --organization-id 3---|----------------|----------------|-----------------------|-------------ID | NAME | CONSUMED | LIFECYCLE ENVIRONMENT | CONTENT VIEW---|----------------|----------------|-----------------------|-------------2 | 1-rhel6-puppet | 0 of Unlimited | | ak_2 1 | 1-rhel5-puppet | 0 of Unlimited | | ak_1 ---|----------------|----------------|-----------------------|-------------#


13

4.7. Next stepsWe have now finished the process of recreating Satellite 5 data types into Satellite 6 entities. To gain the best experience and information for feedback please continueto use and test the Satellite 6 Beta creating from scratch the same type of data-types that the tooling recreated and better understand Satellite 6 concepts. Login to thenewly created organizations and review the data and use it. Provide feedback on the command line tooling, ease of use, user experience, inconsistencies, potentialimprovements, and finally any feedback on bugs with the tooling.


14

Revision HistoryRevision 0.1-0 Tue June 17 2014 Clifford Perry

Initial Version

Revision 0.2-0 Mon June 30 2014 Clifford Perry6.0 Beta Version

Index

Revision History

15

Red Hat Satellite 6 Red Hat Satellite 6 Beta Transition ... · In an active transition, the object is to decommission Satellite 5 after translating Satellite 5 data models to Satellite

Documents