Chapter 5. Importing Red Hat Content

1. In the Satellite web UI, navigate to Administer > Settings.
2. Click the Content tab.

3. Change the default download policy depending on your requirements:

   • To change the default download policy for a Red Hat repository, change the value of the Default Red Hat Repository download policy setting.
   • To change the default download policy for a custom repository, change the value of the Default Custom Repository download policy setting.

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

For CLI Users

1. List the repositories for an organization:

   # hammer repository list \
   --organization-label organization-label

2. Change the download policy for a repository to one of immediate, on_demand, background:

   # hammer repository update \
   --organization-label organization-label  \
   --product "Red Hat Enterprise Linux Server" \
   --name "Red Hat Enterprise Linux 7 Server Kickstart x86_64 7.5"  \
   --download-policy immediate

Procedure

1. In the Satellite web UI, navigate to Content > Red Hat Repositories.
2. To find repositories, either enter the repository name, or toggle the Recommended Repositories button to the on position to view a list of repositories that you require.
3. In the Available Repositories pane, click a repository to expand the repository set.
4. Click the Enable icon next to the base architecture and release version that you want.

For CLI Users

1. To search for your product, enter the following command:

   # hammer product list --organization "My_Organization"

2. List the repository set for the product:

   # hammer repository-set list \
   --product "Red Hat Enterprise Linux Server" \
   --organization "My_Organization"

3. Enable the repository using either the name or ID number. Include the release version, for example,7Server and base architecture, for example, x86_64. For example:

   # hammer repository-set enable \
   --name "Red Hat Enterprise Linux 7 Server (RPMs)" \
   --releasever "7Server" \
   --basearch "x86_64" \
   --product "Red Hat Enterprise Linux Server" \
   --organization "My_Organization"

For Web UI Users

1. In the Satellite web UI, navigate to Content > Products and select the product that contains the repositories that you want to synchronize.
2. Select the repositories that you want to synchronize and click Sync Now.

1. In the Satellite web UI, navigate to Content > Products.
2. Select the product containing the corrupted repository.
3. Select the name of a repository you want to synchronize.
4. From the Select Action menu, select Advanced Sync.
5. Select the option and click Sync.

For CLI users

1. Obtain a list of repository IDs:

   # hammer repository list --organization "My_Organization"

2. Synchronize a corrupted repository using the necessary option:

   • For the optimized synchronization:

     # hammer repository synchronize --incremental true --id 1

   • For the complete synchronization:

     # hammer repository synchronize --skip-metadata-check true --id 1

   • For the validate content synchronization:

     # hammer repository synchronize --validate-contents true --id 1

Procedure

1. In the Satellite web UI, navigate to Content > Products and select the check box next to each of the Products that you want to change.
2. From the Select Action list, select Manage HTTP Proxy.

3. Select an HTTP Proxy Policy from the list:

   • Global Default: Use the global default proxy setting.
   • No HTTP Proxy: Do not use an HTTP proxy, even if a global default proxy is configured.
   • Use specific HTTP Proxy: Select an HTTP Proxy from the list. You must add HTTP proxies to Satellite before you can select a proxy from this list. For more information, see Section 5.12, “Adding a New HTTP Proxy”.
4. Click Update.

Procedure

1. In the Satellite web UI, navigate to Content > Products and click the name of the Product that contains the repository.
2. In the Repositories tab, click the name of the repository.
3. Locate the HTTP Proxy field and click the edit icon.

4. Select an HTTP Proxy Policy from the list:

   • Global Default: Use the global default proxy setting.
   • No HTTP Proxy: Do not use an HTTP proxy, even if a global default proxy is configured.
   • Use specific HTTP Proxy: Select an HTTP Proxy from the list. You must add HTTP proxies to Satellite before you can select a proxy from this list. For more information, see Section 5.12, “Adding a New HTTP Proxy”.
5. Click Save.

Procedure

1. In the Satellite web UI, navigate to Infrastructure > HTTP Proxies and select New HTTP Proxy.
2. In the Name field, enter a name for the HTTP proxy.

3. In the URL field, enter the URL for the HTTP proxy, including the port number. The following host names are available:

   Host name	Port	Protocol
   subscription.rhsm.redhat.com	443	HTTPS
   subscription.rhn.redhat.com	443	HTTPS
   cdn.redhat.com	443	HTTPS

4. If your HTTP proxy requires authentication, enter a Username and Password.
5. Optional: In the Test URL field, enter the HTTP proxy URL, then click Test Connection to ensure that you can connect to the HTTP proxy from Satellite.
6. Click the Locations tab and add a location.
7. Click the Organization tab and add an organization.
8. Click Submit.

1. To control the number of synchronization jobs that run in parallel, configure the PULP_CONCURRENCY parameter in the /etc/default/pulp_workers file. For example, to set the number of jobs that run in parallel to 1, change PULP_CONCURRENCY to 1:

   PULP_CONCURRENCY=1

   By default, on a system with less than 8 CPUs, PULP_CONCURRENCY is set to the number of CPUs. On a system with more than 8 CPUs, it is set to 8.

2. To set the maximum network speed for synchronizing in bytes per second, configure the max_speed parameter. This parameter must be configured separately for each importer in the /etc/pulp/server/plugins.conf.d/ directory. For example, to set the maximum speed for synchronizing RPM content to 10 bytes per second, set the "max_speed" parameter in the /etc/pulp/server/plugins.conf.d/yum_importer.json file to 10:

   # cat /etc/pulp/server/plugins.conf.d/yum_importer.json
   {
       "proxy_host": null,
       "proxy_port": null,
       "proxy_username": null,
       "proxy_password": null,
       "max_speed": 10
   }

3. Verify the syntax of the file after editing:

   # json_verify < /etc/pulp/server/plugins.conf.d/yum_importer.json
   JSON is valid

4. Restart the satellite-maintain services to apply the changes:

   # satellite-maintain service restart

1. In the Satellite web UI, navigate to Content > Sync Plans and click New Sync Plan.
2. In the Name field, enter a name for the plan.
3. In the Description field, enter a description of the plan.
4. From the Interval list, select the interval at which you want the plan to run.
5. From the Start Date and Start Time lists, select when to start running the synchronization plan.
6. Click Save.
7. Click the Products tab, then click Add. Select the Red Hat Enterprise Linux Server product and click Add Selected.

For CLI Users

1. To create the synchronization plan, enter the following command:

   # hammer sync-plan create \
   --name "Red Hat Products 2" \
   --description "Example Plan for Red Hat Products" \
   --interval daily \
   --sync-date "2016-02-01 01:00:00" \
   --enabled true \
   --organization "My_Organization"

2. Assign the Red Hat Enterprise Linux Server product to it:

   # hammer product set-sync-plan \
   --name "Red Hat Enterprise Linux Server" \
   --sync-plan "Red Hat Products" \
   --organization "My_Organization"

3. View the available synchronization plans for an organization to verify that the synchronization plan is created:

   # hammer sync-plan list --organization "Default Organization"

1. Run the following Bash script:

   ORG="Your_Organization"
   SYNC_PLAN="daily_sync_at_3_a.m"
   
   for i in $(hammer --no-headers --csv product list --organization $ORG --per-page 999 | grep -vi not_synced | awk -F, {'{ if ($5!=0) print $1}'})
   do
     hammer sync-plan create --name $SYNC_PLAN --interval daily --sync-date "2018-06-20 03:00:00" --enabled true --organization $ORG
     hammer product set-sync-plan --sync-plan $SYNC_PLAN --organization $ORG --id $i
   done

2. After executing the script, view the products assigned the synchronization plan:

   # hammer product list --organization $ORG --sync-plan $SYNC_PLAN