opennebula conf 2014 | understanding the opennebula model for cloud provisioning by ruben s. montero
DESCRIPTION
OpenNebula’s quest for simplicity touches every aspect of the software,and one of the greater effort has been put into the provisioning model. A smooth experience for users entails a proper design of the concepts, ironing out the flow of day to day operations, as well as proper tools for the administrators to manage its cloud. For this reason, OpenNebula features Virtual Datacenters (vDCs), which are containers for the execution of virtual machines, as well as a way of hiding physical resources from group members. Three actors are identified in this model: the cloud administrator, the vDC administrator and the end user. In this talk we will see how this vDCs are created, how physical resources are associated to them and administrators of the vDCs are managed and given permissions. All this topped with an excellent interface, the Cloud View, adapted for each of the actors.TRANSCRIPT
Understanding the OpenNebula Model for Cloud Provisioning
Welcome to OpenNebulaConf 2014!
Ruben S. Montero
OpenNebula.org#OpenNebulaConf
A Multi-tenant Infrastructure
Physical Resource● Tools to establish sharing policies of physical resources● Proper isolation of users● Control and limit usage
Virtual Resources● Self-provisioning● Accomodate different user provisioning models (cattle vs pet)
OpenNebula.org#OpenNebulaConf
Logical group of hypervisors, datastores and virtual networks
A Multi-tenant Infrastructure
Cluster A Cluster B
Placement Policies: Allocate a VM to a given cluster
Access Control: Allocate users to a given cluster
Resources can be assigned to more than one cluster to better balance resource allocation 4.12
OpenNebula.org#OpenNebulaConf
A cluster provides resources to a user group
A Multi-tenant Infrastructure
Cluster A Cluster B
User Group A User Group B
Quota:Limit group/user usage
Showback, users get an estimated associated resource usage cost based on CPU and MEMORY cost 4.12
Self-Provision: ● VMs ↔ Hypervisors● Images ↔ Datastores● Address↔Virtual Networks
OpenNebula.org#OpenNebulaConf
Virtual Data Center
A Multi-tenant Infrastructure
Resource Provider User Group A
VDC Admin: Autonomic management of VDC users
Simple Provision: Use a cloud-like interface
Federate: VDC can spread several Datacenters / Zones
OpenNebula.org#OpenNebulaConf
VDC admin can save VM changes for her VDC users
Bootstraping the Cloud
1. Disks
● Vanilla OS installations● Pre-built appliances● Context & user inputs
● Include HW presets● Hypervisor settings● Placement policies● Cost
3. VM Template
2. Network Interface Controllers
● Pre-defined connections● Set at deployment time● Re-use Network attributes
Datastore & Virtual Network determines running cluster
Security Groups with VNET semantics
4.12
OpenNebula.org#OpenNebulaConf
Interfacing the Cloud: Cattle vs Pets
● HA, Backup policies● Richer interfaces● Long-lasting life-cycles
● Easily disposed● Simple interfaces● Short life-cycles
OpenNebula.org#OpenNebulaConf
Interfacing the Cloud: Cattles
● Instantiate many times same installation● Use context● Limited set of operations● mainly GUI access - CloudView
Improve Clone VMs to templatesto support multiple disks
4.12
Clone before deploy (instantiate to persistent)
4.12
Cloud View
Taking care of those cattles...
OpenNebula.org#OpenNebulaConf
Interfacing the Cloud: Pets
● Instantiate many times same installation● Persistency + Backup (snapshots)● Rich set of operations● API + CLI + Sunstone access
Cold attach of disks and NIC 4.12
Migrate VMs across system datastores
4.12
Taking care of those pets..
Sunstone
OpenNebula.org#OpenNebulaConf
Danke!Thank You!