Earlier  
Posted Nick Remark
#openstack-nova - 2018-12-18
22:32:03 jackding cfriesen: make sense, I will modify the spec.
23:03:01 openstackgerrit Jack Ding proposed openstack/nova-specs master: Select cpu model from a list of cpu models https://review.openstack.org/620959
23:04:23 jackding cfriesen: new patchset uploaded
23:07:45 openstackgerrit Jack Ding proposed openstack/nova-specs master: Flavor Extra Spec and Image Properties Validation https://review.openstack.org/618542
23:09:31 jackding jaypipes: could you revisit https://review.openstack.org/#/c/618542/ see if your questions are answered? Thanks,
23:28:36 jackding cfriesen: You mean host.compute_cpu() is only for libvirt driver or do you mean the entire spec only applies to libvirt driver?
#openstack-nova - 2018-12-19
00:19:28 openstackgerrit Hongbin Lu proposed openstack/nova-specs master: [WIP] Support scheduling VM's NICs to different PFs https://review.openstack.org/626055
00:24:34 openstackgerrit sean mooney proposed openstack/nova-specs master: Add spec for sriov live migration https://review.openstack.org/605116
00:54:27 openstackgerrit Matt Riedemann proposed openstack/nova master: Drop old service version check compat from _delete_while_booting https://review.openstack.org/623589
00:54:27 openstackgerrit Matt Riedemann proposed openstack/nova master: Remove "API Service Version" upgrade check https://review.openstack.org/615348
01:47:07 openstackgerrit zhaodan7597 proposed openstack/nova master: fix a bug, when creating a vmware instance from a volume,and it goes to error state, the volume still in "in use" state. https://review.openstack.org/571112
01:54:51 openstackgerrit zhaodan7597 proposed openstack/nova master: Bug description: when creating a vmware instance from a volume is failed, vm goes to error state, the volume is in "in use" state, and after deleting the vm, the state of the volume is still in "in use" and can't be deleted. https://review.openstack.org/571112
01:59:29 openstackgerrit Merged openstack/nova master: Make [cinder]/catalog_info no longer require a service_name https://review.openstack.org/620738
02:15:06 openstackgerrit zhaodan7597 proposed openstack/nova master: Catch the not found exception when power off an bfv wmware instance failed https://review.openstack.org/571112
03:30:03 openstackgerrit zhaodan7597 proposed openstack/nova master: Catch the not found exception when powering off a wmware instance https://review.openstack.org/571112
03:46:30 openstackgerrit Brin Zhang proposed openstack/nova-specs master: Support admin to specify project to create snapshot https://review.openstack.org/616843
04:13:47 gmann gibi: i replied on this, please check if that make sense - https://review.openstack.org/#/c/625002/
04:34:58 openstackgerrit Ghanshyam Mann proposed openstack/nova master: Use renamed template 'integrated-gate-py3' https://review.openstack.org/626088
06:05:22 openstackgerrit zhaodan7597 proposed openstack/nova master: Catch the not found exception when powering off a wmware instance https://review.openstack.org/626095
06:08:08 openstackgerrit zhaodan7597 proposed openstack/nova master: Catch the not found exception when powering off a wmware instance https://review.openstack.org/626095
06:10:48 openstackgerrit zhaodan7597 proposed openstack/nova master: Catch the not found exception when powering off a wmware instance https://review.openstack.org/571112
06:18:56 openstackgerrit Takashi NATSUME proposed openstack/nova master: Adds view builders for keypairs controller https://review.openstack.org/347289
06:19:31 openstackgerrit Takashi NATSUME proposed openstack/nova master: Fix 500 error while passing 4-byte unicode data https://review.openstack.org/407514
07:31:14 openstackgerrit zhaodan7597 proposed openstack/nova master: Catch the not found exception when powering off a vmware instance https://review.openstack.org/571112
08:05:06 openstackgerrit Yongli He proposed openstack/nova-specs master: add 'show-server-group' spec https://review.openstack.org/612255
08:12:20 openstackgerrit Martin Midolesov proposed openstack/nova master: vmware:add support for the hw_video_ram image property https://review.openstack.org/564193
08:12:52 openstackgerrit wingwj proposed openstack/nova master: Fix a broken-link in nova doc https://review.openstack.org/626110
08:22:51 openstackgerrit wingwj proposed openstack/nova master: Fix a broken-link in nova doc https://review.openstack.org/626113
08:26:51 openstackgerrit wingwj proposed openstack/nova master: Fix a broken-link in nova doc https://review.openstack.org/626110
08:43:36 openstackgerrit Merged openstack/nova master: Remove legacy request spec compat code from API https://review.openstack.org/614309
08:46:02 gibi gmann: hi! regarding https://review.openstack.org/#/c/625002/ do we assume that every dependency related code change are fully covered with unit and functional test?
09:16:04 gibi gmann: left a reply in https://review.openstack.org/#/c/625002/
13:10:49 openstack Launchpad bug 1809095 in OpenStack Compute (nova) "Wrong representor port was unplugged from OVS during cold migration" [Undecided,New]
13:10:49 mriedem sean-k-mooney: you might be able to triage this https://bugs.launchpad.net/nova/+bug/1809095
13:11:53 sean-k-mooney ill take a look. form the title it sounds like its related to os-vif and mellonox hardware offload
13:22:56 gibi mriedem: I left a hint about the serialization problem in https://review.openstack.org/#/c/582417/6/nova/compute/rpcapi.py@736
13:24:24 openstack Launchpad bug 1809061 in OpenStack Compute (nova) "KeyError when booting multi-stagger-instances" [Undecided,New]
13:24:24 mriedem melwitt: this sounds very similar to a thing you fixed about caching HostState values globally per scheduler worker https://bugs.launchpad.net/nova/+bug/1809061
13:30:54 mriedem gibi: replied, thanks i'll mess with that
13:35:15 openstack Launchpad bug 1809040 in OpenStack Compute (nova) "pci device lost when error in the configuration file " [Undecided,New]
13:35:15 mriedem sean-k-mooney: stephenfin: you may also enjoy https://bugs.launchpad.net/nova/+bug/1809040 but i'm not really sure what to do about it,
13:35:27 mriedem basically, they goofed their pci passthrough whitelist config during an upgrade,
13:35:42 mriedem and lost all the pci device inventory that was previously discovered and assigned to a given vm once they rebooted the vm
13:36:58 mriedem maybe they can cold migrate their way out of it
13:37:06 mriedem pci devices are only assigned during claims right?
13:39:13 mriedem frickler: you should have your queens/pike releases now
13:39:41 stephenfin mriedem: Just finishing up a rather lengthy email. I'll take a look soon as that's done
13:39:56 stephenfin mriedem: But yeah, only during claims to the best of my recollection
13:41:26 frickler mriedem: yes, I saw the notification on the bug report, thank you
13:44:43 mgariepy ha, hello :)
13:45:54 mgariepy the cold migrate might work guess i don't tend to migrate vms with pci passthrough tho.. and resize isn't really an option since it allow you to select a new flavor and not old same one.
13:46:39 mriedem cold migrate is just resize without a new flavor
13:47:39 mriedem the pci passthrough whitelist / framework is a fickle beast
13:47:57 mriedem given the "inventory" in nova is the intersection of what's in the config and what's on the host
13:50:13 mgariepy my use case is more like: 1 vm / host with all the ressources, (pci passthrough ram and cpu), resize doesn't really work in that case.
13:51:32 mgariepy i noticed that the pci devices are re-created in the db, how is the link made to the computes ?
13:51:55 mgariepy pci passthrough is fun. it gave me quite a few issues lately.
13:52:22 mriedem so you can't cold migrate the vm because ther are no other available hosts with the same pci device?
13:52:26 mriedem *there
13:52:35 mgariepy no there isn't
13:54:16 mriedem hmm, i wonder if you could trick the resize to same host though by creating a private duplicate flavor with some bogus extra spec like foo=bar
13:54:34 mgariepy in nova.pci_devices why isn't it link to the compute node id ?
13:54:40 mriedem you'd have to of course enable this option https://docs.openstack.org/nova/latest/configuration/config.html#DEFAULT.allow_resize_to_same_host
13:54:52 mgariepy when recreating the device
13:55:26 mriedem i'm really not the person that can answer low level questions about how the pci device code works within nova,
13:55:36 mriedem hopefully sean-k-mooney and/or stephenfin could help there
13:56:01 mriedem iow i have to look all of the code up every time i need to investigate it
13:56:28 mriedem the PciDevice object does have a compute_node_id field
13:56:30 sean-k-mooney mriedem: sorry was reading bug. what is the context
13:56:53 mgariepy as far as i'm concern, if i have a compute node, and the devices is the same in the same pci address, it should be ""undeleted"" instead of created again.
13:57:31 openstack Launchpad bug 1809040 in OpenStack Compute (nova) "pci device lost when error in the configuration file " [Undecided,New]
13:57:31 mgariepy sean-k-mooney, https://bugs.launchpad.net/nova/+bug/1809040
13:58:14 mgariepy sean-k-mooney, in nova.pci_devices why isn't it link to the compute node id ?
13:58:45 mgariepy https://paste.ubuntu.com/p/Pn76QVmwqr/
13:59:19 mriedem they are linked to compute node 23 there
13:59:34 sean-k-mooney mgariepy: they are
14:00:09 mgariepy yep, but the issue is that if i remove the passthrough config from nova.conf, it get the deleted_at but if I re-add it it create new one.
14:00:17 mgariepy in the same host, same address. etc..
14:00:36 sean-k-mooney yes
14:00:41 sean-k-mooney that is expected
14:01:29 sean-k-mooney the id filed is an auto incremting filed and the uuid is randomly generated if the device id not found in the database
14:01:34 mgariepy wouldn't be better to re-use the old entry if all the info matches?
14:02:06 stephenfin mgariepy: For what it's worth, that also confused me but it is expected
14:02:06 sean-k-mooney mgariepy: if we have already deleted it no
14:02:23 mgariepy the 2 first are the ""original"" one, then the 2 other are the new one created.
14:02:31 mriedem it seems that things break down on reboot here https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L5350
14:02:42 mriedem pci_manager.get_instance_pci_devs(instance) must be returning []
14:02:45 sean-k-mooney mgariepy: we do it this way because you could have pull the card and install a different one in the same slot
14:02:59 mgariepy yes.
14:03:24 mgariepy then the product id would have changed
14:03:26 sean-k-mooney that could break the guest if we jsut blindly reused it
14:03:29 mriedem and i think that's probably [] because i think instance.pci_devices is set during a resource claim, which doesn't happen on reboot
14:03:42 sean-k-mooney no the product ids could be the same but if they were nics
14:03:52 sean-k-mooney that were usidn for pf passthouhg the mac woudl have changed
14:03:58 openstackgerrit Merged openstack/nova master: Fix a broken-link in nova doc https://review.openstack.org/626110
14:04:10 mgariepy yes for a nic, that's true.
14:04:25 mgariepy that's my testbed , the other system i have uses graphic card :D
14:04:26 mgariepy haha
14:04:41 sean-k-mooney event for gpus we only the vendor id and produc id are recored
14:04:47 sean-k-mooney not the subvend id

Earlier   Later