| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2019-07-16 | |||
| 15:03:58 | openstackgerrit | Shilpa Devharakar proposed openstack/nova master: Enable request filter forbidden_aggregates https://review.opendev.org/667952 | |
| 15:22:23 | openstackgerrit | sean mooney proposed openstack/nova stable/stein: [DNM] testing bug/1813789 revert resize events https://review.opendev.org/671079 | |
| 15:22:35 | artom | That was fast | |
| 15:23:28 | sean-k-mooney | it took longer then i planned but i think ^ is right | |
| 15:25:02 | sean-k-mooney | i guess not | |
| 15:26:15 | sean-k-mooney | oh i think im missing a new line | |
| 15:27:22 | sean-k-mooney | and a space | |
| 15:27:52 | openstackgerrit | sean mooney proposed openstack/nova stable/stein: [DNM] testing bug/1813789 revert resize events https://review.opendev.org/671079 | |
| 15:34:48 | sean-k-mooney | ok zull accpeted that so it should report back eventually | |
| 16:34:19 | efried | shilpasd: still around? | |
| 16:34:40 | openstackgerrit | Boris Bobrov proposed openstack/nova master: Provide HW_CPU_X86_AMD_SEV trait when SEV is supported https://review.opendev.org/638680 | |
| 16:34:41 | openstackgerrit | Boris Bobrov proposed openstack/nova master: Extract SEV-specific bits on host detection https://review.opendev.org/636334 | |
| 16:34:41 | openstackgerrit | Boris Bobrov proposed openstack/nova master: Add extra spec parameter and image property for memory encryption https://review.opendev.org/664420 | |
| 16:34:42 | openstackgerrit | Boris Bobrov proposed openstack/nova master: Apply SEV-specific guest config when SEV is required https://review.opendev.org/644565 | |
| 16:34:42 | openstackgerrit | Boris Bobrov proposed openstack/nova master: Add |
|
| 16:34:43 | openstackgerrit | Boris Bobrov proposed openstack/nova master: Enable booting of libvirt guests with AMD SEV memory encryption https://review.opendev.org/666616 | |
| 16:35:59 | efried | shilpasd: I'm going to edit the commit message of https://review.opendev.org/#/c/671075 real quick so I can be +2 on the whole series. | |
| 16:37:03 | openstackgerrit | Eric Fried proposed openstack/nova master: Add a new request filter to forbidden aggregates https://review.opendev.org/671075 | |
| 16:37:36 | openstackgerrit | Eric Fried proposed openstack/nova master: Enable request filter forbidden_aggregates https://review.opendev.org/667952 | |
| 16:38:20 | efried | dansmith: I'm +2 all the way up on the forbidden aggs series ^ | |
| 16:40:01 | efried | the biggish final patch is mostly doc | |
| 16:44:07 | openstackgerrit | Raubvogel proposed openstack/nova master: Author: Mauricio Tavares |
|
| 16:45:53 | openstackgerrit | Raubvogel proposed openstack/nova master: Author: Mauricio Tavares |
|
| 17:03:04 | openstackgerrit | Boris Bobrov proposed openstack/nova master: Enable booting of libvirt guests with AMD SEV memory encryption https://review.opendev.org/666616 | |
| 17:03:04 | openstackgerrit | Boris Bobrov proposed openstack/nova master: Apply SEV-specific guest config when SEV is required https://review.opendev.org/644565 | |
| 17:20:06 | efried | sean-k-mooney: you around? | |
| 17:20:49 | sean-k-mooney | kind of | |
| 17:20:54 | efried | I try and I try, but I just can't follow this stuff. Would you please review https://review.opendev.org/#/c/670588/ for me? I'll proxy your +1. | |
| 17:21:06 | sean-k-mooney | im wait on food to be delivered in 20 mins or so | |
| 17:21:18 | efried | I think it was your suggestion anyway from the subsequent patch | |
| 17:21:54 | sean-k-mooney | oh right. in the non ovs case we added a noop pluging to os vif to handel generic vhost-user plugging | |
| 17:22:07 | sean-k-mooney | and for the ovs case its already handeled by os-vif | |
| 17:23:09 | efried | yeah, see, I can read those words, but I've never been able to follow the code around that area | |
| 17:23:11 | sean-k-mooney | so those functions should never get called. but ill trace through the code and confim | |
| 17:23:16 | efried | thanks | |
| 17:24:27 | sean-k-mooney | well it used to do an indrect function call by appending the vif type to a prefix and using gettr to look up the function | |
| 17:24:39 | sean-k-mooney | so it was not exactly the simplest code | |
| 17:25:27 | sean-k-mooney | that actully predates me working on openstack but i never really understood why we did it that way | |
| 17:25:30 | efried | yeah, the getattr removal is in the subsequent patch, and I was able to follow that. But it's also dependent on this being right. | |
| 17:26:20 | sean-k-mooney | this code path is for netwroking-vpp or snabb switch | |
| 17:26:41 | sean-k-mooney | its very very rarly used but we still dont want to break people that use it | |
| 17:37:07 | openstackgerrit | Merged openstack/nova master: Defaults missing group_policy to 'none' https://review.opendev.org/657796 | |
| 17:53:27 | sean-k-mooney | efried: done. i have put a walk through of how the dead code would have been called in the past but it is never used after https://review.opendev.org/#/q/Ifab3006454708ab290b93f02d82b794c334c3946 was merged last cycle | |
| 17:53:44 | efried | thanks sean-k-mooney | |
| 17:54:31 | sean-k-mooney | no worries dinner just arrived so ill be away for a while. i might be back in an hour or two | |
| 18:01:06 | spatel | sean-k-mooney: yt? | |
| 18:01:49 | spatel | virsh list command showing instance-<uuid> is there anyway it can show hostname of instance | |
| 18:03:29 | spatel | In google people saying "virsh domhostname <domain>" but what is domain going to be? | |
| 18:03:51 | spatel | also i don't think kvm support that | |
| 18:20:18 | donnyd | Was there still interest in the NUMA for fortnebula? | |
| 18:20:49 | donnyd | LOL... interest in NUMA topologies | |
| 18:21:35 | donnyd | I have things to a more stable state with decent performance, so now I can move forward | |
| 18:25:31 | openstackgerrit | Mauricio Tavares proposed openstack/nova master: Increases the level of detail provided by the debug messages in pci_passthrough_filter.py. https://review.opendev.org/671106 | |
| 18:30:41 | efried | artom, sean-k-mooney: ---^ ? | |
| 18:39:58 | artom | donnyd, yes please, I would like 1 the NUMA ;) | |
| 18:40:24 | donnyd | LOL +2 | |
| 18:40:27 | artom | For serious though, yeah, flavors with >= 2 NUMA nodes would be awesome | |
| 18:40:34 | donnyd | you get 2 numas artom | |
| 18:41:26 | donnyd | I am not deep in the zuul or nodepool code, so how does the test work. Can you ask for a specific flavor? | |
| 18:41:53 | donnyd | I need a way to stay compatible with the other jobs | |
| 18:41:59 | artom | efried, I don't even know where to start with that. I guess look at the logic before drowning them with the formatting and whitespace nits? | |
| 18:42:24 | artom | donnyd, that's not my strong suite, I'm afraid | |
| 18:42:55 | efried | artom: I was pointing at donnyd, not at Mauricio's patch | |
| 18:43:06 | artom | efried, oh, hah | |
| 18:43:38 | efried | my ---^ was an attempt to go around the corner | |
| 18:44:16 | artom | donnyd, sean-k-mooney would most likely know, though I hate to pile even more things on this plate | |
| 18:44:31 | artom | Or ask in -infra? Is that good advice? | |
| 18:46:39 | donnyd | 2:44 PM <clarkb> we can do provider specific flavors but generally avoid that to handle cloud outages | |
| 18:46:39 | donnyd | 2:44 PM <clarkb> there isnt | |
| 19:04:21 | donnyd | artom: I will have to learn how to setup NUMA aware flavors, (unless someone knows off the top of their head) and it looks like we have a path forward | |
| 19:05:59 | artom | donnyd, it's kinda tedious, but not super hard: https://docs.openstack.org/nova/latest/user/flavors.html | |
| 19:06:05 | artom | Scroll down to CPU topology | |
| 19:06:24 | artom | Sorry, NUMA topology | |
| 19:06:34 | donnyd | Ok, I will take a look | |
| 19:07:08 | artom | Actually both | |
| 19:07:58 | artom | hw:cpu_ controls the guest topology, hw:numa_ controls how it maps onto host hardware | |
| 19:11:30 | openstackgerrit | Merged openstack/nova master: Use Adapter global_request_id kwarg https://review.opendev.org/670907 | |
| 19:58:44 | prometheanfire | is one of the use cases for nova to run 1-3 compute nodes in 3-4 DCs across the world? (via host aggregates and AZs) | |
| 19:59:02 | openstackgerrit | Eric Fried proposed openstack/nova master: DB API changes to get non-matching aggregates from metadata https://review.opendev.org/671074 | |
| 19:59:02 | openstackgerrit | Eric Fried proposed openstack/nova master: Nova object changes for forbidden aggregates request filter https://review.opendev.org/671072 | |
| 19:59:03 | openstackgerrit | Eric Fried proposed openstack/nova master: Enable request filter forbidden_aggregates https://review.opendev.org/667952 | |
| 19:59:03 | openstackgerrit | Eric Fried proposed openstack/nova master: Add a new request filter to forbidden aggregates https://review.opendev.org/671075 | |
| 20:00:10 | efried | prometheanfire: What's this in reference to? | |
| 20:00:53 | prometheanfire | sometihng I may be doing soon | |
| 20:01:09 | prometheanfire | cross continental rabbit could be fun | |
| 20:01:34 | prometheanfire | just not sure if it's an intended (supported) use case for nova | |
| 20:03:34 | openstackgerrit | Merged openstack/nova master: vif: Remove 'plug_vhostuser', 'unplug_vhostuser' https://review.opendev.org/670588 | |
| 20:06:09 | efried | ohh, okay. So you're asking if you can make a setup like that? | |
| 20:06:22 | efried | prometheanfire: in a single cell? | |
| 20:06:39 | efried | Cause I would imagine you can surely do a multi-cell that way | |
| 20:06:50 | efried | donnyd: do you know about this? | |
| 20:07:19 | prometheanfire | ya, could do it multi-cell I suppose, single cell may be nice management wise though | |
| 20:07:48 | efried | prometheanfire: isn't that how zuul is set up? | |
| 20:07:59 | prometheanfire | the main question I have is if I'll need to run non-compute stuff at each location or not (I'd rather it just be nova-compute and neutron agent type stuff) | |
| 20:08:00 | donnyd | well if you look at any of the big clouds out there, it would appear they try to stay away from this type of thing | |
| 20:08:01 | efried | running a nodepool across a dozen different locations | |
| 20:08:46 | donnyd | Control plane / internal stuff usually stays on the same l2//3 networks | |
| 20:08:54 | efried | You might have to run a cell conductor at each site. I would think your db performance would be crap if you didn't. | |
| 20:09:03 | donnyd | But I am not entirely sure what the ask is | |
| 20:09:56 | prometheanfire | how to best build a cloud that spans multiple DCs, but it still small beans (a couple hosts per location) | |