Hi Ricardo, Yes, the overall strategy is get rid of libvirt, we are making the transition in two steps. 4.2 uses rvmomi + vmware tools for storage, networking, and monitoring.
VirtualMachine management, uses both, libvirt to define the guest and basic operations; while rvmomi is used just for attachnic and reconfigure the guest. In the next version 4.4, we will re-implement the other functions... Cheers Ruben On Thu, Jul 18, 2013 at 7:33 PM, Ricardo Duarte <[email protected]> wrote: > Hi there, > > As the new 4.2 release uses RbVmomi, why is there still the need for > Libvirt? > Also, why is there still a need for adding the oneadmin and keysto the > ESXi hosts? > Shouldn't it be possible to do everything through RbVmomi and the vSphere > API? > > Thanks, > Ricardo Duarte > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > > -- > <http://lists.opennebula.org/listinfo.cgi/users-opennebula.org> > -- > Join us at OpenNebulaConf2013 in Berlin, 24-26 September, 2013 > -- > Ruben S. Montero, PhD > Project co-Lead and Chief Architect > OpenNebula - The Open Source Solution for Data Center Virtualization > <http://lists.opennebula.org/listinfo.cgi/users-opennebula.org> > www.OpenNebula.org | [email protected] | @OpenNebula >
_______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
