Replacing vCloud with OpenNebula
0 likes694 views
The document outlines Haufe Group's implementation of OpenNebula for their virtualization orchestration, detailing the company's software development and current infrastructure challenges with VMware products. OpenNebula offers benefits such as reduced license costs and increased customization, although it currently lacks certain network virtualization features. The planned architecture aims to improve deployment ease and provide a unified interface for public cloud use, enhancing the workflow for software testing and resource management.
Replacing vCloud with OpenNebula
- 1. OpenNebula @ Haufe Group A somewhat unusual Use-case 26th of September 2019 | Techday@NTS, Vienna
- 2. PATRICK MARTINS SYSTEMS ENGINEER JENS LANGHAMMER LINUX DEVOPS PROFESSIONAL
- 3. Table of Contents • What we do, who we are • Current Situation • Why OpenNebula • What OpenNebula is missing • Planned Architecture • Public Cloud
- 4. What we do at Haufe • We make software (e.g. tax, finance, payroll) • A wide range of Products • From Web-Applications over mobile Apps to Desktop Applications • Many small, autonomous teams • Teams can consume central Services, but don’t have to
- 5. Haufe, NTS and OpenNebula
- 6. Tardis • Project Owner à Alexander Keller • Technical Lead à Jens Langhammer • Patrick Martins à external Support • 3 planed releases Future-proof virtualisation orchestration for software testing with commercial support
- 7. Current Situation – Software Testing • vCloud Director SP • vSphere 6.5 • 14 Hosts, 128 Cores, 2 TB RAM • 650+ VMs • Interactions • Testers create new VMs via the Portal • VMs are created via the API • Use-cases • Automated Builds • Support Agents replicating Client Setups
- 8. Current Workflow • vApps to ”containerise” Images • Single Client VM • Server + Client VM • Network is always fenced • About 1500 pre-built Images • Base Images for all sorts of Operating Systems • Automated builds create Images
- 9. Issues • Unknown Future of vCloud Director • High Maintenance effort • Little Customisation • High License costs • Locked into the VMware-ecosystem
- 10. How OpenNebula helps us • Fewer License Costs • Hosts running Ubuntu • Support through NTS • Open-Source, thus customizable • Abstraction • Workloads might need vSphere for Support • Possibility to use Public Clouds • Easier Maintenance
- 11. What OpenNebula is missing • Fully automated Network Virtualization • Higher Quality Console • Lifecycle for OpenNebula Services • VM Leases OpenNebula „Fund a feature“
- 12. Planned Architecture Virtual Cloud Infrastructure IaaS Cloud Stack Bare-Metal-Deployment & Life-Cycle-Management Config-Management (SDI) Automation Infrastructure Physical Hardware Hypervisor Storage Networking Physical Infrastructure NFS 802.1Q VLAN VXLAN (OpenNebula Services Provider)
- 13. Public Cloud Beware the Buzzwords
- 14. Current Situation – Public Cloud • AWS Accounts per Project • Default Subnets, Security Groups, etc • No ”hard” guidelines – Teams can do what they want
- 17. Goal • Make it easier to deploy • Provide a single Interface • Prevent Users from abuse • Familiar Environment
- 18. Enter Watson… • Simplify AWS Network Selection • Simplify AWS EC2 Authentication • Simplify Domain Join
- 20. Behind the scenes • Set SUBNETID • Set SECURITYGROUPIDS • Set Name Tag based on OpenNebula Name • Linux • Set SSH-Key based on User’s SSH-Key • Windows • Set Random Password • Domain Join (the complicated way)
- 21. Demo Time!