| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-cyborg - 2020-08-25 | |||
| 02:09:40 | openstackgerrit | wangzhh proposed openstack/cyborg-specs master: Add Attribute API specification. https://review.opendev.org/738331 | |
| 05:55:41 | openstackgerrit | Wenping Song proposed openstack/python-cyborgclient master: Add e.g. for groups when create device profile https://review.opendev.org/747829 | |
| 06:47:39 | openstackgerrit | Brin Zhang proposed openstack/cyborg-specs master: Add Attribute API specification. https://review.opendev.org/738331 | |
| 07:19:47 | openstackgerrit | wangzhh proposed openstack/cyborg-specs master: Add Attribute API specification. https://review.opendev.org/738331 | |
| 07:27:10 | openstackgerrit | wangzhh proposed openstack/cyborg-specs master: Add Attribute API specification. https://review.opendev.org/738331 | |
| 08:28:12 | openstackgerrit | wangzhh proposed openstack/cyborg-specs master: Add Attribute API specification. https://review.opendev.org/738331 | |
| 10:08:41 | openstackgerrit | Brin Zhang proposed openstack/cyborg-specs master: Create soecs directory for Wallaby https://review.opendev.org/747888 | |
| #openstack-cyborg - 2020-08-26 | |||
| 00:38:04 | openstackgerrit | Brin Zhang proposed openstack/cyborg-specs master: Create soecs directory for Wallaby https://review.opendev.org/747888 | |
| 06:47:11 | openstackgerrit | Brin Zhang proposed openstack/cyborg-specs master: Create specs directory for Wallaby https://review.opendev.org/747888 | |
| 07:01:00 | openstackgerrit | Shogo Saito proposed openstack/cyborg master: Programming support (v2 Deployable API) https://review.opendev.org/698190 | |
| 08:09:51 | openstackgerrit | Wenping Song proposed openstack/python-cyborgclient master: Add e.g. for groups when create device profile https://review.opendev.org/747829 | |
| 09:03:06 | openstackgerrit | Merged openstack/python-cyborgclient master: Add e.g. for groups when create device profile https://review.opendev.org/747829 | |
| 12:12:55 | openstackgerrit | Wenping Song proposed openstack/cyborg master: Optimize microversion support https://review.opendev.org/746282 | |
| #openstack-cyborg - 2020-08-27 | |||
| 03:05:25 | Yumeng | hi xinranwang__, s_shogo swp20 brinzhang_ | |
| 03:05:39 | brinzhang_ | hi Yumeng | |
| 03:05:40 | swp20 | hi Yumeng | |
| 03:05:44 | xinranwang__ | Hi all | |
| 03:06:10 | s_shogo | Hi all | |
| 03:06:10 | Yumeng | hi chenke | |
| 03:06:17 | chenke | hi all | |
| 03:06:21 | chenke | hi yumeng. shogo. | |
| 03:06:21 | swp20 | Hi all | |
| 03:06:25 | chenke | hi wenping. | |
| 03:06:47 | chenke | I leave some comments on your patches. | |
| 03:06:56 | swp20 | yeah, i see. | |
| 03:07:02 | Yumeng | s_shogo: I asked haibin to join our meeting today. he will join soon. you guys can discuss Program API things ：） | |
| 03:07:05 | swp20 | thanks chenke. | |
| 03:07:27 | s_shogo | Yumeng great! | |
| 03:07:50 | Yumeng | ok. let's start | |
| 03:07:58 | Yumeng | #startmeeting openstack-cyborg | |
| 03:07:59 | openstack | Meeting started Thu Aug 27 03:07:58 2020 UTC and is due to finish in 60 minutes. The chair is Yumeng. Information about MeetBot at http://wiki.debian.org/MeetBot. | |
| 03:08:00 | openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | |
| 03:08:03 | openstack | The meeting name has been set to 'openstack_cyborg' | |
| 03:08:12 | Yumeng | #topic Roll call | |
| 03:08:16 | Yumeng | #info Yumeng | |
| 03:08:37 | s_shogo | #info s_shogo | |
| 03:08:37 | swp20 | #info swp20 | |
| 03:08:48 | xinranwang__ | #info xinranwang__ | |
| 03:09:16 | brinzhang_ | #info brinzhang_ | |
| 03:10:03 | Yumeng | hi shaohe_feng | |
| 03:10:11 | shaohe_feng | hi all | |
| 03:10:20 | shaohe_feng | hi Yumeng, morning | |
| 03:11:35 | Yumeng | cool, we have so many people today | |
| 03:11:40 | brinzhang_ | Hi all, we should have a aggrement of the tempary report result of the 3rd-party driver | |
| 03:11:47 | Yumeng | #topic Agenda | |
| 03:12:12 | brinzhang_ | where to save the tempart results | |
| 03:12:12 | Yumeng | brinzhang_: yes, that's one of the topic I want to mention | |
| 03:12:21 | brinzhang_ | yeah ^^ | |
| 03:14:05 | Yumeng | as discussed in Intel QAT driver patch: https://review.opendev.org/#/c/725821/7//COMMIT_MSG | |
| 03:14:10 | brinzhang_ | I am ok with the qat driver patch, and the inspur fpga driver patch, just with the temparory reulst | |
| 03:14:53 | xinranwang__ | do we have a template wiki to show test result? | |
| 03:15:52 | brinzhang_ | xinranwant_: may we should have to create a tempate for this | |
| 03:16:42 | brinzhang_ | the etherpad is not save, because it can be modified by everyone | |
| 03:16:50 | xinranwang__ | IMO, the format of test result is not a big deal. Just to show the driver works. | |
| 03:16:56 | brinzhang_ | s/save/safe | |
| 03:17:42 | chenke | #info chenke | |
| 03:18:22 | swp20 | xinranwang__: your format of test result is good enough. | |
| 03:18:48 | brinzhang_ | xinranwang_: not exactly all, we shoul keep the readable of the result, so the format shuold be beautiful ASAP | |
| 03:19:11 | Yumeng | xinranwang__: about the template, I'm fine with the structure of your report. I think that make sense to showt the report results and provision results | |
| 03:19:33 | xinranwang__ | I remember it was a website call paste.openstack.org, things like that. | |
| 03:19:44 | Yumeng | xinranwang__: just one small question, we can add openstack accelerator device list to show the report result in cyborg side. | |
| 03:19:47 | xinranwang__ | does anyone know that website> | |
| 03:20:11 | brinzhang_ | xinranwang_: paste.openstack.org is also a temparory place too | |
| 03:21:02 | brinzhang_ | I am trend to use wiki | |
| 03:21:09 | xinranwang__ | brinzhang_: does everyone can modify it? | |
| 03:21:19 | xinranwang__ | Yumeng: ok, sure | |
| 03:21:19 | Yumeng | brinzhang_, xinranwang__: I also have the concern that etherpad and paste.openstack.org are temparory. anyobe can modify it | |
| 03:22:15 | brinzhang_ | xinranwang_: no, but it will be lost with a long time | |
| 03:22:31 | xinranwang__ | brinzhang_: ok, got it. | |
| 03:22:59 | Yumeng | we can create a wiki page to record the driver report result and then add the link to the driver-support table on doc page https://docs.openstack.org/cyborg/latest/reference/support-matrix.html#driver-support | |
| 03:23:00 | xinranwang__ | It seems a wiki page is the better one | |
| 03:23:05 | brinzhang_ | we can use wiki, but how do we let the user or operator know the result exist in wiki? | |
| 03:23:05 | Yumeng | what do you think? | |
| 03:23:37 | xinranwang__ | We can mention this wiki page in cyborg doc | |
| 03:24:50 | brinzhang_ | agree, and we can add a column as "temparory result", marked when it merged | |
| 03:24:58 | shaohe_feng | the https://docs.openstack.org/cyborg/latest/reference/support-matrix.html#driver-support should add item to show the link | |
| 03:25:05 | shaohe_feng | yes | |
| 03:25:11 | Yumeng | yes, agree | |
| 03:25:44 | brinzhang_ | such as, Added it in Victoria (Auguest, 2020) | |
| 03:26:06 | Yumeng | yes, we can do that. | |
| 03:26:11 | brinzhang_ | and past the wiki test result link | |
| 03:26:16 | xinranwang__ | lol, like a biography for the driver | |
| 03:27:13 | Yumeng | yep =_< | |
| 03:27:23 | brinzhang_ | ok, let do it by this way, after meeting, I will send an email to the ML, that everyone should do, if they are not have the third-party CI | |
| 03:27:33 | swp20 | aggree | |
| 03:28:00 | Yumeng | brinzhang_: cool. | |
| 03:28:46 | Yumeng | about the driver implementation, I have another quesion to discuss | |
| 03:29:02 | Yumeng | VENDOR_MAPS format of GPU,FPGA are different, should we keep consistent? | |
| 03:29:30 | Yumeng | FPGA is like this https://github.com/openstack/cyborg/blob/master/cyborg/accelerator/drivers/fpga/base.py#L23 | |
| 03:29:45 | Yumeng | while GPU is like https://github.com/openstack/cyborg/blob/master/cyborg/accelerator/drivers/gpu/base.py#L26 | |
| 03:30:38 | swp20 | we can merge them in one dict. | |
| 03:31:04 | brinzhang_ | move this to a common file? | |
| 03:32:18 | xinranwang__ | Yumeng: what do you mean by difference | |
| 03:32:22 | brinzhang_ | VENDER_MAPS = ['GPU': {'0x8086': 'intel', ..}, 'FPGA': {'','', ...}] | |
| 03:32:46 | brinzhang_ | how about like this? that we can maintain this in one place | |
| 03:34:06 | xinranwang__ | Just wondering why we should do this. Is there any gap in current implementation? | |
| 03:34:40 | brinzhang_ | not array, a dict. VENDER_MAPS = {'GPU': {'0x8086': 'intel', ..}, 'FPGA': {'','', ...}} | |
| 03:36:27 | brinzhang_ | xinranwang_: I am not sure what Yumeng want todo, but from the maintain accelerator devices type and vendor, that we can merge this, because we can easy to know what devices that we can support | |
| 03:37:28 | brinzhang_ | but as you said, is it make sense? It make sense to me. ^ | |
| 03:38:00 | Yumeng | xinranwang__: initially, this is a downstream problem I found in baremetal support. ironic report Nvidia GPU vendor_id as hexadecimal int, while we accept vendor_id as string | |