Earlier  
Posted Nick Remark
#openstack-cyborg - 2019-10-17
03:34:36 Sundar We could. We need to talk about it. Right now, we got some drivers for GPU and Ascend. However, the maintainers are not regularly participating in Cyborg activities. That makes me concerned about maintenance. Also, we don;t have 3rd party CI for any driver yet. We are planning that for FPGAs, but what about other drivers?
03:35:01 Sundar I was replying about drivers, not PF
03:35:27 shaohe_feng so the questions is that.
03:35:43 shaohe_feng If a end user apply a FPGA
03:35:43 Sundar As a team, we may have to decide on a higher bar for drivers. That is something we can discuss here on at the PTG.
03:35:45 Sundar *or
03:35:56 shaohe_feng I will not attend PTG.
03:36:29 Sundar Ah yes, too bad. You can give your ideas here or in the PTG etherpad.
03:36:30 shaohe_feng if he found there's bug on his bitstream?
03:36:50 shaohe_feng what should he do?
03:37:06 shaohe_feng delete the VM, rebuild a new VM with a FPGA?
03:37:14 Sundar Passing a FPGA PF to a VM is potential security hole, because we don;t know what bitstreams get programmed
03:37:14 s_shogo Wow, it's so good > CI for FPGA driver's.
03:37:22 shaohe_feng or just re-program it?
03:38:21 Sundar We have a usage model called Runtime Programming, which we don't support today. It involves VM issuing requests for new bitstreams, Cyborg or something receives that request and does the reprogramming. We don;t see many customers asking for that
03:38:42 shaohe_feng maybe, the end user after doing his AI, then he want to change the AI model, which means he maybe need a new bitstream for his AI net model.
03:38:48 shaohe_feng what should he do?
03:39:16 xinranwang I think we can provider a program interface for this kind of users.
03:39:25 xinranwang in vf use case.
03:39:44 Sundar He could get the VM to issue a request somehow to underlying infra. That is not there today. Today, he only needs to stop that VM and start a new one
03:40:13 Sundar xinranwang: User cannot reprogram a FPGA via VF.
03:40:59 shaohe_feng yes, but he take a great effort to setup his AI env, such as install the openvino and the dependency, set connection with the camera maybe.
03:41:07 xinranwang if boot with bit-stream failed, vm should become failed. if user boot a vm successfully, and want reprogram the FPGA, what will we do.
03:41:27 shaohe_feng so should should delete vm, rebuild one, and take effort to setup the env again?
03:42:58 shaohe_feng Seams now, the user just can use FPGA as fix function PCI devices once he create the VM
03:43:29 Sundar If there is a strong customer demand for that, have that customer(s) call Intel. This use case will require changes in the product level, software stack and in Cyborg. It will also require discussion among ourselves in Cyborg community.
03:44:21 shaohe_feng I did not seen the flexible advantage of FPGA.
03:44:44 xinranwang hat is a problem.
03:44:52 xinranwang * That
03:45:09 Sundar There are different usage models of FPGA. Many customers are adopting it with the current software stack.
03:45:21 Sundar Perhaps we can take this offline, rather than hold everybody up.
03:45:22 shaohe_feng the question is that, cyborg is not adopt in a product at present. So we miss so many customer demand for end user.
03:45:23 xinranwang IMHO, Cyborg should support reprogram right?
03:45:53 Sundar xinranwang: It should and it does today (at least will after Nova integ).
03:46:59 xinranwang Sundar: Yes, so I think it is doable for user who want update their bitstream.
03:47:28 shaohe_feng so I should tell the user who wants to try cyborg, that we will not support reprogram, right?
03:48:29 s_shogo In my case,the current PAC seems to have some constraints (ex necessary for disabling SR-IOV when programming) and that is problem for reprogram in our usecase.
03:48:32 Sundar shaohe_feng: Why do you say that? We can reprogram when a VM is being launched. We cannot reprogram after a VM is launched. Most users today need only the former, from what we have seen.
03:48:36 s_shogo I would like to discuss these constraints are temporary or not, and cyborg( and user ) should think them as premise or not,in PTG and so on.
03:49:25 Sundar s_shogo: Sure, I;ll add usage models as a topic at the PTG, and come with some slides explaining our thoughts/plans.
03:49:48 s_shogo Great, thanks > Sundar
03:49:55 shaohe_feng Sundar, just think you want to do a AI with FPGA. you want to try you different model to find the best solution, what you should do?
03:50:30 shaohe_feng You can can add the reprogram in the etherpad list.
03:50:58 shaohe_feng and involve more end users to discuss it during PTG.
03:51:05 Sundar General question to all: s_shogo, chenke, Yumeng, shaohe_feng, xinranwang: Are you interested in FPGAs with networking? Adding that will require further discussion. We started that at the beginning of Train, but didn't follow u.
03:51:26 Sundar s/u./up./
03:52:03 Sundar It will require Cyborg-Neutron interaction. I have some ideas for that, but they haven't been discussed deeply with neutron community yet.
03:52:30 xinranwang s_shogo: Could you list the constraints you met in etherpad?
03:53:10 s_shogo I have great interest in networking with FPGA, as a telco-carrier. ut there is not clear demand for interaction with neutron.
03:53:23 s_shogo s/ut/but/
03:54:19 shaohe_feng I have looked into OVS card base FPGA before.
03:54:21 s_shogo xinranwang: ok, I'll list the constraints in etherpad, it may include misunderstanding, pointing out is welcome and happy for me :)
03:54:28 shaohe_feng it can works with DPDK.
03:54:28 Sundar s_shogo: The question is, does the networking solution require basic resources like MAC/IP addresses, and more advanced things like security groups and VXLAN config? These things are best left to neutron, rather than Cyborg replicating them.
03:55:39 xinranwang s_shogo: thanks, I am willing to see it. We can check if we also met them :P
03:56:47 Sundar OK, anything else for today?
03:57:45 Yumeng Sundar: Yes, I have intrests in smart NICs network adapter base FPGA, things like that.
03:57:53 Yumeng nothing else. thanks!
03:58:07 Sundar Great. Glad to hear the widespread interest.
03:58:27 s_shogo The current application in networking in FPGA is limited, so these parameters could be applied via application or operation.
03:59:19 Sundar s_shogo and Yumeng: For my interest, are you more interested in OVS offload or in offloading apps like vRAN or vEPC?
04:00:31 s_shogo Sundar: Yes, I have interested in them. These performance is critical for telco-carrier.
04:01:20 Sundar SO, you are interested in both types?
04:01:55 Sundar OCS offload is quite different architecturally from application offload
04:01:58 Sundar *OVS
04:02:13 Sundar The former is from the host, latter from VM.
04:02:22 Sundar Cyborg has to do different things for both
04:02:43 shaohe_feng We have a OVS offload card.
04:04:20 shaohe_feng can do some scenarios on it.
04:04:50 Sundar Anyway, we are past the time. We can cover this in next meeting.
04:04:56 Sundar Thanks, everybody! Have a good day. :)
04:05:02 shaohe_feng bye
04:05:07 Sundar #topic endmeeting
04:05:10 chenke bye.
04:05:16 xinranwang bye
04:05:19 Yumeng bye
04:05:46 s_shogo bye
04:55:30 s_shogo The last message was failed to send...
04:58:17 s_shogo I think there are several patterns in connecting OVS-accelerator (direct virtio, SR-IOV+DPDK, using tc flower,etc), and that effects cyborg and driver's operation.
04:58:46 s_shogo Anyway , I would like to discuss them in next chance:)
#openstack-cyborg - 2019-10-19
09:07:03 openstackgerrit chenker proposed openstack/cyborg master: Fix attach_handle status error when creating vm successfully https://review.opendev.org/689617
#openstack-cyborg - 2019-10-21
01:17:21 openstackgerrit chenker proposed openstack/cyborg master: Fix attach_handle status error when creating vm successfully https://review.opendev.org/689617
14:22:20 openstackgerrit chenker proposed openstack/cyborg master: Fix attach_handle status error when creating vm successfully https://review.opendev.org/689617
14:38:07 openstackgerrit chenker proposed openstack/cyborg master: Fix attach_handle status error when creating vm successfully https://review.opendev.org/689617
#openstack-cyborg - 2019-10-22
04:11:02 openstackgerrit kangyufei proposed openstack/cyborg master: Switch to Ussuri jobs https://review.opendev.org/689924
05:49:36 openstackgerrit kangyufei proposed openstack/python-cyborgclient master: Switch to Ussuri jobs https://review.opendev.org/689940
08:29:54 openstackgerrit Merged openstack/cyborg master: Fix attach_handle status error when creating vm successfully https://review.opendev.org/689617
#openstack-cyborg - 2019-10-23
08:24:36 openstackgerrit chenker proposed openstack/cyborg master: Remove useless glance api_servers define https://review.opendev.org/685542
08:24:36 openstackgerrit chenker proposed openstack/cyborg master: Simplify devstack script for generating cyborg.conf https://review.opendev.org/690509
08:26:50 openstackgerrit chenker proposed openstack/cyborg master: Simplify devstack script for generating cyborg.conf https://review.opendev.org/690509
08:50:12 openstackgerrit chenker proposed openstack/cyborg master: Update docstring for apply_patch https://review.opendev.org/690517
10:29:15 openstackgerrit YumengBao proposed openstack/cyborg master: Update api-ref: deprecate v1 add v2 device_profile section https://review.opendev.org/690539
#openstack-cyborg - 2019-10-24
02:53:34 openstackgerrit YumengBao proposed openstack/cyborg master: Update api-ref: deprecate v1 add v2 device_profile section https://review.opendev.org/690539
03:01:54 Sundar #startmeeting openstack-cyborg
03:01:55 openstack Sundar: Error: Can't start another meeting, one is in progress. Use #endmeeting first.
03:02:02 Sundar #endmeeting
03:02:04 openstack Meeting ended Thu Oct 24 03:02:02 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
03:02:05 openstack Minutes: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2019/openstack_cyborg.2019-10-17-03.01.html
03:02:06 openstack Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_cyborg/2019/openstack_cyborg.2019-10-17-03.01.txt
03:02:07 openstack Log: http://eavesdrop.openstack.org/meetings/openstack_cyborg/2019/openstack_cyborg.2019-10-17-03.01.log.html

Earlier   Later