14:01:51 #startmeeting openstack-cyborg 14:01:52 Meeting started Wed Jul 11 14:01:51 2018 UTC and is due to finish in 60 minutes. The chair is zhipeng. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:53 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:57 The meeting name has been set to 'openstack_cyborg' 14:02:03 #topic Roll Call 14:02:09 #info Howard 14:02:14 #info Li_Liu 14:03:33 #info Helloway 14:03:45 #info shaohe_feng 14:03:46 everyone plz use the #info cmd to sign up 14:04:03 #info wangzhh 14:04:35 #info 14:04:59 #info gaojinghua 14:05:54 #sum12 14:06:21 shaohe_feng will sundar attend ? 14:06:50 zhipeng, I do not think so 14:07:00 on vacation ? 14:07:00 he is on vocation. 14:07:02 yes 14:07:12 until when ? 14:07:25 seems \7/25 14:08:11 from July 10 night through July 25, coming back on 26th. 14:08:22 lol 14:08:40 long vacation. 14:08:48 okey let's get into business 14:09:00 #topic Rocky Development Update 14:09:05 #link https://review.openstack.org/#/q/status:open+project:openstack/cyborg 14:09:12 #topic os-acc design 14:09:33 https://review.openstack.org/577438 14:09:56 Li_Liu shaohe_feng is there any consensus converging on the current proposal ? 14:11:26 I don't have any further comments on that one 14:11:38 meaning satisfied ? 14:11:45 or still waiting for answers 14:11:47 I really want to know the scope of the os-acc. 14:12:34 will it cover the program and instance binding? 14:14:20 we have not define the binding interface. The binding should pass hostname and instance uuid and request spec. 14:14:32 Li_Liu wangzhh Coco-Gao what's your opinion 14:14:55 I think so. os-acc call cyborg to program and bind. 14:15:36 it should be able to call the program API 14:16:04 rest full API 14:16:15 ? 14:16:22 but how it calls it is the problem here 14:16:23 Not just restful api. 14:16:32 exactly 14:16:43 rest/rpc/something else? 14:17:14 for the moment, the most intuitive way is calling the REST API I am currently writing 14:17:35 can program also call RPC? 14:17:46 wangzhh how's the os-brick handling the attach ? 14:17:58 wangzhh sundar suggest to use rpc call? 14:18:14 I've talked to Sundar about it. We agreed that os-acc should call not just api. 14:19:06 In fact, call api only is another option. 14:19:38 besides api what could it call ? 14:20:29 Maybe allowing os-acc directly call the vendor driver api is another option 14:20:53 that would be the original design right ? 14:21:02 contain it on the compute node level 14:21:08 without any api interactions 14:21:19 In some cases, we must call api. But sometimes, rpc call is a good code path, too. 14:21:33 os-acc call cyborg-agent using rpc? 14:21:56 CoCo: Yes 14:22:17 The original design right. 14:23:01 ok, when should we use rpc and when should we use api? 14:23:27 Sorry, lost an "is". 14:24:41 Attach, deatch use rpc. 14:26:44 zhipeng: "contain it on the compute node level". that should be the easiest way for now 14:27:00 will attach/detach involving binding shaohe_feng mentioned ? 14:29:38 Binding is before attach I think? 14:30:08 bind the vm instance with the acc instance ? 14:30:18 do we have similar process in other module ? 14:31:09 the binding should be taken care of before the process get to the vendor driver 14:31:13 Neutron 14:31:40 i think there was a comment from Sundar states that it is kinda different for neutron 14:31:46 the port binding 14:31:48 Nova call neutron-agent directly to allocate port. 14:31:50 and the acc binding 14:33:15 okey let's arrange another ZOOM call for specificities 14:33:28 the big problem here is about the os-acc scope, like shaohe said 14:33:37 what we want it to be for Rocky release 14:33:46 In my opinion, we can imply it as the design now. For the api and os-acc are stable. We can refactor it if needed. 14:33:57 bare minimum , or we want binding, programming in it as well 14:34:36 we need to start implementation as soon as possible for sure 14:34:50 I agree with wangzhh, we should get the thing working first 14:35:03 ZOOM call would be great 14:35:24 Li_Liu will it block FPGA programing if os-acc does not include program support ? 14:36:07 no it should not as my programming support is a stand alone feature 14:36:15 it does not depends on others 14:36:57 okey then let's shoot for the minimum feature goal 14:37:26 shall we have a ZOOM meeting say 10:00 am tmr ? 14:37:35 discuss os-acc in detail ? 14:37:53 you mean china time? 14:38:07 yes, 10:00pm for Toronto 14:38:14 should be fine 14:38:17 about less than 12 hours later 14:38:22 up to you guys 14:38:33 wangzhh shaohe_feng Coco-Gao okey ? 14:38:53 I'm OK. 14:39:03 ok 14:39:34 ok then I assume shaohe is ok as well :) 14:39:37 moving on 14:39:43 #topic GPU driver 14:39:44 could you guys post some notes about your discussion ? 14:39:53 sum12 definitely 14:40:20 wangzhh any timeline for the GPU driver ? 14:40:36 #link https://review.openstack.org/574075 14:41:04 I'll update the commit tmr. 14:41:23 can you also reply to the NVIDIA guy ? 14:41:36 i remember he asked about an introduction about the driver code 14:41:40 in the email thread 14:41:44 Of course. I have promised Mike. 14:42:13 gr8t :) 14:42:16 moving on 14:42:25 #topic FPGA API 14:42:28 I think Mike asked more than the driver code, but the cyborg related code as well. 14:42:39 #link https://review.openstack.org/579315 14:42:48 Li_Liu is this still premature ? 14:43:26 Coco: Yes. I'll try my best to describe it. 14:44:07 zhipeng, it's not ready yet 14:44:26 okey got it 14:44:40 moving on to next 14:44:46 #topic Quota support 14:44:50 #link https://review.openstack.org/564968 14:44:59 xinran___ 14:45:55 why is there a 16KiB file change in the patch ? 14:46:03 the swp file 14:46:37 haha. :) 14:47:01 lol so weird 14:47:49 xinran__ are you around ? 14:47:53 http://docs.ocselected.org/openstack-manuals/kilo/networking-guide/content/logical-architecture.html 14:48:38 #link https://docs.openstack.org/install-guide/get-started-logical-architecture.html 14:49:08 https://review.openstack.org/#/c/580022/2/.gitignore This commit could resolve the swp file. 14:50:44 I’m here 14:50:59 Sorry for the swp file... 14:51:08 Haha 14:51:11 no problem 14:51:30 other than that, plz address Li Liu's commenty 14:51:37 and let's move forward 14:51:43 OK 14:52:28 okey i think we reviewed most of the important current available patches 14:52:59 zhipeng, what's the currently time line? 14:53:18 shooting for code completion before RC freeze 14:53:53 ok 14:54:13 but the os-acc and nova interaction is still faaar behind.. 14:55:28 https://releases.openstack.org/rocky/schedule.html 14:55:39 os-acc will miss the R release i'm fraid 14:55:44 as non-client libraries 14:56:07 but as long as we have code implementation, we could have docs guiding the user how to use it 14:56:19 ok 14:56:35 the week of Aug 20 - Aug 24 is the RC deadline 14:56:48 I am just hoping we can make cyborg be in a usable state in R 14:56:54 which gives us barely more than a month of time 14:57:01 Li_Liu of course 14:57:34 #topic Berlin Summit CFP 14:57:47 since we will merge accelerator&deployable db table, should we modify the code after xinran's code being merged? 14:57:50 Plz be aware that the Berlin Summit CFP ends on Jul 17th 14:58:08 Zhipeng, Li_liu, if we can't merge os-acc in nova in time. Can we offer the code as patch to user? 14:58:20 wangzhh that was what I meant 14:58:31 because the repo is aleady there, thx xinran__ 14:58:40 as long as we have workable code 14:58:49 in or out of a release is not that big a deal 14:58:52 zhipeng, will you go to Berlin? 14:59:17 yes definitely 14:59:22 maybe will do a keynote 14:59:28 with cyborg+AI 14:59:35 but nothing settled yet :P 14:59:36 that's great 14:59:44 Wow~ 15:00:10 nice 15:00:27 a big maybe, let see how Mark Collier and others works out the arrangement 15:00:31 maybe nothing 15:00:56 plz remember submit topic for Berlin Summit 15:01:05 ok see you guys tmr on ZOOM 15:01:10 10am Beijing time 15:01:17 tomorrow? 15:01:17 Coco_Gao: I think you can go ahead because quota support still need Oslo limit be ready 15:01:41 yes tmr 15:02:02 xinran__ let's discuss it tmr as well 15:02:31 OK 15:02:55 thx everyone 15:02:59 #endmeeting