Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.
6 YEARS (+) OPENNEBULA
LESSONS LEARNED
{
"firstName": "Sebastian",
"lastName": "Mangelkramer",
"jobDescription": "Technology Manager",
"datacenterSince": 2001,
"...
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: ca...
There is often a lack of automation and
simpler, faster deployment.
What was that with „on-demand“
(or self-service and AP...
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
Vi...
LETS DIG A BIT DEEPER
IMAGINE THE PROCESS:
„NEW VM“
OpenNebula Integration Automation PresentationProvider
Request new VM
- Self Service
- API
- CLI
• Image Mapping
$TEMPLATE...
WHAT WE DO WITH ONE
Enable our customers with solutions
IN BRIEF
Extend OpenNebula (Drivers, Hooks, BestPractice)
IN BRIEF
https://github.com/smangelkramer/one-
kubespray
https://github.c...
Support the Project and the Community
IN BRIEF
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!!!
LESSONS LEARNED #1
THINK ABOUT SOLUTIONS
NOT INFRASTRUCTURE
OpenNebula abstracts the Infrastructure
and let you focus on y...
LESSONS LEARNED #2
CHANGE THE
CONSUMPTION MODEL
Encourage yourself to integrate this new
model into your processes and get...
LESSONS LEARNED #3
IT Automation mostly starts at
the VM deployment process
Open Nebula is the perfect starter drug for
au...
LESSONS LEARNED #4
OFTEN THERE IS NO „ONE“
SOLUTION.
You HAD TO mix several OSS f.e. like Jenkins,
Ansible,... to build up...
VOICE OF THE CUSTOMER
• XMLRPC – Customers like RestAPIs
• PRICE – to cheap for Enterprises (?)
• VAULT – password safe in...
OpenNebulaConf2019 - 6 years (+) OpenNebula - Lessons learned - Sebastian Mangelkramer and Florian Mandlmeier - NTS
OpenNebulaConf2019 - 6 years (+) OpenNebula - Lessons learned - Sebastian Mangelkramer and Florian Mandlmeier - NTS
OpenNebulaConf2019 - 6 years (+) OpenNebula - Lessons learned - Sebastian Mangelkramer and Florian Mandlmeier - NTS
OpenNebulaConf2019 - 6 years (+) OpenNebula - Lessons learned - Sebastian Mangelkramer and Florian Mandlmeier - NTS
Nächste SlideShare
Wird geladen in …5
×

OpenNebulaConf2019 - 6 years (+) OpenNebula - Lessons learned - Sebastian Mangelkramer and Florian Mandlmeier - NTS

64 Aufrufe

Veröffentlicht am

Insight into more than 6 years experience with OpenNebula from different perspectives: ISP & Datacenter Provider and Consultant / System Integrator
Lessons learned, "the dos and don'ts" and how we convince and enable customers with OpenNebula - and the NTS ecosystem.

Veröffentlicht in: Software
  • Als Erste(r) kommentieren

  • Gehören Sie zu den Ersten, denen das gefällt!

OpenNebulaConf2019 - 6 years (+) OpenNebula - Lessons learned - Sebastian Mangelkramer and Florian Mandlmeier - NTS

  1. 1. 6 YEARS (+) OPENNEBULA LESSONS LEARNED
  2. 2. { "firstName": "Sebastian", "lastName": "Mangelkramer", "jobDescription": "Technology Manager", "datacenterSince": 2001, "opennebulaSince": 2011, "motivation": "Relax, we care", "loves": ["nts", "dc", "opennebula"], "age": "36", } { "firstName": "Florian", "lastName": "Mandlmeier", "jobDescription": "Systems Engineer", "itAutomationSince": 2014, "motivation": "Relax, we care", "type": "lazy", "loves": ["automation", "nts", "opennebula"], "establishedIn": 1994, }
  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. WHAT WE DO WITH ONE
  19. 19. Enable our customers with solutions IN BRIEF
  20. 20. Extend OpenNebula (Drivers, Hooks, BestPractice) IN BRIEF https://github.com/smangelkramer/one- kubespray https://github.com/smangelkramer/one-graphite https://github.com/OpenNebula/one/issues/2161
  21. 21. Support the Project and the Community IN BRIEF
  22. 22. WHY ?
  23. 23. WELL..., THERE ARE MANY REASONS
  24. 24. LACK OF COMPLEXITY
  25. 25. ABILITY TO INTEGRATE
  26. 26. MATURITY
  27. 27. BUT: THERE ARE OTHER REASONS CAN YOU IMAGINE?
  28. 28. EXCELLENT PARTNERS THANK YOU, OPENNEBULA TEAM!!!
  29. 29. LESSONS LEARNED #1 THINK ABOUT SOLUTIONS NOT INFRASTRUCTURE OpenNebula abstracts the Infrastructure and let you focus on your needs
  30. 30. LESSONS LEARNED #2 CHANGE THE CONSUMPTION MODEL Encourage yourself to integrate this new model into your processes and get better. OpenNebula is „the ONE ring to rule them all“ (in regards of any IT infrastructure)
  31. 31. LESSONS LEARNED #3 IT Automation mostly starts at the VM deployment process Open Nebula is the perfect starter drug for automation because it‘s simple and powerful
  32. 32. LESSONS LEARNED #4 OFTEN THERE IS NO „ONE“ SOLUTION. You HAD TO mix several OSS f.e. like Jenkins, Ansible,... to build up a solution. This can be a bit complex and competitors has their own ecosystem... But you have the freedom of choice!
  33. 33. VOICE OF THE CUSTOMER • XMLRPC – Customers like RestAPIs • PRICE – to cheap for Enterprises (?) • VAULT – password safe in ONE • Storage vMotion for KVM • HOOKS – no „central“ management

×