| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-cyborg - 2018-07-30 | |||
| 14:35:15 | xinran__ | jiangguocai: plz feel fee to let us know if you wanna ask something about placement | |
| 14:35:24 | xinran__ | #info xinran__ | |
| 14:35:40 | jiangguocai | shaohe_feng: l reviewed your code about placement client. but not called in other code | |
| 14:35:56 | LI_Liu | #info Li Liu | |
| 14:36:46 | wangzhh | Hi, xinran__, PLZ look at the comment in line. I have the same question. | |
| 14:36:56 | Sundar | Li_Liu: The PF/VF stored in the DB will be a different object than the OVO exchanged between drivers/agent for PF/VF. The latter is exposed, the former is Cyborg-internal. | |
| 14:37:04 | jiangguocai | shaohe_feng: do you want to design it for a service？ | |
| 14:37:21 | edleafe | #info Ed Leafe | |
| 14:37:28 | shaohe_feng | jiangguocai, no, it just a lib | |
| 14:37:30 | wangzhh | Welcome! | |
| 14:37:35 | shaohe_feng | morning efried | |
| 14:37:54 | efried | shaohe_feng: ō/ | |
| 14:38:07 | LI_Liu | Sundar: Thank you for the clearification | |
| 14:38:07 | Coco | what's the topic now? can't catch much of your discussion. | |
| 14:38:08 | efried | We having a meeting? | |
| 14:38:31 | xinran__ | wangzhh: which comment? Sorry, I just lost the connection... | |
| 14:39:27 | wangzhh | https://review.openstack.org/#/c/585146/ | |
| 14:39:35 | shaohe_feng | edleafe, we have add many amazing features theses days, os-acc, cyborg-client. will be ready for the interaction with nova in next release. | |
| 14:39:36 | wangzhh | Here. | |
| 14:39:55 | shaohe_feng | edleafe, and we need your help on nova side. :) | |
| 14:39:58 | Sundar | efried: yes, this is the Cyborg drivers meeting, which happens Mondays 7 am PDT. | |
| 14:40:34 | edleafe | shaohe_feng: My involvement with the Nova project has been greatly reduced. You will probably have more success with efried | |
| 14:40:52 | xinran__ | wangzhh: let me have a look | |
| 14:41:26 | shaohe_feng | edleafe, ok, thanks. | |
| 14:42:04 | shaohe_feng | Sundar, have talked with efried on nova interaction? | |
| 14:42:44 | Sundar | shaohe: the entire os-acc spec discussion is an extended conversation with efried :) | |
| 14:43:05 | shaohe_feng | these days we are so busy, sorry for the delay. | |
| 14:44:28 | shaohe_feng | but any one wants to learn more about how placement work during the cyborg/nova interaction. can discuss with xinran__ | |
| 14:44:54 | Sundar | shaohe: NP. | |
| 14:45:01 | Sundar | efried: Saw your reply in the spec. I can explain the Cyborg driver model. Would you be available at 9 am PDT? | |
| 14:45:02 | LI_Liu | I have to drop guys. Have a good night/day | |
| 14:45:26 | shaohe_feng | LI_Liu, have a good day. Bye. | |
| 14:45:35 | wangzhh | Bye, Uncle li. | |
| 14:45:49 | efried | Sundar: I.e. 1:15 from now? Yes, wfm. | |
| 14:46:22 | shaohe_feng | Coco, you miss the refacor of driver return data. Sundar suggested to use his VANs model. You can discuss it with him about more details. | |
| 14:46:28 | jiangguocai | shaohe_feng: for driver to call？can you take a simple for us, thanks | |
| 14:46:56 | shaohe_feng | jiangguocai, yes. will come out soon. | |
| 14:47:03 | Sundar | Great, efried. I'll catch you on #openstack-nova | |
| 14:47:15 | efried | Sundar: Here is probably more appropriate. | |
| 14:47:28 | efried | unless it will interrupt something else. | |
| 14:47:38 | xinran__ | wangzhh: you mean how cyborg report the resource to placement? | |
| 14:47:48 | shaohe_feng | jiangguocai, can you discribe your drivers? Let me give you a solution. | |
| 14:47:50 | shaohe_feng | here. | |
| 14:48:03 | Coco | OK, I will talk with Sundar about more details of the VANs model. | |
| 14:48:49 | wangzhh | xinran__, Yes. I want to know the data structure and how we call it. | |
| 14:49:40 | shaohe_feng | welcome jiapei | |
| 14:50:19 | jiapei | hey, morning Shaohe | |
| 14:50:33 | shaohe_feng | wangzhh, do you just pass the physical GPU to VM? | |
| 14:50:44 | shaohe_feng | nvdia? | |
| 14:50:47 | wangzhh | Yes。 | |
| 14:51:38 | shaohe_feng | One card is one GPU? | |
| 14:52:06 | wangzhh | Yes. No share mode now. | |
| 14:52:21 | xinran__ | wangzhh: you can check the provider_report in resource_tracker.py | |
| 14:54:32 | xinran__ | wangzhh: oh sorry these code is not in this patch | |
| 14:54:56 | xinran__ | wangzhh: let me check and tell you after meeting | |
| 14:55:06 | shaohe_feng | wangzhh, that's a not a complex use case. | |
| 14:55:09 | wangzhh | OK. | |
| 14:55:22 | shaohe_feng | next topic: | |
| 14:56:02 | shaohe_feng | #topic Traits and attribution format. | |
| 14:57:08 | shaohe_feng | maybe Coco and Sundar should pay a attention on this . | |
| 14:57:40 | Sundar | I need to drop off in 3 min. What is this topic about? | |
| 14:57:55 | shaohe_feng | if we want to the cyborg pick up the expect accelerators | |
| 14:58:24 | shaohe_feng | we should have enough info in the attribution of deployable . | |
| 14:59:06 | shaohe_feng | and driver return dates should report them. | |
| 14:59:40 | shaohe_feng | so we should add a new fields for the return VANs model? | |
| 15:00:46 | shaohe_feng | and if we want to scheduler pick up the right host. we should also report the correct traits. | |
| 15:00:59 | Sundar | Not sure I follow. The Cyborg drivers return enough data for the agent to create traits and RPs for that device | |
| 15:01:15 | shaohe_feng | Sundar, yes. | |
| 15:01:22 | Sundar | Anyways, I'll catch up on this. Please start an email thread on this | |
| 15:01:26 | xinran__ | wangzhh: device name, rc, trait, total number, these should be passed to placement by calling placement client | |
| 15:01:45 | Sundar | Bye for now. | |
| 15:01:51 | shaohe_feng | So who will report these infos? | |
| 15:02:55 | jiangguocai | shaohe_feng: Ok，I pushed hpts driver tonight，with review 587994. I need to add 'Custom_accelelerator_hpts' and Tairst，acc resource number to novi， can you give me some suggest. | |
| 15:02:56 | wangzhh | OK, xinran__, when will you commit the patch about it? | |
| 15:03:39 | xinran__ | Tmr morning | |
| 15:04:22 | wangzhh | Good! Thx. | |
| 15:04:31 | shaohe_feng | So let's please make our own tasks go well. | |
| 15:04:33 | xinran__ | :) | |
| 15:04:54 | shaohe_feng | #topic AoB | |
| 15:05:10 | shaohe_feng | ^ jiangguocai, wangzhh, Coco | |
| 15:05:28 | Coco | shaohe_feng, ? | |
| 15:05:54 | shaohe_feng | any things else want to talk? | |
| 15:06:15 | wangzhh | Nothing. | |
| 15:06:29 | shaohe_feng | OK, if no let's end the meeting. | |
| 15:06:39 | shaohe_feng | have a good night, every one. | |
| 15:06:42 | shaohe_feng | Bye. | |
| 15:06:46 | wangzhh | Bye, everyone. | |
| 15:06:59 | shaohe_feng | #endmeeting | |
| 15:07:02 | openstack | Meeting ended Mon Jul 30 15:06:59 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | |
| 15:07:03 | openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack_cyborg_driver/2018/openstack_cyborg_driver.2018-07-30-14.00.html | |
| 15:07:04 | openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_cyborg_driver/2018/openstack_cyborg_driver.2018-07-30-14.00.txt | |
| 15:07:05 | openstack | Log: http://eavesdrop.openstack.org/meetings/openstack_cyborg_driver/2018/openstack_cyborg_driver.2018-07-30-14.00.log.html | |
| 16:25:15 | Sundar_ | Hello | |
| 16:25:41 | efried | What I'd like to understand a bit more about, though, is what's a driver vs. a plugin? | |
| 16:25:41 | efried | Seems like we've come to an agreement on most of the high points in the spec. If we just fix those up, I'll be happy with it. As I've said, I think a lot of the details will shake out in the implementation. | |
| 16:25:41 | efried | Hi Sundar_. | |
| 16:25:49 | efried | What are their respective responsibilities and roles? | |
| 16:26:46 | Sundar_ | Ah, good question. When you first proposed a plugin, I thought you knew about Cyborg drivers already, and still wanted another mechanism. Anyways, here's how I look at it ... | |
| 16:28:10 | Sundar_ | Both plugins and drivers represent ways to handle vendor/device/hypervisor/architecture-specific aspects that should not be in core Cyborg or os-acc. | |
| 16:29:23 | Sundar_ | There are two ways that os-acc can interact with Cyborg. (a) Leave most of the work to Cyborg: then the drivers are the main extensibility mechanism. (b) Leave only device-specific aspects to Cyborg and hypervisor and other aspects to the plugin. | |