15:00:07 #startmeeting blazar 15:00:07 Meeting started Thu Jul 7 15:00:07 2022 UTC and is due to finish in 60 minutes. The chair is priteau. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:07 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:07 The meeting name has been set to 'blazar' 15:00:12 #topic Roll call 15:00:19 Hi priteau, I wanted to introduce adamcooper, who is helping develop Blazar with Chameleon. 15:00:30 Hello everyone :) 15:00:50 Hello Mark and Adam 15:01:13 Good to hear that you are involved too 15:01:44 Thank you :) 15:02:17 #topic Contributions for Zed release 15:02:28 Let's review where we are 15:02:46 In terms of schedule 15:02:54 Next week is Zed-2 milestone 15:03:03 Feature freeze is Sep 1st 15:03:27 We have the following open patches: https://review.opendev.org/q/project:openstack%252Fblazar+branch:master+status:open 15:03:49 I reviewed the rpc layer removal patch 15:04:28 I left comments on Gerrit, but to summarise, I am not sure if we want to fully move all API-triggered operations to the API process 15:04:43 I agree, I'm wondering if we should abandon the patch entirely 15:04:52 This will mean there will be some interaction with other services from API and some from the manager 15:05:11 Which could make it harder to implement a distributed manager in the future 15:05:34 Does this patch make it easier to implement 3rd party plugins? 15:07:20 I'll need to update the third party plugin patch so it uses RPC, which adds some more code. But individual plugins shouldn't need to deal with RPC I think 15:07:56 Mainly, I made third party plugins dependent on this change to avoid adding the RPC code, and then removing it again once this RPC removal went through 15:08:38 I see 15:09:33 Do you think it would add much code to support RPC? 15:10:42 No I think it would add ~100, should just be creating a service file and updating the manager 15:10:50 ~100 lines that is 15:12:25 Then, if you don't object, I would prefer we go that way 15:12:37 The main motivation behind removing RPC was to increase performance, but the RPC layer only added 1/6 of a second as overhead, if the API and Manager were on the same machine in my tests. It also reduces the size of the code base slightly. But I agree that bogging down the API process for these slight advantages doesn't seem worth it 15:13:23 We can still potentially remove RPC calls for get/list which might be more frequent 15:13:32 But maybe via a later patch 15:13:45 Yes, I think then the first priority is updating third party plugins so it doesn't depend on this 15:15:39 I suppose this would be your priority for this cycle 15:16:14 In the meantime I can focus on finalising smaller patches that have been waiting for a while 15:16:30 adamcooper: are you planning to work on something specific? 15:16:45 Adam's been working on some usability and bug fixes we've identified 15:17:17 Yes, I can link them here in a moment 15:17:28 I think for the next meeting, I can share a list of what we've done and if it is of interest we can submit it 15:17:42 Ah ok 15:17:46 That would be great 15:21:02 Should we discuss at the next meeting then? 15:21:51 Yes that would be for the best, I'll be more prepared then with what changes we have in our fork 15:22:45 I am off next week, should we agree to meet 2 weeks from now? 15:23:05 I am out July 21 15:23:23 July 28 it is then 15:23:43 that works for me 15:23:49 works for me as well 15:24:55 Anything else you would like to discuss today? 15:25:33 I did not. Do you have a list of the minor patches you are working on for the zed release? 15:26:46 I recall we had a planning etherpad document, I can add Chameleon fork features there to discuss, if that works for you 15:27:28 I don't really have a list yet, as I am focusing on other projects, but I will pick a few from our plan 15:27:31 #link https://etherpad.opendev.org/p/april2022-ptg-blazar 15:27:54 OK, sounds good 15:28:53 Let's wrap up for today then. Thanks for joining! 15:29:31 Have a good day! 15:29:38 Thanks Pierre! 15:30:11 #endmeeting