Uyuni proxy #10177 ke

[keichwa]

• master
  close https://github.com/SUSE/spacewalk/issues/10177

[juliogonzalez]

Several changes requested. Also, please check if the procedures are working by using real instances (if not done already).

After reviewing the whole files, I really wonder if the differences are so big to justify different docs for Uyuni and SUSE Manager in this case. Not my call, but both having ifs and having separate files brings problems maintaining (one makes the doc somehow harder to read, the other forces to changes two files - adding the risk of people not remembering about one).

[juliogonzalez]

We should check this, as now we are duplicating the question for SUSE Manager 4.1 and Uyuni (and 4.0 if we port there)

[keichwa]

new: https://github.com/SUSE/spacewalk/issues/10521

[juliogonzalez]

I suggest you add the issue URL here.

[keichwa]

Extract from my mails (per request):

I'm still wondering how I can bootstrap an opensuse client where I can
install the proxy.  I have these repos from
https://download.opensuse.org:

Leap_15-Uyuni-Client-Tools
leap15_1
leap15_1_update
proxy_uyuni4


I already created these channels:

leap 15.1                      uyuni documentation     35157   0       0
leap 15.1 update               uyuni documentation     7476    666     0
Leap_15-Uyuni-Client-Tools     uyuni documentation     80      0       0
proxy uyuni4                   uyuni documentation     84      0       0
zz my uyuni proxy4 leap151     uyuni documentation     42785   666     1

Now I first need a bootstrap repo and a recommendation how a should
arrange the channels for the proxy (base and child channels).

And this one:

> This list is somehow confusing for me, can you provide the URLs of the 
> repositories assigned to the chanells?

https://download.opensuse.org/distribution/leap/15.1/repo/oss
https://download.opensuse.org/update/leap/15.1/oss/
https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Master:/openSUSE_Leap_15-Uyuni-Client-Tools/openSUSE_Leap_15.0/

Instead of
https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable/images/repo/Uyuni-Proxy-4.0-POOL-x86_64-Media1/
I shall probably use Master here too.

> How did you add the channels? Via spacewalk-common-channels?

With the Web UI (Software > Manage > Channels).  You can access it here:
https://d137.suse.de/ — the VM is running on my workstation.

I tried spacewalk-common-channels, but it did not like me.

[juliogonzalez]

What I got from @paususe is that whoever is documenting, should test if the changes are correct (in short: verify that the procedure works as described), specially when something is new or for big rewrites.

@paususe am I missing anything?

[keichwa]

What I got from @paususe is that whoever is documenting, should test if the changes are correct (in short: verify that the procedure works as described), specially when something is new or for big rewrites.

Fine with me! And I'd especially like to continue with Uyuni docs and testing! Much more than re-organizing the Reference Guide ;)

@paususe am I missing anything?

Question is whether this applies for SUMA and Uyuni the same way.

[Loquacity]

What I got from @paususe is that whoever is documenting, should test if the changes are correct (in short: verify that the procedure works as described), specially when something is new or for big rewrites.

Fine with me! And I'd especially like to continue with Uyuni docs and testing! Much more than re-organizing the Reference Guide ;)

We don't have a problem with a lack of content in our books, adding new content is something that seems to have been happening quite effectively for many years. Unfortunately, sometimes you have to do the plumbing as well. I appreciate that reorganising guides is the most boring sort of docs plumbing, and we've done an awful lot of it over the past year. I promise that once the Ref Guide is done (in a couple of months, max), then we can get back to the more exciting stuff. See my email on 4.1 docs deliverables, there's a lot more exciting things coming down the pipeline for you to get stuck into.

@paususe am I missing anything?

Question is whether this applies for SUMA and Uyuni the same way.

[jcayouette]

lgtm

[juliogonzalez]

Question is whether this applies for SUMA and Uyuni the same way.

That's what I do when I contribute to the doc, doesn't matter if it's for SUSE Manager or Uyuni, and it's what I'd expect for any external contributor as well (not calling you external contributor :-))

FMPOV it's just a matter of good practice. In the same way a PR for the code project (uyuni-project/uyuni) should be tested and working, a PR for the doc should be tested and working.

[juliogonzalez]

I am sorry to be so direct, but no approval from my side unless we have a final e2e test.

If we are going to improve this, let's make sure that at least it works as it should.

That doesn't mean this can't get merged, you go ahead but at your own risk :-)

[keichwa]

Julio González Gil <notifications@github.com> writes:

I am sorry to be so direct, but no approval from my side unless we have a final e2e test.

Make perfect sense! I'm now about to verify it. The registration stage still needs to be updated and committed. We just debugged it, but I never actually committed it ;) Next I'll not do such an exercise on my own; I'll ask for a demo first ;)

…

-- Karl Eichwalder SUSE Software Solutions Germany GmbH Product & Solution Documentation Maxfeldstraße 5 90409 Nürnberg, Germany Geschäftsführer: Felix Imendörffer (HRB 36809, AG Nürnberg)

[keichwa]

I am sorry to be so direct, but no approval from my side unless we have a final e2e test.

If we are going to improve this, let's make sure that at least it works as it should.

I do not know what "e2e" means. But I now was able to install, register, and set up an Uyuni Proxy. It's worth reading and approving, @juliogonzalez

That doesn't mean this can't get merged, you go ahead but at your own risk :-)
Now I can happily take the risk. My description is not a smooth reading (becaus of the xrefs), but now it work.

@Loquacity I created a new file, but do not know where to include it in the configuration config nav file. It's client-configuration/pages/clients-opensuse.adoc. I need your help, please.

[keichwa]

Another question: Do we also want this in the 4.0 documentation?

[juliogonzalez]

I do not know what "e2e" means. But I now was able to install, register, and set up an Uyuni Proxy. It's worth reading and approving, @juliogonzalez

I meant End-to-End testing, which is what you did (testing that it works as in a production environment).

I will try to review it today.

Another question: Do we also want this in the 4.0 documentation?

Not needed.

[juliogonzalez]

In general LGTM, but:

• Leap 15.0 is not supported as it's EoL
• Link the new opensuse client doc to the nav page.
• FMPOV we should only support salt for Uyuni Proxies (but @mcalmer and @paususe should agree as well)
• Remove all comments that are not strictly needed
• For things to be reviewed, add the URLs to the relevant issues.