| tobberydberg | Morning o/ | 08:00 |
|---|---|---|
| frickler | \o | 08:01 |
| frickler | tobberydberg: seems to be as busy as usual, do you want to start the meeting anyway? | 08:02 |
| tobberydberg | I guess we give people a couple of minutes to join.... | 08:04 |
| fkr | o/ | 08:04 |
| tobberydberg | Well, lets start and see if more joint along the meeting | 08:10 |
| tobberydberg | #startmeeting publiccloud_sig | 08:10 |
| opendevmeet | Meeting started Wed Dec 7 08:10:31 2022 UTC and is due to finish in 60 minutes. The chair is tobberydberg. Information about MeetBot at http://wiki.debian.org/MeetBot. | 08:10 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 08:10 |
| opendevmeet | The meeting name has been set to 'publiccloud_sig' | 08:10 |
| tobberydberg | as usual, agenda here: https://etherpad.opendev.org/p/publiccloud-sig-meeting | 08:10 |
| tobberydberg | #topic 1. Forum sessions Vancouver | 08:12 |
| frickler | are people really still considering travelling around the world? | 08:13 |
| tobberydberg | I first wanted to bring up a few smaller topics | 08:13 |
| tobberydberg | I wanted to ask people to think of potential forum sessions for Vancouver | 08:14 |
| fkr | wohoo :) | 08:14 |
| fkr | yes! | 08:14 |
| tobberydberg | well, don't know ... maybe that is the first question then ;-) | 08:14 |
| tobberydberg | I will :-) | 08:14 |
| tobberydberg | But at least, start to think about it, deadline is due (at least officially) mid January | 08:18 |
| fkr | ack. will think of something, and will also fish in the scs community | 08:20 |
| tobberydberg | Sounds good | 08:20 |
| tobberydberg | Lets move on | 08:20 |
| tobberydberg | #topic 2. Co-chair | 08:20 |
| tobberydberg | I thought about asking if someone would be interested to be co-chair in this SIG? | 08:22 |
| fkr | what does co-chairing mean in terms of duties? | 08:22 |
| tobberydberg | Not to many people so maybe good to bring up at some other time when we are more people :-) | 08:22 |
| tobberydberg | Well, to be honest, helping out facilitating these meetings | 08:22 |
| tobberydberg | In the longer run my personal wish is that we will start doing some actual work as well facilitated by this group, but that doesn't just apply to chairs, its for everyone so to say | 08:24 |
| fkr | sounds reasonable | 08:24 |
| fkr | I think, this kind of work is important and I do have an interest in a lively public cloud sig which usually means, one has to step up. | 08:25 |
| tobberydberg | Either way, I will be here most of the time, but I've had a lot of traveling here lately and will be plenty a head as well, and some times its hard to make the meeting | 08:26 |
| fkr | tobberydberg: I'll approach you about that in the next days and maybe discuss wether that is something where I would throw my hat in the ringt | 08:26 |
| tobberydberg | Sounds perfect fkr | 08:26 |
| tobberydberg | well, lets continue then | 08:26 |
| tobberydberg | #topic 3. Standard set of properties | 08:27 |
| tobberydberg | If I remember correctly, you had some discussions with SCS people regarding this fkr? Something interesting to report from that? | 08:28 |
| fkr | I started that but failed to follow through due to lots of other stuff. I have later today a date with a colleague of mine, where I will adress how we can collect feedback | 08:30 |
| tobberydberg | Ok, so maybe next time we can here more about that then :-) | 08:30 |
| tobberydberg | I got a ping from someone regarding the interop testing of the work we are doing here, and that is still a goal for us I firmly believe | 08:32 |
| fkr | +1 | 08:32 |
| tobberydberg | Would be super to get that in place before Vancouver | 08:32 |
| tobberydberg | I know gtema is doing some work regarding getting interop testing going from a central location and not be a self paste thing | 08:33 |
| tobberydberg | that combination, interop testing of the standard properties in that matter would be great | 08:34 |
| frickler | what gtema does is for OSC/sdk afaict, for properties something refstack-like would have to be done I think? | 08:35 |
| tobberydberg | you are right | 08:36 |
| tobberydberg | but for me that is a little bit of "interop testing" in it self :-) | 08:36 |
| tobberydberg | Sloppy expression from my side | 08:36 |
| tobberydberg | Martin Kopec from interop wg was it that reached out and asked for a collaborative brainstorming/planning session with us | 08:36 |
| tobberydberg | I personally believe that would be super to host. Potentially invite them to our next meeting? | 08:38 |
| tobberydberg | If you agree I'm happy to write him an email | 08:38 |
| frickler | sure, kopecmartin is around in e.g. #openstack-qa, too | 08:38 |
| tobberydberg | cool | 08:40 |
| tobberydberg | When it comes to the actual standard properties ... should we aim to summarize that more officially in a spec (no place to host it yet), the wiki page for the group or somewhere else? | 08:40 |
| fkr | tobberydberg: is there a ADR/PEP or similar like way of documenting such things in the openinfra universe? | 08:41 |
| tobberydberg | For the stupid person, can you explain the acronyms? ;-) | 08:42 |
| frickler | I would think continuing in the etherpad should be fine for now. we can then either create a new repo or try to find some existing place to attach to | 08:43 |
| tobberydberg | Sounds good frickler ... potentially create a stand alone etherpad for it as well if needed | 08:44 |
| tobberydberg | If I get the gist right of your question fkr I would say that it is specs that is the official way | 08:44 |
| tobberydberg | But I agree with frickler that we keep it simple for now | 08:46 |
| fkr | +1 for simple | 08:46 |
| tobberydberg | #action tobberydberg to invite interop wg to a joint session discussing how we can work together on central interop validation and standard properties | 08:47 |
| tobberydberg | anything else we should discuss on this matter right now, should we leave it at this where we create a etherpad summary and potentially get feedback from SCS how they see the matter? | 08:50 |
| tobberydberg | I'll take that as moving on :-) | 08:56 |
| tobberydberg | #topic 4. Other matters | 08:56 |
| tobberydberg | Anything else that we should discuss today? | 08:56 |
| tobberydberg | I guess not ... we leave it for today. Thanks a lot for today! | 09:00 |
| tobberydberg | #endmeeting | 09:00 |
| opendevmeet | Meeting ended Wed Dec 7 09:00:07 2022 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 09:00 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/publiccloud_sig/2022/publiccloud_sig.2022-12-07-08.10.html | 09:00 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/publiccloud_sig/2022/publiccloud_sig.2022-12-07-08.10.txt | 09:00 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/publiccloud_sig/2022/publiccloud_sig.2022-12-07-08.10.log.html | 09:00 |
| fkr | tobberydberg: sorry, overlooked your earlier question: ADR = architecture decision record, PEP= Python Enhancement Proposal | 09:00 |
| fkr | ways to document how and why certain decisions were taken so that it can be followed upon later in a good way | 09:00 |
| tobberydberg | That is what I thought, but wasn't sure about the acronyms :-) | 09:02 |
| frickler | I think that pretty much matches what openstack does in a spec, not sure we have a formal reference for that | 09:03 |
| tobberydberg | It probably does, yes | 09:03 |
| frickler | these may be useful, though the former is likely a bit outdated https://wiki.openstack.org/wiki/Blueprints https://docs.openstack.org/project-team-guide/open-development.html#specifications | 09:19 |
| ttx | #startmeeting large_scale_sig | 15:00 |
| opendevmeet | Meeting started Wed Dec 7 15:00:04 2022 UTC and is due to finish in 60 minutes. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:00 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:00 |
| opendevmeet | The meeting name has been set to 'large_scale_sig' | 15:00 |
| ttx | #topic Rollcall | 15:00 |
| amorin | o/ | 15:00 |
| ttx | Is anyone here for the Large Scale SIG meeting? | 15:00 |
| kbarrientos[m] | o/ | 15:00 |
| belmoreira | o/ | 15:00 |
| ttx | pinging frickler mnaser | 15:01 |
| * mnaser is around | 15:01 | |
| ttx | Our agenda for today is at: | 15:01 |
| ttx | #link https://etherpad.openstack.org/p/large-scale-sig-meeting | 15:02 |
| ttx | ok let's get started | 15:02 |
| ttx | #topic Next Ops Deep Dive Episode | 15:02 |
| ttx | Last week I unfortunately could not confirm either Societe Generale or Ubisoft for the Dec 8 slot | 15:02 |
| ttx | It was too late to find another guest and correctly promote the episode, so we decided to skip | 15:02 |
| ttx | The new proposed date is January 26, with Ubisoft | 15:02 |
| ttx | mnaser, amorin, belmoreira: Would that be possible for y'all to host on that day ? | 15:03 |
| amorin | checking my calendar | 15:03 |
| amorin | should be good | 15:03 |
| belmoreira | ttx it would be great if next time you ping the hosts about the final decision to cancel the episode | 15:04 |
| belmoreira | I was not sure about this outcome | 15:04 |
| ttx | ah sorry... thought that was clearer | 15:04 |
| belmoreira | sorry, after seeing mnaser proposal it wasn't clear for me | 15:05 |
| ttx | I blame mnaser | 15:05 |
| belmoreira | no worries, I defenitely misunderstood | 15:05 |
| belmoreira | :) | 15:05 |
| ttx | would Jan 26 work for you | 15:05 |
| mnaser | >:( | 15:06 |
| mnaser | i can be there | 15:06 |
| belmoreira | honestly is too soon for me to commit to the date | 15:06 |
| belmoreira | but I will keep you posted | 15:06 |
| ttx | ok | 15:07 |
| ttx | I'll collect final guest names and start a prep thread | 15:07 |
| amorin | ack | 15:07 |
| ttx | #action ttx to collect Jan 26 Ubisoft guest names | 15:07 |
| ttx | #action ttx to start an episode prep thread with hosts and guests | 15:07 |
| ttx | For the episode after that, we should try to go big and feature a 1Mcore club member | 15:08 |
| ttx | Like China Mobile, China Unicom, Walmart Labs... | 15:08 |
| ttx | Could also do YahooJapan/LINE or Workday but we had them in past episodes so would rather give priority to those | 15:08 |
| ttx | I'll work with kbarrientos[m] and Allison on getting good contacts there | 15:08 |
| kbarrientos[m] | great idea! | 15:08 |
| kbarrientos[m] | :D | 15:09 |
| ttx | Any other suggestion we should add to that list? | 15:09 |
| belmoreira | look good to me | 15:09 |
| kbarrientos[m] | yep good list for now, im sure more will come to mind later | 15:10 |
| ttx | ok... any other question / comment on that topic? | 15:11 |
| ttx | #topic Large Scale doc | 15:12 |
| ttx | #link https://docs.openstack.org/large-scale | 15:12 |
| ttx | Anything new to report here? | 15:12 |
| amorin | nothing here | 15:12 |
| amorin | I wasn't able to move the number of db connection forward yet | 15:13 |
| ttx | ack | 15:13 |
| ttx | #topic Next meetings | 15:13 |
| ttx | With an episode on January 26, I'd like to move IRC meetings to even weeks in 2023 | 15:13 |
| ttx | That means doing the next IRC meeting on January 11 rather than January 4 | 15:13 |
| ttx | Would that work for y'all? | 15:13 |
| amorin | that works for me | 15:13 |
| belmoreira | +1 | 15:13 |
| kbarrientos[m] | same | 15:14 |
| ttx | #info Next IRC meeting on January 11 | 15:14 |
| ttx | #info OpenInfra Live on January 26 | 15:14 |
| ttx | #action ttx to update IRC meetings schedule to even weeks for 2023, starting Jan 11 | 15:14 |
| ttx | #topic Open discussion | 15:15 |
| ttx | we have nothing specific posted on the agenda | 15:15 |
| ttx | Anything else, anyone? | 15:15 |
| ttx | silence is consent! | 15:17 |
| ttx | Thanks everyone | 15:17 |
| ttx | Have a great holiday period | 15:17 |
| belmoreira | thank you | 15:17 |
| kbarrientos[m] | thanks :)! | 15:17 |
| ttx | Talk to you all in 2023 | 15:17 |
| amorin | thanks! | 15:17 |
| ttx | #endmeeting | 15:17 |
| opendevmeet | Meeting ended Wed Dec 7 15:17:24 2022 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:17 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/large_scale_sig/2022/large_scale_sig.2022-12-07-15.00.html | 15:17 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/large_scale_sig/2022/large_scale_sig.2022-12-07-15.00.txt | 15:17 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/large_scale_sig/2022/large_scale_sig.2022-12-07-15.00.log.html | 15:17 |
| ttx | https://review.opendev.org/c/opendev/irc-meetings/+/866873 Move Large Scale SIG meeting on even weeks in 2023 | 15:24 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!