| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-cyborg - 2018-05-14 | |||
| 14:40:32 | Li_Liu | yes, agree | |
| 14:40:41 | shaohe_feng | agree. | |
| 14:41:23 | shaohe_feng | Helloway: are you here? | |
| 14:42:06 | Helloway | yes] | |
| 14:42:31 | shaohe_feng | you have contributed a spdk driver. | |
| 14:42:42 | shaohe_feng | can you give us some introduce about it. | |
| 14:45:31 | shaohe_feng | ^ Helloway: | |
| 14:45:36 | Helloway | spdk driver can help cyborg to discovery the resources about spdk_based app(like nvmf_tgt, iscsi_target) | |
| 14:46:06 | sundar_ | helloway: Is there any specific hardware for this? | |
| 14:46:40 | shaohe_feng | Does it need a REST API? | |
| 14:47:03 | Helloway | include the nvme device and subsystems..and more | |
| 14:49:00 | sundar_ | helloway: So, is the expectation that Cyborg will discover the NVMe device as a PCIe device, and publish its properties as traits in Nova? | |
| 14:51:19 | Helloway | currently It does not have rest api? | |
| 14:51:32 | Helloway | currently It does not have rest api. | |
| 14:52:10 | shaohe_feng | will it report NVME device to placement? | |
| 14:53:39 | Helloway | sundar: not local pcie device, maybe it is more like nvme over fabric | |
| 14:53:40 | sundar_ | My understanding is, SPDK drivers are bit like DPDK poll mode drivers that run in user space. Something else needs to discover the PCI device. Helloway, please confirm if what you have is a user mode SPDK driver | |
| 14:55:08 | jiapei | I guess Helloway means something over fabric, through REST API | |
| 14:55:35 | jiapei | I'm also interested in this | |
| 14:56:08 | sundar_ | jiapei: I thought helloway said earlier that there is no REST API for this. | |
| 14:56:40 | sundar_ | Helloway: Appreciate if you can give us a writeup with some description of what you have and what you want | |
| 14:58:44 | shaohe_feng | let start next topic? | |
| 14:59:11 | sundar_ | What is the conclusion on SPDK and NVMe -- is it in plan for Rocky? | |
| 14:59:38 | shaohe_feng | #action improvement on driver | |
| 14:59:54 | shaohe_feng | Helloway: any play for Rocky? | |
| 15:00:32 | Helloway | ok, sorry I type slowly. I will write something for you guys through the email | |
| 15:00:46 | sundar_ | I need to join my next call. I'll try to keep an eye on this page. | |
| 15:00:52 | Helloway | ok? | |
| 15:01:09 | shaohe_feng | Helloway: good, thanks. | |
| 15:01:31 | shaohe_feng | sundar_: OK. | |
| 15:01:35 | Helloway | thanks :) | |
| 15:01:49 | wangzhh | Helloway: Thanks. | |
| 15:02:47 | shaohe_feng | now we will support more and more drivers. maybe we need a schema check for different drivers's report info. | |
| 15:03:55 | shaohe_feng | And currently we lookup the cyborg specific module path for multi-driver. | |
| 15:04:20 | shaohe_feng | should we change it to entry points? | |
| 15:05:04 | shaohe_feng | and another improvement for the current drivers? | |
| 15:06:19 | shaohe_feng | Li_Liu: oh, we should leverage your new pf/vf implementation to report accelerators info to conductor. | |
| 15:06:48 | Li_Liu | yes | |
| 15:07:20 | Li_Liu | It should be ready to use | |
| 15:07:40 | shaohe_feng | Good. Let's start to change it. | |
| 15:07:55 | shaohe_feng | Ok, next topic. | |
| 15:08:32 | shaohe_feng | #topic code review | |
| 15:08:34 | shaohe_feng | Pending patch: https://review.openstack.org/#/q/status:open+project:openstack/cyborg | |
| 15:12:04 | shaohe_feng_ | AoB? | |
| 15:12:17 | shaohe_feng_ | something wrong with my network? | |
| 15:12:40 | shaohe_feng_ | I rejoin | |
| 15:14:28 | shaohe_feng_ | okey meeting adjourned | |
| 15:14:51 | shaohe_feng_ | #endmeeting | |
| 15:14:54 | openstack | Meeting ended Mon May 14 15:14:51 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | |
| 15:14:55 | openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack_cyborg_driver/2018/openstack_cyborg_driver.2018-05-14-14.01.html | |
| 15:14:56 | openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_cyborg_driver/2018/openstack_cyborg_driver.2018-05-14-14.01.txt | |
| 15:14:57 | openstack | Log: http://eavesdrop.openstack.org/meetings/openstack_cyborg_driver/2018/openstack_cyborg_driver.2018-05-14-14.01.log.html | |
| 15:15:25 | shaohe_feng_ | have a good night, Chinese guys. | |
| 15:15:46 | shaohe_feng_ | And have good day, Li_Liu, sundar_ and rorojo | |
| 15:16:18 | Helloway | good night, everyone | |
| 15:16:44 | Li_Liu | good night guys | |
| 19:18:30 | ildikov | Li_Liu: hi | |
| #openstack-cyborg - 2018-05-15 | |||
| 12:03:46 | NokMikeR | Hi, after installing devstack + cyborg - so the cyborg accelerator service is shown in the api list (via horizon) - how do you interact with cyborg? is there any cli commands available or how can we make a basic fake accelerator to test it? | |
| 12:06:48 | zhipengh[m] | shaohe_: is working on the client | |
| 12:35:58 | NokMikeR | is there any basic curl + api command to test it or how do you interact with the actual driver level features? | |
| 12:36:44 | zhipengh[m] | Yes there is curl available | |
| 13:23:37 | NokMikeR | is there any documentation available showing how to interact with cyborg using curl, or the api directly? | |
| #openstack-cyborg - 2018-05-16 | |||
| 09:23:11 | openstackgerrit | ShaoHe Feng proposed openstack/python-cyborgclient master: base framework for cyborg client. https://review.openstack.org/565023 | |
| 09:30:37 | openstackgerrit | ShaoHe Feng proposed openstack/cyborg master: change service type to "accelerator" https://review.openstack.org/568799 | |
| 09:31:39 | shaohe_feng | hi all, I have change service type to accelerator | |
| 10:18:32 | NokMikeR | is there a test cli available to use cyborg via the "openstack" command? | |
| 10:29:13 | zhipengh[m] | NokMikeR: wait for shaohe_feng 's upcoming patch :) | |
| 12:55:42 | NokMikeR | do you have anything that shows the curl for authenticating and sending a command to cyborg? looking at the base.py unit testing code theres some hard coded fields - I mean should I really look at the code, reverse engineer that to figure out how to use it? | |
| 12:56:39 | zhipengh[m] | NokMikeR_: let me try to find the example we had | |
| 12:56:50 | NokMikeR | thank you | |
| 13:54:05 | shaohe_feng | NokMikeR, TOKEN=`openstack token issue -f value -c id` | |
| 13:54:21 | shaohe_feng | curl -i -X GET -H "X-Auth-Token: $TOKEN" http://localhost:6666/accelerators | |
| 14:00:45 | zhipeng | #startmeeting openstack-cyborg | |
| 14:00:46 | openstack | Meeting started Wed May 16 14:00:45 2018 UTC and is due to finish in 60 minutes. The chair is zhipeng. Information about MeetBot at http://wiki.debian.org/MeetBot. | |
| 14:00:47 | openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | |
| 14:00:49 | openstack | The meeting name has been set to 'openstack_cyborg' | |
| 14:00:57 | zhipeng | #topic roll call | |
| 14:01:02 | Li_Liu | #info Li_Liu | |
| 14:01:03 | zhipeng | #info Howard | |
| 14:01:18 | shaohe_feng | #shaohe_feng | |
| 14:01:31 | Sundar | #info Sundar | |
| 14:01:40 | shaohe_feng | #info shaohe_feng | |
| 14:02:09 | zhipeng | let's wait for another 4 mins for other people show up :) | |
| 14:02:16 | Helloway | #info Helloway | |
| 14:02:17 | sum12 | info sum12 | |
| 14:02:21 | sum12 | #info sum12 | |
| 14:04:10 | edleafe | #info Ed Leafe | |
| 14:06:48 | xinran__ | Hi all | |
| 14:07:00 | zhipeng | hi xinran__ :) | |
| 14:07:05 | xinran__ | #info xinran__ | |
| 14:07:06 | zhipeng | let's get started | |
| 14:07:25 | zhipeng | #topic summit prep | |
| 14:07:41 | zhipeng | first of all, I want to confirm Sundar's core nomination | |
| 14:07:54 | zhipeng | we don't have any objections, right ? | |
| 14:08:56 | zhipeng | okey than congrats Sundar :) | |
| 14:09:24 | Sundar | Thanks, zhipeng! | |
| 14:09:27 | xinran__ | Congratulations | |
| 14:09:44 | sum12 | \o/ congratulations | |
| 14:10:03 | Li_Liu | congratz | |
| 14:10:10 | shaohe_feng | Congratz | |