This new release of the appliance, tailored to ease the provisioning of resources from vSphere based infrastructures, comes packed with exciting new features.
- In vOneCloud 1.6 is now possible to define virtual machine capacity, in terms of CPU and Memory presented to the guest OS, changing this value from the vCenter Template at the time of cloning a new Virtual Machine.
- Along this line, it is also possible to resize the capacity of a Virtual Machine after deployment.
- Moreover, it is also possible to confine vOneCloud users on a particular vCenter Resource Pool, making it possible to enforce company security policies by reducing the rights of the needed credentials by the appliance and also offering to vOneCloud users a subset of all the available hardware resources controlled by vCenter.
- In order to facilitate the customization of Virtual Machines, in terms of configuring software packages and perform any generic administration task at guest OS boot time, vOneCloud introduces the ability to run any script at boot time, using a new set of contextualization packages.
- Improvements are also offered in the VNC connection capabilities, to accommodate foreign keyboards.
The above features and components add to the already present ability to expose a multi-tenant cloud-like provisioning layer through the use of virtual data centers, self-service portal, or hybrid cloud computing to connect in-house vCenter infrastructures with public clouds. vOneCloud seamlessly integrates with running vCenter virtualised infrastructures, leveraging advanced features such as vMotion, HA or DRS scheduling provided by the VMware vSphere product family.
vOneCloud is zero intrusive (although it fully manages the life cycle of VMs), try it out without the need to commit to it. If you happen (as strange at that may be!) to don’t like it you can just remove the appliance.
Lead Cloud Engineer & Engineering Manager at OpenNebula