15:00:43 <priteau> #startmeeting blazar
15:00:43 <opendevmeet> Meeting started Thu Jul 28 15:00:43 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:43 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:43 <opendevmeet> The meeting name has been set to 'blazar'
15:00:49 <priteau> #topic Roll call
15:01:38 <priteau> Hello mppowers
15:01:43 <mppowers> Hello!
15:03:20 <priteau> Hello adamcooper
15:03:58 <adamcooper> Hi priteau!
15:05:28 <priteau> #topic Zed release cycle
15:05:45 <priteau> We are about one month away from feature freeze
15:06:15 <priteau> It is on September 1st
15:06:47 <priteau> Did you have the chance to progress on your patches since our last meeting? Not much time on my side unfortunately :(
15:07:13 <mppowers> I also have do not have much time to work on my blazar patches lately
15:07:56 <mppowers> We do have some outstanding blazar work in the Chameleon fork, some of which Adam has recently been working on which may be easier to finish in time
15:08:08 <mppowers> I added a section to the PTG planning etherpad https://etherpad.opendev.org/p/april2022-ptg-blazar
15:09:38 <mppowers> I think that summarizes most of what we have different, I think you've seen most of it prior, I know Jason had some old gerrit changes he submitted that never got finished
15:09:57 <priteau> If you are happy to leave the third-party plugin aside for now, I would be happy to push this lower hanging fruit
15:10:20 <priteau> At least for the general community it would be more useful
15:10:23 <mppowers> Yes, I won't have the time this cycle to do the work on it that is required
15:12:14 <priteau> Let's focus on the smaller patches then
15:12:36 <priteau> I can take soft-delete since I wrote the original patch
15:13:50 <mppowers> OK, that sounds good. Since then, we came across an issue with it when deleting resources
15:14:17 <priteau> It's possible it's out of date with the additional changes you've made in your fork
15:14:26 <mppowers> ah perhaps
15:14:56 <priteau> Do you have some details about the issue you saw?
15:15:30 <mppowers> yes, here is the PR https://github.com/ChameleonCloud/blazar/pull/73
15:16:02 <mppowers> which adds it to the resource tables (e.g. computehosts) and the resource properties too
15:16:21 <priteau> Thanks
15:17:36 <priteau> Should we assign owners to the other patches?
15:18:13 <priteau> I need to check again the stop using trust patch
15:18:45 <mppowers> Sure, adamcooper worked on the unset resource properties and the host reallocate API endpoint for us
15:19:07 <mppowers> I'm unsure if there was interest in having the host reallocate API endpoint upstream, I think it's more useful for the Chameleon baremetal case
15:20:04 <priteau> This is sort of a manual alternative to the healing feature?
15:20:39 <mppowers> Yes, basically
15:21:40 <priteau> It might still be useful for operators
15:21:54 <priteau> If having it upstream helps with your maintenance
15:21:57 <priteau> I am ok
15:22:49 <mppowers> I think it works either way.
15:23:49 <mppowers> We also have a case for an end user to use it to swap out a specific node within their lease, and are updating the dashboard for it. Again, this may only make sense for baremetal reservations
15:25:21 <mppowers> Here is the PR with some screenshots, for a better understanding of what I mean https://github.com/ChameleonCloud/blazar-dashboard/pull/31
15:25:26 <priteau> I may make sense for host reservation of hypervisors too, if it turns out the hypervisor you reserved doesn't work exactly like intende
15:26:18 <mppowers> OK, then I think we could have adamcooper work on those changes
15:26:26 <adamcooper> Sounds good to me
15:27:13 <priteau> I've updated the etherpad
15:29:06 <mppowers> If I find time to work on blazar, I will work on updating third party plugins as discussed last meeting
15:29:25 <priteau> ok
15:29:54 <priteau> Let's move on to the next topic
15:30:09 <priteau> #topic October 2022 PTG
15:30:35 <priteau> PTG is back as an in-person event
15:30:38 <priteau> https://openinfra.dev/ptg/
15:31:28 <priteau> I don't think I will be attending. The other projects I am involved with are having virtual meetings.
15:31:42 <priteau> As such I would propose to have a virtual meeting as well.
15:32:01 <mppowers> That sounds like a good plan to me
15:33:09 <priteau> We will aim for the same week if that works for people.
15:34:15 <mppowers> that should work for me, I'm tentatively planning some time off around then, but do not have specific dates
15:34:39 <priteau> I will probably have time off the week after or the next one
15:34:51 <priteau> We could always have the meeting before or later
15:35:27 <priteau> Columbus is fairly close for you, but it would be a long trip for me ;-)
15:36:30 <mppowers> yes, I understand. I'd have to talk more with the team to see what the interest is in attending
15:37:06 <priteau> Unless you are deeply involved in contributing to an OpenStack project, I don't think it makes much sense to go.
15:37:14 <priteau> The summit would be more interesting for you
15:37:22 <priteau> Next one is Vancouver in 2023
15:38:01 <mppowers> that makes sense, I'll pencil in the summit on the calendar for now
15:38:35 <priteau> the next OpenInfra Summit in Vancouver, Canada on June 13-15, 2023.
15:39:07 <mppowers> thanks :)
15:39:27 <priteau> That's all I have for today
15:39:30 <priteau> Anything else?
15:39:53 <mppowers> nothing else from me
15:40:14 <priteau> Let's wrap up then
15:40:28 <priteau> Next meeting on August 11, if you are available.
15:40:53 <mppowers> sounds like a plan, talk to you then!
15:40:58 <priteau> Thanks for joining!
15:41:00 <priteau> #endmeeting