vOneCloud is an OpenNebula distribution optimized to work on existing VMware vCenter deployments to provide full cloud features.
The new version vOneCloud version 3.4 is powered by OpenNebula 5.8 “Edge”, and, as such, includes functionalities present in Edge relevant to vOneCloud:
- Change boot order of VM devices updating the VM Template. More info here.
- VM migration between clusters and datastores is now supported, check here.
- Migrate images from KVM to vCenter, or vice versa. More info here.
- New configuration file, default behaviour in the process of image importation can be changed. More info here.
- VM actions can be specified relative to the VM start scheduled actions, for example: terminate this VM after a month of being created.
- Automatic selection of Virtual Networks for VM NICs, balance network usage at deployment time or reduce clutter in your VM Template list. More info here.
- New self-provisioning model for networks, Virtual Network Templates. Users can now instantiate their own virtual networks from predefined templates with their own addressing.
- Support for NIC Alias, VM’s can have more than one IP associated to the same network interface. More info here.
More important, vOneCloud 3.4 has been certified with support for vSphere 6.0, 6.5 and 6.7.
vOneCloud is distributed as a virtual appliance for vSphere. It contains all required OpenNebula services within a single CentOS Linux appliance. All components are fully open-source and have been certified to work in enterprise environments. You can build your cloud in just 5 minutes!
You can download an OVA with 3.4 already installed. If you are a customer with an active support subscription, you can upgrade your vOneCloud instance with one click from the Control Panel.
OpenNebula interacts with vCenter instances by interfacing with its SOAP API. This API allows remote communication, enabling architectures where the OpenNebula instance and the vCenter environment are remotely located.
A single OpenNebula instance can orchestrate several vCenter instances remotely located in the hybrid cloud environment.
Connectivity between data centers needs to have low latency in order to have a reliable management of vCenter from OpenNebula (see Figure 1).
For more information see also: