Hi there: We spoke about this today in the OpenStack Ansible meeting, we've come up with the following steps:
1) Create a role for placement which will be called `os_placement` located in `openstack/openstack-ansible-os_placement` 2) Integrate that role with the OSA master and stop using the built-in placement service 3) Update the playbooks to handle upgrades and verify using our periodic upgrade jobs For #1, Guilherme from the OSA team will be taking care of creating the role initially, I'm hoping that maybe we can get it done sometime this week. I think it'll probably take another week to integrate it into the main repo. The difficult task really comes in the upgrade jobs, I really hope that we can get some help on this as this probably puts a bit of a load already on Guilherme, so anyone up to look into that part when the first 2 are completed? :) Thanks, Mohammed On Thu, Oct 25, 2018 at 7:34 PM Matt Riedemann <mriede...@gmail.com> wrote: > > Hello OSA/TripleO people, > > A plan/checklist was put in place at the Stein PTG for extracting > placement from nova [1]. The first item in that list is done in grenade > [2], which is the devstack-based upgrade project in the integrated gate. > That should serve as a template for the necessary upgrade steps in > deployment projects. The related devstack change for extracted placement > on the master branch (Stein) is [3]. Note that change has some dependencies. > > The second point in the plan from the PTG was getting extracted > placement upgrade tooling support in a deployment project, notably > TripleO (and/or OpenStackAnsible). > > Given the grenade change is done and passing tests, TripleO/OSA should > be able to start coding up and testing an upgrade step when going from > Rocky to Stein. My question is who can we name as an owner in either > project to start this work? Because we really need to be starting this > as soon as possible to flush out any issues before they are too late to > correct in Stein. > > So if we have volunteers or better yet potential patches that I'm just > not aware of, please speak up here so we know who to contact about > status updates and if there are any questions with the upgrade. > > [1] > http://lists.openstack.org/pipermail/openstack-dev/2018-September/134541.html > [2] https://review.openstack.org/#/c/604454/ > [3] https://review.openstack.org/#/c/600162/ > > -- > > Thanks, > > Matt > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mna...@vexxhost.com W. http://vexxhost.com __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
