On Wed, Dec 4, 2013 at 3:30 PM, Michael DeHaan <[email protected]>wrote:
> So we have some content to automate OpenStack here if you have not already > seen it: > > https://github.com/ansible/ansible-redhat-openstack > > As far as best practices, I'd recommend > > github.com/ansible/ansible-examples for learning usual tips and also the > "Best Practices" and "Roles" sections of the docs. > > Looks like a lot of your content is already pretty good though! > > I won't say they are neccessarily "best possible OpenStack toplogy" so > much, just some content examples -- which I think is not exactly what you > were looking for. > I definitely did look at the ansible-redhat-openstack playbook and I think I borrowed a couple of things. :) No swift stuff there though. I do like Lorin's openstack modules: https://github.com/lorin/openstack-ansible-modules especially in terms of setting up keystone versus copying and running a script to create endpoints and such. Thanks, Curtis. > > Definitely welcome others to share what they've done too :) > > > > > > On Wed, Dec 4, 2013 at 1:51 PM, Curtis <[email protected]> wrote: > >> Hi, >> >> I just wanted to mention that I have been working on an Ansible playbook >> to deploy OpenStack Swift Object Storage (Havana version) on multiple >> virtual machines. >> >> The repo can be found here: https://github.com/curtisgithub/swiftacular >> >> Right now it deploys 7 vagrant based virtual machines with things like >> SSL enabled Keystone, an SSL termination server for the Swift Proxy, and is >> using a replication network which is a new feature of OpenStack Swift >> Havana. There is a README in the git repo that describes a bit more. >> >> I'm still working on Ansible and OpenStack best practices, so if anyone >> has any tips, sees anything I'm doing wrong, do let me know so that I can >> figure that kind of thing out. >> >> I'm finding that on the surface things like OpenStack, Puppet, Ansible >> are generally straight forward, but once you get into them it's hard to >> decipher the best way to do things, whether that means "best practices" or >> "generally accepted way of doing things" or what have you. :) >> >> Thanks for any input, >> Curtis. >> >> PS. delegate_to was super helpful. >> >> -- >> Twitter: @serverascode >> Blog: serverascode.com >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Ansible Project" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > Michael DeHaan <[email protected]> > CTO, AnsibleWorks, Inc. > http://www.ansibleworks.com/ > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- Twitter: @serverascode Blog: serverascode.com -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
