14:00:45 #startmeeting openstack-cyborg 14:00:46 Meeting started Wed May 16 14:00:45 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:47 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:49 The meeting name has been set to 'openstack_cyborg' 14:00:57 #topic roll call 14:01:02 #info Li_Liu 14:01:03 #info Howard 14:01:18 #shaohe_feng 14:01:31 #info Sundar 14:01:40 #info shaohe_feng 14:02:09 let's wait for another 4 mins for other people show up :) 14:02:16 #info Helloway 14:02:17 info sum12 14:02:21 #info sum12 14:04:10 #info Ed Leafe 14:06:48 Hi all 14:07:00 hi xinran__ :) 14:07:05 #info xinran__ 14:07:06 let's get started 14:07:25 #topic summit prep 14:07:41 first of all, I want to confirm Sundar's core nomination 14:07:54 we don't have any objections, right ? 14:08:56 okey than congrats Sundar :) 14:09:24 Thanks, zhipeng! 14:09:27 Congratulations 14:09:44 \o/ congratulations 14:10:03 congratz 14:10:10 Congratz 14:10:24 Thanks, everybody :) 14:10:59 okey about summit 14:11:11 Sundar when will you arrive at Vancouver ? 14:11:18 Sunday afternoon 14:11:36 same here 14:12:08 Do we want to review the list of questions I have made for the forum? 14:12:38 Sundar I don't think we need to review that 14:12:49 just discuss it at the forum would be great :) 14:13:07 Sundar Li_Liu there will be a upstream institute activity 14:13:22 and i was told cyborg was among the request by many new comers 14:13:51 so if you guys have time you can go to the meeting venue and do a brief training i guess :P 14:14:06 ok, I can show up there once I settle down things 14:14:25 training on what? 14:14:31 Cyborg Intro? 14:14:43 probably 14:14:48 Sounds good 14:14:56 some devstack intro maybe 14:15:09 ildiko is the contact person 14:15:23 ildikov 14:15:38 Do you have the full name of the contact, by any chance? 14:16:06 Ah, got it: Ildiko Vancsa 14:16:12 yep :) 14:16:38 she's our upstream institute ambassador :) 14:16:49 Sundar, ping me on wechat once you get there 14:16:57 we can go together 14:17:36 sounds like a plan :) 14:17:43 Sure, Li_Liu 14:18:05 okey plz also get in touch with our Lenovo and other colleagues 14:18:13 and have a team photo :) 14:18:18 for sure 14:18:34 gr8t :) 14:18:41 #topic sub team report 14:19:09 shaohe_feng i saw you guys had a great driver subteam meeting 14:19:20 could you give a brief summary on that ? 14:20:41 zhipeng, I setup a wiki about it. 14:21:06 https://wiki.openstack.org/wiki/Meetings/CyborgTeamMeeting 14:21:26 Weekly Cyborg sub-team meeting 14:22:05 o/ 14:22:11 we get agreement that the meeting will be biweekly 14:22:30 #link #link https://wiki.openstack.org/wiki/Meetings/CyborgDriverTeamMeeting 14:22:30 also discuss the current status of drivers support 14:23:13 ildikov just mentioned the upstream institue earlier :) 14:23:19 ildikov: Thanks for joining. Just FYI that the upstream institute is meeting on Sat/Sun, but I will be there only on Sunday. 14:23:27 please ping me if you can come to the training on Sunday, I can give a short summary on it 14:23:31 Helloway introduce her SPDK driver 14:23:45 ildikov: Sure, thanks 14:23:47 rodrigo introduce intel OPAE API. 14:23:54 I can come in the afternoon 14:24:32 Sundar: it's ok 14:24:35 Also some improvement on accelerator driver. 14:24:58 Sundar: it's more about answering students' questions on Cyborg as we have a few indicated that they are interested in the project 14:25:01 shaohe_feng anywhere i can find the minutes ? 14:25:22 zhipeng: thanks for the mention! :) 14:25:57 ildikov don't mention it (no pun intended :P) 14:26:32 zhipeng: my bad :) 14:26:47 :P 14:27:04 shaphe_feng i think I can dig out the minutes :) 14:27:13 thanks for hosting the meeting, it has a great start 14:27:14 zhipeng, it upload the log automaticly 14:27:28 did xilinx people join ? 14:27:34 let me find it. 14:27:46 zhipeng, xilinx people not joined 14:28:04 Li_Liu, will connect with them 14:28:04 okey thx 14:28:19 Li_Liu any update on the doc team side ? 14:28:25 hopeful next time, they can join. 14:28:40 no response.. 14:28:54 is Dutch still the contact? 14:29:20 zhipeng, http://eavesdrop.openstack.org/meetings/openstack_cyborg_driver/2018/openstack_cyborg_driver.2018-05-14-14.01.log.html 14:29:25 it is here. 14:29:32 thx man :) 14:29:45 Li_Liu no he left Xilinx 14:29:51 Chuck Song is the contact 14:30:02 hmm. ok 14:32:39 FYI, I am readying a patch for driver-agent API update. It would be good to know who is working on what area 14:32:42 Li_Liu any update on the doc side ? 14:33:09 SUndar i think lenovo team could help on that 14:33:15 zhipeng, not yet, I will start org it after the summit 14:33:54 okey 14:34:56 #topic critical rocky spec review 14:38:22 #info python-cyborgclient update 14:38:25 #link https://review.openstack.org/#/c/565023/ 14:38:44 and #link https://review.openstack.org/568799 14:38:50 zhipeng, as we discussed 14:38:57 this took large chunk of time last meeting 14:38:57 I have change the command to: 14:39:08 so plz review it and if ok let's land it now 14:39:13 openstack accelerator list 14:39:20 ^ Sundar 14:40:03 and change the service type to accelerator 14:40:37 shaohe: Sure. I did +1 just now 14:41:40 thanks 14:41:48 I will give a +2 14:42:36 we can add more command base on this patch 14:42:50 then users can easy to use cyborg 14:42:57 yes :) 14:43:01 this is a big help 14:43:15 been waiting for this. 14:43:19 this is great 14:43:25 shaohe: https://review.openstack.org/#/c/565023/ looks good. There are still some references to deprecation. I'll try to understand that and post comments. 14:43:50 May be we can remove the deprecated stuff later too 14:44:08 yes. let it work first. 14:44:14 then others can works on it. 14:44:27 it is a base patch for other commands. 14:44:53 I notice NokMikeR need cyborg client. 14:45:09 okey :) 14:45:52 #info quota specs 14:46:04 xinran__ do you have any further updates ? 14:48:06 I have update the spec 14:49:10 And also submitted the patch 14:49:10 Now I think quota usage can 14:49:10 work 14:49:24 When users create or delete one accelerator quota usage will also be updated 14:50:04 great. 14:50:05 sounds great 14:51:25 Need more review now 14:53:10 OK, will review it soon. 14:53:42 Sundar: thanks 14:54:16 thanks xinran__ , will review it. 14:54:26 #info fpga programming spec 14:54:30 We need to understand what it means to reserve an accelerator in Cyborg without informing Nova 14:54:38 Li_Liu you think this is in good shape ? 14:55:16 I think so 14:55:28 Sundar, do you have further comments? 14:55:39 I addressed your comments in my last patch 14:55:46 Yea, what does it mean for the driver to reserve an accelerator? 14:56:30 I will post comments on the patch 14:56:33 Sundar prepare for future usage ? 14:57:24 are you talking about the programming spec? 14:58:15 zhipeng: I will post comments after thinking some more 14:58:29 Li_Liu: I think we are talking of Xinran's quota spec 14:58:55 Sundar: you mean quota reserve or ... 14:59:05 Sundar regarding the fpga programming spec ? 14:59:26 :) 14:59:50 xinran: yes, in your patch: self._driver.reserve(...) 15:00:19 zhipeng: I will review all the specs and post comments :) 15:00:35 okey :) 15:01:05 I think admin can set the reserve. if reserve, cyborg should not report to placement? 15:01:53 shaohe_feng: you can report total=1 and reserved=1 15:02:10 at least with the bug fix that's currently being worked on 15:02:25 edleafe, got it. thanks. 15:02:46 edleafe, which bug? 15:03:10 Sundar: we need to reserve quota usage first, check delta+current usage < 0 or not, but quota usage will not be updated at this time. and after create accelerator successfully, we need call commit to update quota usage. 15:03:33 shaohe_feng: https://review.openstack.org/#/c/568613/ 15:03:59 shaohe_feng: it's still being debated whether this is a bug fix or a behavior change :) 15:04:11 Did I get your point? 15:05:33 edleafe, thanks. 15:06:56 xinran: As edleafe said, the better way is to increment the reserved count in Placement. Not all drivers may support the concept of reservation. 15:09:58 #info cyborg-nova interaction 15:10:10 Sundar have you address ed's comment on the spec ? 15:10:32 Sundar: okay let’s discuss after meeting 15:10:37 zhipeng, I will do it today. 15:10:39 have to drop. see you guys in the summit :) 15:10:57 okey :) 15:11:18 I think there is value in having one RC for FPGAs, one for GPUS, etc. I need to articulate it in the response. :) 15:11:19 Sundar, Do you have changed to multi resource class? 15:11:22 so let's try to review as many as possible by the end of the week 15:11:42 shaohe: yes, the spec has been updated to have one RC for each device type (GPU, FPGA, etc.) 15:13:19 good. Thanks. 15:13:58 #topic AoB 15:14:04 any other business :) 15:15:55 okey let's conclude the meeting now, thx everyone for showing up :) 15:15:59 safe travels 15:16:02 #endmeeting