System information

Deleting imported user [8->6].
Deleting imported user [9->7].
Report a bug
3.7.3. T ransit ioning Syst em Groups t o Host Collect ions
Red Hat Satellite 5 uses system groups to maintain collections of multiple systems. Satellite 6 uses
host collections to perform the same task. The Satellite transition tools provide options to transition
your Satellite 5 system groups to Satellite 6 host collections.
The following example demonstrates a typical use case. Run this command on your Satellite 6
system, and substitute the CSV file with your own:
# hammer import host-collection --csv-file /tmp/exports/system-
groups.csv
Creating new host_collection: dev
Creating new host_collection: test
Creating new host_collection: prod
Creating new host_collection: east
Creating new host_collection: west
Creating new host_collection: dbs
Creating new host_collection: web
Creating new host_collection: apps
You can use the hammer ho st-co l l ecti o n l i st --o rg ani zati o n-i d ORG-ID to verify that
the system groups have been recreated as host collections. Ensure you use the correct organization
ID.
You can also log in to the WebUI as an administrator to verify that the host collections were created.
Ensure you are in the correct organization, and then navigate to Hosts → Host Co llection s.
Report a bug
3.7.4 . Enabling Yum Reposit ories
Red Hat Satellite 5 and Satellite 6 use different methods to group RPM files and to present them. In
Satellite 5, all RPM files are placed into channels which you clone, and you then manage the content
from within those cloned channels. The satel l i te-sync command synchronizes Red Hat
channels from RHN into Satellite 5. In Satellite 6, everything is a yum repository and you filter the
content from that repository that is exposed to the systems being managed by Satellite 6.
Several options exist for recreating Satellite 5 repositories and importing the content:
Use the hammer i mpo rt repo si to ry --synchro ni ze command to initiate repository
synchronization in the background.
Use the hammer i mpo rt repo si to ry --synchro ni ze --wai t command to initiate
repository synchronization in the background, but wait for each synchronization to complete
before proceeding to the next repository.
Use the hammer i mpo rt repo si to ry command with neither option and then synchronize the
content manually using the WebUI or hammer commands.
⁠Chapt er 3. T ransit ioning fro m Sat ellit e 5 t o 6
29