Hi Jeremy, thanks for your encouraging feedback!
On Sun, Feb 26, 2017 at 5:05 AM, Jeremy Hajek <[email protected]> wrote: I had one piece of advice. The Docker material needs to be reviewed > because the concepts there are vastly different than Virtualization. > Perhaps the Docker material could be its own track/specialization? > This depends a lot of the depth of Docker. You're right, the current objectives are mostly about using Docker, not about configuring its latest detail and understand the actual containerization on a Kernel level. If we would like to test that, we would need to require more background in Linux / operating system than we currently ask the candidates of the new exam to have. Such an exam would probably be better off in the LPIC-3 track since we can expect a high level of Linux proficiency. For the LPIC-OT DevOps Tools Engineer, we intentionally want to keep these requirements low to make the effort to study the objectives reasonable for software developers too. How far do you get into these technical background in your lectures? > What I mean is traditional Virtualization which we have been using for a > while now (VMware, Virtual Box, others) is essentially the same concepts > as a regular PC-- its hardware virtualization (virt of a BIOS, Drivers, and > so on) > > Docker (and containers in general) move to a different concept of > immutable infrastructure--which flies in the face of all the LPIC base > standards. Those needs are lessened when you are enabling containers that > have no SSH even. Containers that are being spun up via AWS Lambda for > instance are done so fast and then destroyed--because it is cheaper to spin > a container up calculate something and then spin it down (much in the way > you would use a function()in a programming language) . TL DR Containers > (Docker) are more than just lightweight virtualization. > Good point. So far, we we have "Design software to be run in containers" in 701.1 which strives this a little. Do you think adding "Understand major differences between containers and virtual machines" to either 702.1 or 702.3 helps? 702.1 would be pretty Docker-specific, 702.3 we could allow us to cover this in a more generic way. We also have the security implications of containers as well as awareness of other container solutions (rkt) here. Let me know what you think -- and thank you for pointing this out. Fabian
_______________________________________________ lpi-examdev mailing list [email protected] http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
