System information

5. Import repositories.
6. Import custom channels and cloned channels as content views.
7. Import activation keys.
8. Import kickstart snippets as template snippets.
9. Import configuration files to puppet modules.
10. Import system profiles as content hosts.
Important
The order in which you import entities is important. Entities are owned by organizations in
Satellite 5; consequently, you need to import organizations before users, for example. You can
use the hammer i mpo rt al l --d ry-run command to list the available entities and the
order in which they should be imported.
O p t io n s f o r Imp o rting En t it ies
Satellite 6 gives you the option of importing entities separately or all together. This section describes
these two approaches.
Assuming a set of Satellite 5 export files is available, a manual import session would appear as
follows:
# hammer shell
hammer> import organization --csv-file=FILE
hammer> import user --csv-file=FILE
If the Satellite 5 data is stored in /tmp/expo rts (the result, for example, of unpacking the output of
spacewal k-expo rt), you can use the following command to import everything:
# hammer import all --directory=/tmp/exports
Report a bug
3.7.1. Import ing Organiz at ions
To transition organizations, use the users. csv file and recreate the Satellite 5.6 organizations
listed within it. You can use the hammer i mpo rt command on the command line or use the hammer
interactive shell.
Run the following command to import organizations into Satellite 6:
# hammer import organization --csv-file /tmp/exports/users.csv
The following is an example of an interactive session. This example also demonstrates the --
upl o ad -mani fests-fro m and --verbo se options:
Examp le 3.2. Examp le o f Int eractive Impo rt Session
Chapt er 3. T ransit ioning fro m Sat ellit e 5 t o 6
25