Posted	Nick	Remark
#openstack-cyborg - 2018-07-19
08:09:04	openstackgerrit	wangzhh proposed openstack/os-acc master: Init os-acc https://review.openstack.org/583097
08:55:10	pliu	Hi Cyborg, may I ask where I can find a demo record of Cyborg. I see some presentations of Cyborg, however I want to see a real demo of it. Thanks
11:22:48	openstackgerrit	wangzhh proposed openstack/os-acc master: Init os-acc https://review.openstack.org/583097
15:46:54	openstackgerrit	wangzhh proposed openstack/os-acc master: Init os-acc https://review.openstack.org/583097
20:51:12	openstackgerrit	Merged openstack/os-acc master: Init os-acc https://review.openstack.org/583097
#openstack-cyborg - 2018-07-20
00:41:33	openstackgerrit	Rodrigo Rojo proposed openstack/cyborg master: Adds OPAE FPGA driver https://review.openstack.org/584170
01:23:35	openstackgerrit	wangzhh proposed openstack/os-acc master: Fix package name https://review.openstack.org/584182
04:42:52	openstackgerrit	Merged openstack/os-acc master: Fix package name https://review.openstack.org/584182
09:23:12	openstackgerrit	coco-Gao proposed openstack/cyborg master: Add "interface_type" field in deployable DB https://review.openstack.org/584296
09:48:53	openstackgerrit	sahid proposed openstack/os-acc master: objects: prepare objects framework https://review.openstack.org/584299
11:27:57	openstackgerrit	coco-Gao proposed openstack/cyborg master: Add "interface_type" field in deployable DB https://review.openstack.org/584296
12:55:47	openstackgerrit	OpenStack Release Bot proposed openstack/os-acc master: Update reno for stable/rocky https://review.openstack.org/584362
#openstack-cyborg - 2018-07-21
00:47:39	openstackgerrit	Rodrigo Rojo proposed openstack/cyborg master: Adds OPAE FPGA driver https://review.openstack.org/584170
03:28:28	rrojo	@shaohe_feng?
03:29:25	rrojo	hello
03:38:08	openstackgerrit	Rodrigo Rojo proposed openstack/cyborg master: Adds OPAE FPGA driver https://review.openstack.org/584170
03:41:19	rrojo	hi Shaohe
#openstack-cyborg - 2018-07-22
14:48:50	openstackgerrit	wangzhh proposed openstack/cyborg master: Imply new cyborg deployable api https://review.openstack.org/584641
15:07:56	openstackgerrit	wangzhh proposed openstack/cyborg master: Imply new cyborg deployable api https://review.openstack.org/584641
#openstack-cyborg - 2018-07-24
06:10:45	openstackgerrit	ShaoHe Feng proposed openstack/cyborg master: support provider https://review.openstack.org/585146
07:06:31	openstackgerrit	Vu Cong Tuan proposed openstack/cyborg master: Switch to stestr https://review.openstack.org/580927
07:58:55	openstackgerrit	coco-Gao proposed openstack/cyborg master: Add "interface_type" field in deployable DB https://review.openstack.org/584296
08:08:35	openstackgerrit	Vu Cong Tuan proposed openstack/cyborg master: Switch to stestr https://review.openstack.org/580927
#openstack-cyborg - 2018-07-25
14:00:05	zhipeng	#startmeeting openstack-cyborg
14:00:06	openstack	Meeting started Wed Jul 25 14:00:05 2018 UTC and is due to finish in 60 minutes. The chair is zhipeng. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:08	openstack	Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:10	openstack	The meeting name has been set to 'openstack_cyborg'
14:00:31	zhipeng	#topic Roll Call
14:00:37	zhipeng	#info Howard
14:00:53	wangzhh	#info wangzhh
14:01:42	seungwook	Hi there~^^
14:01:47	zhipeng	hi rianx_ and seungwook :)
14:01:54	zhipeng	brianx_
14:02:07	shaohe_feng	#info shaohe_feng
14:02:09	Yumeng__	#info Yumeng
14:02:18	Helloway	#info Helloway
14:02:41	seungwook	Hi zhipeng, shaohe and yumeng
14:02:54	seungwook	Hi brianx
14:02:57	shaohe_feng	hi seungwook, welcome
14:03:27	Yumeng__	welcome seungwook
14:03:34	Yumeng__	:)
14:03:47	seungwook	Thanks all~ : )
14:04:04	zhipeng	Hi brianx__
14:04:15	Li_Liu	#info Li_Liu
14:04:34	seungwook	Hi Li Liu
14:04:56	Li_Liu	Hey Seungwook! welcome to the party
14:05:29	seungwook	Hi xinran
14:06:06	wangzhh	Hey Seungwook! Welcome!
14:06:23	zhipeng	#topic Rocky Development Update
14:06:26	seungwook	Thank wangzhh
14:06:36	zhipeng	so the deadline we are facing this week
14:06:43	zhipeng	is the client lib deadline
14:06:54	seungwook	Ho vrv
14:07:05	zhipeng	shaohe_feng how's the client side prepared ? Could we make it on time ?
14:08:33	shaohe_feng	zhipeng, which more features should we add for the client?
14:08:38	shaohe_feng	zhipeng, allocation?
14:08:59	zhipeng	could we do basic CRUD ?
14:09:00	shaohe_feng	zhipeng, unallocation?
14:09:04	Li_Liu	Does fpga program count?
14:09:26	Li_Liu	the program api should be ready this week
14:09:34	shaohe_feng	zhipeng, we can only list accelerators
14:10:00	Li_Liu	but calling the client part I am not sure
14:10:18	zhipeng	i don't think we could have programming in client on time
14:10:29	zhipeng	shaohe_feng, once coco and zhenghao's patch in
14:10:34	Li_Liu	ok, as least the api part
14:10:42	zhipeng	could we quickly add allocation and unallocation ?
14:10:45	xinran__	hi seungwook welcome
14:10:53	zhipeng	in the most simple form, add to the db, remove from db
14:11:09	shaohe_feng	zhipeng, if we want to let nova call cyborg. we do not need CRUD for accelerators. we need CRUD for deployables.
14:11:52	Li_Liu	according to the discussion in here: https://etherpad.openstack.org/p/cyborg-rocky-development
14:11:52	seungwook	Thank xinran
14:12:43	shaohe_feng	we can use the current PATCH deployable for allocation and unallocation
14:12:56	shaohe_feng	but I do not think this is a good ideas.
14:13:19	shaohe_feng	also do we need batch allocation?
14:13:59	shaohe_feng	for example, a user want 3 deployables, can he call once allocation?
14:13:59	zhipeng	which patch are you talking about ?
14:14:15	wangzhh	https://review.openstack.org/#/c/584641/ Maybe this one.
14:14:20	shaohe_feng	API part
14:14:39	zhipeng	why is it not a good idea ?
14:14:58	shaohe_feng	yes.
14:16:09	shaohe_feng	IMHO, There should better be a explicit API for these two actions
14:16:33	shaohe_feng	I also use PATCH for allocation and unallocation for my POC.
14:16:52	shaohe_feng	just for I do not touch more cyborg code
14:17:25	xinran__	I think there should be an unified api which does allocation and unallocation
14:17:41	zhipeng	xinran__ what do you mean by unified ?
14:17:50	xinran__	Instead of implementing in deployable api
14:17:52	shaohe_feng	the PATCH method, it is for resource, not for collections. So it can not support batch allocation
14:17:53	Coco	#info Coco
14:18:03	Li_Liu	1 api for both alloc and unalloc?
14:18:16	xinran__	I mean another independent api :)
14:18:27	Coco	2 independent api.
14:18:28	xinran__	#info xinran__
14:18:57	Li_Liu	shaohe_feng, i think as least there is no harm to have the PATCH method, even for long term
14:19:37	shaohe_feng	#link https://github.com/shaohef/cyborg/commit/13cb904809376584f3cf78b7d7f120817d83c2ad
14:19:52	shaohe_feng	this is a poc about half years ago
14:20:07	Coco	patch method can keep, but patch can do many things, not only allocate or unallocate.
14:20:15	shaohe_feng	I use it PATCH for unallocation
14:20:15	zhipeng	I agree with Li_Liu's assessment, should be good at the moment
14:20:35	shaohe_feng	curl -g -i -X PATCH http://localhost:6666/deployables/$UUID -H "Content-Type: application/json" \
14:20:35	shaohe_feng	-H "Accept: application/json" -H "X-Auth-Token: $(openstack token issue -f value -c id)" -d '

Earlier   Later