Skip to content

Removed air-gapped deployment from Uyuni guide #3896

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

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

0rnela
Copy link
Contributor

@0rnela 0rnela commented Apr 17, 2025

Description

Target branches

  • master

@0rnela 0rnela requested a review from deneb-alpha April 17, 2025 14:34
@0rnela 0rnela marked this pull request as draft April 17, 2025 14:35
@juliogonzalez
Copy link
Member

@0rnela this is strictly speaking not correct.

I think the page is wrong for both SUSE Multi-Linux Manager 5.1 and the future Uyuni, as we now provide RPMs with the images (for Uyuni those will come with the upcoming version).

So unless I am wrong, the instructions should mention the RPMs. And of course a single image is not enough anymore, as the postgresql container uses a separate image. This is valid for SUSE Multi-Linux Manager 5.1 and the future Uyuni

So even if I am wrong about the RPMs, this probably means this page:

  • Needs to stay and maybe be duplicated (one for Uyuni one for SUSE Multi-Linux Manager) or needs IFs, so different image names and different registries are used for Uyuni or SUSE Multi-Linux Manager
  • Needs changes to include the new postgresql image, or to use the RPMs

Please coordinate with Hexagon about this one.

@juliogonzalez
Copy link
Member

https://documentation.suse.com/suma/5.0/en/suse-manager/installation-and-upgrade/container-deployment/suma/server-air-gapped-deployment-suma.html does not mention skopeo or such things anymore, but the RPMs.

Some IMHO at master we need two pages, or ifs to use the same method with slightly different things for Uyuni and SUSE Multi-Linux Manager (such as the RPM names)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants