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.

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

129 views

Published on

How and what we do with OpenNebula to enable our customers for a completely new way how it is consumed in a modern, service orientated IT. We will also talk about the question, why we have chosen OpenNebula and how deep is the level - and ability - of integration of the NTS CAPTAIN into existing 2nd and 3rd party tools like IPAM, CMDBs, backup, monitoring, approval processes and much more...

Published in: Software
  • Be the first to comment

  • Be the first to like this

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

  1. 1. WHAT WE DO WITH OPENNEBULA AND WHY WE DO IT
  2. 2. { "firstName": "Sebastian", "lastName": "Mangelkramer", "jobDescription": "Technology Manager", "datacenterSince": 2001, "motivation": "Relax, we care", "loves": ["nts", "dc", "opennebula"], "age": "36", }
  3. 3. HOW A CLASSIC DATACENTER LOOKS LIKE IMAGINE
  4. 4. WHAT DO YOU THINK IS MISSING (OR THE CHALLENGE)?
  5. 5. NO SELF SERVICE
  6. 6. NO API
  7. 7. NO AUTOMATION
  8. 8. WHAT DOES THE USER WANT?
  9. 9. A useable server or VM. “Actually“, simple – isn‘t it? NOT MUCH, ACTUALLY
  10. 10. WHAT'S THE CHALLENGE?
  11. 11. 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!“
  12. 12. 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
  13. 13. WHAT DO WE NEED TO CHANGE?
  14. 14. THE CONSUMPTION MODEL!
  15. 15. 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
  16. 16. LETS DIG A BIT DEEPER IMAGINE THE PROCESS: „NEW VM“
  17. 17. 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“
  18. 18. SOME INSIGHTS INTO OUR PROJECTS
  19. 19. USE CASE #1 Simply Deploy VMs Technologies / Components: OpenNebula + VMware Power Shell Domainjoin
  20. 20. 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
  21. 21. WITH OPEN NEBULA Instantiate VM - Login to Open Nebula - Choose Template - Press „Instantiate“ Takes about 1-2 minutes to the ready VM!
  22. 22. USE CASE #2 CI / CD PIPELINE Technologies / Components: OpenNebula + vCenter + MS Azure Terraform Ansible & AWX Jenkins Git
  23. 23. FROM WORKSHOP...
  24. 24. IT WORKS – THANKS TO OPENNEBULA HOOKS ... TO THE FINAL SOLUTION SHORT LIVE-DEMO IS POSSIBLE J
  25. 25. 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
  26. 26. • 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
  27. 27. WHY ?
  28. 28. WELL..., THERE ARE MANY REASONS
  29. 29. LACK OF COMPLEXITY
  30. 30. ABILITY TO INTEGRATE
  31. 31. MATURITY
  32. 32. BUT: THERE ARE OTHER REASONS CAN YOU IMAGINE?
  33. 33. EXCELLENT PARTNERS THANK YOU, OPENNEBULA TEAM!!!
  34. 34. OUR (ONE) A-TEAM Patrick Martins Florian Mandlmeier Phlilipp Kainz
  35. 35. OTHER STUFF https://github.com/smangelkramer/one-kubesprayhttps://github.com/smangelkramer/one-graphite

×