Gotta Chime in Here... If there is going to be a virtualization sub exam it must minimally cover the following:
libvirt/virsh, qemu, openvswitch, openstack virtuoso (at least the difference between it and kvm) ovirt paravirtualized drivers Specific packages: virt-* packages fence-virtd package (why do you need a virtualization fence) open-vm-tools (vSphere specific but important) If you leave out any of those in favor of Type 2 hypervisors such as virtual box you are missing the entire point of "server" virtualization and real virtualization within an enterprise. It is not about 'easy' it is about 'certification' a certification on a type 2 hypervisor is similar to a certification on Microsoft word, glad you know the app, but I really do not care. I want a cert that covers SERVER virtualization. I.e Type 1 hypervisors of which KVM and Xen are such. Cover those topics make the cert worthwhile to anyone in the virtualization community. Best regards, -- Edward L. Haletky President AstroArch Consulting, Inc. http://www.astroarch.com/ Author of VMware vSphere(TM) and Virtual Infrastructure Security <http://www.astroarch.com/?page_id=268> On Jun 21, 2013, at 7:14 AM, Bryan J Smith <[email protected]> wrote: > On Fri, Jun 21, 2013 at 8:02 AM, Anselm Lingnau > <[email protected]> wrote: > Bryan J Smith wrote: > > Or just libvirt, virsh, etc... that has drivers for different Hypervisors, > > different container approaches, etc... > > Whatever. I like libvirt and virsh and would like to see them exposed more in > the LPIC-304 exam. > > Ummm ... I think you missed my point. If people want something in > sub-LPIC-3, then why not libvirt and virsh _before_ anything else? > > However, FWIW, if all you want is a CentOS virtual machine on your Debian box > to check out RPM then VirtualBox is very probably the easiest way to go. > > OMG. This ... wow ... nevermind. You understand VirtualBox is not all GPL, > and it's not upstream for a reason ... correct? > > It may not be 100% ideologically pure but it works well and takes only three > minutes to set up – which gives people that much more time to check out RPM. > When I have only a few days to take people through the LPIC-1 material, that > sort of thing counts. > > There's VirtualPC, VMware Player, etc... for Windows. > And Xen and/or KVM built-into Linux, if containers won't work (e.g., > different distro). > > I'm not getting into any debate on this. > > My _point_ is why is _no-one_ even mentioning libvirt/virsh when it is > _exactly_ what we should be covering _if_ we are going to introduce something > sub-LPIC-3. That's my point. > > I'm not here with the bumper sticker, "My hypervisor beat up your honor > student." Context. > > If you'd rather be ideologically pure and don't mind spending more time > setting up libvirt *and* something that will do the actual virtualisation > instead of doing what you originally set out to do (like checking out RPM) > then I don't have an issue with that. It is probably interesting and you will > very likely learn *something* for life. More power to you. > > Libvirt is _built-in_ to _every_ distro. It's like GLibC. What don't you > understand about that? > > Virsh is just a command line interface (CLI) for common administration, true > _standard_ virtually all distros _agreed_ to include and support. You don't > get any more "universal" than that. > > We cover a lot of things in LPIC-1, even LPIC-2, that aren't complete > configuration/setup, but junior administrators use day-in, day-out. I cannot > think of a better example than libvirt/virsh. > > In any event I think that virtualisation as such is best left in LPIC-304 > rather than shoehorned (with all the best of intentions, of course) into > LPIC-1/2. I don't see much point in dragging individual bits and pieces into > the lower exams that will just lead to more of those endless cans of worms of > which we have quite enough already. That includes libvirt and virsh. > > And yet ... virsh is usable "out-of-the-box" on virtually _any_ distro. > > I don't know how much of a better argument I can make. This isn't about > "purity." This is about "commonality." > > But I think you can't see that, because you have VirtualBox on the mind. And > you're not the only one who teaches LPI to people, even newbies. ;) > > > -- > Bryan J Smith - Professional, Technical Annoyance > b.j.smith at ieee.org - http://www.linkedin.com/in/bjsmith > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. _______________________________________________ > lpi-examdev mailing list > [email protected] > http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
_______________________________________________ lpi-examdev mailing list [email protected] http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
