[Openstack-operators] Moving from distro packages to containers (or virtualenvs...)
Matthew Thode
prometheanfire at gentoo.org
Fri May 13 19:51:45 UTC 2016
On 05/13/2016 01:59 PM, Joshua Harlow wrote:
> Matthew Thode wrote:
>> On 05/13/2016 12:48 PM, Joshua Harlow wrote:
>>>>> * Was/is kolla used or looked into? or something custom?
>>>>>
>>>> Openstack-ansible, which is Openstack big-tent. It used to be
>>>> os-ansible-deployment in stackforge, but we've removed the
>>>> rackspacisms.
>>>> I will say that openstack-ansible is one of the few that have been
>>>> doing upgrades reliably for a while, since at least Icehouse, maybe
>>>> further.
>>> Whats the connection between 'openstack-ansible' and 'kolla', is there
>>> any (or any in progress?)
>>>
>>
>> The main difference is that openstack-ansible uses more heavy weight
>> containers from a common base (ubuntu 14.04 currently, 16.04/cent
>> 'soon'), it then builds on top of that, uses python virtualenvs as well.
>> Kolla on the other hand creates the container images centrally and
>> ships them around.
>
> So I guess its like the following (correct me if I am wrong):
>
> openstack-ansible
> -----------------
>
> 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>>
>
More or less, we do in place upgrades, so long lived containers, but
could just as easily destroy and replace.
> kolla
> -----
>
> 1. Builds up (installing things and such) *docker* containers outside of
> deployment hosts (say inside jenkins) [not ansible]
> 2. Ships built up containers to *a* docker hub
> 3. Ansible then runs commands on deployment hosts to download image from
> docker hub
> 4. Connects all the things together (more ansible).
> 5. Decommissions existing container (if it exists) and replaces with new
> container (more more ansible).
> 6. <<profit>>
>
> Yes the above is highly simplistic, but just trying to get a feel for
> the different base steps here ;)
>
I think so? not sure as I don't work with kolla
>>
>> The other thing to note is that Kolla has not done a non-greenfield
>> upgrade as far as I know, I know it's on their roadmap though.
>>
--
-- Matthew Thode (prometheanfire)
More information about the OpenStack-operators
mailing list