| tobberydberg | o/ | 07:01 |
|---|---|---|
| fkr | o/ | 07:01 |
| gtema | hey | 07:01 |
| fkr | totally forgot that we're having our scs summit ;) | 07:01 |
| gtema | lol | 07:01 |
| fkr | tobberydberg: Johan was here yesterday :) | 07:01 |
| tobberydberg | Ah, right! Going well? | 07:01 |
| fkr | totally | 07:01 |
| tobberydberg | Yea, on stage right? | 07:02 |
| fkr | indeed. with kurt. | 07:02 |
| tobberydberg | exactly | 07:02 |
| tobberydberg | A lot of people? | 07:02 |
| fkr | i'll actually have to be on a panel shortly, so I'll not be able to stick around too long | 07:02 |
| fkr | 140 people | 07:02 |
| fkr | so really good | 07:02 |
| fkr | we aimed for 100 | 07:02 |
| tobberydberg | Ok, that is great! I waned to be there, but didn't fit the schedule | 07:03 |
| tobberydberg | Ok. So lets start then | 07:03 |
| tobberydberg | #startmeeting publiccloud_sig | 07:03 |
| opendevmeet | Meeting started Wed May 24 07:03:31 2023 UTC and is due to finish in 60 minutes. The chair is tobberydberg. Information about MeetBot at http://wiki.debian.org/MeetBot. | 07:03 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 07:03 |
| opendevmeet | The meeting name has been set to 'publiccloud_sig' | 07:03 |
| tobberydberg | #topic 1. Use of domain admin users / domain manager role - Invitation to Lean Coffee @ SCS (fkr) | 07:03 |
| fkr | indeed | 07:04 |
| fkr | we want to discuss the use of domains and 'admin' role within it | 07:04 |
| fkr | (basically what also came up here again: https://lists.openstack.org/pipermail/openstack-discuss/2023-May/033803.html) | 07:04 |
| fkr | I already reached out to cleura and my proposal would be to have a joined call on June 5th 15:05 CEST | 07:05 |
| fkr | since we would like to see wether we can help push this forward, but in order to we'd like to understand better how the CSPs currently work with this | 07:06 |
| gtema | looking forward on that really. We have this in OTC and I would love upstream to have it as well | 07:06 |
| fkr | gtema: I'd really like you to join there as well :) | 07:06 |
| tobberydberg | I think that suits me fine ... will try to invite som more people internally | 07:06 |
| fkr | are there others you two are aware of, that we should actively reach out to? | 07:07 |
| tobberydberg | (FYI - I have a hard stop at 0730 UTC today, will have to drop of then) | 07:07 |
| tobberydberg | I think a email to the mailing list with the invite would be good? | 07:07 |
| gtema | yeah | 07:07 |
| fkr | I will take care of that | 07:08 |
| fkr | ok. this was what I wanted to achieve with the agenda point :) | 07:09 |
| tobberydberg | This would actually also qualify as a Forum session in vancouver...but a little bit late now... | 07:09 |
| tobberydberg | Thanks | 07:09 |
| tobberydberg | #topic 2. Further things regarding Forum session Vancouver? | 07:09 |
| gtema | since PTG is during same time we can easily put it there if necessary | 07:09 |
| fkr | aye | 07:09 |
| tobberydberg | True gtema | 07:09 |
| fkr | and some PTG rooms can be used hybrid if I understood mailing list correct | 07:09 |
| gtema | right | 07:10 |
| fkr | (that way I could join - a bit selfish here ;) | 07:10 |
| gtema | :) | 07:10 |
| tobberydberg | +1 | 07:10 |
| tobberydberg | So, regarding forum sessions .... I've added the session proposed by gtema ... haven't seen if it got to the schedule or not | 07:10 |
| gtema | great | 07:11 |
| tobberydberg | So lets wait and see | 07:11 |
| tobberydberg | Except for that, I think that qualifies to the next topic | 07:12 |
| tobberydberg | #topic 3. Planning PTG sessions Vancouver | 07:13 |
| tobberydberg | First on that topic is to schedule the session slots | 07:13 |
| gtema | I find it so difficult to plan times now. Maybe be spontan? | 07:14 |
| tobberydberg | Suggestion from my side, have two 2 hour blocks - wednesday and thursday afternoons | 07:14 |
| fkr | (am silent, since i'll not be physically there ;) | 07:15 |
| tobberydberg | I feel the same way, but I think it would be good with some plan, for others to plan as well | 07:15 |
| gtema | agree on both (proposal) | 07:16 |
| tobberydberg | the thought with two blocks is more to give option for people to join if they have a block at one slop | 07:17 |
| fkr | +1 | 07:17 |
| tobberydberg | What topics to we want to cover? | 07:17 |
| gtema | testing (certification) | 07:18 |
| tobberydberg | Way forward with the standard properties? Or should that move into various teams meetings? | 07:18 |
| gtema | surely continue discussion on properties agreements | 07:18 |
| tobberydberg | testing of course, will be as a followup of the forum session | 07:19 |
| gtema | with teams we can discuss what we want. But we perfectly know that what they agree on will not come immediately | 07:19 |
| gtema | so we need to do some interim steps ourselves | 07:19 |
| tobberydberg | Maybe have a BoF kind of thing if we have newcomers? | 07:19 |
| tobberydberg | agreed | 07:19 |
| fkr | +1 on the properties | 07:19 |
| gtema | do we have newcomers (/me scratching my neck) | 07:20 |
| gtema | ? | 07:20 |
| fkr | gtema: yes | 07:20 |
| gtema | ahso - ok | 07:20 |
| fkr | gtema: tobberydberg and I have been in touch with them and they will join vancouver iirc | 07:20 |
| gtema | awesome | 07:20 |
| fkr | or we've been reached out to (is the better wording) | 07:21 |
| tobberydberg | There were a few in Berlin as well that I haven't talked to since then, hopefully some of them join in vancouver as well | 07:21 |
| tobberydberg | The domain admin thing would be another candidate indeed | 07:22 |
| fkr | +1 | 07:22 |
| tobberydberg | For me, roles in general ... I personally don't really get my head around all of that | 07:23 |
| gtema | you are right | 07:23 |
| gtema | btw - over the weekend were discussing with noonedeadpunk in sdk room things around service catalog and abilities to hide out non public endpoints | 07:24 |
| gtema | with also ability to override endpoints based on the domain used | 07:24 |
| puck | Apologies for being late. | 07:25 |
| gtema | this is not really sdk topic, but I see it also fitting the publiccloud domain | 07:25 |
| tobberydberg | fair thing as well | 07:25 |
| tobberydberg | welcome puck :-) | 07:25 |
| fkr | hey puck | 07:25 |
| puck | Just seeing a little bit on this topic, we're interested in using domains to provide our customers a better experience. | 07:26 |
| tobberydberg | I said earlier that I need to drop out at 0730 UTC .... but I can make one of you chair if you would like to continue discussing | 07:27 |
| tobberydberg | Will you be in vancouver puck? I might have asked you this previously as well | 07:27 |
| fkr | I'll jump out now. talk to you later. | 07:28 |
| puck | I don't think you have. Unfortunately it is highly unlikely I will be there (would love to visit Canada though, I'm Canadian, just never been there) | 07:28 |
| fkr | puck: then you and me are the remotees for the PTG ;) - so I'm not alone. that is good. | 07:29 |
| puck | aye | 07:29 |
| tobberydberg | Ok :-) Yea, nice country and Vancouver super nice city | 07:29 |
| puck | Seems that if two of you will be dropping out of the meeting, there isn't much point in me talking to myself. :) | 07:30 |
| tobberydberg | puck and gtema ... will you continue the meeting or should I and it now? | 07:30 |
| gtema | I would say end | 07:30 |
| puck | Oh, two of us. I think we might as well end. | 07:30 |
| tobberydberg | Ok, then I'll end the meeting now. We can continue discussion here even outside of meeting if needed | 07:31 |
| gtema | great | 07:31 |
| tobberydberg | Take care and thanks for today! | 07:31 |
| tobberydberg | #endmeeting | 07:31 |
| opendevmeet | Meeting ended Wed May 24 07:31:24 2023 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 07:31 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/publiccloud_sig/2023/publiccloud_sig.2023-05-24-07.03.html | 07:31 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/publiccloud_sig/2023/publiccloud_sig.2023-05-24-07.03.txt | 07:31 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/publiccloud_sig/2023/publiccloud_sig.2023-05-24-07.03.log.html | 07:31 |
| gtema | have a nice day folks | 07:31 |
| puck | Likewise, time to rustle up some dinner here. | 07:31 |
| noonedeadpunk | sorry wasn't being in time, but yeah, alternate catalogs and it's filtering I'd say is public cloud topic for sure | 08:28 |
| stenstad | gtema: We have that implemented in our system, no endpoints enabled by default, and customer can enable the services (endpoints) they want via web interface. When they enable the service, we add the endpoint to keystone and also set up resource limits. Customers can only enable services if they have valid billing. | 12:13 |
| stenstad | I'm going to Vancouver, would love to chat about it there. Haven't been to the summit since Tokyo. | 12:14 |
| frickler | stenstad: that sounds interesting, are you using keystone endpoint groups for that? also I assume that this is a closed-source implementation? | 12:46 |
| stenstad | Yes, we're using endpoint groups with project_endpoint_group mappings. It has evolved over the years to adapt to Keystone changes. It's closed source in terms of it not really being anything special (I assume everyone is doing this?) and integrated in internal management system. | 12:50 |
| stenstad | After user has been thru registration process (custom workflow on horizon server), and account is activated by us (admin backend), domain gets enabled in Keystone. After they add billing option/get verified for credit (custom horizon panel) they are able to enable services. Enabling a service (defined in admin backend) will add all endpoint dependencies to enable that service, and also set up limits on the account. | 12:55 |
| stenstad | In our admin backend we define a service with descriptions (shown to user), endpoint groups to add to project, roles to add to project, and dependencies on other services. I.e. the LB (Octavia + Amphora) service has dependencies on Compute service and Secrets (Barbican) service. Also tags for "hidden" services, default services (like keystone), beta or private/dev/testing services that are only available for cloud admins. | 13:01 |
| stenstad | Ofcourse, this only affects the catalog, so you have to set quotas to 0 where you can.. | 13:01 |
| knikolla | o/ | 14:30 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!