3. OpenNebula.systems
OpenNebula 5.4
HA & Federation
● Built-in replication (no more MySQL master-slave)
● Based on Raft for zone HA
● Similar for zone federation
Sunstone
sched &
drivers
oned Sunstone
oned
Sunstone
sched &
drivers
oned
Master zone
followers
leader
Sunstone
sched &
drivers
oned Sunstone
oned
Sunstone
sched &
drivers
oned
Slave zone
followers
leader
4. OpenNebula.systems
OpenNebula 5.4
VMGroups
● Affinity: VM-VM, VM-Host, Role-Role
● A VM bind to a VMGroup at instantiation
ROLE = [ NAME = backup, POLICY = ANTI_AFFINED, HOST_ANTI_AFFINED = ”5,6” ]
ROLE = [ NAME = db, POLICY = AFFINED, HOST_AFFINED = ”2,3,4” ]
ROLE = [ NAME = monitor ]
ROLE = [ NAME = frontend ]
ANTI_AFFINED = “db, backup”
AFFINED = “monitor, front-end”
host1 host2 host3 host4 host5 host6
5. OpenNebula.systems
OpenNebula 5.4
Other Enhancements
● non-SLAAC address ranges for IPv6
● IPv6 Security groups
● Improved audit trails (extended history records)
● Custom redefinition of action rights
● Minor enhancements Storage (Ceph snapshots, live resize)
● DB housekeeping
● Re-worked dialogs in Sunstone
7. OPENNEBULA FEATURES
FEATURES FOR VIRTUAL INFRA MANAGEMENT AND CLOUD ORCHESTRATION
KVM Xen
Virtual Infra Management
•Capacity management
•Multi-VM management
•Resource optimization
•HA and business continuity
OpenNebula
Cloud Management
•VDC multi-tenancy
•Simple cloud GUI and interfaces
•Service elasticity/provisioning
•Federation/hybrid
vCenter
VMware
OpenNebula
OpenNebula.systems
9. KEY POINTS
OpenNebula.systems
● Seamless integration
● Leverages vMotion, HA, DRS scheduling…
● OpenNebula provides multi-tenant, cloud-like
provisioning layer, benefiting from quotas, etc.
● Maintain VMware management tools, procedures
and workflows
● Virtual Machines are deployed using Templates that
already exist in vCenter.
● Access a vCenter server that manages one or more
ESX Clusters.
10. KEY POINTS
OpenNebula.systems
● Access a vCenter server that manages one or more
ESX Clusters.
● Each vCenter Cluster is represented as an
aggregated hypervisor:
○ OpenNebula chooses the vCenter Cluster
○ VMware DRS chooses the ESX Host
● After being instantiated with OpenNebula it can be
managed either with OpenNebula (add/remove
NICs, control life-cycle) or through vCenter
(OpenNebula will poll).
12. REQUIREMENTS
OpenNebula.systems
● vCenter 5.5, 6.0 and 6.5.
● At least one cluster with at least one ESX 5.5, 6.0 or
6.5 host.
● VMware tools in the guest OS.
● vCenter user for OpenNebula
● ESX Hosts in a Cluster must share a Datastore
● DRS is strongly recommended
● VNC is supported
13. WORKFLOW
OpenNebula.systems
● Import vCenter Cluster (OpenNebula Host)
● Import or Create Networks. IP range and VLAN.
● Import vCenter Template
○ Creates Networks
○ Creates Images
○ Creates Datastores
● Update Template (Optional)
○ Add disks, nics, context, etc.
● Instantiate VM
○ Disk Resize, etc...
23. NETWORKING
OpenNebula.systems
● Manage Networks, not just consume them
● Create Networks (Port Groups) in vCenter
● Works for standard or distributed switches
● It can also create Switches if PHYDEV is specified
(vmnic1, …)
● Configure the underlying network dynamically.
Including VLAN IDs.
● Provide isolation dynamically.
26. SPEED
OpenNebula.systems
● Rewrite of the monitorization routines
● New caching component for vCenter resources
● Rapid access to vCenter objects
● Pre-migrator to ease OpenNebula upgrades
Overall improvement by 2 orders of magnitude!
28. FIXING LIMITATIONS
OpenNebula.systems
● Attach / Detach poweroff state
● Choose in what folder VMs will be placed
● Context regeneration
● Resources with spaces (including cluster names)
● Proper cleanup of terminated VMs after poweroff
● Recover delete cleans all resources
● VNC is configured automatically for Wild VMs