08:13:42 #startmeeting publiccloud_sig 08:13:42 Meeting started Wed Apr 26 08:13:42 2023 UTC and is due to finish in 60 minutes. The chair is tobberydberg. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:13:42 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:13:42 The meeting name has been set to 'publiccloud_sig' 08:14:13 #topic 1. Summary of thoughts PTG 08:14:46 Well this topic and the next ties into each other pretty much 08:16:30 do we have any outcome of the discussion with Jimmy and co about forum proposal on certification discussion? 08:18:34 Well ... they were not sure about forum session for it, some things are already happening in that area. But, it we feel that a forum session is the right way, we will try to get that in even if deadline have passed 08:18:59 But they acknowledge the issue in general I would say 08:18:59 okay 08:19:34 I wouldn't say the totally agreed wth me with everything though 08:20:03 So, I think that we should have a session about it if possible 08:21:34 good 08:22:26 Nova team seamed ok with adding the support we talked about regarding the standard properties stuff from their end, but will take quite some time to get it in since if affect APIs. Is that a fair summary of that? 08:22:38 And the way forward for that would be a Nova backlog spec 08:22:47 yes, this is correct 08:23:02 For reference https://etherpad.opendev.org/p/march2023-ptg-publiccloud 08:23:13 and in the meanwhile SDK implementation would need to be improved to allow better client filtering 08:23:21 yes 08:23:42 to that is the way forward regarding flavors at least. 08:23:46 *so 08:24:17 For me it remains a bit unclear what is the actual outcome we're aiming for: are we fine with detail implementations or do we seek for a normative "paper"? 08:25:01 Not sure what you mean NilsMagnus[m] 08:25:32 https://specs.openstack.org/openstack/nova-specs/specs/backlog/approved/robustify-compute-hostnames.html 08:26:26 Above is an example of what we would need to produce, if that is what you mean by outcome 08:30:28 I guess we will need some discussions with Glance team as well for the images part 08:30:42 Jumping topics here... 08:30:46 #topic 3. Forum sessions Vancouver status 08:31:11 Not many here, but did you submit your proposed topic gtema ? 08:31:17 @toby: so we talked in our team here about filtering and name conventions, as an example. But how does this become "reality" for the users? Do we deem it sufficient that affected teams implement this (option 1) or do we aim for a normative document ("on public cloud matters") describing this (option 2)? 08:32:09 well, I am on sick leave right now and completely missed the deadline. There is one topic of SDK and OSC together with stephenfin 08:32:28 and the certification discussion was not submitted 08:32:48 but I am sure we can get it through if desired 08:33:12 Ok. Lets see if we can propose those outsie of the deadline 08:34:39 okay, then there is/was some confusion here, since I thought we signed up for a session, but then it's probably just me who got confused 08:35:04 trying to find email to see remember what Jimmy was thinking 08:35:12 (I was talking with Jimmy about session matters, but not specifically about this one) 08:35:16 NilsMagnus[m] .. I would say it is a combination, some changes in code would give better possibilities for "guidelines" 08:37:54 The CfP-engine is slow ... 08:39:18 I can reach out to Jimmy and see if we can get it in 08:40:06 no, I have just this poly-language-support registered as a forum session, which is touching our topic here only very reotely. +1 for reaching out to jimmy 08:41:15 Maybe even create another session regarding the standard properties? Or should we try to join/suggest thos to operator hours for Nova and Glance? 08:41:56 not sure that operator hours are fitting perfectly, but i should be still ok in my eyes 08:42:42 Better with a forum session potentially? 08:43:22 I see if I can write something up... 08:43:50 maybe even then PTG rather then forum directly? We can get more "dev" attention on the discussion 08:44:00 true 08:44:17 have you seen anything regarding team signup for PTG? 08:44:46 we can still go to operator hours to ask what other operators are thinking on some props standartisation 08:44:47 no, there was nothing so far 08:46:27 for sure 08:46:28 Good, then we hold on for that 08:46:30 #topic 4. Timeslot change proposal 08:46:52 Would like to touch on this as well, even if we are not that many people here today... 08:47:08 Would 0700 UTC work for you? 08:47:26 hehe, great to ask when just 3 person are in 08:47:48 during DST - it is ok for me, on wintertime it is surely not great anymore 08:47:58 Yea, I know ... will be hard to make a decision on that today 08:48:40 that will mean 0800 local time during winter... 08:48:49 for you that is :-) 08:49:42 saying 8:00 GMT (not UTC) 08:50:08 ah, this does not have DST either 08:50:48 this meeting is right now 0800 UTC, so 0900 during winter and 1000 during summer 08:51:04 change request is to put it an hour earlier... 08:51:13 correct, 0800 during winter time for us sitting in Europe is not too great 08:51:36 I would agree on changing it now and bringing it back in October 08:52:22 Which is totally fine for me as well. This freaking daylight saving time... 08:53:24 I can put that in the notes for this meeting for people to review and we can push the decision so people get time to comment on it. 08:53:25 right, but I would also not agree on sticking at winter time (light between 0300 - 2000 in summer is terrible) 08:54:27 I would agree to stick on summertime :-) 08:54:29 lighter longer in the afternoon, morning doesnät matter, get enough light from the screens at that time ;-) 08:55:33 I am really worrying on getting light way to early when everybody sleeps and dark when people still want to be out in garden 08:55:50 exactly 08:56:22 ANd if they also could agree to give us 20 more degrees during winder it would be awesome ;-) 08:56:34 lol 08:57:28 Anything else before we close the shop for today? 08:57:52 not from my side 09:00:14 Ok. Then I think we wrap up. Talk to you all (!!!) in two weeks ;-) 09:00:36 thank you too, see ya 09:00:49 #endmeeting