[Openstack-operators] Moving from distro packages to containers (or virtualenvs...)
jesse.pretorius at gmail.com
Fri May 13 22:15:26 UTC 2016
On 13 May 2016 at 19:59, Joshua Harlow <harlowja at fastmail.com> wrote:
> So I guess its like the following (correct me if I am wrong):
> 1. Sets up LXC containers from common base on deployment hosts (ansible
> here to do this)
> 2. Installs things into those containers (virtualenvs, packages, git
> repos, other ... more ansible)
> 3. Connects all the things together (more more ansible).
> 4. Decommissions existing container (if it exists) and replaces with new
> container (more more more ansible).
> 5. <<profit>>
As OpenStack-Ansible treats the LXC containers like hosts (this is why OSA
supports deploying to LXC machine containers and to VM's or normal hosts)
we don't replace containers - we simply deploy the new venv into a new
folder, reconfigure, then restart the service to use the new venv.
To speed things up in large environments we pre-build the venvs on a repo
server, then all hosts or containers grab them from the repo server
The mechanisms we use allow deployers to customise the packages built into
the venvs (you might need an extra driver in the neutron/cinder venvs, for
instance) and allow the OpenStack services to build directly from any git
source (this means you can maintain your own fork with all the fixes you
need, if you want to).
With OpenStack-Ansible you're also not forced to commit to the integrated
build. Each service role is broken out into its own repository, so you're
able to write your own Ansible playbooks to consume the roles which setup
the services in any way that pleases you.
The advantage in our case of using the LXC containers is that if something
ends up broken somehow in the binary packages (this hasn't happened yet in
my experience) you're able to simply blow away the container and rebuild it.
I hope this helps. Feel free to ping me any more questions.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-operators