No argument on introduction (awareness). The question is ... at what level, and when?
LPI Certified Level 1 & 2 (LPIC-1 & 2) for junior & senior sysadmins is really broad. It's really difficult to pare it down, but that's also the great value of the certification too. These will be the objectives for the next few years. So ... ** Like most things in the LPIC-1 & 2, for a junior, let alone senior, sysadmin knowing of something, before -- to be blunt -- screw it up, is key. I've already run into multiple cases where very, very experienced GNU/Linux sysadmins dorked up Docker volumes. That's why I get a bit ... 'adamant' that we at least consider 'awareness' for a sysadmin, especially senior, for the future. Not saying it's included in the objectives, but it would be good if we recognize we're getting systems with containers ... and sysadmins may not know. Setting up containers? Infrastucture, storage, network, etc... for them? Nope. That's DevOps. But awareness that they exist, and doing something might dork them up, and their storage? Absolutely, I think it's time, at least for a senior sysadmin LPIC-2. A JTA or other survey that identifies how many existing LPIC-2 certified individuals are running into containers would probably be good to gauge adoption. After all, some enterprises are running dedicated container platforms like SuSE Rancher Kubernetes Engine (RKE), Red Hat OpenShift Container Platform (OCP) and others, or even putting them on hosting platforms, since they offer the container platforms directly (e.g., even Microsoft offers OCP now, not just Amazon et al.). But more and more, especially in the case of workstation systems as well as various on-site servers, we're seeing Docker, Podman and other implements without a formal environment. Not a shocker because the first purpose of OpenShift (pre-Docker and pre-LXC) using kernel namespaces, cgroups and SELinux back in the '00s was as a development environment for JBoss developers at Red Hat. These are the container runtimes we have to be aware of as senior sysadmins. - bjs **P.S. Drawing comparisons to Red Hat, I really don't like having, even for a RHEL-only (or CentOS Stream-only) environment, only a RHCSA (or RHCE for that matter), and prefer LPIC-1 w/RHCSA (and LPIC-2 w/RHCE -- especially since the RHCE is basically just Ansible for services configuration & setup). I'll even take a LPIC-1 only over RHCSA only at times, depending on the environment, if someone only has one. LPIC-1 (and LPIC-2) have almost an order of magnitude more breath and awareness, even implementation. On Sun, Feb 20, 2022 at 1:27 PM Rilindo Foster <[email protected]> wrote: > If we want to include an introduction to container concepts (and I could > see validity of that argument) I would suggest putting in the 202 exam. It > is a nice, natural segue for all the application topics there - basically, > transition from what the apps are to how you would deploy those apps *today. > > (With the emphasis on *introduction*, since the deep dive into containers > is covered in the 305 exam) > > https://www.lpi.org/our-certifications/exam-305-objectives > > > > I would probably be reluctant to add containerisation to the LPIC-2 exam – >> I >> agree with Fabian's comments about scope creep. It is probably best left >> in >> the DevOps area for now. >> > > And yet ... senior sysadmins will run into containers running on systems. > Should it not be awareness at some point? I think LPIC-1 will eventually > be unable to avoid the awareness level at some point.** > > - bjs > > **P.S. We're at the point in my current environment where we're pushing > out Containers to run under WSL2, including using Ansible playbooks to > configure/manage them. But WSL2 isn't on the exam, of course. > > -- > Bryan J Smith - http://www.linkedin.com/in/bjsmith > E-mail: b.j.smith at ieee.org or me at bjsmith.me > > _______________________________________________ > lpi-examdev mailing list > [email protected] > https://list.lpi.org/mailman/listinfo/lpi-examdev > > > -- -- Bryan J Smith - http://www.linkedin.com/in/bjsmith E-mail: b.j.smith at ieee.org or me at bjsmith.me
_______________________________________________ lpi-examdev mailing list [email protected] https://list.lpi.org/mailman/listinfo/lpi-examdev
