Posted	Nick	Remark
#openstack-nova - 2019-04-10
20:54:17	openstackgerrit	Matt Riedemann proposed openstack/nova master: Use InstanceList.get_count_by_hosts when deleting a compute service https://review.openstack.org/651647
21:12:57	openstackgerrit	Matt Riedemann proposed openstack/nova master: Add archive_deleted_rows wrinkle to cross-cell functional test https://review.openstack.org/651650
21:15:09	openstackgerrit	Matt Riedemann proposed openstack/nova master: Add archive_deleted_rows wrinkle to cross-cell functional test https://review.openstack.org/651650
21:33:08	openstackgerrit	Matt Riedemann proposed openstack/nova-specs master: FUP for I68498afd481f7291a6102928d7999b4be49ded7a https://review.openstack.org/651653
21:47:09	openstackgerrit	Merged openstack/nova stable/stein: Override the 'get' method in DriverBlockDevice class https://review.openstack.org/647646
21:47:14	openstackgerrit	Merged openstack/nova stable/stein: Don't warn on network-vif-unplugged event during live migration https://review.openstack.org/650060
21:55:55	openstackgerrit	Merged openstack/nova stable/stein: libvirt: disconnect volume when encryption fails https://review.openstack.org/650931
22:01:33	openstackgerrit	Merged openstack/nova stable/stein: Move create of ComputeAPI object in websocketproxy https://review.openstack.org/649374
22:35:13	openstackgerrit	Colleen Murphy proposed openstack/nova stable/rocky: Move create of ComputeAPI object in websocketproxy https://review.openstack.org/649375
23:51:49	openstackgerrit	Artom Lifshitz proposed openstack/nova master: Revert "Wait for network-vif-plugged on resize revert" https://review.openstack.org/639396
23:51:49	openstackgerrit	Artom Lifshitz proposed openstack/nova master: [WIP] Revert resize: wait for external events in compute manager https://review.openstack.org/644881
#openstack-nova - 2019-04-11
00:34:03	openstackgerrit	Dakshina Ilangovan proposed openstack/nova-specs master: Resource Management Daemon - Base Enablement https://review.openstack.org/651130
01:39:41	openstackgerrit	ya.wang proposed openstack/nova-specs master: Expose auto converge and post copy https://review.openstack.org/651681
02:42:17	gmann	sean-k-mooney: artom : we are good on 648123 from microversion point of view. It is not breaking any API contract. Commented inline. https://review.openstack.org/#/c/648123/4
02:42:43	gmann	tempest schema test is passing which make sure the API contract verification
03:11:37	openstackgerrit	Boxiang Zhu proposed openstack/nova-specs master: Add host and hypervisor_hostname flag to create server https://review.openstack.org/645458
03:54:37	openstackgerrit	Merged openstack/nova master: Add test coverage for nova.privsep.libvirt. https://review.openstack.org/648616
04:06:22	openstackgerrit	Merged openstack/nova master: Add test coverage for nova.privsep.qemu. https://review.openstack.org/649191
04:16:07	openstackgerrit	Merged openstack/nova stable/stein: Do not persist RequestSpec.ignore_hosts https://review.openstack.org/649320
09:02:52	openstackgerrit	Theodoros Tsioutsias proposed openstack/nova-specs master: Add PENDING vm state https://review.openstack.org/648687
10:20:00	openstackgerrit	Chris Dent proposed openstack/nova master: Use update_provider_tree in vmware virt driver https://review.openstack.org/651615
10:29:42	openstackgerrit	Chris Dent proposed openstack/nova master: Delete the placement code https://review.openstack.org/618215
10:39:11	openstackgerrit	Merged openstack/nova-specs master: Spec: Use in_tree getting allocation candidates https://review.openstack.org/646029
11:46:38	openstackgerrit	Stephen Finucane proposed openstack/nova master: trivial: Remove dead nova.db functions https://review.openstack.org/649570
11:48:02	stephenfin	gibi: Wanna send this cleanup patch on its way? https://review.openstack.org/#/c/650018/
11:58:18	gibi	stephenfin: done
11:58:24	stephenfin	ta
12:03:01	artom	gmann, cheers! (if you're still awake/around)
12:39:03	cdent	aspiers: have you seen http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004779.html ?
12:39:41	aspiers	cdent: yes, it's on my TODO list :)
12:39:47	aspiers	still jetlagged from SUSECON
12:39:54	cdent	roger, thanks
12:40:15	aspiers	I saw that efried felt OK with the status quo though
12:40:37	openstackgerrit	Tetsuro Nakamura proposed openstack/nova master: Add in_tree field to RequestGroup object https://review.openstack.org/649534
12:40:37	aspiers	I'm inclined to agree that "don't do that" is a reasonable stance
12:40:37	openstackgerrit	Tetsuro Nakamura proposed openstack/nova master: Add get_compute_nodes_by_host_or_node() https://review.openstack.org/650877
12:40:38	openstackgerrit	Tetsuro Nakamura proposed openstack/nova master: Pass target host to RequestGroup.in_tree https://review.openstack.org/650878
12:40:38	openstackgerrit	Tetsuro Nakamura proposed openstack/nova master: Query `in_tree` to placement https://review.openstack.org/649535
12:40:44	sean-k-mooney	/query cdent
12:41:01	cdent	?
12:41:52	sean-k-mooney	i was going to pm you and had an extra space
12:41:54	sean-k-mooney	:)
12:42:54	aspiers	lucky you noticed before you said something rude in public ;-)
13:31:27	mnaser	is the nova archive tool not hitting cell0 a decision by design?
13:32:03	dansmith	mnaser: do you mean archive_deleted_rows?
13:32:08	mnaser	yeah
13:32:23	dansmith	isn't there an all cells flag for that?
13:32:33	mnaser	that was an unmerged patch afaik
13:32:46	dansmith	ah, okay, well, then yes by design? :)
13:32:49	openstackgerrit	Boxiang Zhu proposed openstack/nova master: Make evacuation respects anti-affinity rule https://review.openstack.org/649963
13:32:53	dansmith	run it against a config pointing at cell0
13:33:02	mnaser	https://review.openstack.org/#/c/587858/
13:33:18	mnaser	err well
13:33:20	mnaser	looks like that was a dup of https://review.openstack.org/#/c/507486/
13:33:35	mnaser	which seems to have stalled out
13:36:11	dansmith	mnaser: you can run purge --all-cells --before
13:36:25	dansmith	oh wait,
13:36:33	dansmith	I was thinking that did an archive first but it does not, nevermind
13:36:41	dansmith	it's not like I wrote that...
13:36:49	mnaser	it's early :p
13:36:57	dansmith	yeah, YEAH.
13:39:19	mnaser	anyways, I rechecked that patch and I can iterate here and there to get it to land eventually
13:39:27	mnaser	though probably not at a fast pace
13:54:18	stephenfin	dansmith, jaypipes, cdent, bauzas: Reworking the cpu-resources spec at the moment. It feels like the general preference is to have a hard break between the current behavior and the new placement-based flow, right?
13:54:56	stephenfin	as in only newly deployed compute nodes would support the new behavior
13:54:57	bauzas	stephenfin: well, my opinion would be to not have a modification if you have the same options
13:55:17	sean-k-mooney	?
13:55:32	bauzas	but maybe however for CONF.vcpu_pin_set
13:55:36	cdent	stephenfin: I'd need to load that context back in before being able to say something useful, so will defer to others for now
13:55:59	stephenfin	sean-k-mooney: Pretty much this https://review.openstack.org/#/c/555081/22/specs/train/approved/cpu-resources.rst@725
13:56:36	bauzas	stephenfin: so, see my opinion :
13:56:56	dansmith	stephenfin: no, I think that's the opposite of what we want
13:56:57	bauzas	- no modifications for the same options but CONF.vcpu_pin_set
13:56:58	sean-k-mooney	well i really wish we did not confalate vCPU with floating
13:57:12	sean-k-mooney	or with pinned
13:57:23	sean-k-mooney	it has a different meaning then either
13:58:14	sean-k-mooney	anyway personally i would like to have two paralle implementions. in train. freeze the current one and implement a paralle placemnt native one and then switch in U or later
13:58:44	stephenfin	dansmith: It is? What is the preference?
13:58:53	stephenfin	sean-k-mooney: Yeah, that's pretty much where my head was going
13:59:19	stephenfin	as for conflating VCPU with floating, I'm not sure what other term we could use
13:59:51	sean-k-mooney	a vCPU can be floating or pinned
13:59:58	dansmith	stephenfin: I think I said on the review that I was opposed to us solving the problem of accounting by making people move their guests around between computes that are counting the old way and new way
14:00:18	dansmith	stephenfin: so having compute nodes never transition to the new way (without being cleaned off first) is not okay
14:00:20	mriedem	melwitt: just fyi that i replied to some of your replies in the quotas from placement change https://review.openstack.org/#/c/638073/2
14:00:22	mriedem	https://review.openstack.org/#/c/638073/
14:00:25	sean-k-mooney	i dont like using the vCPU resouce class in plamenet to mean just floating as it has a different menanitn the VCPU in the flavor
14:00:25	mriedem	if you're working on updates
14:01:05	stephenfin	sean-k-mooney: We're eventually going to kill vcpus in the flavor though
14:01:09	sean-k-mooney	dansmith: ok so you are asking for an inpalce reshape or other mechanisuym
14:01:27	jaypipes	sean-k-mooney: I think I'm pretty clear in the glossary of that spec.
14:01:30	sean-k-mooney	stephenfin: im not really a fan of that but we could
14:01:55	sean-k-mooney	jaypipes: yes i know what it say in the spec
14:02:01	mriedem	mnaser: dansmith already said this but you can archive cell0 by just running it against a nova.conf with [database]/connection pointed at cell0
14:02:07	jaypipes	sean-k-mooney: that glossary clearly delineates between guest vCPU threads, shared host CPUs (floating CPUs) and dedicated host CPUs (pinned to a guest vCPU thread)
14:02:20	stephenfin	sean-k-mooney: Yeah, we won't need it once we're modelling this stuff in placement. That'd be a future work item though
14:02:39	stephenfin	sean-k-mooney: and VCPU and PCPU are far more succinct than VCPU_SHARED and VCPU_DEDICATED, even if we're overloading the term vCPU
14:02:40	dansmith	stephenfin: we are? (going to kill vcpu in the flavor) ?
14:03:07	sean-k-mooney	dansmith: see i dint think we were
14:03:13	dansmith	sean-k-mooney: me either :)
14:03:22	stephenfin	dansmith: https://review.openstack.org/#/c/555081/22/specs/train/approved/cpu-resources.rst@727

Earlier   Later