16:00:38 #startmeeting blazar 16:00:38 Meeting started Thu Jan 13 16:00:38 2022 UTC and is due to finish in 60 minutes. The chair is priteau. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:38 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:38 The meeting name has been set to 'blazar' 16:01:36 #topic Roll call 16:01:49 Hello mppowers! 16:02:02 Hello priteau 16:02:40 Is Jason joining today? 16:02:54 I think so, I'll ping 16:03:59 Hello diurnalist! 16:04:24 o7 16:04:59 Happy New Year to you both 16:05:14 Happy New Year to you too 16:06:02 Agenda for today: 16:06:07 * Blazar whiteboard 16:06:16 * Yoga release planning 16:06:31 #topic Blazar whiteboard 16:07:10 A long long time ago I created an Etherpad to act as a shared whiteboard to keep track of important notes 16:07:31 It hasn't been used much recently, but I have now refreshed it 16:07:33 #link https://etherpad.opendev.org/p/blazar-whiteboard 16:07:47 I will aim to keep it up to date from now on 16:08:22 nice 16:08:40 CI Status: will track whether CI is OK or broken. Currently only has master, but I will add branches once we have some backports to trigger jobs 16:09:07 Small patches ready to approve: if you have just a minute or two to spend on reviews, this is a list to check 16:09:27 All three are ready for you diurnalist 16:10:19 Review priorities will be listing patches that are deemed "ready to review" and of high importance for the next release 16:10:49 Needs work: patches that have been reviewed and need to be updated 16:11:23 You can also query similar things dynamically with Gerrit, but this will be a more curated list 16:11:25 sounds good, will check them out today 16:12:16 This brings us to the next topic 16:12:20 Should I add my own patches to "ready to review" once they are? Or are you managing this priteau? 16:12:47 Feel free to add your patches, at this point any of your patches are a priority :) 16:12:56 OK, will do 16:13:15 #topic Yoga release planning 16:13:37 We're past the Yoga-2 milestone now 16:14:04 The feature freeze is 6 weeks away 16:14:57 But maybe more importantly, Feb 14 - Feb 18 is final release for non-client libraries 16:15:28 This includes blazar-nova 16:16:07 So I would like to ask if you can review this revisited patch to add preemptibles support: https://review.opendev.org/c/openstack/blazar-nova/+/749151 16:16:44 There is another patch which lives inside blazar, which I am still updating, I'll try to submit it tomorrow 16:16:59 But having early feedback on the blazar-nova one would be good 16:17:09 ok 16:17:16 Other review priorities: 16:17:25 810126: Restore lease status during a non fatal lease update exception | https://review.opendev.org/c/openstack/blazar/+/810126 16:17:41 Mark has just updated it, I'll review again after this meeting 16:18:07 While testing it I discovered a bug in blazar that was introduced as part of the usage enforcement framework 16:18:08 824579: Fix lease update when resource_type parameter is missing | https://review.opendev.org/c/openstack/blazar/+/824579 16:18:35 So this is a candidate for backport to xena and wallaby 16:18:46 As is Mark's patch 16:20:11 Reservation calendar in blazar-dashboard is another important one. It's one of the next ones on my list. 16:21:46 Thanks for pointing out 805461: Update list_allocations in hosts plugin to expose start and end dates | https://review.opendev.org/c/openstack/blazar/+/805461 16:22:06 I've not reached this one yet 16:22:23 Then we have the patches that need work 16:22:46 I've left comments on resource properties patches, for both service and client 16:23:13 Third-party plugins and RPC layer, I've not yet reached, and they aren't passing CI 16:24:07 My apologies on the resource properties patch, I fixed some of the issues Jason mentioned, but accidentally proposed a new patch that reverted it. I'll still need to update to support --all though. 16:25:17 I didn't notice that. That will be quicker to fix then. 16:25:41 My comment about splitting patches is only for submissions of new changes, this one can stay in a single change 16:26:14 OK, sounds good. 16:28:54 Anything else which I may have overlooked? 16:30:22 That is all I can think of 16:31:06 It's quite a list but I think we can merge a good chunk of it 16:31:53 awesome, i will get looking at the patches today too 16:32:47 I remember you deployed, or were thinking about deploying, some early version of my preemptibles patches. Is this still active? 16:33:10 yes, though i'm not sure if it's deployed to prod. we did deploy to dev for testing 16:33:19 it was pretty straightforward if i recall 16:35:22 It would be great to get some testing of the new patches once they're up 16:36:49 Is there anything that needs to be discussed live for any of these changes? 16:37:31 mppowers: what do you think of my suggestion to replace capability by property? 16:38:06 I think it makes sense. I agree it is confusing to have both terminology 16:38:34 End users were not exposed at all to capabilities, so it's a good time to choose just one term and stick to it 16:38:57 Also property is used by many other OpenStack resources, on images, on flavors, etc. 16:39:12 agree 16:41:51 Anything else to discuss today? 16:42:31 That's all for me 16:43:31 OK. Let's keep interacting via Gerrit. 16:43:42 Thanks both for joining, and let's talk in two weeks time. 16:44:07 Talk to you then 16:44:26 #endmeeting