Re: [openstack-dev] [tripleo][openstack-ansible][nova][placement] Owners needed for placement extraction upgrade deployment tooling
On Wed, 31 Oct 2018, Eduardo Gonzalez wrote: - Run db syncs as there is not command for that yet in the master branch - Apply upgrade process for db changes The placement-side pieces for this are nearly ready, see the stack beginning at https://review.openstack.org/#/c/611441/ -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent__ 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
Re: [openstack-dev] [tripleo][openstack-ansible][nova][placement] Owners needed for placement extraction upgrade deployment tooling
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 () 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 > 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
Re: [openstack-dev] [tripleo][openstack-ansible][nova][placement] Owners needed for placement extraction upgrade deployment tooling
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 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 signature.asc Description: PGP signature __ 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
Re: [openstack-dev] [tripleo][openstack-ansible][nova][placement] Owners needed for placement extraction upgrade deployment tooling
On Tue, 30 Oct 2018, Mohammed Naser wrote: We spoke about this today in the OpenStack Ansible meeting, we've come up with the following steps: Great! Thank you, Guilherme, and Lee very much. 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 Makes sense. 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? :) The upgrade-nova script in https://review.openstack.org/#/c/604454/ has been written to make it pretty clear what each of the steps mean. With luck those steps can translate to both the ansible and tripleo environments. Please feel free to add me to any of the reviews and come calling in #openstack-placement with questions if there are any. -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent__ 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
Re: [openstack-dev] [tripleo][openstack-ansible][nova][placement] Owners needed for placement extraction upgrade deployment tooling
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? On Thu, Oct 25, 2018 at 1:34 PM Matt Riedemann 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 > -- Emilien Macchi __ 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
Re: [openstack-dev] [tripleo][openstack-ansible][nova][placement] Owners needed for placement extraction upgrade deployment tooling
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 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
