This document discusses how to configure OpenNebula to use hybrid cloud resources from Amazon EC2 and Microsoft Azure in addition to on-premise resources. It provides instructions on setting up credentials and drivers to integrate EC2 and Azure, creating VM templates that can launch in different regions and cloud providers, and how deployed VMs will be monitored and managed through the standard OpenNebula interfaces.

1. Ruben S. Montero
Chief Architect // @ruben_s_montero // rsmontero@opennebula.org
OpenNebula Hybrid Clouds
with Amazon & Azure

2. Hybrid Cloud Computing...
...or the Utility Computing promise made true
Cloud Management
on premise
Windows
Azure
VM VM VM VM VM

3. The OpenNebula take on Hybrid Clouds
Transparent integration of Cloud & on premise
Management Interface
Host
● Cloud
● Region (EC2) / Location (AZ)
● vCenter cluster
● KVM hypervisor
Capacity Management
● Scheduling policies
● Accounting
● Quotas
● Capacity allocation
Usage Interface
API
● VM template catalog
● VM operations
Workflow
● Context
● OneFlow
● OneGate

4. Adding EC2 to your Cloud
Requirements
● Access Credentials
● Enable Amazon EC2 drivers
● Plan the maximum capacity to offload and regions to use
/etc/one/ec2_driver.conf
/etc/one/sched.conf

5. Adding EC2-enabled VM Templates
Requirements
● AMI-ID representing the VM in each target region
● Relevant EC2 attributes:
○ INSTANCETYPE
○ KEYPAIR
○ USERDATA
○ SECURITYGROUPS
virtual machine template
○ ELASTICIP
○ TAGS
○ AVAILABILITYZONE
○ ...
Also in the very same VM template:
● Definitions for different EC2 regions (e.g. keypairs, sg…)
● Definitions for other cloud providers
● A “on-premise” definition

6. Using EC2-enabled VM Templates
Interfaces
● Same API, CLI and Sunstone interface
● Some operations are not available (compared to KVM)
● Information obtained through monitoring:
AWS_IMAGE_ID : ami-668f1e70
AWS_INSTANCE_TYPE : t1.micro
AWS_KEY_NAME : ruben
AWS_PRIVATE_DNS_NAME: ip-10-86-138-54.ec2.internal
AWS_PRIVATE_IP_ADDRESS: 10.86.138.54
AWS_PUBLIC_DNS_NAME : ec2-54-237-169-132.compute-1.amazonaws.com
AWS_PUBLIC_IP_ADDRESS: 54.237.169.132
AWS_SECURITY_GROUPS : sg-8e45a3e7

7. Using EC2-enabled VM Templates
Context in EC2:
● curl http://169.254.169.254/latest/user-data
● User inputs
● SSH keys
● START_SCRIPT
● Can be processed through context packages
Existing EC2 instances:
● Monitor together with the AWS region
● Imported as Wild VMs
● Can be controlled through OpenNebula interfaces & APIs

8. EC2 Driver. New in 5.4
● Improved driver (e.g. life-cycle and monitoring)
● Configuration moved to the host

9. Adding Microsoft Azure to your Cloud
Requirements
● Access Credentials
● Enable Azure drivers
● Plan the maximum capacity to offload and regions to use
/etc/one/az_driver.conf
/etc/one/az_driver.default
/etc/one/sched.conf

10. Adding Azure-enabled VM Templates
Requirements
● Same principle as in Amazon EC2
● Specific VM template attributes:
○ INSTANCE_TYPE
○ IMAGE
○ VM_USER
○ VM_PASSWORD
virtual machine template
○ STORAGE_ACCOUNT
○ WIN_RM
○ CLOUD_SERVICE
○ TCP_ENDPOINTS
○ ...

11. THANKS!
OpenNebulaConf 2017 US
5th
edition