15:00:03 <priteau> #startmeeting blazar
15:00:03 <opendevmeet> Meeting started Thu Feb  8 15:00:03 2024 UTC and is due to finish in 60 minutes.  The chair is priteau. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:03 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:03 <opendevmeet> The meeting name has been set to 'blazar'
15:00:08 <priteau> #topic Roll call
15:00:34 <priteau> o/
15:00:38 <mppowers> o/
15:01:58 <priteau> Hi Anish
15:02:22 <Anish> Hey Pierre
15:02:26 <mattcrees> o/
15:03:05 <priteau> #topic Caracal release
15:03:18 <priteau> We have 3 weeks to go until feature freeze
15:03:48 <priteau> We have merged this one
15:03:50 <priteau> 907279: Add support for specifying a custom CA bundle | https://review.opendev.org/c/openstack/blazar/+/907279
15:03:56 <priteau> And it was also backported to stable branches
15:04:11 <priteau> We have deployed it on an internal cloud, it works :)
15:04:34 <priteau> We still need to fix the blazar-dashboard in the same way, mattcrees is working on it
15:04:56 <mattcrees> Yes, I'm aiming to get it fixed before the feature freeze
15:05:35 <priteau> Anish: Thanks for updating the following patch
15:05:36 <priteau> 903613: Add non-fatal handling for enforcement exceptions | https://review.opendev.org/c/openstack/blazar/+/903613
15:06:01 <priteau> I only had minor comments so I would approve it now
15:06:16 <priteau> Could anyone else add a review too?
15:06:22 <priteau> mppowers and/or mattcrees
15:06:25 <mppowers> yes, I can do that
15:06:54 <mattcrees> I'll try and find the time tomorrow
15:07:19 <Anish> Yes. Created a WIP patch for 907907: Disabled field in computehost | https://review.opendev.org/c/openstack/blazar/+/907907
15:07:58 <Anish> There is a problem with that though. I thought we could discuss about it either now or offline.
15:08:08 <priteau> Feel free to share the issue now
15:08:37 <Anish> Mentioned it in the commit message. Setting disabled field works as desired (only admin can set/unset) Creating lease on a disabled=True node doesn't work as desired (any project and user can reserve such node) Expected behaviour: Only admins/admin project should be able to create lease on such nodes  Looks like using context policy.enforce does not work if an explicit policy is not defined. Do we need to have an
15:09:16 <Anish> in `_matching_hosts` is a user is admin or from admin project
15:10:12 <priteau> I see. I would need to look into it in more details, I don't have the answer right now.
15:10:40 <Anish> Sure. Not a problem
15:11:07 <mppowers> I believe the change uses a method that worked elsewhere in blazar to check for admin, but for some reason it isn't working there. There might be a better way to go about it all together.
15:12:21 <priteau> I can try to investigate and post feedback on the patch
15:12:50 <Anish> Thanks
15:13:10 <priteau> No more progress yet on the flavor reservation
15:13:16 <priteau> Anything else going on?
15:13:52 <mattcrees> Nothing else from me atm.
15:13:59 <mppowers> nothing from me either
15:14:03 <Anish> Nothing from me
15:15:34 <priteau> Let's finish then
15:15:37 <priteau> Thanks for joining!
15:15:41 <priteau> Bye all
15:15:41 <priteau> #endmeeting