diff --git a/l10n-weblate/installation-and-upgrade.cfg b/l10n-weblate/installation-and-upgrade.cfg index 9755ce7cd94..8218eacd083 100644 --- a/l10n-weblate/installation-and-upgrade.cfg +++ b/l10n-weblate/installation-and-upgrade.cfg @@ -14,6 +14,7 @@ [type: asciidoc] modules/installation-and-upgrade/pages/container-deployment/mlm/migrations/server/server-mlm-43-51.adoc $lang:translations/$lang/modules/installation-and-upgrade/pages/container-deployment/mlm/migrations/server/server-mlm-43-51.adoc [type: asciidoc] modules/installation-and-upgrade/pages/container-deployment/mlm/migrations/server/server-mlm-50-51.adoc $lang:translations/$lang/modules/installation-and-upgrade/pages/container-deployment/mlm/migrations/server/server-mlm-50-51.adoc [type: asciidoc] modules/installation-and-upgrade/pages/container-deployment/mlm/proxy-air-gapped-deployment-mlm.adoc $lang:translations/$lang/modules/installation-and-upgrade/pages/container-deployment/mlm/proxy-air-gapped-deployment-mlm.adoc +[type: asciidoc] modules/installation-and-upgrade/pages/container-deployment/mlm/proxy-conversion-from-client-mlm.adoc $lang:translations/$lang/modules/installation-and-upgrade/pages/container-deployment/mlm/proxy-conversion-from-client-mlm.adoc [type: asciidoc] modules/installation-and-upgrade/pages/container-deployment/mlm/proxy-deployment-mlm.adoc $lang:translations/$lang/modules/installation-and-upgrade/pages/container-deployment/mlm/proxy-deployment-mlm.adoc [type: asciidoc] modules/installation-and-upgrade/pages/container-deployment/mlm/proxy-deployment-vm-mlm.adoc $lang:translations/$lang/modules/installation-and-upgrade/pages/container-deployment/mlm/proxy-deployment-vm-mlm.adoc [type: asciidoc] modules/installation-and-upgrade/pages/container-deployment/mlm/proxy-deployment-vmdk-mlm.adoc $lang:translations/$lang/modules/installation-and-upgrade/pages/container-deployment/mlm/proxy-deployment-vmdk-mlm.adoc @@ -23,7 +24,6 @@ [type: asciidoc] modules/installation-and-upgrade/pages/container-deployment/mlm/server-deployment-vm-mlm.adoc $lang:translations/$lang/modules/installation-and-upgrade/pages/container-deployment/mlm/server-deployment-vm-mlm.adoc [type: asciidoc] modules/installation-and-upgrade/pages/container-deployment/mlm/server-deployment-vmdk-mlm.adoc $lang:translations/$lang/modules/installation-and-upgrade/pages/container-deployment/mlm/server-deployment-vmdk-mlm.adoc [type: asciidoc] modules/installation-and-upgrade/pages/container-deployment/mlm/snippet-warn-images-sl-micro.adoc $lang:translations/$lang/modules/installation-and-upgrade/pages/container-deployment/mlm/snippet-warn-images-sl-micro.adoc -[type: asciidoc] modules/installation-and-upgrade/pages/container-deployment/proxy-conversion-from-client.adoc $lang:translations/$lang/modules/installation-and-upgrade/pages/container-deployment/proxy-conversion-from-client.adoc [type: asciidoc] modules/installation-and-upgrade/pages/container-deployment/snippet-actkey-bootstrap-proxy-mlm.adoc $lang:translations/$lang/modules/installation-and-upgrade/pages/container-deployment/snippet-actkey-bootstrap-proxy-mlm.adoc [type: asciidoc] modules/installation-and-upgrade/pages/container-deployment/snippet-generate_proxy_config.adoc $lang:translations/$lang/modules/installation-and-upgrade/pages/container-deployment/snippet-generate_proxy_config.adoc [type: asciidoc] modules/installation-and-upgrade/pages/container-deployment/snippet-hardened-tmpdir.adoc $lang:translations/$lang/modules/installation-and-upgrade/pages/container-deployment/snippet-hardened-tmpdir.adoc @@ -36,6 +36,7 @@ [type: asciidoc] modules/installation-and-upgrade/pages/container-deployment/snippet-transfer_proxy_config.adoc $lang:translations/$lang/modules/installation-and-upgrade/pages/container-deployment/snippet-transfer_proxy_config.adoc [type: asciidoc] modules/installation-and-upgrade/pages/container-deployment/uyuni/migrate-uyuni-to-a-container.adoc $lang:translations/$lang/modules/installation-and-upgrade/pages/container-deployment/uyuni/migrate-uyuni-to-a-container.adoc [type: asciidoc] modules/installation-and-upgrade/pages/container-deployment/uyuni/proxy-container-setup-uyuni.adoc $lang:translations/$lang/modules/installation-and-upgrade/pages/container-deployment/uyuni/proxy-container-setup-uyuni.adoc +[type: asciidoc] modules/installation-and-upgrade/pages/container-deployment/uyuni/proxy-conversion-from-client-uyuni.adoc $lang:translations/$lang/modules/installation-and-upgrade/pages/container-deployment/uyuni/proxy-conversion-from-client-uyuni.adoc [type: asciidoc] modules/installation-and-upgrade/pages/container-deployment/uyuni/proxy-deployment-uyuni.adoc $lang:translations/$lang/modules/installation-and-upgrade/pages/container-deployment/uyuni/proxy-deployment-uyuni.adoc [type: asciidoc] modules/installation-and-upgrade/pages/container-deployment/uyuni/proxy-k3s-deployment-uyuni.adoc $lang:translations/$lang/modules/installation-and-upgrade/pages/container-deployment/uyuni/proxy-k3s-deployment-uyuni.adoc [type: asciidoc] modules/installation-and-upgrade/pages/container-deployment/uyuni/proxy-migration-uyuni.adoc $lang:translations/$lang/modules/installation-and-upgrade/pages/container-deployment/uyuni/proxy-migration-uyuni.adoc diff --git a/modules/installation-and-upgrade/nav-installation-and-upgrade-guide.adoc b/modules/installation-and-upgrade/nav-installation-and-upgrade-guide.adoc index 69400d2774c..df3bb7e0611 100644 --- a/modules/installation-and-upgrade/nav-installation-and-upgrade-guide.adoc +++ b/modules/installation-and-upgrade/nav-installation-and-upgrade-guide.adoc @@ -39,7 +39,7 @@ ifeval::[{uyuni-content} == true] *** xref:install-proxy.adoc[Proxy] **** xref:container-deployment/uyuni/proxy-container-setup-uyuni.adoc[Containerized {productname} Proxy Setup] **** xref:container-deployment/uyuni/proxy-deployment-uyuni.adoc[Proxy Deployment on {leapmicro}] -**** xref:container-deployment/proxy-conversion-from-client.adoc[{productname} Proxy Conversion From Client] +**** xref:container-deployment/uyuni/proxy-conversion-from-client-uyuni.adoc[{productname} Proxy Conversion From Client] **** xref:container-deployment/uyuni/proxy-k3s-deployment-uyuni.adoc[Proxy Deployment on K3s] endif::[] @@ -54,7 +54,7 @@ ifeval::[{mlm-content} == true] **** xref:connect-payg.adoc[Connect {payg} Instance] *** xref:install-proxy.adoc[Proxy] **** xref:container-deployment/mlm/proxy-deployment-mlm.adoc[{productname} Proxy Deployment] -**** xref:container-deployment/proxy-conversion-from-client.adoc[{productname} Proxy Conversion From Client] +**** xref:container-deployment/mlm/proxy-conversion-from-client-mlm.adoc[{productname} Proxy Conversion From Client] **** xref:container-deployment/mlm/proxy-deployment-vm-mlm.adoc[Proxy Deployment as Virtual Machine - KVM] **** xref:container-deployment/mlm/proxy-deployment-vmdk-mlm.adoc[Proxy Deployment Virtual Machine - VMware] **** xref:container-deployment/mlm/proxy-k3s-deployment-mlm.adoc[Proxy Deployment on K3s] diff --git a/modules/installation-and-upgrade/pages/container-deployment/mlm/proxy-conversion-from-client-mlm.adoc b/modules/installation-and-upgrade/pages/container-deployment/mlm/proxy-conversion-from-client-mlm.adoc new file mode 100644 index 00000000000..9e5554db90a --- /dev/null +++ b/modules/installation-and-upgrade/pages/container-deployment/mlm/proxy-conversion-from-client-mlm.adoc @@ -0,0 +1,117 @@ +[[proxy-conversion-from-client-mlm]] += Proxy conversion from client + +== Introduction + +This chapter describes how {productname} proxy can be registered with {productname} server from the {webui}. + +The client which is a candidate for conversion to proxy must adhere to the following pre-requisites: + +* it must already be onboarded +* it is reachable +* it has access to client tools +* it has access to proxy channels + +ifeval::[{mlm-content} == true] +* it is one of the following systems: +** {sles} 15 SP7 +** {sl-micro} 6.1 +endif::[] + + +== Convert the client to {productname} Proxy + +The process of conversion is done entirely from the {webui} for already registered clients. +For more information about client onboarding, see xref:client-configuration:registration-overview.adoc[]. + +The following two procedures describe the client conversion to a proxy. +Either procedure can be used, and will achieve the same outcome. + +.Procedure: Converting client to {productname} Proxy using dedicated button +. For the client chosen to be converted to proxy, go to its [literal]``Overview`` page. +. Click button btn:[Convert to Proxy]. +. Wait for the conversion to complete. +. Confirm that the conversion has been successful by locating a new tab [literal]``Proxy`` on the [literal]``Overview`` page. +. Confirm there are two tabs within [literal]``Proxy``: [literal]``Clients`` and [literal]``Configuration``. + +Proceed with the steps to <>. + +.Procedure: Converting client to {productname} Proxy by changing client's properties +. For the client chosen to be converted to proxy, go to its [literal]``Properties`` page. +. Locate the section [literal]``Add-on System Types``. +. Check the option [literal]``Proxy``. +. Click button btn:[Update Properties]. +. Follow the displayed note and apply highstate to complete the conversion. +. Confirm that the conversion has been successful by locating a new tab [literal]``Proxy`` on the [literal]``Overview`` page. +. Confirm there are two tabs within [literal]``Proxy``, [literal]``Clients`` and [literal]``Configuration``. + +Proceed with the steps to <>. + + +[[configure-proxy]] +== Configure the Proxy + +Once the client had been succesfully converted to proxy, it needs to be configured. + +.Procedure: Configuring the Proxy +. In the {webui}, navigate to menu:Proxy[Configuration] and fill in the required data: +. In the [guimenu]``Parent FQDN`` field type fully qualified domain name for the parent server or proxy. +. In the [guimenu]``Proxy SSH port`` field type SSH port on which SSH service is listening on {productname} Proxy. It is recommended to keep default 8022. +. In the [guimenu]``Max Squid cache size [MB]`` field type maximal allowed size for Squid cache. +. In the [guimenu]``Proxy admin email`` field type the administrator's email. +. In the section [literal]``Certificates`` select one of two options: [literal]``Keep`` or [literal]``Replace``. +* Select [literal]``Keep`` if an existing certificates should be used. + This option is not available when you configure the proxy for the first time. +* Select [literal]``Replace`` if the new server certificates should be provided for {productname} proxy. ++ +The certificate can be replaced by one of the two options: ++ +** an existing certificate, provided by the third-party authority +** a brand new certificate generated from the existing {productname} CA certificate for the proxy, by using command [command]``rhn-ssl-tool`` ++ +For more information about certificate creation, see xref:administration:ssl-certs.adoc[]. +. In the section [literal]``Source`` select one of two options: [literal]``RPM`` or [literal]``Registry``. ++ +. Option [literal]``RPM`` is recommended for air-gapped or restricted environments. ++ + +[WARNING] +==== +If [literal]``RPM`` option is selected, a number of packages must be installed before proceeding further. +==== + ++ +Go to [literal]``Software`` tab, search and install the following packages (the example illustrates the use of [literal]``x86_64`` architecture): + +* suse-multi-linux-manager-5.1-x86_64-proxy-httpd-image +* suse-multi-linux-manager-5.1-x86_64-proxy-salt-broker-image +* suse-multi-linux-manager-5.1-x86_64-proxy-squid-image +* suse-multi-linux-manager-5.1-x86_64-proxy-ssh-image +* suse-multi-linux-manager-5.1-x86_64-proxy-tftpd-image + ++ + +Return to Proxy configuration tab, and continue with the remaining configuration. + +. Option [literal]``Registry`` can be used if connectivity is available. ++ +For more information about deployment in air-gapped environment, see xref:installation-and-upgrade:container-deployment/mlm/proxy-air-gapped-deployment-mlm.adoc[]. + +. In case [literal]``Registry`` is selected, proceed with selecting one of two options: [literal]``Simple`` or [literal]``Advanced``. +. If the option selected is [literal]``Simple``, provide the values in [literal]``Registry URL`` and [literal]``Containers Tag``. ++ +* For [literal]``Registry URL`` use [literal]``registry.suse.com/suse/multi-linux-manager/5.1/x86_64``. +* Select the tag from the drop-down list. + +. If the option selected is [literal]``Advanced`` additional section of the form opens. ++ +* For every indivudual URL field, use the registry [literal]``registry.suse.com/suse/multi-linux-manager/5.1/x86_64`` and the corresponding suffix, or example _proxy-httpd_ or _salt-broker_. +* Select the tag from the drop-down list. +. Once all fields are filled in, click btn:[Apply] to apply the changes. + + +[WARNING] +==== +When configuring a proxy chain, the parent proxy needs access to any registry that a child proxy is set to use as its source. +==== + diff --git a/modules/installation-and-upgrade/pages/container-deployment/proxy-conversion-from-client.adoc b/modules/installation-and-upgrade/pages/container-deployment/proxy-conversion-from-client.adoc deleted file mode 100644 index 4b0ebc644bd..00000000000 --- a/modules/installation-and-upgrade/pages/container-deployment/proxy-conversion-from-client.adoc +++ /dev/null @@ -1,43 +0,0 @@ -[[proxy-conversion-from-client-mlm]] -= Proxy conversion from client - -== Introduction - -This chapter describes how {productname} proxy can be registered with {productname} server. -The main principle consists of using a functionality within {webui} which converts an already onboarded client to a proxy. - -The client which is a candidate for conversion to proxy must adhere to the following pre-requisites: - -* it must already be onboarded -* it is reachable -* it has access to client tools - -ifeval::[{mlm-content} == true] -* it is one of the following systems: -** {sles} 15 SP7 -** {sl-micro} 6.1 -endif::[] - - -== Convert the client to {productname} Proxy - -The process of conversion is done entirely from the {webui} for already registered clients. -For more information about client onboarding, see xref:client-configuration:registration-overview.adoc[]. - -The following two procedures describe the client conversion to a proxy. -Either procedure can be used, and will achieve the same outcome. - -.Procedure: Converting client to {productname} Proxy using dedicated button -. For the client chosen to be converted to proxy, go to its [literal]``Overview`` page. -. Click button btn:[Convert to Proxy]. -. Wait for the conversion to complete. -. Confirm that the conversion has been successful by locating a new tab [literal]``Proxy`` on the [literal]``Overview`` page. - - -.Procedure: Converting client to {productname} Proxy by changing client's properties -. For the client chosen to be converted to proxy, go to its [literal]``Properties`` page. -. Locate the section [literal]``Add-on System Types``. -. Check the option [literal]``Proxy``. -. Click button btn:[Update Properties]. -. Follow the displayed note and apply highstate to complete the conversion. -. Confirm that the conversion has been successful by locating a new tab [literal]``Proxy`` on the [literal]``Overview`` page. diff --git a/modules/installation-and-upgrade/pages/container-deployment/uyuni/proxy-conversion-from-client-uyuni.adoc b/modules/installation-and-upgrade/pages/container-deployment/uyuni/proxy-conversion-from-client-uyuni.adoc new file mode 100644 index 00000000000..4ecfeb2e7bb --- /dev/null +++ b/modules/installation-and-upgrade/pages/container-deployment/uyuni/proxy-conversion-from-client-uyuni.adoc @@ -0,0 +1,110 @@ +[[proxy-conversion-from-client-uyuni]] += Proxy conversion from client + +== Introduction + +This chapter describes how {productname} proxy can be registered with {productname} server from the {webui}. + +The client which is a candidate for conversion to proxy must adhere to the following pre-requisites: + +* it must already be onboarded +* it is reachable +* it has access to client tools +* it has access to proxy channels + +== Convert the client to {productname} Proxy + +The process of conversion is done entirely from the {webui} for already registered clients. +For more information about client onboarding, see xref:client-configuration:registration-overview.adoc[]. + +The following two procedures describe the client conversion to a proxy. +Either procedure can be used, and will achieve the same outcome. + +.Procedure: Converting client to {productname} Proxy using dedicated button +. For the client chosen to be converted to proxy, go to its [literal]``Overview`` page. +. Click button btn:[Convert to Proxy]. +. Wait for the conversion to complete. +. Confirm that the conversion has been successful by locating a new tab [literal]``Proxy`` on the [literal]``Overview`` page. +. Confirm there are two tabs within [literal]``Proxy``: [literal]``Clients`` and [literal]``Configuration``. + +Proceed with the steps to <>. + +.Procedure: Converting client to {productname} Proxy by changing client's properties +. For the client chosen to be converted to proxy, go to its [literal]``Properties`` page. +. Locate the section [literal]``Add-on System Types``. +. Check the option [literal]``Proxy``. +. Click button btn:[Update Properties]. +. Follow the displayed note and apply highstate to complete the conversion. +. Confirm that the conversion has been successful by locating a new tab [literal]``Proxy`` on the [literal]``Overview`` page. +. Confirm there are two tabs within [literal]``Proxy``, [literal]``Clients`` and [literal]``Configuration``. + +Proceed with the steps to <>. + + +[[configure-proxy]] +== Configure the Proxy + +Once the client had been succesfully converted to proxy, it needs to be configured. + +.Procedure: Configuring the Proxy +. In the {webui}, navigate to menu:Proxy[Configuration] and fill in the required data: +. In the [guimenu]``Parent FQDN`` field type fully qualified domain name for the parent server or proxy. +. In the [guimenu]``Proxy SSH port`` field type SSH port on which SSH service is listening on {productname} Proxy. It is recommended to keep default 8022. +. In the [guimenu]``Max Squid cache size [MB]`` field type maximal allowed size for Squid cache. +. In the [guimenu]``Proxy admin email`` field type the administrator's email. +. In the section [literal]``Certificates`` select one of two options: [literal]``Keep`` or [literal]``Replace``. +* Select [literal]``Keep`` if an existing certificates should be used. + This option is not available when you configure the proxy for the first time. +* Select [literal]``Replace`` if the new server certificates should be provided for {productname} proxy. ++ +The certificate can be replaced by one of the two options: ++ +** an existing certificate, provided by the third-party authority +** a brand new certificate generated from the existing {productname} CA certificate for the proxy, by using command [command]``rhn-ssl-tool`` ++ +For more information about certificate creation, see xref:administration:ssl-certs.adoc[]. +. In the section [literal]``Source`` select one of two options: [literal]``RPM`` or [literal]``Registry``. ++ +. Option [literal]``RPM`` is recommended for air-gapped or restricted environments. ++ + +[WARNING] +==== +If [literal]``RPM`` option is selected, a number of packages must be installed before proceeding further. +==== + ++ +Go to [literal]``Software`` tab, search and install the following packages (the example illustrates the use of [literal]``x86_64`` architecture): + +* uyuni-proxy-httpd-image +* uyuni-proxy-salt-broker-image +* uyuni-proxy-squid-image +* uyuni-proxy-ssh-image +* uyuni-proxy-tftpd-image + ++ + +Return to Proxy configuration tab, and continue with the remaining configuration. + +. Option [literal]``Registry`` can be used if connectivity is available. ++ +For more information about deployment in air-gapped environment, see xref:installation-and-upgrade:container-deployment/mlm/proxy-air-gapped-deployment-mlm.adoc[]. + +. In case [literal]``Registry`` is selected, proceed with selecting one of two options: [literal]``Simple`` or [literal]``Advanced``. +. If the option selected is [literal]``Simple``, provide the values in [literal]``Registry URL`` and [literal]``Containers Tag``. ++ +* For [literal]``Registry URL`` use [literal]``registry.opensuse.org/uyuni``. +* Select the tag from the drop-down list. + +. If the option selected is [literal]``Advanced`` additional section of the form opens. ++ +* For every indivudual URL field, use the registry [literal]``registry.opensuse.org/uyuni`` and the corresponding suffix, or example _proxy-httpd_ or _salt-broker_. +* Select the tag from the drop-down list. +. Once all fields are filled in, click btn:[Apply] to apply the changes. + + +[WARNING] +==== +When configuring a proxy chain, the parent proxy needs access to any registry that a child proxy is set to use as its source. +==== +