Re: [openstack-dev] [tripleo] The Weekly Owl - 25th Edition
On Thu, 2018-08-02 at 13:30 -0400, Pradeep Kilambi wrote: > > > On Wed, Aug 1, 2018 at 6:06 PM Jill Rouleau wrote: > > On Tue, 2018-07-31 at 07:38 -0400, Pradeep Kilambi wrote: > > > > > > > > > On Mon, Jul 30, 2018 at 2:17 PM Jill Rouleau > > wrote: > > > > On Mon, 2018-07-30 at 11:35 -0400, Pradeep Kilambi wrote: > > > > > > > > > > > > > > > On Mon, Jul 30, 2018 at 10:42 AM Alex Schultz > .com > > > > > > > > > > wrote: > > > > > > On Mon, Jul 30, 2018 at 8:32 AM, Martin Magr > om> > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > On Tue, Jul 17, 2018 at 6:12 PM, Emilien Macchi > edha > > > > t.co > > > > > > m> wrote: > > > > > > >> > > > > > > >> Your fellow reporter took a break from writing, but is > > now > > > > back > > > > > > on his > > > > > > >> pen. > > > > > > >> > > > > > > >> Welcome to the twenty-fifth edition of a weekly update in > > > > TripleO > > > > > > world! > > > > > > >> The goal is to provide a short reading (less than 5 > > minutes) > > > > to > > > > > > learn > > > > > > >> what's new this week. > > > > > > >> Any contributions and feedback are welcome. > > > > > > >> Link to the previous version: > > > > > > >> http://lists.openstack.org/pipermail/openstack-dev/2018-J > > une/ > > > > 1314 > > > > > > 26.html > > > > > > >> > > > > > > >> +-+ > > > > > > >> | General announcements | > > > > > > >> +-+ > > > > > > >> > > > > > > >> +--> Rocky Milestone 3 is next week. After, any feature > > code > > > > will > > > > > > require > > > > > > >> Feature Freeze Exception (FFE), asked on the mailing- > > list. > > > > We'll > > > > > > enter a > > > > > > >> bug-fix only and stabilization period, until we can push > > the > > > > > > first stable > > > > > > >> version of Rocky. > > > > > > > > > > > > > > > > > > > > > Hey guys, > > > > > > > > > > > > > > I would like to ask for FFE for backup and restore, > > where we > > > > > > ended up > > > > > > > deciding where is the best place for the code base for > > this > > > > > > project (please > > > > > > > see [1] for details). We believe that B support for > > > > overcloud > > > > > > control > > > > > > > plane will be good addition to a rocky release, but we > > started > > > > > > with this > > > > > > > initiative quite late indeed. The final result should the > > > > support > > > > > > in > > > > > > > openstack client, where "openstack overcloud > > (backup|restore)" > > > > > > would work as > > > > > > > a charm. Thanks in advance for considering this feature. > > > > > > > > > > > > > > > > > > > Was there a blueprint/spec for this effort? Additionally do > > we > > > > have > > > > > > a > > > > > > list of the outstanding work required for this? If it's just > > > > these > > > > > > two > > > > > > playbooks, it might be ok for an FFE. But if there's > > additional > > > > > > tripleoclient related changes, I wouldn't necessarily feel > > > > > > comfortable > > > > > > with these unless we have a complete list of work. Just as > > a > > > > side > > > > > > note, I'm not sure putting these in tripleo-common is going > > to > > > > be > > > > > > the > > > > > > ideal place for this. > > > > > > > > Was it this review? https://review.openstack.org/#/c/582453/ > > > > > > > > For Stein we'll have an ansible role[0] and playbook repo[1] > > where > > > > these > > > > types of tasks should live. > > > > > > > > [0] https://github.com/openstack/ansible-role-openstack-operatio > > ns > > > > [1] https://review.openstack.org/#/c/583415/ > > > Thanks Jill! The issue is, we want to be able to backport this to > > > Queens once merged. With the new repos you're mentioning would > > this be > > > possible? If no, then this wont work for us unfortunately. > > > > > > > We wouldn't backport the new packages to Queens, however the repos > > will > > be on github and available to clone and use. This would be far > > preferable than adding them to tripleo-common so late in the rocky > > cycle > > then having to break them back out right away in stein. > > Understood. To extend this further, we will need to integrate these > into tripleoclient. That way a user can just run $ openstack overcloud > backup - and get all the data backendup instead of running the play > books manually. Would this be possible with keeping these in a > separate tripleo ansible repo? How do we currently handle undercloud > backup. Where do we currently keep those playbooks? > We're not currently providing backup playbooks, this is a new feature. So it would be great if there were spec we could organize around. Cedric is working on a patch for running ansible playbooks via tripleoclient that should help: https://review.openstack.org/#/c/586538 / > > > > > > > > > > > > > > > > > > > > > > > > > > Thanks Alex. For Rocky, if we can ship the playbooks with > > relevant > > > > > docs we should be good. We will integrated with client in > >
Re: [openstack-dev] [tripleo] The Weekly Owl - 25th Edition
On Wed, Aug 1, 2018 at 6:06 PM Jill Rouleau wrote: > On Tue, 2018-07-31 at 07:38 -0400, Pradeep Kilambi wrote: > > > > > > On Mon, Jul 30, 2018 at 2:17 PM Jill Rouleau wrote: > > > On Mon, 2018-07-30 at 11:35 -0400, Pradeep Kilambi wrote: > > > > > > > > > > > > On Mon, Jul 30, 2018 at 10:42 AM Alex Schultz > > > > > > > wrote: > > > > > On Mon, Jul 30, 2018 at 8:32 AM, Martin Magr > > > > > wrote: > > > > > > > > > > > > > > > > > > On Tue, Jul 17, 2018 at 6:12 PM, Emilien Macchi > > t.co > > > > > m> wrote: > > > > > >> > > > > > >> Your fellow reporter took a break from writing, but is now > > > back > > > > > on his > > > > > >> pen. > > > > > >> > > > > > >> Welcome to the twenty-fifth edition of a weekly update in > > > TripleO > > > > > world! > > > > > >> The goal is to provide a short reading (less than 5 minutes) > > > to > > > > > learn > > > > > >> what's new this week. > > > > > >> Any contributions and feedback are welcome. > > > > > >> Link to the previous version: > > > > > >> http://lists.openstack.org/pipermail/openstack-dev/2018-June/ > > > 1314 > > > > > 26.html > > > > > >> > > > > > >> +-+ > > > > > >> | General announcements | > > > > > >> +-+ > > > > > >> > > > > > >> +--> Rocky Milestone 3 is next week. After, any feature code > > > will > > > > > require > > > > > >> Feature Freeze Exception (FFE), asked on the mailing-list. > > > We'll > > > > > enter a > > > > > >> bug-fix only and stabilization period, until we can push the > > > > > first stable > > > > > >> version of Rocky. > > > > > > > > > > > > > > > > > > Hey guys, > > > > > > > > > > > > I would like to ask for FFE for backup and restore, where we > > > > > ended up > > > > > > deciding where is the best place for the code base for this > > > > > project (please > > > > > > see [1] for details). We believe that B support for > > > overcloud > > > > > control > > > > > > plane will be good addition to a rocky release, but we started > > > > > with this > > > > > > initiative quite late indeed. The final result should the > > > support > > > > > in > > > > > > openstack client, where "openstack overcloud (backup|restore)" > > > > > would work as > > > > > > a charm. Thanks in advance for considering this feature. > > > > > > > > > > > > > > > > Was there a blueprint/spec for this effort? Additionally do we > > > have > > > > > a > > > > > list of the outstanding work required for this? If it's just > > > these > > > > > two > > > > > playbooks, it might be ok for an FFE. But if there's additional > > > > > tripleoclient related changes, I wouldn't necessarily feel > > > > > comfortable > > > > > with these unless we have a complete list of work. Just as a > > > side > > > > > note, I'm not sure putting these in tripleo-common is going to > > > be > > > > > the > > > > > ideal place for this. > > > > > > Was it this review? https://review.openstack.org/#/c/582453/ > > > > > > For Stein we'll have an ansible role[0] and playbook repo[1] where > > > these > > > types of tasks should live. > > > > > > [0] https://github.com/openstack/ansible-role-openstack-operations > > > [1] https://review.openstack.org/#/c/583415/ > > Thanks Jill! The issue is, we want to be able to backport this to > > Queens once merged. With the new repos you're mentioning would this be > > possible? If no, then this wont work for us unfortunately. > > > > We wouldn't backport the new packages to Queens, however the repos will > be on github and available to clone and use. This would be far > preferable than adding them to tripleo-common so late in the rocky cycle > then having to break them back out right away in stein. > Understood. To extend this further, we will need to integrate these into tripleoclient. That way a user can just run $ openstack overcloud backup - and get all the data backendup instead of running the play books manually. Would this be possible with keeping these in a separate tripleo ansible repo? How do we currently handle undercloud backup. Where do we currently keep those playbooks? > > > > > > > > > > > > > > > > > > > Thanks Alex. For Rocky, if we can ship the playbooks with relevant > > > > docs we should be good. We will integrated with client in Stein > > > > release with restore logic included. Regarding putting tripleo- > > > common, > > > > we're open to suggestions. I think Dan just submitted the review > > > so we > > > > can get some eyes on the playbooks. Where do you suggest is better > > > > place for these instead? > > > > > > > > > > > > > > Thanks, > > > > > -Alex > > > > > > > > > > > Regards, > > > > > > Martin > > > > > > > > > > > > [1] https://review.openstack.org/#/c/582453/ > > > > > > > > > > > >> > > > > > >> +--> Next PTG will be in Denver, please propose topics: > > > > > >> https://etherpad.openstack.org/p/tripleoci-ptg-stein > > > > > >> +--> Multiple squads are currently brainstorming a framework > > > to > > > > >
Re: [openstack-dev] [tripleo] The Weekly Owl - 25th Edition
On Tue, 2018-07-31 at 07:38 -0400, Pradeep Kilambi wrote: > > > On Mon, Jul 30, 2018 at 2:17 PM Jill Rouleau wrote: > > On Mon, 2018-07-30 at 11:35 -0400, Pradeep Kilambi wrote: > > > > > > > > > On Mon, Jul 30, 2018 at 10:42 AM Alex Schultz > > > > > wrote: > > > > On Mon, Jul 30, 2018 at 8:32 AM, Martin Magr > > > > wrote: > > > > > > > > > > > > > > > On Tue, Jul 17, 2018 at 6:12 PM, Emilien Macchi > t.co > > > > m> wrote: > > > > >> > > > > >> Your fellow reporter took a break from writing, but is now > > back > > > > on his > > > > >> pen. > > > > >> > > > > >> Welcome to the twenty-fifth edition of a weekly update in > > TripleO > > > > world! > > > > >> The goal is to provide a short reading (less than 5 minutes) > > to > > > > learn > > > > >> what's new this week. > > > > >> Any contributions and feedback are welcome. > > > > >> Link to the previous version: > > > > >> http://lists.openstack.org/pipermail/openstack-dev/2018-June/ > > 1314 > > > > 26.html > > > > >> > > > > >> +-+ > > > > >> | General announcements | > > > > >> +-+ > > > > >> > > > > >> +--> Rocky Milestone 3 is next week. After, any feature code > > will > > > > require > > > > >> Feature Freeze Exception (FFE), asked on the mailing-list. > > We'll > > > > enter a > > > > >> bug-fix only and stabilization period, until we can push the > > > > first stable > > > > >> version of Rocky. > > > > > > > > > > > > > > > Hey guys, > > > > > > > > > > I would like to ask for FFE for backup and restore, where we > > > > ended up > > > > > deciding where is the best place for the code base for this > > > > project (please > > > > > see [1] for details). We believe that B support for > > overcloud > > > > control > > > > > plane will be good addition to a rocky release, but we started > > > > with this > > > > > initiative quite late indeed. The final result should the > > support > > > > in > > > > > openstack client, where "openstack overcloud (backup|restore)" > > > > would work as > > > > > a charm. Thanks in advance for considering this feature. > > > > > > > > > > > > > Was there a blueprint/spec for this effort? Additionally do we > > have > > > > a > > > > list of the outstanding work required for this? If it's just > > these > > > > two > > > > playbooks, it might be ok for an FFE. But if there's additional > > > > tripleoclient related changes, I wouldn't necessarily feel > > > > comfortable > > > > with these unless we have a complete list of work. Just as a > > side > > > > note, I'm not sure putting these in tripleo-common is going to > > be > > > > the > > > > ideal place for this. > > > > Was it this review? https://review.openstack.org/#/c/582453/ > > > > For Stein we'll have an ansible role[0] and playbook repo[1] where > > these > > types of tasks should live. > > > > [0] https://github.com/openstack/ansible-role-openstack-operations > > [1] https://review.openstack.org/#/c/583415/ > Thanks Jill! The issue is, we want to be able to backport this to > Queens once merged. With the new repos you're mentioning would this be > possible? If no, then this wont work for us unfortunately. > We wouldn't backport the new packages to Queens, however the repos will be on github and available to clone and use. This would be far preferable than adding them to tripleo-common so late in the rocky cycle then having to break them back out right away in stein. > > > > > > > > > > > > Thanks Alex. For Rocky, if we can ship the playbooks with relevant > > > docs we should be good. We will integrated with client in Stein > > > release with restore logic included. Regarding putting tripleo- > > common, > > > we're open to suggestions. I think Dan just submitted the review > > so we > > > can get some eyes on the playbooks. Where do you suggest is better > > > place for these instead? > > > > > > > > > > > Thanks, > > > > -Alex > > > > > > > > > Regards, > > > > > Martin > > > > > > > > > > [1] https://review.openstack.org/#/c/582453/ > > > > > > > > > >> > > > > >> +--> Next PTG will be in Denver, please propose topics: > > > > >> https://etherpad.openstack.org/p/tripleoci-ptg-stein > > > > >> +--> Multiple squads are currently brainstorming a framework > > to > > > > provide > > > > >> validations pre/post upgrades - stay in touch! > > > > >> > > > > >> +--+ > > > > >> | Continuous Integration | > > > > >> +--+ > > > > >> > > > > >> +--> Sprint theme: migration to Zuul v3 (More on > > > > >> https://trello.com/c/vyWXcKOB/841-sprint-16-goals) > > > > >> +--> Sagi is the rover and Chandan is the ruck. Please tell > > them > > > > any CI > > > > >> issue. > > > > >> +--> Promotion on master is 4 days, 0 days on Queens and Pike > > and > > > > 1 day on > > > > >> Ocata. > > > > >> +--> More: https://etherpad.openstack.org/p/tripleo-ci-squad- > > meet > > > > ing > > > > >> > > > > >> +-+ >
Re: [openstack-dev] [tripleo] The Weekly Owl - 25th Edition
On Mon, Jul 30, 2018 at 2:17 PM Jill Rouleau wrote: > On Mon, 2018-07-30 at 11:35 -0400, Pradeep Kilambi wrote: > > > > > > On Mon, Jul 30, 2018 at 10:42 AM Alex Schultz > > wrote: > > > On Mon, Jul 30, 2018 at 8:32 AM, Martin Magr > > > wrote: > > > > > > > > > > > > On Tue, Jul 17, 2018 at 6:12 PM, Emilien Macchi > > m> wrote: > > > >> > > > >> Your fellow reporter took a break from writing, but is now back > > > on his > > > >> pen. > > > >> > > > >> Welcome to the twenty-fifth edition of a weekly update in TripleO > > > world! > > > >> The goal is to provide a short reading (less than 5 minutes) to > > > learn > > > >> what's new this week. > > > >> Any contributions and feedback are welcome. > > > >> Link to the previous version: > > > >> http://lists.openstack.org/pipermail/openstack-dev/2018-June/1314 > > > 26.html > > > >> > > > >> +-+ > > > >> | General announcements | > > > >> +-+ > > > >> > > > >> +--> Rocky Milestone 3 is next week. After, any feature code will > > > require > > > >> Feature Freeze Exception (FFE), asked on the mailing-list. We'll > > > enter a > > > >> bug-fix only and stabilization period, until we can push the > > > first stable > > > >> version of Rocky. > > > > > > > > > > > > Hey guys, > > > > > > > > I would like to ask for FFE for backup and restore, where we > > > ended up > > > > deciding where is the best place for the code base for this > > > project (please > > > > see [1] for details). We believe that B support for overcloud > > > control > > > > plane will be good addition to a rocky release, but we started > > > with this > > > > initiative quite late indeed. The final result should the support > > > in > > > > openstack client, where "openstack overcloud (backup|restore)" > > > would work as > > > > a charm. Thanks in advance for considering this feature. > > > > > > > > > > Was there a blueprint/spec for this effort? Additionally do we have > > > a > > > list of the outstanding work required for this? If it's just these > > > two > > > playbooks, it might be ok for an FFE. But if there's additional > > > tripleoclient related changes, I wouldn't necessarily feel > > > comfortable > > > with these unless we have a complete list of work. Just as a side > > > note, I'm not sure putting these in tripleo-common is going to be > > > the > > > ideal place for this. > > Was it this review? https://review.openstack.org/#/c/582453/ > > For Stein we'll have an ansible role[0] and playbook repo[1] where these > types of tasks should live. > > [0] https://github.com/openstack/ansible-role-openstack-operations > [1] https://review.openstack.org/#/c/583415/ Thanks Jill! The issue is, we want to be able to backport this to Queens once merged. With the new repos you're mentioning would this be possible? If no, then this wont work for us unfortunately. > > > > > > Thanks Alex. For Rocky, if we can ship the playbooks with relevant > > docs we should be good. We will integrated with client in Stein > > release with restore logic included. Regarding putting tripleo-common, > > we're open to suggestions. I think Dan just submitted the review so we > > can get some eyes on the playbooks. Where do you suggest is better > > place for these instead? > > > > > > > > Thanks, > > > -Alex > > > > > > > Regards, > > > > Martin > > > > > > > > [1] https://review.openstack.org/#/c/582453/ > > > > > > > >> > > > >> +--> Next PTG will be in Denver, please propose topics: > > > >> https://etherpad.openstack.org/p/tripleoci-ptg-stein > > > >> +--> Multiple squads are currently brainstorming a framework to > > > provide > > > >> validations pre/post upgrades - stay in touch! > > > >> > > > >> +--+ > > > >> | Continuous Integration | > > > >> +--+ > > > >> > > > >> +--> Sprint theme: migration to Zuul v3 (More on > > > >> https://trello.com/c/vyWXcKOB/841-sprint-16-goals) > > > >> +--> Sagi is the rover and Chandan is the ruck. Please tell them > > > any CI > > > >> issue. > > > >> +--> Promotion on master is 4 days, 0 days on Queens and Pike and > > > 1 day on > > > >> Ocata. > > > >> +--> More: https://etherpad.openstack.org/p/tripleo-ci-squad-meet > > > ing > > > >> > > > >> +-+ > > > >> | Upgrades | > > > >> +-+ > > > >> > > > >> +--> Good progress on major upgrades workflow, need reviews! > > > >> +--> More: https://etherpad.openstack.org/p/tripleo-upgrade-squad > > > -status > > > >> > > > >> +---+ > > > >> | Containers | > > > >> +---+ > > > >> > > > >> +--> We switched python-tripleoclient to deploy containerized > > > undercloud > > > >> by default! > > > >> +--> Image prepare via workflow is still work in progress. > > > >> +--> More: > > > >> https://etherpad.openstack.org/p/tripleo-containers-squad-status > > > >> > > > >> +--+ > > > >> | config-download | > > > >>
Re: [openstack-dev] [tripleo] The Weekly Owl - 25th Edition
On Mon, 2018-07-30 at 11:35 -0400, Pradeep Kilambi wrote: > > > On Mon, Jul 30, 2018 at 10:42 AM Alex Schultz > wrote: > > On Mon, Jul 30, 2018 at 8:32 AM, Martin Magr > > wrote: > > > > > > > > > On Tue, Jul 17, 2018 at 6:12 PM, Emilien Macchi > m> wrote: > > >> > > >> Your fellow reporter took a break from writing, but is now back > > on his > > >> pen. > > >> > > >> Welcome to the twenty-fifth edition of a weekly update in TripleO > > world! > > >> The goal is to provide a short reading (less than 5 minutes) to > > learn > > >> what's new this week. > > >> Any contributions and feedback are welcome. > > >> Link to the previous version: > > >> http://lists.openstack.org/pipermail/openstack-dev/2018-June/1314 > > 26.html > > >> > > >> +-+ > > >> | General announcements | > > >> +-+ > > >> > > >> +--> Rocky Milestone 3 is next week. After, any feature code will > > require > > >> Feature Freeze Exception (FFE), asked on the mailing-list. We'll > > enter a > > >> bug-fix only and stabilization period, until we can push the > > first stable > > >> version of Rocky. > > > > > > > > > Hey guys, > > > > > > I would like to ask for FFE for backup and restore, where we > > ended up > > > deciding where is the best place for the code base for this > > project (please > > > see [1] for details). We believe that B support for overcloud > > control > > > plane will be good addition to a rocky release, but we started > > with this > > > initiative quite late indeed. The final result should the support > > in > > > openstack client, where "openstack overcloud (backup|restore)" > > would work as > > > a charm. Thanks in advance for considering this feature. > > > > > > > Was there a blueprint/spec for this effort? Additionally do we have > > a > > list of the outstanding work required for this? If it's just these > > two > > playbooks, it might be ok for an FFE. But if there's additional > > tripleoclient related changes, I wouldn't necessarily feel > > comfortable > > with these unless we have a complete list of work. Just as a side > > note, I'm not sure putting these in tripleo-common is going to be > > the > > ideal place for this. Was it this review? https://review.openstack.org/#/c/582453/ For Stein we'll have an ansible role[0] and playbook repo[1] where these types of tasks should live. [0] https://github.com/openstack/ansible-role-openstack-operations [1] https://review.openstack.org/#/c/583415/ > > Thanks Alex. For Rocky, if we can ship the playbooks with relevant > docs we should be good. We will integrated with client in Stein > release with restore logic included. Regarding putting tripleo-common, > we're open to suggestions. I think Dan just submitted the review so we > can get some eyes on the playbooks. Where do you suggest is better > place for these instead? > > > > > Thanks, > > -Alex > > > > > Regards, > > > Martin > > > > > > [1] https://review.openstack.org/#/c/582453/ > > > > > >> > > >> +--> Next PTG will be in Denver, please propose topics: > > >> https://etherpad.openstack.org/p/tripleoci-ptg-stein > > >> +--> Multiple squads are currently brainstorming a framework to > > provide > > >> validations pre/post upgrades - stay in touch! > > >> > > >> +--+ > > >> | Continuous Integration | > > >> +--+ > > >> > > >> +--> Sprint theme: migration to Zuul v3 (More on > > >> https://trello.com/c/vyWXcKOB/841-sprint-16-goals) > > >> +--> Sagi is the rover and Chandan is the ruck. Please tell them > > any CI > > >> issue. > > >> +--> Promotion on master is 4 days, 0 days on Queens and Pike and > > 1 day on > > >> Ocata. > > >> +--> More: https://etherpad.openstack.org/p/tripleo-ci-squad-meet > > ing > > >> > > >> +-+ > > >> | Upgrades | > > >> +-+ > > >> > > >> +--> Good progress on major upgrades workflow, need reviews! > > >> +--> More: https://etherpad.openstack.org/p/tripleo-upgrade-squad > > -status > > >> > > >> +---+ > > >> | Containers | > > >> +---+ > > >> > > >> +--> We switched python-tripleoclient to deploy containerized > > undercloud > > >> by default! > > >> +--> Image prepare via workflow is still work in progress. > > >> +--> More: > > >> https://etherpad.openstack.org/p/tripleo-containers-squad-status > > >> > > >> +--+ > > >> | config-download | > > >> +--+ > > >> > > >> +--> UI integration is almost done (need review) > > >> +--> Bug with failure listing is being fixed: > > >> https://bugs.launchpad.net/tripleo/+bug/1779093 > > >> +--> More: > > >> https://etherpad.openstack.org/p/tripleo-config-download-squad-st > > atus > > >> > > >> +--+ > > >> | Integration | > > >> +--+ > > >> > > >> +--> We're enabling decoupled deployment plans e.g for OpenShift, > > DPDK > > >> etc: > > >>
Re: [openstack-dev] [tripleo] The Weekly Owl - 25th Edition
On Mon, Jul 30, 2018 at 10:42 AM Alex Schultz wrote: > On Mon, Jul 30, 2018 at 8:32 AM, Martin Magr wrote: > > > > > > On Tue, Jul 17, 2018 at 6:12 PM, Emilien Macchi > wrote: > >> > >> Your fellow reporter took a break from writing, but is now back on his > >> pen. > >> > >> Welcome to the twenty-fifth edition of a weekly update in TripleO world! > >> The goal is to provide a short reading (less than 5 minutes) to learn > >> what's new this week. > >> Any contributions and feedback are welcome. > >> Link to the previous version: > >> > http://lists.openstack.org/pipermail/openstack-dev/2018-June/131426.html > >> > >> +-+ > >> | General announcements | > >> +-+ > >> > >> +--> Rocky Milestone 3 is next week. After, any feature code will > require > >> Feature Freeze Exception (FFE), asked on the mailing-list. We'll enter a > >> bug-fix only and stabilization period, until we can push the first > stable > >> version of Rocky. > > > > > > Hey guys, > > > > I would like to ask for FFE for backup and restore, where we ended up > > deciding where is the best place for the code base for this project > (please > > see [1] for details). We believe that B support for overcloud control > > plane will be good addition to a rocky release, but we started with this > > initiative quite late indeed. The final result should the support in > > openstack client, where "openstack overcloud (backup|restore)" would > work as > > a charm. Thanks in advance for considering this feature. > > > > Was there a blueprint/spec for this effort? Additionally do we have a > list of the outstanding work required for this? If it's just these two > playbooks, it might be ok for an FFE. But if there's additional > tripleoclient related changes, I wouldn't necessarily feel comfortable > with these unless we have a complete list of work. Just as a side > note, I'm not sure putting these in tripleo-common is going to be the > ideal place for this. > Thanks Alex. For Rocky, if we can ship the playbooks with relevant docs we should be good. We will integrated with client in Stein release with restore logic included. Regarding putting tripleo-common, we're open to suggestions. I think Dan just submitted the review so we can get some eyes on the playbooks. Where do you suggest is better place for these instead? > > Thanks, > -Alex > > > Regards, > > Martin > > > > [1] https://review.openstack.org/#/c/582453/ > > > >> > >> +--> Next PTG will be in Denver, please propose topics: > >> https://etherpad.openstack.org/p/tripleoci-ptg-stein > >> +--> Multiple squads are currently brainstorming a framework to provide > >> validations pre/post upgrades - stay in touch! > >> > >> +--+ > >> | Continuous Integration | > >> +--+ > >> > >> +--> Sprint theme: migration to Zuul v3 (More on > >> https://trello.com/c/vyWXcKOB/841-sprint-16-goals) > >> +--> Sagi is the rover and Chandan is the ruck. Please tell them any CI > >> issue. > >> +--> Promotion on master is 4 days, 0 days on Queens and Pike and 1 day > on > >> Ocata. > >> +--> More: https://etherpad.openstack.org/p/tripleo-ci-squad-meeting > >> > >> +-+ > >> | Upgrades | > >> +-+ > >> > >> +--> Good progress on major upgrades workflow, need reviews! > >> +--> More: > https://etherpad.openstack.org/p/tripleo-upgrade-squad-status > >> > >> +---+ > >> | Containers | > >> +---+ > >> > >> +--> We switched python-tripleoclient to deploy containerized undercloud > >> by default! > >> +--> Image prepare via workflow is still work in progress. > >> +--> More: > >> https://etherpad.openstack.org/p/tripleo-containers-squad-status > >> > >> +--+ > >> | config-download | > >> +--+ > >> > >> +--> UI integration is almost done (need review) > >> +--> Bug with failure listing is being fixed: > >> https://bugs.launchpad.net/tripleo/+bug/1779093 > >> +--> More: > >> https://etherpad.openstack.org/p/tripleo-config-download-squad-status > >> > >> +--+ > >> | Integration | > >> +--+ > >> > >> +--> We're enabling decoupled deployment plans e.g for OpenShift, DPDK > >> etc: > >> > https://review.openstack.org/#/q/topic:alternate_plans+(status:open+OR+status:merged) > >> (need reviews). > >> +--> More: > >> https://etherpad.openstack.org/p/tripleo-integration-squad-status > >> > >> +-+ > >> | UI/CLI | > >> +-+ > >> > >> +--> Good progress on network configuration via UI > >> +--> Config-download patches are being reviewed and a lot of testing is > >> going on. > >> +--> More: https://etherpad.openstack.org/p/tripleo-ui-cli-squad-status > >> > >> +---+ > >> | Validations | > >> +---+ > >> > >> +--> Working on OpenShift validations, need reviews. > >> +--> More: > >> https://etherpad.openstack.org/p/tripleo-validations-squad-status > >> > >>
Re: [openstack-dev] [tripleo] The Weekly Owl - 25th Edition
On Mon, Jul 30, 2018 at 8:32 AM, Martin Magr wrote: > > > On Tue, Jul 17, 2018 at 6:12 PM, Emilien Macchi wrote: >> >> Your fellow reporter took a break from writing, but is now back on his >> pen. >> >> Welcome to the twenty-fifth edition of a weekly update in TripleO world! >> The goal is to provide a short reading (less than 5 minutes) to learn >> what's new this week. >> Any contributions and feedback are welcome. >> Link to the previous version: >> http://lists.openstack.org/pipermail/openstack-dev/2018-June/131426.html >> >> +-+ >> | General announcements | >> +-+ >> >> +--> Rocky Milestone 3 is next week. After, any feature code will require >> Feature Freeze Exception (FFE), asked on the mailing-list. We'll enter a >> bug-fix only and stabilization period, until we can push the first stable >> version of Rocky. > > > Hey guys, > > I would like to ask for FFE for backup and restore, where we ended up > deciding where is the best place for the code base for this project (please > see [1] for details). We believe that B support for overcloud control > plane will be good addition to a rocky release, but we started with this > initiative quite late indeed. The final result should the support in > openstack client, where "openstack overcloud (backup|restore)" would work as > a charm. Thanks in advance for considering this feature. > Was there a blueprint/spec for this effort? Additionally do we have a list of the outstanding work required for this? If it's just these two playbooks, it might be ok for an FFE. But if there's additional tripleoclient related changes, I wouldn't necessarily feel comfortable with these unless we have a complete list of work. Just as a side note, I'm not sure putting these in tripleo-common is going to be the ideal place for this. Thanks, -Alex > Regards, > Martin > > [1] https://review.openstack.org/#/c/582453/ > >> >> +--> Next PTG will be in Denver, please propose topics: >> https://etherpad.openstack.org/p/tripleoci-ptg-stein >> +--> Multiple squads are currently brainstorming a framework to provide >> validations pre/post upgrades - stay in touch! >> >> +--+ >> | Continuous Integration | >> +--+ >> >> +--> Sprint theme: migration to Zuul v3 (More on >> https://trello.com/c/vyWXcKOB/841-sprint-16-goals) >> +--> Sagi is the rover and Chandan is the ruck. Please tell them any CI >> issue. >> +--> Promotion on master is 4 days, 0 days on Queens and Pike and 1 day on >> Ocata. >> +--> More: https://etherpad.openstack.org/p/tripleo-ci-squad-meeting >> >> +-+ >> | Upgrades | >> +-+ >> >> +--> Good progress on major upgrades workflow, need reviews! >> +--> More: https://etherpad.openstack.org/p/tripleo-upgrade-squad-status >> >> +---+ >> | Containers | >> +---+ >> >> +--> We switched python-tripleoclient to deploy containerized undercloud >> by default! >> +--> Image prepare via workflow is still work in progress. >> +--> More: >> https://etherpad.openstack.org/p/tripleo-containers-squad-status >> >> +--+ >> | config-download | >> +--+ >> >> +--> UI integration is almost done (need review) >> +--> Bug with failure listing is being fixed: >> https://bugs.launchpad.net/tripleo/+bug/1779093 >> +--> More: >> https://etherpad.openstack.org/p/tripleo-config-download-squad-status >> >> +--+ >> | Integration | >> +--+ >> >> +--> We're enabling decoupled deployment plans e.g for OpenShift, DPDK >> etc: >> https://review.openstack.org/#/q/topic:alternate_plans+(status:open+OR+status:merged) >> (need reviews). >> +--> More: >> https://etherpad.openstack.org/p/tripleo-integration-squad-status >> >> +-+ >> | UI/CLI | >> +-+ >> >> +--> Good progress on network configuration via UI >> +--> Config-download patches are being reviewed and a lot of testing is >> going on. >> +--> More: https://etherpad.openstack.org/p/tripleo-ui-cli-squad-status >> >> +---+ >> | Validations | >> +---+ >> >> +--> Working on OpenShift validations, need reviews. >> +--> More: >> https://etherpad.openstack.org/p/tripleo-validations-squad-status >> >> +---+ >> | Networking | >> +---+ >> >> +--> No updates this week. >> +--> More: >> https://etherpad.openstack.org/p/tripleo-networking-squad-status >> >> +--+ >> | Workflows | >> +--+ >> >> +--> No updates this week. >> +--> More: https://etherpad.openstack.org/p/tripleo-workflows-squad-status >> >> +---+ >> | Security | >> +---+ >> >> +--> Working on Secrets management and Limit TripleO users efforts >> +--> More: https://etherpad.openstack.org/p/tripleo-security-squad >> >> ++ >> | Owl fact | >> ++ >> Elf owls live in a cacti. They are the smallest owls, and live in the >> southwestern United States and
Re: [openstack-dev] [tripleo] The Weekly Owl - 25th Edition
On Tue, Jul 17, 2018 at 6:12 PM, Emilien Macchi wrote: > Your fellow reporter took a break from writing, but is now back on his pen. > > Welcome to the twenty-fifth edition of a weekly update in TripleO world! > The goal is to provide a short reading (less than 5 minutes) to learn > what's new this week. > Any contributions and feedback are welcome. > Link to the previous version: > http://lists.openstack.org/pipermail/openstack-dev/2018-June/131426.html > > +-+ > | General announcements | > +-+ > > +--> Rocky Milestone 3 is next week. After, any feature code will require > Feature Freeze Exception (FFE), asked on the mailing-list. We'll enter a > bug-fix only and stabilization period, until we can push the first stable > version of Rocky. > Hey guys, I would like to ask for FFE for backup and restore, where we ended up deciding where is the best place for the code base for this project (please see [1] for details). We believe that B support for overcloud control plane will be good addition to a rocky release, but we started with this initiative quite late indeed. The final result should the support in openstack client, where "openstack overcloud (backup|restore)" would work as a charm. Thanks in advance for considering this feature. Regards, Martin [1] https://review.openstack.org/#/c/582453/ > +--> Next PTG will be in Denver, please propose topics: > https://etherpad.openstack.org/p/tripleoci-ptg-stein > +--> Multiple squads are currently brainstorming a framework to provide > validations pre/post upgrades - stay in touch! > > +--+ > | Continuous Integration | > +--+ > > +--> Sprint theme: migration to Zuul v3 (More on > https://trello.com/c/vyWXcKOB/841-sprint-16-goals) > +--> Sagi is the rover and Chandan is the ruck. Please tell them any CI > issue. > +--> Promotion on master is 4 days, 0 days on Queens and Pike and 1 day on > Ocata. > +--> More: https://etherpad.openstack.org/p/tripleo-ci-squad-meeting > > +-+ > | Upgrades | > +-+ > > +--> Good progress on major upgrades workflow, need reviews! > +--> More: https://etherpad.openstack.org/p/tripleo-upgrade-squad-status > > +---+ > | Containers | > +---+ > > +--> We switched python-tripleoclient to deploy containerized undercloud > by default! > +--> Image prepare via workflow is still work in progress. > +--> More: https://etherpad.openstack.org/p/tripleo-containers-squad-st > atus > > +--+ > | config-download | > +--+ > > +--> UI integration is almost done (need review) > +--> Bug with failure listing is being fixed: https://bugs.launchpad. > net/tripleo/+bug/1779093 > +--> More: https://etherpad.openstack.org/p/tripleo-config-download-squ > ad-status > > +--+ > | Integration | > +--+ > > +--> We're enabling decoupled deployment plans e.g for OpenShift, DPDK > etc: https://review.openstack.org/#/q/topic:alternate_plans+ > (status:open+OR+status:merged) (need reviews). > +--> More: https://etherpad.openstack.org/p/tripleo-integration-squad-s > tatus > > +-+ > | UI/CLI | > +-+ > > +--> Good progress on network configuration via UI > +--> Config-download patches are being reviewed and a lot of testing is > going on. > +--> More: https://etherpad.openstack.org/p/tripleo-ui-cli-squad-status > > +---+ > | Validations | > +---+ > > +--> Working on OpenShift validations, need reviews. > +--> More: https://etherpad.openstack.org/p/tripleo-validations-squad-s > tatus > > +---+ > | Networking | > +---+ > > +--> No updates this week. > +--> More: https://etherpad.openstack.org/p/tripleo-networking-squad-st > atus > > +--+ > | Workflows | > +--+ > > +--> No updates this week. > +--> More: https://etherpad.openstack.org/p/tripleo-workflows-squad-status > > +---+ > | Security | > +---+ > > +--> Working on Secrets management and Limit TripleO users efforts > +--> More: https://etherpad.openstack.org/p/tripleo-security-squad > > ++ > | Owl fact | > ++ > Elf owls live in a cacti. They are the smallest owls, and live in the > southwestern United States and Mexico. It will sometimes make its home in > the giant saguaro cactus, nesting in holes made by other animals. However, > the elf owl isn’t picky and will also live in trees or on telephone poles. > > Source: http://mentalfloss.com/article/68473/15-mysterious-facts-abo > ut-owls > > Thank you all for reading and stay tuned! > -- > Your fellow reporter, 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 > >
[openstack-dev] [tripleo] The Weekly Owl - 25th Edition
Your fellow reporter took a break from writing, but is now back on his pen. Welcome to the twenty-fifth edition of a weekly update in TripleO world! The goal is to provide a short reading (less than 5 minutes) to learn what's new this week. Any contributions and feedback are welcome. Link to the previous version: http://lists.openstack.org/pipermail/openstack-dev/2018-June/131426.html +-+ | General announcements | +-+ +--> Rocky Milestone 3 is next week. After, any feature code will require Feature Freeze Exception (FFE), asked on the mailing-list. We'll enter a bug-fix only and stabilization period, until we can push the first stable version of Rocky. +--> Next PTG will be in Denver, please propose topics: https://etherpad.openstack.org/p/tripleoci-ptg-stein +--> Multiple squads are currently brainstorming a framework to provide validations pre/post upgrades - stay in touch! +--+ | Continuous Integration | +--+ +--> Sprint theme: migration to Zuul v3 (More on https://trello.com/c/vyWXcKOB/841-sprint-16-goals) +--> Sagi is the rover and Chandan is the ruck. Please tell them any CI issue. +--> Promotion on master is 4 days, 0 days on Queens and Pike and 1 day on Ocata. +--> More: https://etherpad.openstack.org/p/tripleo-ci-squad-meeting +-+ | Upgrades | +-+ +--> Good progress on major upgrades workflow, need reviews! +--> More: https://etherpad.openstack.org/p/tripleo-upgrade-squad-status +---+ | Containers | +---+ +--> We switched python-tripleoclient to deploy containerized undercloud by default! +--> Image prepare via workflow is still work in progress. +--> More: https://etherpad.openstack.org/p/tripleo-containers-squad-status +--+ | config-download | +--+ +--> UI integration is almost done (need review) +--> Bug with failure listing is being fixed: https://bugs.launchpad.net/tripleo/+bug/1779093 +--> More: https://etherpad.openstack.org/p/tripleo-config-download-squad-status +--+ | Integration | +--+ +--> We're enabling decoupled deployment plans e.g for OpenShift, DPDK etc: https://review.openstack.org/#/q/topic:alternate_plans+(status:open+OR+status:merged) (need reviews). +--> More: https://etherpad.openstack.org/p/tripleo-integration-squad-status +-+ | UI/CLI | +-+ +--> Good progress on network configuration via UI +--> Config-download patches are being reviewed and a lot of testing is going on. +--> More: https://etherpad.openstack.org/p/tripleo-ui-cli-squad-status +---+ | Validations | +---+ +--> Working on OpenShift validations, need reviews. +--> More: https://etherpad.openstack.org/p/tripleo-validations-squad-status +---+ | Networking | +---+ +--> No updates this week. +--> More: https://etherpad.openstack.org/p/tripleo-networking-squad-status +--+ | Workflows | +--+ +--> No updates this week. +--> More: https://etherpad.openstack.org/p/tripleo-workflows-squad-status +---+ | Security | +---+ +--> Working on Secrets management and Limit TripleO users efforts +--> More: https://etherpad.openstack.org/p/tripleo-security-squad ++ | Owl fact | ++ Elf owls live in a cacti. They are the smallest owls, and live in the southwestern United States and Mexico. It will sometimes make its home in the giant saguaro cactus, nesting in holes made by other animals. However, the elf owl isn’t picky and will also live in trees or on telephone poles. Source: http://mentalfloss.com/article/68473/15-mysterious-facts-about-owls Thank you all for reading and stay tuned! -- Your fellow reporter, 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
