Opennebula New Presentation
Opennebula New Presentation
16 April, 2021
Objectives
• Introduction and Benefits of the latest OpenNebula version (Yashika)
• OpenNebula features for the different cloud types
Private (Anisha)
Hybrid (Abhishek)
Public (Abhishek)
• Architecture of OpenNebula (Akash)
• Deployment of OpenNebula (Ankit)
• Provisioning Model of OpenNebula (Rashi)
• Consumption Model of Open Nebula (Ayush)
• Compare OpenNebula with other similar technologies (Ayush)
What is OpenNebula?
Open-Source Toolkit for Building Cloud Infrastructures
Infrastructure User
• Faster delivery and scalability of services to meet dynamic demands
• Support for heterogeneous execution environments
• Full control of the lifecycle of virtualized services management
System Integrators
• Fits into any existing data center
• Builds any type of Cloud deployment
• Open-source software, Apache license
• Seamless integration with any product and service in the virtualization/cloud
ecosystem and management tool in the data center
Features – Private Clouds
Private Clouds
• The infrastructure is owned and used by a single organization
• Private clouds enable a flexible and agile management of local infrastructure
• Not a new model, datacenter management has been around for a while
• Internal interfaces expose additional functionality for managing virtualized
resources and controlling data center operation, not exposed by cloud interfaces
• Cloud interfaces may be also provided for users requiring higher abstraction
• Centralized management
• VM placement optimization
• Dynamic resizing and partitioning
of the infrastructure
• Support for heterogeneous
workloads
Features – Private Clouds
Private Clouds
Feature Function
Internal Interface • Unix-like CLI for fully management of VM life-cycle and physical boxes
• XML-RPC API and libvirt virtualization API
Scheduler • Requirement/rank matchmaker allowing the definition of workload and
resource-aware allocation policies
• Support for advance reservation of capacity through Haizea
Virtualization • Xen, KVM, and VMware
Management • Generic libvirt connector (VirtualBox planned for 1.4.2)
Image Management • General mechanisms to transfer and clone VM images
Network Management • Definition of isolated virtual networks to interconnect VMs
Service Management • Support for multi-tier services consisting of groups of inter-connected
and Contextualization VMs, and their auto-configuration at boot time
Security • Management of users by the infrastructure administrator
Fault Tolerance • Persistent database backend to store host and VM information
Scalability • Tested in the management of medium scale infrastructures with hundreds
of servers and VMs (no scalability issues has been reported)
Installation • Installation on a UNIX cluster front-end without requiring new services
• Distributed in Ubuntu 9.04 (Jaunty Jackalope)
Flexibility and • Open, flexible and extensible architecture, interfaces and components,
Extensibility allowing its integration with any product or tool
Features – Hybrid Clouds
Hybrid Clouds
Feature Function
Feature Function
Cloud Consumer
Cloud Application
Developer
Cloud
Administrator
Cloud Integrator
The Anatomy of the Cloud
OpenNebula Architecture - Infrastructure Agnostic and Highly Customizable
Cloud
CLI GUI
Servers
Scheduler
OCA (Ruby, Java)
XML-RPC API
OpenNebula core
It does not have any specific infrastructure requirements, fitting well into any pre-
existing environment, storage, network, or user-management policies.
The user can take advantage of the native OpenNebula cloud API (OCA), available as
Java, Ruby, and XML-RPC API.
The Anatomy of the Cloud
OpenNebula Architecture – Performance and Security
Security is also taken into serious consideration. Host communication takes place
exclusively through secured connections protected with the SSH RSA keypairs
and Secure Socket Layer (SSL).
Ebtables works at the Address Resolution Protocol (ARP) level, also known as
the data link layer in the OSI stack.
The Anatomy of the Cloud
Cloud Architecture - The Internals of the Cloud
Network Storage
• VLAN • VM disks (file & block)
• Firewalling • Image Distribution
• Multiple Technologies • Multiple Backends
Monitoring,Virtualization,
Storage and Network
• Repository of VM images
• Multiple Backends (LVM, Ceph)
Front end is also called as master node is a single gateway is responsible for queuing
Scheduling and submitting the job to machine in cluster.
Provide an interface to the user for managing , monitoring, and submitting the job.
It host the virtual machine repository and also run the transfer services to manage the
transfer of virtual machine image to concern work node.
It provides raw computing power for processing the jobs which is submitted
by the master node.
Benefits
• Partition of cloud resources
• Complete isolation of users, organizations or workloads
• Allocation of Clusters with different levels of security, performance or high
availability to different groups with different workload profiles
• Containers for the execution of virtual appliances (SDDCs)
• Way of hiding physical resources from Group members
• Simple federation and scalability of cloud infrastructures beyond a single
cloud instance and data center
The OpenNebula Consumption Model
Front-end
Worker Nodes
The OpenNebula Consumption Model
Administration
Yes Yes No No Yes
Interface
Hybrid Cloud
No No No No Yes
Computing
Flexibility and
Yes No Yes Yes Yes
Extensibility
1. https://opennebula.io/docs/
2. https://www.opensourceforu.com/2017/02/an-
introduction-to-opennebula/
3. https://archives.opennebula.org/about:technology
4. https://github.com/OpenNebula/one
Thank You !