| rafaelweingartner | Hello guys! | 14:00 |
|---|---|---|
| rafaelweingartner | #startmeeting cloudkitty | 14:00 |
| opendevmeet | Meeting started Mon May 16 14:00:08 2022 UTC and is due to finish in 60 minutes. The chair is rafaelweingartner. Information about MeetBot at http://wiki.debian.org/MeetBot. | 14:00 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:00 |
| opendevmeet | The meeting name has been set to 'cloudkitty' | 14:00 |
| rafaelweingartner | Roll count | 14:00 |
| rafaelweingartner | \O | 14:00 |
| mkarpiarz | Hi! | 14:00 |
| rafaelweingartner | #topic OpenInfra Summit Berlin 2022 | 14:03 |
| rafaelweingartner | We have two forums accepted. Now, we need to think about the approach we will adopt to conduct the forum panels. | 14:04 |
| rafaelweingartner | First, the CloudKitty onboarding panel | 14:04 |
| rafaelweingartner | I saw in the mailing list that we were discussing the operators feedback panel to showoff the use cases that we have | 14:05 |
| rafaelweingartner | however, what if we used some of the use cases in the on-boarding? | 14:05 |
| rafaelweingartner | to make the discussion more concrete | 14:05 |
| mkarpiarz | I thought this session was supposed to be about the project itself... | 14:06 |
| rafaelweingartner | The operator feedback I was envisioning something more like requests/complaints from operators on what they like, what they do not like, and what they would like to change in CloudKitty in the near future | 14:06 |
| rafaelweingartner | you mean, about joining the project, contributing and so on | 14:07 |
| rafaelweingartner | and not necessarely about using cloudkitty | 14:07 |
| mkarpiarz | No, about CloudKitty but also explaining the architecture and how to use it. | 14:09 |
| mkarpiarz | You know, something for beginners. | 14:09 |
| rafaelweingartner | I see | 14:09 |
| rafaelweingartner | Something like CloudKitty 101, like the concept of CloudKitty, requirements, setup, troubleshooting, and so on | 14:10 |
| mkarpiarz | I think so. Unless it's a bad idea in your opinion. | 14:11 |
| rafaelweingartner | I think it is fine, I was just interpreting the idea of the panel differently | 14:11 |
| rafaelweingartner | but I like this other approach as well | 14:11 |
| mkarpiarz | This might be tricky to pull off without a projector/screen though... | 14:13 |
| rafaelweingartner | exactly | 14:13 |
| rafaelweingartner | I was going to address that now | 14:13 |
| rafaelweingartner | what approach should we use? | 14:13 |
| rafaelweingartner | because a panel, we will not normally have access to such material | 14:13 |
| mkarpiarz | It's your (and Pierre's) call; I'll only be there for the first day. | 14:14 |
| rafaelweingartner | Sure =) | 14:14 |
| rafaelweingartner | I guess we can prepare like a deck of slides maybe to guide the discussion, or, maybe a white sheet like a polster or something to allow us to sketch things up | 14:15 |
| mkarpiarz | OK, what do you want to use to create this? A shared etherpad? | 14:16 |
| rafaelweingartner | I was thinking on that | 14:17 |
| rafaelweingartner | but, if there are no tables in the room | 14:17 |
| rafaelweingartner | I was thinking in a flip chart | 14:18 |
| mkarpiarz | I think it would be best to use something all three of us can add content to and then use this as a guide during the panel. | 14:18 |
| rafaelweingartner | I see | 14:19 |
| rafaelweingartner | then, an etherpad would be the best idea | 14:19 |
| mkarpiarz | I just don't know which collaboration tool would be the best. | 14:19 |
| mkarpiarz | Yeah, that's fine for me. | 14:19 |
| mkarpiarz | Also, do you know if people will be allowed to join the panel remotely? | 14:20 |
| rafaelweingartner | I did not receive this information | 14:20 |
| mkarpiarz | Ah, OK. | 14:21 |
| rafaelweingartner | So, the onboarding is going to be about the initial setups and design of CloudKitty. Then, we have the operators feedback where we will present/discuss the use cases we have with Ceilometer, Prometheus, and so on. Is that it? | 14:23 |
| mkarpiarz | Yes, this makes sense to me. | 14:24 |
| rafaelweingartner | ok | 14:24 |
| mkarpiarz | onboarding -> for beginners, feedback -> for advanced users | 14:24 |
| rafaelweingartner | I will create the two etherpads to guide these forum panels then and share with you guys | 14:24 |
| mkarpiarz | Thanks. Share the link and we can start working on a outline. :) | 14:25 |
| rafaelweingartner | sure, will do that | 14:26 |
| rafaelweingartner | I will try to do that this week | 14:26 |
| mkarpiarz | Thanks! | 14:27 |
| rafaelweingartner | So, moving on | 14:27 |
| rafaelweingartner | #topic Target reviews | 14:27 |
| rafaelweingartner | The patches https://review.opendev.org/c/openstack/cloudkitty/+/830375, and https://review.opendev.org/c/openstack/cloudkitty/+/832923 were approved and merged | 14:28 |
| rafaelweingartner | but the bot did not execute the final merging process due to an issue in the CI | 14:28 |
| mkarpiarz | Ah! | 14:28 |
| rafaelweingartner | It is probably some library issue that appeared in between the patches being validated and then merged | 14:29 |
| mkarpiarz | So what do we need to do? | 14:29 |
| rafaelweingartner | I guess that the issue was resolved already by me in patch: https://review.opendev.org/c/openstack/cloudkitty/+/837442 | 14:29 |
| rafaelweingartner | which is open, and there, the CI passes | 14:29 |
| rafaelweingartner | therefore, we could review and get that patch merged, which would both resolve one CI issue and introduce a new feature :) | 14:30 |
| rafaelweingartner | or, I can separate that fix, if you guys prefer so | 14:30 |
| mkarpiarz | Either approach is fine by me. I'll check out and review 837442. | 14:33 |
| rafaelweingartner | Ok, thanks! | 14:33 |
| rafaelweingartner | there is also this one: https://review.opendev.org/c/openstack/cloudkitty/+/684734 | 14:33 |
| rafaelweingartner | waiting for other people's review | 14:33 |
| rafaelweingartner | And, I also have these others: https://review.opendev.org/c/openstack/cloudkitty/+/837200, https://review.opendev.org/c/openstack/python-cloudkittyclient/+/838724, and https://review.opendev.org/c/openstack/python-cloudkittyclient/+/839052 | 14:35 |
| rafaelweingartner | which is interesting to review and get merged | 14:35 |
| rafaelweingartner | You already reviewed and approved the last one | 14:35 |
| mkarpiarz | Sure, so this one is ready to be merged, right? | 14:36 |
| rafaelweingartner | the https://review.opendev.org/c/openstack/cloudkitty/+/684734 , yes | 14:37 |
| mkarpiarz | OK, done. | 14:39 |
| rafaelweingartner | thanks! | 14:39 |
| rafaelweingartner | but, I guess, that it is going to have a similar issue when merging as the other ones | 14:39 |
| rafaelweingartner | and, last but not least, the open floor moment. | 14:43 |
| rafaelweingartner | #topic Open floor moment | 14:43 |
| rafaelweingartner | Now, I open for general questions and topics that people might have. | 14:43 |
| mkarpiarz | Nothing from my side. | 14:44 |
| rafaelweingartner | Nothing else from my side as well | 14:46 |
| rafaelweingartner | Thank you guys for participating. Have a nice week. | 14:47 |
| rafaelweingartner | #endmeeting | 14:47 |
| opendevmeet | Meeting ended Mon May 16 14:47:06 2022 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:47 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/cloudkitty/2022/cloudkitty.2022-05-16-14.00.html | 14:47 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/cloudkitty/2022/cloudkitty.2022-05-16-14.00.txt | 14:47 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/cloudkitty/2022/cloudkitty.2022-05-16-14.00.log.html | 14:47 |
| mkarpiarz | Thanks, Rafael! | 14:48 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!