Hello everybody, i am a little bit confused about this discussion about Xen, Kubernetes and the LXC/LXD Part.
But first things first. In the old 304 Exam Xen has a weight of 9, in the new one 4. I think this is a good compromise. Yes, KVM is the winner against Xen, but Xen is not dead. There are a few companies that using Xen and look at this: https://xenproject.org/about-us/project-members/ . So, I know Amazon will left Xen, but Xen is under the Linux Foundation and in the next Years Xen will not die and this year there will be a new Version 4.13. So, Stephan, the new 305 Exam gave LXC/LXD a weight of 6. My colleague at work does not understand that. The say: LXC/LXD is dead because of docker. So, and now? My opion is that LXC/LXD is not dead, but with docker / podman the Standing is another. <https://dict.leo.org/englisch-deutsch/work> Maybe the weight of 6 are a little bit to high, but i can live with this. ;) Fabian, this is the Point you talking about: make we an Exam for Admins or DevOps? To push Kubernetes to 7 is to much. I think 4-5 would be okay. So, about Docker and Podman. As Fabian started the discussion last year about the new 300 Exams (300/303/304) nothing went out about the financial issue and the sold to Mirantis from docker. And Red Hat 8 comes this year with Podman, right? So, the guys from LPI has to start to generate the questions and the answers. And this was definitely not in the last week ;) What i am trying to say is this: the LPI can not see in the future and at one point at time they have to start writing questions. So, when LPI changes the complete Docker Things to Podman, what is in half a year? Maybe somethings change again and we have the discussion about some points here again. And this goes so on and there will be not a new 305 Exam ;) Regards Dirk Am 02.12.19 um 19:08 schrieb Stephan Wenderlich: > Update: > Noticed LXC/LXD is on the new curriculum NICE ! > But Docker got a higher weight...and Docker Swarm is included > ...nope...not good. Docker-Swarm is almost dead. > > Why no PodMan ??? > > On 02.12.19 19:01, Stephan Wenderlich wrote: >> >> Hi, >> >> XEN classic is almost dead. Their documentation is very weak and many >> links do not work anymore for years. At the other hand, KVM and >> exspecially Proxmox are huge. So, I would put the whole XEN Topic to >> an awareness level. >> What I totally disagree with is docker. They do have serious >> financial issues and almost everything is sold to Mirantis. If one >> truly dives into docker, you will notice some big disadvantages (like >> no real init, one main daemon etc.). Podman from RedHat will overcome >> all these problems. >> >> Docker and Kubernetes do not fit in. >> >> What I would like to see is LXC/LXD, which are really popular and >> they don't need a shady Docker-Hub. Proxmox offers them directly via >> GUI and with the Proxmox Cluster System, a HA system like K8S is >> avaiable. >> >> On 28.11.19 16:51, Fabian Thorns wrote: >>> Dear all, >>> >>> before removing the 'draft' status from the 305 objectives page >>> (https://wiki.lpi.org/wiki/LPIC-305_Objectives_V3.0), what do you >>> think about the current relevance of Xen (weight: 4) and Qemu >>> (weight: 6) compared to Kubernetes (currently contained in a weight >>> 2 objective). To me it seems that Xen becomes less and less relevant >>> while Qemu/KVM is almost entirely used through other means (libvirt, >>> proxmox, ...), so testing their specific options and configuration >>> knobs might be arguable. >>> >>> On the other hand, Docker is more and more used through Kubernetes. >>> Currently we just cover the overall concepts of Kubernetes. What if >>> we would reduce the weights of Xen and Qemu to 1 and 2 or 2 and 3 >>> respectively to just cover the architecture in order to free up 5 to >>> 7 weight points which we could spend on Kubernetes instead? We could >>> create another objective about understanding the architecture of >>> Kubernetes, set up a Kubernetes cluster through kubeadm and >>> understand the roles and functions of the most important Kubernetes >>> objects (pods, replicasets, deployments, daemonsets, services, >>> ingress). I wouldn't test creating and managing these objects since >>> that would be more related to the DevOps certification, but cover >>> enough for a kubernetes node admin to understand what their users >>> are doing. >>> >>> Let me know your thoughts :) >>> >>> Fabian >>> >>> >>> _______________________________________________ >>> lpi-examdev mailing list >>> [email protected] >>> https://list.lpi.org/mailman/listinfo/lpi-examdev >> >> _______________________________________________ >> lpi-examdev mailing list >> [email protected] >> https://list.lpi.org/mailman/listinfo/lpi-examdev > > _______________________________________________ > lpi-examdev mailing list > [email protected] > https://list.lpi.org/mailman/listinfo/lpi-examdev
_______________________________________________ lpi-examdev mailing list [email protected] https://list.lpi.org/mailman/listinfo/lpi-examdev
