03:00:48 #startmeeting openstack-cyborg 03:00:49 Meeting started Wed Apr 24 03:00:48 2019 UTC and is due to finish in 60 minutes. The chair is Sundar. Information about MeetBot at http://wiki.debian.org/MeetBot. 03:00:50 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 03:00:52 The meeting name has been set to 'openstack_cyborg' 03:00:55 #info Coco_gao 03:01:04 #info Li_Liu 03:01:04 #info Sundar 03:01:13 #info yikun 03:01:40 Good to have many of us right at the beginning 03:02:23 Agenda: PTG session time allocation, Summit project update slides 03:02:27 Anything else? 03:03:08 Have we decided the team dinner date yet? 03:03:39 It is Thu evening. But we haven't decided a place yet. I'll leave that to all of you 03:04:00 ok 03:04:08 2th May, right? 03:04:21 yikun: Yes 03:04:26 Sundar: ok 03:04:30 OK, maybe we can keep the old place. 03:04:33 #topic PTG session planning 03:05:20 We have 3.5 hours on Thu afternoon (1:30-5) and 2.5 hours on Fri afternoon (1:30-4) because I need to leave by 4 to catch my flight 03:05:33 Not much time! We need to plan the sessions tightly 03:05:48 You can all continue on Fri eve and on Sat too, when I am gone 03:06:48 BTW, Fri morn are the cross-projects with Nova and ironic 03:06:52 #info wangzhh 03:07:25 Shall we start allocating times to the topics in Looking at: https://etherpad.openstack.org/p/cyborg-ptg-train ? 03:07:51 s/Looking at// 03:08:01 Hi all 03:08:07 xinranwang: hi 03:08:16 Hi xinranwang, wangzhh and Yumeng 03:08:28 #info xinranwang 03:08:42 hi Sundar yikun 03:08:45 Hi Sundar, and all 03:08:50 # info Yumeng 03:09:00 Hi Sundar, hi all. 03:09:04 Retrospective: keep it to 10 min? 03:09:51 Too short? 03:10:16 Sundar: I think we should classify these topic in etherpad, such as, driver, api, common/design...and then do the allocation tiems 03:10:27 * times 03:11:11 10min if no other people join, because we all familar with the project status. 03:11:26 Sundar, agree with yikun 03:11:38 yikun: ok. The main topics in my mind are: Train Goals, Networked FPGAs, mapping names to UUIDs, new drivers/devices (incl. Ascend) 03:11:39 Better to classify 03:12:15 Yikun, do you need more time for topic #line 58? 03:12:16 Some of them are cross-cutting across these categories, esp. first 2 03:12:52 wangzhh: checking... 03:13:56 wangzhh: bitstream management? So what's the "more time" mean? you mean the more time to discuss in PTG? 03:14:42 Yep, I saw you leave comment 'expand the bitstream to more generic level'. So... 03:14:50 yikun, all: In my mind, bitstream mgmt means Cyborg provides APIs to parse metadata for bitstreams, validate and upload in Glance. What else do you have in mind? 03:15:37 I think firmware update etc. are usually done as part of host config, with pupper/ansible/... 03:15:54 *puppet 03:16:12 wangzhh: ok, make sense, it is just some idea for "Do not provide specific API for specific type driver." 03:16:49 Got it. 03:16:51 Sundar: I'm thinking bitstream md5 checksum to check integrity. 03:16:55 I thought there were a generic Driver in code, but we don't use that or inherit from that. 03:17:51 ikuo_o: That is up to the vendor stack, because they may use different checksums, authentication/decryption schemes, or even do it in hardware in some cases 03:18:13 About the bug, do we need specific time for that? 03:18:14 Coco, Yep, but, actually, it is out of date. Should be improved as our new design. 03:18:22 Coco_gao: yes, https://github.com/openstack/cyborg/blob/master/cyborg/accelerator/drivers/generic_driver.py 03:18:49 Thanks, yikun. The generic driver is too old. 03:18:55 Have you all looked at the driver API in Line 396 https://review.opendev.org/#/c/608624/4/specs/stein/approved/cyborg-api-wflows-for-instance-ops.rst ? The can_handle API can be dropped but can you review the rest? 03:20:07 So these APIs is belong to the generic_driver.py? 03:20:55 Anyways, I'll take a first stab like this: 30 min each for Train Goals, Networked FPGAs, mapping names to UUIDs, new drivers/devices, NTT's discussion. That is 2.5 hours. Now we can add more time to some of these topics and fit more on Friday 03:20:56 Sundar, OK 03:21:32 Sundar: sounds good 03:21:33 May be new devices needs more time 03:22:13 Thanks, Sundar! 03:22:53 ikuo_o: Welcome :) 03:23:03 I need some time in Friday to dicuss the dirty data caused by conductor diff. 03:23:29 Coco_gao: Good. Conductor diff: 15-30 min? 03:23:37 That's good 03:23:51 PCI slot change on reboot -- why is it any different than Nova's PCI subsystem? 03:25:34 I will make sure with shaohe, and see if we need to discuss that. 03:25:51 wangzhh, Coco_gao: any performance countres planned for GPUs? I am thinking just report driver-reported perf counters from agent to a collectd plugin. From there, it can be consumed by telemetry/ceilometer, prometheus, .... 03:25:53 Right now , we can skip that 03:26:04 Coco_gao: ok 03:27:45 Who is the owner of L42 idea? I plus some info on it 03:28:24 yikun: do you mean SmartNIC? 03:28:33 "Performance/health monitoring for GPUs or any other devices?" 03:30:01 Whuuu, difficult to monitor it now, because when we passthrough the GPU in the vm. Host will lost control of this device. I'll consider about that. 03:30:36 yikun: I responded too. I would like to find an owner. 03:31:00 I'm not the owner but the function seems useful. 03:31:08 Does FPGA or other devices have the same scenario? 03:31:10 wangzhh: yea, same problem for FPGAs, but we should have the PF in the host from where we can get shell counters. 03:31:45 Besides, we also have dependence on the vendor stack 03:32:04 yikun: Does Ascend support SR-IOV? 03:32:27 Sundar, Yep. Depend on vendor stack. 03:33:58 If Ascend supports SR-IOV, and we can get performance counters from its PF, we have a potential use case. Otherwise, we'll focus on other practical things and then come to this. 03:35:14 Sundar: ascend 310 don't support sr-iov yet 03:35:25 Then shall we deprioritize this topic for PTG? 03:36:00 ascend support entire pci passthrough right 03:36:05 yes 03:36:26 passthrough is supported. 03:36:44 Sundar, Depend on the priorities and our time. 03:36:46 Sundar: I think we still can add this topic in PTG 03:37:16 OK, I only said de-prioritized. So, if there's time after topics, sure 03:37:46 Driver support for Movidius - who owns this? 03:38:05 Shaohe? 03:38:06 Sundar: i think is Shaohe 03:38:08 Coco 03:38:37 RISC-V? 03:39:06 We use Movidius in the Edge. 03:39:32 Movidius is a USB device, right? 03:39:33 Coco_gao: Cool. Maybe both you and Shaohe can drive it? 03:39:42 Yes 03:40:38 It's USB right now, in order to use it, we need to install openvino 03:40:44 I should a topic for post-PTG plans. That's important. Merge pilot with master, add FPGA CI, etc. are important for Nova intgration 03:41:03 Sundar, agree 03:41:17 the most important thing is nova integration 03:41:28 Sundar: thanks for your hard work, and the pilot is the most import one. 03:41:38 * important 03:42:46 Xinranwang is looking at tempest plugins for Cyborg CI, right? I can help her. Anybody else wants to help? It will be a set of CI test cases. So, could be lots of work. 03:43:25 yes, that's also a part of post ptg plan 03:44:11 I can take part of these if it is not emergency. 03:44:49 wangzhh: It is not an emergency, but until we get the CI going, Nova will probably not merge. 03:45:35 Please see https://etherpad.openstack.org/p/ptg-train-xproj-nova-cyborg 03:45:52 does nova guys require to have CI done before they merge? 03:46:03 I can also join once there is time. 03:46:33 btw, my visa is still on administrative processing. only 4days to go. I'm highly probably not be able to attend the summit and ptg. the new project update looks great for me! 03:46:36 thanks wangzhh Yumeng 03:46:38 xinranwang: Please see that link. 03:47:27 Yumeng: That's tough. We'll keep you updated 03:47:44 Thanks for the slides review 03:48:01 but I will join remotely, will we have remote access just like last ptg did? 03:48:12 Sundar: ok, will look into it. Thanks 03:48:43 Yumeng: I'll check and get back 03:48:59 Sundar:ok. thanks 03:49:31 nice to have remote access, I can join remotely also :) 03:50:00 @all, shall I take a stab at time assignments based on the above, and you can add your comments if you want changes? 03:52:36 Silence means yes, I think :) 03:52:48 It's ok. 03:53:08 OK, cool. I'll update and ping you all 03:53:24 #topic Tomorrow's Zoom meeting 03:54:01 I will present the PTG demo. This is highly important to get consensus across projects. Please attend and provide your feedback. 03:54:21 I will attend the meeting. 03:54:22 Should we take up anything else tomorrow? 03:54:31 ikuo_o: Thanks 03:55:14 I'm preparing material for PTG, but nothing for tomorrow. 03:55:30 Cool. 03:55:40 #topic AoB 03:55:46 Anything else? 03:56:45 It's ok, thanks Sundar. 03:57:03 Great. See you all tomorrow. Have a good day! 03:57:10 #endmeeting