OpenNebula provides the tools and methods needed to dynamically grow your cloud infrastructure with Edge Clusters built with virtual and physical resources running on remote cloud providers. You are able to grow your private cloud with resources at cloud and edge data center locations and enable true hyrbid and multi-cloud environments to meet latency, bandwidth, or data regulation needs of your workload.
In this quick start guide we use Edge Clusters to easily build a cloud infrastructure and try the main operation and user features of OpenNebula.
Edge Clusters can be virtual or metal depending of the instance type used to build the cluster. Note that not all providers offer both instance types.
|Edge/Cloud Provider||Edge Cluster||Hypervisor|
|Equinix||metal||KVM, Firecracker and LXC|
|AWS||metal||KVM, Firecracker and LXC|
|Vultr||metal (in progress)||KVM, Firecracker and LXC|
|On-prem||metal||KVM, Firecracker and LXC|
The Edge Cluster type determines the hypervisor and workload that can be run in the cluster. The following table summarizes the Edge Cluster you need to run specific workloads:
|Use Case||Edge Cluster||Hypervisor|
|I want to run application containers…||virtual||LXC|
|I want to run virtual servers…||metal||KVM, LXC|
|I want to run a Kubernetes cluster…||metal||KVM (k8s based)|
|Firecracker (k3s based)|
In the above table, application containers are those imported from DockerHub, LinuxContainers or TunrkeyLinux, as well as images created from DockerFiles. On the other hand Virtual servers use full system disk images.