Red Hat Satellite 6 Administration
Create and publish content views, and promote them to lifecycle environments on an environment path.
You must always perform all the Satellite operational tasks by connecting to the Satellite Server, via either the web UI or the CLI, including for configuring Capsule or organization-specific content views, provisioning, and job creation. When you perform an operational task for some content host, such as provisioning or remote job execution, the Satellite Server knows which Capsule (internal or remote) handles the specified content hosts and initiates tasks through that Capsule and its proxy services.
To provide content to hosts from a Capsule Server, you must first create a content view on Satellite Server, add repositories to the content view, and publish it.
You can synchronize all Satellite content by using the synchronize command, and provide either the capsule ID or the name.
[root@satellite ~]# hammer capsule content synchronize \
--name capsule_name
[.......................................................................] [100%]You can limit the content that is pushed to a Capsule Server by promoting the content view to a lifecycle environment in an environment path and synchronizing the lifecycle environment with Capsule Server. To provide content to a host from Capsule Server, you must add a lifecycle environment to the Capsule Server, so that it can synchronize its content from the Satellite Server.
To add a lifecycle environment to Capsule Server with the web UI, navigate to → , and select the Capsule Server to add a lifecycle to. Click and then click the tab. Select the lifecycle environments to add to Capsule and then click .
After you add the lifecycle environments to Capsule Server, you can synchronize the content. To synchronize the content, click the tab. In the section, click the list. Choose one of the following options to synchronize the content:
focuses on speed by bypassing unneeded steps such as syncing unchanged metadata.
syncs repositories even if upstream metadata is unchanged.
removes the cached content from the Capsule Server if its download policy is configured as
On Demand.
You can use the following commands to synchronize a lifecycle environment to Capsule Server by using the Capsule Server name.
First, list the available Capsule Servers.
[root@satellite ~]#hammer capsule list---|---------------------------|--------------------------|--------------------- ID | NAME | URL | FEATURES ---|---------------------------|--------------------------|--------------------- 2 |capsule.lab.example.com| https://capsule.lab... | Container_Gateway... 1 | satellite.lab.example.com | https://satellite.lab... | Discovery,Dynflow... ---|---------------------------|--------------------------|---------------------
For the selected Capsule Server, list the available lifecycle environments.
[root@satellite ~]# hammer capsule content available-lifecycle-environments \
--name capsule.lab.example.com
---|-------------|---------------------
ID | NAME | ORGANIZATION
---|-------------|---------------------
2 | Library | Operations
5 | Capsule | Operations
1 | Library | Default Organization
6 | Development | Operations
---|-------------|---------------------Then, add the selected lifecycle environment to the Capsule Server.
[root@satellite ~]# hammer capsule content add-lifecycle-environment \
--lifecycle-environment Development --organization Operations \
--name capsule.lab.example.com
Lifecycle environment successfully added to the capsule.Finally, synchronize the lifecycle environment to the Capsule Server.
[root@satellite ~]# hammer capsule content synchronize \
--lifecycle-environment Development --organization Operations \
--name capsule.lab.example.com
[.......................................................................] [100%]Red Hat Satellite provides several download policies for synchronizing RPM content for repositories. For example, you might want to download only the content metadata and defer the actual content download for later.
The sets when the Capsule Server downloads packages from the Satellite Server.
The On Demand download policy downloads only the metadata during the Capsule repository synchronization, and packages are downloaded to the Capsule Server only when content hosts request package management.
The Immediate download policy causes Satellite to begin downloading all packages regardless of individual repository settings.
The Inherit from Repository download policy uses the policy that is set on individual repositories, and supports different policies on each repository.
To change the download policy for a Capsule Server, from the Satellite web UI, navigate to → , and select the Capsule Server to edit. Click , and on the tab, locate the field. Then, select the required download policy and click .
To change the download policy for a Capsule Server, from the CLI, use the following command:
[root@satellite ~]# hammer capsule update --download-policy DOWNLOAD_POLICY \
--name capsule.lab.example.comThe possible values for the DOWNLOAD_POLICYon_demand, immediate, and inherit.
References
For more information, see the Managing Content Views chapter in the Red Hat Satellite 6.11 Managing Content guide at https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html-single/managing_content/index#Managing_Content_Views_content-management
For more information, see the Adding Life Cycle Environments to Capsule Servers section in the Installing Capsule Server guide at https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html-single/installing_capsule_server/index#Adding_Life_Cycle_Environments_capsule
