Posted	Nick	Remark
#openstack-nova - 2018-03-19
14:14:34	openstackgerrit	Jay Pipes proposed openstack/nova master: add _get_usages_from_trees() function https://review.openstack.org/534967
14:14:34	openstackgerrit	Jay Pipes proposed openstack/nova master: _get_trees_matching_all_resources() sum children https://review.openstack.org/534866
14:14:35	openstackgerrit	Jay Pipes proposed openstack/nova master: WIP - populate alloc cands for trees https://review.openstack.org/534968
14:14:35	openstackgerrit	Jay Pipes proposed openstack/nova master: validate provider summary structure https://review.openstack.org/536516
14:20:55	openstackgerrit	Jay Pipes proposed openstack/nova master: add test for scenario with sum of child resources https://review.openstack.org/534339
14:20:55	openstackgerrit	Jay Pipes proposed openstack/nova master: tests for alloc candidates with nested and traits https://review.openstack.org/531899
14:20:56	openstackgerrit	Jay Pipes proposed openstack/nova master: add _get_usages_from_trees() function https://review.openstack.org/534967
14:20:56	openstackgerrit	Jay Pipes proposed openstack/nova master: _get_trees_matching_all_resources() sum children https://review.openstack.org/534866
14:20:57	openstackgerrit	Jay Pipes proposed openstack/nova master: WIP - populate alloc cands for trees https://review.openstack.org/534968
14:20:57	openstackgerrit	Jay Pipes proposed openstack/nova master: validate provider summary structure https://review.openstack.org/536516
14:23:26	openstackgerrit	Merged openstack/nova-specs master: Add host info to instance action events https://review.openstack.org/543277
14:27:44	jaypipes	efried: ^^ I'm getting that nested providers in allocation candidates series back inline...
14:27:53	efried	jaypipes: Cool dude.
14:28:33	efried	Did you see my potentially earth-shattering dissenting opinion on the "split one resource across multiple providers" thing?
14:28:45	jaypipes	efried: no. link?
14:29:22	efried	jaypipes: https://review.openstack.org/#/c/534339/ -- my last comment, on PS5 before rebases
14:38:01	mriedem	dansmith: replied in https://review.openstack.org/#/c/543277/
14:38:16	mriedem	still don't see the need for hostId in the action events API, but people at the PTG wanted it
14:38:48	dansmith	mriedem: I'm commenting about the rst syntax, using `` instead of "
14:40:25	mriedem	oh, heh
14:40:46	mriedem	i can push a doc cleanup patch on that
14:41:34	kashyap	mriedem: melwitt: Heya, I've read the full chat between you both, dansmith, et al (including the quip: "besides the fix, you can also configure nova for other goodies!").
14:41:49	kashyap	Not to discuss this to death, but 3 quick points:
14:42:03	dansmith	mriedem: that's all I was saying :)
14:42:16	kashyap	(2) The two Nova config options thing just causes untold pain for all vendors with all their unique deployment tools; and just wastes precious time all around for little gain.
14:42:16	kashyap	(1) I want to do the Right Thing & not rush anything in.
14:42:20	kashyap	(3) On your point: "well, what I mean is if you use it and it breaks something in queens/pike/ocata then we're probably not going to fix things to accommodate the various flags they enable" — That's a good point. Yes, we have to loudly and clearly document that "NB: There's a huge combination of CPU flags possible, just by virtue of them being available in a given CPU. It's not reasonable to
14:42:26	kashyap	test all combinations; so if an Operator wants to try certain flags, it's their responsibility to test if that works in their environment".
14:44:22	openstackgerrit	Chris Dent proposed openstack/nova master: Move placement exceptions into the placement package https://review.openstack.org/549862
14:44:44	kashyap	melwitt: mriedem: As a last point, as dansmith also said in different words on Friday here —
14:44:55	kashyap	It is not sensible to create an intentionally incompatible syntax in the Nova config file when the actual Nova code to process the config options is largely identical in both cases.
14:45:34	openstackgerrit	Chris Dent proposed openstack/nova master: Optional separate database for placement API https://review.openstack.org/362766
14:47:16	openstackgerrit	Chris Dent proposed openstack/nova master: Isolate placement database config https://review.openstack.org/541435
14:47:29	openstackgerrit	Chris Dent proposed openstack/nova master: WIP: Ensure that os-traits sync is attempted only at start of process https://review.openstack.org/553857
14:51:12	openstackgerrit	Lenny Verkhovsky proposed openstack/nova master: Adding NVMEoF for libvirt driver https://review.openstack.org/482640
15:01:41	openstackgerrit	Matt Riedemann proposed openstack/nova-specs master: Address review comments from afdc828db3c9d0205b6ded268db24f5cdf857fa6 https://review.openstack.org/554251
15:04:32	openstackgerrit	Silvan Kaiser proposed openstack/nova master: Exec systemd-run with privileges in Quobyte driver https://review.openstack.org/554195
15:06:19	kaisers1	efried: fyi https://review.openstack.org/#/c/554195/2
15:06:30	openstackgerrit	Eric Fried proposed openstack/nova master: Report client: Remove version discovery comment https://review.openstack.org/554253
15:06:41	efried	jaypipes, mriedem, cdent ^
15:06:45	efried	kaisers1: ack
15:06:55	efried	edleafe: also --^
15:06:57	cfriesen	is github.com enforcing ssh versions now? I just got a "Peer reports incompatible or unsupported protocol version."
15:07:48	efried	Could that be what kashyap was running into earlier?
15:08:14	kashyap	efried: Probably; it's gone now. I'm able to fetch 'https' from git.o.o.
15:08:42	kashyap	cfriesen: I also had troubles this morning w/ GitHub as my 'origin' for Nova
15:08:57	cfriesen	looks like they're "weak crypto" versions of https
15:09:07	cfriesen	bah, they're *disabling*
15:09:26	kashyap	Yeah, apparently
15:09:58	efried	Cause it's crucial that the content of a public repo be strongly encrypted.
15:10:14	efried	Is that, what, so we don't get MITMs injecting viruses into the codebase for us?
15:11:03	efried	tox -e py27 -- trojan_horse ?
15:11:30	jaypipes	edleafe, cdent: do we have a bug in placement that diga might be able to pick up? he's looking for some work in placement/scheduler.
15:12:14	cfriesen	is it possible to use SSH URLs with github?
15:12:27	cfriesen	I don't see any on the nova page
15:12:55	jroll	cfriesen: yep, git@github.com:openstack/nova
15:13:03	jroll	need to add your public key in settings
15:13:08	edleafe	jaypipes: diga: there's always https://bugs.launchpad.net/nova/+bugs?field.tag=placement as a starting point
15:13:20	cfriesen	jroll: thanks
15:13:25	jroll	np
15:13:48	diga	edleafe: Sure, will go through it
15:14:49	diga	jaypipes: Thank you for your help
15:16:43	jaypipes	diga: if I come across something for you, I will let you know.
15:17:01	diga	jaypipes: Sure
15:21:56	diga	jaypipes: I also know NFV technologies like hugepages, numa, dpdk very well. If you have something on that, let me know
15:23:57	jaypipes	diga: cool. can you review this spec please? https://review.openstack.org/#/c/552924/
15:24:17	diga	jaypipes: sure
15:28:12	Spaz-Home	Morning folks
15:29:39	openstackgerrit	Chris Dent proposed openstack/nova master: Optional separate database for placement API https://review.openstack.org/362766
15:29:39	openstackgerrit	Chris Dent proposed openstack/nova master: Move placement exceptions into the placement package https://review.openstack.org/549862
15:29:40	openstackgerrit	Chris Dent proposed openstack/nova master: WIP: Ensure that os-traits sync is attempted only at start of process https://review.openstack.org/553857
15:29:40	openstackgerrit	Chris Dent proposed openstack/nova master: Isolate placement database config https://review.openstack.org/541435
15:32:13	Spaz-Home	Actually taking a relax weekend.. no coding.. just boiling 55 Habaneros, 2 Ghost Peppers, and trying to make a hot sauce without killing myself. Enjoy your day Cloud Creators :p
15:38:03	cdent	jaypipes: what's the status of your "standardized provider descriptor file" spec/idea? Where on the scale or need<->experimental fishing is that?
15:38:23	jaypipes	cdent: it's dead.
15:38:29	jaypipes	cdent: I'll abandon it.
15:38:32	cdent	dead fish
15:38:40	jaypipes	cdent: smelly dead fish.
15:39:05	jaypipes	cdent: I did too :) but I understand why dansmith doesn't.
15:42:25	mriedem	sahid: there are a couple of issues in the tests for https://review.openstack.org/#/c/497457/2
15:42:27	mriedem	https://review.openstack.org/#/c/497457/
15:42:39	mriedem	sahid: specifically self.assertEqual(0, guest.migrate_configure_max_speed.called)
15:42:44	mriedem	.called is a boolean
15:43:05	mriedem	it's probably better to use guest.migrate_configure_max_speed.assert_not_called()
15:44:04	mriedem	if you're about done for the day i could clean those up and then just approve
15:44:49	sahid	oh i was sure of that "called" returns a number
15:44:52	sahid	no no, i will
15:44:59	mriedem	call_count returns a number
15:45:03	sahid	but thanks for asking :)
15:45:12	sahid	ack
15:45:29	mriedem	thanks for finding that issue in the multinode job config
15:46:31	sahid	mriedem: yeah, it's that g-api service which looked very strange
15:47:06	openstackgerrit	Jay Pipes proposed openstack/nova master: validate provider summary structure https://review.openstack.org/536516
15:47:07	openstackgerrit	Jay Pipes proposed openstack/nova master: WIP - populate alloc cands for trees https://review.openstack.org/534968
15:47:39	kashyap	sahid: One more nit there: s/TAPs devices/TAP devices/ :-)
15:47:46	kashyap	(In driver.py)
15:48:49	cfriesen	has anyone run into problems with setuptools recently? I got a report that 39.0.1 didn't work with our version of pike, wondering if it's a general problem.
15:49:05	sahid	kashyap: :) sure i will address that too
15:49:41	kashyap	Thx
15:50:42	dansmith	cfriesen: I had an issue downstream last week where the parse_version was returning a tuple instead of a string

Earlier   Later