Wednesday, 2021-06-23

*** sboyron is now known as Guest32214:44
ttx#startmeeting large_scale_sig15:00
opendevmeetMeeting started Wed Jun 23 15:00:21 2021 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
opendevmeetThe meeting name has been set to 'large_scale_sig'15:00
ttx#topic Rollcall15:00
ttxWho is here for the Large Scale SIG meeting, in our new location?15:00
genekuoo/15:00
amorino/15:00
belmoreirao/15:00
ttxI'll ping people on #openstack-meeting-3 just in case15:00
ttxOur agenda for today is at:15:01
ttx#link https://etherpad.openstack.org/p/large-scale-sig-meeting15:01
ttx#topic Next OpenInfraLive session15:01
ttxTwo weeks ago we produced a great episode, continuing our upgrade discussion15:02
ttxThe "Large Scale openStack" episodes are some of the most popular on the platform for now15:02
ttxOur next "large scale openstack" show will be... July 1515:02
ttxWe need to decide on the topic ASAP so that we can gather guest speakers and promote the show15:02
ttxWe have three top candidates, taken from suggestions at https://etherpad.opendev.org/p/large-scale-sig-lightning-talks:15:03
ttx- Inception: Run your OpenStack control plane on top of the infrastructure that it manages15:03
ttx- Monitoring a large scale deployment15:03
ttx- How OpenStack large clouds manage their spare capacity15:03
ttxAny preference?15:03
amorinI dont have personal preference15:04
belmoreirapersonally, I'm interested in "How OpenStack large clouds manage their spare capacity" :)15:04
amorinthats a big topic15:04
belmoreira"Inception" it will be cool, but maybe later?15:04
genekuoI also don't have a strong preference15:04
amorinall of them are good candidates IMHO15:04
ttxMy only concern with this one is who would do the base presentation?15:05
amorinInception is maybe not *only* related to largescale15:05
ttxIn terms of format, we need to avoid the "too many presentations, no time for discussion" issue we had with upgrades15:05
ttxSo I think we should prefer a narrow topic, with one single 5-10min presentation, followed by a panel discussion between 4-5 people15:05
ttxwith "spare capacity" do we have anyone ready to do the base presentation?15:06
genekuoMonitoring IMO is a very large topic15:06
ttxgenekuo: yeah we should probably be more specific15:06
amorinabout monitoring, we can talk, but my speaker is not available easily on 1515:06
amorinabout spare, belmiro, you were willing to talk, right?15:07
amorinbelmoreira15:07
belmoreiraI think is an interesting topic to discuss... I have a lot of questions :)15:07
ttxbelmoreira: do you think we can do the show without any leading presentation?15:08
belmoreiraamorin, would you be willing to talk?15:08
amorinI think we have few things to say, but I know we are not the best on this topic...15:08
belmoreiraI think public clouds is even more challenging 15:08
amorinI can still ask the team and come back to you asap15:08
ttxWe can discuss who the guest speakers could be but i want to nail down the format first15:09
ttxif we do presentation + panel, we need a presenter15:09
genekuoI can also ask the team that manages capacity to see if they can talk15:09
ttxalternatively we can do pure panel15:09
ttxif we have many questions, that could work15:09
belmoreirattx having only one presentation may be very narrow scope. Probably people are doing different things... public/private clouds are completly different15:10
ttxit's narrow but it's a just a trick to get people engaged15:10
ttxor maybe it's more a presentation to introduce the topic15:11
belmoreirattx true!15:11
genekuoI will prefer presentations + panels15:11
genekuoshort presentations about how currently people manages capacities first15:11
ttxLike " the problem with excess capacity: rather than "what we do at CERN with extra capacity"15:11
genekuoI agree with belmoreira that private/public cloud may have a completely different view to this topic15:12
ttxgenekuo: short presentations did not work well for us last time, just took too much time and not enough engagement between participants15:12
ttxbut maybe we can start the discussion by introducing the challenge we want to discuss, using a few slides15:13
ttxthat would set the stage15:13
belmoreiraa presentation stating thee problem and then the discussion about what people usually do 15:13
ttxand then we can ask the panel questions15:13
amorinsounds like a good plan15:13
belmoreiraI think I just said the same as ttx :)15:13
genekuoSounds good to me15:13
ttxbelmoreira: since you find the topic interesting, I nominate you for stating what the challenge is15:14
belmoreiranomination accepted :)15:14
ttxAlso... if people have a point to make that could really use a slide to explain, we can prepare it in advance and plug it during the show15:15
ttx(or keep it in reserve)15:15
ttxThat makes the show a bit less like a Zoom call15:15
ttxOK so...15:16
ttx#agreed Topic should be "How OpenStack large clouds manage their spare capacity"15:16
ttx#agreed Belmiro will do the initial "challenge statement" short presentation15:16
belmoreiraquestion: is any of you using something similar to spot instances?15:17
ttxBeyond Belmiro, who here has a great story on that topic to share and wants to be on the show?15:17
ttxand... who else should we invite to join?15:17
amorinI think I will find someone, or at least something to say15:17
amorinI just need to talk back about this with the team15:17
belmoreiranot a "great story" :) I just think it's a real problem15:17
amorinso you can count on us15:17
ttxI'd like us to rotate speakers if possible, to avoid making it look like a club too much15:17
amorinagree15:18
genekuoI can ask the team managing this part. I think they can at least provide some input to the problems15:18
ttxLike we could have someone from CityNetwork or Binero for the public cloud side15:18
amorinrotate the speakers, or rotate the companies?15:18
amorinok yes15:18
belmoreira"CityNetwork or Binero" that would be great15:18
ttxThat could be in addition to you arnaud if you have a good story to share15:18
amorinI can also be "spare speaker"15:19
amorinif we have enought15:19
ttxsince the challenge is clear on public clouds, I would not mind having two15:19
ttx\ok good15:19
amorinDo you have any contact with fuga.cloud?15:19
ttxno15:19
amorinI know they are using openstack, maybe I can find a contact15:19
ttxInMotion could be interesting, they have a "openstack-as-a-service" offering that should generate a lot of spare capacity15:20
ttxOtherwise, i'd love to have someone from Verizon Media (like James Penick since they have a huge capacity15:20
ttxCloud&Heat could be fun too15:21
ttxI'll reach out to those and ask if they want to join. Any other participant suggestion?15:22
ttxgenekuo: do you have a story to tell on that topic?15:22
genekuoCapacity is actually manage by a separate team. I can ask if they are willing to talk15:23
ttx#info Belmiro will participate, Arnaud is available in case we need him, Gene will ask the capacity team15:23
ttx#info thierry to reach out to CityNetwork / Binero / InMotion/ Cloud&heat / Verizon Media15:24
ttxbelmoreira: if you do the problem statement, my added value is limited on the show, so I was wondering if you could just do the intro/outro and follow the episode script15:24
ttxThen I can focus on triaging questions and selecting good ones... it's been hard for me to do both15:25
ttxSo I'll be around, just not "on" the show15:25
ttxbelmoreira: are you ok with leading the discussion on that one?15:25
belmoreiraThat's a big challenge. i'm happy to try15:25
ttx(We'll work on the script of questions together)15:26
ttx#info Belmiro will emcee the show, thierry will be backstage selecting questions15:26
ttxAlright.. anything else on that? I'll keep y'all posted on the progress in recruiting guest speakers15:27
genekuoSounds like a good plan to me15:27
ttxalright then15:27
ttx#topic Progress/Blockers15:27
ttx* Stage 1 - Configure (amorin)15:28
ttx#link https://wiki.openstack.org/wiki/Large_Scale_SIG/Configure15:28
amorinI havnt been working on this topic for a while, dont have much time at the moment15:28
ttx++15:28
ttx* Stage 2 - Monitor (genekuo)15:29
ttx#link https://wiki.openstack.org/wiki/Large_Scale_SIG/Monitor15:29
genekuoNot much update on the wiki part15:29
genekuoMostly working on oslo.metrics stuff15:30
ttxno blocker?15:30
genekuoI would like to know the gap to a 1.0.0 release15:30
genekuoI actually put this topic in open discussion15:30
ttxok15:31
ttx* Stage 3 - Scale Up (ttx)15:31
ttx#link https://wiki.openstack.org/wiki/Large_Scale_SIG/ScaleUp15:31
ttxno progress recently, openinfra.live has been eating my bandwidth15:31
ttx# Stage 4/5 - Scale Out, upgrade & maintain (belmoreira)15:31
ttx#link https://wiki.openstack.org/wiki/Large_Scale_SIG/ScaleOut15:31
ttx#link https://wiki.openstack.org/wiki/Large_Scale_SIG/UpgradeAndMaintain15:31
belmoreiraI will use the info from the previous shows to update it. Will try to do it for the next meeting.15:32
ttxyeah... Was wondering if there was any insight to extract from our upgrades show that we could use15:32
ttxalright, next topic15:32
ttx#topic Next meetings15:32
ttxWe'll have one more IRC meeting between now and our next OpenInfra Live show15:32
ttxSo the schedule for next meetings looks like:15:33
ttx- July 7: IRC meeting15:33
ttx- July 15: OILive15:33
ttxAfter that my proposal would be to skip the meeting on July 2115:33
ttxthen have a meeting on August 4 with whoever will be around, one on August 18 and book August 26 for the next live episode.15:33
ttx(I booked August 26 for our next episode)15:33
ttxHow does that sound?15:34
genekuoNo problem for me15:34
ttx#info next meetings: July 7 IRC meeting, July 15 OpenInfra Live, July 21 skip, August 4 IRC meeting15:34
amorinaugust will be hard for me15:35
belmoreiraI can't join for the July 7 meeting15:35
amorinjuly ok15:35
ttxhmm15:35
ttxbelmoreira: July 7 we would have discussed lastminute prep for the OILive episode, so if you;re not around it's probably not worth it15:35
belmoreirabut I can catch up later with ttx15:35
ttxok, still useful to have async point15:36
ttxa sync point I mean15:36
ttxamorin: re: August I'm on the same boat... if we think we can't make a show on Aug 26, better push back the date15:37
ttxamorin: when would you be back?15:37
amorinnot before september15:37
amorinseptember 8 I think15:37
ttxmaybe we could do the Inception episode on Aug 2615:37
amorin1  will be hard also15:37
ttxsince you will sit out that one I guess15:37
amorinyup15:37
ttxthen we can plan one around monitoring early October15:38
ttxok15:38
belmoreiraplease keep the meeting for the 7. I have already my Wednesday afternoon blocked, but let's see... I may be able to join a little bit later15:38
ttx#info Next OILive episode after the Jul 15 one will be Aug 26, probably around Inception15:38
ttx#topic Open discussion15:39
ttxFloor is yours genekuo 15:39
genekuoYeah, I would like to know if there is any general guideline or a checklist to go to 1.0.0 release for projects15:39
genekuoI saw in wiki page that we currently still have 2 gaps (bandit and test coverage)15:40
genekuoCurrently I've tested the basic features and confirm it working in devstack15:41
ttxre: bandit we should enable it, and make it skip the predictable file path using "# nosec"15:41
ttxtest coverage, I have no idea how mucgh we test but it's probably minimal15:42
ttxwould be good to add more if we can15:42
ttxbut we should aim at 1.0.0 in Xena release15:42
ttxif you think it's not going to significantly change in the near future15:42
genekuoOK, I'll start working on bandit and test coverage15:43
ttxin terms of general guidelines, 1.0.0 means you apply deprecation rules, backward compatibility etc15:43
ttxso if you remove an option, you need to continue to support it as deprecated over two openstack releases, etc15:44
ttxso it's good to be suer about the API and config options and general architecture before declaring 1.0.015:44
ttxsure*15:44
ttxgenekuo: you mentioned talking with another user recently... how did that go?15:45
ttxIt's generally a good test that the lib works for several use cases15:45
genekuoThey actually figured out how to test it with the half done code I proposed15:45
genekuoHaven't got back to them to see if they have any feedback15:46
ttxok15:46
ttxmaybe that would be good to do before planting a 1.0.0 flag15:46
genekuoLet me ask them if there's any point for improvement15:46
ttxok, does that answer your questions?15:46
genekuoYep, thanks a lot!15:47
ttxAlright then... Anything else, anyone?15:47
genekuoAnother small question come up in my mind15:47
genekuoDo we gather statistics for wiki view count?15:48
genekuoWill be interesting to know how much people actually reach the wiki page15:49
amoringuys, I need to run right now, see you next week!15:49
genekuoThanks amorin!15:49
ttxunfortunately no15:49
ttxno usage stats on wiki15:49
ttxok let's close15:50
ttxThanks everyone15:50
genekuoThanks!15:50
ttx#endmeeting15:50
opendevmeetMeeting ended Wed Jun 23 15:50:10 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:50
opendevmeetMinutes:        https://meetings.opendev.org/meetings/large_scale_sig/2021/large_scale_sig.2021-06-23-15.00.html15:50
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/large_scale_sig/2021/large_scale_sig.2021-06-23-15.00.txt15:50
opendevmeetLog:            https://meetings.opendev.org/meetings/large_scale_sig/2021/large_scale_sig.2021-06-23-15.00.log.html15:50
belmoreirathanks15:50

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!