diff --git a/guides/common/assembly_managing-alternate-content-sources.adoc b/guides/common/assembly_managing-alternate-content-sources.adoc index f24bdec6b0b..f204ca9d867 100644 --- a/guides/common/assembly_managing-alternate-content-sources.adoc +++ b/guides/common/assembly_managing-alternate-content-sources.adoc @@ -2,12 +2,20 @@ include::modules/con_managing-alternate-content-sources.adoc[] -include::modules/proc_configuring-custom-alternate-content-sources.adoc[leveloffset=+1] +include::modules/proc_creating-custom-alternate-content-sources-by-using-web-ui.adoc[leveloffset=+1] -include::modules/proc_configuring-simplified-alternate-content-sources.adoc[leveloffset=+1] +include::modules/proc_creating-custom-alternate-content-sources-by-using-cli.adoc[leveloffset=+1] + +include::modules/proc_creating-simplified-alternate-content-sources-by-using-web-ui.adoc[leveloffset=+1] + +include::modules/proc_creating-simplified-alternate-content-sources-by-using-cli.adoc[leveloffset=+1] ifdef::satellite[] -include::modules/proc_synchronizing-smart-proxy-directly-from-red-hat-cdn.adoc[leveloffset=+2] +include::modules/proc_synchronizing-smart-proxy-directly-from-red-hat-cdn-by-using-web-ui.adoc[leveloffset=+1] endif::[] -include::modules/proc_configuring-rhui-alternate-content-sources.adoc[leveloffset=+1] +include::modules/proc_creating-rhui-alternate-content-sources-by-using-web-ui.adoc[leveloffset=+1] + +include::modules/proc_creating-rhui-alternate-content-sources-by-using-cli.adoc[leveloffset=+1] + +include::modules/ref_permissions-required-to-manage-alternate-content-sources.adoc[leveloffset=+1] diff --git a/guides/common/modules/con_managing-alternate-content-sources.adoc b/guides/common/modules/con_managing-alternate-content-sources.adoc index 74658d3d12e..0ff789bf692 100644 --- a/guides/common/modules/con_managing-alternate-content-sources.adoc +++ b/guides/common/modules/con_managing-alternate-content-sources.adoc @@ -1,15 +1,17 @@ :_mod-docs-content-type: CONCEPT -[id="Managing_Alternate_Content_Sources_{context}"] +[id="managing-alternate-content-sources"] = Managing alternate content sources -Alternate content sources define alternate paths to download content during synchronization. +[role="_abstract"] +Alternate content sources (ACS) define alternate paths to download content during synchronization. The content itself is downloaded from the alternate content source, while the metadata is downloaded from the {ProjectServer} or the upstream URL, depending on the configuration. -You can use alternate content source to speed up synchronization if the content is located on the local filesystem or on a nearby network. -You can set up alternate content sources for {ProjectServer} and {SmartProxy}. +You can use alternate content sources to speed up synchronization if the content is located on the local filesystem or on a nearby network. +You can set up alternate content sources for {ProjectServer} and {SmartProxyServers}. + You must refresh the alternate content source after creation or after making any changes. A weekly cron job refreshes all alternate content sources. -You can also refresh the alternate content sources manually by using the {ProjectWebUI} or the Hammer CLI. +You can also refresh the alternate content sources manually by using the {ProjectWebUI} or Hammer CLI. Alternate content sources associated with your {ProjectServer}, or {SmartProxyServers} attached to multiple organizations, affect all organizations. There are three types of alternate content sources: @@ -19,31 +21,15 @@ Custom alternate content sources download the content from any upstream reposito Simplified:: Simplified alternate content sources copy the upstream repository information from your {ProjectServer} for the selected products. -Simplified alternate content sources are ideal for situations where the connection from your {SmartProxy} to the upstream repo is faster than from your {ProjectServer}. +Simplified alternate content sources are ideal for situations where the connection from your {SmartProxyServer} to the upstream repository is faster than to your {ProjectServer}. ifdef::satellite[] -Selecting the Red Hat products when creating a simplified alternate content source will download the content to the {SmartProxies} from the {Team} CDN. +Selecting the Red{nbsp}Hat products when creating a simplified alternate content source will download the content to the {SmartProxyservers} from the Red{nbsp}Hat CDN. endif::[] RHUI:: -RHUI alternate content sources download content from a Red Hat Update Infrastructure server. +RHUI alternate content sources download content from a Red{nbsp}Hat Update Infrastructure (RHUI) server. {ProjectWebUI} provides examples to help you find the network paths and to import authentication credentials. ifdef::satellite[] The RHUI alternate content source must be RHUI version 4 or greater and use the default installation configuration. For example, AWS RHUI is unsupported because it uses an installation scenario with unique authentication requirements. endif::[] - -.Permission requirements for alternate content sources - -Non-administrator users must have the below permissions to manage alternate content sources: - -. `view_smart_proxies` -. `view_content_credentials` -. `view_organizations` -. `view_products` - -In addition to the above permissions, assign permissions specific to alternate content sources, depending on the actions the users can perform: - -. `view_alternate_content_sources` -. `create_alternate_content_sources` -. `edit_alternate_content_sources` -. `destroy_alternate_content_sources` diff --git a/guides/common/modules/proc_configuring-custom-alternate-content-sources.adoc b/guides/common/modules/proc_configuring-custom-alternate-content-sources.adoc deleted file mode 100644 index d9bd48c7329..00000000000 --- a/guides/common/modules/proc_configuring-custom-alternate-content-sources.adoc +++ /dev/null @@ -1,63 +0,0 @@ -:_mod-docs-content-type: PROCEDURE - -[id="Configuring_Custom_Alternate_Content_Sources_{context}"] -= Configuring custom alternate content sources - -.Prerequisites -* If the repository requires SSL authentication, import the SSL certificate and key to the {Project}. -For more information, see {ContentManagementDocURL}importing-custom-ssl-certificates-by-using-web-ui[Importing Custom SSL Certificates] in _{ContentManagementDocTitle}_. -* Note that the alternate content source paths consist of a base URL appended with the subpaths that you provide. -For example, if your base URL is `\https://{server-example-com}` and your subpaths are `rhel7/` and `rhel8/`, then both `\https://{server-example-com}/rhel7/` and `\https://{server-example-com}/rhel8/` will be searched. - -.Procedure -. In the {ProjectWebUI}, navigate to *Content* > *Alternate Content Sources*. -. Click *Add Source* and set the *Source type* as *Custom*. -. Select the *Content type*. -. In the *Name* field, enter a name for the alternate content source. -. Optional: In the the *Description* field, provide a description for the ACS. -. Select {SmartProxies} to which the alternate content source is to be synced. -. Enter the Base URL of the alternate content source. -. Enter a comma-separated list of Subpaths. -. Provide the *Manual Authentication* or *Content Authentication* credentials, if these are needed. -. If SSL verification is required, enable *Verify SSL* and select the SSL CA certificate. -. Review details and click *Add*. -. Navigate to *Content* > *Alternate Content Sources* > click the vertical ellipsis next to the newly created alternate content source > Select *Refresh*. - -[id="cli-configuring-custom-alternate-content-sources_{context}"] -.CLI procedure -. Configure a custom alternate content source: -+ -[options="nowrap" subs="+quotes,attributes"] ----- -$ hammer alternate-content-source create \ ---alternate-content-source-type custom \ ---base-url "_https://local-repo.example.com:port_" \ ---name "_My_ACS_Name_" \ ---smart-proxy-ids __My_{smart-proxy-context-titlecase}_ID__ ----- -. Check if the newly created alternate content source is listed: -+ -[options="nowrap" subs="+quotes,attributes"] ----- -$ hammer alternate-content-source list ----- -. Refresh the alternate content source: -+ -[options="nowrap" subs="+quotes,attributes"] ----- -$ hammer alternate-content-source refresh --id _My_Alternate_Content_Source_ID_ ----- -. Add the {SmartProxies} to which the alternate content source is to be synced: -+ -[options="nowrap" subs="+quotes,attributes"] ----- -$ hammer alternate-content-source update \ ---id _My_Alternate_Content_Source_ID_ \ ---smart-proxy-ids __My_{smart-proxy-context-titlecase}_ID__ ----- -. Refresh the alternate content sources: -+ -[options="nowrap" subs="+quotes,attributes"] ----- -$ hammer alternate-content-source refresh --id _My_Alternate_Content_Source_ID_ ----- diff --git a/guides/common/modules/proc_configuring-rhui-alternate-content-sources.adoc b/guides/common/modules/proc_configuring-rhui-alternate-content-sources.adoc deleted file mode 100644 index d2e1d0136c3..00000000000 --- a/guides/common/modules/proc_configuring-rhui-alternate-content-sources.adoc +++ /dev/null @@ -1,77 +0,0 @@ -:_mod-docs-content-type: PROCEDURE - -[id="Configuring_RHUI_Alternate_Content_Sources_{context}"] -= Configuring RHUI alternate content sources - -.Prerequisites -* Generate the client entitlement certificates for the required repos on the RHUA node as described in {RHDocsBaseURL}red_hat_update_infrastructure/4/html/configuring_and_managing_red_hat_update_infrastructure/assembly_cmg-creating-client-ent-cert-config-rpm_configuring-and-managing-red-hat-update-infrastructure#proc_cmg-creating-client-entitlement-certificate_assembly_cmg-creating-client-ent-cert-config-rpm[Creating a client entitlement certificate with the Red Hat Update Infrastructure Management Tool] in _Configuring and Managing Red Hat Update Infrastructure_. -* Import the client entitlement certificates into {Project}. -For more information, see {ContentManagementDocURL}importing-custom-ssl-certificates-by-using-web-ui[Importing Custom SSL Certificates] in _{ContentManagementDocTitle}_. -* Obtain a list of the subpaths for the required repositories. -Execute the following command on your RHUA server: -+ -[options="nowrap" subs="+quotes,attributes"] ----- -# rhui-manager repo info --repo_id _My_Repo_ID_ ----- -* Note that the alternate content source paths consist of a base URL appended with the subpaths that you provide. -For example, if your base URL is `\https://{server-example-com}` and your subpaths are `rhel7/` and `rhel8/`, then both `\https://{server-example-com}/rhel7/` and `\https://{server-example-com}/rhel8/` will be searched. - -.Procedure -. In the {ProjectWebUI}, navigate to *Content* > *Alternate Content Sources*. -. Click *Add Source* and set the *Source type* as *RHUI*. -. Generate RHUI certificates using the command provided in the {ProjectWebUI}. -Ensure that you pass the repo labels of the desired repositories. -. In the *Name* field, enter a name for the alternate content source. -. Optional: In the *Description* field, provide a description for the ACS. -. Select {SmartProxies} to which the alternate content source is to be synced. -. Optional: Select *Use HTTP proxies* if you want the ACS to use the {SmartProxy}'s HTTP proxy. -. Enter the Base URL of the Red Hat Update Infrastructure CDS node. -. Enter a comma-separated list of Subpaths. -. Provide the *Content Credentials*, if these are needed. -. If SSL verification is required, enable *Verify SSL* and select the SSL CA certificate. -. Review details and click *Add*. -. Navigate to *Content* > *Alternate Content Sources*, click the vertical ellipsis next to the newly created alternate content source, and select *Refresh*. - -[id="cli-configuring-rhui-alternate-content-sources_{context}"] -.CLI procedure -. On {ProjectServer}, enter the following command: -+ -[options="nowrap" subs="+quotes,attributes"] ----- -$ hammer alternate-content-source create \ ---alternate-content-source-type rhui \ ---base-url "_https://rhui-cds-node/pulp/content_" \ ---name "_My_ACS_Name_" \ ---smart-proxy-ids __My_{smart-proxy-context-titlecase}_ID__ \ ---ssl-client-cert-id _My_SSL_Client_Certificate_ID_ \ ---ssl-client-key-id _My_SSL_Client_Key_ID_ \ ---subpaths _path/to/repo/1/,path/to/repo/2/_ \ ---verify-ssl 1 ----- -. Check if the newly created alternate content source is listed: -+ -[options="nowrap" subs="+quotes,attributes"] ----- -$ hammer alternate-content-source list ----- -. Refresh the alternate content source: -+ -[options="nowrap" subs="+quotes,attributes"] ----- -$ hammer alternate-content-source refresh --id _My_Alternate_Content_Source_ID_ ----- -. Add the {SmartProxies} to which the alternate content source is to be synced: -+ -[options="nowrap" subs="+quotes,attributes"] ----- -$ hammer alternate-content-source update \ ---id _My_Alternate_Content_Source_ID_ \ ---smart-proxy-ids __My_{smart-proxy-context-titlecase}_ID__ ----- -. Refresh the alternate content sources: -+ -[options="nowrap" subs="+quotes,attributes"] ----- -$ hammer alternate-content-source refresh --id _My_Alternate_Content_Source_ID_ ----- diff --git a/guides/common/modules/proc_configuring-simplified-alternate-content-sources.adoc b/guides/common/modules/proc_configuring-simplified-alternate-content-sources.adoc deleted file mode 100644 index 8a9d5354f92..00000000000 --- a/guides/common/modules/proc_configuring-simplified-alternate-content-sources.adoc +++ /dev/null @@ -1,41 +0,0 @@ -:_mod-docs-content-type: PROCEDURE - -[id="Configuring_Simplified_Alternate_Content_Sources_{context}"] -= Configuring simplified alternate content sources - -.Procedure -. In the {ProjectWebUI}, navigate to *Content* > *Alternate Content Sources*. -. Click *Add Source* and set the *Source type* as *Simplified*. -. Select the *Content type*. -. In the *Name* field, enter a name for the alternate content source. -. Optional: In the *Description* field, provide a description for the ACS. -. Select {SmartProxies} to which the alternate content source is to be synced. -. Optional: Select *Use HTTP proxies* if you want the ACS to use the {SmartProxyServer}'s HTTP proxy. -. Select the products that should use the alternate content source. -. Review details and click *Add*. -. Navigate to *Content* > *Alternate Content Sources*, click the vertical ellipsis next to the newly created alternate content source, and select *Refresh*. - -[id="cli-configuring-simplified-alternate-content-sources_{context}"] -.CLI procedure -. Create a simplified ACS: -+ -[options="nowrap" subs="+quotes,attributes"] ----- -$ hammer alternate-content-source create \ ---alternate-content-source-type simplified \ ---name _My_ACS_Name_ \ ---product-ids _My_Product_ID_ \ ---smart-proxy-ids __My_{smart-proxy-context-titlecase}_ID__ ----- -. Check if the newly created ACS is listed: -+ -[options="nowrap" subs="+quotes,attributes"] ----- -$ hammer alternate-content-source list ----- -. Refresh the ACS: -+ -[options="nowrap" subs="+quotes,attributes"] ----- -$ hammer alternate-content-source refresh --id _My_ACS_ID_ ----- diff --git a/guides/common/modules/proc_creating-custom-alternate-content-sources-by-using-cli.adoc b/guides/common/modules/proc_creating-custom-alternate-content-sources-by-using-cli.adoc new file mode 100644 index 00000000000..4372c38249a --- /dev/null +++ b/guides/common/modules/proc_creating-custom-alternate-content-sources-by-using-cli.adoc @@ -0,0 +1,40 @@ +:_mod-docs-content-type: PROCEDURE + +[id="creating-custom-alternate-content-sources-by-using-cli"] += Creating custom alternate content sources by using Hammer CLI + +[role="_abstract"] +You can create custom alternate content sources (ACS) to define alternate paths to download content during synchronization. + +.Prerequisites +* If the repository requires SSL authentication, import the SSL certificate and key into {Project}. +For more information, see {ContentManagementDocURL}importing-custom-ssl-certificates-by-using-cli[Importing custom SSL certificates by using Hammer CLI] in _{ContentManagementDocTitle}_. +* You have the base URL and subpaths of your alternate content source. +For example, if your base URL is `\https://{server-example-com}` and your subpaths are `rhel10/` and `rhel9/`, then {Project} will search `\https://{server-example-com}/rhel10/` and `\https://{server-example-com}/rhel9/`. + +.Procedure +. Create a custom alternate content source: ++ +[options="nowrap" subs="+quotes,attributes"] +---- +$ hammer alternate-content-source create \ +--alternate-content-source-type custom \ +--base-url "_https://local-repo.example.com:port_" \ +--name "_My_ACS_Name_" \ +--smart-proxy-ids __My_{smart-proxy-context-titlecase}_ID_1__,__My_{smart-proxy-context-titlecase}_ID_2__ \ +--verify-ssl _true_ +---- +. Refresh your alternate content source: ++ +[options="nowrap" subs="+quotes,attributes"] +---- +$ hammer alternate-content-source refresh --name "_My_ACS_Name_" +---- + +.Verification +* Verify that the task ran successfully: ++ +[options="nowrap" subs="+quotes,attributes"] +---- +$ hammer task list --search "Refresh Alternate Content Source" +---- diff --git a/guides/common/modules/proc_creating-custom-alternate-content-sources-by-using-web-ui.adoc b/guides/common/modules/proc_creating-custom-alternate-content-sources-by-using-web-ui.adoc new file mode 100644 index 00000000000..bc0d38df4ec --- /dev/null +++ b/guides/common/modules/proc_creating-custom-alternate-content-sources-by-using-web-ui.adoc @@ -0,0 +1,35 @@ +:_mod-docs-content-type: PROCEDURE + +[id="creating-custom-alternate-content-sources-by-using-web-ui"] += Creating custom alternate content sources by using {ProjectWebUI} + +[role="_abstract"] +You can create custom alternate content sources (ACS) to define alternate paths to download content during synchronization. + +.Prerequisites +* If the repository requires SSL authentication, import the SSL certificate and key into {Project}. +For more information, see {ContentManagementDocURL}Importing_Custom_SSL_Certificates_content-management[Importing {customssl} certificates] in _{ContentManagementDocTitle}_. +* You have the base URL and subpaths of your alternate content source. +For example, if your base URL is `\https://{server-example-com}` and your subpaths are `rhel10/` and `rhel9/`, then {Project} will search `\https://{server-example-com}/rhel10/` and `\https://{server-example-com}/rhel9/`. + +.Procedure +. In the {ProjectWebUI}, navigate to *Content* > *Alternate Content Sources*. +. Click *Add source*. +. Set the *Source type* to *Custom*. +. Select the *Content type* from the drop-down list. +. In the *Name* field, enter a name for your custom ACS. +. Optional: In the *Description* field, provide a description for the ACS. +. Select {SmartProxies} to which you want to synchronize content from your alternate content source. +. If you require synchronizing content through the HTTP proxy of your {SmartProxies}, select *Use HTTP proxies*. +. In the *Base URL* field, enter the base URL of the alternate content source. +. In the *Subpaths* field, provide a comma-separated list of subpaths. +. If your alternate content source requires authentication, select the *Manual authentication* or *Content credentials*. +. If SSL verification is required, enable *Verify SSL* and select the SSL CA certificate. +. Click *Add*. +. Navigate to *Content* > *Alternate Content Sources*. +. Click the vertical ellipsis next to the newly created alternate content source and click *Refresh*. + +.Verification +. In the {ProjectWebUI}, navigate to *Monitor* > *{Project} Tasks* > *Tasks*. +. Search for `Refresh Alternate Content Source`. +. Verify that the task finished successfully. diff --git a/guides/common/modules/proc_creating-rhui-alternate-content-sources-by-using-cli.adoc b/guides/common/modules/proc_creating-rhui-alternate-content-sources-by-using-cli.adoc new file mode 100644 index 00000000000..524c0f906e0 --- /dev/null +++ b/guides/common/modules/proc_creating-rhui-alternate-content-sources-by-using-cli.adoc @@ -0,0 +1,43 @@ +:_mod-docs-content-type: PROCEDURE + +[id="creating-rhui-alternate-content-sources-by-using-cli"] += Creating RHUI alternate content sources by using Hammer CLI + +[role="_abstract"] +You can use RHUI alternate content sources to configure your {SmartProxy} to sync content from a Red{nbsp}Hat Update Infrastructure server. + +.Prerequisites +* Generate the client entitlement certificates for the required repos on the RHUA node as described in {RHDocsBaseURL}red_hat_update_infrastructure/4/html/configuring_and_managing_red_hat_update_infrastructure/assembly_cmg-creating-client-ent-cert-config-rpm_configuring-and-managing-red-hat-update-infrastructure#proc_cmg-creating-client-entitlement-certificate_assembly_cmg-creating-client-ent-cert-config-rpm[Creating a client entitlement certificate with the Red Hat Update Infrastructure Management Tool] in _Configuring and Managing Red Hat Update Infrastructure_. +* Import the client entitlement certificates into {Project}. +For more information, see {ContentManagementDocURL}importing-custom-ssl-certificates-by-using-cli[Importing custom SSL certificates by using Hammer CLI] in _{ContentManagementDocTitle}_. +* Obtain a list of the subpaths for the required repositories. +Execute the following command on your RHUA server: ++ +[options="nowrap" subs="+quotes,attributes"] +---- +# rhui-manager repo info --repo_id _My_Repo_ID_ +---- +* Note that the alternate content source paths consist of a base URL appended with the subpaths that you provide. +For example, if your base URL is `\https://{server-example-com}` and your subpaths are `rhel7/` and `rhel8/`, then both `\https://{server-example-com}/rhel7/` and `\https://{server-example-com}/rhel8/` will be searched. + +.Procedure +. Create a RHUI alternate content source: ++ +[options="nowrap" subs="+quotes,attributes"] +---- +$ hammer alternate-content-source create \ +--alternate-content-source-type rhui \ +--base-url "_https://rhui-cds-node.example.com/pulp/content_" \ +--name "_My_ACS_Name_" \ +--smart-proxy-ids __My_{smart-proxy-context-titlecase}_ID_1__,__My_{smart-proxy-context-titlecase}_ID_2__ \ +--ssl-client-cert-id _My_SSL_Client_Certificate_ID_ \ +--ssl-client-key-id _My_SSL_Client_Key_ID_ \ +--subpaths _path/to/repo/1/,path/to/repo/2/_ \ +--verify-ssl _true_ +---- +. Refresh the alternate content source: ++ +[options="nowrap" subs="+quotes,attributes"] +---- +$ hammer alternate-content-source refresh --name "_My_ACS_Name_" +---- diff --git a/guides/common/modules/proc_creating-rhui-alternate-content-sources-by-using-web-ui.adoc b/guides/common/modules/proc_creating-rhui-alternate-content-sources-by-using-web-ui.adoc new file mode 100644 index 00000000000..bd7c71c9cd2 --- /dev/null +++ b/guides/common/modules/proc_creating-rhui-alternate-content-sources-by-using-web-ui.adoc @@ -0,0 +1,39 @@ +:_mod-docs-content-type: PROCEDURE + +[id="creating-rhui-alternate-content-sources-by-using-web-ui"] += Creating RHUI alternate content sources by using {ProjectWebUI} + +[role="_abstract"] +You can use RHUI alternate content sources to configure your {SmartProxy} to sync content from a Red{nbsp}Hat Update Infrastructure server. + +.Prerequisites +* Generate the client entitlement certificates for the required repos on the RHUA node as described in {RHDocsBaseURL}red_hat_update_infrastructure/4/html/configuring_and_managing_red_hat_update_infrastructure/assembly_cmg-creating-client-ent-cert-config-rpm_configuring-and-managing-red-hat-update-infrastructure#proc_cmg-creating-client-entitlement-certificate_assembly_cmg-creating-client-ent-cert-config-rpm[Creating a client entitlement certificate with the Red Hat Update Infrastructure Management Tool] in _Configuring and Managing Red Hat Update Infrastructure_. +* Import the client entitlement certificates into {Project}. +For more information, see {ContentManagementDocURL}Importing_Custom_SSL_Certificates_content-management[Importing {customssl} certificates] in _{ContentManagementDocTitle}_. +* Obtain a list of the subpaths for the required repositories. +Execute the following command on your RHUA server: ++ +[options="nowrap" subs="+quotes,attributes"] +---- +# rhui-manager repo info --repo_id _My_Repo_ID_ +---- +* You have the base URL and subpaths of your alternate content source. +For example, if your base URL is `\https://{server-example-com}` and your subpaths are `rhel10/` and `rhel9/`, then {Project} will search `\https://{server-example-com}/rhel10/` and `\https://{server-example-com}/rhel9/`. + +.Procedure +. In the {ProjectWebUI}, navigate to *Content* > *Alternate Content Sources*. +. Click *Add source*. +. Set the *Source type* to *RHUI*. +. Generate RHUI certificates using the command provided in the {ProjectWebUI}. +Ensure that you pass the repo labels of the desired repositories. +. In the *Name* field, enter a name for your RHUI ACS. +. Optional: In the *Description* field, provide a description for the ACS. +. Select {SmartProxies} to which you want to synchronize content from your alternate content source. +. If you require synchronizing content through the HTTP proxy of your {SmartProxies}, select *Use HTTP proxies*. +. In the *Base URL* field, enter the base URL of the Red{nbsp}Hat Update Infrastructure CDS node. +. In the *Subpaths* field, provide a comma-separated list of subpaths. +. If your alternate content source requires authentication, provide the *SSL client certificate* and *SSL client key*. +. If SSL verification is required, enable *Verify SSL* and select the SSL CA certificate. +. Click *Add*. +. Navigate to *Content* > *Alternate Content Sources*. +. Click the vertical ellipsis next to the newly created alternate content source and click *Refresh*. diff --git a/guides/common/modules/proc_creating-simplified-alternate-content-sources-by-using-cli.adoc b/guides/common/modules/proc_creating-simplified-alternate-content-sources-by-using-cli.adoc new file mode 100644 index 00000000000..cb26dbd26d9 --- /dev/null +++ b/guides/common/modules/proc_creating-simplified-alternate-content-sources-by-using-cli.adoc @@ -0,0 +1,33 @@ +:_mod-docs-content-type: PROCEDURE + +[id="creating-simplified-alternate-content-sources-by-using-cli"] += Creating simplified alternate content sources by using Hammer CLI + +[role="_abstract"] +You can create simplified alternate content sources (ACS) to reuse the upstream source to download content during synchronization on {SmartProxyServers}. + +.Procedure +. Create a simplified alternate content source: ++ +[options="nowrap" subs="+quotes,attributes"] +---- +$ hammer alternate-content-source create \ +--alternate-content-source-type simplified \ +--name "_My_ACS_Name_" \ +--product-ids _My_Product_ID_1_,_My_Product_ID_2_ \ +--smart-proxy-ids __My_{smart-proxy-context-titlecase}_ID_1__,__My_{smart-proxy-context-titlecase}_ID_2__ +---- +. Refresh your alternate content source: ++ +[options="nowrap" subs="+quotes,attributes"] +---- +$ hammer alternate-content-source refresh --name "_My_ACS_Name_" +---- + +.Verification +* Verify that the task ran successfully: ++ +[options="nowrap" subs="+quotes,attributes"] +---- +$ hammer task list --search "Refresh Alternate Content Source" +---- diff --git a/guides/common/modules/proc_creating-simplified-alternate-content-sources-by-using-web-ui.adoc b/guides/common/modules/proc_creating-simplified-alternate-content-sources-by-using-web-ui.adoc new file mode 100644 index 00000000000..2b40a81ecfc --- /dev/null +++ b/guides/common/modules/proc_creating-simplified-alternate-content-sources-by-using-web-ui.adoc @@ -0,0 +1,26 @@ +:_mod-docs-content-type: PROCEDURE + +[id="creating-simplified-alternate-content-sources-by-using-web-ui"] += Creating simplified alternate content sources by using {ProjectWebUI} + +[role="_abstract"] +You can create simplified alternate content sources (ACS) to reuse the upstream source to download content during synchronization on {SmartProxyServers}. + +.Procedure +. In the {ProjectWebUI}, navigate to *Content* > *Alternate Content Sources*. +. Click *Add source*. +. Set the *Source type* to *Simplified*. +. Select the *Content type* from the drop-down list. +. In the *Name* field, enter a name for your simplified ACS. +. Optional: In the *Description* field, provide a description for the ACS. +. Select {SmartProxies} to which you want to synchronize content from your alternate content source. +. If you require synchronizing content through the HTTP proxy of your {SmartProxies}, select *Use HTTP proxies*. +. Select the products that should use the alternate content source. +. Click *Add*. +. Navigate to *Content* > *Alternate Content Sources*. +. Click the vertical ellipsis next to the newly created alternate content source and click *Refresh*. + +.Verification +. In the {ProjectWebUI}, navigate to *Monitor* > *{Project} Tasks* > *Tasks*. +. Search for `Refresh Alternate Content Source`. +. Verify that the task finished successfully. diff --git a/guides/common/modules/proc_synchronizing-smart-proxy-directly-from-red-hat-cdn-by-using-web-ui.adoc b/guides/common/modules/proc_synchronizing-smart-proxy-directly-from-red-hat-cdn-by-using-web-ui.adoc new file mode 100644 index 00000000000..e25a93d87aa --- /dev/null +++ b/guides/common/modules/proc_synchronizing-smart-proxy-directly-from-red-hat-cdn-by-using-web-ui.adoc @@ -0,0 +1,20 @@ +:_mod-docs-content-type: PROCEDURE + +[id="synchronizing-{smart-proxy-context}-directly-from-red-hat-cdn-by-using-web-ui"] += Synchronizing {SmartProxy} directly from Red{nbsp}Hat CDN by using {ProjectWebUI} + +[role="_abstract"] +You can use simplified alternate content sources to configure your {SmartProxyServers} to sync content directly from Red{nbsp}Hat CDN instead of {ProjectServer}. + +.Procedure +. In the {ProjectWebUI}, navigate to *Content* > *Alternate Content Sources*. +. Click *Add source*. +. Set the *Source type* as *Simplified*. +. Set the *Content type* to *Yum*. +. In the *Name* field, enter a name for the alternate content source. +. Optional: In the *Description* field, provide a description for the alternate content source. +. Select {SmartProxies} that you want to sync directly from Red{nbsp}Hat CDN. +. If you require synchronizing content through the HTTP proxy of your {SmartProxies}, select *Use HTTP proxies*. +. Select the Red{nbsp}Hat products that should be synced to the {SmartProxy} from Red{nbsp}Hat CDN. +. Review details and click *Add*. +. Navigate to *Content* > *Alternate Content Sources*, click the vertical ellipsis next to the newly created alternate content source, and select *Refresh*. diff --git a/guides/common/modules/proc_synchronizing-smart-proxy-directly-from-red-hat-cdn.adoc b/guides/common/modules/proc_synchronizing-smart-proxy-directly-from-red-hat-cdn.adoc deleted file mode 100644 index 1e1e2143e42..00000000000 --- a/guides/common/modules/proc_synchronizing-smart-proxy-directly-from-red-hat-cdn.adoc +++ /dev/null @@ -1,20 +0,0 @@ -:_mod-docs-content-type: PROCEDURE - -[id="Synchronizing_{smart-proxy-context}_Directly_From_Red_Hat_CDN_{context}"] -= Synchronizing {SmartProxy} directly from Red Hat CDN - -You can use simplified alternate content sources to configure your {SmartProxy} to sync content directly from Red Hat CDN. - -.Procedure -. In the {ProjectWebUI}, navigate to *Content* > *Alternate Content Sources*. -. Click *Add Source* and set the *Source type* as *Simplified*. -. Set the *Content type* to *Yum*. -. In the *Name* field, enter a name for the alternate content source. -. Optional: In the *Description* field, provide a description for the alternate content source. -. Select {SmartProxies} that you want to sync directly from Red Hat CDN. -. Optional: Select *Use HTTP proxies* if you want the ACS to use the HTTP proxy on {SmartProxy}. -. Select the Red Hat products that should be synced to the {SmartProxy} from Red Hat CDN. -. Review details and click *Add*. -. Navigate to *Content* > *Alternate Content Sources*, click the vertical ellipsis next to the newly created alternate content source, and select *Refresh*. - -The {SmartProxy} will now download content from Red Hat CDN and not the {Project}. diff --git a/guides/common/modules/ref_permissions-required-to-manage-alternate-content-sources.adoc b/guides/common/modules/ref_permissions-required-to-manage-alternate-content-sources.adoc new file mode 100644 index 00000000000..2b0cff66461 --- /dev/null +++ b/guides/common/modules/ref_permissions-required-to-manage-alternate-content-sources.adoc @@ -0,0 +1,19 @@ +:_mod-docs-content-type: REFERENCE + +[id="permissions-required-to-manage-alternate-content-sources"] += Permissions required to manage alternate content sources + +[role="_abstract"] +You need permissions to manage alternate content sources (ACS) on {ProjectName}. + +Permissions to view ACS:: +* `view_content_credentials` +* `view_organizations` +* `view_products` +* `view_smart_proxies` + +Permissions to manage ACS:: +* `create_alternate_content_sources` +* `destroy_alternate_content_sources` +* `edit_alternate_content_sources` +* `view_alternate_content_sources`