Appendix D. Synchronizing Content Between Satellite Servers

Create the Export Directory

1. Create the export directory:

   # mkdir /var/www/html/pub/export

2. Ensure the foreman user has read and write permissions on the export directory:

   # chown foreman:foreman /var/www/html/pub/export

3. Configure the SELinux context:

   # semanage fcontext -a -t httpd_sys_rw_content_t \
   "/var/www/html/pub/export(/.*)?"
   # restorecon -RvF /var/www/html/pub/export
   # ls -Zd /var/www/html/pub/export \
   drwxr-xr-x. foreman foreman \
   system_u:object_r:httpd_sys_rw_content_t:s0 /var/www/html/pub/export

1. In the web UI, navigate to Administer > Settings, and click the Katello tab.
2. Locate the pulp_export_destination variable in the Name column, and click the Value field.
3. Enter the export destination, for example /var/www/html/pub/export, in the Value field and click Save.

To change the global default Download Policy using the web UI:

1. Go to Administer > Settings.
2. On the Katello tab, locate default_download_policy.
3. In the Value field, click the edit icon.
4. Set the value to immediate, and then click Save.

To change the Download Policy for an existing repository using the web UI:

1. In the web UI, navigate to Content > Products, and click the required product name.
2. On the Repositories tab, click the required repository, locate the Download Policy field, and click the edit icon.
3. From the drop-down list, select Immediate, and then click Save.

For Web UI Users

1. Ensure Products are synchronized to the required date.

2. Go to Content Content Views. Click Create New View. Enter following details to create a CV:

   1. Name — A plain text name for the CV. Enter Export_CV.
   2. Label — An internal ID for the CV. Red Hat Satellite 6 automatically completes this field based on what you have entered for Name.
   3. Description — An optional plain text description of the CV.
   4. Composite View — Defines whether or not to use a Composite Content View. Leave this option unselected.
3. Click Save to submit your changes.
4. On the Repository Selection screen, select the repositories to be added to the new CV from the Repository Selection table. Click Add Repositories to add selected packages to the CV.

5. Go to Yum Content Filters and click New Filter. Enter following details to create a filter for including non-errata packages:

   1. Name — A plain text name for the filter. Enter Non-errata Products.
   2. Content type — A drop-down menu listing types of content to be included into the filter. Choose Package.
   3. Inclusion type — A drop-down menu defining whether the content will be included or excluded from the CV. Choose Include.
   4. Description — An optional plain text description of the filter. Enter Include all non-errata Products.
   5. Click Save.
   6. On the Include RPM screen, select the Include all RPMs with no errata check box.

6. Go to Yum Content Filters and click New Filter. Enter following details to create a filter for including errata packages in accordance with the required date range:

   1. Name — A plain text name for the filter. Enter Erratas untill YYYY-MM-DD.
   2. Content type — A drop-down menu listing types of content to be included into the filter. Choose Erratum - Date and Type.
   3. Inclusion type — A drop-down menu defining whether the content will be included or excluded from the CV. Choose Include.
   4. Description — An optional plain text description of the filter. Enter Include errata products untill YYYY-MM-DD.
   5. Click Save.
   6. On the Erratum Date Range screen, select all Security, Enhancement and Bugfix errata types.
   7. Select the Updated On check box in Data type.
   8. Fill in the Start Date and End Date menus to configure the date range of Products for the filter.
   9. Click Save.
7. Click Publish New Version, fill in a short description of a version into the Description field. Ensure the Force Yum Metadata Regeneration check box is not selected.
8. Click Save to publish the CV version ready for exporting.

For CLI Users

1. Use the hammer content-view create command to create a new CV:

   # hammer content-view create \
   --name "Export_CV" \
   --organization "Default Organization"

2. Use the hammer content-view add-repository command to add repositories to the CV:

   # hammer content-view add-repository \
   --name "Export_CV" \
   --product "Red Hat Satellite" \
   --repository "Red Hat Satellite Tools 6.3 for RHEL 7 Server RPMs x86_64" \
   --organization "Default Organization"
   # hammer content-view add-repository \
   --name "Export_CV" \
   --product "Red Hat Satellite Capsule" \
   --repository "Red Hat Satellite Capsule Tools 6.2 for RHEL 7 Server RPMs x86_64" \
   --organization "Default Organization"

3. Create filters for the new CV:

   1. Use the hammer content-view filter create command to create a filter for including non-errata packages:

      # hammer content-view filter create \
      --content-view "Export_CV" \
      --inclusion true \
      --name "Non-errata_Products" \
      --type rpm \
      --original-packages true \
      --organization "Default Organization"

   2. Use the hammer content-view filter create command to create a filter for including errata packages:

      # hammer content-view filter create \
      --content-view "Export_CV" \
      --inclusion true \
      --name "Erratas until YYYY-MM-DD" \
      --type erratum \
      --organization "Default Organization"

   3. Use the hammer content-view filter rule create command to create a rule defining the date range:

      # hammer content-view filter rule create \
      --content-view "Export_CV" \
      --content-view-filter "Erratas until YYYY-MM-DD" \
      --end-date YYYY-MM-DD \
      --types security,enhancement,bugfix \
      --organization "Default Organization"

4. Use the hammer content-view publish command to publish the CV version ready for exporting. It is recommended to fill in the date ranges of repositories under the --description option.

   # hammer content-view publish \
   --name "Export_CV" \
   --description "Repositories until YYYY-MM-DD" \
   --force-yum-metadata-regeneration true \
   --async \
   --organization "Default Organization"

To Determine Which Content View Version to Export:

1. Use the hammer content-view version list command to determine which version of a Content View to export. For example:

   $ hammer content-view version list \
   --organization "Default Organization"
   ---|-------------------------------|---------|-----------------------
   ID | NAME                          | VERSION | LIFECYCLE ENVIRONMENTS
   ---|-------------------------------|---------|-----------------------
   3  | Export_CV 2.0                 | 2.0     | Library
   2  | Export_CV 1.0                 | 1.0     | Library
   1  | Default Organization View 1.0 | 1.0     | Library
   ---|-------------------------------|---------|-----------------------

To Export a Content View Version:

1. Use the hammer content-view version export command to export a version of a Content View:

   # hammer content-view version export --id 3

2. On a downstream server, use the hammer organization update command to add new repositories to an organization. Set the address to the directory corresponding to the version you want within the exported Content View as shown:

   $ hammer organization update \
   --name "Default Organization" \
   --redhat-repository-url \
   http://satellite.example.com/var/www/html/pub/export/Default_Organization-Export_CV-v2.0/Default_Organization/content_views/Export_CV/2.0
   
   Organization updated

To Import a Repository:

1. Make the data available for a repository over HTTP, not HTTPS. For example, copy the exported directory to the /var/www/html/pub/export/ directory on the downstream server, which is available over HTTP by default.
2. In the web UI, navigate to Content Red Hat Subscriptions.
3. Select Manage Manifests.

4. On the Import/Remove Manifest tab, set the Red Hat CDN URL address field to match the location of a content directory and a listing file within the exported repository.

   For example, if the exported repository is located in /var/www/html/pub/export/7f6a4f46-c77b-4781-bbd9-871764f8c8b8, set the URL to be http://satellite.example.com/pub/export/7f6a4f46-c77b-4781-bbd9-871764f8c8b8/Default_Organization/Library/.

5. Click Save.
6. Navigate to Content Red Hat Repositories and select the check box of the repository you have exported.

To Import a Content View:

1. Make the data available for a repository over HTTP, not HTTPS. For example, copy it to the /var/www/html/pub/export/ directory on the downstream server.
2. In the web UI, navigate to Content Red Hat Subscriptions.
3. Select Manage Manifests.

4. On the Import/Remove Manifest tab, set the Red Hat CDN URL address field to match the location of a content directory and a listing file within the exported Content View.

   For example, if the exported CV is located in /var/www/html/pub/export/Default_Organization-Export_CV-v1.0, set the URL to be http://satellite.example.com/pub/export/Default_Organization-Export_CV-v1.0/Default_Organization/content_views/Export_CV/1.0/

5. Click Save.
6. Navigate to Content Red Hat Repositories and check the repository you have exported.

7. On a downstream server, use the hammer organization update command to add new repositories to an organization. Set the address to the directory corresponding to the version you want within the exported Content View as shown:

   $ hammer organization update \
   --name "Default Organization" \
   --redhat-repository-url \
   http://satellite.example.com/pub/export/Default_Organization-Export_CV-v1.0/Default_Organization/content_views/Export_CV/1.0/
   
   Organization updated