Hi, from kolla side I've started the work. In kolla images [0] for now only placement is separated to an independent image, only source is code is being installed, binary still uses nova-placement packages until a binary package exists from the debian and centos families.
In kolla-ansible [1] placement service has been moved into a separate role applied just before nova. Things missing for now: - Binary packages from distributions - Run db syncs as there is not command for that yet in the master branch - Apply upgrade process for db changes [0] https://review.openstack.org/#/c/613589/ [1] https://review.openstack.org/#/c/613629/ Regards El mié., 31 oct. 2018 a las 10:19, Lee Yarwood (<lyarw...@redhat.com>) escribió: > On 30-10-18 14:29:12, Emilien Macchi wrote: > > On the TripleO side, it sounds like Lee Yarwood is taking the lead with a > > first commit in puppet-placement: > > https://review.openstack.org/#/c/604182/ > > > > Lee, can you confirm that you and your team are working on it for Stein > > cycle? > > ACK, just getting back online after being out for three weeks but still > planning on getting everything in place by the original M2 goal we > agreed to at PTG. I'll try to post more details by the end of the week. > > Cheers, > > Lee > > > On Thu, Oct 25, 2018 at 1: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/ > > -- > Lee Yarwood A5D1 9385 88CB 7E5F BE64 6618 BCA6 6E33 F672 > 2D76 > __________________________________________________________________________ > 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 >
__________________________________________________________________________ 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
