WHAT WE DO WITH OPENNEBULA
AND WHY WE DO IT
{
"firstName": "Sebastian",
"lastName": "Mangelkramer",
"jobDescription": "Technology Manager",
"datacenterSince": 2001,
"motivation": "Relax, we care",
"loves": ["nts", "dc", "opennebula"],
"age": "36",
}
HOW A CLASSIC DATACENTER
LOOKS LIKE
IMAGINE
WHAT DO YOU THINK IS MISSING
(OR THE CHALLENGE)?
NO SELF SERVICE
NO API
NO AUTOMATION
WHAT DOES THE USER WANT?
A useable server or VM.
“Actually“, simple – isn‘t it?
NOT MUCH, ACTUALLY
WHAT'S THE CHALLENGE?
THIS (OR SIMILAR) IS HOW ONE CAN IMAGINE A DATA CENTER
Complex, a lot of systems (parts), bare base components
Analogy: car to server/VM:
“All I want to do is drive!“
There is often a lack of automation and
simpler, faster deployment.
What was that with „on-demand“
(or self-service and API`s in the age of the cloud)?
IN BRIEF
WHAT DO WE NEED TO
CHANGE?
THE CONSUMPTION MODEL!
Abstraction / Orchestration (IaaS)
In-Guest Automation – „ready VM“
Integration via Hooks
VM Workloads / DevOps / CI-CD
Virtual Datacenter (VDC)
cloud.company.com
• Self-Service • API
Consume:
• ready VM
O n - P r e m
Governance:
• Ressources
• Location
• Cost
Central Auth via AD
• Auth
• User / Group
VDC = How IT is consumed
• Shares and slices IT
Make IT Infrastructure „invisible“
• Abstract IT Infrastructure
• „VM everywhere“
VM
Catalog
Content Library
• VM Templates
Realize VM
1
Automate
2
Present
3
LETS DIG A BIT DEEPER
IMAGINE THE PROCESS:
„NEW VM“
OpenNebula Integration Automation PresentationProvider
Request new VM
- Self Service
- API
- CLI
• Image Mapping
$TEMPLATE
- VMware
- KVM
- AWS
- Azure
• Hooks
- IPAM
- CMDB
- Backup
- Monitoring
- DNS
- …
• Automate OS
- IP / Hostname
- Credentials
- AD Join
- Scripts
- …
• VDC / Portal
• API
• Realize
Ready
VM1
2
3
4
• VMware vSphere
• Linux KVM
• AWS
• Azure
PROCESS : „NEW VM“
SOME INSIGHTS INTO OUR
PROJECTS
USE CASE #1
Simply Deploy VMs
Technologies / Components:
OpenNebula + VMware
Power Shell Domainjoin
BEFORE OPENNEBULA
create VM
install
OS
config
OS
- Login to vSphere
- Create emtpy VM
- Configure VM
- Mount ISO to VM
- Start VM
- Go to VM console
- OS Installation
Configure:
- Network
- Hostname
- (domain join)
…
takes about 15 minutes
WITH OPEN NEBULA
Instantiate VM
- Login to Open Nebula
- Choose Template
- Press „Instantiate“
Takes about 1-2 minutes to the ready VM!
USE CASE #2
CI / CD PIPELINE
Technologies / Components:
OpenNebula + vCenter + MS Azure
Terraform
Ansible & AWX
Jenkins
Git
FROM WORKSHOP...
IT WORKS – THANKS TO OPENNEBULA HOOKS
... TO THE FINAL SOLUTION
SHORT LIVE-DEMO IS POSSIBLE J
USE CASE #3
REPLACE VCLOUD
Technologies / Components:
• OpenNebula + KVM
• Many Hooks (ServiceNow, CheckMK,...)
• VDC /User Provisioning via XMLRPC
• VXLAN with BGP-EVPN for Fenced Nets
• Extended Network Model for OpenNebula (VXLAN EVPN)
• Some really interesting “Fund a Feature“ Requests
• A 100% Replacement of VCD with ONE + KVM (!)
OUTCOMES USE-CASE #3
WHY ?
WELL..., THERE ARE MANY REASONS
LACK OF COMPLEXITY
ABILITY TO INTEGRATE
MATURITY
BUT: THERE ARE OTHER REASONS
CAN YOU IMAGINE?
EXCELLENT PARTNERS
THANK YOU, OPENNEBULA TEAM!!!
OUR (ONE) A-TEAM
Patrick Martins Florian Mandlmeier Phlilipp Kainz
OTHER STUFF
https://github.com/smangelkramer/one-kubesprayhttps://github.com/smangelkramer/one-graphite
NTS: What We Do With OpenNebula - and Why We Do It

NTS: What We Do With OpenNebula - and Why We Do It