Thursday, 2024-11-07

opendevreviewRajesh Tailor proposed openstack/nova master: Fix instance task_state during shelve  https://review.opendev.org/c/openstack/nova/+/93429406:39
opendevreviewBalazs Gibizer proposed openstack/nova stable/2024.2: Reproduce bug 2085975 in functional  https://review.opendev.org/c/openstack/nova/+/93430108:22
opendevreviewBalazs Gibizer proposed openstack/nova stable/2024.2: Route shared storage RPC to evac dest at startup  https://review.opendev.org/c/openstack/nova/+/93430208:22
opendevreviewBalazs Gibizer proposed openstack/nova stable/2024.1: Reproduce bug 2085975 in functional  https://review.opendev.org/c/openstack/nova/+/93430308:24
opendevreviewBalazs Gibizer proposed openstack/nova stable/2024.1: Route shared storage RPC to evac dest at startup  https://review.opendev.org/c/openstack/nova/+/93430408:24
opendevreviewBalazs Gibizer proposed openstack/nova stable/2023.2: Reproduce bug 2085975 in functional  https://review.opendev.org/c/openstack/nova/+/93430508:26
opendevreviewBalazs Gibizer proposed openstack/nova stable/2023.2: Route shared storage RPC to evac dest at startup  https://review.opendev.org/c/openstack/nova/+/93430608:26
opendevreviewBalazs Gibizer proposed openstack/nova stable/2023.1: Reproduce bug 2085975 in functional  https://review.opendev.org/c/openstack/nova/+/93430808:28
opendevreviewBalazs Gibizer proposed openstack/nova stable/2023.1: Route shared storage RPC to evac dest at startup  https://review.opendev.org/c/openstack/nova/+/93430908:28
chris218Hi guys, how does stuff defined in api/validation/extra_specs translate to virt/libvirt/config? I'm trying to figure out how os_boot_dev is set in LibvirtConfigGuest since it can't be used with boot_order in LibvirtConfigGuestDisk09:57
opendevreviewStephen Finucane proposed openstack/os-vif master: mypy: Add type annotations  https://review.opendev.org/c/openstack/os-vif/+/74516210:26
sean-k-mooneychris218: it mostly does not.  api/validation/extra_specs is just chekcing of the extra spec values are valid at the api level to determin if we shoudl reject the request early when you are defining a flavor and setting the extra specs10:30
sean-k-mooneythe xml generation is entirly seperate10:31
sean-k-mooneyos_boot_dev is not an extra spec or image property, we do not support configing which device is bootable. its either the root disk or the rescue disk10:33
chris218Yea but stuff like hw:boot_menu then translates to os_bootmenu, right?10:34
sean-k-mooneyit can yes, we intentionally do not expose everyting a hypervior can configure10:34
sean-k-mooneychris218: is there a partical reason your interested in modifying the boot dev10:36
chris218I'm still playing with the idea of exposing network booting through some flavor extra spec10:37
sean-k-mooneyah the last time this came up i suggested adding it as a property on the neutron port10:38
chris218I see that libvirt supports <boot order="X"> on interfaces 10:38
sean-k-mooneybasicaly just adding a boot flag to a port10:38
chris218Yea10:39
sean-k-mooneyif you use the boot menu today you can network boot already10:39
sean-k-mooneyneuton can set the tftp server info in the dhcp repsonce on the port too10:39
chris218You'd have to select it manually first though 10:39
sean-k-mooneyyes you would10:39
sean-k-mooneythe thing is nova does not currently suppprot creating a vm wihtout a glance image or a cinder volume. 10:40
sean-k-mooneyso you would have to deal with that ux as well10:40
chris218Last time I asked about it somebody suggested using rescue image with it pxe but downside of this is that unrescuing is kind of inflexible and you can't power off and then unrescue server10:41
sean-k-mooneywe could supprot unrescue to stopped10:43
sean-k-mooneyi belive it curretly returns you to active if the server was active before10:43
*** chuanm9 is now known as chuanm12:21
s3rj1kHi all, would this RFA https://bugs.launchpad.net/nova/+bug/2086867 need an actual spec or specless blueprint is enough?15:33
gibis3rj1k: If it has an API impact, requires DB schema change, or has an upgrade impact then you need a spec. Otherwise it would make sense to propose it as a specless bp and put it on the agenda of some upcoming nova meeting.15:36
gibiand we can discuss it on the meeting if it is simple enough to accept it as specless15:37
s3rj1kgibi: it adds a config option but other than that it's pretty much a small change, can we assume it's specless and in case if it is not I will do spec for it later? After upcoming nova meeting15:40
gibis3rj1k: yeah, that approach make sense15:42
gibilets assume it is specless until the meeting discussion15:43
s3rj1kgibi: great thanks, also when/where is the community meeting will take place?15:44
s3rj1kTuesdays 16:00 UTC (#openstack-nova on OFTC) ?15:47
gibis3rj1k: correct. https://wiki.openstack.org/wiki/Meetings/Nova15:52
gibiyou can add you blueprint to the agenda by editing that page15:53
gibiplease add it to the Open discussion section15:53
gibibauzas: ^^ fyi15:57
s3rj1kgibi: done, thanks for walking me through the formalities16:02
sean-k-mooneyim not sure if this need a code change16:07
sean-k-mooneydont we already have the ablity to specify the migration and livemigration inbound adress16:08
sean-k-mooneyif you set those to an ip then nova will use the ip for scp too i belive16:08
sean-k-mooneyhttps://docs.openstack.org/nova/latest/configuration/config.html#libvirt.live_migration_inbound_addr and https://docs.openstack.org/nova/latest/configuration/config.html#libvirt.migration_inbound_addr16:08
sean-k-mooneys3rj1k: ^16:10
s3rj1ksean-k-mooney: I'll try to verify this before meetup, thanks for heads-up16:40
sean-k-mooneybauzas: can you add https://review.opendev.org/q/topic:%22bug/2074219%22 to your review queue in the morning 17:41
*** haleyb is now known as haleyb|out22:44
*** tosky_ is now known as tosky23:40

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!