Hello,

OpenStack is not a hypervisor but a cloud layer ontop of Hypervisors... 
Management stacks matter as well.

Re: Bring things together
That is a tough one perhaps require multiple LPI-300 exams to gain a Speciality 
would be my suggestion.... Cloud would require virt+sec+storage+network+etc.... 
Use a higher level concept....

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 10:27 AM, Bryan J Smith <[email protected]> wrote:

> On Fri, Jun 21, 2013 at 11:19 AM, Edward Haletky <[email protected]> wrote:
> LPIC-1 or 2 they are VERY basic. Everyone needs to know how to do them.
> 
> Well,  I wasn't going to go too far in my opinion, but yes, that is my view 
> too, _if_ we are going to cover virtualization sub-LPIC-3.
>  
> Agreed. However, knowing ovirt/RHEV/Openstack GUIs are important as well.
> 
> oVirt/RHEV is just too stack-specific, even if oVirt was supposed to be the 
> generic management/user interface framework for more than just KVM.
> 
> OpenStack would require its own series of exams.  But yes, it's looking more 
> and more like it's the solution everyone is getting behind (except only one, 
> proprietary company).
> 
> 2 or a speciality of 3 but keep it to KVM, Xen, OpenVZ, etc. and also cloud 
> layers such as OpenStack.
> 
> OpenStack as a Hypervisor does get rather interesting.
> 
> But as a rule, Upstream buy-in matters.
>  
> We cannot avoid identity but that should be part of a security specialization.
> 
> The bigger question is ...
> 
> We can have specialty exams on Virtualization, Storage and Identity ... but 
> how do we bring them together?
> 
> If you think LPI is the only organization wrestling with this, think again.  
> ;)
> 
> I do not see a forth level either but multiple specialty levels. Yet, since 
> virtualization is a must then put the basics lower down for KVM and make 
> openvswitch, migration, etc a speciality.
> 
> LPI has to be careful to avoid making it Hypervisor-centric, even if there is 
> only one, totally open source stack out there, and it is built around KVM.
> 
> 
> --
> 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

Reply via email to