opendevreview | Merged openstack/nova master: Allow autopep8 to fix more things https://review.opendev.org/c/openstack/nova/+/949292 | 03:13 |
---|---|---|
opendevreview | Merged openstack/nova master: reorder and extend pre-commit hooks https://review.opendev.org/c/openstack/nova/+/949299 | 03:13 |
opendevreview | Merged openstack/nova master: Return HTTP400 for multi spec pci alias if PCI in Placement https://review.opendev.org/c/openstack/nova/+/951007 | 03:28 |
opendevreview | Merged openstack/nova master: Multiple spec per PCI alias limitation https://review.opendev.org/c/openstack/nova/+/944062 | 03:28 |
opendevreview | Merged openstack/nova master: Validated that PCI alias has proper ids https://review.opendev.org/c/openstack/nova/+/951129 | 03:28 |
opendevreview | Merged openstack/nova master: Validate [pci]alias at service startup https://review.opendev.org/c/openstack/nova/+/951143 | 03:31 |
opendevreview | Merged openstack/nova master: Cache [pci]alias parsing https://review.opendev.org/c/openstack/nova/+/951151 | 03:31 |
opendevreview | Rajesh Tailor proposed openstack/nova master: Add support for showing instance-action finish_time https://review.opendev.org/c/openstack/nova/+/928933 | 06:38 |
Uggla | melwitt, I think you are right, we forget about this patch. | 06:46 |
opendevreview | Rajesh Tailor proposed openstack/nova master: Fix instance vm_state during shelve https://review.opendev.org/c/openstack/nova/+/934294 | 06:58 |
*** sambork_ is now known as sambork | 08:40 | |
opendevreview | Rajesh Tailor proposed openstack/nova-specs master: Show finish_time field in instance action show https://review.opendev.org/c/openstack/nova-specs/+/929780 | 10:22 |
opendevreview | Rajesh Tailor proposed openstack/nova-specs master: Show finish_time field in instance action show https://review.opendev.org/c/openstack/nova-specs/+/929780 | 11:08 |
opendevreview | Rajesh Tailor proposed openstack/nova-specs master: Show finish_time field in instance action show https://review.opendev.org/c/openstack/nova-specs/+/929780 | 11:47 |
opendevreview | Rajesh Tailor proposed openstack/nova-specs master: Show finish_time field in instance action show https://review.opendev.org/c/openstack/nova-specs/+/929780 | 12:02 |
opendevreview | Johannes Beisiegel proposed openstack/nova master: Adds packing_host_pci_numa_cells_allocation_strategy option https://review.opendev.org/c/openstack/nova/+/952451 | 12:58 |
opendevreview | Balazs Gibizer proposed openstack/nova stable/2025.1: Add functional reproducer for bug 2102038 https://review.opendev.org/c/openstack/nova/+/952452 | 13:25 |
opendevreview | Balazs Gibizer proposed openstack/nova stable/2025.1: Return HTTP400 for multi spec pci alias if PCI in Placement https://review.opendev.org/c/openstack/nova/+/952453 | 13:25 |
opendevreview | Balazs Gibizer proposed openstack/nova stable/2025.1: Multiple spec per PCI alias limitation https://review.opendev.org/c/openstack/nova/+/952454 | 13:26 |
opendevreview | Balazs Gibizer proposed openstack/nova stable/2025.1: Validated that PCI alias has proper ids https://review.opendev.org/c/openstack/nova/+/952455 | 13:26 |
opendevreview | Balazs Gibizer proposed openstack/nova stable/2025.1: Validate [pci]alias at service startup https://review.opendev.org/c/openstack/nova/+/952456 | 13:26 |
opendevreview | Balazs Gibizer proposed openstack/nova stable/2025.1: Cache [pci]alias parsing https://review.opendev.org/c/openstack/nova/+/952457 | 13:26 |
opendevreview | Merged openstack/nova master: api: Add response body schemas for hypervisors APIs (3/3) https://review.opendev.org/c/openstack/nova/+/937247 | 13:57 |
opendevreview | Merged openstack/nova master: api: Address issues with hypervisors APIs https://review.opendev.org/c/openstack/nova/+/950867 | 14:16 |
stephenfin | sean-k-mooney: Every +W'd openapi patch is now merged and gmaan has most of the outstanding patches reviewed. The ball's in your court now if you're happy/eager for us to keep moving on these 🙏 | 14:29 |
opendevreview | Moritz Wanzenböck proposed openstack/nova master: Implement extend_volume for local devices https://review.opendev.org/c/openstack/nova/+/878763 | 14:38 |
sean-k-mooney | stephenfin: ack. not today but ill try and do a pass on some/all them tomorrow | 14:38 |
sean-k-mooney | thats really good progress | 14:39 |
stephenfin | thanks | 14:39 |
stephenfin | and yes, great progress | 14:39 |
sean-k-mooney | so there are 16 patches i think for nova outstanding. do you stil have another batch on your github once this next bactch is done or is this the full set - any followups needed | 14:40 |
sean-k-mooney | stephenfin: context im tryign to decied if i think we can get this compleded by m2 or not | 14:41 |
sean-k-mooney | it woudl be nice if we can but im not sure how much review time i can dedicate between now and then | 14:42 |
stephenfin | Ah, there's quite a few patches still outstanding. 20 in total, targeting 14 APIs (I've split the servers one up into 6 patches, as you've already seen) | 14:43 |
stephenfin | When is m2? Assuming it's less than ~6 weeks away, that sounds optimistic | 14:43 |
sean-k-mooney | so the 16 that are open and ~20 after. ok well i hope we can land the first batch of 16 before m2 and we can then continut with the rest. its july 3rd i think | 14:44 |
sean-k-mooney | so 3 weeks time | 14:44 |
sean-k-mooney | that not a deadline by any means i just wanted to knwo were we were since i knew you proviosly had more patches that were pending | 14:45 |
sean-k-mooney | i dont knwo what gmaan PTO plans are like and im also aware that they have the policy work to do this cycle so im just trying to guage it we are likely to get this compelte this cyle. i think we are still on track to do that | 14:46 |
opendevreview | sean mooney proposed openstack/nova master: [DNM] testing rdo experimental jobs https://review.opendev.org/c/openstack/nova/+/927762 | 14:47 |
sean-k-mooney | gibi: as an fyi whiel that "works" we get some volume related test failures if i recall corectly | 14:48 |
sean-k-mooney | im not really sure why | 14:48 |
sean-k-mooney | gibi: ^ we also need to clean up the fr2 branch of the operator to remvoe the duplicate definiton of the pragm that may or may not cause that job to fail | 14:49 |
sean-k-mooney | gibi: if it does nto work as exepcted let me knwo an ill take a quick look | 14:49 |
gibi | sean-k-mooney: thanks. I just told the story about this possibility to artom and then I wanted to see if it still works | 14:53 |
gibi | I will report back | 14:53 |
sean-k-mooney | we have the watcher-operator reporting on changes to master opendev.org prs | 14:54 |
sean-k-mooney | we had to swap it to use c10s contianers | 14:54 |
sean-k-mooney | so its defintly possibel btu this is actully going to break because we dropped 3.9 supprot | 14:54 |
sean-k-mooney | gibi: we can chat downstream about how to prot the test change form watcher-operator to nova-operator to make this work if your interested | 14:55 |
sean-k-mooney | although maybe not this evening | 14:55 |
sean-k-mooney | the short version is https://github.com/openstack-k8s-operators/watcher-operator/blob/main/.zuul.yaml#L308-L344 defiens a c10s based job that will run on all changes ot opendev master for watcher | 14:57 |
sean-k-mooney | we have both watcher and epoxy version fo those jobs so that we will be able to do some testing on stable/2025.1 to if needed | 14:57 |
sean-k-mooney | https://github.com/openstack-k8s-operators/watcher-operator/blob/main/.zuul.yaml#L153-L270 | 14:57 |
sean-k-mooney | chandan got all that working in the last month or so, if we want to improve our upstream nova testign we can definetly do that in the future | 14:58 |
gibi | thanks for the pointers | 15:00 |
gmaan | sean-k-mooney: no PTO planned until Sept. for policy, yes that is what I will be pushing now. but I will keep eyes on stephenfin series if anything new or need re-review | 15:16 |
sean-k-mooney | gmaan: just as a follow up any removal of the tempest policy tests wont happen until 2025.1 goes to unmaintaed right | 15:17 |
sean-k-mooney | so it will be removed in 2026.2 or 2027.1 ish | 15:18 |
gmaan | sean-k-mooney: there are no specific policy tests there but idea is to move the tempest tests to move to new defaults (as default) and we have one job testing tempest on old defaults also | 15:18 |
sean-k-mooney | sorry not policy | 15:19 |
sean-k-mooney | i ment the schema validation | 15:19 |
sean-k-mooney | so updating tempest to nolonger needign to validate the repsocne once stephens seriss is supported on all stable branches | 15:19 |
sean-k-mooney | assuming 2025.2 is the first release with fully coverage we need to keep the nova schema test until 2025.1 moves to unmainted right? | 15:20 |
gmaan | ok. we can discuss that if we need to remove but anyways that can only happen after 2026.1 to unmaintained (if Nova implement all in 2025.2). But we discussed in last PTG, we might keep both side | 15:21 |
sean-k-mooney | well once we have the coverage in tree | 15:21 |
sean-k-mooney | we shoudl not need to ask people to extend the tempest schdma validation for new changes | 15:21 |
sean-k-mooney | that really what im poking at. only doing that in one place, in nova going forwarwad instead o both in nova and tempest | 15:22 |
sean-k-mooney | but your right we can discuss that at the next ptg | 15:23 |
gmaan | I am ok for that but let's discuss during 2026.1 unmaintained status change time. if no objection then I am ok to remove | 15:23 |
sean-k-mooney | well its 2025.1 not 2026.1 | 15:23 |
sean-k-mooney | anyway not todays problem :) | 15:24 |
gmaan | next PTG might be too early, anyways we need to keep them until 2026.1 (after 2025.2 EOL but I am considering 2026.1 as immediate SLURP after Nova has all schema) | 15:24 |
sean-k-mooney | right but its not when the first slurp that supprot it that is imporant | 15:24 |
sean-k-mooney | it when the last slurp that does not that matters | 15:24 |
sean-k-mooney | so its when 2025.1 goies unmaintined that tempest could consider removing the vlaidation | 15:25 |
sean-k-mooney | which will likely be during the 2026.2 or 2027.1 cycle | 15:25 |
gmaan | yeah, SLURP thing does not need to be mandatory as such. 2025.1 unmaintained is also ok | 15:27 |
gmaan | I will say let's discuss during 2026.1/2027.1 PTG when 2025.1 is moving to unmaintained | 15:28 |
stephenfin | gmaan, sean-k-mooney: Joining late, but we can/should just copy-paste the schemas from Nova to Tempest | 15:57 |
gmaan | yeah, if Nova required schema to implement during API change then it is not big deal to keep Tempest one also up to dated | 15:58 |
gmaan | as Tempest hats on, I can make sure those are syncup and tempest has all schema covered. I already started that for current schema https://review.opendev.org/q/topic:%22latest-microversion-testing%22 | 16:09 |
opendevreview | Balazs Gibizer proposed openstack/nova stable/2024.2: Add functional reproducer for bug 2102038 https://review.opendev.org/c/openstack/nova/+/952478 | 16:45 |
opendevreview | Balazs Gibizer proposed openstack/nova stable/2024.2: Return HTTP400 for multi spec pci alias if PCI in Placement https://review.opendev.org/c/openstack/nova/+/952479 | 16:45 |
opendevreview | Balazs Gibizer proposed openstack/nova stable/2024.2: Multiple spec per PCI alias limitation https://review.opendev.org/c/openstack/nova/+/952480 | 16:45 |
opendevreview | Balazs Gibizer proposed openstack/nova stable/2024.2: Validated that PCI alias has proper ids https://review.opendev.org/c/openstack/nova/+/952481 | 16:45 |
opendevreview | Balazs Gibizer proposed openstack/nova stable/2024.2: Validate [pci]alias at service startup https://review.opendev.org/c/openstack/nova/+/952482 | 16:45 |
opendevreview | Balazs Gibizer proposed openstack/nova stable/2024.2: Cache [pci]alias parsing https://review.opendev.org/c/openstack/nova/+/952483 | 16:45 |
JayF | TheJulia: jfyi https://review.opendev.org/c/openstack/ironic/+/949385/6 apparently needs rebasing to land. As long as it's a trivial rebase ping me and I'll reapply +2A | 16:47 |
TheJulia | heh, wrong channel :) | 16:48 |
opendevreview | Balazs Gibizer proposed openstack/nova stable/2024.1: Add functional reproducer for bug 2102038 https://review.opendev.org/c/openstack/nova/+/952484 | 16:48 |
opendevreview | Balazs Gibizer proposed openstack/nova stable/2024.1: Return HTTP400 for multi spec pci alias if PCI in Placement https://review.opendev.org/c/openstack/nova/+/952485 | 16:48 |
opendevreview | Balazs Gibizer proposed openstack/nova stable/2024.1: Multiple spec per PCI alias limitation https://review.opendev.org/c/openstack/nova/+/952486 | 16:48 |
opendevreview | Balazs Gibizer proposed openstack/nova stable/2024.1: Validated that PCI alias has proper ids https://review.opendev.org/c/openstack/nova/+/952487 | 16:48 |
opendevreview | Balazs Gibizer proposed openstack/nova stable/2024.1: Validate [pci]alias at service startup https://review.opendev.org/c/openstack/nova/+/952488 | 16:48 |
opendevreview | Balazs Gibizer proposed openstack/nova stable/2024.1: Cache [pci]alias parsing https://review.opendev.org/c/openstack/nova/+/952489 | 16:48 |
* JayF has been doing that a lot today | 16:51 | |
TheJulia | no worries | 16:53 |
sean-k-mooney | JayF: so on that | 17:16 |
sean-k-mooney | not inclduing the MTU in the metadta was specificly request by ironic a number of cycles ago | 17:17 |
JayF | I meant to tell you: welcome to the claude-code club :) It was nice to see someone not-me using it :D | 17:17 |
JayF | Sounds like we've corrected a previous mistake, then. | 17:17 |
sean-k-mooney | we do it condtionally | 17:17 |
sean-k-mooney | if the network has dhcp we dont incldue it and allow it to be managed vi dhcp | 17:17 |
JayF | Julia is the expert in this bit moreso than I am :) | 17:18 |
sean-k-mooney | btu if there is no dhcp enabled we includde it for people doing static ip | 17:18 |
sean-k-mooney | ack i was just wonderign why its only coming up now it think we didi it 2 or we release ago | 17:18 |
sean-k-mooney | TheJulia: context was includign the MTU infroamtion in teh metadat made it much harder to go form ml2/ovs to ml2/ovn becacuce that requried reducing the mtu | 17:19 |
sean-k-mooney | so neuton asked us to only set it if there was no dhcp | 17:20 |
sean-k-mooney | JayF: on claude-code ya i decied to pay for it for a year and see where the state of the art is vs local llms ectra | 17:21 |
JayF | sean-k-mooney: so, you want some advice since I've been poking at it for a few weeks? I made a openstack-dev dir, put a claude.md in it, and checked out my other projects under it | 17:21 |
sean-k-mooney | so far im likeing the terminal first approch not that i have done a lot with it | 17:21 |
TheJulia | sean-k-mooney: we've had reports of mtu weirdness and we're seeing a huge increase in not using dhcp so just makes sense to address it. | 17:21 |
JayF | the pycharm ide integration is nice, it uses the jetbrains diff stuff | 17:21 |
sean-k-mooney | JayF: you mean like this https://github.com/SeanMooney/grian-dev | 17:22 |
TheJulia | since, the mismatch between what is known and what an OS can assume otherwise introduces a huge amount of risk | 17:22 |
JayF | if you wanna use mine as a start https://www.irccloud.com/pastebin/sL4RIxrg/CLAUDE.md | 17:22 |
sean-k-mooney | JayF: i also have created https://github.com/SeanMooney/openstack-ai-style-guide | 17:22 |
sean-k-mooney | which i might rename because i want ot evolve that ot be more hten just style | 17:22 |
JayF | okay I think yours wins for quality lol | 17:22 |
JayF | but I will say: the pattern of "start claude in a dir that has all your openstack stuff checked out" has been really nice | 17:23 |
sean-k-mooney | i got claude to help write it | 17:23 |
TheJulia | plus, cases where dhcp may not even be accessible without network data out of the box and where config drive must be relied upon to get started | 17:23 |
JayF | I gave it a sample thing during trying it out, pointing it to a feature that'd require implementation in Ironic + modification of hte nova virt driver, and it did a decent job of navigating it | 17:23 |
JayF | TheJulia: sean-k-mooney: plus the uncomfortable reality that often Ironic knows more about the physical network situation than neutron/nova :( | 17:24 |
sean-k-mooney | TheJulia: so that odd becasue we do still include the mtu info if dncp is disabled on neutron | 17:24 |
sean-k-mooney | TheJulia: if we are not then that a regresion we shoudl fix in nova too | 17:24 |
TheJulia | sean-k-mooney: dhcp only matters if it is reachable out of the box, that is not always true. It is clear cut for VMs, but you can have greater hurdles with physical machines | 17:24 |
sean-k-mooney | TheJulia: ah so this is also related to prot groups and bond/vlan netowrking | 17:25 |
JayF | sean-k-mooney: everything is also related to that :) | 17:25 |
JayF | sean-k-mooney: there's very few people running ironic in the real world not using at least one of those | 17:25 |
sean-k-mooney | well if we know its ironic, which we shoudl be cause it vnic type=baremetal | 17:25 |
sean-k-mooney | we may be able ot make ti work better, | 17:25 |
sean-k-mooney | but if you have already fixed it on the ironic side | 17:26 |
sean-k-mooney | then thats fine too | 17:26 |
JayF | Having Ironic own some of the newtork metadata is a feature we'd need for standalone anyway | 17:26 |
JayF | and gives us more flexibility since (as I said before) we often know more than you all do about the physical world | 17:26 |
sean-k-mooney | ya that makes sense | 17:26 |
TheJulia | Yeah, we're seeing more asks for smoothing that general experience so, just makes sense to spot/address the highly specific items to make things better | 17:26 |
sean-k-mooney | i also think thie idea of ironic haveign the ablity to generate or enrish the config drive is also useful for that case | 17:26 |
TheJulia | So... | 17:27 |
TheJulia | Funny you should mention that! | 17:27 |
JayF | and honestly, the more I think about ^^ (the physical world not always being perfectly modelled in nova) is a ... feature not a bug? The entire benefit of ironic+nova integrated is keeping the experience simple ... and the real world is complex as hell lol | 17:27 |
TheJulia | we've semi-wondered outloud about "should we offer ssh key injection?!" | 17:27 |
sean-k-mooney | well keyparis works with ironic already right | 17:28 |
TheJulia | oh yeah | 17:28 |
sean-k-mooney | but you mean in standalone | 17:28 |
TheJulia | yeah | 17:28 |
sean-k-mooney | i sort of feel like the keypari really shoudl be in keystone | 17:28 |
JayF | we already support it in a supremely roundabout way | 17:28 |
sean-k-mooney | and hten we jsut get it form there or in barbican | 17:28 |
JayF | sean-k-mooney: notably that doesn't help most of our standalone users who use basic auth :) | 17:28 |
TheJulia | sean-k-mooney: agree, and that would make it sort of easier | 17:28 |
sean-k-mooney | btu legacy | 17:28 |
TheJulia | yup | 17:28 |
JayF | you can do arbitrary file injection in a deploy template | 17:28 |
JayF | but that's a lot of crap to do just to get an ssh key in | 17:28 |
TheJulia | yeah | 17:29 |
sean-k-mooney | i mean teh format of the config drive/metadata is pretty standarsied | 17:29 |
sean-k-mooney | so having the ablity for ironic to do that is not a bad thing | 17:29 |
JayF | TheJulia: the killer potential feature hiding under the surface there: Ironic somehow being able to inject troubleshooting-keys into IPA at boot time :D | 17:29 |
sean-k-mooney | woudl we use it in the combined case proably not but maybe | 17:29 |
TheJulia | JayF: I'd have concerns about doing that, but yeah, I've had asks for it in the past | 17:30 |
sean-k-mooney | JayF: cant it od that or do you have to buidl them in | 17:30 |
JayF | TheJulia: I have concerns about the whole thing but I'm assuming we can find a way to have the cake and eat it too :D | 17:30 |
sean-k-mooney | its been a long time since i deployed with bifrost | 17:30 |
TheJulia | So one thing on this entire subject, I'd <3 if nova just shipped us the dicts, but I'd have to double check the constraints and modeling for user input in nova again | 17:30 |
sean-k-mooney | but i remeber sshing into the ipa in the past to debug somthing | 17:30 |
TheJulia | its been years since I've walked that code path | 17:30 |
sean-k-mooney | TheJulia: JayF may rememebr this better then i but i think we just send you json blobs today | 17:31 |
sean-k-mooney | i woudl have to look but i dont think we provide a filesytem but i oculd be wrong | 17:31 |
TheJulia | sean-k-mooney: I don't think y'all actually do | 17:31 |
JayF | I remember nothing :) | 17:31 |
JayF | but we can check! | 17:31 |
TheJulia | I think we get handed an iso9660 file right now | 17:31 |
sean-k-mooney | oh ok | 17:32 |
sean-k-mooney | i mean we can always change that if you come up with a design | 17:32 |
TheJulia | the factory which builds it in the overall virt utils, if memory serves just hands us the file pre-formed | 17:32 |
sean-k-mooney | i might be conflating this with the auto leasee feature | 17:32 |
* TheJulia looked at that relatively recently | 17:32 | |
TheJulia | yeah | 17:32 |
sean-k-mooney | so the reaosn i was quistioning it is we currently store it in memcache | 17:33 |
sean-k-mooney | if you turn that one | 17:33 |
sean-k-mooney | so we ahve it in a dict like serisable datascuture | 17:33 |
TheJulia | Isent there a mechanism on the nova side to do file injection? | 17:34 |
sean-k-mooney | yes its deprecated and ahs been for about a decaade or so | 17:34 |
TheJulia | oh, good | 17:34 |
sean-k-mooney | its called personality files | 17:34 |
sean-k-mooney | you can also pass a user-data cript for cloud init that is what was ment to repalce arbity file injection | 17:35 |
TheJulia | okay, as I mentioned, it has been ages | 17:35 |
TheJulia | in the user-data payload right? | 17:35 |
sean-k-mooney | ya, either by passing somethign like a valut cred and downloading the afctul data on first boot or inline | 17:35 |
sean-k-mooney | it depens on the usecase | 17:36 |
TheJulia | yup, unfortunately I've done stuff like that long ago | 17:36 |
sean-k-mooney | https://github.com/openstack/nova/blob/master/nova/virt/ironic/driver.py#L1108-L1141 | 17:37 |
TheJulia | Yeah, we don't allow file passing today, but if that is the personality files stuff, maybe since its been deprecated so long it might make sense to drop and refactor? | 17:38 |
sean-k-mooney | so righ now we create a tempory file generate the config data gzip it, base64 encode and then decode it and pass that ot ironci | 17:38 |
TheJulia | dunno | 17:38 |
TheJulia | we only permit a pass-in of meta-data, user-data, and network-data via configdrive api on our provision endpoint | 17:39 |
TheJulia | I could have sworn that was structured a little differnetly in nova, but thanks! | 17:40 |
sean-k-mooney | it is | 17:40 |
sean-k-mooney | this is the ironic customtioation | 17:40 |
sean-k-mooney | all the other virt drviers share common code. the ironic driver uses the common code but then modifyes it before sending to to the ironci api | 17:41 |
sean-k-mooney | TheJulia: the ironic driver enriches the network metadta for exmaple https://github.com/openstack/nova/blob/master/nova/virt/ironic/driver.py#L1045-L1106 | 17:41 |
sean-k-mooney | the rest use https://github.com/openstack/nova/blob/master/nova/api/metadata/base.py#L112 | 17:42 |
sean-k-mooney | so we have an objet in memoy thaat can redner subpaths into json for the metadta api https://github.com/openstack/nova/blob/master/nova/api/metadata/base.py#L317 | 17:44 |
sean-k-mooney | or produce the content for the config drive https://github.com/openstack/nova/blob/master/nova/api/metadata/base.py#L590 | 17:45 |
TheJulia | Yeah, for portgroups. we can likely just rip that out and address it locally in ironic at some point | 17:45 |
sean-k-mooney | so it would not take much to jsut add a method to this obejc tthat wil return the data in a singel json dict | 17:46 |
sean-k-mooney | filepath -> file content | 17:46 |
TheJulia | yeah, that would be fairly straight forward | 17:46 |
sean-k-mooney | that acctully what that generator returns already | 17:46 |
sean-k-mooney | its just a mateter of passing it to ironic in a way that would work better for ye | 17:47 |
TheJulia | something for some point down the road | 17:47 |
sean-k-mooney | yep, we can always imrpove things like that if we know about the pain point and someone has time to od the work | 17:50 |
sean-k-mooney | TheJulia: speaning of improment https://review.opendev.org/c/openstack/nova-specs/+/471815 | 17:51 |
sean-k-mooney | i need to get back to that but tha tis aimed at making the data we pass more useful for the vlan trunking case | 17:51 |
sean-k-mooney | although that not nessisarly ironic speicific it shoudl be useful for any dirver the support neutron trunk ports | 17:52 |
TheJulia | Hmmmm | 17:52 |
TheJulia | I'll add that to my list to look at when I don't have a migraine | 17:52 |
TheJulia | Unfortunately, I woke up with one today :( | 17:52 |
sean-k-mooney | that sucks, i often get eystrain headaches or if i forget to take my blodd pressure medication but i fortunate to never had to deal with migraines | 17:53 |
sean-k-mooney | that actully is propsoing inlcudign the mtu info for the vlan sub intereface by the way | 17:55 |
TheJulia | oh good, becuase that would be a logical requirement. | 17:56 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!