-
Notifications
You must be signed in to change notification settings - Fork 106
Extending proxy conversion instructions #4174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
The file can be checked here: |
modules/installation-and-upgrade/pages/container-deployment/proxy-conversion-from-client.adoc
Outdated
Show resolved
Hide resolved
modules/installation-and-upgrade/pages/container-deployment/proxy-conversion-from-client.adoc
Outdated
Show resolved
Hide resolved
modules/installation-and-upgrade/pages/container-deployment/proxy-conversion-from-client.adoc
Outdated
Show resolved
Hide resolved
modules/installation-and-upgrade/pages/container-deployment/proxy-conversion-from-client.adoc
Outdated
Show resolved
Hide resolved
…oxy-conversion-from-client.adoc Co-authored-by: Karl Eichwalder <ke@suse.de>
Following the feedback, this is the final version: |
modules/installation-and-upgrade/pages/container-deployment/proxy-conversion-from-client.adoc
Outdated
Show resolved
Hide resolved
modules/installation-and-upgrade/pages/container-deployment/proxy-conversion-from-client.adoc
Outdated
Show resolved
Hide resolved
I have a couple of additional comments that as being an admin using the doc, I'd like to be more clear about. Feel free to consider/not to consider them :) "Configure the Proxy" section: |
modules/installation-and-upgrade/pages/container-deployment/proxy-conversion-from-client.adoc
Outdated
Show resolved
Hide resolved
** 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That should be already covered in the requisites to convert to a proxy actually, bc they'd also required to have access to mgrpxy and podman
** 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, just noticed that the alternative install methods do explicitly mention the bootstrapping and channel setup. In that case suggest reviewing then what I documented @ https://confluence.suse.com/display/~RMestre/Proxy+Onboarding
Overview
Currently, setting up a proxy involves the following steps:
- Onboard minion;
- Configure channels;
- Generate proxy configuration file;
- Transfer proxy configuration file into the minion;
- Install software into minion (podman and mgrpxy);
- Execute mgrpxy install;
For this initial feature iteration, our goal is to streamline the process defined by steps 3, 4, 5 & 6. We will archive this by extending the existing web UI functionality (Systems > Proxy Configuration). Once the user fills in the necessary information in a form, the system will automatically set up (or update) the minion as a proxy with minimal manual intervention.
bearing in mind that step 2 "Configure channels" could be read as "add and sync the proxy extension child channel." and after this you would be able to install the packages as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Introduction might be made clearer, see suggestion.
...nstallation-and-upgrade/pages/container-deployment/mlm/proxy-conversion-from-client-mlm.adoc
Outdated
Show resolved
Hide resolved
...llation-and-upgrade/pages/container-deployment/uyuni/proxy-conversion-from-client-uyuni.adoc
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cosmetic suggestion
...llation-and-upgrade/pages/container-deployment/uyuni/proxy-conversion-from-client-uyuni.adoc
Outdated
Show resolved
Hide resolved
…uni/proxy-conversion-from-client-uyuni.adoc Co-authored-by: Karl Eichwalder <ke@suse.de>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for the changes @0rnela
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't fully review yet, but why do we have 2 sepparated pages for uyuni and MLM? The content really similar, with just a few deviations.
Can that be handled with the ifeval::[{mlm-content} == true]
All other pages in this section are separated for MLM and Uyuni. |
...nstallation-and-upgrade/pages/container-deployment/mlm/proxy-conversion-from-client-mlm.adoc
Outdated
Show resolved
Hide resolved
...nstallation-and-upgrade/pages/container-deployment/mlm/proxy-conversion-from-client-mlm.adoc
Outdated
Show resolved
Hide resolved
...nstallation-and-upgrade/pages/container-deployment/mlm/proxy-conversion-from-client-mlm.adoc
Outdated
Show resolved
Hide resolved
...nstallation-and-upgrade/pages/container-deployment/mlm/proxy-conversion-from-client-mlm.adoc
Outdated
Show resolved
Hide resolved
...llation-and-upgrade/pages/container-deployment/uyuni/proxy-conversion-from-client-uyuni.adoc
Outdated
Show resolved
Hide resolved
...llation-and-upgrade/pages/container-deployment/uyuni/proxy-conversion-from-client-uyuni.adoc
Outdated
Show resolved
Hide resolved
...llation-and-upgrade/pages/container-deployment/uyuni/proxy-conversion-from-client-uyuni.adoc
Outdated
Show resolved
Hide resolved
...nstallation-and-upgrade/pages/container-deployment/mlm/proxy-conversion-from-client-mlm.adoc
Outdated
Show resolved
Hide resolved
...llation-and-upgrade/pages/container-deployment/uyuni/proxy-conversion-from-client-uyuni.adoc
Outdated
Show resolved
Hide resolved
…m/proxy-conversion-from-client-mlm.adoc Co-authored-by: Cedric Bosdonnat <cbosdonnat@suse.com>
…uni/proxy-conversion-from-client-uyuni.adoc Co-authored-by: Cedric Bosdonnat <cbosdonnat@suse.com>
…uni/proxy-conversion-from-client-uyuni.adoc Co-authored-by: Cedric Bosdonnat <cbosdonnat@suse.com>
…m/proxy-conversion-from-client-mlm.adoc Co-authored-by: Cedric Bosdonnat <cbosdonnat@suse.com>
…uni/proxy-conversion-from-client-uyuni.adoc Co-authored-by: Cedric Bosdonnat <cbosdonnat@suse.com>
…m/proxy-conversion-from-client-mlm.adoc Co-authored-by: Cedric Bosdonnat <cbosdonnat@suse.com>
...nstallation-and-upgrade/pages/container-deployment/mlm/proxy-conversion-from-client-mlm.adoc
Outdated
Show resolved
Hide resolved
...nstallation-and-upgrade/pages/container-deployment/mlm/proxy-conversion-from-client-mlm.adoc
Show resolved
Hide resolved
...nstallation-and-upgrade/pages/container-deployment/mlm/proxy-conversion-from-client-mlm.adoc
Outdated
Show resolved
Hide resolved
...nstallation-and-upgrade/pages/container-deployment/mlm/proxy-conversion-from-client-mlm.adoc
Show resolved
Hide resolved
...nstallation-and-upgrade/pages/container-deployment/mlm/proxy-conversion-from-client-mlm.adoc
Show resolved
Hide resolved
...nstallation-and-upgrade/pages/container-deployment/mlm/proxy-conversion-from-client-mlm.adoc
Show resolved
Hide resolved
...nstallation-and-upgrade/pages/container-deployment/mlm/proxy-conversion-from-client-mlm.adoc
Outdated
Show resolved
Hide resolved
...nstallation-and-upgrade/pages/container-deployment/mlm/proxy-conversion-from-client-mlm.adoc
Show resolved
Hide resolved
I have incorporated all comments. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left some suggestions and nit-picks.
. 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* Select [literal]``Keep`` if an existing certificates should be used. | |
* Select [literal]``Keep`` if an existing certificate should be used. |
+ | ||
The certificate can be replaced by one of the two options: | ||
+ | ||
** an existing certificate, provided by the third-party authority |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
** an existing certificate, provided by the third-party authority | |
** an existing certificate, provided by a third-party authority |
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`` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
** a brand new certificate generated from the existing {productname} CA certificate for the proxy, by using command [command]``rhn-ssl-tool`` | |
** a brand new certificate generated from the existing {productname} CA certificate for the proxy, by using the command [command]``rhn-ssl-tool`` |
|
||
. 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[]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For more information about deployment in air-gapped environment, see xref:installation-and-upgrade:container-deployment/mlm/proxy-air-gapped-deployment-mlm.adoc[]. | |
For more information about deployment in air-gapped environment, see xref:installation-and-upgrade:container-deployment/mlm/proxy-air-gapped-deployment-mlm.adoc[]. |
Once space too much.
* 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
. If the option selected is [literal]``Advanced`` additional section of the form opens. | |
. If the option selected is [literal]``Advanced``, an additional section of the form opens. |
Description
Additional clarifications for the proxy conversion from client process which covers new sub-tab Configuration.
Target branches
Links