[opensuse-kubic] Explanation on the different Kubic and MicroOS images
Hi all, is there a explanation somewhere (that I did not find?) on what the heap of different images is? I was looking for e.g. a list of packages that are included in one image, but not in the other. In other words, what makes the kubeadm one a better choice than the "Tumbleweed kubic" image for my use case? What is either offering or missing, in comparison? When to choose one over the other? I could look into the kiwi templates, I guess, but I was hoping there was a wiki page or presentation or similar... ;-) Kind Regards, Johannes Taking OpenStack qcow2 images as example: openSUSE-MicroOS.x86_64-16.0.0-ContainerHost-OpenStack-Cloud-Snapshot20191110.qcow2 This would be "Tumbleweed Kubic - Multi-purpose Standalone & Kubernetes Container Operating System based on openSUSE MicroOS " openSUSE-MicroOS.x86_64-16.0.0-Kubic-kubeadm-OpenStack-Cloud-Snapshot20191110.qcow2 This would be "kubeadm Certified Kubernetes - Certified Kubernetes Distribution using kubeadm atop an openSUSE MicroOS base system" And then we have the plain MicroOS: openSUSE-MicroOS.x86_64-16.0.0-OpenStack-Cloud-Snapshot20191110.qcow2 -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
On Tue, 2019-11-12 at 14:27 +0100, Johannes Kastl wrote:
Hi all,
is there a explanation somewhere (that I did not find?) on what the heap of different images is?
I was looking for e.g. a list of packages that are included in one image, but not in the other. In other words, what makes the kubeadm one a better choice than the "Tumbleweed kubic" image for my use case? What is either offering or missing, in comparison? When to choose one over the other?
I could look into the kiwi templates, I guess, but I was hoping there was a wiki page or presentation or similar... ;-)
Kind Regards, Johannes
Taking OpenStack qcow2 images as example:
openSUSE-MicroOS.x86_64-16.0.0-ContainerHost-OpenStack-Cloud- Snapshot20191110.qcow2 This would be "Tumbleweed Kubic - Multi-purpose Standalone & Kubernetes Container Operating System based on openSUSE MicroOS "
a more accurate description would be "Single Purpose Standalone Container Host Operating system based on MicroOS"
openSUSE-MicroOS.x86_64-16.0.0-Kubic-kubeadm-OpenStack-Cloud- Snapshot20191110.qcow2 This would be "kubeadm Certified Kubernetes - Certified Kubernetes Distribution using kubeadm atop an openSUSE MicroOS base system"
This is accurate, but I'd prefer it if it read "openSUSE Kubic - Certified Kubernetes Distribution atop an openSUSE MicroOS base system"
And then we have the plain MicroOS: openSUSE-MicroOS.x86_64-16.0.0-OpenStack-Cloud-Snapshot20191110.qcow2
"Plain MicroOS - Single Purpose Standalone Operating System with no example workload" In short, the images map to the various system roles available by the MicroOS and Kubic ISOs, with the MicroOS Container Host being a shared role that is available on both the MicroOS and the Kubic ISOs. Does this help? -- Richard Brown Linux Distribution Engineer - Future Technology Team Phone +4991174053-361 SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer -- To unsubscribe, e-mail: opensuse-kubic+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kubic+owner@opensuse.org
Am 12.11.19 um 14:37 schrieb Richard Brown:
Does this help?
A little. kubeadm is for building up a kubernetes cluster by using kubeadm commands manually. For building up a Kubernetes cluster using the mechanisms from SUSE CaaSP 3.x I would use the kubeadm images for the admin node and the other image for masters and workers? If I just want to have a single host running docker/cri-o/... I would use the containerhost one? Maybe I find some time in the next couple of weeks and would start a small wiki page describing that... Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
On Wed, 2019-11-13 at 10:26 +0100, Johannes Kastl wrote:
Am 12.11.19 um 14:37 schrieb Richard Brown:
Does this help?
A little.
kubeadm is for building up a kubernetes cluster by using kubeadm commands manually.
Correct
For building up a Kubernetes cluster using the mechanisms from SUSE CaaSP 3.x I would use the kubeadm images for the admin node and the other image for masters and workers?
The SUSE CaaSP Team have not contributed their mechanisms to openSUSE so we have no images that are anologous to that.
If I just want to have a single host running docker/cri-o/... I would use the containerhost one?
The container host ones run podman - crio only makes sense in the context of Kubernetes. We don't have images using the "docker open source runtime" images any more. (Docker Inc's approach to trademarks mean we'd have to be very careful how we'd refer to them if we did)
Maybe I find some time in the next couple of weeks and would start a small wiki page describing that...
Thank you - https://en.opensuse.org/Kubic:Installation#Download would probably be the first place to update Regards, Richard
Johannes
-- Richard Brown Linux Distribution Engineer - Future Technology Team Phone +4991174053-361 SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer -- To unsubscribe, e-mail: opensuse-kubic+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kubic+owner@opensuse.org
Am 13.11.19 um 10:56 schrieb Richard Brown:
On Wed, 2019-11-13 at 10:26 +0100, Johannes Kastl wrote:
kubeadm is for building up a kubernetes cluster by using kubeadm commands manually.
Correct
Thanks for the confirmation.
For building up a Kubernetes cluster using the mechanisms from SUSE CaaSP 3.x I would use the kubeadm images for the admin node and the other image for masters and workers?
The SUSE CaaSP Team have not contributed their mechanisms to openSUSE so we have no images that are anologous to that.
Sorry to hear that. I found skuba (used in CaaSP 4.x) is also not present in openSUSE... :-( And sorry, I just guessed as the "role" chosen during installation sounded similar.
If I just want to have a single host running docker/cri-o/... I would use the containerhost one?
The container host ones run podman - crio only makes sense in the context of Kubernetes. We don't have images using the "docker open source runtime" images any more. (Docker Inc's approach to trademarks mean we'd have to be very careful how we'd refer to them if we did)
So it comes with podman out of the box, that is what I wanted to know. If (for some strange reason) I want to have cri-o or install docker from $SOMEHWERE_ELSE, I guess this image would be the best to start from, wouldn't it? Or better use plain MicroOS in that case?
Maybe I find some time in the next couple of weeks and would start a small wiki page describing that...
Thank you - https://en.opensuse.org/Kubic:Installation#Download would probably be the first place to update
Its on my todolist^W kanban board... Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
On Wed, Nov 13, Johannes Kastl wrote:
Am 13.11.19 um 10:56 schrieb Richard Brown:
On Wed, 2019-11-13 at 10:26 +0100, Johannes Kastl wrote:
use the containerhost one?
The container host ones run podman - crio only makes sense in the context of Kubernetes. We don't have images using the "docker open source runtime" images any more. (Docker Inc's approach to trademarks mean we'd have to be very careful how we'd refer to them if we did)
So it comes with podman out of the box, that is what I wanted to know. If (for some strange reason) I want to have cri-o or install docker from $SOMEHWERE_ELSE, I guess this image would be the best to start from, wouldn't it? Or better use plain MicroOS in that case?
If you start with podman, you have to deinstall RPMs and replace them with others for cri-o, not sure about docker. So it's easier to start with plain MicroOS in that case. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Felix Imendoerffer (HRB 36809, AG Nürnberg) -- To unsubscribe, e-mail: opensuse-kubic+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kubic+owner@opensuse.org
Am 13.11.19 um 11:20 schrieb Thorsten Kukuk:
On Wed, Nov 13, Johannes Kastl wrote:
So it comes with podman out of the box, that is what I wanted to know. If (for some strange reason) I want to have cri-o or install docker from $SOMEHWERE_ELSE, I guess this image would be the best to start from, wouldn't it? Or better use plain MicroOS in that case?
If you start with podman, you have to deinstall RPMs and replace them with others for cri-o, not sure about docker. So it's easier to start with plain MicroOS in that case.
Thorsten, thanks a lot for the confirmation. Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
participants (3)
-
Johannes Kastl -
Richard Brown -
Thorsten Kukuk