<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Wed, Aug 1, 2018 at 6:06 PM Jill Rouleau <<a href="mailto:jillr@redhat.com">jillr@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Tue, 2018-07-31 at 07:38 -0400, Pradeep Kilambi wrote:<br>
> <br>
> <br>
> On Mon, Jul 30, 2018 at 2:17 PM Jill Rouleau <<a href="mailto:jillr@redhat.com" target="_blank">jillr@redhat.com</a>> wrote:<br>
> > On Mon, 2018-07-30 at 11:35 -0400, Pradeep Kilambi wrote:<br>
> > > <br>
> > > <br>
> > > On Mon, Jul 30, 2018 at 10:42 AM Alex Schultz <<a href="mailto:aschultz@redhat.com" target="_blank">aschultz@redhat.com</a><br>
> > ><br>
> > > wrote:<br>
> > > > On Mon, Jul 30, 2018 at 8:32 AM, Martin Magr <<a href="mailto:mmagr@redhat.com" target="_blank">mmagr@redhat.com</a>><br>
> > > > wrote:<br>
> > > > ><br>
> > > > ><br>
> > > > > On Tue, Jul 17, 2018 at 6:12 PM, Emilien Macchi <emilien@redha<br>
> > <a href="http://t.co" rel="noreferrer" target="_blank">t.co</a><br>
> > > > m> wrote:<br>
> > > > >><br>
> > > > >> Your fellow reporter took a break from writing, but is now<br>
> > back<br>
> > > > on his<br>
> > > > >> pen.<br>
> > > > >><br>
> > > > >> Welcome to the twenty-fifth edition of a weekly update in<br>
> > TripleO<br>
> > > > world!<br>
> > > > >> The goal is to provide a short reading (less than 5 minutes)<br>
> > to<br>
> > > > learn<br>
> > > > >> what's new this week.<br>
> > > > >> Any contributions and feedback are welcome.<br>
> > > > >> Link to the previous version:<br>
> > > > >> <a href="http://lists.openstack.org/pipermail/openstack-dev/2018-June/" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/2018-June/</a><br>
> > 1314<br>
> > > > 26.html<br>
> > > > >><br>
> > > > >> +---------------------------------+<br>
> > > > >> | General announcements |<br>
> > > > >> +---------------------------------+<br>
> > > > >><br>
> > > > >> +--> Rocky Milestone 3 is next week. After, any feature code<br>
> > will<br>
> > > > require<br>
> > > > >> Feature Freeze Exception (FFE), asked on the mailing-list.<br>
> > We'll<br>
> > > > enter a<br>
> > > > >> bug-fix only and stabilization period, until we can push the<br>
> > > > first stable<br>
> > > > >> version of Rocky.<br>
> > > > ><br>
> > > > ><br>
> > > > > Hey guys,<br>
> > > > ><br>
> > > > > I would like to ask for FFE for backup and restore, where we<br>
> > > > ended up<br>
> > > > > deciding where is the best place for the code base for this<br>
> > > > project (please<br>
> > > > > see [1] for details). We believe that B&R support for<br>
> > overcloud<br>
> > > > control<br>
> > > > > plane will be good addition to a rocky release, but we started<br>
> > > > with this<br>
> > > > > initiative quite late indeed. The final result should the<br>
> > support<br>
> > > > in<br>
> > > > > openstack client, where "openstack overcloud (backup|restore)"<br>
> > > > would work as<br>
> > > > > a charm. Thanks in advance for considering this feature.<br>
> > > > ><br>
> > > > <br>
> > > > Was there a blueprint/spec for this effort? Additionally do we<br>
> > have<br>
> > > > a<br>
> > > > list of the outstanding work required for this? If it's just<br>
> > these<br>
> > > > two<br>
> > > > playbooks, it might be ok for an FFE. But if there's additional<br>
> > > > tripleoclient related changes, I wouldn't necessarily feel<br>
> > > > comfortable<br>
> > > > with these unless we have a complete list of work. Just as a<br>
> > side<br>
> > > > note, I'm not sure putting these in tripleo-common is going to<br>
> > be<br>
> > > > the<br>
> > > > ideal place for this.<br>
> > <br>
> > Was it this review? <a href="https://review.openstack.org/#/c/582453/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/582453/</a><br>
> > <br>
> > For Stein we'll have an ansible role[0] and playbook repo[1] where<br>
> > these<br>
> > types of tasks should live.<br>
> > <br>
> > [0] <a href="https://github.com/openstack/ansible-role-openstack-operations" rel="noreferrer" target="_blank">https://github.com/openstack/ansible-role-openstack-operations</a> <br>
> > [1] <a href="https://review.openstack.org/#/c/583415/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/583415/</a><br>
> Thanks Jill! The issue is, we want to be able to backport this to<br>
> Queens once merged. With the new repos you're mentioning would this be<br>
> possible? If no, then this wont work for us unfortunately.<br>
> <br>
<br>
We wouldn't backport the new packages to Queens, however the repos will<br>
be on github and available to clone and use. This would be far<br>
preferable than adding them to tripleo-common so late in the rocky cycle<br>
then having to break them back out right away in stein.<br></blockquote><div><br></div><div><br></div><div>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? </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
> <br>
> <br>
> > <br>
> > <br>
> > > <br>
> > > Thanks Alex. For Rocky, if we can ship the playbooks with relevant<br>
> > > docs we should be good. We will integrated with client in Stein<br>
> > > release with restore logic included. Regarding putting tripleo-<br>
> > common, <br>
> > > we're open to suggestions. I think Dan just submitted the review<br>
> > so we<br>
> > > can get some eyes on the playbooks. Where do you suggest is better<br>
> > > place for these instead?<br>
> > > <br>
> > > > <br>
> > > > Thanks,<br>
> > > > -Alex<br>
> > > > <br>
> > > > > Regards,<br>
> > > > > Martin<br>
> > > > ><br>
> > > > > [1] <a href="https://review.openstack.org/#/c/582453/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/582453/</a><br>
> > > > ><br>
> > > > >><br>
> > > > >> +--> Next PTG will be in Denver, please propose topics:<br>
> > > > >> <a href="https://etherpad.openstack.org/p/tripleoci-ptg-stein" rel="noreferrer" target="_blank">https://etherpad.openstack.org/p/tripleoci-ptg-stein</a><br>
> > > > >> +--> Multiple squads are currently brainstorming a framework<br>
> > to<br>
> > > > provide<br>
> > > > >> validations pre/post upgrades - stay in touch!<br>
> > > > >><br>
> > > > >> +------------------------------+<br>
> > > > >> | Continuous Integration |<br>
> > > > >> +------------------------------+<br>
> > > > >><br>
> > > > >> +--> Sprint theme: migration to Zuul v3 (More on<br>
> > > > >> <a href="https://trello.com/c/vyWXcKOB/841-sprint-16-goals" rel="noreferrer" target="_blank">https://trello.com/c/vyWXcKOB/841-sprint-16-goals</a>)<br>
> > > > >> +--> Sagi is the rover and Chandan is the ruck. Please tell<br>
> > them<br>
> > > > any CI<br>
> > > > >> issue.<br>
> > > > >> +--> Promotion on master is 4 days, 0 days on Queens and Pike<br>
> > and<br>
> > > > 1 day on<br>
> > > > >> Ocata.<br>
> > > > >> +--> More: <a href="https://etherpad.openstack.org/p/tripleo-ci-squad-" rel="noreferrer" target="_blank">https://etherpad.openstack.org/p/tripleo-ci-squad-</a><br>
> > meet<br>
> > > > ing<br>
> > > > >><br>
> > > > >> +-------------+<br>
> > > > >> | Upgrades |<br>
> > > > >> +-------------+<br>
> > > > >><br>
> > > > >> +--> Good progress on major upgrades workflow, need reviews!<br>
> > > > >> +--> More: <a href="https://etherpad.openstack.org/p/tripleo-upgrade-s" rel="noreferrer" target="_blank">https://etherpad.openstack.org/p/tripleo-upgrade-s</a><br>
> > quad<br>
> > > > -status<br>
> > > > >><br>
> > > > >> +---------------+<br>
> > > > >> | Containers |<br>
> > > > >> +---------------+<br>
> > > > >><br>
> > > > >> +--> We switched python-tripleoclient to deploy containerized<br>
> > > > undercloud<br>
> > > > >> by default!<br>
> > > > >> +--> Image prepare via workflow is still work in progress.<br>
> > > > >> +--> More:<br>
> > > > >> <a href="https://etherpad.openstack.org/p/tripleo-containers-squad-sta" rel="noreferrer" target="_blank">https://etherpad.openstack.org/p/tripleo-containers-squad-sta</a><br>
> > tus<br>
> > > > >><br>
> > > > >> +----------------------+<br>
> > > > >> | config-download |<br>
> > > > >> +----------------------+<br>
> > > > >><br>
> > > > >> +--> UI integration is almost done (need review)<br>
> > > > >> +--> Bug with failure listing is being fixed:<br>
> > > > >> <a href="https://bugs.launchpad.net/tripleo/+bug/1779093" rel="noreferrer" target="_blank">https://bugs.launchpad.net/tripleo/+bug/1779093</a><br>
> > > > >> +--> More:<br>
> > > > >> <a href="https://etherpad.openstack.org/p/tripleo-config-download-squa" rel="noreferrer" target="_blank">https://etherpad.openstack.org/p/tripleo-config-download-squa</a><br>
> > d-st<br>
> > > > atus<br>
> > > > >><br>
> > > > >> +--------------+<br>
> > > > >> | Integration |<br>
> > > > >> +--------------+<br>
> > > > >><br>
> > > > >> +--> We're enabling decoupled deployment plans e.g for<br>
> > OpenShift,<br>
> > > > DPDK<br>
> > > > >> etc:<br>
> > > > >> <a href="https://review.openstack.org/#/q/topic:alternate_plans+(statu" rel="noreferrer" target="_blank">https://review.openstack.org/#/q/topic:alternate_plans+(statu</a><br>
> > s:op<br>
> > > > en+OR+status:merged)<br>
> > > > >> (need reviews).<br>
> > > > >> +--> More:<br>
> > > > >> <a href="https://etherpad.openstack.org/p/tripleo-integration-squad-st" rel="noreferrer" target="_blank">https://etherpad.openstack.org/p/tripleo-integration-squad-st</a><br>
> > atus<br>
> > > > >><br>
> > > > >> +---------+<br>
> > > > >> | UI/CLI |<br>
> > > > >> +---------+<br>
> > > > >><br>
> > > > >> +--> Good progress on network configuration via UI<br>
> > > > >> +--> Config-download patches are being reviewed and a lot of<br>
> > > > testing is<br>
> > > > >> going on.<br>
> > > > >> +--> More: <a href="https://etherpad.openstack.org/p/tripleo-ui-cli-sq" rel="noreferrer" target="_blank">https://etherpad.openstack.org/p/tripleo-ui-cli-sq</a><br>
> > uad-<br>
> > > > status<br>
> > > > >><br>
> > > > >> +---------------+<br>
> > > > >> | Validations |<br>
> > > > >> +---------------+<br>
> > > > >><br>
> > > > >> +--> Working on OpenShift validations, need reviews.<br>
> > > > >> +--> More:<br>
> > > > >> <a href="https://etherpad.openstack.org/p/tripleo-validations-squad-st" rel="noreferrer" target="_blank">https://etherpad.openstack.org/p/tripleo-validations-squad-st</a><br>
> > atus<br>
> > > > >><br>
> > > > >> +---------------+<br>
> > > > >> | Networking |<br>
> > > > >> +---------------+<br>
> > > > >><br>
> > > > >> +--> No updates this week.<br>
> > > > >> +--> More:<br>
> > > > >> <a href="https://etherpad.openstack.org/p/tripleo-networking-squad-sta" rel="noreferrer" target="_blank">https://etherpad.openstack.org/p/tripleo-networking-squad-sta</a><br>
> > tus<br>
> > > > >><br>
> > > > >> +--------------+<br>
> > > > >> | Workflows |<br>
> > > > >> +--------------+<br>
> > > > >><br>
> > > > >> +--> No updates this week.<br>
> > > > >> +--> More: <a href="https://etherpad.openstack.org/p/tripleo-workflows" rel="noreferrer" target="_blank">https://etherpad.openstack.org/p/tripleo-workflows</a><br>
> > -squ<br>
> > > > ad-status<br>
> > > > >><br>
> > > > >> +-----------+<br>
> > > > >> | Security |<br>
> > > > >> +-----------+<br>
> > > > >><br>
> > > > >> +--> Working on Secrets management and Limit TripleO users<br>
> > > > efforts<br>
> > > > >> +--> More: <a href="https://etherpad.openstack.org/p/tripleo-security-" rel="noreferrer" target="_blank">https://etherpad.openstack.org/p/tripleo-security-</a><br>
> > squa<br>
> > > > d<br>
> > > > >><br>
> > > > >> +------------+<br>
> > > > >> | Owl fact |<br>
> > > > >> +------------+<br>
> > > > >> Elf owls live in a cacti. They are the smallest owls, and<br>
> > live in<br>
> > > > the<br>
> > > > >> southwestern United States and Mexico. It will sometimes make<br>
> > its<br>
> > > > home in<br>
> > > > >> the giant saguaro cactus, nesting in holes made by other<br>
> > animals.<br>
> > > > However,<br>
> > > > >> the elf owl isn’t picky and will also live in trees or on<br>
> > > > telephone poles.<br>
> > > > >><br>
> > > > >> Source:<br>
> > > > >> <a href="http://mentalfloss.com/article/68473/15-mysterious-facts-abou" rel="noreferrer" target="_blank">http://mentalfloss.com/article/68473/15-mysterious-facts-abou</a><br>
> > t-ow<br>
> > > > ls<br>
> > > > >><br>
> > > > >> Thank you all for reading and stay tuned!<br>
> > > > >> --<br>
> > > > >> Your fellow reporter, Emilien Macchi<br>
> > > > >><br>
> > > > >><br>
> > > ><br>
> > ____________________________________________________________________<br>
> > > > ______<br>
> > > > >> OpenStack Development Mailing List (not for usage questions)<br>
> > > > >> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subjec" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subjec</a><br>
> > t:un<br>
> > > > subscribe<br>
> > > > >> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
> > -dev<br>
> > > > >><br>
> > > > ><br>
> > > > ><br>
> > > ><br>
> > ____________________________________________________________________<br>
> > > > ______<br>
> > > > > OpenStack Development Mailing List (not for usage questions)<br>
> > > > > Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject</a><br>
> > :uns<br>
> > > > ubscribe<br>
> > > > > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-</a><br>
> > dev<br>
> > > > ><br>
> > > > <br>
> > > ><br>
> > ____________________________________________________________________<br>
> > > > ______<br>
> > > > OpenStack Development Mailing List (not for usage questions)<br>
> > > > Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:u" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:u</a><br>
> > nsub<br>
> > > > scribe<br>
> > > > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-de" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-de</a><br>
> > v<br>
> > > > <br>
> > > <br>
> > > -- <br>
> > > Cheers,<br>
> > > ~ Prad<br>
> > ><br>
> > ____________________________________________________________________<br>
> > __<br>
> > > ____<br>
> > > OpenStack Development Mailing List (not for usage questions)<br>
> > > Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:uns" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:uns</a><br>
> > ubsc<br>
> > > ribe<br>
> > > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev_" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev_</a><br>
> > ____________________________________________________________________<br>
> > _____<br>
> > OpenStack Development Mailing List (not for usage questions)<br>
> > Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsub" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsub</a><br>
> > scribe<br>
> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> > <br>
> <br>
> -- <br>
> Cheers,<br>
> ~ Prad<br>
> ______________________________________________________________________<br>
> ____<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubsc" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubsc</a><br>
> ribe<br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">Cheers,<br>~ Prad</div></div>