1RHN-SATELLITE-EXPORTER(8) RHN-SATELLITE-EXPORTER(8)
2
6 rhn-satellite-exporter - A tool that exports satellite content into a
7 directory in an XML format. That content can then be imported using
8 satellite-sync's -m option.
9
11 rhn-satellite-exporter [ options ... ] [ -v ] [ --verbose ]
12 [ -dDIRECTORY ] [ --dir=DIRECTORY ]
16 [ -cCHANNEL_LABEL ] [ --channel=CHANNEL_LABEL ]
20 [ --hard-links ]
24 [ --start-date=START_DATE ]
28 [ --end-date=END_DATE ]
32 [ -p ] [ --print-configuration ]
36 [ --step ]
40 [ --no-rpms ]
44 [ --no-packages ]
48 [ --no-errata ]
52 [ --no-kickstarts ]
56 [ --debug-level ]
60 [ --email ]
64 [ --traceback-mail ]
68 [ --db=DBUSERNAME/DBPASSWORD@DBSID ]
72 [ --help ]
76
79 The RHN Satellite Exporter (rhn-satellite-exporter) tool exports satel‐
80 lite content in an XML format that is understood by satellite-sync's -m
81 option. The means of transporting the exported information to the
82 satellite is up to the user and beyond the scope of this document. The
83 content is exported into a directory that is specified by the user with
84 the -d option. rhn-satellite-exporter can export the following content:
85 Channel Families, Arches, Channel Metadata, Blacklists, RPMS, RPM Meta‐
86 data, Errata, Kickstarts.
87 The amount of time it takes rhn-satellite-exporter to export data is
89 dependent on the number and size of the channels being exported. Using
90 the --no-packages, --no-kickstarts, --no-errata, and --no-rpms options
91 will reduce the amount of time it takes for rhn-satellite-exporter to
92 run, but they will also prevent potentially useful information from
93 being exported. For that reason, they should only be used when you are
94 certain that you will not need the content that they exclude. Addition‐
95 ally, you will need to use the matching options for satellite-sync when
96 importing the data. For example, if you use --no-kickstarts with rhn-
97 satellite-exporter you will have to use satellite-sync's --no-kick‐
98 starts option when importing the data.
99 If you are exporting one of the base channels provided by RHN, you will
101 also need to export the tools channel associated with that base channel
102 in order to kickstart machines to the distribution in the base channel.
103 For instance, if you export rhel-i386-as-4 you should also export the
104 rhn-tools-rhel-4-as-i386 channel in order to kickstart machines to RHEL
105 4 AS. This is because the tools channels contain the auto-kickstart
106 packages that install packages for kickstarting a machine through the
107 Satellite.
108 When importing an exported channel into a satellite on which you have
110 not run satellite-sync, you will need to use satellite-sync's --rhn-
111 cert option to import the entitlements cert.
112 The --db option is mainly intended for debug purposes. If you decide to
114 use this option, be warned that rhn-satellite-exporter will not be able
115 to export the RPMs for the channel you are dumping if the RPMs are not
116 already imported into the satellite you are running rhn-satellite-
117 exporter on. As an example, if you are running rhn-satellite-exporter
118 on Satellite A with the --db option to connect to the database for
119 Satellite B, rhn-satellite-exporter will not find the RPMs because they
120 are not on Satellite A. They are on Satellite B. The exception to this
121 is if the channel(s) you are exporting exist on both Satellite A and
122 Satellite B.
123 The --email option is used to send a report to the administrator's
125 email address when the export is complete. If an error occurs when the
126 --email option is set, the error should be included in the report. The
127 only time that --email will not work is if an error occurs while the
128 program is starting up. Increasing the debug level by using --debug-
129 level will increase the amount of information included in the report.
130
132 -dDIR, --dir=DIR
133 Place the exported information into this directory.
134 --hard-links
136 Hard link exported packages and kickstarts to original files.
137 -cCHANNEL_LABEL,
139 Process data for this specific channel (specified by label)
140 only. NOTE: the channel's *label* is NOT the same as the chan‐
141 nel's *name*.
142 --start-date=START_DATE
144 The start date limit that the last modified dates are compared
145 against. Should be in the format 'YYYYMMDDHH24MISS'. If you did
146 not enter hour, minute and/or second, then zero is assumed. I.e.
147 date 20100101 is expanded to 20100101000000.
148 --end-date=END_DATE
150 The end date limit that the last modified dates are compared
151 against. Must be in the format 'YYYYMMDDHH24MISS'. If you did
152 not enter hour, minute and/or second, then zero is assumed. I.e.
153 date 20100101 is expanded to 20100101000000.
154 --make-isos=MAKE_ISOS
156 Create channel dump isos directory called satellite-isos.
157 Usage: --make-isos=cd or dvd.
158 --list-channels
160 List the channels that can be exported.
161 --list-steps
163 List all of the steps that rhn-satellite-exporter takes while
164 exporting data. These can be used as values for --step.
165 -p, --print-configuration
167 Print the configuration and exit.
168 --print-report
170 Print a report to the terminal when the export is complete.
171 --step Export information only up to this step.
173 --no-rpms
175 Do not export RPMs.
176 --no-packages
178 Do not export RPM metadata.
179 --no-errata
181 Do not export errata.
182 --no-kickstarts
184 Do not export kickstart data.
185 --debug-level
187 Set the debug level to this value. Overrides the value in
188 /etc/rhn/rhn.conf for this tool.
189 --email
191 Email a report of what was exported and what errors may have
192 occurred.
193 --traceback-mail
195 Alternative email address for --email.
196 --db=DBUSERNAME/DBPASSWORD@DBSID
198 Extract information from this database. The value must be an
199 Oracle connection string that is configured in your tnsnames.ora
200 file.
201 -h, --help
203 Show help message and exit.
204
206 satellite-sync(8)
207
209 John Wregglesworth <wregglej@redhat.com>
210Version 1.0 18 November 2010 RHN-SATELLITE-EXPORTER(8)