| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2018-12-18 | |||
| 19:19:57 | mriedem | which is probably why you're seeing them move sometimes | |
| 19:21:08 | mriedem | which reminds me https://review.openstack.org/#/c/567701/ | |
| 19:30:48 | sean-k-mooney | hehe ill add that to my review list after https://review.openstack.org/#/c/594527/ | |
| 19:33:52 | openstackgerrit | Lee Yarwood proposed openstack/nova master: WIP block_device: Optionally recreate attachments when refreshing connection_info https://review.openstack.org/579004 | |
| 19:35:08 | sean-k-mooney | melwitt: johnthetubaguy jaypipes if ye have time could you take a look at https://review.openstack.org/#/c/591607/11 | |
| 19:43:01 | lyarwood | melwitt / mriedem_afk ; https://review.openstack.org/#/c/618478/ - Would you mind hitting this dead horse again, preferably enough times to kill it if it's a non-starter so I can move on and try fixing this another way, cheers! | |
| 19:44:15 | melwitt | sean-k-mooney: will do | |
| 19:44:32 | melwitt | lyarwood: yes, sorry I didn't get to it yesterday. will do it today | |
| 19:44:48 | lyarwood | hmm killing a dead horse, I think it's time to log off for the day. | |
| 19:44:56 | lyarwood | melwitt: ack np thanks again | |
| 19:51:26 | openstackgerrit | Merged openstack/nova master: Drop request spec migration code https://review.openstack.org/614265 | |
| 20:06:59 | canori01 | If I set an invalid default_schedule_zone, will that prevent the instances from crossing AZ's? | |
| 20:50:07 | mriedem_afk | canori01: it would likely prevent the instance from even booting | |
| 20:51:40 | canori01 | mriedem: The problem I have is I have different storage backends for the boot volume on my different az's. I want the instances to boot in any az, but not move cross-AZ after booting. Is that possible? | |
| 20:54:06 | mriedem | do you want the server to be in the same AZ as the root volume? and if so, do the root volumes have non-default AZs? | |
| 20:54:14 | mriedem | i.e. specific cinder AZs per storage type/backend? | |
| 20:54:51 | mriedem | if so, you might be interested in https://review.openstack.org/#/c/469675/ | |
| 20:55:09 | mriedem | otherwise i'm not aware of a way to restrict a server to an AZ after it's been created and the user didn't request it | |
| 20:55:17 | mriedem | jaypipes: are you? ^ | |
| 20:56:07 | canori01 | The boot volumes are all ephemeral actually. I just want the instance to stay in the az of the hypervisor it orginally spawned in | |
| 20:56:10 | mriedem | you can restrict a server to certain AZs implicitly by pinning the flavor/images to host aggregates | |
| 20:56:47 | canori01 | ah, alright. I think I'll have to go the flavor route | |
| 20:56:56 | mriedem | because otherwise you have latency between the server and the root volume, thus defeating the HPC gains you had by co-locating them on the same host, yes? | |
| 20:58:10 | mriedem | with https://review.openstack.org/#/c/469675/ if you set [cinder]cross_az_attach=False and the user doesn't request an AZ, the compute API would proxy the AZ from the root volume to the server so they are co-located in the same AZ (assuming the cinder volume has a non-default AZ) | |
| 20:58:37 | mriedem | i'm not sure that helps you unless you have an AZ *per host* | |
| 20:59:23 | mriedem | canori01: http://lists.openstack.org/pipermail/openstack-dev/2017-February/thread.html#112847 is also related | |
| 21:13:42 | canori01 | mriedem: Thanks! | |
| 21:15:10 | mriedem | canori01: yw | |
| 22:12:58 | openstackgerrit | Jack Ding proposed openstack/nova-specs master: Flavor Extra Spec and Image Properties Validation https://review.openstack.org/618542 | |
| 22:30:14 | jackding | cfriesen: regarding https://review.openstack.org/#/c/620959, it would be nice to fail earlier at compute node startup, so iterate through list of cpu models and validate each cpu_model + cpu flags using host.compare_cpu()? | |
| 22:31:20 | cfriesen | jackding: I think that would be better than waiting for it to fail with no end-user feedback later on when someone tries to use it. | |
| 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: Remove "API Service Version" upgrade check https://review.openstack.org/615348 | |
| 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 | |
| 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 | mriedem | sean-k-mooney: you might be able to triage this https://bugs.launchpad.net/nova/+bug/1809095 | |
| 13:10:49 | openstack | Launchpad bug 1809095 in OpenStack Compute (nova) "Wrong representor port was unplugged from OVS during cold migration" [Undecided,New] | |
| 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 | 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:24:24 | openstack | Launchpad bug 1809061 in OpenStack Compute (nova) "KeyError when booting multi-stagger-instances" [Undecided,New] | |
| 13:30:54 | mriedem | gibi: replied, thanks i'll mess with that | |
| 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:15 | openstack | Launchpad bug 1809040 in OpenStack Compute (nova) "pci device lost when error in the configuration file " [Undecided,New] | |
| 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 | |