Earlier  
Posted Nick Remark
#openstack-cyborg - 2018-07-11
14:12:34 shaohe_feng will it cover the program and instance binding?
14:14:20 shaohe_feng we have not define the binding interface. The binding should pass hostname and instance uuid and request spec.
14:14:32 zhipeng Li_Liu wangzhh Coco-Gao what's your opinion
14:14:55 wangzhh I think so. os-acc call cyborg to program and bind.
14:15:36 Li_Liu it should be able to call the program API
14:16:04 shaohe_feng rest full API
14:16:15 shaohe_feng ?
14:16:22 Li_Liu but how it calls it is the problem here
14:16:23 wangzhh Not just restful api.
14:16:32 Li_Liu exactly
14:16:43 Li_Liu rest/rpc/something else?
14:17:14 Li_Liu for the moment, the most intuitive way is calling the REST API I am currently writing
14:17:35 shaohe_feng can program also call RPC?
14:17:46 zhipeng wangzhh how's the os-brick handling the attach ?
14:17:58 Coco_Gao wangzhh sundar suggest to use rpc call?
14:18:14 wangzhh I've talked to Sundar about it. We agreed that os-acc should call not just api.
14:19:06 wangzhh In fact, call api only is another option.
14:19:38 zhipeng besides api what could it call ?
14:20:29 Li_Liu Maybe allowing os-acc directly call the vendor driver api is another option
14:20:53 zhipeng that would be the original design right ?
14:21:02 zhipeng contain it on the compute node level
14:21:08 zhipeng without any api interactions
14:21:19 wangzhh In some cases, we must call api. But sometimes, rpc call is a good code path, too.
14:21:33 Coco_Gao os-acc call cyborg-agent using rpc?
14:21:56 wangzhh CoCo: Yes
14:22:17 wangzhh The original design right.
14:23:01 Coco_Gao ok, when should we use rpc and when should we use api?
14:23:27 wangzhh Sorry, lost an "is".
14:24:41 wangzhh Attach, deatch use rpc.
14:26:44 Li_Liu zhipeng: "contain it on the compute node level". that should be the easiest way for now
14:27:00 zhipeng will attach/detach involving binding shaohe_feng mentioned ?
14:29:38 xinran__ Binding is before attach I think?
14:30:08 zhipeng bind the vm instance with the acc instance ?
14:30:18 zhipeng do we have similar process in other module ?
14:31:09 Li_Liu the binding should be taken care of before the process get to the vendor driver
14:31:13 wangzhh Neutron
14:31:40 zhipeng i think there was a comment from Sundar states that it is kinda different for neutron
14:31:46 zhipeng the port binding
14:31:48 wangzhh Nova call neutron-agent directly to allocate port.
14:31:50 zhipeng and the acc binding
14:33:15 zhipeng okey let's arrange another ZOOM call for specificities
14:33:28 zhipeng the big problem here is about the os-acc scope, like shaohe said
14:33:37 zhipeng what we want it to be for Rocky release
14:33:46 wangzhh 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 zhipeng bare minimum , or we want binding, programming in it as well
14:34:36 zhipeng we need to start implementation as soon as possible for sure
14:34:50 Li_Liu I agree with wangzhh, we should get the thing working first
14:35:03 Li_Liu ZOOM call would be great
14:35:24 zhipeng Li_Liu will it block FPGA programing if os-acc does not include program support ?
14:36:07 Li_Liu no it should not as my programming support is a stand alone feature
14:36:15 Li_Liu it does not depends on others
14:36:57 zhipeng okey then let's shoot for the minimum feature goal
14:37:26 zhipeng shall we have a ZOOM meeting say 10:00 am tmr ?
14:37:35 zhipeng discuss os-acc in detail ?
14:37:53 Li_Liu you mean china time?
14:38:07 zhipeng yes, 10:00pm for Toronto
14:38:14 Li_Liu should be fine
14:38:17 zhipeng about less than 12 hours later
14:38:22 Li_Liu up to you guys
14:38:33 zhipeng wangzhh shaohe_feng Coco-Gao okey ?
14:38:53 wangzhh I'm OK.
14:39:03 Coco_Gao ok
14:39:34 zhipeng ok then I assume shaohe is ok as well :)
14:39:37 zhipeng moving on
14:39:43 zhipeng #topic GPU driver
14:39:44 sum12 could you guys post some notes about your discussion ?
14:39:53 zhipeng sum12 definitely
14:40:20 zhipeng wangzhh any timeline for the GPU driver ?
14:40:36 zhipeng #link https://review.openstack.org/574075
14:41:04 wangzhh I'll update the commit tmr.
14:41:23 zhipeng can you also reply to the NVIDIA guy ?
14:41:36 zhipeng i remember he asked about an introduction about the driver code
14:41:40 zhipeng in the email thread
14:41:44 wangzhh Of course. I have promised Mike.
14:42:13 zhipeng gr8t :)
14:42:16 zhipeng moving on
14:42:25 zhipeng #topic FPGA API
14:42:28 Coco_Gao I think Mike asked more than the driver code, but the cyborg related code as well.
14:42:39 zhipeng #link https://review.openstack.org/579315
14:42:48 zhipeng Li_Liu is this still premature ?
14:43:26 wangzhh Coco: Yes. I'll try my best to describe it.
14:44:07 Li_Liu zhipeng, it's not ready yet
14:44:26 zhipeng okey got it
14:44:40 zhipeng moving on to next
14:44:46 zhipeng #topic Quota support
14:44:50 zhipeng #link https://review.openstack.org/564968
14:44:59 zhipeng xinran___
14:45:55 zhipeng why is there a 16KiB file change in the patch ?
14:46:03 zhipeng the swp file
14:46:37 wangzhh haha. :)
14:47:01 zhipeng lol so weird
14:47:49 zhipeng xinran__ are you around ?
14:47:53 shaohe_feng http://docs.ocselected.org/openstack-manuals/kilo/networking-guide/content/logical-architecture.html
14:48:38 shaohe_feng #link https://docs.openstack.org/install-guide/get-started-logical-architecture.html
14:49:08 wangzhh https://review.openstack.org/#/c/580022/2/.gitignore This commit could resolve the swp file.
14:50:44 xinran__ I’m here
14:50:59 xinran__ Sorry for the swp file...
14:51:08 xinran__ Haha
14:51:11 zhipeng no problem
14:51:30 zhipeng other than that, plz address Li Liu's commenty

Earlier   Later