[openstack-dev] [kolla] PTG Summary

Adam Spiers aspiers at suse.com
Thu Mar 8 15:50:12 UTC 2018

Paul Bourke <paul.bourke at oracle.com> wrote:
>Hi all,
>Here's my summary of the various topics we discussed during the PTG. 
>There were one or two I had to step out for but hopefully this serves 
>as an overall recap. Please refer to the main etherpad[0] for more 
>details and links to the session specific pads.


>self health check support
>* This had some crossover with the monitoring discussion.
>* Kolla has some checks in the form of our 'sanity checks', but these 
>are underutilised and not implemented for every service. Tempest or 
>rally would be a better fit here.
>* Remove the sanity check code from kolla-ansible - it's not fit for 
>purpose and our assumption is noone is using it.
>* Make contact with the self healing SIG, and see if we can help here. 
>They may have recommendations for us.
>* Make a spec for this.


Would be great to collaborate!  As the SIG is still new we don't have
regular meetings set up yet, but please join #openstack-self-healing
on IRC, and you can mail the openstack-sigs list with [self-healing]
in the subject.

>Implement rolling upgrade for all core projects
>* Started by defining the 'terms of engagement', i.e. what do we mean 
>by rolling upgrade in kolla, what we currently have vs. what projects 
>support, etc.
>* There are two efforts under way here, 1) supporting online upgrade 
>for all core projects that support it, 2) supporting FFU(offline) 
>upgrade in Kolla.
>* lujinluo is working on a way to do online FFU in Kolla.
>* Testing - we need gates to test upgrade.
>* Finish implementation of rolling upgrade for all projects that 
>support it in Rocky
>* Improve documentation around this and upgrades in general for Kolla
>* Spec in Rocky for FFU and associated efforts
>* Begin looking at what would be required for upgrade gates in Kolla

Yes, a spec or other docs nailing down exactly what is meant by
rolling upgrade and FFU upgrade would be a great help.  I was in the
FFU session in Dublin and it felt to me like not everyone was on the
same page yet regarding the precise definitions, making it difficult
for all projects to move forward together in a coherent fashion.

More information about the OpenStack-dev mailing list