| *** mhen_ is now known as mhen | 02:26 | |
| noonedeadpunk | #startmeeting freezer | 15:03 |
|---|---|---|
| opendevmeet | Meeting started Mon Feb 9 15:03:47 2026 UTC and is due to finish in 60 minutes. The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:03 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:03 |
| opendevmeet | The meeting name has been set to 'freezer' | 15:03 |
| noonedeadpunk | #topic rollcall | 15:03 |
| noonedeadpunk | o/ | 15:03 |
| mhen | o/ | 15:03 |
| noonedeadpunk | sorry for being late | 15:03 |
| noonedeadpunk | #topic elasticsearch engine | 15:06 |
| noonedeadpunk | So, patches were pushed, as I did not get any negative feedback around them, I guess I will go along with merging them later today | 15:06 |
| noonedeadpunk | pretty much the last chance to vote against it :p | 15:07 |
| mhen | I mean many other OpenStack services do also use SQLAlchemy and they tend to have much higher processing load than I could imagine for Freezer so I think it should be fine | 15:09 |
| noonedeadpunk | yup, agreed | 15:09 |
| noonedeadpunk | #topic office hours | 15:09 |
| noonedeadpunk | I actually don't have much for agenda today | 15:09 |
| noonedeadpunk | as I think most patches and work has been merged | 15:09 |
| noonedeadpunk | I did not have much progress with central scheduling last week | 15:10 |
| noonedeadpunk | And will likely have negative time for it this week | 15:10 |
| noonedeadpunk | though feature freeze is Feb 23... | 15:10 |
| noonedeadpunk | so this feels kinda super tight... | 15:11 |
| Luzi | o/ | 15:11 |
| noonedeadpunk | doesn't mean I'm gonna stop or anything, but realistically it could mean that we won't land it for 2026.1... unless will backport it... | 15:11 |
| noonedeadpunk | which is not a suitable thing to backport to be frank | 15:12 |
| mhen | yea sounds like a pretty major architectural change | 15:12 |
| mhen | Luzi and I are currently involved in some other project so sadly we cannot offer any substantial contribution power the next few weeks either :/ | 15:13 |
| Luzi | yeah :/ | 15:13 |
| noonedeadpunk | sure, no worries at al | 15:14 |
| noonedeadpunk | how are you plans to add some kind of resource snapshots? | 15:14 |
| noonedeadpunk | are they still valid or postponed/abandoned? | 15:14 |
| mhen | while working on all the other patchsets recently I had an increasingly hard time imagining how I could fit it into the architecture of Freezer to be completely honest | 15:15 |
| mhen | especially tying all the individual backups (modes/engines) together and recreate the hierarchy of the metadata snapshot of a project | 15:16 |
| noonedeadpunk | I belive the mode/engines should be severely refactored to be frank, as I agree that's a mess today | 15:17 |
| noonedeadpunk | but yeah | 15:17 |
| noonedeadpunk | I see where the challange is | 15:17 |
| mhen | ideally, I would prefer a top-down approach: snapshot the metadata (topology) of a project (or filtered subsets of it) and then go from there to capture individual backup sources (server images, volumes etc.) | 15:18 |
| noonedeadpunk | fwiw, I've reached couple of users who tried to run freezer last year and reported issues with $things | 15:18 |
| noonedeadpunk | and got a positive feedback from one of them, that current master fixed most of their issues | 15:18 |
| mhen | oh cool | 15:18 |
| noonedeadpunk | but then it can be done on API side? | 15:19 |
| noonedeadpunk | not sure though | 15:19 |
| noonedeadpunk | The somehow interesting part is actually restoration part, as for network topology, user does not have enough permissions for full restoration | 15:22 |
| noonedeadpunk | specifically part with external networks | 15:22 |
| mhen | tracking the correct spots where individual backups belong in the whole topology is hard and backup metadata structure and contents differing between modes/engines makes it harder | 15:22 |
| mhen | yea, those parts would be placeholders that would need to be filled on restore | 15:23 |
| noonedeadpunk | from other side, freezer kinda does one architectural thing interestingly, as it runs with user privileges | 15:23 |
| noonedeadpunk | so it's abale to create vms/disks for the project without issues | 15:23 |
| noonedeadpunk | even with central thing - it will be issuing keystone trust for auth | 15:24 |
| noonedeadpunk | so that should not be a problem at least | 15:24 |
| mhen | yes, that certainly helps for the project side of things | 15:24 |
| mhen | and I find the Keystone trust approach very good | 15:25 |
| mhen | but I think at least that whole engine/mode thing needs a refactor before I would consider to pick up that project topology/metadata snapshot idea again | 15:27 |
| noonedeadpunk | ok, let's see then how it may work out... Once scheduling part is ready I'll try to check on how to refactor these | 15:27 |
| noonedeadpunk | And for the next cycle there's hopefully some help coming from my org as well for this | 15:28 |
| noonedeadpunk | ok, if that's it, I'd propose to end the meeting early | 15:29 |
| mhen | +1 | 15:29 |
| noonedeadpunk | fwiw, I'm not sure if I will be around next week. | 15:29 |
| noonedeadpunk | but will let know | 15:29 |
| mhen | ack | 15:29 |
| noonedeadpunk | #endmeeting | 15:29 |
| opendevmeet | Meeting ended Mon Feb 9 15:29:38 2026 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:29 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/freezer/2026/freezer.2026-02-09-15.03.html | 15:29 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/freezer/2026/freezer.2026-02-09-15.03.txt | 15:29 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/freezer/2026/freezer.2026-02-09-15.03.log.html | 15:29 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!