Start Here: OpenNebula Overview¶
Welcome to OpenNebula documentation!
OpenNebula is an open-source management platform to build IaaS private, public and hybrid clouds. Installing a cloud from scratch could be a complex process, in the sense that many components and concepts are involved. The degree of familiarity with these concepts (system administration, infrastructure planning, virtualization management...) will determine the difficulty of the installation process.
If you are new to OpenNebula you should go through this short introduction before proceeding to the deployment and administration guides.
Step 1. Choose Your Hypervisor¶
The first step is to decide on the hypervisor that you will use in your cloud infrastructure. The main OpenNebula distribution provides full support for the two most widely used hypervisors, KVM and VMware (through vCenter), at different levels of functionality.
- Virtualization and Cloud Management on KVM. Many companies use OpenNebula to manage data center virtualization, consolidate servers, and integrate existing IT assets for computing, storage, and networking. In this deployment model, OpenNebula directly integrates with KVM and has complete control over virtual and physical resources, providing advanced features for capacity management, resource optimization, high availability and business continuity. Some of these deployments additionally use OpenNebula’s Cloud Management and Provisioning features when they want to federate data centers, implement cloudbursting, or offer self-service portals for end users.
- Cloud Management on VMware vCenter. Other companies use OpenNebula to provide a multi-tenant, cloud-like provisioning layer on top of VMware vCenter. These deployments are looking for provisioning, elasticity and multi-tenancy cloud features like virtual data centers provisioning, datacenter federation or hybrid cloud computing to connect in-house infrastructures with public clouds, while the infrastructure is managed by already familiar tools for infrastructure management and operation, such as vSphere and vCenter Operations Manager.
- Containerization with LXD. Containers are the next step towards virtualization. They have a minimal memory footprint and skip the compute intensive and sometimes unacceptable performance degradation inherent to hardware emulation. You can have a very high density of containers per virtualization node and run workloads close to bare-metal metrics. LXD focuses on system containers, instead of similar technologies like Docker, which focuses on application containers.
After having installed the cloud with one hypervisor you may add other hypervisors. You can deploy heterogeneous multi-hypervisor environments managed by a single OpenNebula instance. An advantage of using OpenNebula on VMware is the strategic path to openness as companies move beyond virtualization toward a private cloud. OpenNebula can leverage existing VMware infrastructure, protecting IT investments, and at the same time gradually integrate other open-source hypervisors, therefore avoiding future vendor lock-in and strengthening the negotiating position of the company.
There are other virtualization technologies, like Xen, supported by the community. Please refer to the OpenNebula Add-ons Catalog.
Step 2. Design and Install the Cloud¶
2.1. Design the Cloud Architecture¶
In order to get the most out of an OpenNebula Cloud, we recommend that you create a plan with the features, performance, scalability, and high availability characteristics you want in your deployment. We have prepared Cloud Architecture Design guides for KVM and LXD and vCenter to help you plan an OpenNebula installation, so you can easily architect your deployment and understand the technologies involved in the management of virtualized resources and their relationship. These guides have been created from the collective information and experiences from hundreds of users and cloud client engagements. Besides the main logical components and interrelationships, these guides document software products, configurations, and requirements of infrastructure platforms recommended for a smooth OpenNebula installation.
2.2. Install the Front-end¶
The next step is the installation of OpenNebula in the cloud front-end. This installation process is the same for any underlying hypervisor.
Optionally you can setup a high available cluster for OpenNebula for OpenNebula to reduce downtime of core OpenNebula services, and configure a MySQL backend as an alternative to the default Sqlite backend if you are planning a large-scale infrastructure.
2.3. Install the Virtualization hosts¶
Now you are ready to add the virtualization nodes. The OpenNebula packages bring support for KVM, LXD and vCenter nodes. In the case of vCenter, a host represents a vCenter cluster with all its ESX hosts. You can add different hypervisors to the same OpenNebula instance, or any other virtualization technology, like Xen, supported by the community. Please refer to the OpenNebula Add-ons Catalog.
Step 3. Set-up Infrastructure and Services¶
3.1. Integrate with Data Center Infrastructure¶
Now you should have an OpenNebula cloud up and running with at least one virtualization node. The next step is, if needed, to perform the integration of OpenNebula with your infrastructure platform and define the configuration of its components. When using the vCenter driver, no additional integration is required because the interaction with the underlying networking, storage and compute infrastructure is performed through vCenter.
However when using KVM or LXD, in the open cloud architecture, OpenNebula directly manages the hypervisor, networking and storage platforms, and you may need additional configuration:
3.2. Configure Cloud Services¶
Sunstone, the OpenNebula GUI, brings by default a pre-defined configuration of views. Optionally it can be customized and extended to meet your needs. You can customize the roles and views, improve security with x509 authentication and SSL or improve scalability for large deployments.
Step 4. Operate your Cloud¶
4.1. Define a Provisioning Model¶
Before configuring multi-tenancy and defining the provisioning model of your cloud, we recommend you go through this introduction to the OpenNebula provisioning model. In a small installation with a few hosts, you can skip this guide and use OpenNebula without giving much thought to infrastructure partitioning and provisioning. But for medium and large deployments you will probably want to provide some level of isolation and structure.
- Regarding the underlying infrastructure, OpenNebula provides complete functionality for the management of the physical hosts and clusters in the cloud. A Cluster is a group of Hosts that can have associated Datastores and Virtual Networks.
- Regarding user management, OpenNebula features advanced multi-tenancy with powerful users and groups management, an Access Control List mechanism allowing different role management with fine grain permission granting over any resource, resource quota management to track and limit computing, storage and networking utilization, and a configurable accounting and showback system to visualize and report resource usage data and to allow their integration with chargeback and billing platforms, or to guarantee fair share of resources among users.
- Last but not least, you can define VDCs (Virtual Data Center) as assignments of one or several user groups to a pool of physical resources. While clusters are used to group physical resources according to common characteristics such as networking topology or physical location, Virtual Data Centers (VDCs) allow creating “logical” pools of resources (which could belong to different clusters and zones) and allocate them to user groups.
4.2. Manage Virtual Resources¶
Now everything is ready for operation. OpenNebula provides full control to manage virtual resources.
- Virtual machine image management that allows storing disk images in catalogs (termed datastores), that can then be used to define VMs or shared with other users. The images can be OS installations, persistent data sets or empty data blocks that are created within the datastore.
- Virtual network management of Virtual networks that can be organized in network catalogs, and provide means to interconnect virtual machines. This kind of resource can be defined as IPv4, IPv6, or mixed networks, and can be used to achieve full isolation between virtual networks. Networks can be easily interconnected by using virtual routers and KVM and LXD users can also dynamically configure security groups
- Virtual machine template management with a template catalog system that allows registering virtual machine definitions in the system, to be instantiated later as virtual machine instances.
- Virtual machine instance management with a number of operations that can be performed to control the lifecycle of the virtual machine instances, such as migration (live and cold), stop, resume, cancel, power-off, etc.
Several reference guides are provided for more information about definition files, templates and the CLI.
4.3. Create Virtual Machines¶
One of the most important aspects of the cloud is the preparation of the images for our users. OpenNebula uses a method called contextualization to send information to the VM at boot time. Its most basic usage is to share networking configuration and login credentials with the VM so it can be configured. More advanced cases can be starting a custom script on VM boot, or preparing a configuration to use OpenNebula Gate.
Step 5. Install Advanced Components¶
This step is optional and only for advanced users. We recommend you familiarize yourself with OpenNebula before installing these components.
OpenNebula brings the following advanced components:
- Implementation of the EC2 Query and EBS public cloud interfaces.
- OneFlow allows multi-VM application and auto-scaling to define, execute and manage multi-tiered elastic applications, or services composed of interconnected Virtual Machines with deployment dependencies between them and auto-scaling rules.
- The datacenter federation functionality allows for the centralized management of multiple instances of OpenNebula for scalability, isolation and multiple-site support.
- Application insight with OneGate allows Virtual Machine guests to pull and push VM information from OpenNebula. Users and administrators can use it to gather metrics, detect problems in their applications, and trigger OneFlow elasticity rules from inside the VM.
- Marketplaces for sharing, provisioning and consuming cloud images. They can be seen as external datastores, where images can be easily imported, exported and shared by a federation of OpenNebula instances.
- Cloud bursting gives support to build a hybrid cloud, an extension of a private cloud to combine local resources with resources from remote cloud providers. A whole public cloud provider can be encapsulated as a local resource to be able to use extra computational capacity to satisfy peak demands. Out of the box connectors are shipped to support Amazon EC2 and Microsoft Azure cloudbursting.
- Disaggregated Data Centers provides tools to build and grow the physical infrastructure with resources from public bare-metal cloud providers, e.g. Amazon EC2 and Packet. New physical machines are allocated from the provider, configured to run the hypervisor and added into OpenNebula as new clusters with hosts, datastores and virtual networks.
Step 6. Integrate with other Components¶
This step is optional and only for integrators and builders.
Because no two clouds are the same, OpenNebula provides many different interfaces that can be used to interact with the functionality offered to manage physical and virtual resources.
- Modular and extensible architecture with customizable plug-ins for integration with any third-party data center infrastructure platform for storage, monitoring, networking, authentication, virtualization, cloud bursting and market.
- API for integration with higher level tools such as billing, self-service portals... that offers all the rich functionality of the OpenNebula core, with bindings for ruby and java and XML-RPC API,
- OneFlow API to create, control and monitor multi-tier applications or services composed of interconnected Virtual Machines.
- Sunstone custom routes and tabs to extend the sunstone server.
- Hook Manager to trigger administration scripts upon VM state change.