Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

OpenNebula Conf 2014 | Understanding the OpenNebula Model for Cloud Provisioning by Ruben S. Montero


Published on

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.

Published in: Software
  • Be the first to comment

  • Be the first to like this

OpenNebula Conf 2014 | Understanding the OpenNebula Model for Cloud Provisioning by Ruben S. Montero

  1. 1. Welcome to OpenNebulaConf 2014! Understanding the OpenNebula Model for Cloud Provisioning Ruben S. Montero
  2. 2. 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) #OpenNebulaConf
  3. 3. A Multi-tenant Infrastructure Logical group of hypervisors, datastores and virtual networks 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 #OpenNebulaConf
  4. 4. A Multi-tenant Infrastructure A cluster provides resources to a user group Cluster A Cluster B User Group A User Group B Quota:Limit group/user usage Self-Provision: ● VMs ↔ Hypervisors ● Images ↔ Datastores ● Address↔Virtual Networks Showback, users get an estimated associated resource usage cost based on CPU and MEMORY cost 4.12 #OpenNebulaConf
  5. 5. A Multi-tenant Infrastructure Virtual Data Center 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 #OpenNebulaConf
  6. 6. Bootstraping the Cloud VDC admin can save VM changes for her VDC users 3. VM Template ● Include HW presets ● Hypervisor settings ● Placement policies ● Cost 1. Disks ● Vanilla OS installations ● Pre-built appliances ● Context & user inputs Security Groups with VNET semantics 4.12 2. Network Interface Controllers ● Pre-defined connections ● Set at deployment time ● Re-use Network attributes Datastore & Virtual Network determines running cluster #OpenNebulaConf
  7. 7. Interfacing the Cloud: Cattle vs Pets ● Easily disposed ● Simple interfaces ● Short life-cycles ● HA, Backup policies ● Richer interfaces ● Long-lasting life-cycles #OpenNebulaConf
  8. 8. Interfacing the Cloud: Cattles ● Instantiate many times same installation ● Use context ● Limited set of operations ● mainly GUI access - CloudView Cloud View Improve Clone VMs to templates to support multiple disks 4.12 Clone before deploy (instantiate to persistent) 4.12 Taking care of those cattles... #OpenNebulaConf
  9. 9. Interfacing the Cloud: Pets ● Instantiate many times same installation ● Persistency + Backup (snapshots) ● Rich set of operations ● API + CLI + Sunstone access Sunstone Cold attach of disks and NIC 4.12 Migrate VMs across system datastores 4.12 Taking care of those pets.. #OpenNebulaConf
  10. 10. Danke! Thank You! #OpenNebulaConf