Earlier  
Posted Nick Remark
#openstack-nova - 2018-03-15
17:27:20 dansmith tssurya: if you survey some other backports you'll see some "Conflicts:" examples
17:27:20 tssurya I didn't know if it was an allowed practice
17:27:38 tssurya dansmith: thanks will look them up
17:27:49 dansmith tssurya: example: https://review.openstack.org/#/c/540145/
17:28:16 jaypipes claudiub|2: added review note.
17:28:25 tssurya dansmith: perfect thank you!
17:28:31 claudiub|2 \o/ thanks. :D
17:56:23 cfriesen are there any known issues with nic tagging in Newton?
17:57:07 stephenfin artom: ^ ?
17:57:09 cfriesen I'm failing schema validation, wondering if it's something we screwed up but I don't see us changing anything in that area.
17:57:19 cfriesen (by "we" I mean my organization)
17:58:12 cdent jaypipes: you might enjoy this buglet: https://bugs.launchpad.net/nova/+bug/1756151
17:58:13 openstack Launchpad bug 1756151 in OpenStack Compute (nova) "placement os-traits sync checked every request" [Low,Triaged]
18:03:02 cfriesen stephenfin: artom: ah yes, microversion 2.37 broke tagging, and 2.42 added it back in.
18:13:15 mriedem melwitt: have you heard anything new about a project update session at the summit?
18:15:09 melwitt mriedem: no, I'm gonna ask anne about it
18:15:15 mriedem nova project update doesn't fall under the category of CI/CD, HPC or EDGE so probably not
18:15:19 mriedem i replied to the ML thread
18:15:25 mriedem quite dickishly
18:16:13 melwitt heh. I tried to find them in the summit schedule and found none
18:16:19 mriedem same
18:17:29 mriedem nova project update: feature k8s!
18:17:34 mriedem *featuring
18:17:35 mriedem damn
18:20:48 jaypipes efried, edleafe: where are we on your battling microversion changes?
18:21:20 efried jaypipes: It's tied up on the home stretch while zuul unwinds its panties.
18:21:27 efried See topic
18:21:34 jaypipes k
18:24:51 openstackgerrit Matt Riedemann proposed openstack/nova master: Use ksa adapter for cinder client https://review.openstack.org/508345
18:24:54 mriedem efried: i've tried to rebase this but there are some known broken things in it ^
18:25:44 efried mriedem: Yeah, I had to put it aside for other "more urgent" things.
18:26:01 efried I swear I had it working at some point in the cycle.
18:26:34 efried but by the end, it was definitely busted and I couldn't figure out how to fix it without spending a big chunk of time.
18:28:31 openstackgerrit Claudiu Belu proposed openstack/nova master: db: Adds live-resize to Migration model migration_type https://review.openstack.org/185961
18:28:31 openstackgerrit Claudiu Belu proposed openstack/nova master: compute: Adds instance live-resize https://review.openstack.org/248581
18:34:20 openstackgerrit Surya Seetharaman proposed openstack/nova master: [WIP] Add CellMappingList.get_all_enabled() query method https://review.openstack.org/550188
18:34:20 openstackgerrit Surya Seetharaman proposed openstack/nova master: Add disabled field to CellMapping object https://review.openstack.org/550090
18:40:24 cdent nice message efried
18:40:40 openstackgerrit Surya Seetharaman proposed openstack/nova master: Add CellMappingList.get_all_enabled() query method https://review.openstack.org/550188
18:40:53 efried Thanks cdent. I guess if anyone was gonna bother to read the whole thing, it'd be you :)
18:41:21 cdent yeah, spose so
18:41:34 cdent I think you'll find there's a vast army of silent readers out there
18:41:48 cdent their silence can sometimes be rather disturbing
18:46:06 efried cdent: I'm quite a slow reader, and I often feel that pain when something's important enough that I know I gotta read it, but really long (like dhellman's missive on requirements). I guess for people who read at normal speeds, it's not such an onerous task.
18:47:25 cdent efried: yeah, I've been reminded many times that my attitude towards reading comes from something of a position of privilege. Apparently I read _very_ fast when it comes to email and similar forms.
18:47:42 efried That explains a lot.
18:48:49 efried I envy those who can read fast and not miss stuff. That's why I read slow - because I'm being real thorough (terrified of missing some detail or - gods forbid - failing to catch a typo!)
18:49:23 edleafe heh, just started reading efried's email
18:50:12 edleafe An hourglass would be good enough :)
18:52:35 cdent efried: I'm certain that I miss stuff, but I'm usually grazing for meaning, not details
18:52:58 efried I should develop that skill. FOMO.
18:53:18 cdent maybe not, probably useful to have both styles around
18:53:23 mriedem mgoddard_: stephenfin: dansmith: so maybe the numa topology filter is ok with ironic http://logs.openstack.org/12/553412/1/check/ironic-tempest-dsvm-ipa-wholedisk-bios-agent_ipmitool-tinyipa/2b781af/logs/screen-n-sch.txt.gz#_Mar_15_15_24_11_093172
18:53:27 mriedem that devstack change didn't blow up
18:53:33 dansmith sweet
18:53:41 cdent for me it's in part a learned skill to intentionally miss out on some stuff
18:55:03 mriedem could have sworn something about the IronicNodeState object was different such that the filter would fail with it
18:55:12 mriedem also, it's not like we actually have pci requests in these CI jobs
18:55:30 edleafe I tried to learn to skim back in college. I always felt like I never got anything out of it, so I went back to reading details
18:55:58 edleafe efried: excellent recap
18:55:59 dansmith mriedem: that's true, I guess a flavor or request with pci or numa could break if there are ironic hosts in there somehow,
18:56:09 dansmith but I dunno what that would be really
18:56:29 efried edleafe: Thanks.
18:56:36 mriedem dansmith: the other thing might have been something to do with allocation ratios, but grasping at straws
18:57:29 dansmith we don't have ratios for those types though
18:58:04 mriedem goes into the numa topology limits
18:58:08 mriedem the cpu and ram allocation ratois
18:58:55 cfriesen mriedem: we have a private patch to enable ironic and regular nodes...had to make some of the scheduler filters check the hypervisor type.
18:59:12 mriedem cfriesen: is there anything you guys don't have a private patch for?
18:59:33 cfriesen mriedem: we try to upstream stuff, but it takes forever
18:59:40 mgoddard_ mriedem: that's good news!
19:00:01 cfriesen mriedem: plus, we only need to worry about one hypervisor
19:00:16 mriedem mgoddard_: well, it's kind of a false positive i think
19:00:34 mriedem cfriesen: it takes even longer when you don't even propose them
19:00:45 dansmith mriedem: it's not a false positive, it's just not comprehensive.. it means something, it just doesn't mean it all works fine :)
19:01:39 mriedem i think host_topology_and_format_from_host might be the thing
19:02:20 mriedem that's just always None for ironic i think
19:02:22 cfriesen mriedem: yeah, I know. I don't control how much upstreaming time I get. Looks like we modified NUMATopologyFilter to check the hypervisor type, and modified AggregateInstanceExtraSpecsFilter to ignore the "baremetal" and "storage" keys.
19:02:45 dansmith mriedem: if that breaks if it's none, that probably also precludes using any two hypervisors together where one is libvirt with numa and the other doesn't support it, right?
19:03:14 mriedem nvm, that would just filter out that ironic node
19:03:19 mriedem / host
19:03:38 openstackgerrit Eric Berglund proposed openstack/nova master: WIP: Resize https://review.openstack.org/553583
19:03:59 mriedem cfriesen: if you could figure out *why* you "Looks like we modified NUMATopologyFilter to check the hypervisor type" that would be nice
19:04:13 mriedem because at some point i thought these wouldn't work but i can't figure out why now
19:04:24 dansmith yeah at least upstreaming the bug would be worthwhile
19:04:33 mriedem ++
19:04:42 dansmith although they do that, so if you did in this case, then .. cool :)
19:04:56 cfriesen mriedem: let me check with the author
19:10:48 sean-k-mooney mriedem: cfriesen perhaps because you wanted to avoid qemu hosts when there are numa requests?
19:11:59 mgoddard_ perhaps the bug is just that the NUMA filter doesn't work for ironic, rather than that it rejects all bare metal hosts?
19:12:11 cfriesen sean-k-mooney: don't think so, this was specifically part of allowing one nova-scheduler to handle both libvirt/kvm and ironic compute nodes
19:12:29 sean-k-mooney cfriesen: ah ok
19:13:41 sean-k-mooney mgoddard_: well if i ask for a 2 numa node instance the ironic should be able to select a node with 2 numa nodes however i dont think ironic adds numa info into the compute nodes table for the filter to use
19:13:53 mgoddard_ exactly
19:14:08 mgoddard_ same with cpu pinning
19:14:19 sean-k-mooney mgoddard_: no cpu pinning is different
19:14:20 mgoddard_ and hyperthreading
19:14:35 cfriesen mriedem: back to the nova-compute service delete issue, when deleting a service via the API, nova.db.sqlalchemy.api.service_destroy() will soft-delete both the service and the service and the compute_node entry, but placement is still around. Then we create the compute node again and get new service and compute_node entries with a different uuid but the same hostname.
19:14:36 sean-k-mooney cpu pinning does not make sense in a phyical server context
19:14:39 dansmith it wouldn't matter these days anyway, ironic nodes report a CUSTOM_IRONIC_FOO resource and no cpu/mem

Earlier   Later