Thursday, 2020-04-02

*** raildo has quit IRC00:33
*** yamamoto has joined #openstack-meeting-301:01
*** yamamoto has quit IRC02:04
*** links has joined #openstack-meeting-302:17
*** links has quit IRC03:00
*** yamamoto has joined #openstack-meeting-303:03
*** igordc has quit IRC03:42
*** fnordahl has joined #openstack-meeting-305:10
*** links has joined #openstack-meeting-305:25
*** lajoskatona has joined #openstack-meeting-306:03
*** maciejjozefczyk has quit IRC07:04
*** slaweq has joined #openstack-meeting-307:08
*** ralonsoh has joined #openstack-meeting-308:12
*** e0ne has joined #openstack-meeting-308:15
*** yamamoto has quit IRC08:56
*** yamamoto has joined #openstack-meeting-308:58
*** yamamoto has quit IRC09:13
*** yamamoto has joined #openstack-meeting-309:31
*** lajoskatona has quit IRC10:09
*** yamamoto has quit IRC10:29
*** yamamoto has joined #openstack-meeting-310:30
*** negronjl has quit IRC10:32
*** negronjl has joined #openstack-meeting-310:35
*** lajoskatona has joined #openstack-meeting-311:01
*** apetrich has joined #openstack-meeting-311:36
*** yamamoto has quit IRC11:42
*** yamamoto has joined #openstack-meeting-311:43
*** raildo has joined #openstack-meeting-312:08
*** yamamoto has quit IRC12:14
*** yamamoto has joined #openstack-meeting-312:19
*** yamamoto has quit IRC12:19
*** yamamoto has joined #openstack-meeting-312:20
*** njohnston has quit IRC13:08
*** ianychoi_ has joined #openstack-meeting-313:17
*** ianychoi has quit IRC13:20
*** tosky has joined #openstack-meeting-313:22
*** ianychoi_ is now known as ianychoi13:23
*** njohnston has joined #openstack-meeting-313:24
*** markmcclain has joined #openstack-meeting-313:26
*** jeremyfreudberg has joined #openstack-meeting-313:44
*** tellesnobrega has joined #openstack-meeting-314:07
jeremyfreudberg#startmeeting sahara14:07
openstackMeeting started Thu Apr  2 14:07:49 2020 UTC and is due to finish in 60 minutes.  The chair is jeremyfreudberg. Information about MeetBot at http://wiki.debian.org/MeetBot.14:07
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:07
*** openstack changes topic to " (Meeting topic: sahara)"14:07
openstackThe meeting name has been set to 'sahara'14:07
tellesnobregao/14:08
jeremyfreudbergo/14:08
jeremyfreudbergsorry for the late start14:08
tellesnobregano worries from my side14:08
jeremyfreudbergwe will likely be brief here anyway, but respect for the calendar is a good thing14:08
toskycorrect14:09
jeremyfreudberg#topic news/updates14:10
*** openstack changes topic to "news/updates (Meeting topic: sahara)"14:10
toskyI'm double booked but I have some notes14:10
jeremyfreudbergsure14:10
toskyit has been a busy week14:10
tosky- sahara-dashboard is mostly fixed (there is a pending update on stable/train)14:10
tosky- a change in openstackclient broke saharaclient. It seems we need to fix it on our side, despite the breakages happened on a stable release. More information on: http://storyboard.openstack.org/#!/story/200750114:10
toskyThis should be fixed before the saharaclient release (or immediately after).14:10
tosky- sahara, on the other hand, is blocker by https://storyboard.openstack.org/#!/story/2007450  - I was told it is due to the Session object being garbage collected, which means we should ensure it's still around. But I haven't found an easy way.14:10
tosky- there is another breakage in the buildimages job, but it's not a blocker right now14:10
tosky- there are various "hacking"-related updates, feel free to vote on those which are passing14:10
toskyThe two issues reported on storyboard are the critical ones and NEED HELP!14:10
toskyEOF14:11
jeremyfreudbergthank you for that tosky14:11
jeremyfreudbergi will look at those stories14:11
jeremyfreudbergyeah, those are not so easy14:13
toskythe saharaclient one it's probably not complicated, it just takes a bit more time14:14
jeremyfreudbergyeah, seems so14:14
toskythe sqlalchemy is tricky to understand, I suspect the fix may be a oneliner14:15
jeremyfreudbergi will try to find some time14:15
jeremyfreudberg#topic open discussion14:15
*** openstack changes topic to "open discussion (Meeting topic: sahara)"14:15
jeremyfreudbergi am already the ptl again for vitcoria, officially14:16
jeremyfreudbergi am also a a candidate for tc14:16
toskythanks!14:16
jeremyfreudbergi assume everybody is already aware but i like to have it in the meeting logs14:16
toskyfor both14:16
jeremyfreudberganyway, i don't have anything else to report today, so we can close it14:18
toskyyep - so please if you want to work on something, I'd say to focus on saharaclient, which is going to be released first14:18
jeremyfreudbergyes, that is good advice14:19
jeremyfreudbergok, thanks everyone!14:19
toskythank you!14:20
toskyo/14:20
jeremyfreudberg#endmeeting14:20
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:20
openstackMeeting ended Thu Apr  2 14:20:51 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:20
openstackMinutes:        http://eavesdrop.openstack.org/meetings/sahara/2020/sahara.2020-04-02-14.07.html14:20
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/sahara/2020/sahara.2020-04-02-14.07.txt14:20
openstackLog:            http://eavesdrop.openstack.org/meetings/sahara/2020/sahara.2020-04-02-14.07.log.html14:20
*** jeremyfreudberg has left #openstack-meeting-314:21
*** tosky has left #openstack-meeting-314:23
*** macz_ has joined #openstack-meeting-314:55
*** links has quit IRC15:03
*** _erlon_ has joined #openstack-meeting-315:48
_erlon_.15:48
*** jamesmcarthur has joined #openstack-meeting-315:55
*** elod has joined #openstack-meeting-315:56
*** rambo_li has joined #openstack-meeting-315:57
gibi#startmeeting nova16:00
openstackMeeting started Thu Apr  2 16:00:11 2020 UTC and is due to finish in 60 minutes.  The chair is gibi. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: nova)"16:00
openstackThe meeting name has been set to 'nova'16:00
*** yamamoto has quit IRC16:00
artomo/ (sorta - it's also lunch time, so I'm feeding the kiddos)16:01
bauzas\o16:01
gmanno/16:01
bauzas(it's beer time but I can wait)16:01
_erlon_\O16:01
gibio/16:01
elodo/16:01
dansmitho/16:01
gibibauzas: I understand your pain as we are in the same timezone so I will be quick16:02
gibi#topic Last meeting16:02
*** openstack changes topic to "Last meeting (Meeting topic: nova)"16:02
gibi#link Minutes from last meeting: http://eavesdrop.openstack.org/meetings/nova/2020/nova.2020-03-26-16.00.log.html16:02
gibiPlans for a virtual PTG is still up on the ML #link http://lists.openstack.org/pipermail/openstack-discuss/2020-March/013555.html16:02
gibiTwo company rule are less strict now as per #link http://lists.openstack.org/pipermail/openstack-discuss/2020-March/013553.html16:02
gibiWe have two new cores lyarwood and gmann. Welcome! \o/16:02
gibianything we have to discuss about these topics?16:03
gmannthanks everyone.16:03
gibi#topic Bugs (stuck/critical)16:04
*** openstack changes topic to "Bugs (stuck/critical) (Meeting topic: nova)"16:04
gibiNo Critical bugs16:04
gibisomebody added the following to the wiki without a nick16:04
gibiOVS drops RARP packets by QEMU upon live-migration causes up to 40s ping pause [1]16:04
*** sean-k-mooney has joined #openstack-meeting-316:04
bauzasgibi: FWIW, there was a meeting from the Foundation about any plans for the Virtual PTG16:04
rambo_liyeah ,it is me16:04
bauzasbut i can discuss this during the open discussion16:04
gibibauzas: ack, let's do discuss that in the open16:05
rambo_lihttps://bugs.launchpad.net/neutron/+bug/181598916:05
openstackLaunchpad bug 1815989 in OpenStack Compute (nova) "OVS drops RARP packets by QEMU upon live-migration causes up to 40s ping pause in Rocky" [Medium,In progress] - Assigned to sean mooney (sean-k-mooney)16:05
rambo_liHow can we solve this bug thoroughly?And it has serious impact on the OpenStack environment.16:05
gibirambo_li: floor is yours16:05
gibirambo_li, sean-k-mooney: do you see a need for a change in nova?16:05
sean-k-mooneygibi: i have not looked at this is some time but if i remeber correctly this is related to the use of multple port binding and some nova neutron interactions16:07
rambo_liI want to know if there is  someone following up, such an sean16:07
sean-k-mooneyhttps://review.opendev.org/#/c/602432/16:07
sean-k-mooneyi think that is require among other things to make it work16:08
sean-k-mooneywell to fix the issue16:08
sean-k-mooneythe proablem is as long as libvirt is pluging the interface we can not fix this16:08
sean-k-mooneyso we need to delegate pluging in all cases to os-vif to fix it which that does but we need a neutron fix as well before that can proceed16:09
sean-k-mooneywhich is https://review.opendev.org/#/c/64025816:09
sean-k-mooneyi have not been working on this since last cycle16:09
gibisean-k-mooney: thanks16:09
gibirambo_li: do you or somebody on your side can help with pushing the patches forward?16:10
gibirambo_li: I also suggest to ping ralonsoh from neutron about the neutron side of the fix16:11
*** jamesmcarthur has quit IRC16:11
sean-k-mooneyclip notes version is libvirt add the port to ovs, then there is a short race between neutorn wiring it up and qemu sending the RARP16:11
rambo_li I agree the ning yao in this comment .so how can we solve it thoroughly. Is that possible to activate the port binding before the vm shutting down on the source host and vm being running on the destination host?16:12
*** jamesmcarthur has joined #openstack-meeting-316:12
sean-k-mooneyrambo_li: no wont work16:12
sean-k-mooneyrambo_li: libvirt deletes the prot and recreates it16:12
ralonsohI'll sync up with sean-k-mooney after the meeting16:12
sean-k-mooneywhich mean that neutron needs to set it up again16:12
sean-k-mooneybut yes we can talk after16:12
rambo_liyeah , we can talk it after16:13
gibiralonsoh, sean-k-mooney, rambo_li: thanks. let me know if I can help somehow16:13
gibistill about bugs16:14
gibi#link 108 new untriaged bugs (+6 since the last meeting): https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New16:14
gibiso we are over 100 again :/16:14
gibistill I haven't had time to go and triage some16:14
gibianyhow moving forward16:14
gibi#topic Gate status16:14
*** openstack changes topic to "Gate status (Meeting topic: nova)"16:14
gibimelwitt, lyarwood, gmann: how is the gate doing recently?16:14
gibiI filed a functinal test stability bug and pushed a fix recently https://bugs.launchpad.net/nova/+bug/187038516:15
openstackLaunchpad bug 1870385 in OpenStack Compute (nova) "AcceleratorServerTest.test_create_server_with_error fails intermittently" [Medium,In progress] - Assigned to Balazs Gibizer (balazs-gibizer)16:15
*** jamesmcarthur has quit IRC16:16
gmanni did not see any blocking but i was busy on policy things to finish so not aware if any bug is happening frequently (but not blocking).16:16
gibigmann: thanks16:16
gibi#topic Release Planning16:16
*** openstack changes topic to "Release Planning (Meeting topic: nova)"16:16
gibiThis week we have "Final release for non-client libraries"16:17
gibiI think we are ready. os-vif did not need a new release since 2.0.016:17
gibiI talked with tetsuro, he handles os-resource-classes and os-traits16:17
gibiOne week until Milestone 316:17
gibiwhich means Feature freeze is next week16:17
gibifrom the 30 approved BPs for Ussuri 10 have already been implemented(+2 since last week) \o/16:17
gibiThere are 9 open BPs still targeted to ussuri-3 #link https://launchpad.net/nova/+milestone/ussuri-316:18
gibiany question about the FF?16:18
artomAny differences/plans around FFEs this cycle?16:18
*** jamesmcarthur has joined #openstack-meeting-316:18
gibiI don't think there is any difference16:19
artomOr ask as usual for things that almost made it and are worht it?16:19
gmanngibi: 9th April is FF right?16:19
sean-k-mooneygibi: the cybrog blueprint is more or less complete although there are some follow up patches that would still be good to merge16:19
bauzasI wouldn't argue for my single side, but I think that in this period, an exceptional FFE period could help a bit16:20
gibiartom: yes. post an FFe mail to the ML if you need one16:20
gibigmann: yes, Apr 9 EOB if the FF16:20
artomgibi, not me personally, I got nothing this cycle - but I'm aware of at least 1 that'll probably happen, so wanted to make sure16:20
gmannok, thanks16:20
bauzasone week left indeed16:20
gibisean-k-mooney: I see some doc patch open but that can go in after FF16:21
gibisean-k-mooney: do you want to push the evac fix for Ussuri?16:21
*** jamesmcarthur has quit IRC16:21
sean-k-mooneyam if i can get it done before FF it would be nice to have16:21
sean-k-mooneyso we have at least one move operation but lets cross that bridge next week16:21
gibisean-k-mooney: sure, if it is ready I think me and dansmith can push it through16:22
sean-k-mooneyi need to finish refactoring it and testing it but i hope to have a version for ye to review tomrrow16:22
gibibauzas: we have to produce RC1 on the week of 20th of April so we have 3 weeks between FF and RC116:23
bauzasI know16:23
gibiso I don't see too much possibility to extend FF (except the usual FFe request)16:23
bauzasand I know it will stretch things if we go with exceptions16:23
*** yamamoto has joined #openstack-meeting-316:23
bauzasI'd have appreciated if the TC would have changed a bit of release window, but that's not the case16:23
bauzasanyway, not a big case on my side like I said16:24
gibiOK, anything else about FF?16:24
gibiM3 also means Final release for client libraries16:25
gibiwe have novaclient patches open to support the newly merged microversions, 2.83 and 2.8416:25
gibi#link https://review.opendev.org/#/c/71308916:25
gibi#link https://review.opendev.org/#/c/71456116:25
gibiI left feedback on 2.8316:25
artomHave we started requiring osc patches as well, btw?16:25
gibi2.84 is trivial just queued up behind 2.8316:25
artomOtherwise the novaclient-osc gap will just get larger and larger16:25
gibiartom: good question16:25
artomI guess we can save that for open discussion?16:26
gibiartom: I have nothing else now for the release topic so lets discuss osc16:26
bauzasgibi: okay, I'll review those novaclient patches urgentlyu16:26
gibihonestly I don't know if we have a written rule for requiring osc patches16:26
bauzaswe don't (yet)16:26
artomOr I guess osdk? It's the new official thing, right?16:27
gibiartom: I feel you know more about osc and sdk than me :)16:27
artomgibi, if I do, it's only barely ;)16:27
artomFWIW, I think we should make it compulsory, like we do for novaclient16:28
bauzasit's just some companies recommend this tool in their documentation but not novaclient16:28
gibianyhow time is sort until the last osc release for ussuri so let's try to make a decision for V cycle about such requirement16:28
artomWe can ask mordred for the right place to put the new code, but we can't continue just adding stuff to novaclient16:28
artomOtherwise, as I said, the gap will grow and grow and grow16:28
artomBut yeah, V is a good time to start :)16:29
gibiartom: if we add the bindig code to novaclient then osc can consume that still?16:29
bauzaswe discussed it at a couple of PTGs16:29
bauzasthe main issue wasn't the design16:29
artomgibi, not sure - IIUC it still needs to be wired up16:29
sean-k-mooneygibi: it could but its kind of going againt the dirction of osc swapping to the sdk16:29
bauzasthe main issue was that nobody was signing off for it16:29
gibiOK, so this is a topic for the PTG16:30
artomsean-k-mooney, yeah, I wasn't sure of what the new hotness was16:30
artomSubstitute "official openstack client program" for osc :)16:30
gibiartom, bauzas, sean-k-mooney: does some of you can add the topic to the etherpad with as many background as you have?16:30
bauzasI can, my tab is open16:30
artomgibi, I brought it up, I'll do it16:30
bauzasoh cool16:31
gibihttps://etherpad.openstack.org/p/nova-victoria-ptg16:31
artombauzas, ok, unjinx! It's all yours16:31
artomDammit, too late!16:31
artom;)16:31
gmannFYI. Virtual PTG planning meeting is on April 6th and 7th one.16:31
gmannabout dates and all16:31
bauzasgmann: I followed one this afternoon my time16:32
bauzasthere are notes already16:32
gmannbauzas: great16:32
bauzasbut I promised to discuss it during the opens16:32
gibiyepp16:32
gibiso moving forward16:32
gibi#topic Stable Branches16:32
*** openstack changes topic to "Stable Branches (Meeting topic: nova)"16:32
gmann+116:32
gibiI see fairly short review backlogs on both train and stein16:32
gibilyarwood is off this week. elod: anything newsworthy on stable?16:32
elodnothing special,16:33
elodshort backlogs as you wrote16:33
gibithanks16:34
gibi#topic Sub/related team Highlights16:34
*** openstack changes topic to "Sub/related team Highlights (Meeting topic: nova)"16:34
gibiPlacement (tetsuro)16:34
*** jamesmcarthur has joined #openstack-meeting-316:34
*** yamamoto has quit IRC16:34
gibiAPI (gmann)16:34
gibigmann: anything besides the progressing policy work?16:35
gmannpushing the policy stuff in speedy way16:35
gmannother than that nothing specific to mention.16:35
gibigmann: thanks16:35
gibi#topic Stuck Reviews16:35
*** openstack changes topic to "Stuck Reviews (Meeting topic: nova)"16:35
*** yamamoto has joined #openstack-meeting-316:35
gibinothing on the agenda16:35
*** yamamoto has quit IRC16:35
gibido you have anything to discuss here?16:36
*** yamamoto has joined #openstack-meeting-316:36
gibi#topic Open discussion16:36
*** openstack changes topic to "Open discussion (Meeting topic: nova)"16:36
gibiNew Scheduler Affinity/Anti-affinity Filter (erlon)16:36
gibi_erlon_: your turn16:37
_erlon_hey guys16:37
_erlon_so, we are planning to add a Affinity/Anti-affinity filter to Nova, and want to get some feedback16:38
artomDifferent from what we already have?16:38
_erlon_artom: yes16:38
sean-k-mooney_erlon_: what is the goal and how does it differ form the existing filter/weigher we have for hard and soft affintiy16:38
bauzasI think it could be discussed in a spec16:39
_erlon_artom: so, the use case is that, we can want to create a bunch of VMs and want Nova to spread them  across multiple AZs16:39
sean-k-mooneywell it will need one but i was hoping for a clip notes version asn tehre are issues with palacement when it comes to affinity and anti afinity16:39
_erlon_bauzas: that was my next question, if we needed that to be on a spec16:39
dansmiththat would go against our current AZ behavior, outside even the control of a filter, IMHO16:40
_erlon_sean-k-mooney: clip note version?16:40
bauzaswhat dansmith said16:40
dansmiththat'd be the job for an external tool, IMHO16:40
*** yamamoto has quit IRC16:40
bauzasbut again, I'd prefer to discuss this in a spec16:40
sean-k-mooney_erlon_: you answered it you want to do AZ anti affintiy16:40
_erlon_dansmith: what outside the ontrol of a filter? the host group affinity does exacly that16:41
sean-k-mooneyclip notes version is the short version :)16:41
_erlon_got it16:41
sean-k-mooney_erlon_: well for a start it would only work if you did not have an az in the boot request.16:41
dansmithsean-k-mooney: but then we assign the default AZ if you don't,16:42
bauzasI feel they want host aggregate anti-affinity16:42
_erlon_sean-k-mooney: yes, i think that should be a limitation16:42
sean-k-mooney_erlon_: this is specvicly for nova multi create api right e.g. boot 5 servers with one request16:42
dansmithso the filter would need to override that behavior I think16:42
bauzasand not server anti-affinity16:42
bauzasbut either way, drafting it on the fly seems difficult as we at least need to understand what problem we have to solve16:43
sean-k-mooneydansmith: which would be too late if we have dont the az->host aggrate to placement aggreaet mapping already16:43
bauzas_erlon_: do you feel okay with writing a spec and mainly explaining *what* you want to solve ?16:43
sean-k-mooney_erlon_: have you filed a blueprint to track this feature?16:43
bauzas_erlon_: forget first about the solution and explain what's missing for your needs16:43
bauzasin the nova toolket16:44
_erlon_sean-k-mooney: not necessarily, we tryied using the same group affinity for hosts. So, we create a group, set its affinity, and all the isntances created in that group will land/or not in the same or different AZ16:44
gibibauzas:  +116:44
bauzasand maybe we could come up with a solution for you that wouldn't require some new implementation work16:44
dansmithsean-k-mooney: I'd have to look at the order of where that gets set and assumed, but I'm skeptical about doing this inside nova in general16:44
bauzas_erlon_: in general, that's what happens with filters16:44
_erlon_bauzas: so, are you faminilar witth the host affinity groups?16:44
bauzasmost of the times, the current state is flexible enough to address lots of needs16:44
gibi_erlon_: as bauzas suggested, please write a short spec focusing on the use case and let's continue the discussion in that spec.16:45
bauzas_erlon_: spec up, and then ping me16:45
sean-k-mooneydansmith: ya i was more thinking it might have to be a pre request filter at a minium as a normal filter would be too late.16:45
_erlon_gibi: bauzas: sounds good16:45
sean-k-mooneystill intersted in understand the usecase in anycase16:45
gibiOK, going back to virtual PTG plannign16:45
_erlon_the other questions16:45
gibinvm16:45
gibi_erlon_: yes?16:46
bauzas_erlon_: and if you already have code up, good news! you can just use your own filters out-of-tree without loosing time to convince ourselves :p16:46
_erlon_I didnt see any spec freeze in the nova schedule16:46
_erlon_do you guys have it?16:46
sean-k-mooneyits noramlly milestone 216:46
gibi_erlon_: Ussuri spec freeze are in the past16:46
sean-k-mooneyalthough we have change it in the past to be milestone 116:46
bauzaswe no longer do spec freeze16:46
bauzasbut yeah m-216:46
bauzasactually, yeah we do16:46
gibiV cycle schedule #link https://releases.openstack.org/victoria/schedule.html16:47
_erlon_ok16:47
gibiM2 is end of july16:47
sean-k-mooney_erlon_: you have about 2-4 months before the deadline16:47
sean-k-mooneyya16:47
_erlon_sean-k-mooney: ok16:47
bauzasagain, focus on the problem16:47
bauzasexplain your usecase16:47
_erlon_about using it of tree, we have hit problems in the past as we have to manually alter the distro package16:48
_erlon_bauzas: sure, makes sense16:48
sean-k-mooney_erlon_: im guesin you are using AZs to model fault domains and you want to magage the scudling accordingly to acchive ha16:48
bauzas_erlon_: FWIW, you can just package your single filter separately, it'll work fine16:49
bauzasno need to alter anything16:49
sean-k-mooneybut i think we can likely move on for now if there are other topics16:49
bauzas++16:49
gibilet's continue this on #openstack-nova as I'd like to go back to the virtual PTG thing for a bit16:49
gibibauzas: so you already heard some info from the fundation today16:49
bauzasno precise info, it was a discussion16:50
_erlon_bauzas: we only manage to make nova to see it by changing the eggs16:50
bauzasand I raised the concerns I had16:50
bauzas_erlon_: let's continue this over -nova please16:50
gibibauzas: cool. I will try to read up on that discussion and see how it relates to my current plans16:50
_erlon_but anywasy, Ill publish a spec later guys. thanks a lot for now16:50
gibi_erlon_: thanks16:50
bauzas#link https://etherpad.openstack.org/p/Virtual_PTG_Planning16:51
bauzastl;dr: the PTG would be on 2 weeks (or more)16:51
bauzaswe could potentially have two distinct periods, one for cross-project discussion, the other being the project team discussions16:52
bauzasoverlapping sessions potentially16:52
bauzasand maybe large time slots in the day to allow contributors from different timezones to join16:52
bauzasbut the main thing is : there will be two more sessions to attend16:52
bauzas(if you bear using Zoom)16:53
bauzasdates are on the etherpad16:53
gibiApril 6th at 17 UTC16:53
bauzasso, like any other business, if you care, you dare join16:53
gibiApril 7th at 2 UTC16:53
gibibauzas: thanks for the summary16:53
bauzasthat's it from me16:53
sean-k-mooneyideally i think we should try to organsise our own seesion slots within that period to avoid overlap were we can16:53
sean-k-mooneynot that i expect we would all attend every session. we dont even do that in person16:54
sean-k-mooneybut jsut to avoid overlap where it not needed16:54
gibisean-k-mooney: yeah, I feel organizing a real time session per topic for important topics are easier than have an umbrella slot16:54
bauzassean-k-mooney: ideally I'd appreciate the Foundation to back us16:54
gibibauzas: back us with what?16:54
bauzasby providing mission letters to our management, asking them to not bear us during the timeslots16:55
gibibauzas: I see16:55
sean-k-mooneywell i dont think its very different then how we normally manage our time at the ptg16:55
bauzasthat's why defining some specific period of time could help16:55
bauzassean-k-mooney: yes and no16:55
bauzasnot paying attention to the internal channels during the usual PTG definitely helps16:55
gibibauzas: good point. I have to block out all my downstream meeting for that two weeks16:55
gibiwhich will be fun :)16:56
bauzasgibi: that's why the Foundation wants the dates to be well communicated16:56
bauzasand understood16:56
sean-k-mooneyif we can arrange some buckets of time that suite the majority of peopel, with foundation help if possibel we can then schdule within those slots as needed.16:56
artombauzas, tbf, I don't think RH management will be a problem :) Other companies I have no idea about16:57
sean-k-mooneyya that true16:57
sean-k-mooneyif i was at the ptg i would not be attending the meetings that week anyway16:57
gibianything else? we have 2 minutes16:58
bauzasartom: sure, but I don't speak here for my single company :)16:58
bauzasalthough some escalations could occur...16:58
artombauzas, right, but that's implicitly understood to be top priority at all times16:58
artomAnyways16:59
artomFWIW, RH hosted a community event around running virtual meetups16:59
artomI took some notes, with some maybe interesting ideas16:59
artomI'll send that to the ML16:59
gibiartom: thanks!16:59
gibi... 20 seconds16:59
sean-k-mooneyim not really planning to attend the virtual ptg planning metting16:59
sean-k-mooneyartom bauzas can you update us next week17:00
gibithank your for joining. o/17:00
gibi#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"17:00
openstackMeeting ended Thu Apr  2 17:00:09 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova/2020/nova.2020-04-02-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova/2020/nova.2020-04-02-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/nova/2020/nova.2020-04-02-16.00.log.html17:00
gibisean-k-mooney: sorry we run out of time17:00
bauzassean-k-mooney: I joined one of those events, I'm personnally done with it17:00
sean-k-mooneygibi: no worries lest go back to the nova channel17:00
bauzasI raised my concerns, I heard some feedback, I'm done17:00
*** sean-k-mooney has left #openstack-meeting-317:00
*** artom has quit IRC17:16
*** artom has joined #openstack-meeting-317:16
*** rambo_li has quit IRC17:24
*** jamesmcarthur has quit IRC17:28
*** jamesmcarthur has joined #openstack-meeting-317:29
*** jamesmcarthur has quit IRC17:54
*** jamesmcarthur has joined #openstack-meeting-317:55
*** lajoskatona has quit IRC18:22
*** jamesmcarthur has quit IRC18:24
*** jamesmcarthur has joined #openstack-meeting-318:25
*** jamesmcarthur has quit IRC18:26
*** jamesmcarthur has joined #openstack-meeting-318:26
*** diablo_rojo has quit IRC18:26
*** ralonsoh has quit IRC18:28
*** diablo_rojo has joined #openstack-meeting-318:29
*** yamamoto has joined #openstack-meeting-318:39
*** yamamoto has quit IRC18:47
*** tellesnobrega has quit IRC19:05
*** tellesnobrega has joined #openstack-meeting-319:06
*** elod has left #openstack-meeting-319:08
*** jamesmcarthur has quit IRC19:15
*** jamesmcarthur has joined #openstack-meeting-319:16
*** jamesmcarthur has quit IRC19:16
*** jamesmcarthur has joined #openstack-meeting-319:16
*** jamesmcarthur has quit IRC20:02
*** jamesmcarthur has joined #openstack-meeting-320:02
*** raildo_ has joined #openstack-meeting-320:17
*** jamesmcarthur has quit IRC20:19
*** raildo has quit IRC20:20
*** jamesmcarthur has joined #openstack-meeting-320:26
*** jamesmcarthur has quit IRC21:03
*** jamesmcarthur has joined #openstack-meeting-321:03
*** igordc has joined #openstack-meeting-321:05
*** e0ne has quit IRC21:06
*** slaweq has quit IRC21:07
*** jamesmcarthur has quit IRC21:08
*** slaweq has joined #openstack-meeting-321:14
*** jamesmcarthur has joined #openstack-meeting-321:26
*** jamesmcarthur has quit IRC21:26
*** jamesmcarthur has joined #openstack-meeting-321:26
*** slaweq has quit IRC21:26
*** raildo_ has quit IRC21:34
*** yamamoto has joined #openstack-meeting-322:45
*** yamamoto has quit IRC22:49
*** openstack has joined #openstack-meeting-322:59
*** ChanServ sets mode: +o openstack22:59
*** macz_ has quit IRC22:59

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!