14:00:08 #startmeeting cloudkitty 14:00:08 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:08 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:08 The meeting name has been set to 'cloudkitty' 14:00:17 Roll count 14:00:20 \O 14:00:21 Hi! 14:03:48 #topic OpenInfra Summit Berlin 2022 14:04:18 We have two forums accepted. Now, we need to think about the approach we will adopt to conduct the forum panels. 14:04:47 First, the CloudKitty onboarding panel 14:05:12 I saw in the mailing list that we were discussing the operators feedback panel to showoff the use cases that we have 14:05:23 however, what if we used some of the use cases in the on-boarding? 14:05:33 to make the discussion more concrete 14:06:30 I thought this session was supposed to be about the project itself... 14:06:30 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:07:13 you mean, about joining the project, contributing and so on 14:07:23 and not necessarely about using cloudkitty 14:09:17 No, about CloudKitty but also explaining the architecture and how to use it. 14:09:38 You know, something for beginners. 14:09:50 I see 14:10:26 Something like CloudKitty 101, like the concept of CloudKitty, requirements, setup, troubleshooting, and so on 14:11:02 I think so. Unless it's a bad idea in your opinion. 14:11:50 I think it is fine, I was just interpreting the idea of the panel differently 14:11:56 but I like this other approach as well 14:13:11 This might be tricky to pull off without a projector/screen though... 14:13:18 exactly 14:13:23 I was going to address that now 14:13:30 what approach should we use? 14:13:48 because a panel, we will not normally have access to such material 14:14:20 It's your (and Pierre's) call; I'll only be there for the first day. 14:14:37 Sure =) 14:15:28 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:16:51 OK, what do you want to use to create this? A shared etherpad? 14:17:14 I was thinking on that 14:17:22 but, if there are no tables in the room 14:18:36 I was thinking in a flip chart 14:18:50 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:19:10 I see 14:19:18 then, an etherpad would be the best idea 14:19:21 I just don't know which collaboration tool would be the best. 14:19:37 Yeah, that's fine for me. 14:20:05 Also, do you know if people will be allowed to join the panel remotely? 14:20:34 I did not receive this information 14:21:48 Ah, OK. 14:23:18 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:24:04 Yes, this makes sense to me. 14:24:12 ok 14:24:24 onboarding -> for beginners, feedback -> for advanced users 14:24:30 I will create the two etherpads to guide these forum panels then and share with you guys 14:25:15 Thanks. Share the link and we can start working on a outline. :) 14:26:35 sure, will do that 14:26:39 I will try to do that this week 14:27:14 Thanks! 14:27:49 So, moving on 14:27:51 #topic Target reviews 14:28:12 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:27 but the bot did not execute the final merging process due to an issue in the CI 14:28:54 Ah! 14:29:02 It is probably some library issue that appeared in between the patches being validated and then merged 14:29:03 So what do we need to do? 14:29:11 I guess that the issue was resolved already by me in patch: https://review.opendev.org/c/openstack/cloudkitty/+/837442 14:29:17 which is open, and there, the CI passes 14:30:08 therefore, we could review and get that patch merged, which would both resolve one CI issue and introduce a new feature :) 14:30:20 or, I can separate that fix, if you guys prefer so 14:33:02 Either approach is fine by me. I'll check out and review 837442. 14:33:40 Ok, thanks! 14:33:52 there is also this one: https://review.opendev.org/c/openstack/cloudkitty/+/684734 14:33:59 waiting for other people's review 14:35:00 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:07 which is interesting to review and get merged 14:35:23 You already reviewed and approved the last one 14:36:53 Sure, so this one is ready to be merged, right? 14:37:19 the https://review.opendev.org/c/openstack/cloudkitty/+/684734 , yes 14:39:00 OK, done. 14:39:14 thanks! 14:39:34 but, I guess, that it is going to have a similar issue when merging as the other ones 14:43:42 and, last but not least, the open floor moment. 14:43:49 #topic Open floor moment 14:43:57 Now, I open for general questions and topics that people might have. 14:44:28 Nothing from my side. 14:46:58 Nothing else from my side as well 14:47:00 Thank you guys for participating. Have a nice week. 14:47:06 #endmeeting