Information about version pinning missing

[stdevel]

When installing Uyuni Server or Proxy, the installation documentation points to using the "latest and greatest" repository. In some cases, users might not want to use the very latest version of Uyuni, but the version before.

Also, when having a very outdated version of Uyuni, updating to the most recent version is likely to fail.

Documentation Update Required

It would be great to have a not about version pinning in the "Install Uyuni Server with openSUSE" section.

Let me know if you basically think that this is a good idea. I can create a PR for you.

What does the documentation say now?

It simply suggests using the very latest repository packages.

What change is required?

A note could be added.

What content needs to be added?

The documentation should mention additional repository URLs deoending on architecture and type (Server, Proxy):

• https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Snapshots:/YYYY.MM/images/repo/Uyuni-Server-POOL-x86_64-Media1/
• https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Snapshots:/YYYY.MM/images/repo/Uyuni-Server-POOL-aarch64-Media1/
• https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Snapshots:/YYYY.MM/images/repo/Uyuni-Proxy-POOL-x86_64-Media1/
• https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Snapshots:/YYYY.MM/images/repo/Uyuni-Proxy-POOL-aarch64-Media1/

Subject Matter Expert (SME)

I don't know.

Version

Which version of the software is this feature/update expected to land in (if known)? Next? Which version of the documentation must this feature/update land in (if known)? Next? Does the content need to be backported to previous documentation versions (if known)? Would be useful, so yes.

Internal SUSE Reporters

This repository is public. If you are reporting an issue that needs to remain company confidential, please use the internal Bugzilla instance instead.

[juliogonzalez]

Hello!

The Snapshots are not supported, only the latest Uyuni version (Stable) is, as it's a rolling release product and updates should be applied frequently.

So the Snapshot should not be part of the documentation. However they can be used for testing, and if the user needs to migrate to intermediate version (on its own), before going to the latest, such workaround could be used (again, not supported, Snapshots are not even tested).

So I'd suggest documenting them at the site, clearly specifying the limitations.

[stdevel]

Thanks for your opinion, @juliogonzalez - just created PR #2536 regarding this. What do you think? Is the wording okay?

[juliogonzalez]

Not being supported, I'd put this on the site, rather than on the documentation.

Not only it's not supported, it can require more stuff such as matching the right OS for the right snapshot for example.

But ultimately it's for the doc team to decide where they want to handle, of course :-)

[keichwa]

Maybe, it would be the best to add some such note to https://www.uyuni-project.org/pages/devel-version.html? Then we could consider whether we want to reference it from installation instructions. This hopefully would not confuse users.

[juliogonzalez]

Maybe, it would be the best to add some such note to https://www.uyuni-project.org/pages/devel-version.html? Then we could consider whether we want to reference it from installation instructions. This hopefully would not confuse users.

I'd better consider a new snapshots.html page for this. The instructions are going to be different from what devel looks like, including the warnings, and we should not even have a list of repositories for client tools, as we don't have snapshots for them.

[keichwa]

I'd better consider a new snapshots.html page for this. The instructions are going to be different from what devel looks like, including the warnings, and we should not even have a list of repositories for client tools, as we don't have snapshots for them.

Sure, such a new page would be helpful. Then we could add a warning note to the product documentation and provide a link the the new page. I guess we must add the new page to https://github.com/uyuni-project/uyuni-project.github.io to the pages directory as HTML? (I never contributed to that repo.)