03:00:43 #startmeeting openstack-cyborg 03:00:44 Meeting started Thu Dec 12 03:00:43 2019 UTC and is due to finish in 60 minutes. The chair is Sundar49. Information about MeetBot at http://wiki.debian.org/MeetBot. 03:00:45 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 03:00:47 The meeting name has been set to 'openstack_cyborg' 03:00:52 Hi all 03:01:13 Hi all. 03:01:19 info chenke. 03:01:23 info# chenke 03:01:25 #info Yumeng 03:01:34 Hi chenke, Yumeng 03:01:51 Hi Sundar49 03:01:52 Let's give a min for folks to join 03:02:08 Hi all. 03:02:20 Hi 03:02:26 I just added https://wiki.openstack.org/wiki/Cyborg/Policy to the policy page 03:02:57 Yumeng: nice! 03:03:02 good 03:03:30 Great. 03:03:53 Good, let's get started 03:04:05 Agenda: https://wiki.openstack.org/wiki/Meetings/CyborgTeamMeeting#Agenda 03:04:16 #info s_shogo 03:04:21 Anything to add? 03:04:58 #topic Secure_Default_Policies_Popup_Team 03:05:01 mainly three questions needs to disscuss with you guys. please take a look at the bottom of https://wiki.openstack.org/wiki/Cyborg/Policy 03:05:16 Yumeng, could you explain to us what's happening in this area? 03:06:54 What do the terms mean, member vs. reader? 03:08:24 Yumeng: ^ 03:08:49 emmm. to be simple. the main problem today is that : 1) admin everywhere 2)insecure custom roles: many policy rules simply use "" as the rule 3)not support read-only 03:10:08 Our RBAC policies allow for admin and user roles, I think. Are we considering more roles, like member and reader? 03:10:15 these means sometimes users may have too much or not enough privileges 03:11:34 Have there been any meetings across the popup team? 03:11:40 something like that. 1)we need consistent admin over all openstack projects 2) we need to have read-only 03:12:10 3) we can have a scoped-RBAC including project-scope and system-scope 03:12:36 I see. So you could have a project-scope admin? 03:13:37 yes. project-scope works for most of our current cases. maybe we need consider add system-scope for device related RBAC 03:14:03 emmm. seems I need to propose a spec to describe this in more details 03:14:11 Re. the question about cyborg:arq:create, I agree that allowing any user to create an ARQ is too liberal, esp. because the ARQ creator can also program the device. 03:14:29 Yea, a spec would be welcome 03:15:13 yes. I have same concerns on cyborg:arq:create 03:15:28 How do we fix that? 03:16:06 Hi all, sorry for late 03:16:30 should we change to admin? 03:17:15 I was wondering why the initial design was allowing any user? 03:17:25 Does anyone know that? 03:17:29 That is too restrictive. We want some auhtorized users to crete, and others should be forbidden. 03:17:46 I mean: ^ for admin 03:18:53 Does it make to sense to have granular roles like, device profile reader/writer, ARQ reader/writer etc.? 03:19:32 sundar49: emmm seems no writer, only reader 03:20:16 Who can POST device profiles, PATCH arqs, etc.? Apart from admin? 03:21:35 Yumeng, chenke, xinranwang, wangzhh: ^ 03:22:01 I only use admin to create device_profile. 03:22:12 I think only admin 03:22:36 admin in project scope? 03:22:58 yes. 03:23:02 emmm Yep. I remembered that we disscussed about it before. And only admin allowed. 03:24:03 Yumeng: So, the next step is that we need to review this table in the wiki? 03:24:20 are you included in any meetings they have for this ? 03:26:09 If anybody has any thoughts, please speak up. 03:27:08 #topic Devstack components for multi-node 03:27:23 Shaohe's table: end of https://etherpad.openstack.org/p/cyborg-ptg-ussuri 03:27:59 Any further comments? 03:28:33 If not, shall we close this as final? 03:29:09 I have one. 03:29:18 9. agent enabled_drivers N Y N 03:29:47 agent enabled_drivers? 03:30:36 chenke, what is the comment? 03:30:38 I think cyborg-agent node's conf need this . 03:31:09 Oh yes, it should be N N Y 03:31:16 Ye. 03:31:26 Please write that in the etherpad 03:31:53 Thanks, chenke. Anything else? 03:32:21 Sundar49: not yet. I just talked to zhurong. his idea is that this can be flexible. we can either use admin directly to post ARQ or use any user to make this post request to a system user to help do this post and return results. 03:32:44 about 10. api ramdisk_heartbeat_timeout 03:33:07 I don't know why we need this 03:33:26 Sundar49: I will propose a spec today and welcome you guys to disscuss. 03:33:59 Yumeng: when a user wants to launch a VM with accelerators, he needs the ability to POST and PATCH ARQs, right? Does he have to ask the admin to create the VM? 03:34:20 Yumeng: ok, we can discuss in the spec 03:35:05 chenke: I don't see a reason for it either. We can probably drop it. 03:35:25 Agree. 03:36:29 Ok, moving on 03:36:53 For functional testing, we don't have Li today 03:37:14 #topic Programming 03:37:34 API proposal: https://etherpad.openstack.org/p/cyborg-ussuri-programming-apis 03:37:57 Has anybody reviewed this yet? 03:39:18 s_shogo, would you like to bring up or discuss your patch? 03:39:53 Yap,My patch relates the bottom of the proposal, > " Update FPGA user logic (bitstream)" 03:41:16 My first comment is, it probably needs more validation :) Validation of inputs, Needs some checks: is the bitstream id valid, is the bitstream already programmed, is the deployable in use, etc. 03:41:23 Also, UT 03:41:43 There is no specific topic, so 03:42:14 Thank you Sundar49 , I improve that. 03:42:21 Thanks 03:43:49 Before we move onto other things, have you all had a chance to look at the comments in https://review.opendev.org/#/c/692707/6/nova/objects/external_event.py@36 https://review.opendev.org/#/c/631244/51/nova/conductor/manager.py@1578 03:44:16 This will have impact on Cyborg side too 03:45:01 Ok. Will look at it after meeting. 03:45:25 ok 03:45:36 #topic Storyboard, specs, patches 03:46:19 I know there is a long list of specs and patches for me to look at :). Does anybody want to raise anything specific to expedite? 03:47:45 Very quiet meeting today :) 03:48:11 Ok, I''m going to keep chugging on Nova side. Please ping me if you have comments/questions/concerns 03:48:40 Have a good day, everybody! 03:48:50 bye. see you 03:48:52 #endmeeting