| opendevreview | Vanou Ishii proposed openstack/ironic stable/zed: [iRMC] Handle IPMI incompatibility in iRMC S6 2.x https://review.opendev.org/c/openstack/ironic/+/870881 | 07:03 |
|---|---|---|
| vanou | good morning ironic | 07:09 |
| arne_wiebalck | Good morning, vanou and Ironic! | 07:24 |
| vanou | Hi arne_wiebalck | 07:37 |
| rpittau | good morning ironic! o/ | 08:12 |
| vanou | Hi rpittau | 08:28 |
| rpittau | hey vanou :) | 08:28 |
| arne_wiebalck | Good morning rpittau o/ | 08:50 |
| rpittau | hey arne_wiebalck :) | 09:19 |
| kubajj | Good morning everyone! | 09:32 |
| waleedm_ | Hi guys, could you please push merging this patch https://review.opendev.org/c/openstack/ironic-python-agent/+/566544 | 09:35 |
| kubajj | dtantsur: could you have a look at https://review.opendev.org/c/openstack/ironic/+/870799 again? I've worked on it on Saturday. | 10:46 |
| kubajj | Also, does this one make any sense? https://review.opendev.org/c/openstack/ironic/+/871394 | 10:46 |
| opendevreview | Vanou Ishii proposed openstack/ironic master: [WIP] Deal with iRMC virtual media incompatibility https://review.opendev.org/c/openstack/ironic/+/823790 | 11:04 |
| dtantsur | kubajj: hey, weekend is for resting :) anyway, one issue in unit tests, everything else looks great. | 13:59 |
| opendevreview | Jakub Jelinek proposed openstack/ironic master: Reorganise Inventory Storage https://review.opendev.org/c/openstack/ironic/+/870799 | 14:15 |
| kubajj | dtantsur: That would be the ideal, but hasn't been the case for me during semester. | 14:16 |
| dtantsur | yeah, I can imagien | 14:16 |
| kubajj | dtantsur: Have you seen the https://review.opendev.org/c/openstack/ironic/+/871394 I was just guessing what should happen. Also, I had a question about the context. What context can I pass to it? | 14:17 |
| dtantsur | kubajj: I think there is a bit of layering violation: dbapi should not access object API. Since we don't need to run swift deletion in a transaction, I suggest you do it on conductor level (i.e. in destroy_node in the conductor manager). | 14:19 |
| kubajj | dtantsur: Ok, I'll just move it then | 14:20 |
| opendevreview | Jakub Jelinek proposed openstack/ironic master: Erase swift inventory entry on node deletion https://review.opendev.org/c/openstack/ironic/+/871394 | 14:54 |
| kubajj | dtantsur: I updated both of them, if you have a minute. (I'll need to rebase the second one though š®āšØ ) | 14:55 |
| JayF | Good morning | 15:01 |
| JayF | #startmeeting ironic | 15:01 |
| opendevmeet | Meeting started Mon Jan 23 15:01:12 2023 UTC and is due to finish in 60 minutes. The chair is JayF. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:01 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:01 |
| opendevmeet | The meeting name has been set to 'ironic' | 15:01 |
| dtantsur | o/ | 15:01 |
| matfechner | o/ | 15:01 |
| JayF | Who all is here for the meeting? | 15:01 |
| JayF | o/ | 15:01 |
| rloo | o/ | 15:01 |
| JayF | #topic Announcements/Reminder | 15:01 |
| vanou | o/ | 15:01 |
| JayF | As always; a reminder to be sure to review patches tagged ironic-week-prio and please tag your patches if they need review | 15:02 |
| JayF | #topic Actions from previous meetings | 15:02 |
| JayF | My action is being fulfilled later in this meeting; only other one was rpittau promising to contact VirtualPDU folks | 15:02 |
| JayF | since we have patches for 'em | 15:02 |
| rpittau | o/ | 15:02 |
| rpittau | JayF: I did contacted them but haven't got any answers | 15:03 |
| rpittau | you should be in CC btw | 15:03 |
| * rpittau is in 2 meetings at the same time | 15:03 | |
| JayF | rpittau: might wanna check to make sure you have a good email for me then; I can't find that email CC and don't remember seeing it | 15:04 |
| JayF | either way; moving on | 15:04 |
| rpittau | JayF: ack, I'll check later | 15:04 |
| JayF | #topic Review Ironic CI status & Update whiteboard if needed | 15:04 |
| JayF | I think we have a decent handle on CI for the first time in a while, yeah? | 15:04 |
| JayF | I know TheJulia was working on some kind of flakey unit test, that's landed which should help too | 15:05 |
| JayF | no other input there so I'm moving on | 15:06 |
| JayF | #topic 2023.1 Work in Progress | 15:06 |
| JayF | I also wanted us to look today not only at the status of items in progress | 15:06 |
| JayF | but also look at the full list of things we were considering for Antelope | 15:06 |
| JayF | possibly as an input into the PTG for bobcat | 15:07 |
| JayF | #link https://specs.openstack.org/openstack/ironic-specs/priorities/2023-1-workitems.html | 15:07 |
| * iurygregory is late o/ | 15:07 | |
| JayF | #link https://etherpad.opendev.org/p/IronicWorkstreams2023.1 | 15:07 |
| JayF | #link https://etherpad.opendev.org/p/ironic-bobcat-ptg | 15:07 |
| JayF | We had 7 items in the original list; only about three have ever been represented in the progress etherpad | 15:08 |
| JayF | and even if that was outta whack; I haven't seen much patch-movement on the other 4 either | 15:08 |
| JayF | are we going to get to those? | 15:08 |
| kubajj | o/ | 15:09 |
| TheJulia | o/ sick today | 15:09 |
| TheJulia | I think Steveās stuff already merged, Iāve not heard nor seen anything on active steps. | 15:10 |
| dtantsur | kubajj: do you think you could keep our inspector merging project updates in https://etherpad.opendev.org/p/IronicWorkstreams2023.1 ? | 15:10 |
| JayF | TheJulia: the conductor and scaling locking stuff? | 15:10 |
| TheJulia | Md5 is at the low end of my priority list | 15:10 |
| dtantsur | neither active steps nor RAID clean-up is moving to my best knowledge | 15:11 |
| TheJulia | JayF: yeah, I can check when Iām feeling human | 15:11 |
| JayF | ack; I didn't realize that | 15:11 |
| JayF | In the general topic of things-for-this-cycle-which-haven't-happened, I also owe some research on a bugtracker flip over | 15:11 |
| * TheJulia pulled a back muscle and now has a head cold | 15:11 | |
| JayF | I'll take an action to write something up and have it for next meeting so we can do the flipover before B | 15:11 |
| JayF | #action JayF to write up a migration plan to launchpad to present next meeting | 15:12 |
| kubajj | dtantsur: I guess so. Is there some template for it? | 15:12 |
| dtantsur | kubajj: I'll populate the today's version, you can keep it similar | 15:12 |
| JayF | I'll also migrate the items that are unstarted to the bobcat etherpad for re-consideration | 15:12 |
| JayF | it's tough for me to imagine them getting started this late (although it'd be awesome if they did :D) | 15:13 |
| JayF | going to move on now if there's no other comments on workstreams | 15:13 |
| TheJulia | Often stuff does get started late and just doesnāt merge in time to release, fwiw. It was a driving factor behind releasing more often. | 15:13 |
| JayF | I don't have any investment in getting these in "B" release in particular; I just am trying to know what's getting done and what's not :D | 15:14 |
| JayF | s/B/A/ | 15:14 |
| JayF | Speaking of releases... | 15:14 |
| JayF | #topic Future of Bugfix Releases | 15:14 |
| JayF | I think we have as much of a quorum as we'll ever get for this discussion | 15:15 |
| JayF | We (I?) have not cut any bugfix releases this cycle. | 15:15 |
| JayF | AFAICT there hasn't been much call for them so far. | 15:15 |
| JayF | I'd like to 1) Amend the policy to specify we only cut a release when there's an interested party | 15:15 |
| JayF | and 2) See if we should cut a bugfix release now-ish (if not nowish, it's awful close to A release) | 15:16 |
| JayF | and 3) Try to establish a cadence on the far side for support of bugfix branches (so they aren't ad-hoc retired like I did with several of them last week) | 15:16 |
| rpittau | JayF: I was planning a bugfix cut this week or early next week | 15:17 |
| JayF | lets make sure to cut zed with a minor version bump (so there will be room lol) before we do that rpittau | 15:17 |
| JayF | we landed a backport which was a bit of a stretch for iRMC and we wanted to get a minor version bump in zed before it was too late to account for that | 15:17 |
| rpittau | JayF: right, I'll make sure of that | 15:17 |
| JayF | I can try to make sure that happens today if you want; I think we're back in a good spot to release | 15:18 |
| rpittau | that would be great | 15:18 |
| vanou | thanks | 15:18 |
| dtantsur | whatever we decide, we need a written policy that we should try to follow | 15:18 |
| dtantsur | what we have now says "a release and a branch roughly every 2 months" | 15:19 |
| dtantsur | we're not doing it any more apparently :) | 15:19 |
| JayF | I didn't proactively cut a release that I was fairly sure there were no customers for and none of the release liasons chose to either | 15:19 |
| JayF | I'd say it wasn't an explicit decision not to do it so much as I thought it more important to cleanup the branches we had left behind first | 15:19 |
| dtantsur | I'm not blaming you, only saying that whatever we decide to actually do should be documented :) | 15:20 |
| JayF | I agree our docs should match our reality; but I think maintaining releases that have little/no users is not as good of a path as updating the docs :D | 15:20 |
| JayF | I'll push an update to that spec, that reflects my statement in #1 (we'll only cut a release if there's a downstream sponsor/consumer who requests it) | 15:21 |
| dtantsur | I assume we don't observe much usage of bugfix branches outside of OCP? | 15:21 |
| rloo | do we know how many users are using the bugfix releases? if any? | 15:21 |
| JayF | I checked the pypi stats for it once | 15:21 |
| JayF | it was a couple thousand | 15:21 |
| JayF | was hard to tell if it was "mirroring noise" vs actual users | 15:21 |
| dtantsur | JayF: updating spec is good, but I'd rather see something in the officail "releasing" docs | 15:21 |
| JayF | dtantsur: our releasing docs are the openstack ones + the spec that modifies it for ironic | 15:21 |
| JayF | dtantsur: if you're talking about a third doc, I may not know it exists :) | 15:21 |
| dtantsur | I mean https://docs.openstack.org/ironic/latest/contributor/releasing.html | 15:22 |
| JayF | going to leave that open and make sure it gets updated too | 15:22 |
| JayF | #action JayF to propose updates to release policy to make bugfix releases explicitly optional | 15:23 |
| JayF | So we've covered the first two items; I'll update the policy, rpittau is cutting a release soon | 15:23 |
| rloo | so the idea is to create the bugfix branches and do any backports to them, but NOT release unless there is a request? | 15:23 |
| JayF | I'm going to propose a doc update that says we evaluate whether or not to cut a bugfix branch at the 2nd and 4th month of the cycle | 15:24 |
| JayF | if there are sufficient changes and interested users; we cut one | 15:24 |
| JayF | otherwise we do not | 15:24 |
| JayF | and for the most part, we maintain bugfix branches to a similar standard of quality to stable branches | 15:24 |
| rloo | ok. so 1. we might not cut a bugfix branch. IF we cut a bugfix branch, will we always do one or more releases off of that bugfix branch? | 15:25 |
| JayF | yep | 15:25 |
| JayF | The other item I'd like to pull on tin this discussion -> ironic bugfix/18.1 / IPA bugfix/8.1 / inspector bugfix/10.7 are all some of the oldest branches in our CI at this point | 15:25 |
| JayF | Is downstream still consuming these? | 15:25 |
| JayF | If yes, we should keep em up, if not, maybe we should retire them out | 15:25 |
| rpittau | JayF: unfortunately downstream we're still consuming them | 15:26 |
| JayF | It's fortunate that we aren't maintining the branch for nobody :D | 15:26 |
| rpittau | lol | 15:26 |
| JayF | as long as it's in use, that's what my concern is | 15:26 |
| rloo | (I can't recall why we'd want the same bugfix branch to have more than one release if eg we have branches bugfix 10.1 & 10.2. why do we still want 10.1 releases after 10.2 is released? | 15:26 |
| rpittau | JayF: I can tell you that we're going to consume those for at least other 5 months | 15:26 |
| JayF | rpittau: it'd be neat if we could capture that info somewhere, e.g. change https://etherpad.opendev.org/p/IronicBugfixBranchCleanup into a tracking etherpad for it | 15:27 |
| rloo | does "consuming" imply that they need to keep being updated? | 15:27 |
| JayF | because I know that info is around and I wish it was written down | 15:27 |
| rpittau | JayF: I'll take care of that | 15:27 |
| rpittau | rloo: correct | 15:27 |
| JayF | rloo: so basically; the primary consumer for these bugfix releases are downstream RH releases | 15:27 |
| JayF | rloo: so as long as RH is consuming them, we'll keep backporting to them; and if/when it makes sense (and there's version-number-room) we might occassionally cut a release | 15:28 |
| rloo | so RH is consuming what is on the branch, not the actual releases from those branches? | 15:28 |
| JayF | rloo: historically, my bigger concern with these is that we had ~18 total branches that were not being consumed and were configured in CI still | 15:28 |
| JayF | rloo: yes | 15:28 |
| JayF | rloo: so we only cut releases when there's something egregiously broken enough that we don't wanna risk even a single user getting it :) | 15:29 |
| rloo | that doesn't make sense (sorry). too much overhead etc. there's got to be a simpler way. | 15:29 |
| JayF | right now a nontrivial % of that overhead is that releasing tools don't work on those branches | 15:29 |
| JayF | so it's manual work to cut one, to release one, and to retire one | 15:29 |
| rloo | (yeah, like the two PRs i backported to two bugfix branches, which i'll bring up later) | 15:30 |
| JayF | So are we to the end of bugfix branch chat? If so we can move on, otherwise happy to entertain more questions/discussion | 15:30 |
| rloo | summarize please | 15:30 |
| rloo | there were 2 issues you brought up JayF | 15:31 |
| JayF | 1) I will put in a PR for bugfix branch policy updates; it'll be easier to review the actual text instead of talking about it in chat. | 15:31 |
| JayF | 2) rpittau is cutting a bugfix release late this week or early next | 15:31 |
| JayF | 3) The oldest of our bugfix branches need to stay maintained for ~5 more months | 15:31 |
| rloo | 'a bugfix release' --> releases for all the bugfix branches we have open? | 15:32 |
| JayF | no, meaning we cut a release from master | 15:32 |
| JayF | bugfix/[version] | 15:32 |
| JayF | I don't know what version that would be, but we're talking a new branch/release line that'd be supported | 15:32 |
| rloo | ah, ok, so this would be the last bugfix branch/release we'll cut 'as per policy', before you propose that we only do ti if someone asks for it. | 15:33 |
| TheJulia | And that gives us a point to be able to release from again off that branch or someplace to put patches for intermediate releases, which the need has come up in the past | 15:33 |
| rloo | i get for intermediate releases, but i don't get why we still keep them around AFTER the major release goes out | 15:33 |
| rpittau | it's going to be bugfix/21.2 | 15:33 |
| rpittau | for iornic | 15:33 |
| rpittau | ironic* | 15:33 |
| JayF | rloo: the easiest mental model for them is "extra stable releases" | 15:34 |
| rloo | selective extra stable releases :-( | 15:35 |
| TheJulia | Because some folks donāt or are not able to jump to the next stable release, but can pull in a minor update. | 15:35 |
| rloo | since RH is using it, i'm sure there is a valid need! | 15:35 |
| JayF | ack; I'm going to move on njjow | 15:36 |
| JayF | There are no RFEs to review; skipping topic. | 15:36 |
| JayF | #topic Open Discussions | 15:37 |
| JayF | vanou had an item on the agenda about Vulnerability Management | 15:37 |
| JayF | vanou: I see you wrote quite a bit; are you are of the OpenStack VMT policy? | 15:37 |
| JayF | https://security.openstack.org/vmt-process.html | 15:37 |
| opendevreview | Baptiste Jonglez proposed openstack/networking-generic-switch master: Add ngs_ssh_disabled_algorithms setting https://review.opendev.org/c/openstack/networking-generic-switch/+/868316 | 15:38 |
| vanou | No. When I consult it on storyboard, community member says Ironic doesn't follow VMT | 15:38 |
| TheJulia | We are not a VMT managed project. | 15:38 |
| TheJulia | We do consult with them though. | 15:38 |
| dtantsur | It's a bit weird, we're following the processes but we're not tracked by the team (for some reason that probably no longer holds today) | 15:38 |
| JayF | Yeah; I was about to say; I follow VMT policy as written usually for security things w/Ironic | 15:39 |
| JayF | even if we aren't listed as following their policy | 15:39 |
| JayF | should I pull on that string and see why and "fix" it ? | 15:39 |
| dtantsur | The answer could be "our team is small" | 15:39 |
| dtantsur | but we should at least agree on an escalation path | 15:39 |
| dtantsur | so that the team does not say "we don't know about Ironic", but rather "Ironic is handled by a separate team and your contact persons are $this" | 15:40 |
| JayF | I believe that is mostly what happens in practice, alreayd | 15:40 |
| dtantsur | well, apparently we give impression that Ironic does not have a security process | 15:40 |
| TheJulia | vanou: is this providing clarity? | 15:40 |
| JayF | Yeah; which I appreciate vanou bringing to our attention | 15:40 |
| TheJulia | I think the issue is vanou didnāt find an explicit policy in our docs | 15:41 |
| rloo | is the question: why aren't we, and should we/ironic be included in that vulnerability management process? | 15:41 |
| JayF | I think the answer to that is "I don't know" and "Yes" from my perpsective rloo :D | 15:41 |
| JayF | fungi: If you're around; you happen to know the historical reason why Ironic isn't security-managed by VMT? | 15:41 |
| rloo | if no one disagrees wrt ironic being part of that process, then i think someone could volunteer to see what is needed to get ironic added? :) | 15:41 |
| fungi | ingesting context, please wait | 15:42 |
| TheJulia | It predates my time, goes back to the time of jroll or Aeva | 15:42 |
| rloo | (maybe it was when only the core openstack services were included) | 15:42 |
| TheJulia | rloo: possible | 15:43 |
| vanou | TheJulia: yes. but I think it's better to have vulnerability handlig policy. Especially like in case of Fujitsu vulnerability, there are 2 domain of code responsibility. | 15:43 |
| fungi | JayF: i don't know if it was simply because nobody did it, or because of some other reason, bit we have a process for inclusion here: | 15:43 |
| fungi | #link https://security.openstack.org/repos-overseen.html | 15:44 |
| dtantsur | Ironic would add quite a few to this list | 15:44 |
| fungi | well, maybe. you'd need to make sure each repository met the criteria | 15:44 |
| TheJulia | That is a point, we would need review the vmt polcity because a library we did not control needed to be fixed and an option had to be added to the method call with ironic | 15:45 |
| TheJulia | We, speaking in terms of ironic the project | 15:45 |
| JayF | Reading those VMT requirements; we should wait until we migrate back to launchpad. | 15:45 |
| fungi | i'm happy to be counted in "we" for purposes of helping check things | 15:45 |
| fungi | just let me know if you need assistance | 15:46 |
| JayF | But in the meantime; I'd be extremely +2 to a change to Ironic docs stating that we prefer OpenStack's VMT policy to be followed for Ironic items when it can make sense | 15:46 |
| TheJulia | +2 as well | 15:46 |
| JayF | in cases like vanou mentions; I think we're better off being a big tent | 15:46 |
| rpittau | I'm also in favor | 15:47 |
| JayF | if a library that we primarily use is vulnerable, impacting ironic, it only makes sense to treat it like an ironic vuln if the library maintainers are on board | 15:47 |
| rloo | yup, agreed. (I think we've been handling security issues already but good to make it explicit/consistent) | 15:47 |
| JayF | Does someone wanna take that doc update action? | 15:47 |
| JayF | I think I'm already like 3 action items deep :D | 15:47 |
| vanou | o/ | 15:47 |
| JayF | #action vanou to update Ironic docs to indicate we generally follow OpenStack policies around security and disclosure | 15:48 |
| vanou | I want to update. When I get stuck I'll ask you help | 15:48 |
| rloo | Thanks vanou! | 15:48 |
| JayF | please do; we're all here to help | 15:48 |
| vanou | Thanks too all! | 15:48 |
| JayF | thanks! | 15:48 |
| JayF | Anything else for Open Discussion? | 15:48 |
| rloo | so quickly | 15:48 |
| rloo | i am moving on to non-openstack stuff | 15:48 |
| rloo | this is probably the last meeting for me. i'll post something later. maybe. | 15:49 |
| vanou | Oh | 15:49 |
| JayF | Thank you for all the years and years of stacking opens rloo | 15:49 |
| rpittau | rloo: :( | 15:49 |
| vanou | Yeah. Thanks rloo | 15:49 |
| rloo | i have 2 PRs open still. both are for bugfix branches, 20.2 & 19.0. CI fails for them. I'd normally just abandon them, but the backport merged to an 18.x branch. wanted to know what you think i ought to do | 15:49 |
| rpittau | thanks for everything rloo | 15:50 |
| TheJulia | rloo: it has been great working with you! Thank you for all your contributions! | 15:50 |
| JayF | rloo: you wanna #link those here? those two changes? | 15:50 |
| rpittau | rloo: I'll check them, probably issues on CI | 15:50 |
| rloo | i'm sorry to be leaving the community but it is time I think. I've met a lot of wonderful people -- am so happy you are still working on ironic! | 15:50 |
| rpittau | and we need those for that https://review.opendev.org/q/topic:pin-tox-bugfix-ironic | 15:50 |
| rloo | https://review.opendev.org/c/openstack/ironic/+/868026 & https://review.opendev.org/c/openstack/ironic/+/868027 | 15:50 |
| fungi | rloo: you'll be missed! you've been a fixture of the community for as long as i can remember | 15:50 |
| JayF | rloo: if you're going to be gone-gone, would you like your core access migrated to "core emeritus"; so we don't have to worry about your account being compromised? | 15:50 |
| rloo | heh, fungi -- i hope you will be there forever! | 15:51 |
| JayF | (that's just a nice way of saying pulling your access but we'll give it back if you come back :D ) | 15:51 |
| rloo | JayF: yes please. | 15:51 |
| JayF | #action JayF to remove rloo from core list as she is not actively working on OpenStack anymore :( | 15:51 |
| dtantsur | rloo: oh :( this community won't be the same without you. I hope we cross the roads again | 15:51 |
| rloo | dtantsur: sigh. it has been awesome. so glad to have met many of you in person. many great memories!!! | 15:52 |
| dtantsur | indeed! | 15:52 |
| arne_wiebalck | rloo: Thanks for all the work and the contributions! (I think in all these past years, we actually never met in person :)) | 15:52 |
| dtantsur | will it make TheJulia or myself the oldest Ironicer still here? :) | 15:52 |
| rloo | oh arne_wiebalck. yes, so sorry we never met! | 15:52 |
| TheJulia | dtantsur: longest standing | 15:53 |
| rloo | will make dtantsur the oldest... | 15:53 |
| arne_wiebalck | well, the invitation for a CERN tour stands, even for ex-Ironicers, so whenever you are in the area ... :) | 15:53 |
| rloo | or would it be jay... he was 'out' for a bit so not sure. | 15:53 |
| JayF | I'm pretty sure I'd say it was dtantsur | 15:53 |
| rloo | thx arne_wiebalck! | 15:53 |
| dtantsur | :D | 15:53 |
| rloo | (has been so long i can't remember if IPA or dtansur was first) | 15:54 |
| dtantsur | I definitely was reviewing the IPA addition, which makes me think I was already a core :D | 15:54 |
| dtantsur | at least when agent_ipmitool was proposed | 15:54 |
| dtantsur | oh, memories :) | 15:54 |
| * dtantsur remembers "zapping" and sheds a tear | 15:55 | |
| JayF | Heh, the giant horrible patch of doom which had like 100+ patchsets before we gave up and broke it down into pieces lol | 15:55 |
| dtantsur | yeah! | 15:55 |
| JayF | dtantsur: I'm still sour we dropped that naming | 15:55 |
| rloo | there must be some ex-openstack/alumni community ;) | 15:55 |
| JayF | I think it's here lol | 15:55 |
| fungi | if you want to count the discussions at the bar where lifeless and devananda were debating the original design as early... | 15:55 |
| fungi | sorry, aeva | 15:56 |
| ashinclouds[m] | Memories are memories :) | 15:56 |
| rloo | ha ha. before my time. long live ironic (and openstack!) | 15:56 |
| JayF | I remember the mid-cycle at Yahoo sunnyvale (nudge nudge rloo) where we were like "how about an agent" | 15:56 |
| JayF | and Aeva looked at us like we were a child asking for a trip to disney | 15:56 |
| JayF | until we showed them the working agent lol | 15:56 |
| JayF | #endmeeting | 15:56 |
| opendevmeet | Meeting ended Mon Jan 23 15:56:59 2023 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:56 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/ironic/2023/ironic.2023-01-23-15.01.html | 15:56 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/ironic/2023/ironic.2023-01-23-15.01.txt | 15:56 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/ironic/2023/ironic.2023-01-23-15.01.log.html | 15:56 |
| dtantsur | I could not travel until the Paris summit, so I don't remember this part | 15:56 |
| JayF | we can keep talking :D | 15:57 |
| dtantsur | must be hilarious :) | 15:57 |
| fungi | ironic brainstorming was one of the first conversations i got dragged into at hp cloud. fond memories | 15:57 |
| JayF | Real talk: the only reason we even considered things other than Ironic for OnMetal, (and started building the agent and stuff outside) | 15:57 |
| rloo | that mid-cycle at yahoo was fun. harlow and i were looking at each other thinking... what the... who are all these people, etc. | 15:57 |
| JayF | was because of how many WTFs/second were generated by the iSCSI deploy driver methodology LOL | 15:57 |
| dtantsur | haha, glad I managed to get rid of it | 15:58 |
| JayF | that was a nice day :D | 15:58 |
| JayF | dtantsur: arne_wiebalck: I might be a couple minutes late to our meeting; I'll be there shortly | 15:58 |
| TheJulia | dtantsur: and surprisingly little complaint/pushback in the end! | 15:58 |
| dtantsur | JayF: ehmm.. our meeting is on Thu? | 15:58 |
| arne_wiebalck | JayF: erm ... we have a meeting? | 15:58 |
| dtantsur | at least I don't have other invites | 15:58 |
| JayF | oh, we were GOING to do it after ironic meeting, and we didn't | 15:58 |
| JayF | and for some reason it was stuck in my head we had it | 15:58 |
| JayF | lol | 15:59 |
| dtantsur | TheJulia: I think a lot of people sighed with relief :D | 15:59 |
| JayF | sorry that's what happens when second 1 of work for the day is starting a meeting :D | 15:59 |
| dtantsur | JayF: yeah, then we realized it may be too early :) | 15:59 |
| TheJulia | dtantsur: perhaps once they gave the direct driver a spin :) | 15:59 |
| * dtantsur is curious when the support for legacy boot will finally be removed | 16:00 | |
| arne_wiebalck | JayF: dtantsur: for the one on Thu ... I have conflict now ... could we do this a later, e.g. 5pm UTC? | 16:00 |
| JayF | that is going to create an uproar | 16:00 |
| dtantsur | arne_wiebalck: 5pm is doable | 16:00 |
| JayF | I have to check personal calendar for that, it's outside my normal working hours | 16:00 |
| arne_wiebalck | dtantsur: UTC, so 6pm CET | 16:00 |
| TheJulia | dtantsur: possibly never, at least one vendor is saying they will carry it on āforeverā in their firmware | 16:00 |
| dtantsur | arne_wiebalck: yep, I got it | 16:01 |
| dtantsur | TheJulia: never say never, and so on :) | 16:01 |
| TheJulia | dtantsur: or at least, they are carrying UEFI boot loader code to boot bios as a default mode | 16:01 |
| TheJulia | dtantsur: true | 16:01 |
| dtantsur | maybe in a few years we all use ARM64 | 16:01 |
| JayF | arne_wiebalck: dtantsur: moved | 16:01 |
| arne_wiebalck | JayF: should that be more in your working hours (I hesitated to propose sth earlier) | 16:01 |
| dtantsur | my wife just got a new MacBook at work, and was blissfully unaware it's not Intel until I pointed it out | 16:01 |
| arne_wiebalck | JayF: *shouldn't | 16:02 |
| JayF | arne_wiebalck: eh, it's not a big deal, just an hour on the end of my day | 16:02 |
| JayF | arne_wiebalck: and I don't have anything else booked :) | 16:02 |
| JayF | oh I just misadjusted the time | 16:02 |
| JayF | 5pm UTC is 9am my time | 16:02 |
| * JayF adjusts the meeting again | 16:02 | |
| TheJulia | dtantsur: ARM or RISC-V all the things | 16:02 |
| arne_wiebalck | :-D | 16:02 |
| JayF | So on Thurs; I had glyph for my OSS Office Hours | 16:03 |
| JayF | he was talking about as a stategy to get contributors to "scale down" | 16:03 |
| JayF | and it really has me hooked in terms of thinking about how to use Ironic in a homelab use case | 16:03 |
| arne_wiebalck | JayF: dtantsur: thanks! | 16:04 |
| dtantsur | JayF: bifrost? | 16:04 |
| JayF | dtantsur: maybe; that's still a little heavy I think but it's closer | 16:05 |
| dtantsur | metal3 on kind? | 16:05 |
| JayF | dtantsur: that is more along the lines of what I was wondering | 16:05 |
| dtantsur | I'm not sure I agree that bifrost is heavy, I wonder how you define that? | 16:05 |
| JayF | when I think of not-heavy, I'm thinking of things like ... ready to go containers | 16:06 |
| JayF | or completely ephemeral ironic's (maybe using sqlite to persist) | 16:06 |
| dtantsur | that does sound like metal3 on kind | 16:06 |
| JayF | yeah, exactly | 16:06 |
| JayF | except I never thought about being able to use it on kind | 16:06 |
| dtantsur | that's how metal3's CI is bootstrapped: it builds an "undercloud" with kind | 16:06 |
| dtantsur | or minikube | 16:06 |
| dtantsur | this undercloud deploys a control plane, and the deployment "pivots" there | 16:07 |
| dtantsur | if we ever finish the metal3 CI job, you'll see it all in action | 16:07 |
| JayF | oh yeah; I can't wait to look at that | 16:07 |
| JayF | that sounds awesome | 16:07 |
| TheJulia | Iād really like to remove the autocommit enablement ;) | 16:08 |
| * JayF starts digging foundations for a "scaling down ironic" talk at summit+1 | 16:08 | |
| dtantsur | nice! I wonder where it will be | 16:08 |
| * TheJulia is going to put down the phone and see if she can find cold meds :( | 16:08 | |
| dtantsur | I'd happily collaborate, but travel budgets are miserable today | 16:09 |
| dtantsur | TheJulia: get better and get some rest! | 16:09 |
| JayF | TheJulia: feel better o/ | 16:09 |
| vanou | TheJulia: take care :( | 16:11 |
| opendevreview | Merged openstack/ironic bugfix/20.2: Pin tox to version lower than 4 https://review.opendev.org/c/openstack/ironic/+/871099 | 16:32 |
| opendevreview | Merged openstack/ironic bugfix/19.0: Pin tox to version lower than 4 https://review.opendev.org/c/openstack/ironic/+/871098 | 16:32 |
| opendevreview | Merged openstack/ironic bugfix/21.0: Pin tox to version lower than 4 https://review.opendev.org/c/openstack/ironic/+/871097 | 16:32 |
| opendevreview | Verification of a change to openstack/bifrost stable/zed failed: Fix CI https://review.opendev.org/c/openstack/bifrost/+/871041 | 16:36 |
| kubajj | dtantsur: if you're still around, could I get re-reviews? | 16:44 |
| NobodyCam | Good Morning and Happy Monday Ironic Folks! | 16:50 |
| JayF | o/ | 16:52 |
| NobodyCam | o/ | 16:54 |
| dtantsur | kubajj: yep, looking | 16:55 |
| rpittau | good night! o/ | 16:58 |
| opendevreview | Merged openstack/bifrost master: Fix deprecated module ansible lint error https://review.opendev.org/c/openstack/bifrost/+/866040 | 17:46 |
| opendevreview | Merged openstack/bifrost master: Copy shim and grub into tftp and http directories https://review.opendev.org/c/openstack/bifrost/+/849247 | 18:07 |
| opendevreview | Merged openstack/bifrost master: Remove enable_uefi_ipxe https://review.opendev.org/c/openstack/bifrost/+/849248 | 18:07 |
| opendevreview | Jay Faulkner proposed openstack/ironic-specs master: Clarify model; bugfix branches not guaranteed https://review.opendev.org/c/openstack/ironic-specs/+/871535 | 20:41 |
| opendevreview | Jay Faulkner proposed openstack/ironic master: Clarify release docs: bugfix releases optional https://review.opendev.org/c/openstack/ironic/+/871537 | 21:01 |
| opendevreview | Jay Faulkner proposed openstack/ironic master: Clarify release docs: bugfix releases optional https://review.opendev.org/c/openstack/ironic/+/871537 | 21:22 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!