Posted	Nick	Remark
#openstack-nova - 2017-10-17
01:23:59	jichen	mriedem: no, every compute node has 1:1 relation to one hypervisor , I think powerVM used to have this problem and they modify the arch and now they have 1:1 relation?
01:24:34	mriedem	i think neo / novalink was always 1:1
01:24:55	jichen	ok, maybe I remember wrong thing about powerVM
01:25:07	jichen	we request one compute service running to represent a hypervisor , so if you have 5 z/VM to be managed , you have to create 5 compute service and each service running with nova.conf point to the z/VM to be managed
01:33:54	openstackgerrit	Merged openstack/nova-specs master: add z/VM Driver https://review.openstack.org/464915
01:38:17	openstackgerrit	Eric Fried proposed openstack/nova master: Send Allocations to spawn https://review.openstack.org/511879
01:38:26	mriedem	jichen: is there a blueprint in launchpad?
01:38:49	jichen	mriedem: I will create a new one right now, thanks for the reminder
01:56:18	openstackgerrit	Merged openstack/nova master: doc: Fix command output in scheduler document https://review.openstack.org/511839
01:59:32	openstackgerrit	Yikun Jiang proposed openstack/nova-specs master: Add pagination and timestamp filtering support for os-migrations API https://review.openstack.org/506030
03:18:20	openstackgerrit	Zhenyu Zheng proposed openstack/nova master: Add instance action record for attach/detach interface https://review.openstack.org/512190
03:33:42	openstackgerrit	Merged openstack/nova master: Fix nova-manage commands that do not exist https://review.openstack.org/512324
03:46:25	openstackgerrit	Yikun Jiang proposed openstack/nova-specs master: Add pagination and changes since filter support for os-instance-action API https://review.openstack.org/507762
04:00:11	BenderRodriguez	Help!
04:00:24	BenderRodriguez	I'm getting http 500 errors when attempting to run "openstack hypervisor list"
04:00:30	BenderRodriguez	The error is shown to be this: EmptyCatalog: The service catalog is empty.
04:00:44	BenderRodriguez	http://controller:8774/v2.1/os-hypervisors/detail returned with HTTP 500
04:01:39	BenderRodriguez	nova is listed as a compute service in "openstack service list"
04:01:43	BenderRodriguez	so I'm not sure what's going wrong
04:01:46	BenderRodriguez	any ideas?
05:06:29	priya_	BenderRodriguez - check openstack --debug hypervisor list
05:19:37	openstackgerrit	Takashi NATSUME proposed openstack/python-novaclient master: Fix missing metavar in aggregate-update https://review.openstack.org/512485
05:56:30	alex_xu	efried: I think the case you talk about can be supported by non-numbered request
05:57:14	alex_xu	efried: but the current code doesn't work for that case, that isn't the trait implementation problem, it is the current code implementation problem
06:40:18	openstackgerrit	jichenjc proposed openstack/nova master: Refactor placement version check https://review.openstack.org/512497
06:52:16	openstackgerrit	Zhenyu Zheng proposed openstack/nova-specs master: Improve the performance of filtering instances by IP. https://review.openstack.org/509326
07:04:25	openstackgerrit	Dai Dang Van proposed openstack/python-novaclient master: Use generic user for both zuul v2 and v3 https://review.openstack.org/512515
07:13:50	openstackgerrit	Dai Dang Van proposed openstack/python-novaclient master: Use generic user for both zuul v2 and v3 https://review.openstack.org/512515
07:19:43	openstackgerrit	Zhenyu Zheng proposed openstack/nova master: Add instance action record for attach/detach interface https://review.openstack.org/512190
08:02:25	openstackgerrit	Ghanshyam Mann proposed openstack/nova-specs master: Spec for API extensions policy removal https://review.openstack.org/508101
08:06:24	gmann	alex_xu: ^^ updated the spec for policy things
08:19:28	alex_xu	gmann: thanks, will reach to it before the end of day
08:21:04	gmann	alex_xu: thanks. also BPs are separated out with policy change and other extensions merge things. mriedem has approved the specless BP for extensions merge things
08:24:42	alex_xu	gmann: cool!
08:25:46	openstackgerrit	Andrey Volkov proposed openstack/osc-placement master: CLI for inventories https://review.openstack.org/457533
08:25:46	openstackgerrit	Andrey Volkov proposed openstack/osc-placement master: CLI for allocations https://review.openstack.org/457534
08:25:47	openstackgerrit	Andrey Volkov proposed openstack/osc-placement master: CLI for usages https://review.openstack.org/457535
08:25:47	openstackgerrit	Andrey Volkov proposed openstack/osc-placement master: CLI for aggregates https://review.openstack.org/505643
08:25:48	openstackgerrit	Andrey Volkov proposed openstack/osc-placement master: [WIP] CLI for resource classes https://review.openstack.org/511182
08:25:48	openstackgerrit	Andrey Volkov proposed openstack/osc-placement master: [WIP] RP list: member_of and resources parameters https://review.openstack.org/511183
08:38:47	rabel	hi there, can we finally merge https://review.openstack.org/#/c/494169/ ?
08:39:50	rabel	and could someone help me with https://review.openstack.org/#/c/402632/ ? zuul does not seem to be rechecking for a week
08:45:26	openstackgerrit	Andrey Volkov proposed openstack/osc-placement master: CLI for inventories https://review.openstack.org/457533
08:45:27	openstackgerrit	Andrey Volkov proposed openstack/osc-placement master: CLI for allocations https://review.openstack.org/457534
08:45:27	openstackgerrit	Andrey Volkov proposed openstack/osc-placement master: CLI for usages https://review.openstack.org/457535
08:45:28	openstackgerrit	Andrey Volkov proposed openstack/osc-placement master: CLI for aggregates https://review.openstack.org/505643
08:45:28	openstackgerrit	Andrey Volkov proposed openstack/osc-placement master: [WIP] CLI for resource classes https://review.openstack.org/511182
08:45:29	openstackgerrit	Andrey Volkov proposed openstack/osc-placement master: [WIP] RP list: member_of and resources parameters https://review.openstack.org/511183
08:45:34	gibi	rabel: as http://zuulv3.openstack.org/ does not show that your patch is handled by zuul right now you can simply recheck https://review.openstack.org/#/c/402632/ again
08:46:29	rabel	gibi: thanks for the hint. i did so a week ago, but nothing has happened. do you know why?
08:47:38	gibi	rabel: in the past weeks infra tried to migrate from zuul v2 to zuul v3 and that resulted several restart of zuul. I guess your patch was affected by such a restart
08:48:10	rabel	gibi: ah ok. thank you!
09:04:25	jichen	cdent: hi ,may I ask a placement rest api question?
09:05:00	openstackgerrit	Zhenyu Zheng proposed openstack/nova master: Add instance action record for attach/detach interface https://review.openstack.org/512190
09:05:43	cdent	jichen: yes, sure. what’s up?
09:06:00	jichen	cdent: we have some code like : req.response.location = util.resource_class_url(req.environ, rc)
09:06:09	jichen	but I didn't see any response in the output
09:06:22	jichen	I think nova compute api has something like Location: xxxx ?
09:06:39	jichen	Date: Tue, 17 Oct 2017 08:49:01 GMT
09:06:40	jichen	Server: Apache/2.4.18 (Ubuntu)
09:06:42	jichen	Content-Length: 62
09:06:43	jichen	Content-Type: application/json
09:06:45	jichen	OpenStack-API-Version: placement 1.10
09:06:46	jichen	vary: OpenStack-API-Version
09:06:48	jichen	x-openstack-request-id: req-d638ece0-f12d-4d06-8f04-1f68c8a21650
09:06:49	jichen	Connection: close
09:06:54	jichen	this is what I got from a 'curl xxx' to placement
09:07:50	jichen	I mean, in the response header, do we plan to have a header about Location or not?
09:07:51	cdent	jichen: what request were you making?
09:08:51	jichen	curl -g -i -X PUT "http://192.168.122.243/placement/resource_providers/929b0597-e4e0-47f7-b4af-9a8c2c8f61d0/traits?nameith:CUSTOM" -H "OpenStack-API-Version: compute 2.53" -H "Content-Type: application/json" -H "OpenStack-API-Version: placement 1.10" -H "X-Auth-Token: gAAAAABZ5cPl6wpCFyQIbl2-JLuKEEOiUSNaeu7OGtcqoBRz-mDwP8bGS6IfdA139oVqv4AGKSGHpCBklbx6seqrsNPwUB_yZY5kmUAXxg5B_FB7V99RJV_Db3ovJu2xHlk
09:08:53	jichen	YJ5sn9mo3di0kzJtl5AT0dxaL_iCR8GVp1rEEajIwvg0DSk3E8Eo" -d '{"resource_provider_generation": 17, "traits": ["CUSTOM_ABC"]}'
09:09:29	cdent	location will show up in response to only some requests: post to create one inventory, post to create a resource class, put to create a resource class, post to create a resource provider, put to create a trait
09:09:44	cdent	so in that example you’ve done a PUT to a resource provider, which does not support location header
09:09:52	cdent	as written at least
09:09:54	openstackgerrit	Balazs Gibizer proposed openstack/nova master: Move restart_compute_service to a common place https://review.openstack.org/512551
09:09:54	openstackgerrit	Balazs Gibizer proposed openstack/nova master: Enhance service restart in functional env https://review.openstack.org/512552
09:09:55	openstackgerrit	Balazs Gibizer proposed openstack/nova master: Reproduce bug 1724172 in the functional test env https://review.openstack.org/512553
09:09:56	openstack	bug 1724172 in OpenStack Compute (nova) "Allocation of an evacuated instance is not cleaned on the source host if instance is not defined on the hypervisor" [Undecided,New] https://launchpad.net/bugs/1724172
09:10:25	jichen	stack@ubuntu1:~$ curl -g -i -X PUT "http://192.168.122.243/placement/resource_providers/929b0597-e4e0-47f7-b4af-9a8c2c8f61d0/traits" -H ack-API-Version: compute 2.53" -H "Content-Type: application/json" -H "OpenStack-API-Version: placement 1.10" -H "X-Auth-Token: gAAAAABZ5cPl6wpCFyQIbl2-JLuKEEOiUSNaeu7OGtcqoBRz-mDwP8bGS6IfdA139oVqv4AGKSGHpCBklbx6seqrsNPwUB_yZY5kmUAXxg5B_FB7V99RJV_Db3ovJu2xHlkYJ5sn
09:10:27	jichen	9mo3di0kzJtl5AT0dxaL_iCR8GVp1rEEajIwvg0DSk3E8Eo" -d '{"resource_provider_generation": 18, "traits": ["CUSTOM_ABC"]}'
09:10:28	jichen	HTTP/1.1 200 OK
09:10:30	jichen	Date: Tue, 17 Oct 2017 09:09:54 GMT
09:10:31	jichen	Server: Apache/2.4.18 (Ubuntu)
09:10:33	jichen	Content-Length: 62
09:10:34	jichen	Content-Type: application/json
09:10:36	jichen	OpenStack-API-Version: placement 1.10
09:10:37	jichen	vary: OpenStack-API-Version
09:10:39	jichen	x-openstack-request-id: req-4ce20136-afb8-405e-86ff-2397a21cc1c2
09:10:39	cdent	jichen: you’re right that we should probably be consistent about it, but it looks like we weren’t. I think the logic that was used is that a location header is a good idea if the response is empty
09:10:40	jichen	Connection: close
09:10:42	jichen	{"traits": ["CUSTOM_ABC"], "resource_provider_generation": 19}
09:10:44	jichen	sorry, wrong lURL
09:11:03	jichen	2nd URL I used is to PUT traits
09:11:10	cdent	jichen: for long pastes like that it is better to use a pastebin like http://paste.openstack.org/
09:11:17	jichen	ok, right now
09:11:31	cdent	that’s put to add traits to a resource provider, not to create a trait
09:11:57	jichen	cdent: http://paste.openstack.org/show/623800/
09:14:20	priya__	hi ..could somebody review the commit - https://review.openstack.org/#/c/508533/
09:14:44	cdent	jichen: right, so that request corresponds with this handler: https://github.com/openstack/nova/blob/master/nova/api/openstack/placement/handlers/trait.py#L217-L248 which does not set the header
09:14:52	cdent	jichen: do you think it should?

Earlier   Later