| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-cyborg - 2018-07-04 | |||
| 14:02:07 | zhipeng | i forgot today's US's national day | |
| 14:03:39 | Li_Liu | lol | |
| 14:04:25 | zhipeng | let's cancel the meeting lol | |
| 14:05:05 | Li_Liu | sure | |
| 14:05:16 | Li_Liu | have a good nite :) | |
| #openstack-cyborg - 2018-07-05 | |||
| 16:00:36 | openstackgerrit | wu.chunyang proposed openstack/cyborg master: Add release note link in README https://review.openstack.org/580435 | |
| #openstack-cyborg - 2018-07-06 | |||
| 07:06:51 | openstackgerrit | Nguyen Van Trung proposed openstack/cyborg master: Improve .gitignore for project https://review.openstack.org/580022 | |
| #openstack-cyborg - 2018-07-09 | |||
| 06:52:46 | openstackgerrit | Vu Cong Tuan proposed openstack/cyborg master: Switch to stestr https://review.openstack.org/580927 | |
| 12:54:38 | shaohe_feng | For most of developers can not join today’s irc meeting. | |
| 12:54:39 | shaohe_feng | So we can cancel today’s irc meeting. | |
| #openstack-cyborg - 2018-07-10 | |||
| 03:32:57 | openstackgerrit | Vu Cong Tuan proposed openstack/cyborg master: Switch to stestr https://review.openstack.org/580927 | |
| 18:05:47 | dpaterson | Is utilizing cyborg service via container workloads running in OpenStack on the project roadmap? | |
| #openstack-cyborg - 2018-07-11 | |||
| 14:01:44 | Coco-Gao | Hello | |
| 14:01:51 | zhipeng | #startmeeting openstack-cyborg | |
| 14:01:52 | openstack | 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 | openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | |
| 14:01:57 | openstack | The meeting name has been set to 'openstack_cyborg' | |
| 14:02:03 | zhipeng | #topic Roll Call | |
| 14:02:09 | zhipeng | #info Howard | |
| 14:02:13 | Li_Liu | #info Li_Liu | |
| 14:03:33 | Helloway | #info Helloway | |
| 14:03:45 | shaohe_feng | #info shaohe_feng | |
| 14:03:46 | zhipeng | everyone plz use the #info cmd to sign up | |
| 14:04:03 | wangzhh | #info wangzhh | |
| 14:04:35 | Coco_Gao | #info | |
| 14:04:59 | zhipeng | #info gaojinghua | |
| 14:05:54 | sum12 | #sum12 | |
| 14:06:21 | zhipeng | shaohe_feng will sundar attend ? | |
| 14:06:50 | shaohe_feng | zhipeng, I do not think so | |
| 14:07:00 | zhipeng | on vacation ? | |
| 14:07:00 | shaohe_feng | he is on vocation. | |
| 14:07:02 | shaohe_feng | yes | |
| 14:07:12 | zhipeng | until when ? | |
| 14:07:25 | shaohe_feng | seems \7/25 | |
| 14:08:11 | shaohe_feng | from July 10 night through July 25, coming back on 26th. | |
| 14:08:22 | zhipeng | lol | |
| 14:08:40 | Coco_Gao | long vacation. | |
| 14:08:48 | zhipeng | okey let's get into business | |
| 14:09:00 | zhipeng | #topic Rocky Development Update | |
| 14:09:05 | zhipeng | #link https://review.openstack.org/#/q/status:open+project:openstack/cyborg | |
| 14:09:12 | zhipeng | #topic os-acc design | |
| 14:09:33 | zhipeng | https://review.openstack.org/577438 | |
| 14:09:56 | zhipeng | Li_Liu shaohe_feng is there any consensus converging on the current proposal ? | |
| 14:11:26 | Li_Liu | I don't have any further comments on that one | |
| 14:11:38 | zhipeng | meaning satisfied ? | |
| 14:11:45 | zhipeng | or still waiting for answers | |
| 14:11:47 | shaohe_feng | I really want to know the scope of the os-acc. | |
| 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 ? | |