OpenNebulaconf2017US: Configuration management with OpenNebula and Ansible by Jaime Melis, OpenNebula
1 like821 views
The document discusses the integration of OpenNebula with Ansible for infrastructure management, highlighting features like virtual machine deployment, lifecycle management, and application configuration. OpenNebula provides IaaS capabilities while Ansible aids in deploying and maintaining applications, utilizing dynamic inventory to streamline operations. The goal is to execute Ansible playbooks based on the state and metadata from OpenNebula.
OpenNebulaconf2017US: Configuration management with OpenNebula and Ansible by Jaime Melis, OpenNebula
- 1. Jaime Melis OpenNebula Systems Infrastructure Engineer @j_melis [email protected] OpenNebula and Ansible
- 3. IaaS and Configuration Management Hypervisor Infrastructure ● Capacity ● Networking ● Disk Images ● Life-cycle Management Runtime ● System configuration ● Application Life-cycle ● Configuration changes VM
- 4. OpenNebula So, what can you do with OpenNebula alone?
- 5. OpenNebula Contextualization Virtual Machine ISO Image Network Scripts Create Users Swap Hostname Grow Disk PCI Devices SSH Key
- 6. Base Image
- 7. Start Script
- 8. Capacity and User Inputs
- 9. OpenNebula Iaas ● Deploys the VM ● Bootstraps VM / OS (and even the Application) ● VMs are black boxes … OpenNebula doesn't care about the Application running inside
- 10. Ansible deploys and evolves Apps ● Evolves VMs / Apps ● Application aware ● Becoming a standard ● Deploy and maintain Application ● Make changes to the running Application / OS
- 11. Goal Run Ansible playbooks based on OpenNebula state and metadata
- 12. Ansible Dynamic Inventory ● Ruby OCA (XML-RPC) ○ onevm list ⇒ Extract VM state ● Get the data (User - Inputs) ● Run Ansible Playbooks ansible-playbook -i inventory.rb site.yml
- 13. Inventory ● JSON format ● Includes all VM information ● READY = YES ● Written in Ruby (OCA) ● The Label is the Ansible Role ● The User Input 'ANSIBLE' is also the Ansible Role
- 14. Demo
- 15. Orchestrator