14:01:01 #startmeeting Solum Team Meeting 14:01:02 Meeting started Wed Sep 20 14:01:01 2017 UTC and is due to finish in 60 minutes. The chair is zhurong. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:03 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:05 The meeting name has been set to 'solum_team_meeting' 14:02:16 hi zhurong 14:02:24 hi devkulkarni 14:02:36 nice to see you 14:02:42 how was PTG? 14:03:16 PTG is awesome 14:03:45 you should come next time 14:04:01 nice! glad that you had good time at PTG 14:04:30 did you have any solum related discussions with any one? 14:05:01 np, we didn't apply the room 14:05:08 ah right 14:05:25 how were cross-project sessions? 14:06:46 there are not too many cross-project sessions, just the TC goal policy-in-code 14:07:50 I see. did you attend that session? we don't have any keystone policy stuff.. we need to reply to that one comment on the goals patch 14:07:56 others are deployment cross-project 14:08:15 yep, we don't have 14:08:27 I see.. how was the policy-in-code session? 14:08:33 Is there a etherpad for that? 14:09:15 yeah, give me few secends 14:09:41 #link https://wiki.openstack.org/wiki/PTG/Queens/Etherpads 14:09:50 this is all the etherpad 14:10:23 cool 14:10:27 this is good list 14:12:24 in the session about meeting with tc, there was discussion about solum right? what all points were discussed? Is there a etherpad with discussion of that session? 14:13:34 I believe it is this: https://etherpad.openstack.org/p/queens-PTG-TC-SWG 14:13:47 yep 14:14:48 so the concerns listed there is that solum being "user-facing so would need a lot more features/polish/activity to not make us look bad" 14:15:42 I believe you mentioned in the meeting about all the features that we have implemented in last cycle, also completion of the goals 14:16:08 what did tc say about that? 14:16:26 They need more discuss about this 14:17:25 I see. did they say when/how the discussion will happen? 14:18:23 np, we just wait the patch 14:19:01 you mean the patch that will change status of solum? 14:20:05 yep, hope they don't do this 14:21:26 whether or not tc changes our status, we should discuss and decide what is our preferred option 14:21:38 what do you think we should do? 14:22:56 we can list pros/cons of the two options 14:23:09 we can not get more active contributors 14:24:13 1) Remaining official (advantages): a) space at PTG b) Official openstack branding 14:24:57 c) ability to attract contributors (although this has been hard for us as we need to spend more time doing PR of solum) 14:25:55 Remaining official (cons): a) need to implement openstack-wide goals; b) need to be on top of gate issues; 14:27:14 Going unofficial (advantages): a) Not so much pressure to keep implementing openstack-wide goals; b) Not under pressure to keep up with gate issues 14:28:12 Going unofficial (disadvantages): a) No space at PTG - this will more affect any change of attracting new/additional contributors; 14:29:07 we want to stay in big tent, but ... 14:29:33 Constraints: Currently its primarily only two of us involved -- you are also PTL of Murano. I don't have as much time as I used to before 14:30:18 please continue/complete your thought 14:32:00 If TC decided to remove us from official, we have no way to stop this 14:33:19 yes, that is the fact. 14:34:58 I am wondering if from our side do we want to take that decision rather than waiting for tc to make some decision for us? we can look at above pros/cons to help us take some decision (either we decide to stay or we decide to become unofficial) 14:36:21 given your Murano PTL duties, how much time do you have for Solum related work? 14:38:51 btw, I was looking at the sample policy patch: https://review.openstack.org/#/c/502506/1 14:39:12 openstack-wide goals and make gate always green, this is the basic, and this I can satisfy 14:39:49 ok that is good to know 14:40:02 because those are the two main things that I am most concerned about 14:40:09 if we want to remain in big tent 14:40:42 now TC wants more 14:41:04 we had done all of this is the last cycles 14:41:15 s/is/in/g 14:41:34 yeah, you have been on top of the goals and the gate for last couple of cycles 14:42:22 they wants more contributors more features 14:42:31 I wish tc would have explicitly defined a criteria based on number of new features or number of new contributors 14:43:06 hmm 14:43:49 as long as we are not falling short on completing tc goals and the gate is green, we are good imo 14:44:10 and you are saying that you have bandwidth for that? 14:44:52 yep 14:45:15 awesome!! 14:46:48 in that case we can let the tc take the decision. if they decide to make us unofficial on the basis of features and contributors, we can raise the point about where is that defined as an official criteria. I have not come across that to be honest 14:47:41 hope this will never happen 14:48:01 and we can remain focused on completing the goals and ensuring that the gate remains green 14:48:10 yeah, lets hope that will not happen 14:49:44 moving on then -- lets quickly discuss about the failing gate -- 14:49:55 any ideas why it is failing? 14:50:20 I think hongbin's patch will make it green 14:50:47 just merged 14:51:19 oh! 14:51:35 if that makes it green, that will be awesome 14:51:50 I also approved your patches about rootwrap 14:52:19 alright, another point was about the policy-in-code goal 14:53:04 we don't have policy 14:53:13 I think we *might* have to define a default policy file which lists all the resources, methods, and default role that we currently support 14:53:45 I know we don't have policy -- but we do require the user to have certain role, right? 14:54:26 we can check with the policy-goal committee if we are required to define this default policy as part of goal completion 14:54:27 yep, this is right, if add this, maybe will cause some errors 14:54:44 right 14:55:06 may be we can try adding it and see if we run into any issues. 14:55:22 see this is the sample patch: https://review.openstack.org/#/c/502506/1 14:56:39 we *might* have to add something of this sort https://review.openstack.org/#/c/502506/1/sandbox/policies/chairs.py 14:56:57 for our resources - app, workflow, etc. 14:58:12 agree 14:58:32 cool 14:58:51 we can make a comment to that effect in the patch about completion of our policy goal 14:58:56 do you have that handy? 14:59:16 btw, we are almost at the end of the meeting 14:59:32 feel free to end the meeting and we can continue for few minutes in solum channel 14:59:52 ok 14:59:55 #endmeeting