03:08:52 #startmeeting openstack-cyborg 03:08:53 Meeting started Thu Aug 6 03:08:52 2020 UTC and is due to finish in 60 minutes. The chair is Yumeng. Information about MeetBot at http://wiki.debian.org/MeetBot. 03:08:53 hi xinranwang_, swp20, chenke, good moning 03:08:54 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 03:08:56 The meeting name has been set to 'openstack_cyborg' 03:08:59 #topic Roll call 03:09:04 #info Yumeng 03:09:16 #topic Agenda 03:09:16 #info brinzhang_ 03:09:28 #info xinranwang__ 03:09:40 #info swp20 03:09:52 #info chenke 03:10:27 Will be a quick meeting today 03:10:36 progress review and one question from my side. 03:11:17 #topic progress track 03:11:31 #info s_shogo 03:11:40 policy patch got comments from Ghanshyam(high priority): https://review.opendev.org/#/c/740542/ 03:11:56 and I will fix the comments this week. 03:12:05 cool 03:12:20 thanks brinzhang_ for asking gmann to help review 03:12:33 Yumeng: np 03:12:38 I also asked keystone people to help review 03:12:59 yes, we should 03:13:12 and next: nova operations support patches(high priority) need review: https://review.opendev.org/#/c/715326/, https://review.opendev.org/#/c/729563/ 03:14:14 nova people think we should focus on operation support in this release, and we should. 03:15:40 thanks brinzhang_, sean and swp20 for the patch. I spare more time on them. 03:15:58 Yumeng: np 03:16:32 I think the evacuate patch is ok now, need to +2 from gibi 03:16:57 all, pls review if have any spare time, tks. 03:17:45 yes, always lack review.=: 03:18:07 and programme API need refresh(high priority): https://review.opendev.org/#/c/698190/ 03:18:29 I think this should be one of the high priority goals in V release. 03:18:51 we need to add the microversion of this patch 03:20:04 emmm.. will that work cost much time or effort? 03:20:06 just need to add a decorator to check the microversion, it seems not difficult 03:20:51 and before in xinranwang_'s patch already contained the decorator, just move and debug for it, I think 03:21:00 brinzhang_: alright. 03:21:06 ok, I check that 03:21:14 xinranwang__: what do you think? 03:21:53 Yes, program API need a new microversion check. 03:21:59 s_shogo: plse reference https://review.opendev.org/#/c/696860/8/cyborg/api/controllers/base.py@101 03:22:29 We need a decorator to check it. Please refer to my mircroversion previous patchset. 03:22:49 Thanks brinzhang_ for giving this link 03:23:35 brinzhang_ xinranwang__ thanks for the link 03:23:37 I hope this decorator is sample enough for us to use, and also that we can inviate alex_xu and gmann to review, they are expert at API 03:23:38 sounds good. 03:24:04 s/inviate/invite/ 03:24:34 xinranwang_, s_shogo: np 03:25:12 brinzhang_: sure we can. 03:26:47 and Maillist discussion on SRIOV SmartNic Support Spec: http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016339.html , https://review.opendev.org/#/c/742785/ 03:28:32 This spec may take long time to get ideas from nova and neutron and reach an agreement. 03:28:56 I dont think we can merge this spec in V release 03:29:52 first seen this spec just now, I have not reviewed into, but I know there are many content to discuss, refer previous ML 03:30:31 yes, you'are right. not urgent, but important for us to start and continue response and resolve the open issues. 03:31:40 I was thinking set it as a medium priority for this release, not urgent, what do you think ? 03:31:59 yes, if we can have an aggrement of this spec, I think it will be better in V release 03:33:15 nova spec will be freezed, I dont think we can have an aggrement before the deadline 03:33:43 but we can try 03:33:47 yes, sean and gibi mentioned this in the ML. 03:33:59 pls refer to http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016339.html 03:34:07 xinranwang__, Yumeng, shaohe_feng 03:34:33 they think we can continue work, but don't have to merge before spec freeze. 03:34:35 I have received the ML 03:34:57 yes, it is my mean too. 03:35:41 if we can make this spec is ready in V, that we can start to work in W realease, that will be merged fast 03:36:43 yes, that's the best result!. let's try. 03:37:24 LOL 03:37:25 ok. that's all for today's progress track. 03:37:45 Is there any other patch need to discuss? 03:37:46 In next release, it might be the high priority 03:38:07 yse xinranwang__ 03:38:42 ok, the last question from my side. 03:38:53 # topic AOB 03:39:01 yes, aggree to release in next release. 03:39:13 Ah, please review QAT patch as well. Hope we can introduce some new device in this release too. :) 03:39:43 I noticed we always lack of review. how to better review our patches? should we focus on several patches during a period? like setting high priority patches for each week? 03:39:49 My review work will be in next week ^ 03:41:40 Yes, we can set the priority of reviews according to each patches process. 03:42:10 high priority should be based on severals rules: 1) ready to review 2) need to catch up an appropriate deadline or milestones 03:42:33 3) an appropriate priority 03:43:55 agree 03:44:04 xinranwang__: yes, that's what I mean. We have few contributors to review many patchsetss. 03:45:09 songwenping_, s_shogo, what do you think? 03:45:29 Sometimes I am a little bit confused about if the patch is ready for review. Maybe we could use wf-1 when it is not ready? 03:45:41 yes, it's ok for me. 03:46:16 that is good idea >> add priority 03:46:43 agree, I would encourage to use wf-1 when it is not ready. 03:47:47 sound good. 03:48:30 ok. cool. so I will release review priority for each week in wechat group. 03:48:34 have launch now ^ goodbye all 03:49:01 that's all fro today. goodbye brinzhang_ 03:49:07 Thank you all. 03:49:17 Have a good day! bye bye 03:49:22 goodbye 03:49:26 bye 03:49:34 bye 03:49:35 #endmeeting