03:03:42 #startmeeting openstack-cyborg 03:03:43 Meeting started Thu Jan 9 03:03:42 2020 UTC and is due to finish in 60 minutes. The chair is Sundar. Information about MeetBot at http://wiki.debian.org/MeetBot. 03:03:44 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 03:03:46 The meeting name has been set to 'openstack_cyborg' 03:03:50 Hi all 03:04:36 #topic Roll call 03:04:42 Hi all. 03:04:45 #info Sundar 03:04:47 #info chenke 03:04:51 hi 03:04:57 #info wangzh 03:05:05 #info wangzhh 03:05:29 hi all 03:05:33 #info Yumeng 03:05:40 Hi Yumeng and all 03:05:44 Let's get started 03:05:49 #topic Agenda 03:05:50 https://wiki.openstack.org/wiki/Meetings/CyborgTeamMeeting#Agenda 03:06:05 #info s_shogo 03:06:27 Does anybody want to bring up anything else? 03:06:57 Ye. I want your guys help me review the exception patches. 03:07:17 Sure, chenke. I started on some of them. 03:07:27 ye, we got a lot patches to review 03:07:37 Ok. Thanks sundar. 03:07:48 Agreed, Yumeng. I am still catching up. 03:08:09 I will focus on reviewing too, these days 03:08:10 I just called out a few patches that I think may need some discussion 03:08:18 #topic Patches 03:08:19 https://review.opendev.org/#/c/699099/ 03:08:49 One comment was: "Can devices in cyborg be associated to specific projects?" 03:09:01 This is a use case worth discussing here, right? 03:10:52 What do you guys think of this use case? Yumeng, chenke, s_shogo, wangzhh 03:11:16 #info Li_Liu 03:11:57 sundar: are you thinking Lance Bragstad's question? Can devices in cyborg be associated to specific projects? If so, this check should ensure the user has reader authorization on the project in addition to the 'reader' role, correct? 03:12:19 Hi Li, xinranwang: we are discussing a comment in https://review.opendev.org/#/c/699099/ i.e. "Can devices in cyborg be associated to specific projects?" 03:12:22 Hi all, sorry for late 03:12:24 Yumeng: yes 03:12:44 #info xinranwang 03:13:01 xinranwang: np 03:13:44 I think devices can be shared between different project, what do you guys think? 03:13:52 Hi Sundar 03:13:55 I don't think it is necessary. 03:14:01 Sundar 03:14:33 agree with Xinran 03:14:37 The "project" concept here is in the Openstack context right? 03:14:41 xinranwang, Agree. 03:15:23 xinranwang , +1 03:15:25 Li_Liu, Yes 03:15:29 By default, a device can be shared across different projects. The questions seems to be whether there is value in allowing the admin to allocate a set of devices for a specific project. 03:16:03 Agree, since cpu/memory do not associate with project neither 03:16:35 Agree 03:16:50 Acceleration resources should be the same as CPU. 03:16:59 agree 03:17:19 Ok, if we decide not to do this in Ussuri and change our mind later, that is not a problem, AFAICS. I don't see any upgrade issues. Anybody has a different thought? 03:19:52 Apparently not. So, let us agree to not have an option of dedicating a device to a project. 03:20:08 :P 03:20:25 I'll take that as a yes :) 03:20:52 Next patch: https://review.opendev.org/670973 Bump openstackdocs theme 03:21:18 This has been sitting for a while. I am not an expert here. But it seems safe to merge this change. What do you all think? 03:22:24 Li_Liu, Yumeng, chenke, xinranwang, s_shogo, wangzhh: ^ 03:22:46 Agree Merge +1. 03:23:39 Ok, chenke, let's both review it and merge it. Thanks. 03:23:47 Ok. 03:24:18 Drawing all your attention to the ML thread: http://lists.openstack.org/pipermail/openstack-discuss/2020-January/011802.html 03:24:45 I haven;t caught up fully, and will respond soon-ish. If you have any thoughts, we can discuss here. 03:26:09 That seems pretty long. I will try to read through it as well 03:26:17 Sure 03:26:23 #topic AoB 03:26:30 http://lists.openstack.org/pipermail/openstack-discuss/2020-January/011803.html 03:26:52 zhipeng huang had an email reply this. 03:28:31 Yes, chenke. But do we all agree with Arkady's idea? Any points not addressed in the email thread so far. BTW, Arkady was at the PTG and raised issues re. firmware updates, which i captured in https://etherpad.openstack.org/p/cyborg-ussuri-programming-apis 03:29:45 I haven't read this email carefully. I will learn your response. 03:29:50 In my understanding, Ironic deals with devices as just PCI devices, but does inspect their properties 03:30:33 A Cyborg driver can do that. I am not sure that an entire Cyborg driver or its equivalent can be included in the Ironic inspection process. 03:30:57 However, Arkady brings up issues regarding server lifecycle management, warranties, etc. 03:31:33 Yes, ironic can only inspect general pci device, but for example, cyborg can discover vf/pf topology and AFU ID as well. 03:31:50 will read through it later 03:31:57 s/but does inspect/but does NOT inspect/ 03:32:34 Anything else to cover today? 03:32:44 Sundar: seems need more thinking. I will dig the ML more. and Re:https://review.opendev.org/#/c/701518/ Yes. I was testing with a real GPU 03:33:49 Yumeng: good to know 03:34:00 I was testing GPU driver and pls help to review. Li_Liu, chenke, xinranwang, s_shogo, Sundar,wangzhh: ^ 03:34:10 https://review.opendev.org/#/c/701518/ 03:34:14 Yumeng: ok, will review it later 03:34:29 ^_^ thanks! 03:34:45 Please keep continuing the good work, folks! Thanks a lot. Happy New Year, and have a good day! 03:34:49 Bye 03:34:51 Yumeng, Yep, some comments in line. 03:34:52 bye 03:34:53 #endmeeting