.ASP developer and transitioned into supporting web-based applications. The bulk of my time was spent providing production support as an on-call engineer. Who Am I?
Automation Flexible • In early 2014, Rackspace embarked on the journey of developing a RPC version to move from the OpenStack release of Havana onto Icehouse! • Looking to implement improvements gained from the many lessons learned! • New reference architecture had to deliver these 4 core principles:"
• Creating playbooks is highly accessible for developers! • Other groups in Rackspace already using Ansible, and Rackspace has a good relationship with them! • Existing Ansible modules for OpenStack! • Ease of use in configuring hosts and containers! • Only SSH and Python required on the target device, no clients/agents! • Components and configurations can be upgraded or modified in isolation or combination"
• Ansible’s goal first and foremost is simplicity and maximum ease of use • Code is written in Python • Playbooks are written in the YAML format • Clearly defined best practices
deploy the OpenStack Private Cloud, it was broken down into three main playbooks:! • ansible-playbook -e @/etc/rpc_deploy/user_variables.yml playbooks/setup/host-setup.yml! • ansible-playbook -e @/etc/rpc_deploy/user_variables.yml playbooks/infrastructure/haproxy-install.yml (optional)! • ansible-playbook -e @/etc/rpc_deploy/user_variables.yml playbooks/infrastructure/infrastructure- setup.yml! • ansible-playbook -e @/etc/rpc_deploy/user_variables.yml playbooks/openstack/openstack-setup.yml ! All playbooks are dependent on two configuration files:! • rpc_user_config.yml" • user_variables.yml"
Problem Decided to build some playbooks to handle all the pre-implementation work! • Deploy locally; using Vagrant, VirtualBox and of course…Ansible! • git clone --recursive https://github.com/wbentley15/vagrant-rpcv901_deploy.git" • git clone --recursive https://github.com/wbentley15/vagrant-rpcv901.git" • Deploy on Rackspace Public Cloud; solely using Ansible!
the community voted to accept our playbooks as a Stackforge repository, making them the basis of Ansible support for OpenStack going forward! • https://review.openstack.org/#/c/132703 • Community Page: https://review.openstack.org/#/admin/projects/stackforge/os-ansible-deployment • Issues: https://bugs.launchpad.net/~openstack-ansible • IRC on Freenode: #openstack-ansible • Code Location: https://github.com/stackforge/os-ansible-deployment This means a lot to Rackspace and opens up the door for community contribution!