21:00:21 #startmeeting Solum Team Meeting 21:00:22 Meeting started Tue May 5 21:00:21 2015 UTC and is due to finish in 60 minutes. The chair is adrian_otto. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:00:23 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:00:25 The meeting name has been set to 'solum_team_meeting' 21:00:28 #link https://wiki.openstack.org/wiki/Meetings/Solum#Agenda_for_2015-05-05_2100_UTC Our Agenda 21:00:34 #topic Roll Call 21:00:37 ed cranford 21:00:38 Adrian Otto 21:00:43 Melissa Kam 21:00:45 murali allada 21:00:53 devdatta kulkarni 21:01:17 I am having a little internet trouble, so if I am slow responding just carry on, please 21:02:11 hello datsun180b mkam muralia devkulkarni 21:02:21 hello adrian_otto 21:04:44 #topic Announcements 21:04:47 1) Reminder: There will be no team meeting on 2015-05-19 due to the OpenStack Summit. 21:05:08 ok 21:05:14 that concludes prepared announcements. Are there any other announcements from team members? 21:05:18 hi akshayc 21:05:26 james li 21:05:27 hi devkulkarni 21:06:42 #topic Review Action Items 21:06:56 #action adrian_otto to spring clean our blueprints 21:07:10 #action adrian_otto to spring clean our bug list 21:07:26 #action adrian_otto to email the dev list concluding the Solum PTL Election 21:07:46 adrian_otto: just a fyi, sometime last week I looked at some of the bugs and marked them as either resolved or in progress 21:07:49 my hope is to conclude these upon tagging a release 21:07:50 hope you don't mind 21:07:59 thanks! 21:08:08 yes, can use all the help I can get 21:08:12 I was in the middle of submitting a patch for my bug and so while I was at it, did a few 21:08:17 are we ready to tag a release of solum? 21:08:29 I think so.. 21:08:31 that will help to clear our all the fix committed tickets 21:08:35 muralia: what about your patch? 21:08:43 does not need to get in? 21:08:51 which one? the keystone one? 21:08:55 yeah.. 21:09:04 we can wait if we are not ready 21:09:13 no it doesnt. its just improvement and does not block anything 21:09:22 muralia: ahem 21:09:36 james_li, datsun180b, mkam: thoughts? 21:10:09 we can always tag another as a fast follow 21:10:17 well i'd like to get the trigger changes into solum but admittedly it's not mandatory yet 21:10:30 it can always come in another release 21:10:47 mkam/james_li: ? 21:10:52 i good with that 21:11:07 better to have mine: https://review.openstack.org/#/c/170313/ 21:11:10 ok, so I will take an action to tag a release if there are no objections. 21:11:30 adrian_otto: may be after we merge james_li's patch? 21:11:39 ok 21:11:54 I will fix the gate by today 21:12:03 james_li: +1 21:12:21 I think most of the team has already reviewed it 21:12:41 ok, so if you email me when you are ready, I can do my part 21:12:54 thanks adrian_otto 21:13:08 #topic BP/Task Review 21:13:35 any work items requiring team discussion (maybe https://review.openstack.org/#/c/170313/ perhaps?) 21:14:21 sure.. james_li can give high-level description of the patch 21:15:01 it separates the storage of DU image loc and tag 21:15:19 so we don't need to concat the two things into one big string 21:15:30 so improves reliability. 21:16:04 very straightforward 21:16:28 brb, switching connections. 21:17:09 * adrian_otto1 back again 21:17:14 james_li: +1 21:17:52 ok, anything else to cover on tas review? 21:17:56 *task 21:18:18 https://review.openstack.org/#/c/163120/ 21:18:28 that one seems sitting there for a while 21:18:42 muralia: ^^ 21:18:47 yes, this is one of the next few things im going to work on. 21:19:02 basically, we've added a lot of plan validation in the CLI 21:19:27 we need to move it to the API. I'm ok with someone else taking ownership of this patch whil im working on other things 21:19:49 what's it need besides a rebase anyway 21:20:21 this patch was written way before we added things like plan name validation, port number validation and so many other things in the CLI 21:20:29 I think we should hold onto to the validation till we get the app resource 21:20:39 sure 21:20:52 muralia: what if we abandon this patch? 21:20:55 I'm ok with abandoning this and creating a new patch 21:21:10 doing it now 21:21:12 no need to create a new one till we get the app resource in place 21:21:43 done 21:22:00 devkulkarni: +1 21:22:15 that makes sense 21:22:49 akshayc: you around? 21:23:29 looks like really bad connection adrian_otto 21:23:38 yeah, sorry about that 21:23:48 no worries.. 21:24:02 so we decided to abandon that patch which was doing API side validation for plans 21:24:12 we will pick the validation story once we have the app resource 21:24:59 ok, should we advance to open discussion? 21:25:05 sure 21:25:06 and i'd like to get back to that following my trigger changes 21:25:17 #topic Open Discussion 21:25:31 is gpilz around today? 21:25:54 looks like not.. 21:26:24 no, he is not 21:26:29 there were few camp related functional tests which were failing recently, so wanted to check with him if he had any suggestions 21:26:47 let me see if I can find him 21:26:58 or we can reach out to him on solum later 21:27:06 yo 21:27:14 sorry 21:27:23 aha! 21:27:26 I can look into those 21:27:35 do you want to get into it now? 21:27:39 gpilz: do you know where to find what's troubling us? 21:27:58 we are in open discussion, so if you have anything to share this is a good time for it 21:28:02 may be it was a false alarm.. 21:28:05 gpliz: I was working on a new pluggable model for the keystone integration in Solum. 21:28:25 and I was adding support for keystone v2 upstream. this was making a few camp tests fail 21:28:31 functional tests. 21:28:53 can I pick up what you have committed so far and see for myself? 21:28:53 im not sure how to fix them, 21:29:23 sure, i'm still work on it, but theres a WIP patch out there 21:29:36 are camp tests enabled in our gates? 21:29:44 I think not 21:29:52 all the camp functional tests are no-ops if you don't enable camp 21:29:58 we put that in awhile ago 21:30:10 do they run today? 21:30:15 in our gates 21:30:37 no, they don't run on our gates 21:30:44 ok 21:31:17 I thought they were enabled by default 21:31:25 in anycase, I'll ping you if I need help gpliz 21:31:31 okay 21:31:32 https://github.com/stackforge/solum/blob/master/functionaltests/api/base.py#L61 21:31:33 oh! may be you are right mkam 21:31:48 good catch mkam 21:32:04 we can change that to false if we want :) 21:32:13 that's okay 21:32:31 okay to change it to False? 21:32:34 i'd rather know when CAMP breaks if that is okay 21:32:43 no 21:32:43 sure 21:32:52 another approach is to use a nonvoting gate for that 21:33:13 lets see if gpilz and muralia can get to green tests.. 21:33:14 so you get an indication that it's busted, but it will not block a merge 21:33:21 if that happens then we won't have to change anything 21:33:28 yes 21:33:28 but it's better to just have the tests enabled and working all the time 21:33:35 devkulkarni: +1 21:33:39 +1 21:34:58 ok, anything else to discuss today? 21:35:07 if not we can adjourn 21:35:14 sounds good 21:35:18 sure 21:35:24 great, thanks everyone for attending. 21:35:31 thanks adrian_otto 21:35:34 #endmeeting