- openstack-discuss - lists.openstack.org

[neutron] Drivers meeting - agenda
by Slawek Kaplonski 02 Apr '20

02 Apr '20

Hi, I though that it may be useful for You if I will send earlier agenda for next drivers meeting to You. That You will have some time to go through RFEs which are planned to be discussed on our next meeting. For 3.04.2020 I have 3 RFEs to discuss: * https://bugs.launchpad.net/neutron/+bug/1592028 - [RFE] Support security-group-rule creation with address-groups * https://bugs.launchpad.net/neutron/+bug/1869129 - neutron accepts CIDR in security groups that are invalid in ovn - this was reported as issue in ovn but it seems that this may be potentially security issue which will require changes in API to fix, Already proposed patch https://review.opendev.org/#/c/716806/ * https://bugs.launchpad.net/neutron/+bug/1870319 - [RFE] Network cascade deletion API call See You tomorrow on drivers meeting. — Slawek Kaplonski Senior software engineer Red Hat

1 0

[election][cloudkitty][ptl] Announcing my PTL candidacy for CloudKitty (Justin Ferrieu)
by Justin Ferrieu 02 Apr '20

02 Apr '20

Hi all, I would like to nominate myself to be the CloudKitty PTL for the Victoria cycle. The project is quite stable now and just needs an overall maintenance and to meet the community goals. I feel ready to do that. Thank you a lot. Best regards, ---- Justin Ferrieu Mail : justin.ferrieu(a)objectif-libre.com Consultant Cloud Objectif Libre URL : www.objectif-libre.com [1] Au service de votre Cloud Twitter : @objectiflibre Suivez les actualités OpenStack en français en vous abonnant à la Pause OpenStack http://olib.re/pause-openstack Links: ------ [1] http://www.objectif-libre.com

2 1

Fwd: OpenStack Foundation Community Meetings
by Allison Price 02 Apr '20

02 Apr '20

Hi everyone - In case you didn’t see the post on the Foundation mailing list, we have a community meeting tomorrow where we will be talking about updates to OSF events as well as project updates and how you can get involved in the 10th year of OpenStack campaign. One meeting will be in English and one in Mandarin. Bring your questions and see you then! Cheers, Allison > Begin forwarded message: > > From: Allison Price <allison(a)openstack.org> > Subject: OpenStack Foundation Community Meetings > Date: March 26, 2020 at 10:21:15 AM CDT > To: foundation(a)lists.openstack.org > > Hi everyone, > > Next week we are going to have two community meetings to discuss the OpenStack 10th anniversary planning, current community projects, and an update on OSF events. Please join if you would like to hear updates or if you have questions for the OpenStack Foundation team. > > Join us: > Thursday, April 2 at 10am CT / 1500 UTC <https://zoom.us/j/913456204> > Friday, April 3 in Mandarin at 10am China Standard Time <https://zoom.us/j/389363434> > > If you are unable to join one of the above times, I will share a recording to the mailing list after the meetings. > > Cheers, > Allison > > > Allison Price > OpenStack Foundation > allison(a)openstack.org <mailto:allison@openstack.org> > > > >

2 4

Re: [tc] [ironic] Promoting ironic to a top-level opendev project?
by Ilya Etingof 02 Apr '20

02 Apr '20

> So I think we need to dig deeper in the strategy for Ironic, the > adoption obstacles we are trying to remove, and discuss the options. > Being set up as a separate top-level project is one option. But I feel > like changing governance (i.e. no longer be under the TC) has a lot less > impact to change the perception than, say, creating a separate ironic > product website that explains Ironic completely outside of the OpenStack > context (which we could do without changing governance). Ironic product web-site might be highly beneficial anyway. Looking at the functionally similar tool [1], those guys have an impressive web-presence. I can imagine prospective enterprise users would be gravitating toward MaaS just because of that. 1. https://maas.io

1 0

[kolla][uc] Kolla SIG
by Mark Goddard 02 Apr '20

02 Apr '20

Hi, I'd like to propose the creation of a Special Interest Group (SIG) [0] for Kolla. The main aim of the group would be to improve communication between operators and developers. The SIG would host regular virtual project onboarding, project update, and feedback sessions, ideally via video calls. This should remove the necessity of being physically present at Open Infra Summits for participation in the project. I like to think of this as the fifth open [1] (name TBD). I propose that in addition to the above sessions, the SIG should host more informal discussions, probably every 2-4 weeks with the aim of meeting other community members, discussing successes and failures, sharing knowledge, and generally getting to know each other a bit better. These could be via video call, IRC, or a mix. Finally - I propose that we build and maintain a list of Kolla users, including details of their environments and areas of interest and expertise. Of course this would be opt-in. This would help us to connect with subject matter experts and interested parties to help answer queries in IRC, or when making changes to a specific area. This is all up for discussion, and subject to sufficient interest. If you are interested, please add your name and email address to the Etherpad [2], along with any comments, thoughts or suggestions. [0] https://governance.openstack.org/sigs/ [1] https://www.openstack.org/four-opens/ [2] https://etherpad.openstack.org/p/kolla-sig Cheers, Mark

5 9

[all][dev][qa] cirros 0.5.1
by Radosław Piliszek 02 Apr '20

02 Apr '20

Hiya Folks, as you might have noticed, cinder 0.5.1 has been released. This build seems to be passing the current devstack gate. [1] Big thanks to hrw and smoser for letting cirros 0.5.1 happen (and cirros having bright future yet again). Also thanks to mordred for cleaning up SDK testing to pass. :-) I think it would be nice to merge this in Ussuri still, preferably before April. On the other hand, we all know that devstack gate is not super comprehensive and hence I would like to ask teams whose tests depend on interaction with guest OS to test their gates on this patch (or help me help you do that). I deliberately marked it W-1 to avoid merging too early. Let the discussion begin. :-) [1] https://review.opendev.org/711492 -yoctozepto

4 6

[tripleo] meeting notes from the last two weeks
by Wesley Hayutin 01 Apr '20

01 Apr '20

Greetings, I need to see why the openstack meeting bot is not in the #tripleo channel. A record was not automatically kept.. so here is the raw txt from the last two meetings.. I'll get the bot fixed asap. Meeting notes March 24 2020 [08:00:44] <weshay|ruck> #topic agenda [08:00:44] <weshay|ruck> * Review past action items [08:00:44] <weshay|ruck> * One off agenda items [08:00:44] <weshay|ruck> * Squad status [08:00:44] <weshay|ruck> * Bugs & Blueprints [08:00:44] <weshay|ruck> * Projects releases or stable backports [08:00:44] <weshay|ruck> * Specs [08:00:44] <weshay|ruck> * open discussion [08:00:44] <weshay|ruck> Anyone can use the #link, #action and #info commands, not just the moderatorǃ [08:00:44] <weshay|ruck> Hey folks! who's around? [08:00:57] <ekultails> o/ [08:00:59] <arxcruz|rover> o/ [08:01:03] <rlandy> o/ [08:01:11] <tkajinam> o/ [08:01:18] <rfolco> o/ [08:01:24] <pkopec> o/ [08:01:41] <owalsh> o/ [08:01:45] <jbadiapa> o/ [08:02:24] <ysandeep> ysandeep, o/ [08:02:27] <weshay|ruck> #topic review past action items [08:02:27] <weshay|ruck> http://eavesdrop.openstack.org/meetings/tripleo/2020/ [08:02:42] <weshay|ruck> anyone need to raise anything from a previous meeting? [08:03:07] <weshay|ruck> None. [08:03:07] <weshay|ruck> #topic one off agenda items [08:03:07] <weshay|ruck> #link https://etherpad.openstack.org/p/tripleo-meeting-items [08:03:17] <Tengu> «o/ [08:03:18] <weshay|ruck> I added two items to the agenda.. [08:03:27] <weshay|ruck> please add something if you have it.. [08:03:53] * weshay|ruck notes that rdo-cloud the 3rd party ci platform is in a scheduled maint window today [08:04:03] <openstackgerrit> Emilien Macchi proposed openstack/tripleo-heat-templates master: Refactorize test_tht_ansible_syntax to welcome new roles/modules https://review.opendev.org/713669 [08:04:05] <weshay|ruck> the ctrl plane is moving to vexxhost [08:04:10] <openstackgerrit> Emilien Macchi proposed openstack/tripleo-heat-templates master: standalone/overcloud: enable the HA deployment by default https://review.opendev.org/359060 [08:04:16] <weshay|ruck> should be back by tomorrow [08:04:18] <openstackgerrit> Emilien Macchi proposed openstack/tripleo-heat-templates master: Deprecate Keepalived service https://review.opendev.org/657067 [08:04:28] <fultonj> o/ [08:04:33] <marios> hi [08:04:36] <weshay|ruck> any questions? [08:04:43] <weshay|ruck> EmilienM, stop working :) [08:04:45] <cloudnull> o/ [08:04:49] <leanderthal> o/ [08:04:50] <sshnaidm> o/ [08:04:53] <EmilienM> o/ [08:05:01] <weshay|ruck> leanderthal, you may want to get the testday on the agenda :) [08:05:12] <leanderthal> ooOOOooh good call [08:05:19] <weshay|ruck> ok.. the next topic is around bugs [08:05:34] <beagles> o/ [08:05:49] <weshay|ruck> we were up to 60 untriaged bugs last week.. a lot of folks do NOT have access to self triage and that's fine [08:06:09] <weshay|ruck> but if are a member of the tripleo org in launchpad.. we'd hope that you do follow the triage process [08:06:15] <sshnaidm> don't we run a meeting bot? [08:06:21] <weshay|ruck> So Question for the group... [08:06:23] <weshay|ruck> sshnaidm, yes [08:06:38] <weshay|ruck> but maybe it's down.. ? [08:06:40] <weshay|ruck> don't know [08:07:06] <weshay|ruck> Question... Any objects to closing any bugs in marked "New" ( untriaged ) older than 365 days? [08:07:11] <weshay|ruck> objection rather [08:07:17] <marios> weshay|ruck: sounds good to me [08:07:25] <beagles> k [08:07:31] <marios> weshay|ruck: but 'latest updated ' date right? [08:07:45] <weshay|ruck> ya.. I'll account for that... good point [08:07:47] <marios> weshay|ruck: not filed? maybe doesn't matter 365 is long enough that it either /or [08:07:50] <chandankumar> fultonj, fmount https://bugs.launchpad.net/tripleo/+bug/1868731 thanks for looking into that [08:07:51] <openstack> Launchpad bug 1868731 in tripleo "ceph_ansible_skip_tags is getting ignored during multinode overcloud deploy" [Critical,Triaged] [08:07:56] <beagles> (wrong window) but yeah, that sounds reasonable [08:08:02] * florianf (~flfuchs@2a02:8109:9280:1aa8:8bb0:31ca:8557:482c) has joined [08:08:09] <fultonj> chandankumar: thanks [08:08:15] <weshay|ruck> I'll send an email to the list to have folks reopen if they need it [08:08:30] <weshay|ruck> ok.. seeing no objections... we'll go ahead and clean it up :) [08:08:47] <weshay|ruck> #topic one off agenda items [08:08:47] <weshay|ruck> #link https://etherpad.openstack.org/p/tripleo-meeting-items [08:08:47] <weshay|ruck> #topic Active Squad status [08:08:47] <weshay|ruck> ci [08:08:47] <weshay|ruck> #link https://hackmd.io/IhMCTNMBSF6xtqiEd9Z0Kw?both [08:08:47] <weshay|ruck> validations [08:08:47] <weshay|ruck> #link https://etherpad.openstack.org/p/tripleo-validations-squad-status [08:08:47] <weshay|ruck> ceph-integration [08:08:47] <weshay|ruck> #link https://etherpad.openstack.org/p/tripleo-integration-squad-status [08:08:47] <weshay|ruck> transformation [08:08:47] <weshay|ruck> #link https://etherpad.openstack.org/p/tripleo-ansible-agenda [08:08:47] <weshay|ruck> mistral-to-ansible [08:08:47] <weshay|ruck> #link https://etherpad.openstack.org/p/tripleo-mistral-to-ansible [08:09:00] <weshay|ruck> any reviews needed by the squads? [08:09:05] * TrevorV (~TrevorV(a)130-45-79-246.dyn.grandenetworks.net) has joined [08:09:17] <Tengu> validations: we have our package under TripleO governance! [08:09:25] <Tengu> it's been merged today. [08:09:50] <weshay|ruck> rdo governance :) [08:09:51] <cloudnull> weshay|ruck the following reviews would be great to get some eyes on - https://review.opendev.org/#/q/starredby:cloudnull+status:open,n,z [08:10:12] <weshay|ruck> thanks cloudnull [08:10:41] <weshay|ruck> fultonj, I mentioned this earlier.. but ansible 2.9 is being tested along side the latest ceph-ansible.. I don't have a ton of detail on that [08:11:02] * derekh (~derekh(a)93.107.228.126) has joined [08:11:15] <weshay|ruck> ok.. let's move on [08:11:19] <fultonj> weshay|ruck: ack [08:11:26] <weshay|ruck> #topic Moderately Active Squads [08:11:26] <weshay|ruck> Ironic-integration [08:11:26] <weshay|ruck> https://etherpad.openstack.org/p/tripleo-ironic-integration-squad-status [08:11:26] <weshay|ruck> upgrade [08:11:26] <weshay|ruck> #link https://etherpad.openstack.org/p/tripleo-upgrade-squad-status [08:11:26] <weshay|ruck> edge [08:11:26] <weshay|ruck> #link https://etherpad.openstack.org/p/tripleo-edge-squad-status [08:11:26] <weshay|ruck> networking [08:11:26] <weshay|ruck> #link https://etherpad.openstack.org/p/tripleo-networking-squad-status [08:11:47] <weshay|ruck> probably nothing new here [08:11:59] <weshay|ruck> #link https://launchpad.net/tripleo/+milestone/ussuri-3 [08:12:31] <weshay|ruck> 5 New, 28 Incomplete, 4 Invalid, 4 Won't Fix, 4 Confirmed, 385 Triaged, 120 In Progress, 2 Fix Committed, 151 Fix Released [08:12:50] <weshay|ruck> not bad on the bug counts.. I guess [08:13:00] <weshay|ruck> Storyboard bugs. [08:13:00] <weshay|ruck> #link https://storyboard.openstack.org/#!/project_group/76 [08:13:48] <cloudnull> weshay|ruck we've recently updated the mistral_to_ansible board - https://storyboard.openstack.org/#!/board/208 [08:14:17] <weshay|ruck> very nice.. [08:14:31] <weshay|ruck> k.. will include that in the future [08:14:53] <weshay|ruck> There are two blueprints not started for ussuri [08:14:54] <weshay|ruck> Medium tripleo-firewall-rule-reporting New Not started ussuri [08:14:54] <weshay|ruck> Medium remove-puppet Drafting Not started Emilien Macchi ussuri [08:15:02] * amoralej|lunch is now known as amoralej [08:15:20] <weshay|ruck> EmilienM, maybe we move that to the next release or future at this point... [08:15:30] <weshay|ruck> April 20th is m3 I think [08:15:52] <weshay|ruck> and dsneddon owns https://blueprints.launchpad.net/tripleo/+spec/tripleo-firewall-rule-report… [08:16:10] <weshay|ruck> #topic specs [08:16:10] <weshay|ruck> #link https://review.openstack.org/#/q/project:openstack/tripleo-specs+status:open [08:16:39] <weshay|ruck> reviews for luke please https://review.opendev.org/#/c/698828/ on [08:16:39] <weshay|ruck> Add spec for AWX integration. [08:16:55] <weshay|ruck> #topic open discussion [08:16:55] <weshay|ruck> Anything else that folks want to bring up to the meeting? [08:17:07] <EmilienM> weshay|ruck: i'll probably abandon it for now [08:17:12] <weshay|ruck> k.. thanks [08:17:27] <weshay|ruck> anyone else ? [08:17:30] <weshay|ruck> going once [08:17:36] <weshay|ruck> going twice [08:17:43] <marios> weshay|ruck: [08:17:46] <weshay|ruck> #endmeeting tripleo [08:17:49] <marios> do we wantto consider virtual ptg [08:17:53] <marios> weshay|ruck: ? [08:17:54] <weshay|ruck> I'll save the meeting notes [08:17:57] <marios> weshay|ruck: next time then [08:17:58] <marios> ... [08:17:58] <weshay|ruck> marios, that's still not clear [08:18:04] <weshay|ruck> but most likely [08:18:06] <cloudnull> +1 for virt ptg Meeting notes from March 30 2020 <weshay> #topic agenda [08:01:02] <weshay> * Review past action items [08:01:02] <weshay> * One off agenda items [08:01:02] <weshay> * Squad status [08:01:02] <weshay> * Bugs & Blueprints [08:01:02] <weshay> * Projects releases or stable backports [08:01:02] <weshay> * Specs [08:01:02] <weshay> * open discussion [08:01:02] <weshay> Anyone can use the #link, #action and #info commands, not just the moderatorǃ [08:01:02] <weshay> Hey folks! who's around? [08:01:08] <EmilienM> o/ [08:01:18] <ekultails> o/ [08:01:20] <Tengu> ybe [08:01:22] <fultonj> o/ [08:01:24] <rlandy> o/ [08:01:27] <weshay> EmilienM, aye.. I'll get into that [08:01:28] <Tengu> *maybe [08:02:28] <tkajinam> o/ [08:02:30] <ysandeep|rover> o/ [08:02:36] <mwhahaha> o/ [08:02:42] <chandankumar> \o/ [08:04:24] <marios> o/ [08:05:05] <beagles> o/ [08:05:05] <weshay> #topic review past action items [08:05:05] <weshay> http://eavesdrop.openstack.org/meetings/tripleo/2020/ [08:05:05] <weshay> None. [08:05:14] <weshay> #topic one off agenda items [08:05:14] <weshay> #link https://etherpad.openstack.org/p/tripleo-meeting-items [08:05:27] <weshay> ok.. virt ptg.. /me pastes from the agenda some info [08:05:38] <weshay> * Virtual PTG for TripleO [08:05:38] <weshay> * https://etherpad.openstack.org/p/tripleo-victoria-topics [08:05:38] <weshay> * http://lists.openstack.org/pipermail/foundation/2020-March/002854.html [08:05:38] <weshay> * https://www.openstack.org/events/opendev-ptg-2020/ [08:05:38] <weshay> * https://etherpad.openstack.org/p/Virtual_PTG_Planning?_ga=2.148734014.82059… [08:05:38] <weshay> [08:05:38] <weshay> * planning email sent out by foundation - dates for ptg virt event not yet know. [08:05:38] <weshay> * dates for planning [08:05:38] <weshay> - April 2nd at 12:00 UTC [08:05:38] <weshay> - April 6th at 17:00 UTC [08:05:38] <weshay> - April 7th at 2:00 UTC [08:05:38] <weshay> [08:05:53] <arxcruz> o/ [08:06:08] <weshay> I'm going to join the last two mtgs there on the 6th and 7th... [08:06:38] <weshay> once we get dates.. we'll be sending out a email to confirm who would like to attend.. just like previous in person ptg's [08:07:05] <weshay> any questions about the ptg in general before we get into tripleo specific ptg topics [08:07:17] <weshay> hello [08:07:23] <weshay> is it me your looking for? [08:07:23] <marios> weshay: hav we considered the details ... sessions will be in bluejeans? or irc? [08:07:26] <marios> weshay: timezones? [08:07:30] marios maciejjozefczyk Madkiss mandre marbindrakon matbu [08:07:38] <marios> weshay: ah i see you have time already there [08:07:43] <weshay> marios, I assume that will be addressed in these planning sessions [08:08:02] <weshay> note.. those dates are NOT the ptg.. they are PLANNING events FOR the ptg [08:08:05] <weshay> :) [08:08:06] <gfidente> o/ [08:08:07] <marios> weshay: k (the times you have there are for the planning) [08:08:07] <marios> ack [08:08:12] <weshay> aye [08:08:25] <weshay> there is a sign up sheet for the planning.. if you are interested [08:08:34] <weshay> OK.. thanks for responding [08:08:36] <weshay> marios++ [08:08:37] <marios> weshay: perhaps this can just be worked out amongst the folks interested in each session... and we don't need to mandate a way/time [08:08:57] <weshay> there is no mandate for ptg.. volunteers only :) [08:09:08] <weshay> so.. TLDR.. details pending on ptg [08:09:15] <weshay> now for tripleo [08:09:15] <weshay> https://etherpad.openstack.org/p/tripleo-victoria-topics [08:09:37] <weshay> as usual.. please add topics to this list, w/o topics we have no agenda [08:09:57] <weshay> I'll be adding a few myself :) [08:09:59] <marios> weshay: we could overview/presentation about the component pipeline & how it affect how we promote now [08:10:05] * markllama (~mark5163(a)72.32.180.178) has joined [08:10:07] marios maciejjozefczyk Madkiss mandre marbindrakon markllama matbu [08:10:13] <EmilienM> marios++ [08:10:44] <weshay> marios, yes.. usually there is an hour for CI at the ptg.. the new dlrn structure and component based ci is a good topic imho [08:11:02] <Tengu> +42 [08:11:42] <weshay> I would assume that new features.. validation, ansible collections, tripleo-operators should be added to the topic list [08:11:48] <weshay> tripleo-ansible etc [08:12:09] <weshay> any questions about tripleo + ptg? [08:12:27] <Tengu> I'll check with my folks about the validation part. [08:12:32] <weshay> +1 [08:12:39] <Tengu> maybe the container would be nice. [08:13:11] <weshay> EmilienM, you have anything to add? [08:13:36] <EmilienM> not now, indeed we need to come with more topics [08:13:44] <EmilienM> I'll try to gather some from the team [08:14:05] <weshay> ya.. I am looking for parity from previous ptg's.. minus the last one [08:14:32] <weshay> we did not have a lot of folks in china for the last ptg.. and I would expect a backlog of topics [08:14:45] <weshay> so we'll be covering that here for a few weeks I'm sure [08:14:47] <weshay> anyhoo [08:14:50] <weshay> #topic Active Squad status [08:14:50] <weshay> ci [08:14:50] <weshay> #link https://hackmd.io/IhMCTNMBSF6xtqiEd9Z0Kw?both [08:14:50] <weshay> validations [08:14:50] <weshay> #link https://etherpad.openstack.org/p/tripleo-validations-squad-status [08:14:50] <weshay> ceph-integration [08:14:50] <weshay> #link https://etherpad.openstack.org/p/tripleo-integration-squad-status [08:14:50] <weshay> transformation [08:14:50] <weshay> #link https://etherpad.openstack.org/p/tripleo-ansible-agenda [08:14:50] <weshay> mistral-to-ansible [08:14:50] <weshay> #link https://etherpad.openstack.org/p/tripleo-mistral-to-ansible [08:14:56] <weshay> where is the bot? [08:14:57] * haleyb (haleyb@nat/redhat/x-koblohkdhoozsgkh) has joined [08:15:09] <weshay> dang [08:15:26] <weshay> second week in a row.. I'll look into why the meeting bot is not active.. [08:15:32] * bogdando has quit (Ping timeout: 256 seconds) [08:15:48] <weshay> ok.. the point now of calling squads... again... is to facilitate reviews [08:16:02] <weshay> in a more public fashion [08:16:20] <cloudnull> o/ [08:16:27] <weshay> so just a reminder... guidance is to spend 30-60 minutes per day reviewing other peoples code [08:16:32] * bnemec (~bnemec(a)96-41-255-59.dhcp.eucl.wi.charter.com) has joined [08:16:55] <weshay> if you are not doing that.. you're doing opensource wrong :) [08:17:00] <cloudnull> ++ [08:17:32] <weshay> so.. w/o calling out folks specifically... anything that needs attention? [08:18:12] <cloudnull> work on removing mistral is going great: https://review.opendev.org/#/q/starredby:cloudnull+status:open,n,z - these are some reviews that are inflight and we'd greatly appreciate if folks could take a look at them. [08:18:21] <weshay> ++ [08:18:35] <marios> weshay: '3 a day' ;) [08:18:42] <weshay> ++ [08:18:49] <marios> used to be a minimum requirement to be core [08:19:08] <weshay> ya.. hasn't changed.. [08:19:21] * markllama has quit (Ping timeout: 256 seconds) [08:19:24] <marios> weshay: yeah but it used to be enforced more enthusiastically ;) [08:19:26] <weshay> well.. I can show everyone what we look for in cores.. I'll add that to next weeks agenda [08:19:36] <marios> s/enthusiastically/stricly [08:19:41] <marios> strictly even you know what i mean [08:19:49] <weshay> ya.. VERY open in ideas to help facilitate reviews.. [08:20:04] <weshay> all projects struggle w/ that.. but new ideas are welcome [08:20:18] <openstackgerrit> Rabi Mishra proposed openstack/python-tripleoclient master: Fix _get_image() of GlanceClientAdapter to call find_image() https://review.opendev.org/716277 [08:20:20] <weshay> ok.. /me ends the lecture [08:20:31] <weshay> #topic Moderately Active Squads [08:20:31] <weshay> Ironic-integration [08:20:31] <weshay> https://etherpad.openstack.org/p/tripleo-ironic-integration-squad-status [08:20:31] <weshay> upgrade [08:20:31] <weshay> #link https://etherpad.openstack.org/p/tripleo-upgrade-squad-status [08:20:31] <weshay> edge [08:20:31] <weshay> #link https://etherpad.openstack.org/p/tripleo-edge-squad-status [08:20:31] <weshay> networking [08:20:31] <weshay> #link https://etherpad.openstack.org/p/tripleo-networking-squad-status [08:20:31] <weshay> Any squad wanting to bring up their status, or a topic for the general public? [08:20:47] <weshay> #link https://launchpad.net/tripleo/+milestone/ussuri-3 [08:20:58] <Tengu> validations: we're aiming to get our code in train [08:21:08] <Tengu> at least for the new packages - validations-common and validations-libs. [08:21:16] <weshay> 5 New, 28 Incomplete, 5 Invalid, 5 Won't Fix, 4 Confirmed, 378 Triaged, 120 In Progress, 2 Fix Committed, 189 Fix Released [08:21:26] <weshay> Tengu++ [08:21:46] <Tengu> doing so will allow to get a clean code and, well, make our life easier on Red Hat side. [08:21:49] <weshay> Tengu, I see ptg topics in your future :) [08:22:00] * bnemec has quit (Read error: No route to host) [08:22:03] <Tengu> weshay: yep, maybe ;). [08:22:19] <Tengu> (hint: just dropped a mail to my team ;)) [08:22:21] <weshay> so.. bug triage will continue as I have time... just a reminder anything older than 365 days and in new.. will be closed [08:22:40] <weshay> Storyboard bugs. [08:22:40] <weshay> #link https://storyboard.openstack.org/#!/project_group/76 [08:23:02] <weshay> reminder.. be nice to the infra folks and folks driving storyboard... volunteer effort there.. [08:23:16] <openstackgerrit> Martin Kopec proposed openstack/ansible-role-collect-logs master: Extend infrared molecule tests https://review.opendev.org/705552 [08:24:27] * weshay notes... [08:24:40] <weshay> now is the time to start thinking about blueprints and specs for the next cycle [08:24:49] <weshay> here's a dump on ussuri [08:24:50] <weshay> Medium ansible-certmonger Approved Unknown Cédric Jeanneret ussuri [08:24:50] <weshay> Medium ironic-overcloud-ci Approved Slow progress Derek Higgins ussuri [08:24:50] <weshay> Medium multiarch-support Approved Good progress Tony Breeds ussuri [08:24:50] <weshay> Medium nova-less-deploy Approved Good progress Steve Baker ussuri [08:24:50] <weshay> Medium replace-keepalived-undercloud Approved Good progress Emilien Macchi ussuri [08:24:50] <weshay> Medium split-controlplane-workflow Approved Unknown ussuri [08:24:50] <weshay> Medium remove-puppet Drafting Not started Emilien Macchi ussuri [08:24:50] <weshay> Medium tripleo-firewall-rule-reporting New Not started ussuri [08:24:50] <weshay> Undefined tripleo-mistral-to-ansible Approved Good progress Dougal Matthews ussuri [08:25:07] * Tengu hides [08:25:34] <openstackgerrit> Martin Kopec proposed openstack/ansible-role-collect-logs master: Extend infrared molecule tests https://review.opendev.org/705552 [08:25:48] <weshay> ekultails, looks like progress on https://review.opendev.org/698828 [08:25:56] <weshay> Add spec for AWX integration. [08:25:58] <weshay> FYI ^ [08:26:17] <EmilienM> replace-keepalived-undercloud is WIP and waiting on HA byd efault, blocked by not having upgrade jobs on centos8 [08:26:29] <EmilienM> remove-puppet is not in progress, I'm not working on it [08:26:30] <Tengu> for the ansible-certmonger, it's in the Security capable hands, not mine... I just pushed the idea ^^' [08:26:48] <Tengu> ade_lee: -^^ [08:26:55] <weshay> aye.. EmilienM working in the background on that for you... getting advice on the priority for train + centos8 [08:27:43] <weshay> need help reviewing https://review.opendev.org/#/c/715734/ Add new project and repository for tripleo-compute-extras [08:27:45] <weshay> as well folks [08:28:08] <weshay> k.. /moving on [08:28:12] <weshay> #topic open discussion [08:28:12] <weshay> Anything else that folks want to bring up to the meeting? [08:28:26] <weshay> FYI.. I've nominated myself for ptl in victoria.. [08:28:32] <EmilienM> yay! [08:28:34] <Tengu> weshay: you'll get my vote for ptl :) [08:28:45] <fultonj> +1 [08:28:59] * zzzeek has quit (Quit: bye) [08:29:00] <weshay> I would like to help others this cycle better understand what is involved.. and the how-to's to the best of my ability :) [08:29:21] <weshay> so if you are interested in perhaps being ptl.. after victoria.. let me know and I'm happy to walk through it [08:29:50] <weshay> that's it from me.. anyone else have anything new? [08:30:14] <weshay> once [08:30:15] <weshay> twice [08:30:18] <weshay> #endmeeting tripleo [08:30:23] <weshay> thanks all :)

2 2

[election][octavia][ptl] Announcing my PTL candidacy for Octavia
by Michael Johnson 01 Apr '20

01 Apr '20

My fellow OpenStack community, I would like to nominate myself for Octavia PTL during the Victoria cycle. I have previously led the team during the Stein release, and I would like to continue helping our team provide network load balancing services for OpenStack. Looking forward to Victoria I expect the team to finish some major new features, such as the Jobboard transition and introducing HTTP/2 support. Thank you for your support and your consideration for Victoria, Michael Johnson (johnsom)

2 1

[tempest] what is a proper way to install a package into a vm instance spawned by tempest?
by Roman Safronov 01 Apr '20

01 Apr '20

Hi, I wrote a tempest test <https://review.opendev.org/#/c/710975/https://review.opendev.org/#/c/710975/)> which requires keepalived to be running inside vm instance. The test tries to install keepalived package inside vm by running "apt install/yum install". However as I see in upstream gates logs this does not work while the same code works perfectly in our downstream CI using the same image. Do vm instances spawned on upstream gates during tests have a route to the internet? Is there an alternative way that I can use in order to install a package? Thanks in advance -- ROMAN SAFRONOV SENIOR QE, OPENSTACK NETWORKING Red Hat <https://www.redhat.com/> Israel M: +972545433957 <https://red.ht/sig>

4 6

[tosca-parser][heat-translator][tacker] - Need new version of heat-translator and tosca-parser libraries for Tacker
by Patil, Tushar 31 Mar '20

31 Mar '20

Hi PTL and Core Reviewers, We are working on implementing ETSI spec in tacker for Ussuri release for which we have pushed couple of patches in heat-translator [1][2] and tosca-parser[3]. Patch [1] is not yet merged so request core reviewers to please take a look at it. We have uploaded many patches in tacker [4] but most of the patches are failing on CI as it's requires changes from heat-translator and tosca-parser. So we need a new release of heat-translator (after patch [1] is merged) and tosca-parser badly. Please let us know when are you planning to release a new version of these libraries. [1] : https://review.opendev.org/#/q/status:merged+project:openstack/heat-transla… [2] : https://review.opendev.org/#/q/status:open+project:openstack/heat-translato… [3] : https://review.opendev.org/#/c/688633 [4] : https://review.opendev.org/#/q/topic:bp/support-etsi-nfv-specs+(status:open… Thank you. Regards, tpatil Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding.

1 2

[election][ptl][swift] Tim Burke candidacy for Swift PTL
by Tim Burke 31 Mar '20

31 Mar '20

It would be my honor and pleasure to continue serving you as Swift PTL. The world continues to generate and retain ever-increasing amounts of data, and Swift continues to rise to the challenge of storing that data durably and making it highly available. I'm excited to help us engineer now to be ready for next year's data-center demands. To that end, there are several projects we'll be advancing; in general, these are not short-term, though some pieces will surely come in the next cycle. As hard-drive sizes increase, the lots-of-small-files problem has become a lots-of-files problem. Between 16TB hard drives hitting the market and cost concerns pushing us toward ever more drives per box, even historically "reasonable" object sizes will produce noticeable memory pressure that we'd like to reduce. OVH's explorations in this space give us all a leg up that we should take advantage of. As clusters grow, we must ensure Swift can scale with them. Some aspects of that will be relatively straight-forward, like allowing rings to support more than 64k devices. Other challenges are less well-defined; there are likely improvements that could be made in replication and backend protocols, for example, but there is no single way forward. There will likely be some experiments that never land on master -- but as long as they are in the open and we can all learn from them, they will not be failures. All of that must be driven by what we learn by operating real clusters at scale. To do that, we must improve our metrics and monitoring, and find ways to observe the system dynamically. Post-facto log analysis is not tenable when dealing with tens of thousands of requests per second across hundreds of nodes. At the same time, we cannot neglect our client ecosystem. This extends not just to python-swiftclient, but to S3 clients as well. For better or worse, S3 has become the de facto standard interface for object storage, and we must ensure our compatibility is as seamless as possible. This cycle we added S3-compatible versioning, but there is so much more we could be doing, from object life-cycle management to bucket inventories. As always, we will listen to our users and prioritize addressing their pain points. Tim Burke ----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. -----------------------------------------------------------------------------------

1 0

[elections][tc] Nomination
by Radosław Piliszek 31 Mar '20

31 Mar '20

Dear Fellow OpenStackers, I am Radosław Piliszek (yoctozepto) and I am proposing myself as a TC candidate starting Victoria cycle. For the record, I have never been in TC nor a PTL... yet. I am affiliated with a relatively small Polish university: University of Białystok, with the local Computing Centre offering services to local academics. My experience is broad in that this work involves being a whole IT department at once. :-) OpenStack piqued my interest in 2018 when I joined the Foundation as an individual member. Since then I made myself COA (Certified OpenStack Administrator), learnt the jump from "administrator" to "operator" while deploying locally various PoC instances of basic OpenStack services and finally started contributing upstream via bug reports, patches and reviews. I was (and am!) really proud to have been recognized Kolla core due to my work with fellow project members. Later on, DevStack core nomination followed for which I am grateful as well. In the Kolla project I work mostly on ensuring sanity, enhancing testing and fixing current issues while helping fellow contributors to deliver their features and fixes. I also managed to deliver a bigger change in the Train cycle: all-around IPv6-only networking support. I enjoyed the cross-project aspect of this and decided to contribute a bit to the development experience as well and this is how I ended up DevStack core (true story). Nowadays I am wearing multiple hats in the wide community and many of you probably recognize me from IRC where I try to be helpful but also ask questions around (often technical ones like: to be or not to be?). One could say I'm inquisitive (hopefully in the good sense of this word) and in fact I value highly a deeper insight into the problem at hand (probably due to bad experience with hasty actions!). I react to issues quite quickly (bothering infra from time to time - I am really sorry, you folks are doing great job!) and work on solutions with fellow OpenStackers (aka you) which brings real joy and makes experience real. I have a few, rather broad, goals (or thoughts?) of mine: 1) To test, test and test. My motto is: "not tested = not working". Unfortunately, this is actually often the case in reality. :-( Hence, I encourage thorough testing, especially at the functional and integration level. I believe we need to be reliable to be trustworthy. 2) To make OpenStack easily consumable by small companies, especially in public academia but not only. Everyone deserves a good private cloud experience with decent learning curve. This involves prompt and current documentation but also reliable base for installs. (1) and (2) culminate in (3) [1+2=3 - could not have been simpler!] 3) Who are we? BUILDERS! What do we want? TO BUILD! (I hope you know the meme!) Ultimately OpenStack is software built for specific purpose and is meant to be consumed by cloud operators. We have plenty of ways to get OpenStack "installed" but officially we still rely on the archaic assumption that everything is thrown in the same environment. This is rarely the case nowadays due to various layers of separation being applied: virtual envs, OCI images. It would be beneficial to be able to rely on prebuilt official images of OpenStack services and their prerequisites, also for CI. We don't need to rebuild/reinstall keystone, glance, nova and swift just to test neutron that one more time, only to discover pip hangs installing dep of dep of not-even- neutron due to random networking issue.* Similarly this is wasted effort in case of multinode testing. Multiply this by the amount of scenarios and... well, you probably get the picture. I know we can do better: deliver more reliability via more reliability. * Order random for example purposes. This is as many relevant bits as I thought necessary to introduce my candidacy and share my mind with you. Thank you for reaching this far. Radosław Piliszek (yoctozepto) https://review.opendev.org/716363

1 0

[tc][elections] Nomination for TC
by Tobias Rydberg 31 Mar '20

31 Mar '20

Hi fellow Stackers, My name is Tobias Rydberg and I will by this email announce my candidacy for the OpenStack Technical Committee. For those who (yet) don't know me, I'm employed by the cloud provider City Network and through that I've been around and worked with OpenStack since 2014 when we as City Network started our OpenStack journey. I'm a simple person that speak my mind, love to have fun and get to know new people and technologies - and I have to say that being part of this community ticks a lot of those boxes. During the last couple of years I've been chair for the Public Cloud SIG (previously WG), and in that role you might have seen me hosting Forum sessions at all Summits since the Forum was introduced, spreading the word of why OpenStack is super important for public clouds (the Public Cloud Passport Program is a child of PC SIG) and what is still missing... ;-) Even though I'm a developer from the get go, I haven't done a lot of code contributions over the years, but I have tried to contribute in various other ways where being SIG chair is one, driving discussions in the Forums and being part of organising OpenStack days events (Nordic). So, what can I bring to the table? I believe that my background (and precent) with multiple years of running multiple public and private clouds will bring a lot of operator experience. We've over the years also been very focused to deliver OpenStack to customers with very high regulatory compliance demands, such as banks, health care, insurance industry, and as I see it, that is a pretty hot potato right now and I believe that will not cool down for some time. I my current role I have the blessing of talking a lot with customers building their services on top of OpenStack, listening to their experience and feedback - everything from how hard it can be to find the correct piece of documentation to limitations that hinders them from choosing OpenStack as a platform for their service - valuable feedback that not always reach the community. I think that the continued success of OpenStack (for at least 10 more strong years) lies in the hands of the "operators" - the people and the companies that live and breathe OpenStack - the people and the companies that have the experience how OpenStack operates in all the different use cases you can't predict in a public cloud. This is my first time running for a chair at the TC table, my experience of sitting in such chair is by that pretty limited, but I care a lot about this awesome community and I'm eager to learn and to do my fair share to make this community a success to the years to come... Thanks for taking the time to read and to consider my candidacy! Cheers, Tobias

1 0

Upcoming pip changes - stop installing test-requirements in devstack
by Monty Taylor 31 Mar '20

31 Mar '20

Heya, Recently we had to revert a change to devstack that ran pip check. This is a recommendation from the pip team to verify that upcoming addition of a depsolver to pip isn’t going to break us. Well - it is going to break us. The reason it’s going to break us is that we don’t apply constraints to linters (so that projects can deal with those at their own rate) BUT - we install every project’s test-requirements.txt (containing the linters) when we run devstack. That means we uninstall and reinstall flake8 at different versions over and over again - and the final state is not one that is completely consistent. I’ve pushed up this: https://review.opendev.org/#/c/715469/ Which is a patch to stop installing test-requirements in devstack. Realistically we should not need to install this in devstack. Devstack is installing the software which does not need test-requirements - and then we test it with tempest which has its own set of requirements. As a side benefit, devstack is quicker and none of the non-voting jobs on devstack fail now. It’s possible this change could impact people using devstack as a base for single-project functional tests - so it’s worth being careful with. But I think we should get it done and then re-add the pip check as a verification that we’re not going to get broken this summer. Monty

4 4

[charms][ptl][election] PTL Non-candidacy
by Frode Nordahl 31 Mar '20

31 Mar '20

Hello all, The Ussuri cycle is coming to an end and the contributors to the Charms project has done great progress in the key areas we set afoot at the beginning of the cycle. We have also had good participation from the broader community and I hope to see that flourish further in the coming cycles. I believe rotating leadership for open source projects is a good thing and I am happy to pass on the relay baton for the Victoria cycle. -- Frode Nordahl

1 0

[all][elections][ptl][tc] Conbined PTL/TC Nominations Last Days
by Kendall Nelson 31 Mar '20

31 Mar '20

Hello Everyone! A quick reminder that we are in the last hours for declaring PTL and TC candidacies. Nominations are open until Mar 31, 2020 23:45 UTC. If you want to stand for election, don't delay, follow the instructions at [1] to make sure the community knows your intentions. Make sure your nomination has been submitted to the openstack/election repository and approved by election officials. Election statistics[2]: Nominations started @ 2020-03-24 23:45:00 UTC Nominations end @ 2020-03-31 23:45:00 UTC Nominations duration : 7 days, 0:00:00 Nominations remaining : 8:25:21 Nominations progress : 94.99% --------------------------------------------------- Projects[1] : 60 Projects with candidates : 0 ( 0.00%) Projects with election : 0 ( 0.00%) --------------------------------------------------- Need election : 0 () Need appointment : 60 (Adjutant Barbican Blazar Cinder Cloudkitty Congress Cyborg Designate Ec2_Api Freezer Glance Heat Horizon I18n Infrastructure Ironic Karbor Keystone Kolla Kuryr Loci Magnum Manila Masakari Mistral Monasca Murano Neutron Nova Octavia OpenStackAnsible OpenStackSDK OpenStack_Charms OpenStack_Helm Openstack_Chef Oslo Packaging_Rpm Placement Puppet_OpenStack Qinling Quality_Assurance Rally Release_Management Requirements Sahara Searchlight Senlin Solum Storlets Swift Tacker Telemetry Tricircle Tripleo Trove Vitrage Watcher Winstackers Zaqar Zun) =================================================== Stats gathered @ 2020-03-31 15:19:39 UTC This means that with approximately 2 days left, 60 projects will be deemed leaderless. In this case the TC will oversee PTL selection as described by [3]. Thank you, Kendall Nelson(diablo_rojo) & the Election Officials [1] https://governance.openstack.org/election/#how-to-submit-a-candidacy [2] Any open reviews at https://review.openstack.org/#/q/is:open+project:openstack/election have not been factored into these stats. [3] https://governance.openstack.org/resolutions/20141128-elections-process-for…

1 0

[blazar][election][ptl] PTL candidacy for Victoria
by Pierre Riteau 31 Mar '20

31 Mar '20

Hi, I would like to self-nominate to serve as PTL of Blazar for the Victoria release cycle. I have been PTL since the Stein cycle and I am willing to continue in this role. As with many other projects, we are struggling with a lack of contributions. My focus will be to keep our small community active, help new contributors to be more involved in the project, and deliver functionality that will encourage further adoption. Thank you for your support, Pierre Riteau (priteau)

2 1

[nova] Proposing Ghanshyam Mann as nova core
by Balázs Gibizer 31 Mar '20

31 Mar '20

Hi, I'm proposing Ghanshyam Mann to the core team. He is a long time OpenStack and nova contributor. He is one of our API and QA expert. I think he would be a great addition to the team. Cores, please vote (-1, 0, +1) before next Monday (03.30.) Cheers, gibi

8 8

[nova] Proposing Lee Yarwood as nova core
by Balázs Gibizer 31 Mar '20

31 Mar '20

Hi, I'm proposing Lee to the core team. He is around for a long time and he became really active recently not only on the stable branches. I think he would be a great addition to the team. Cores, please vote (-1, 0, +1) before next Monday (03.30.) Cheers, gibi

8 8

[tc][election] Add Rico Lin candidacy for Victoria TC role
by Rico Lin 31 Mar '20

31 Mar '20

Dear all, It has been a great year for me to work on TC and work as TC vice-chair, and I do like to join TC election again and keep serving this community as TC member if I have the honor. In the past year, I have been working on the following tasks: * TC vice-chair: I thank for the vice-chair roles allows me to dive in deeper on TC activity. As we work on TC's daily support for TC chair. IMO, JP shows some nice example to running TC chair by standardizing routine processes. And I do feel it's great to work with him. And from what I learned, to consistent checking on actions for TCs is something we should keep on. Also ML update and host meetings. What I think we should try in advance are keep pushing TC plus UC merging task, and work on providing better decision system so we can make sure at the end of discussion, we have something put into actions and that's been decided by TCs as a group. * Meta SIG chair: It's a great opportunity to working on SIG govern, which works with coordination between devs, ops, and users. We achieved on items like pushing more new SIGs, create SIG guidelines, track SIG status, and of course general SIG govern stuff. But SIGs still needs more attention. Which is one of the goals I have to push SIG forward (And I'm happy to have others as Meta SIG chair). IMO SIG only successful when it can provide a better bridge across all roles. That's something we need to keep pushing our effort to expose SIGs. * Comparison of Official Group Structures: I also work on providing [1] so whoever join this community, can have better understanding on how we works. Over time, our structure require changes, so we can evolve and provide understandable structures for the whole time (and for old and new members). What we can keep working on is to consistently review the structure flow, to make sure everything makes sense for a community to allow consistency and evolution. Also as mentioned, to combine TC and UC, will require more review on structure to make sure teams all get benefits from the achievement we plan. * Cross culture bridge: This is something I'm reeeally proud of. To help community members reach better communication despite language, culture, and timezone barriers. I get the honor to serve a great number of community members on this task, and I'm proud of it. This also alerts me that we need more members in community to become the bridge. We have some great people to keep working on this, but we simply need more from different languages, cultures, and timezone. So community members can have a better way to reach to TCs. * community goal schedule: gmann doing really good job on keep community-wide goal forward. As we implemented our goal schedule to cover from pre-select, select, and implementation schedule. I'm planning to keep govern that process to make sure we jump in the correct routine. [1] https://governance.openstack.org/tc/reference/comparison-of-official-group-… -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin

1 0

[nova] FFU : When should we remove reshape support for a feature ?
by Sylvain Bauza 31 Mar '20

31 Mar '20

Hola, In Stein, I provided a new feature [1] that was checking inventories from multiple children resource providers (RP). Since in Rocky, those inventories were only on the root RP, I had to provide both : #1 : an upgrade support for RPs that were not having a parent RP (that was the case of Stein compute nodes) [2] #2 : a reshape method in the libvirt driver for moving allocations from a root RP to children RPs [3] Now, we're in the Ussuri timeframe and as I was usually doing, I removed the upgrade support (in #1) since we're 100% sure that all compute nodes are either Train or Ussuri [4] This is cool, but now the reshape code I wrote for #2 no longer works (which is normal, since the 'non-Stein' support was removed) [5] Soooooo. Can I also then remove the reshape support ? That would mean that upgrading from Rocky to Train would work, but Rocky to Ussuri wouldn't. I'm personally OK with this, but I guess other people could have concerns with. Do we have any consensus about how longer we would support a reshape ? I think honestly that a 3-releases time window is enough but I can hear some disagreements about this strawman proposal. If so, please voice. -Sylvain [1] https://blueprints.launchpad.net/nova/+spec/vgpu-stein [2] https://review.opendev.org/#/c/636591/ [3] https://review.opendev.org/#/c/599208/ [4] https://review.opendev.org/#/c/715489/ [5] https://541e2403478ac154d5eb-056bfb946e355d1a1a86dc411a70c5ec.ssl.cf2.rackc…

3 3

[all][elections][ptl][tc] Conbined PTL/TC Nominations Last Days
by Ian Y. Choi 31 Mar '20

31 Mar '20

A quick reminder that we are in the last hours for declaring PTL and TC candidacies. Nominations are open until Mar 31, 2020 23:45 UTC. If you want to stand for election, don't delay, follow the instructions at [1] to make sure the community knows your intentions. Make sure your nomination has been submitted to the openstack/election repository and approved by election officials. Election statistics[2]: Nominations started @ 2020-03-24 23:45:00 UTC Nominations end @ 2020-03-31 23:45:00 UTC Nominations duration : 7 days, 0:00:00 Nominations remaining : 9:22:53 Nominations progress : 94.42% --------------------------------------------------- Projects[1] : 60 Projects with candidates : 30 ( 50.00%) Projects with election : 0 ( 0.00%) --------------------------------------------------- Need election : 0 () Need appointment : 30 (Adjutant Barbican Blazar Cloudkitty Congress Cyborg Designate Freezer Heat I18n Infrastructure Karbor Loci Magnum Manila Masakari Nova Octavia OpenStack_Charms Oslo Packaging_Rpm Placement Quality_Assurance Rally Requirements Searchlight Swift Tacker Tricircle Zaqar) =================================================== Stats gathered @ 2020-03-31 14:22:07 UTC This means that with approximately 2 days left, 30 projects will be deemed leaderless. In this case the TC will oversee PTL selection as described by [3]. Thank you, [1] https://governance.openstack.org/election/#how-to-submit-a-candidacy [2] Any open reviews at https://review.openstack.org/#/q/is:open+project:openstack/election have not been factored into these stats. [3] https://governance.openstack.org/resolutions/20141128-elections-process-for…

1 0

[kolla] Tomorrow's meeting cancelled
by Mark Goddard 31 Mar '20

31 Mar '20

Hi, I'm on leave tomorrow and several cores are unavailable so let's skip this week's meeting. Please bear in mind we're approaching OpenStack feature freeze, and our own freeze will follow shortly afterwards. As such, please focus on finishing off and reviewing our cycle priorities. Cheers, Mark

1 0

[qa] Not running for PTL
by Ghanshyam Mann 31 Mar '20

31 Mar '20

Hello Everyone, I would like to announce that I am not running for QA PTL for V cycle. Its been 4 cycles for me as the QA PTL and I think it's time for a new leader to take this responsibility. It has been a great experience for me as PTL and keeping the QA program healthy and active as it was from starting. Stabilizing the testing more and adopting new tooling under QA. Apart from PTL role, I will continue my contribution to QA with the same bandwidth as it is now. There is no change in that and you can keep pining me for any issue or discussions. Also, I will be there for a smooth PTL transition. Thanks everyone for making these 2 years a great learning period for me. -gmann

2 1

[election][heat] PTL candidacy for Victoria
by Rico Lin 31 Mar '20

31 Mar '20

Hi all, I would like to announce my candidacy for Heat PTL for Victoria cycle. Over the past couple of cycles, we running Heat dynamically according to requirements. We never stop encouraging people to join us and provide consistent reviews or fixes as much as we can basic on priorities. And if those priorities not working for you, that means you must join the community to help. I believe the goals for the next cycle should be community CI stability, cross-project/community scenario tests to ensure what we deliver to users will get higher quality and container-native support to make sure we provider useable Orchestration services for container environment. I believe in new features, so we will try to encourage more features and review them as many as possible, but will not plan for team feature goals unless we can trigger more discussion and hands-on.Thank you for taking my self-nomination into consideration. Rico Lin -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin

1 0

[election][kolla]
by Mark Goddard 31 Mar '20

31 Mar '20

Hi, I'd like to nominate myself to serve as the Kolla PTL for the Victoria cycle. I have been PTL for the Train and Ussuri cycles, and would like the opportunity to continue to lead the team. I am pleased with the current state of the project. We have an active community, produce interesting and useful features, and regularly receive positive feedback. The Kolla community has always been notable for being vendor-neutral and operator-driven. I recently made a proposal for a Kolla --SIG-- Club [1] with the aim of improving communication between regular contributors and the wider community. We had a good response, and I'm looking forward to seeing how it progresses this cycle. If elected this cycle I'd like to encourage continued work on some familiar themes - improving sustainability, increasing test coverage, and better integrating Kayobe [2]. I'd also like to see us focus on our documentation. Thanks for reading, Mark Goddard (mgoddard) [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-March/013122.ht… [2] https://docs.openstack.org/kayobe

3 2

[Murano-Open-PaaS] Openstack using guacamole
by Roman Gorshunov 31 Mar '20

31 Mar '20

Hello Samuel, Thanks for your email. Yes, Guacamole can be installed as an app via Murano. Discussions about Open PaaS are now in openstack-discuss mailing list. Please use the tag [Murano-Open-PaaS] in the subject line. I'm re-routing your email. Here are docs for the Murano project [0]. [0] https://docs.openstack.org/murano/latest/ Best regards, Roman Gorshunov On Thu, Mar 26, 2020 at 4:37 PM Samuel Abdullah <samuel(a)silverliningsys.com> wrote: > Hi, > > Would like to ask if it is possible to run guacamole in openstack > environment? > Seek for help on how would this be possible as i saw that guacamole > component are part of the openstack in your murano project > > Looking forward for your reply > > Best Regards > > -- > > <https://www.silverliningsys.com/> > > www.silverliningsys.com > > > *Abu Bakar Samuel Abdullah* > > Cloud Infrastructure & Operations > > > P: +603-2712-0081 > > M: +60.12.654.5938 > > E: samuel(a)silverliningsys.com > _______________________________________________ > OpenStack-Infra mailing list > OpenStack-Infra(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

3 4

[tc][elections] Nomination
by Belmiro Moreira 31 Mar '20

31 Mar '20

Greetings, I'd like to announce my candidacy for the OpenStack Technical Committee (TC). I'm involved with OpenStack since 2011 when CERN started to investigate a Cloud Infrastructure solution. I work in the design/deployment/operation of the CERN OpenStack Cloud. My particular interest has been how to scale and operate large OpenStack deployments. I was an active member of the old Large Deployment Team (LDT), a group of operators that shared ideas on how to scale OpenStack. I had the privilege to learn from a talented group of Operators on how they manage/run their infrastructures. Currently, a new group was created (Large Scale SIG) where I continue to have an active role. I'm fortunate enough to have attended most of the OpenStack Summits since San Francisco (2012). I'm a regular speaker talking about my experience operating OpenStack at scale. Also, I serve regularly as a track chair, participated in few OpenStack Days, Ops Meetups and wrote several blog posts. During the last year I served as a member of the OpenStack User Committee (UC). We focused in the Ambassador Program revamp and SIGs support. If elected I will focus to engage the Operator/Users community with the different Development teams and bring my experience as Developer/Operator to the group to help in the oversight on all the technical matters. It would be an honor to be an advocate of this great community and promote its mission. Thank you for your consideration, Belmiro Moreira

1 0

Add Masayuki Igawa candidacy for Quality_Assurance
by Masayuki Igawa 30 Mar '20

30 Mar '20

Hi everyone, I'd like to announce my candidacy as the PTL for the Quality Assurance PTL role for the Victoria cycle. First off, I would like to thank you all the contributors, core reviewers, PTLs, and anyone who involves and makes the OpenStack better. Let me introduce myself briefly. I have joined the OpenStack community since 2012 as a developer. Now, I'm a core member of some QA projects such as Tempest, os-testr, OpenStack-health, stackviz, coverage2sql, subunit2sql[1]. And I also played the mentors/instructors role at the upstream training in Japan several times. It was a great experience to know how difficult of telling people how OpenStack community is going. In the Ussuri cycle, we've almost completed "Drop Python 2.7 Support"[2] which is one of the Ussuri goals. We also have been trying to keep the gate stable which is the mission of the team. And we approved one interesting spec - "Whitebox Tempest Plugin"[3] which is one of the tempest plugins. It can access controller nodes and/or compute nodes such as read and write INI files, restart services, examine the database, etc. Tempest does not cover this feature because it isn't the scope. However, it is necessary to expand automated testing. We still have a few more planned work pending for Ussuri, such as removing/ migrating the .testr.conf to .stestr.conf, RBAC testing, removing tempest plugin sanity BLACKLIST, adding new glance tests, improving Tempest cleanup, etc. But I think we will be able to accomplish them in the Ussuri cycle as we still have around one month for Ussuri release. Along with daily QA activities, my priorities for QA for the next cycle will be: * New ideas for more tooling and/or tests project to focus on OpenStack or common communities. (whitebox tempest plugin, for example) * Stability of Tempest plugins. The sanity job is already voting, and there are 57 tempest plugins[4], but 12 plugins are in the blacklist. Some of the plugins are deprecated already, but it's hard to know from the registry page. It needs to be classified, and the page can be improved. * Guiding and motivating more contributors to QA projects, improving documentation, and advertising OpenStack QA projects. * Completing Ussuri priority items if it's still lasting. It's hard to accomplish without our collaboration. So, let's do it together! [1] http://stackalytics.com/?user_id=igawa [2] https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html [3] https://specs.openstack.org/openstack/qa-specs/specs/other/whitebox-tempest… [4] https://docs.openstack.org/tempest/latest/plugin-registry.html#detected-plu… Thanks for your consideration! -- Masayuki Igawa (masayukig)

1 1

[election][manila] PTL candidacy for Victoria
by Goutham Pacha Ravi 30 Mar '20

30 Mar '20

Greetings Zorillas & other Stackers, I would like to submit my candidacy to be the PTL of Manila for the Victoria cycle. I stepped up to this role for the Ussuri cycle and have had a tremendous learning experience. I achieved numerous things I set out to do with the support and encouragement of my fellow contributors. I'd like to continue in this role and drive the growth of this project and its community. In my role as the liaison for this community, I was able to effectively aid internalizing the "OpenStack way" of development. The project and its many deliverables saw several new contributors in the Ussuri cycle. This included successful Outreachy and Google Summer of Code interns who continue to contribute beyond the completion of their internships. We were able to prune the core maintainers group to active reviewers while mentoring and adding three new individuals. We also had a significant reduction in our bug backlog, while we continue to farm out issues for potential first time contributors. In the Victoria cycle, I plan to continue on this mission of growing the contributor base, and having Manila be a great on-boarding project for the OpenDev community. In the Ussuri cycle, thanks to our Outreachy interns, their mentors and the reviewers, we merged feature functionality to support the OpenStack Client. Similar velocity was achieved in the manila-csi project through the GSoC internship program and the continued investment beyond. We didn't get much merged in the Ussuri cycle in terms of improving the availability and fault tolerance of the core share-manager service. These multi-cycle work items will remain a matter of focus and I'd devote time to drive these further. The Ussuri cycle also saw reducing feature parity between the DHSS=True and DHSS=False driver modes. This was a goal for this community for several releases and it's coming to fruition through vendor-agnostic community driven design. In Victoria, we plan to continue down this patch and eliminate further feature gaps between many deployment and usability choices with Manila. As PTL, I will drive the community through the OpenStack-wide goals during the Victoria cycle, alongside some of our own: - Graduating experimental features: We have had significant soak time for all three features (Share Replication, Share Migration and Share Groups); and we have begun the steps to take them out of their experimental state. - Apply for the "vulnerability-managed" TC tag: As a community, we worked through our first CVE in Ussuri cycle with the aid and support from the OpenStack Vulnerability Management Team. In the Victoria cycle, we'll drive to achieve this TC tag for the project. - Evolve bug triage criteria, and automate it: Seeing an unmanageable number of bugs is a distraction enough to ignore the bug backlog. As a community we discussed the idea of automating some triage tasks on our backlog. - Address testing gaps: We'll continue to add new test case scenarios and address gaps such as the lack of scenario testing for the cephfs-native protocol. While this goal may not have a definition of done, it is here to convey my intention to prioritizing regression testing on par with feature development. So, if you will have me, I wish to serve through Victoria and get things done. Thank you for your support, Goutham Pacha Ravi <gouthampravi(a)gmail.com> IRC: gouthamr [1] https://review.opendev.org/#/c/716107/

1 0

[all] Virtualized PTG Brainstorming Community Meetings
by Kendall Nelson 30 Mar '20

30 Mar '20

Hello Everyone! So! After Marks initial email[1] that announced we would be virtualizing the PTG and collected volunteers[2] to help brainstorm the best way to hold the PTG virtually, we polled the volunteers for the best times to meet. In trying to be the most inclusive we have settled on three meetings to brainstorm together as a community. They are as follows: - April 2nd at 12:00 UTC - April 6th at 17:00 UTC - April 7th at 2:00 UTC We will be using my zoom[3] and continue using the same etherpad [2] that we collected volunteers in for all the notes from all three meetings. All are welcome! And if you can attend more than one meeting, please do! The more overlap we have the more cohesive discussions we will have. Hope to see you all there! -Kendall Nelson (diablo_rojo) [1] http://lists.openstack.org/pipermail/foundation/2020-March/002854.html [2] https://etherpad.openstack.org/p/Virtual_PTG_Planning [3] https://zoom.us/my/diablorojo

1 0

review.opendev.org Downtime March 20, 2020 at 1400UTC
by Clark Boylan 30 Mar '20

30 Mar '20

Hello all, The OpenDev team is planning to take a short downtime March 20, 2020 from 14:00UTC to 15:00UTC. This outage will enable us to rename a few projects and redeploy Gerrit using containers. The container based deployment is an important first step in our longer term plan for upgrading Gerrit to a modern version. We recognize that this will be a disruption during an already disrupted week for many. We feel this is worthwhile as it fits into project release schedules and sets us up well for the future. Thank you for your patience. Feel free to ask us any questions you may have on this thread or in #opendev on Freenode. Clark

4 5

[first contact][all] Meeting Frequency & Time
by Kendall Nelson 30 Mar '20

30 Mar '20

Hello Everyone, In our meeting yesterday[1], the first one of the year, we discussed changing our meeting frequency to once a month and maybe shifting the day/time. I think Tuesday still works for me but an hour or two earlier wouldn't go amiss. If no-one objects to this, I will put a patch up to change the meeting time & frequency next week to monthly instead of biweekly and -Kendall (diablo_rojo) [1] Meeting Log: http://eavesdrop.openstack.org/meetings/fc_sig/2020/fc_sig.2020-03-25-02.39… [2] Current Meeting Info: http://eavesdrop.openstack.org/#First_Contact_SIG_Meeting

1 1

[ironic][ops] Breaking change coming in the Victoria development cycle
by Julia Kreger 30 Mar '20

30 Mar '20

Greetings everyone, One of the items the ironic team has been focused on is improving security of remote/edge deployments where machines may be deployed on networks where an un-trusted actor could also be present. Our answer to this has been the concept of utilizing a temporary token[0] for the deployment, which we use to validate the agent heartbeat operations, and commands sent back to the agent ramdisk from the conductor. While not a complete solution to all possible attack vectors, it is a step forward and we will be taking more steps during the next cycle. For the Ussuri release, this functionality is always enabled, but is not explicitly required[1]. Deployments, with older ramdisks who choose to require this capability, must update their deployment/rescue/cleaning ramdisks to a version with a newer ironic-python-agent version from Ussuri development cycle. In Victoria, the ironic team will change the default for requirement of agent tokens such that they are required by default. Pre-Ussuri agent ramdisks will no longer work and will need to be updated. Please let us know if you have any questions or concerns. -Julia [0]: https://docs.openstack.org/ironic/latest/admin/agent-token.html [1]: https://docs.openstack.org/ironic/latest/admin/agent-token.html#how-it-works

2 1

[elections][ironic] PTL candidacy for the Victoria cycle
by Julia Kreger 30 Mar '20

30 Mar '20

Greetings my OpenStack family! I realize we are presently in a stressful time. That each of us are worrying, and that many of us are struggling. "Normalizing", and ultimately accepting the things we cannot control is a vital step forward in our personal and community growth. Finding a path forward is critical in this time. Not just as humans in a pandemic, but as also community members in a project. The vital aspect is continuous across both contexts: We cannot do it alone, We must work together! I too have strengths and weaknesses that I am all too well aware of, and there truly is nothing more re-assuring than those around you encouraging you to continue to support them. For we all need sturdy foundations to take the steps forward. To build the next layer! To continue the journey we are on. As such, I hereby announce my candidacy for the role of Project Team Leader for the Ironic project during the Victoria cycle. That is if you will have me. I foresee the upcoming cycle as a time when we will need to be there to support our community and users. This may take the form of advanced features, lending an occasional ear, or going that extra mile to help each other. And if we need a distraction, I believe we have have some difficult problems yet to solve which can have a major impact in not just our code, but the world at large. While not an exhaustive list of items, it is still an impactful list of work we have been discussing and seek to add into Ironic moving forward. * Multi-tenancy, while underway, opens the world to new possibilities and co-ordination of hardware resources with-in an organization or even across organisations. * Persistent Agents allowing for faster re-provision of deployments on the edge and where the networking is in a fixed configuration. * TLS for Agent Communication to help ensure the nodes on the edge remain secure. * kexec could potentially save significant amounts of time between steps of deployment, and enable operators with larger memory footprints to save precious time of a Power-on-Self-Test. * Attestation system integration so we can improve the odds of identifying a machine with modified firmware and prevent it from moving through the hardware life-cycle as a result. * Enhancement of power management, so operators can avoid having to wait for the Power-on-Self-Test, and maybe even power some of those machines off. Onward, together! For I'm fairly sure we've not completely taken over the world... yet. Julia (TheJulia) Kreger

1 0

[ptl][tripleo][election]
by Wesley Hayutin 30 Mar '20

30 Mar '20

Greetings, I would like to propose my candidacy for the TripleO PTL role in the Victoria cycle. This cycle there has been a lot of progress in simplifying the TripleO code base and the steps in the deployment. The team should be very proud about migrating from mistral to ansible, novaless deployment, the creation of tripleo-operator-ansible, removing paunch, and container improvements. We were also able to migrate Ussuri jobs from CentOS-7 to CentOS-8 in the nick of time. Like in the Ussuri cycle I would like to see the project continue to focus on simplification and improving the user experience. * Continue to push forward with tripleo-ansible and the transformation squad. * Work with ansible sig group, kolla, openstack-ansible, tempest and related projects. * Continue to simplify the stack of components where possible to achieve a faster, better and more efficient deployment. * Mature new features like tripleo-operator-ansible. * I would also like to focus on encouraging the project's more recent contributors to take a larger role in active collaboration, participation and leadership. Thank you for the opportunity! https://review.opendev.org/716077

1 0

[oslo] Feature Freeze exception request
by Alan Bishop 30 Mar '20

30 Mar '20

I'd like to request an exception for https://review.opendev.org/710539. CI is fully green now, it has one +2, and an early patch set had +2 from another reviewer. Thanks for your consideration, Alan Bishop (abishop)

2 1

[tc][elections] my nomination
by Jeremy Freudberg 30 Mar '20

30 Mar '20

Hello everyone, I hereby announce my candidacy for the OpenStack Technical Committee. If you don't know me already I'm the guy who proposed that OpenStack releases be named after ATCs[0]. Some people thought my proposal was satire, but it wasn't, so if you're hoping to elect a satirist look elsewhere. However, this incident is part of my motivation to run for the TC. We can't have satire without culture, and clearly our community has a strong culture if we suspect, and even hope, that satirists are lurking about. All of this indicates to me that OpenStack is a special place and so I would like to play a role in the success of that special place by serving on the TC. "Immensely qualified" is the opposite of what I am, but I have some strengths: * I am nosy. * I have touched a lot of areas of OpenStack because Sahara touches a lot of areas of OpenStack. * I understand the struggles of working on a minor project (tiny team and limited audience but still big goals) because Sahara is a minor project. * I am an optimist because optimism is a necessary part of being the PTL of Sahara nowadays. * I am young. I have much to learn, and luckily I love learning. I don't have many specific goals other than making our community as vibrant as possible. Out of vibrancy, good software will hopefully come naturally, in order to make OpenStack the best it can be in the current landscape. For me being a TC member would be mostly about facilitating the exchange and synthesis of ideas (perhaps crazy ones) and not so much about being a source of ideas myself. Of course, if I happen to have a good idea (they tend to strike very suddenly), I'll share it! To close, thanks to all of you for making our community what it is. It is really something special and everyone who I have ever interacted with (or merely spied on) has been such a delight in their own unique way. It would be an honor to serve you all. -Jeremy [0] https://review.opendev.org/#/c/677827/

1 0

[election][plt] Sean McGinnis candidacy for Release Management PTL
by Sean McGinnis 30 Mar '20

30 Mar '20

Hello everyone, I'd like to run for PTL of the Release Management team again. We have a lot of great automation in place in the releases repo to handle a lot of the release process with, hopefully, minimal overhead. That said, we've made some process changes over the last couple of release cycles that have placed a little more work on the release team's shoulders. We have a lot of these processes mostly automated, but a few things that require a little history and trival knowledge yet. Over the next release cycle I would like to work towards automating a little more of that to make sure if/when anyone else steps into a release manager role, it will be an easy introduction to them to follow our release process documentation and have tooling in place to execute each step without needing to have a very deep understanding of how all the various pieces fit together. Like other projects, we've lost some people, or some of us are not able to spend as much time as we used to on the project. But we've also picked up some great help too. Anything we can do to help anyone to join the team and know what to do and how to do it will be better for us all. Thanks for your consideration! Sean

1 0

[election][tc] Nomination for TC
by Graham Hayes 30 Mar '20

30 Mar '20

Hello Everyone, I have been a member of the TC for 2 terms now, and I am running again for another term on the TC. I have been involved in OpenStack as a developer, operator, PTL, and TC member for a long time, and I think that I can continue to contribute to the community on the TC. I worked as the technical lead for the System Operations team in Verizon Cloud Platform, where we ran 90+ OpenStack installs across the world, ranging from 3 compute micro regions where we needed edge style compute, to much larger footprints for core regions in the US. This gave me a unique viewpoint on how people use OpenStack for both small scale, and for large, real time mission critical telecommunications applications. Further back in my career, I was part of a team that ran the DNSaaS service in HP Cloud (based on Designate of course), which combined with my current role in Azure, where I am looking at how people use both on prem and external clouds, gives me a good insight into the needs of a cloud provider. My main focus over the last term has been trying to get a co-ordinated way for organizations to contribute to OpenStack - Graham's soap box at the Board face to face meetings has become a regular event. Thankfully, I think this has helped push this forward, and I know I have seen people getting involved in the projects I keep an eye on. I have also been involved in the design discussions around `Project Teapot`_ which I think is a great way for OpenStack to help people scale and manage their data centers, while providing the services modern applications are starting to use. I firmly believe that something like Teapot is an important focus of development for OpenStack. I think the new `ideas repo`_ is a fantastic idea and encourage people to put what ever they think is a good idea for OpenStack in there. I will definitely be putting up some of the ideas I have talked about over the years in there. As a long time PTL of a project I know the pressures they can be under and can provide insight as we consider the future governance of the OpenStack project, and its sub projects. This has given me a lot of historical knowledge and context to why some things within our community are the way they are, and as we record this to avoid needing something as unreliable as a human brain (rst is a lot better :) ) I feel I can contribute to the discussion. Finally, I feel that over the years I have made it clear that I will speak out even if I know it will cause push back, and this has allowed me to receive frank and honest feedback from people in community who don't always wish to spend the mental energy, or pay the social tax of raising topics that can be controversial. I don't plan on changing this. Lastly, I have really enjoyed working in this community, it has given me a lot both personally and professionally, and I feel that I can still pay that back. If you agree, please vote for me in the up coming elections, if not please ask me questions in the next week or so, but for everyone, please vote for whoever you think will be the best for OpenStack. Thanks for taking the time to read this, - Graham .. _Project Teapot: https://governance.openstack.org/ideas/ideas/teapot/index.html .. _ideas repo: https://opendev.org/openstack/ideas

1 0

[oslo] Feature Freeze is this week
by Ben Nemec 30 Mar '20

30 Mar '20

Apologies for not mentioning this in the meeting this week, but Oslo Feature Freeze is already this Friday.[0] After Friday, anything that is not a bug fix will need a feature freeze exception in order to merge. If you're wondering why Oslo freezes early, there's a doc[1] for that. If you have any questions not answered there, feel free to reply here or ping me on IRC. Thanks. -Ben 0: https://releases.openstack.org/ussuri/schedule.html 1: https://specs.openstack.org/openstack/oslo-specs/specs/policy/feature-freez…

1 1

[elections][tc] Nomination
by Nikolla, Kristi 30 Mar '20

30 Mar '20

Hi all, Please consider my candidacy for a seat on the OpenStack Technical Committee. I'm a software engineer at the Mass Open Cloud[0], a collaboration between the five major universities of the Boston area to create and operate a public cloud that can be replicated and federated. I've been involved with OpenStack for the past 5 years as a user, operator, and developer. I'm a core reviewer for the keystone project, and I'm also running for its PTL for the Victoria cycle[1]. I have a previous unsuccessful run for the TC[2]. Lately, I've also been involved with OpenInfra Labs[3], a new project of the OSF. I do not have a platform per se, and honestly I wasn't planning on running at all. I have a lot to learn, and if I were to be elected, pretty big shoes to fill. If you are looking for someone that already has all the answers, look elsewhere. On the other hand, if you're looking for someone who is eager to grow, learn, and give back to the community in any way he can, I hope you will consider my candidacy. I'm deeply grateful to the OpenStack community and all the people I've had the pleasure of working with, being mentored by, and doing karaoke during the PTGs. You are like family. Thank you, Kristi Nikolla Pronouns: he, him, his [0]. https://massopen.cloud [1]. https://opendev.org/openstack/election/raw/branch/master/candidates/victori… [2]. https://opendev.org/openstack/election/raw/branch/master/candidates/stein/T… [3]. https://openinfralabs.org

1 0

[election][storlets] PTL candidacy for Victoria
by Takashi Kajinami 30 Mar '20

30 Mar '20

Hi All, I'd like to announce my candidacy to run PTL role for Storlets project in the next Victoria cycles. Thanks to the great effort by several members, we've completed all python3 compatibility work during this Ussuri cycle. Because we are a really small team now, I'll expect that we will focus on improving operability and maintenability in this cycle, while we will also discuss how we'll keep our project in the future. Managing that development and discussion is my responsibility in Storlets project. Thank you, Takashi Kajinami

1 0

[LOCI] Failed to build Trove image
by Lingxian Kong 30 Mar '20

30 Mar '20

The command I am using: docker build . \ --build-arg FROM=loci-base:ubuntu \ --build-arg PYTHON3=yes \ --build-arg PROJECT=trove \ --tag loci-trove:ubuntu The error: http://paste.openstack.org/show/791311/ Then I changed pydep.txt: uwsgi [!trove] and ran again, another error occured: http://paste.openstack.org/show/791313/ However, if removed '--build-arg PYTHON3=yes' in the command (even without modifying pydep.txt), the image could be built sucessfully. Does LOCI support to build Python 3 image or I did something wrong? - Best regards, Lingxian Kong Catalyst Cloud

1 0

[tripleo][nova] New project to support advanced Nova features in TripleO
by Piotr Kopec 30 Mar '20

30 Mar '20

Hello, I'd like to introduce a new project and repository [0] that is intended to host Ansible roles to support advanced Nova features, such as FPGA or NVDIMM. Roles will be as generic as possible but the main use case is to use them with TripleO. This project is intendent to be managed similarly to `tripleo-ipa` [1]. Please, accept the change to add new project and repo. Best regards, Piotr [0]: https://review.opendev.org/#/c/715734/ [1]: https://review.opendev.org/#/c/711114/

1 0

[all][tc] Post-mortem of my time on the TC
by Zane Bitter 30 Mar '20

30 Mar '20

As promised last year, I will not be running for a third term as a member of the Technical Committee. I'm stepping down to spend more time with my family (no, really! ;) I thought this would be a good opportunity to talk to those folks who are thinking of running for a seat, or who aren't but should be. The most common question I hear from potential candidates is "what should I actually do on the TC?" I can't tell you what *you* should do, but I can tell you what I did and how that worked out. Maybe that will give you the flavour. And perhaps (he hinted) some of the other outgoing TC members can do the same to provide more of a cross-section. * I drafted and edited the review guide, "How to Review Changes the OpenStack Way", to try to ensure that the best parts of our review culture are evenly distributed across the project: https://docs.openstack.org/project-team-guide/review-the-openstack-way.html (This started as part of an initiative from Julia Kreger to reduce nitpicking in reviews.) In theory anybody could have done this, but in practice I think this is one of those things that only somebody elected to the TC could have driven. I received a lot of feedback afterwards (which is unusual for anything the TC does): several people, and one whole team, mentioned that they had tweaked their reviewing style after this discussion. And hearing their feedback prompted me to tweak my own reviewing style as well. * I drafted and edited the Vision for OpenStack Clouds: https://governance.openstack.org/tc/reference/technical-vision.html. This was a ton of work as it involved consulting with so many people: first, folks in the community who on the surface appeared to have quite different visions for what OpenStack should be, who later turned out to not be so far apart as we all thought. After a lengthy round of reviews, I approached every project team individually to explain the specific relevance to them, and seek their feedback. Finally, I presented it to the OSF Board and held an in-person feedback session at the Forum, after all of which it was approved by the TC. I have some mixed feelings about the success of this. I still believe it was desperately needed... in about 2013. Now the Kubernetes community is succeeding at engaging with actual end users (not just operators), which OpenStack has always failed to do. With contributions to OpenStack dropping, it's not clear that we can, or necessarily should, sustain such a broad vision. It is my hope that if and when the community needs to discuss adjusting our scope, we will do so by amending this document - going through it section by section and deciding which parts to double down on and which to allow to fall by the wayside - and not by a series of ad-hoc actions that leave everybody confused as to what the project is supposed to be once again. On a personal level, the vision has been extremely valuable for me because it required me to spend a lot of time thinking deeply about the various components of OpenStack and how they fit into a greater purpose. A large portion of the value comes from participating in the process, not necessarily the final document. I hope that all of the folks who helped along the way got as much out of it as I did. * I developed the process by which we keep OpenStack up to date with new releases of Python: https://governance.openstack.org/tc/resolutions/20181024-python-update-proc… I also shepherded it through the first couple of release cycles, to try to entrench it as a standard part of each release. (BTW this task needs somebody to take it over.) This mostly involved pointing people back to the resolution and inviting them to formally update it every time someone tried to bikeshed the details, which happened more than I ever believed possible. (To date there have been no changes proposed to the resolution.) * I engaged with the OSF Board to pass on feedback from members in the developer community on the process for adding new Open Infrastructure projects (e.g. Zuul, StarlingX, Airship, Kata). Sometimes the work of the TC is completely invisible! I also tried to convey information the other way, publicising information that was otherwise only available by attending board meetings. (Most TC members usually attend board meetings, including the in-person joint leadership meetings held before Summits.) * In response to feedback from the board, I replaced the "Help Most Wanted" list with the "Upstream Investment Opportunities" list, and kick-started the rewriting of the existing entries in a format that is more targeted at decision-makers: https://governance.openstack.org/tc/reference/upstream-investment-opportuni… (Huge thanks to Tom Barron, who did even more work to complete the job of converting all of the existing entries - proof that you don't need to be a TC member to start contributing to governance activities.) It remains to be seen whether this will have any effect, but this content is now being shared in the community newsletter, and the board is making moves to use it to actively solicit contributions to the community. Previously they felt unable to make use of the Help Most Wanted list because it was written with the wrong audience in mind. * I tweaked the guidelines for the release naming system to better align with our actual practice, because they had diverged somewhat. Believe it or not, this one issue took up more of the TC's time than any other thing that happened in 2019, and I'm very glad that we ended up not needing these tweaks because we eventually replaced the process wholesale, with one that makes it explicit that the TC is ultimately accountable for the release name not causing any international incidents or other snafus. * I researched and documented a design, developed during extensive discussions with many members of the technical community, for a new kind of simplified cloud built partially using OpenStack components but designed to be Kubernetes-native first: Project Teapot https://governance.openstack.org/ideas/ideas/teapot/index.html I do think this is worth building, but if nothing else I really hope this helps bring into focus the parts of OpenStack that remain essential in a Kubernetes-centric world. In writing this I was very much guided by the Vision for OpenStack Clouds as well as the ways in which Kubernetes expects to interact with an underlying cloud. I think we need more of these kinds of exercises, and while they don't have to be sponsored by TC members, I think it helps. If there's a pattern here it's this: take something that's implicitly agreed upon by the community (whether we realise it or not), write it down, seek feedback, and make it explicit so that anyone can refer to it, rather than leaving it as closely held tribal knowledge. Of course it goes without saying that I was involved in many more discussions and reviews that were led by others. I'll leave it to them to talk about those. And it should also go without saying that all of the work listed above was greatly improved by the input of the many talented folks in our community who contributed. In my humble opinion OpenStack is the best open source community of its size ever created. That's because we believe not just in one 'open' (source), but four (https://governance.openstack.org/tc/reference/opens.html) because we're committed to using open tools to build open software; and because, while it's certainly not the case that we can't improve, we have managed to do this while avoiding a widespread culture of bullying. To do all of this on the scale of OpenStack was, as far as I know, completely without precedent. (Perhaps the ASF comes closest, but its projects operate independently, unlike OpenStack subprojects.) All of us should be proud of this achievement. But it didn't happen by accident: it is the product of concerted effort by leaders in our community over the course of a decade. It's been a tremendous privilege to work alongside some of those folks, both before, during and (hopefully) after my time on the TC. I have learned so much from them. Now it is time for others to step up and continue to build that legacy, as the project evolves and adapts over time. The diversification of the OSF also gives us the opportunity to spread our ethos to other projects under the same umbrella, and from there to the open source community as a whole. However, we must remember that having a great community is not enough. To remain relevant, we also need to produce software that meets users' needs, which change over time. By an accident of fate I have approached OpenStack from a different direction than most - I came to OpenStack via the Heat project, which means I've always looked at it from an outside-in standpoint: users are building cloud applications, how can OpenStack provide them with what they need from a cloud through an open API? Many others, by necessity, have approached it from the inside-out: we have all this hardware, how can we expose its capabilities to users? I think it is fair to say that many of these folks and I have found each other's views to be mutually incomprehensible over the years. In writing up the Teapot design, I have learned a lot more about the other perspective. I believe we will need a more people to also grow their understanding in the opposite direction to avoid the trap of most capital-E "Enterprise" software - designed to check the boxes of those who decide what products to buy, but widely hated by all those forced to actually use it. Future TCs will have to grapple with this because nobody else in the community is really empowered to do so. The openstack/ideas repo that JP created is a great place for anybody to start documenting ways that we can improve. For my part, this is not goodbye. However, I have already been splitting my time between OpenStack and metal3.io and I expect that the drift in the other direction will only accelerate now that I no longer have any formal responsibilities here. Please feel free to contact me or ask questions if you think I can help. Stay safe out there, and by "out there" I mean physically isolated in your own homes for the next little while. cheers, Zane.

5 4

[mistral][ptl][election] PTL candidacy for Victoria
by Renat Akhmerov 30 Mar '20

30 Mar '20

Hi, I'm Renat Akhmerov. I'd like to announce my PTL candidacy for Mistral in Victoria cycle. In Ussuri, we kept improving Mistral performance to address use cases that desperately needed it. For the most complex known workflows the execution time has now dropped by 5-6 times. Besides lots of performance changes we also achieved: * Restructured the documentation completely * Fixed a number of documentation pages and added several new ones. There's still a lot to do on that though. * Made a big refactoring of Mistral actions and moved all OpenStack actions into mistral-extra repo. * Added namespaces for actions and workbooks * Added a new cookiecutter-based template for creating Mistral action projects. * Fixed a number of important bugs (for "join" tasks, scheduler etc.). * And lots of other changes.. For V cycle I'd like to keep making Mistral more usable: * Consistent and well-structured documentation * More ways to create Mistral actions (including action providers) * Additional tools that simplify creating custom actions and functions for Mistral * Easier debugging of workflow errors * Easier and smoother installation process We're already making a good progress with all that and anybody who wants to participate is very welcome onboard. The best way to get in touch with us is IRC channel #openstack-mistral or the openstack-discuss mailing list (with [mistral] tag in email subject). [1] https://review.opendev.org/#/c/715837/ Thanks Renat Akhmerov @Nokia

1 0

[election][glance] PTL candidacy for Victoria
by Abhishek Kekane 29 Mar '20

29 Mar '20

Hi All, I would like to announce my candidacy for Glance PTL for the Victoria cycle. Over the past couple of years we've had a small team looking after Glance and planned the priorities accordingly. During Ussuri cycle we were able to add a couple of important features related edge computing, plugin for image decompression, restored s3 driver support in glance-store, removed deprecated sheepdog driver and fixed some important bugs. Should community to select me as PTL for Victoria cycle I would keep driving the key priorities. Production stability, finishing the work we've had in flight and focus on the feature needs related to Edge computing. Thank you for taking my self nomination into consideration, Abhishek Kekane (abhishekk)

1 0

[election][cinder] PTL candidacy for Victoria
by Brian Rosmaita 29 Mar '20

29 Mar '20

Hello everyone, I would like to announce my candidacy for Cinder PTL for the Victoria cycle. Given that I'm the current PTL, you already have a pretty good idea of what things will be like on the Cinder project with me in that role and whether or not it would be a good idea for me to continue. So instead of bribing you with campaign promises, I'd like to take this opportunity to look at the current state of the project and what things look like for the Victoria cycle. The Cinder community remained fairly stable from Train to Ussuri, which was great in these downsizing times. Some of the drivers that were marked 'unsupported' for the Train release have been restored to 'supported' status during the Ussuri cycle. Some, however, have not. We relaxed the removal policy to give vendors more time to address CI issues and to make it easier for operators using such drivers. We'll see during the Victoria cycle whether this actually encourages the vendors of drivers that have been declared 'unsupported' to get their third-party CIs running again and having the drivers reinstated. During Ussuri, the team gained more testing expertise, particularly around creating more scenario tests, though this hasn't been reflected yet in committed code. As we get more scenario tests into the cinder-tempest-plugin, we'll be able to catch more bugs that affect multiple drivers, whereas now what mostly happens is that driver maintainers fix these piecemeal as they become aware that they affect their drivers. Thus, increasing the scnario test coverage will continue to be a focus in Victoria. The virtual PTG that we held as a follow-up to the Shanghai PTG was productive, as were the two virtual mid-cycle meetings we had this cycle. So I think we're in good shape to make the most of the fully virtual Victoria PTG. I think as a community, we're all doing good work on the Cinder project. We've got cinderlib to keep us relevant in a container-oriented world, and I think we're doing a solid job keeping the software stable and reliable. I'm sure the driver maintainers would like to see faster review turnaround (as would we all), so it will be a priority early in the cycle to identify contributors interested in becoming members of the cinder-core team and mentoring them along so that we can eventually increase the size of the core team during the cycle. In short, things are good, they could be better, and I'd like the opportunity to help drive the project as Victoria PTL. Thank you for your consideration, Brian Rosmaita (rosmaita)

1 0

[neutron] Bug deputy report (Mar 23 - Mar 29)
by Hongbin Lu 29 Mar '20

29 Mar '20

Hi all, I am on the bug deputy last week. Below is the bug deputy report: Critical: https://bugs.launchpad.net/neutron/+bug/1868691 neutron-rally-task fails 100% on stable branches https://bugs.launchpad.net/neutron/+bug/1869034 Postgresql periodic job failing every day High: https://bugs.launchpad.net/neutron/+bug/1868724 KeyError 'gateway_ip' in neutron/services/segments/plugin.py Medium: https://bugs.launchpad.net/neutron/+bug/1869057 extension "subnet_dns_publish_fixed_ips" named wrong in the docs Low: https://bugs.launchpad.net/neutron/+bug/1868515 vpnaas ike policy is not allowed to be updated https://bugs.launchpad.net/neutron/+bug/1868686 ovsdb_timeout config option isn't used to set when adding manager https://bugs.launchpad.net/neutron/+bug/1868933 [fwaas] Update the rules for firewall group without ports will cause the status to change from inactive to active https://bugs.launchpad.net/neutron/+bug/1869121 [FWaaS] Can't add rule with destination_port large than source_port https://bugs.launchpad.net/neutron/+bug/1869342 OVNMechanismDriver _ovn_client is a read-only property Cannot triage (need help from lieutenants): https://bugs.launchpad.net/neutron/+bug/1868697 [ovn] transaction error: {"details":"Transaction causes multiple rows in \"MAC_Binding\" table to have identical values https://bugs.launchpad.net/neutron/+bug/1869129 neutron accepts CIDR in security groups that are invalid in ovn https://bugs.launchpad.net/neutron/+bug/1869244 RowNotFound: Cannot find Bridge with name=tbr-XXXXXXXX-X when using trunk bridges with DPDK vhostusermode https://bugs.launchpad.net/neutron/+bug/1869354 FIP isn't properly created for octavia loadbalancers Invalid: https://bugs.launchpad.net/neutron/+bug/1869136 Use public flat network to create vm faild Best regards, Hongbin

1 0