| puck | o/ | 07:59 |
|---|---|---|
| fkr | o/ | 08:00 |
| tobberydberg | o/ | 08:00 |
| tobberydberg | #startmeeting publiccloud_sig | 08:01 |
| opendevmeet | Meeting started Wed Mar 15 08:01:21 2023 UTC and is due to finish in 60 minutes. The chair is tobberydberg. Information about MeetBot at http://wiki.debian.org/MeetBot. | 08:01 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 08:01 |
| opendevmeet | The meeting name has been set to 'publiccloud_sig' | 08:01 |
| fkr | I've re-used the agenda from last time | 08:01 |
| tobberydberg | Perfect! | 08:01 |
| fkr | since from what I gathered, nothing in depth was discussed due to low attendance | 08:01 |
| tobberydberg | At least we are 3 this morning :-) | 08:01 |
| gtema | morning guys | 08:02 |
| tobberydberg | Exactly | 08:02 |
| tobberydberg | Morning! | 08:02 |
| tobberydberg | Lets kick it off | 08:02 |
| tobberydberg | Agenda here: #link https://etherpad.opendev.org/p/publiccloud-sig-meeting | 08:03 |
| tobberydberg | Please put your name in there as well | 08:03 |
| tobberydberg | #topic 1. Support in 3rd party tools that support specific clouds. (Pick up the discussion from last time, when we ran out of time) | 08:03 |
| tobberydberg | To be honest, not really sure where we left that... | 08:03 |
| puck | I don't think we reached it. | 08:04 |
| tobberydberg | Then I can stop looking for that discussion then ;-) | 08:04 |
| gtema | me neither, can't really get what exactly it is about. At least partially it may be to "let's run some form of acceptance tests with SDK/OSC and give soft of verified label for them" | 08:05 |
| puck | I've used a couple of tools that are either OpenStack compatible or S3 compatible, and they'll sometimes have preconfiguration for OpenStack based clouds. I was wondering about how we can make this easier for public clouds. | 08:05 |
| puck | s/preconfiguration for/preconfiguration for some" | 08:05 |
| gtema | problem with all those tools and public clouds is that they all have different configurations and expectations | 08:05 |
| puck | aye | 08:05 |
| gtema | i.e. openshift installer is assuming networking resources are having tags - but this is not necessarily the case | 08:06 |
| gtema | and not every tool is doing proper validation or discovery of facts and capabilities of the cloud | 08:06 |
| puck | microversion support can be intersting as well | 08:06 |
| gtema | I can understand those however - mostly this is a relatively unknown info | 08:06 |
| tobberydberg | A little bit like the work in SDK where we try to deal and abstract the complexity | 08:06 |
| puck | aye | 08:07 |
| gtema | yes, SDK target is exactly to get rid of this whole complexity and based on discovery do one thing or another thing, or just return exception - sorry, not possible | 08:07 |
| gtema | amount of code right now in sdk is pretty much loudly describes this complexity - 150k+ loc | 08:08 |
| gtema | so it is no surprise others are eventually not doing things right | 08:08 |
| tobberydberg | yea, that is a hard nut to crack indeed | 08:08 |
| tobberydberg | Are private cloud "configurations" considered in the SDK work as well, or only focus on public clouds? | 08:09 |
| gtema | well, focus is on the capability of the cloud to let info be discoverable | 08:10 |
| gtema | so in reality there is absolutely nothing what would prohibit it running well for private clouds, assuming they do things right | 08:10 |
| puck | I think private clouds should certainly be supported, however I'm sure a number won't want their details leaked. So if configuration files, or discoverability can be used, that'd be best. | 08:10 |
| tobberydberg | ok ok | 08:10 |
| tobberydberg | right | 08:10 |
| gtema | in reality we are running sdk in the backend of our cloud with custom profiles and hacks - so it works. You just need to know how to cook it | 08:11 |
| puck | Okay, so this is kinda "hmmm, they should use the SDK if possible", although not all the tools are Python, so, <shrug>. | 08:12 |
| gtema | yes, we spent really hell amount of effort to switch OSC/Ansible/Zuul/... towards using SDK. So this is definitely what everybody in the py world should do once trying to work with any OpenStack based cloud | 08:13 |
| tobberydberg | Basically it comes down to the discoverability that is lacking information? | 08:14 |
| tobberydberg | Or just that OpenStack can be configures in millions of ways so it is impossible to actually make everything discoverable | 08:15 |
| gtema | both statements are correct | 08:16 |
| puck | Maybe. Some of the tools will have drop downs with a list of pre-known clouds that include URLS or required tweaks. | 08:16 |
| gtema | that is precisely the point why interop tests in current form are currently telling nothing about real interoperability for users | 08:16 |
| puck | +1 | 08:17 |
| gtema | puck: knowing URLs is not a point here - it's more that once you know identity endpoint of the cloud everything else must be discoverable | 08:17 |
| puck | So, I guess this loops make to the verification tools we're talking about. | 08:17 |
| fkr | gtema: +1 | 08:17 |
| gtema | for that I am currently working on reforming SDK tests so that they can be executed against any cloud (public or private) | 08:18 |
| puck | nice | 08:18 |
| gtema | and that would then tell: if those tests are fine chances are great that SDK/OSC/Ansible/.. will work fine on this cloud for user (not for admin) | 08:18 |
| tobberydberg | Yea, I assume that is the way to go to make that real, probably not super easy but having "real" interop test is a must have as a starting point... | 08:18 |
| tobberydberg | exactly | 08:19 |
| tobberydberg | BTW ... do you have what you need for that work to continue gtema or can we helt or assist in any way? | 08:19 |
| gtema | so far I run those tests for Cloudera and still [ :-( ] wait for other clouds. But in reality we should consider how to treat those results | 08:20 |
| tobberydberg | Credentials to clouds or what not | 08:20 |
| gtema | that was the point for the forum discussion - discuss further items on that | 08:21 |
| tobberydberg | yeps, which is a super good topic | 08:21 |
| puck | I'm happy to facilitate some access to Catalyst Cloud as a test target. | 08:21 |
| tobberydberg | so, jumping to next topic here... | 08:22 |
| tobberydberg | #topic 2. How to proceed with the starters in https://etherpad.opendev.org/p/publiccloud-sig-specs | 08:22 |
| fkr | gtema: i think, i did point you towards https://github.com/SovereignCloudStack/docs/blob/main/community/cloud-resources/cloud-resources.md - that way we can hook you up with access to the clouds we have at hand there | 08:23 |
| gtema | great | 08:23 |
| tobberydberg | I said I would give it a stab ... haven't been able to find the time unfortunate | 08:23 |
| gtema | fkr - right. But I was sofar not able to proceed on that | 08:23 |
| fkr | tobberydberg: is that something where pairing would help? | 08:25 |
| frosty-geek | aye should be no issue to get you an account on scs1 | 08:25 |
| frosty-geek | s/scs1/gx-scs | 08:26 |
| fkr | tobberydberg: I'd be up for that, likely I'm not able to assist you with knowledge, but it would help me ;) and it might help you allocating the time :) | 08:26 |
| tobberydberg | In general for the spec ... good goal to have a first version submitted before the Summit and have a forum session about it? | 08:26 |
| tobberydberg | hahaha, good point fkr, and maybe just what is needed :-) | 08:26 |
| tobberydberg | I'm totally up for that, lets se if we can find a time in the upcoming weeks | 08:27 |
| fkr | +1 | 08:28 |
| fkr | would it make sense to have a session during the upcoming virtual ptg on that as well? | 08:29 |
| fkr | (did I break the conversation? :) | 08:31 |
| gtema | no, everyone is thinking ;-) | 08:31 |
| gtema | for my pov - +1 | 08:31 |
| tobberydberg | +1 | 08:32 |
| tobberydberg | Lets have that as one focused session for a start | 08:32 |
| tobberydberg | With that said, we need to book some time for that as well | 08:32 |
| tobberydberg | But that is the next topic. Lets leave this topic as is and plan for a focused session around this at the PTG | 08:33 |
| fkr | how does that work? | 08:34 |
| fkr | (booking the slot during ptg) | 08:34 |
| tobberydberg | #topic 3. Anything to prep for PTG session? | 08:34 |
| tobberydberg | Yea, saw some email about that... Will see if I can find it | 08:34 |
| tobberydberg | using PTG bot it seams like | 08:35 |
| puck | Is the session scheduled now? I don't see a time. | 08:37 |
| tobberydberg | https://ptg.opendev.org/ptg.html | 08:37 |
| tobberydberg | If we decide on time I can make sure to book | 08:37 |
| fkr | we can pick the day as well? (sorry, stupid first timers questions...) | 08:38 |
| tobberydberg | MONDAY, TUESDAY 1300 UTC ? | 08:38 |
| fkr | sweet | 08:39 |
| fkr | Monday > tuesday | 08:39 |
| tobberydberg | Can we solve this without a poll? ;-) | 08:40 |
| puck | Just do it. ;) | 08:40 |
| fkr | +1 | 08:40 |
| puck | I might be able to attend, unsure, I'll have my kids that week. | 08:40 |
| tobberydberg | Monday 1300 and then 3h?, so 13-16 UTC | 08:41 |
| fkr | +1 | 08:41 |
| tobberydberg | Can't SDK team in there yet, was trying to find if that clashed with your team gtema | 08:42 |
| tobberydberg | But I'll book that for now and we hope for the best | 08:43 |
| gtema | sorry, was afk - I have not booked anything for SDK yet | 08:45 |
| tobberydberg | Done ... except ptg-bot hanged on my last request | 08:45 |
| gtema | so feel free to pick suitable time | 08:45 |
| tobberydberg | +1 | 08:45 |
| fkr | tobberydberg: thanks for taking care of that | 08:45 |
| tobberydberg | Now it is booked and PTG bot woke up again :-) | 08:45 |
| puck | heh | 08:47 |
| puck | Okay, anything else today? | 08:51 |
| gtema | nothing from my side | 08:51 |
| fkr | not from my pov | 08:52 |
| puck | Possibly of interest to folks here: https://www.politico.com/news/2023/03/10/white-house-cloud-overhaul-00086595 | 08:52 |
| gtema | lol | 08:54 |
| fkr | guess we can close it then? | 08:57 |
| puck | Okay, sounds like we're done then. | 08:57 |
| gtema | yup, have a nice day folks | 08:58 |
| frosty-geek | \o | 08:58 |
| puck | \o | 08:58 |
| tobberydberg | Yes | 08:58 |
| * puck heads home from the office, 21:58 here | 08:58 | |
| fkr | \o | 08:59 |
| tobberydberg | got disconneced here... | 08:59 |
| tobberydberg | Thanks for today and have a great day! | 08:59 |
| tobberydberg | #endmeeting | 08:59 |
| opendevmeet | Meeting ended Wed Mar 15 08:59:52 2023 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 08:59 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/publiccloud_sig/2023/publiccloud_sig.2023-03-15-08.01.html | 08:59 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/publiccloud_sig/2023/publiccloud_sig.2023-03-15-08.01.txt | 08:59 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/publiccloud_sig/2023/publiccloud_sig.2023-03-15-08.01.log.html | 08:59 |
| tobberydberg | oh, shit :-) Thanks for joining extra to you :-) | 08:59 |
| puck | No worries, was here supported a Python user group meeting we were hosting where some of our folks were speaking. Then after we'd packed up, I realised that this meeting was about to start! | 09:01 |
| * puck heads off and hopes everyone has a great day | 09:03 | |
| tobberydberg | Same to you! :-) | 09:04 |
| opendevreview | OpenStack Proposal Bot proposed openstack/ha-guide master: Updated from openstack-manuals https://review.opendev.org/c/openstack/ha-guide/+/877460 | 11:21 |
| opendevreview | OpenStack Proposal Bot proposed openstack/operations-guide master: Updated from openstack-manuals https://review.opendev.org/c/openstack/operations-guide/+/877461 | 11:21 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!