Skip to content
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

Initial SUSE Multilinux Manager chapter #462

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

joesusecom
Copy link

This is the draft for the new SUMA chapter. Still work in progress.


== Keeping SLE Micro up to date

TBD: Do we want to give customers options (Elemental all-in, direct registration against SCC), or is SUSE Manager the only fully supported (and documented) option (in SUSE Edge 3.1)?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We already document SCC registration so I think it makes sense to describe SUSE Manager as an optional alternative?


For the next step you need two registration codes that you can find in the SUSE Customer Center:

* Your registration code for SLE Micro 5.5
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be 6.0

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SUMA 5.0 is only supported on SLE Micro 5.5 (but can manage SL Micro 6.x hosts)

Log into your SUSE Manager Server host as root.

Pull the Edge Image Builder container:
podman pull registry.opensuse.org/isv/suse/edge/edgeimagebuilder/containerfile-sp6/suse/edge-image-builder:1.1.0.rc2
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be registry.suse.com/edge/3.1/edge-image-builder:1.1.0

If you either want to preload the image directly to a physical node or directly start it from a VM, you can also use the "raw" image flavor.

Download or copy the image
SL-Micro.x86_64-6.0-Default-SelfInstall-GM.install.iso to the "base-images" directoy and name it "slemicro.iso".
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be the new GM2 image


cd /opt/eib

podman run --rm -it --privileged -v ./:/eib registry.opensuse.org/isv/suse/edge/edgeimagebuilder/containerfile-sp6/suse/edge-image-builder:1.1.0.rc2 build --definition-file iso-definition.yaml
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as above should be the registry.suse.com version


If you haven't created any cloned software channels, you can keep the setting for the Base Channel to "SUSE Manager Default". This will automatically assign the correct SUSE update repository for your edge nodes.

As "Child Channel", select the "include recomended" slider for the hardware architecture your activation key is used for. This will add the "SUSE-Manager-Tools-For-SL-Micro-6.0" channel.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
As "Child Channel", select the "include recomended" slider for the hardware architecture your activation key is used for. This will add the "SUSE-Manager-Tools-For-SL-Micro-6.0" channel.
As "Child Channel", select the "include recommended" slider for the hardware architecture your activation key is used for. This will add the "SUSE-Manager-Tools-For-SL-Micro-6.0" channel.

@@ -0,0 +1,236 @@
== SUSE Manager
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You'll also need to add the front-matter with an anchor then link to it from edge.adoc

@agracey
Copy link
Contributor

agracey commented Nov 21, 2024

I'd like to link to this from the doc I'm writing. Any idea on when it might be ready to publish?

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.

4 participants