Posted	Nick	Remark
#openstack-nova - 2019-09-10
04:39:06	openstackgerrit	Sundar Nadathur proposed openstack/nova master: [WIP] add cyborg tempest job https://review.opendev.org/670999
06:13:31	openstackgerrit	Luyao Zhong proposed openstack/nova master: Claim resources in resource tracker https://review.opendev.org/678452
06:13:31	openstackgerrit	Luyao Zhong proposed openstack/nova master: libvirt: Enable driver discovering PMEM namespaces https://review.opendev.org/678453
06:13:32	openstackgerrit	Luyao Zhong proposed openstack/nova master: libvirt: report VPMEM resources by provider tree https://review.opendev.org/678454
06:13:32	openstackgerrit	Luyao Zhong proposed openstack/nova master: libvirt: Support VM creation with vpmems and vpmems cleanup https://review.opendev.org/678455
06:13:33	openstackgerrit	Luyao Zhong proposed openstack/nova master: Parse vpmem related flavor extra spec https://review.opendev.org/678456
06:24:47	arshad777	I have created a sync replicated volume with peer persistence enabled. Attached this volume
07:18:55	openstackgerrit	Luyao Zhong proposed openstack/nova master: libvirt: Enable driver configuring PMEM namespaces https://review.opendev.org/679640
07:18:56	openstackgerrit	Luyao Zhong proposed openstack/nova master: Add functional tests for virtual persistent memory https://review.opendev.org/678470
07:36:57	openstackgerrit	Takashi NATSUME proposed openstack/python-novaclient master: doc: Add support microversions for options https://review.opendev.org/681174
08:21:11	bauzas	stephenfin: once you're there, see dansmith's comments
08:21:27	bauzas	stephenfin: he wants to squash https://review.opendev.org/#/c/680983/
08:21:44	bauzas	stephenfin: so please try to provide the new revisions this morning
08:51:03	stephenfin	sure thing
09:02:24	openstackgerrit	Balazs Gibizer proposed openstack/nova master: Support reverting migration / resize with bandwidth https://review.opendev.org/676140
09:11:36	openstackgerrit	weibin proposed openstack/nova master: Add support for using ceph RBD ereasure code https://review.opendev.org/681188
09:19:10	openstackgerrit	Balazs Gibizer proposed openstack/nova master: Func test for migrate re-schedule with bandwidth https://review.opendev.org/676972
09:21:29	openstackgerrit	Balazs Gibizer proposed openstack/nova master: Support migrating SRIOV port with bandwidth https://review.opendev.org/676980
09:23:48	openstackgerrit	Balazs Gibizer proposed openstack/nova master: Allow migrating server with port resource request https://review.opendev.org/671497
09:24:40	stephenfin	bauzas: trivial patch with no conflicts here https://review.opendev.org/#/c/679339/
09:24:45	stephenfin	(if you'd be so kind)
09:25:02	bauzas	reminder : I'm French, I'm never kind
09:25:41	stephenfin	bauzas: I'm going to rebase my the cpu-resources series on top of the SEV series to head off the incoming merge conflicts too
09:25:50	stephenfin	while I rework it, that is
09:26:05	bauzas	stephenfin: +Wd FWIW
09:26:08	openstackgerrit	Balazs Gibizer proposed openstack/nova master: Do not query allocations twice in finish_revert_resize https://review.opendev.org/678827
09:26:17	bauzas	stephenfin: cool, I'll look at gibi's series then
09:28:24	openstackgerrit	Balazs Gibizer proposed openstack/nova master: Allow resizing server with port resource request https://review.opendev.org/679019
09:30:40	openstackgerrit	Balazs Gibizer proposed openstack/nova master: Extract pf$N literals as constants from func test https://review.opendev.org/680991
09:30:41	openstackgerrit	Balazs Gibizer proposed openstack/nova master: Improve dest service level func tests https://review.opendev.org/680998
09:34:41	openstackgerrit	Brin Zhang proposed openstack/python-novaclient master: Microversion 2.80: Add user_id/project_id to migration-list API https://review.opendev.org/675023
09:38:26	openstackgerrit	Brin Zhang proposed openstack/python-novaclient master: Microversion 2.80: Add user_id/project_id to migration-list API https://review.opendev.org/675023
09:48:51	bauzas	gibi: I'm almost done with https://review.opendev.org/#/c/676140 but I'll need to do some checks later today
09:57:18	openstackgerrit	Brin Zhang proposed openstack/python-novaclient master: Microversion 2.80: Add user_id/project_id to migration-list API https://review.opendev.org/675023
10:09:57	aspiers	stephenfin: I'm here in case you have any last minute questions about https://review.opendev.org/#/c/644565/
10:21:31	gibi	bauzas: thanks
10:31:48	openstackgerrit	Alexandra Settle proposed openstack/nova master: Fixing broken links https://review.opendev.org/681206
10:32:22	openstackgerrit	Alexandra Settle proposed openstack/nova master: Fixing broken links https://review.opendev.org/681206
11:00:15	aspiers	Is there a way to get a guest's libvirt XML via the nova api? I'm guessing no
11:01:09	aspiers	Would be nice if it was available from https://docs.openstack.org/api-ref/compute/?expanded=show-server-diagnostics-detail#show-server-diagnostics
11:01:58	aspiers	Without the XML I am struggling to see how Tempest can verify that an SEV guest was actually booted with SEV enabled
11:07:23	gmann	aspiers: same case for NFV use case testing from artom L180 -https://etherpad.openstack.org/p/qa-train-ptg
11:07:31	aspiers	hmm
11:07:49	aspiers	gmann: which line?
11:08:08	gmann	in QA PTG, we accepted the idea of adding that tempest plugin into QA but it was action item for artom to propose that.
11:08:11	gmann	L180
11:08:15	aspiers	thanks
11:08:36	aspiers	oh nice
11:08:45	aspiers	yeah "white box plugin" sounds like a good concept
11:09:09	gmann	yeah and it can be expanded with more use case which is out of scope from Tempest
11:09:22	aspiers	right
11:10:31	aspiers	gmann: although I wonder if adding libvirt XML to the show-server-diagnostics API call might be a simpler solution
11:11:13	aspiers	showing the XML could be an admin-only thing
11:12:51	gmann	but even admin-only does it expose more info than nova should ? (from security point of view.)
11:13:38	gmann	I think it was discussed previously also but sean-k-mooney or artom might know more on that.
11:16:31	artom	gmann, yeah, I still want to do that, I was meant to propose a spec for Train but only have a very WIP up
11:17:39	artom	The code exists in RDO project's gerrit, and a Red Hat QE and myself wanted to clear outstanding reviews on there and merging its tests for NUMA live migration
11:17:47	artom	But that didn't happen yet
11:17:54	gmann	i see.
11:18:19	sean-k-mooney	gmann: sorry i was not following chat
11:18:27	sean-k-mooney	what were we talking about
11:18:48	gmann	sean-k-mooney: question from aspiers on exposing the libvirt XML to the show-server-diagnostics API
11:18:56	sean-k-mooney	aspiers: no there is not a way to get the xml form the api
11:19:00	sean-k-mooney	and there nerver will be
11:19:10	aspiers	that's a bold statement :)
11:19:35	sean-k-mooney	it completely violates the cloud abstration to expose that level of detail via the api
11:19:49	sean-k-mooney	a non admin is not even ment to know the hypervior that is in use
11:20:00	aspiers	sean-k-mooney: as admin-only diagnostics there is no violation
11:20:17	aspiers	sean-k-mooney: we're not talking about non-admins
11:20:26	sean-k-mooney	as admin only technically be they could jsut ssh into the host and look at the xml
11:20:37	aspiers	sean-k-mooney: not from tempest they can't
11:20:49	aspiers	plus that's a lot less convenient
11:20:53	sean-k-mooney	tempest shoudl not be asserting behavior of the xml generation
11:20:59	openstackgerrit	Brin Zhang proposed openstack/python-novaclient master: Microversion 2.80: Add user_id/project_id to migration-list API https://review.opendev.org/675023
11:21:13	aspiers	sean-k-mooney: please first read the use case above to understand the need ^^^
11:21:13	sean-k-mooney	that is what functional or white box testing is for
11:21:14	artom	aspiers, yeah, that's quite explicitly out of scope for tempest
11:21:20	sean-k-mooney	tempest if for blackbox testing
11:21:25	artom	But... quite explicitly *in* scope for whitebox :)
11:21:35	gmann	yeah
11:21:44	artom	So now you've landed yourself on the list of people interested, and will be poked mercilessly once it's ready ;)
11:21:44	aspiers	again, this is repeating discussion from a few minutes ago when we talked about the white box plugin
11:22:16	aspiers	if there is a white box plugin for tempest, then that means white box testing *is* in scope for the tempest ecosystem, even if not the core
11:22:16	sean-k-mooney	aspiers: so why cant you boot a vm and ssh into an detect that sev is configured from within the vm?
11:22:20	sean-k-mooney	or at least available
11:22:30	aspiers	sean-k-mooney: how would I detect that?
11:22:35	sean-k-mooney	lscpu?
11:22:45	sean-k-mooney	is there not an msr or cpu flag for sev
11:22:45	aspiers	sean-k-mooney: have you tested that?
11:22:55	sean-k-mooney	no i dont have sev hardware
11:23:20	gmann	aspiers: within scope of QA ecosystem not Tempest ecosystem. Tempest is just a tool under QA :)
11:23:24	artom	aspiers, yeah, we're not saying "don't do it", we're saying "don't propose patches for it to Tempest"
11:23:46	aspiers	artom: OK, it sounded like the former before :)
11:24:02	aspiers	gmann: the white box tempest plugin isn't in the tempest ecosystem? ;-)
11:24:10	sean-k-mooney	aspiers: whitebox and the intel nfv test repo use tempest as a framework
11:24:16	sean-k-mooney	to do this type of testing
11:24:30	sean-k-mooney	but its not in tempest as its out of scope fo tempest
11:24:47	sean-k-mooney	but a whitebox style tempest plugin for sev would be fine
11:24:53	sean-k-mooney	or add it to whitebox
11:25:04	artom	sean-k-mooney, unrelated, but we had some discussion around saving the new NUMA topology in https://review.opendev.org/#/c/634606/75/nova/compute/manager.py@7223 - and in func tests at least, that instance.refresh() isn't necessary (yes, the tests check the InstanceNUMATopology)

Earlier   Later