System RequirementsΒΆ

Note

It is advised to manage one vCenter by only one vOneCloud. Otherwise VMs from both server will clash and poduce errors.

The following components are needed to be present in the infrastructure to implement a cloud infrastructure run by vOneCloud:

vCenter 5.5
  1. The IP or DNS needs to be known, as well as the credentials (username and password) of an admin user.
  1. DRS is not required but it is recommended. vOneCloud does not schedule to the granularity of ESX hosts, and you would need DRS to select the actual ESX host within the cluster.
  1. All ESX belonging to the same vCenter cluster to be exposed to vOneCloud need to share at least one datastore among them.
  1. VMs that will be instantiated through vOneCloud saved as VMs Templates in vCenter.
ESX 5.5 With at least 2 GB of free RAM and 1 free CPU
To enable VNC functionality from vOneCloud there are two requirements: 1) the ESX hosts need to be accesible from vOneCloud and 2) the ESX firewall should allow for VNC connections (see the note below)

Note

To enable VNC functionality for vOneCloud, repeat the following procedure for each ESX:

  • In the vSphere client proceed to Home -> Inventory -> Hosts and Clusters
  • Select the ESX host, Configuration tab and select Security Profile in the Software category.
  • In the Firewall section, select the Properties. Enable GDB Server, then click OK.

vOneCloud ships with a default of 2 CPUs and 2 GB of RAM, and as such it has been certified for infrastructures of the following dimensions:

  • Up to 4 vCenters
  • Up to 40 ESXs managed by each vCenter
  • Up to 1.000 VMs in total, each vCenter managing up to 250 VMs
  • Up to 100 users, being the concurrent limit 10 users accessing the system simultaneously

Note

For infrastructures exceeding the aforementioned limits, we recommend an installation of OpenNebula from scracth on a bare metal server, using the vCenter drivers