.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?
• 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 overall Linux management and 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"
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"
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!
is focused on providing customer solutions to automate application environments. ! • From a high level, the DevOps Automation Service is responsible for helping to provide architecture recommendations based on Rackspace best known methods:! • automating customer application environments with code" • supporting customers with changes necessary to support their application" • providing monitoring and application insight" • providing testing to configuration changes via internal continuous integration testing pipelines."
Customer Scenario was:! • Wanted to split their private cloud resources in half, isolating two core parts of the company." • Since OpenStack is ‘special’ it only made sense to create a playbook to automate all steps needed to accomplish this." • Outcome of that was: https://github.com/wbentley15/openstack-tenant-isolation"
Needed the ability to deploy Hadoop clusters quickly on their bare metal servers." • To accomplish this RAX created playbooks to accomplish this for our customer (of course selfish intentions existed too :D)." • Outcome of that was the ability to deploy Hadoop stacks on the cloud, OnMetal (RAX) public cloud and bare metal gear: https://github.com/rackerlabs/ansible-hadoop"
• 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
wbentley15
cscengineer
nobutomurata
zozotech
aeonpeople
sh_fk2
edeandrea
ninomiya_ii
tatsutaka
brainpadpr
musubi
yanzm
shiba_8ro
mkilby
retrage
cassininazir
jonoalderson
jlugia
codingconduct
trishagee
productmarketing
tessaabrams
tmiket
thekraken
sferik
![17 www.rackspace.com Q&A Session Twitter: @djstayflypro Email: [email protected]](https://files.speakerdeck.com/presentations/d2e7a3d926b0498581d3126ec7373451/slide_16.jpg){kind=link}
