Earlier  
Posted Nick Remark
#openstack-nova - 2026-05-25
13:58:03 sean-k-mooney ok its checked in the bug config
13:58:15 sean-k-mooney let me uncheck it quickly until we have time to dicuss it
13:58:43 sean-k-mooney oh os its actully confire to only expire incomplete bugs currently
13:58:48 sean-k-mooney not any open bug
13:59:24 sean-k-mooney fungi: not sure if you can see https://launchpad.net/nova/+configure-bugtracker
13:59:38 sean-k-mooney i just uncheck the Expire "Incomplete" bug reports when they become inactive
13:59:39 fungi advanced search for nova bugs in expired state sorted by number turns up one that got expired on the 13th too
13:59:40 sean-k-mooney box
14:00:15 sean-k-mooney the nova irc meeting is in a few hours let just add this to opendicuss
14:00:22 sean-k-mooney and we can fiture out if we want it on or off
14:00:44 sean-k-mooney there doesnet seam to be any indication fo what "becomes inactive" actully means
14:00:50 sean-k-mooney i.e. is it weeks or years
14:00:53 fungi i don't have access to that by default (though i could get to it by adding myself to the right group) so will take your word for it
14:02:21 sean-k-mooney its set for cybrog and watcher as well
14:02:24 fungi looks like it's 60 days with no activity while in "incomplete" state, at least (not sure about what other states also trigger it, sll the examples i found so far are for previously-incomplete)
14:02:27 sean-k-mooney this might be on by default
14:03:21 fungi okay, so it might be that it's on for a bunch of projects and i've just somehow not noticed it before today
14:03:24 sean-k-mooney if its resticted to the incompelte state i might be ok with this on. i dont like exiring bugs in general but we only use incomplete when we are missing info
14:04:02 fungi yeah, i mean the example i linked above was perfectly fine to expire, consensus seemed to be that it was likely invalid anyway
14:05:24 fungi anyway, not an emergency, i just wanted to make sure behavior hadn't changed somewhere, but looke like it may have been doing this all along
14:08:29 sean-k-mooney it might have
14:08:44 sean-k-mooney i.e. i dont recall seeing this in a very very long time
14:08:53 sean-k-mooney in anycase added to opendicuss https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
14:09:32 sean-k-mooney fungi: https://bugs.launchpad.net/nova/+bug/2142042 was invlide by the way and not a secuirty bug
14:09:51 sean-k-mooney we only supprot pci passhtough vai the pci_alias
14:10:17 sean-k-mooney we have never allowed attaching pci devices via the resouce: syntax
14:10:41 sean-k-mooney the only thing that ever allwoe dthat was generic mdevs and i have alwasy held that was a mistake
14:11:20 fungi yeah, that's why i say it was fine that it expired
14:11:49 sean-k-mooney im going to leave a comment and mark it invlaid
15:15:42 opendevreview Dominik proposed openstack/nova master: NUMA Topology with Resource Providers: Object changes https://review.opendev.org/c/openstack/nova/+/978209
15:40:15 opendevreview Thibaut Démaret proposed openstack/nova master: libvirt: add disk rotation_rate support for local disks https://review.opendev.org/c/openstack/nova/+/979693
16:07:20 opendevreview Arnaud Morin proposed openstack/nova master: Set correct link for configuration file format https://review.opendev.org/c/openstack/nova/+/989981
17:18:56 jayaanand hi All, i created blueprint as per PTG discussion https://blueprints.launchpad.net/nova/+spec/raw-image-flexclone-optimization. Please review
17:20:06 sean-k-mooney so you have create a bluepitn with the conte of a spec as its decription
17:20:17 sean-k-mooney but you actully need to submit that spec as a review to the nova-specs repo
17:20:29 sean-k-mooney the describe in the plurpint shoudl jsut be the intorduction fo the spec
17:21:08 sean-k-mooney so you need to clone https://github.com/openstack/nova-specs
17:21:25 sean-k-mooney and then add your spec in teh approved folder for this cycle 2026.2
17:21:35 sean-k-mooney and then submit it for review via gerrit
17:22:11 sean-k-mooney you can use the contet you currently have in teh blueprint. by convention the file name shoudl mattch the blurpint name with .rst
17:22:22 sean-k-mooney so raw-image-flexclone-optimization.rst
17:22:35 sean-k-mooney we have some tooling that use that to forralate the spec file and the blueprint
17:24:00 sean-k-mooney jayaanand: just siming it im not sure that the current direction is correct. i.e. wrapping flat with now new config value for NetAppFlexClone
17:24:13 sean-k-mooney well hte netap variant
17:26:26 sean-k-mooney i think images_type=netapp_flexcloen give you are propsoing addign a [netapp_flexclone] config section woudl be a much more natural fit
17:27:35 sean-k-mooney with all that said i dont think there was an general agreement that we shoudl add a vendor sepcifc image_type backend to nova
17:28:02 sean-k-mooney so you will have to build a concentio that that shoudl be doen before we go into the details of how
17:29:13 sean-k-mooney jayaanand: the vendor specific point we raised cant be sidespte by adding a spereat vendor specific cofnig option like netapp_flexclone_enabled = false
17:32:13 sean-k-mooney anyeya i can take a looks once its actully submited for review as a spec but i likely cant commit to reviewign this this cycle so you will need to find concnsoue to build this functionalty in general.
18:45:59 opendevreview Merged openstack/nova master: Set correct link for configuration file format https://review.opendev.org/c/openstack/nova/+/989981
18:46:14 opendevreview Merged openstack/nova master: reno: Update master for unmaintained/2024.1 https://review.opendev.org/c/openstack/nova/+/965491
20:04:22 opendevreview Goutham Pacha Ravi proposed openstack/nova master: Support cold migration with virtiofs shares https://review.opendev.org/c/openstack/nova/+/989633
#openstack-nova - 2026-05-26
04:34:46 opendevreview Goutham Pacha Ravi proposed openstack/nova master: Support cold migration with virtiofs shares https://review.opendev.org/c/openstack/nova/+/989633
06:29:01 opendevreview Goutham Pacha Ravi proposed openstack/nova master: Support cold migration with virtiofs shares https://review.opendev.org/c/openstack/nova/+/989633
10:21:09 opendevreview Stephen Finucane proposed openstack/nova master: Use static pages for eol release release notes https://review.opendev.org/c/openstack/nova/+/989210
10:21:10 opendevreview Stephen Finucane proposed openstack/nova master: docs: Speed up release notes builds https://review.opendev.org/c/openstack/nova/+/989212
10:21:10 opendevreview Stephen Finucane proposed openstack/nova master: Use static pages for eom release release notes https://review.opendev.org/c/openstack/nova/+/989211
12:21:42 cw0306-lee[m] My question is, is nova's policy still same? Or is it able to suggest this subject again?
12:21:42 cw0306-lee[m] https://blueprints.launchpad.net/nova/+spec/selecting-subnet-when-creating-vm
12:21:42 cw0306-lee[m] Hi, nova team! I want to create blueprint about support subnet selection during vm create. However, it rejected in 2015.
12:43:22 opendevreview Merged openstack/nova master: Fix live migration with pinned VM and iothreads https://review.opendev.org/c/openstack/nova/+/988774
12:51:11 opendevreview Balazs Gibizer proposed openstack/nova stable/2026.1: Reproduce bug/2152697 https://review.opendev.org/c/openstack/nova/+/990096
12:51:12 opendevreview Balazs Gibizer proposed openstack/nova stable/2026.1: Fix live migration with pinned VM and iothreads https://review.opendev.org/c/openstack/nova/+/990097
13:24:40 sean-k-mooney cw0306-lee[m]: so nova does not want to add new networkign proxy apis in general
13:24:46 sean-k-mooney but the feature your askign for i think already exists
13:25:24 sean-k-mooney https://docs.openstack.org/api-ref/compute/#id11
13:26:24 sean-k-mooney i think we can pass the subnet when we do --nic in osc
13:27:49 sean-k-mooney ok not quite
13:27:51 sean-k-mooney https://docs.openstack.org/python-openstackclient/latest/cli/command-objects/server.html#cmdoption-openstack-server-create-nic
13:28:02 sean-k-mooney you can pass teh ip to use but not the subnet
13:28:31 sean-k-mooney cw0306-lee[m]: so you cant have neutron allcoate it form a subnot
13:29:07 sean-k-mooney basucly our current stance is if you need anything behod a basic prot on a netork you shoudl create the port in neutron first and pass in the port uuid when creating the vm
13:31:10 sean-k-mooney cw0306-lee[m]: basiclly this falls under https://docs.openstack.org/nova/latest/contributor/project-scope.html#no-more-api-proxies
13:40:36 cw0306-lee[m] sean-k-mooney @_oftc_sean-k-mooney:matrix.org: Thank you for your kind reply. I asked this question because blueprint closed long time ago, so if there is a possibility of adding the option again. Thank you!
13:42:11 sean-k-mooney it was closed because it was nto in line with the future direction of the project. that has not really changed. we have dicussed this on an off a few times but i think the sentiment still remains that we would prefer not to
13:50:08 cw0306-lee[m] Is this blueprint need spec? And when can i talk this with?
13:50:08 cw0306-lee[m] https://blueprints.launchpad.net/nova/+spec/reduce-build-fail-time-base
13:50:08 cw0306-lee[m] Thank you! I have one more question that i made blueprint in 2025-1.
13:53:54 sean-k-mooney cw0306-lee[m]: that could be dicsused in a nova irc meeting as perhaps a specless blueprint
13:54:17 sean-k-mooney the build failure count is jsut use by the weigher to avoid the host
13:54:42 sean-k-mooney having it decay over time is proably a reasonabel optimisation
13:56:07 sean-k-mooney im not sure about doing it in the update_available_resouce perodic but perhaps.
13:56:30 sean-k-mooney i woudl be more incliend to have it be its own persodic and opt into ti by setting the time interval in the config
13:58:33 cw0306-lee[m] Then, can we talk about this on next irc meeting(6/1)? Then I'll add this in agenda.
13:59:29 sean-k-mooney ack
13:59:48 cw0306-lee[m] Thank you very much!
15:13:49 melwitt I haven't looked in more detail yet but fyi looks like we have nova-grenade-multinode failing on stable/2025.1 due to a conflict trying install sphinx https://zuul.opendev.org/t/openstack/build/b433e624b0304542a7acd99c735a051c cc elodilles
15:18:31 elodilles melwitt: sorry for not advertising it earlier here on IRC, but stable/2025.2 and stable/2025.1 gates are blocked :( some details: https://etherpad.opendev.org/p/nova-stable-branch-ci
15:19:00 melwitt elodilles: thanks, sorry I missed it!
15:19:26 elodilles melwitt: grenade on stable/2025.1 could be fixed with this: https://review.opendev.org/c/openstack/grenade/+/989580
15:20:18 elodilles at least, it worked for grenade last week o:) (unfortunately, the skip-level grenade needs another workaround for the patch to merge)
15:21:12 elodilles stable/2025.2 was blocked by the skip-level grenade as well. i hope the fix could work there too
15:21:17 elodilles but :(
15:21:32 elodilles a tempest patch has merged recently :/
15:21:37 elodilles that causes another error
15:22:00 elodilles (move from setup.cfg to pyproject.toml)
15:22:27 elodilles and the above mentioned grenade jobs uses ubuntu-jammy nodeset
15:23:20 elodilles on which tox drops error due to old pbr/setuptools because of the new pyproject.toml setup :/
15:23:33 melwitt @_@ ok
15:24:31 elodilles so now i'm testing a couple of workarounds with this patch: https://review.opendev.org/c/openstack/grenade/+/989786

Earlier   Later