New features in OpenNebula 5.4, Jaime Melis
2 likes832 views
This document summarizes new features in OpenNebula 5.4, including improvements to its integration with vCenter. Some key highlights are: 1) Enhancements to storage functionality like persistent/non-persistent images, disk resizing, and improved Storage DRS support. 2) Increased networking capabilities such as creating port groups and configuring VLAN IDs dynamically. 3) Significant speed improvements through caching and other optimizations, providing access to vCenter objects up to 100x faster. 4) Additional fixes that resolve prior limitations like attach/detach poweroff state and proper cleanup of terminated VMs.
![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](https://image.slidesharecdn.com/newfeaturesinopennebula5-170921143947/85/New-features-in-OpenNebula-5-4-Jaime-Melis-4-320.jpg)
New features in OpenNebula 5.4, Jaime Melis
- 1. New Features in OpenNebula 5.4 OpenNebula.systems © OpenNebula Systems. This presentation is confidential and owned by OpenNebula Systems. Unauthorized use or disclosure of the included information is strictly prohibited. OpenNebula is trademark of OpenNebula Systems. All the other product and company names mentioned herein may be the trademarks or registered trademarks of their respective owners.
- 2. OpenNebula.systems OpenNebula 5.4 Blueprints ● Simplify Deployment ● Simplify Current Features ● vCenter ● … and other enhancements
- 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
- 6. Introduction OpenNebula approach to vCenter integration OpenNebula.systems
- 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...
- 15. GOAL OF OPENNEBULA 5.4 OpenNebula.systems Up to speed with
- 18. STORAGE OpenNebula.systems ● System Datastores. OpenNebula chooses the target datastore (replacing Storage DRS!) ● Persistent & Non-persistent images ● Volatile disks ● Disk Resize upon instantiation ● Linked clones: faster deployment times, smaller disk usage ● Unmanaged disks ● Storage DRS support extended (Volatile & Persistent disks) ● Whole plethora of operations
- 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!
- 27. OpenNebula 5.4 vCenter Improvements Fixing Limitations OpenNebula.systems
- 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