Wednesday, 2023-02-08

ttxLarge Scale SIG meeting will start in 35min!08:26
ttx#startmeeting large_scale_sig09:00
opendevmeetMeeting started Wed Feb  8 09:00:01 2023 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
opendevmeetThe meeting name has been set to 'large_scale_sig'09:00
ttx#topic Rollcall09:00
ttxWho is here for the Large Scale SIG meeting?09:00
june_yio/09:00
belmoreirao/09:00
linkso/09:00
ttxjune_yi: welcome!09:00
ttxOur agenda for today is at:09:01
ttx#link https://etherpad.openstack.org/p/large-scale-sig-meeting09:01
ttxamorin: around?09:01
ttxfelix.huettner: around?09:02
felixhuettner[m]o/09:02
ttxOK let's get started09:03
ttxI see we have a couple of new people, so maybe we can do a quick round of introductions09:03
ttxI'm Thierry Carrez, general manager for the OpenInfra Foundation and co-chair for the Large Scale SIG, trying to facilitate the discussions and sharing of experience here09:04
color_parkHi all. I'm from Samsung sds, south Korea09:04
howardHi, I am working for Samsung SDS, too.09:05
ttxcolor_park: great! I was looking forward to your presence09:05
june_yiI am working on cloud development at Samsung SDS in South Korea with color_park and howard. Nice to meet you all. I'm not familiar with irc meetings, but I'll try to follow along.09:05
ttxMaybe you can give a bit more detail on your setup at Samsung SDS, so that others on the meeting can understand what you are trying to achieve and help answer questions later in the Open discussion?09:06
belmoreiraHello, I'm Belmiro, one of co-founders of this SIG. Currently I work at ESA, managing the ground IT infrastructure.09:06
felixhuettner[m]Hi, I'm Felix working for the STACKIT Cloud offering09:07
amorin_hello!09:08
color_parksamsung sds is responsible for the network and infrastructure of all companies with samsung names. We want to support their services through openstack in the near future and furthermore, we want to get the possibility as csp through openstack :) 09:08
amorin_sorry I am late, completely forgot about the new hour09:08
*** amorin_ is now known as amorin09:09
ttxcolor_park: that is exciting. Feel free to ask our scaling experts questions as you are working through the early design choices09:09
june_yiSamsung SDS is running a local CSP business in Korea and is preparing for expansion based on OpenStack. Multi-Region, Multi-AZ is a technical challenge for us.09:09
amorinI am Arnaud Morin, working for OVHcloud as SRE, mostly involved in deploying and maintaining our Public Cloud offer bases on openstack09:09
ttxok... How about we discuss recommended options in "open discussion" at the end of the meeting? It feels like a good moment for you to engage in the Large Scale SIG09:10
ttxI bet you have plenty of questions09:11
ttxbut let's go through the regular topics of the meeting first09:11
danpaiksorry about that.  some kind of problem at work so i'm in now...09:11
ttxdanpaik: no problem, we are just getting started09:11
danpaikgreat.  my team should have made it in here though.  thx ttx.09:11
ttxWe will discuss Samsung SDS questions in open discussion at the end of our agenda09:12
ttx#topic Next Ops Deep Dive Episode09:12
ttxAs you probably know we run regular live webcasts featuing large scale users sharing their experience with a panel of operators09:12
ttxSo for our next one we need a proposed date and a proposed guest09:13
ttxHow about... April 13? that's avoiding Antelope release and PTG, and gives us time to find a guest09:13
belmoreirafirst congrats to ttx, amorin and felixhuettner[m] for the great episode 09:14
amorinwe miss you belmoreira!09:14
ttxbelmoreira amorin felix.huettner let me know if there are obvious blockers for you on that date09:14
ttxnot the same without you belmoreira ...09:14
amorinbut yes, it went fine and smoothly09:14
amorinchecking my calendar09:14
belmoreirait was very good09:15
felixhuettner[m]thanks09:15
felixhuettner[m]i'm on vaccation on april 1309:15
ttxah.09:15
amorinApril 13 is good for me09:15
ttxCould do April 6 instead09:15
amorinthat works for me also09:16
ttxfelix.huettner: you available for April 6?09:16
felixhuettner[m]that is fine for me09:16
ttxbelmoreira: any preference?09:16
belmoreirathis timeslot can always clash with a major meeting that I have... It's far away for me to know if I need to attend or not.09:18
ttx#agreed Next Large Scale OpenStack OpenInfra Live episode tentatively scheduled April 609:18
ttxAny suggestion who we should showcase there?09:18
amorinshould Societe general be available?09:19
ttxah, yes, that was in our backlog09:19
ttxI'll contact them09:19
belmoreiraThat would be great, since is a completely different use case09:19
ttxWith Samsung SDS engaging at an eearly stage with the group, I was also wondering if we could do an episode around early technical choices for a large scale deployment09:20
ttxbut the hour of the Live episode (15utc) is very inconvenient for them09:20
linkshi all, missed to introduce myself. I work in Red Hat in performance & scale team.09:20
ttxlinks: oh, welcome! 09:21
amorinnice, welcome links!09:21
felixhuettner[m]hi links09:21
ttxso... maybe something to keep in mind for a future episode09:21
felixhuettner[m]should we then maybe also do a live episode that is at a better time?09:21
danpaiksure, happy to do that in a future episode from samsung sds09:21
ttx#action ttx to reach out to Societe generale for April 6 espiode09:22
ttxok let's keep that in mind, it could make for an interesting perspective... like what would you choose if you started again from scratch today09:22
belmoreiraOpenInfra live being Asia time friendly09:23
belmoreirait's a good idea for specific episodes09:23
felixhuettner[m]and i have the feeling that this list is long09:23
ttxdanpaik: how much would the Live broadcast timing (15utc must be.. midnight your time?) be a blocker to your participation?09:24
ttxSo far we have not done episodes at another time, but I can ask09:24
amorinsomething like 9 UTC09:25
amorinthat would be asia friendly, but not US friendly :(09:25
ttxyeah one issue is that our production crew is in the US and our hosts are in Europe :)09:25
danpaikwe can do a midnight participation...09:25
danpaikit will be optional for my team but some of us can probably attend at midnight09:26
ttxdanpaik: ok, that's great to know... we'll definitely try to do one around that theme09:26
ttxwe don't need 10 people, at most 209:26
ttxvolunteers for midnight :)09:26
danpaiksure we should be able to do that09:27
ttx#info other potential guest: Samsung SDS to discuss early choices in large scale09:27
ttxOK I think I have enough to work from.09:27
ttx#topic Large Scale doc09:27
ttx#link https://docs.openstack.org/large-scale09:27
ttxThis is where we try to document the learnings of the SIG09:28
ttxit's organized as a "journey" from configuring for large scale to scaling up, scaling out, and maintaining that 09:28
*** AndroUser is now known as danpaik_mobile09:29
ttxdanpaik june_yi There might be answers to some of your questions in there already09:29
ttxteam: Anything new to report here?09:29
danpaikok we will review the site09:29
amorinnothing new on my side here, but I am pretty sure we can learn from danpaik and links09:29
felixhuettner[m]nope, nothing new from me09:29
ttxdanpaik: we are also interested in the list of things that are *not* addressed in that doc and should be... that's a good area to focus on going forward09:30
ttxso any feedback on that will be great!09:30
danpaikgot it.  we'll focus on stuff not in the doc as well09:31
ttx#topic Next meetings09:31
ttxOur next meeting will be back at the US+EU time, scheduled for Feb 22 at 15utc. I won't be available to chair it though09:31
ttxDo we have a volunteer? I'll make sure to post the reminders and let you know of progress on the Live guests09:32
ttxI'll be around to chair our next APAC+EU meeting March 8, 9utc09:32
amorinI can help09:33
ttxamorin: thanks!09:33
amorinwait , no09:33
amorinI'll be off09:33
ttxoops09:33
amorinI am taking a holiday week, sorry09:33
linksI have some experience in galera/mariadb tunings at scale. Let me rethink on it if it would be a good addition to the doc.09:33
ttxI'm a bit reluctant to skip it since now those are only happening every 4 weeks09:34
amorinlinks amazing! this is one topic we dont have yet fully covered09:34
ttxfelix.huettner: belmoreira would you be around? I'm reluctant to skipping it since it comes only every 4 weeks around now09:35
belmoreiraI can't join this meeting. Have my calendar already with conflicting meetings in this time slot... :(09:35
ttxok sounds like we should just skip it then09:35
ttxnobody will be around anyway09:35
felixhuettner[m]ok i would be there :)09:35
felixhuettner[m]but also fine for me to skip09:35
ttxWe can have a status update thread on the mailing-list to keep everyone informed on that week09:36
felixhuettner[m]links: i'm always interested in galera tuning :D09:36
ttx#info Feb 22 meeting skipped, will have a thread on the mailing-list instead to update status09:37
ttx#info EU+APAC IRC meeting March 8, 9utc09:37
ttx#topic Open discussion09:37
ttxQuestion for Samsung SDS folks: are there any questions at this stage in your project that you would like to ask our resident experts?09:38
ttxor would you like to review the documentation we already produced first? I'd recommend watching past episodes of teh Large Scale OpenStack show on OpenInfra Live too09:38
danpaikwe will prepare a set of questions for the next meeting.  we are primarily interested in using openstack at large scale across multiple regions and zones (many data centers) and haven't seen much of this yet.  09:38
danpaikwe'll do some homework over the next few weeks.  thanks everyone for the warm welcome and look forward to participating in this SIG09:39
ttxok, so your concerns are mainly on scaling out to multiple zones/clusters/regions/AZs09:39
ttxalways a great topic :)09:39
danpaikmain concern is single control plane across multiple data centers each with a separate ceph09:40
danpaikand how we can do that but maybe that's getting too detailed so we can discuss the problems we want to solve first09:40
danpaikand yes you are correct in that our concerns are mainly with scaling across regions and zones, etc.09:40
ttxdetails are good! I think that resonates with the stuff belmoreira was doing at CERN and amorin and felix.huettner are doing now09:40
danpaikthat's great.  collaboration is good!09:41
belmoreira+109:41
ttxdanpaik: it is one of the key benefits of using open infrastructure!09:41
felixhuettner[m]yep i think we definately can share a bunch of ideas09:42
danpaikwe have been working closely with mirantis as well but have some limitations across this architecture that we want to address.09:42
felixhuettner[m]allthough as always there will be no single solution09:42
ttxQuestion for the team: do you want to do anything during the virtual PTG week of March 27?09:42
amorinyup, each deployment is different, but some issues are still easy to avoid09:42
ttxdanpaik: the answer is very often "it depends" which is why discussing it is so useful.09:42
danpaikfelixhuettner[m], amorin, and others: we'll definitely have some fun discussions.09:43
amorin+109:44
felixhuettner[m]+109:44
ttxAlso... we will organize a Large Scale SIG forum session at the OpenInfra Summit in Vancouver, hpoinh to see some of you there!09:44
ttxhoping*09:44
felixhuettner[m]yep, will definately be there09:45
ttxdiscussing ity in person is even better and more productive09:45
belmoreirawill try to join09:45
danpaikwill try as well09:45
amorinunfortunately I wont be there09:46
ttxdo you think we should do something during the virtual PTG week of March 27?09:46
ttxamorin: :(09:46
amorinabout virtual PTG, I am ok to do something if we have some topics to discuss?09:46
amorinor maybe invite people talking with us?09:46
amorinwe did that in past IIRC09:46
ttxwe usually use the spot to recruit new SIG members09:46
amorinI dont remember if it was a success or not09:46
ttxbut lately that was less efficient09:47
amorinack, so maybe we should keep only the vancouver real event09:47
amorinwhich, last time in Berlin, was a great success09:47
ttxbelmoreira: you've been to a bunch, do you think it's worth our time?09:47
ttx(virtual PTG session)09:47
ttxyes, in -person gets plenty of new engagement09:47
belmoreirai the Summit definitely09:48
belmoreirain09:48
ttxok, how about we skip the virtual PTG end of March (focus on our Live episode and regular meetings, and plan to do am in -person session in Vancouver.09:49
amorin+109:49
belmoreiraVirtual PTG depends if we get people interested. It's difficult to say. At least we keep the possibility for people to ask questions and prepare the summit forum session09:50
ttx#agreed Large Scale SIG will not do a virtual PTG session end of March, but will do an in-person session in Vancouver during the summit09:50
ttxwe can change our minds if the mood changes09:50
belmoreirayeap09:50
ttxAnything other topic to discuss, anyone?09:50
amorinnop09:51
ttxThanks links danpaik june_yi color_park for joining us today! It's been one of the most active meetings we've had in a while!09:52
ttxThanks everyone for joining09:52
danpaik_mobileThanks for setting up the new time09:52
june_yi+109:52
ttxNo problem! we should have done that earlier :)09:53
ttx#endmeeting09:53
opendevmeetMeeting ended Wed Feb  8 09:53:21 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:53
opendevmeetMinutes:        https://meetings.opendev.org/meetings/large_scale_sig/2023/large_scale_sig.2023-02-08-09.00.html09:53
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/large_scale_sig/2023/large_scale_sig.2023-02-08-09.00.txt09:53
opendevmeetLog:            https://meetings.opendev.org/meetings/large_scale_sig/2023/large_scale_sig.2023-02-08-09.00.log.html09:53
belmoreirathanks everyone09:53
amorinthanks09:53
ttxYou can access the logs and minutes of the meeting through those links ^09:53
ttxand I'll send a summary to the openstack-discuss mailing-list as well09:54

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