Earlier  
Posted Nick Remark
#openstack-nova - 2021-02-09
21:10:28 openstackgerrit Artom Lifshitz proposed openstack/nova master: Track host NUMA topology in PCI manager https://review.opendev.org/c/openstack/nova/+/774149
21:10:28 openstackgerrit Artom Lifshitz proposed openstack/nova master: WIP: pci: implement the `socket` NUMA affinity policy https://review.opendev.org/c/openstack/nova/+/772779
21:34:17 gmann gibi: melwitt stephenfin multiple network fix is merged, you can recheck failure if there is any https://review.opendev.org/c/openstack/tempest/+/770169
21:34:41 gmann let's see if we see any other test failing for that error.
21:36:43 lyarwood \o/
21:46:19 openstackgerrit Ghanshyam proposed openstack/nova master: DNM:try l-c with direct deps https://review.opendev.org/c/openstack/nova/+/772780
22:09:23 melwitt thanks gmann
23:12:24 openstackgerrit Merged openstack/nova master: Add requested_networks field to RequestSpec object https://review.opendev.org/c/openstack/nova/+/749977
#openstack-nova - 2021-02-10
00:36:28 openstackgerrit Ghanshyam proposed openstack/nova master: DNM:try l-c with direct deps https://review.opendev.org/c/openstack/nova/+/772780
00:55:45 openstackgerrit Merged openstack/placement master: policy: Deprecate 'admin_api' rule https://review.opendev.org/c/openstack/placement/+/772334
00:56:08 openstackgerrit Merged openstack/placement master: policy: Add note about keystone's expansion of roles https://review.opendev.org/c/openstack/placement/+/772752
07:14:01 gibi gmann: awesome, thanks
09:15:16 stephenfin Can someone hit this RBAC release note before I shove that context out of my brain? https://review.opendev.org/c/openstack/placement/+/774654/
09:22:46 kashyap lyarwood: Hmm, I'm hitting this one on F32 DevStack - https://bugs.launchpad.net/devstack/+bug/1885198
09:22:47 openstack Launchpad bug 1885198 in devstack "table `broute' is incompatible, use 'nft' tool" [Undecided,New]
09:28:59 openstackgerrit Vlad Gusev proposed openstack/nova stable/stein: Avoid lazy-loading instance.flavor in cold migration https://review.opendev.org/c/openstack/nova/+/774796
09:37:52 lyarwood kashyap: the failure was before that,
09:37:56 lyarwood 2021-02-09 18:08:18.069 | Cloning into '/home/stack/src/cloud/nova'...
09:37:58 lyarwood 2021-02-09 18:11:10.431 | error: RPC failed; curl 18 transfer closed with outstanding read data remaining
09:38:07 kashyap lyarwood: Yeah, just noticed the 'curl' thing; ugh
09:38:17 lyarwood kashyap: why is it cloning into /home/stack/src/cloud/nova?
09:38:37 kashyap lyarwood: Because I used a custom data dir out of habit
09:40:45 lyarwood stephenfin: did you want to add a link as suggested by lbragstad ?
09:41:23 kashyap lyarwood: But it's not the dir that is reason; still looking why the 'curl' failed - perhaps my poor n/w succumbed to a Nova repo clone
09:48:19 stephenfin lyarwood: ah, I hadn't seen that. Looking
09:55:19 gibi stephenfin: regarding the RBAC; the patch looks good to me. What do you want to do with Lance's comment?
09:55:38 stephenfin I'm reworking it now, but perhaps I can use a follow-up?
09:55:50 stephenfin Or not
09:55:52 stephenfin It'll just take me a bit to write this
09:56:00 stephenfin there's a lot of policies to account for :)
09:56:03 stephenfin *there are
09:56:06 gibi stephenfin: do the write up and then ping me, I will push the patch through
09:56:10 stephenfin (y)
09:56:24 gibi thanks
10:07:32 kashyap lyarwood: Now it fails by trying not find a tenant n/w -- http://paste.openstack.org/show/802501/
10:08:39 lyarwood kashyap: how many nics does your vm have?
10:08:58 kashyap lyarwood: Just one; shall I add one more? /me looks at his working older DevStack setup
10:09:30 lyarwood yeah I've always had two, I assume that's why it's unhappy
10:10:27 kashyap lyarwood: Gah. But ... in the name Zeus, I got it working w/ one NIC on an F31 deployment
10:10:33 kashyap Lemme try; sorry for the noise
10:25:27 openstackgerrit Merged openstack/placement stable/ussuri: Fix Placement Doc https://review.opendev.org/c/openstack/placement/+/762607
10:25:34 openstackgerrit Merged openstack/placement stable/train: Fix Placement Doc https://review.opendev.org/c/openstack/placement/+/762608
11:10:49 openstackgerrit Stephen Finucane proposed openstack/placement master: policy: Add releasenote for RBAC work https://review.opendev.org/c/openstack/placement/+/774654
11:10:49 openstackgerrit Stephen Finucane proposed openstack/placement master: Implement secure RBAC for reshaper https://review.opendev.org/c/openstack/placement/+/774827
11:11:01 stephenfin gibi, lyarwood: ^
11:11:16 stephenfin Also spotted a policy that hadn't been updated. Don't know if that was intentional from lbragstad but I suspect not
11:11:24 gibi stephenfin: ack
11:15:50 gibi stephenfin: all looks good to me
11:22:17 sean-k-mooney kashyap: you should aways use at least 2 nics for a devstack setup
11:22:34 sean-k-mooney 1 for ssh/managment and a second for ovs br-ex
11:23:05 sean-k-mooney you can do it with one but devstack will try and move the ip and add it to the ovs bridge
11:23:13 sean-k-mooney which can cause ssh to drop
11:23:36 sean-k-mooney so unless you run devstack in tmux or screen that can break things
11:24:01 sean-k-mooney you used to be able to just not add any interface but they changed something recently
11:24:20 sean-k-mooney havent spend time figuring out what
11:27:20 kashyap sean-k-mooney: I do run in a 'tmux', IIRC
11:27:59 kashyap sean-k-mooney: In the past, I recall testing just fine w/ one network that is _not_ the 'default' libvirt network. I created a separate NAT br to use for OpenStack n/w
11:28:25 sean-k-mooney then it should complete stacking then if you just have one nic
11:29:33 sean-k-mooney devstack pretty much just works if you use it today on ubuntu and centos. i got it to stack on fedroa too but that is less stable generally due to package conflicts
11:29:43 sean-k-mooney e.g. between pip and dnf
11:36:07 kashyap Fedora is the beast I know; I'm gonna skip CentOS. First, helping a different colleague
11:37:15 kashyap sean-k-mooney: Unrelated: BTW, did you know that the "tsx=off" on kernel command-line will _not_ have any effect in certain cases?
11:38:26 sean-k-mooney like when its off already or the kernel does not have it :P
11:38:54 kashyap sean-k-mooney: Off on the kernel command-line; the processor itself has it
11:38:55 sean-k-mooney centos, centos stream and ubunut all work well
11:39:08 kashyap sean-k-mooney: Reading the upstream documentation in the kernel commit, it points out that "tsx=off" will only have effect on newer CPUs that are not vulnerable to MDS (which is indicated by a microcode) -- https://github.com/torvalds/linux/commit/95c5824f75f3
11:39:41 sean-k-mooney kashyap: sure so it turns it off on procees that dont have it disabled by microcode
11:40:01 sean-k-mooney and for older cpus they are assuming you have teh microcode updated
11:40:13 sean-k-mooney which sound resounable
11:40:28 sean-k-mooney if you want it turned off and there is a newer microcode that does that then you should update
11:41:14 kashyap Yeah; what a bloody mess this is
11:42:00 openstackgerrit Stephen Finucane proposed openstack/nova master: Use neutronclient's port binding APIs https://review.opendev.org/c/openstack/nova/+/706295
11:42:48 sean-k-mooney kashyap: i just do this http://paste.openstack.org/show/802510/
11:44:55 kashyap sean-k-mooney: Also, aside: even "tsx=off" does not remove it from /proc/cpuinfo -- and we should not rely on it anyway. Because it only shows what the hardware has.
11:45:27 sean-k-mooney well that is the only thing we can check
11:45:36 sean-k-mooney what would we use instead
11:45:49 sean-k-mooney dmidecode?
11:46:04 sean-k-mooney that the only thing i can think off but i dont think that will help
11:46:24 sean-k-mooney if /proc/cpuinfo is wrong libvirt will be
11:46:59 sean-k-mooney /proc/cpuinfo change when you have hypterthreading disable/enable in the bios not sure about at the kernel level
11:47:09 sean-k-mooney is that the delta
11:47:15 sean-k-mooney bios vs kernel disable
11:48:55 kashyap There is no BIOS switch for it here.
11:49:24 kashyap sean-k-mooney: But /proc/cpuinfo only shows what the hardware itself has -- the kernel parameter 'tsx=off' will _not_ physicallly remove it from /proc/cpuinfo; it just tells the OS not to use it
11:49:53 kashyap So, anyway, I'm jotting down some notes on this to see find out a reliable approach to check
11:50:25 sean-k-mooney kashyap: well that is not always the case
11:50:28 kashyap sean-k-mooney: Also, there _are_ other ways: We should instead check 'virsh domcapabilities' on the compute node to see the effect of 'tsx=off' parameter.
11:50:48 sean-k-mooney kashyap: if you disabel hyperthreading in the bios ht is removed form /proc/cpuinfo
11:51:04 kashyap sean-k-mooney: That's not the same -- TSX has no BIOS option.
11:51:37 sean-k-mooney right thats why i was asking is this a delta between disabeling a feature at the bios vs kernel
11:51:58 sean-k-mooney e.g. /proc/cpuinfo is showing what the bios reports
11:52:16 kashyap Yep
11:53:01 sean-k-mooney oh i have tsx on my laptop
11:53:07 sean-k-mooney or at least hle
11:53:13 sean-k-mooney wht the other one
11:53:58 kashyap 'rtm'
11:54:02 sean-k-mooney ya i have both hle and rtm
11:58:20 sean-k-mooney skylake so it should be enabled by defult which it does
11:58:43 sean-k-mooney kashyap: i tought you said the upstream kernel disabled tsx?
11:59:09 kashyap sean-k-mooney: It did (like I said, but its effect depends on the processor); what kernel are you running?

Earlier   Later