There are two or three different layers of "cloud virtualization" here.
One is the hypervisor itself, Xen, KVM, or VMWare or (gasp) Hyper-V from Microsoft. I know that libvirt as shipped with SL works with Xen and KVM, think it works with VMWare too but have never tried it. The second is the virtualization management layer--RHEV as bought from red hat or "ovirt" in the Open Source project. As far as I know neither RHEV or ovirt is part of SL. But the extra features that are in those libvirt versions and qemu-kvm versions are gradually getting back ported into the libvirt distributed by the enterprise, or you can go out and find the libvirt source independently. The third are actual cloud softwares such as OpenStack, OpenNebula. RedHat has an "enterprise" version of OpenStack, and another more "Development" environment of it designed to be deployed on top of CentOS. CentOS has long had an OpenNebula packaging and also a Xen on Centos6 setup. I am hoping both of these may be coming our way if and when the SL/Centos link happens but have no official word to that effect. Steve Timm ________________________________ From: [email protected] [[email protected]] on behalf of Yasha Karant [[email protected]] Sent: Tuesday, May 27, 2014 1:12 PM To: scientific-linux-users Subject: Re: SL REST API Is the EMC VMWare "cloud virtualisation" suite consistent/compliant with kvm/libvirt, etc.? My understanding is that the EMC product is compatible with typical REST implimentations in that these evolved from various HTTP related services. Also, for reasons we could discuss off-list (or on list if you prefer), my personal preference is for Xen as a virtualisation suites. My understanding is that Xen does well integrate into a number of environments and distros. Yasha Karant On 05/27/2014 10:02 AM, Jamie Duncan wrote: I would think that your definition of 'cloud' is the most important aspect here, not whether or not the term 'Red Hat' is associated with it. The virtualization technology powering RHEV is kvm, which is fully compliant with libvirt (http://libvirt.org/). If you didn't want to use RHEV or Ovirt you could interact direclty with the libvirt API. The business logic that those products provide isn't there, of course, but you could build that out yourself if you were so inclined. It just takes time & talent. Is that what you're talking about wanting? -jduncan On Tue, May 27, 2014 at 12:52 PM, Yasha Karant <[email protected]<mailto:[email protected]>> wrote: Does SL (i.e., TUV EL) have a standard enterprise-quality production REST API that will interoperate with non-EL "clouds"? The most I could find on a short search is: http://developerblog.redhat.com/2013/12/12/advanced_integration_rhevm-part1/ Advanced integration with Red Hat Enterprise Virtualization Manager (RHEV-M) – Part 1 of 2 and https://fedorahosted.org/rhevm-api/ This is an effort to define an official REST API for Red Hat Enterprise Virtualization <http://www.redhat.com/virtualization/rhev/>. but that the fedorahosted project above is obsolete, replaced by: http://www.ovirt.org/Subprojects in which any mention of TUV by name is in the title of each reference. Yasha Karant -- Thanks, Jamie Duncan @jamieeduncan
