17:00:09 #startmeeting Solum Team Meeting 17:00:10 Meeting started Tue Nov 17 17:00:09 2015 UTC and is due to finish in 60 minutes. The chair is devkulkarni. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:12 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:15 The meeting name has been set to 'solum_team_meeting' 17:00:20 #topic Roll Call 17:00:21 james li 17:00:23 Devdatta Kulkarni 17:00:31 hey james_li 17:01:04 Hi Dev 17:01:14 here is agenda for today's meeting: https://wiki.openstack.org/wiki/Meetings/Solum#Agenda_for_2015-11-17_1700_UTC 17:01:31 I know that adrian_otto and vijendar are out today 17:02:02 I don't see datsun180b either in solum irc room 17:02:38 lets give few minutes for folks to join 17:02:44 o/ 17:02:49 I know that muralia1 and dimtruck are in magnum meeting 17:02:52 oh there they are 17:02:54 hello 17:03:01 hi muralia1 and dimtruck 17:03:06 we have james_li 17:03:07 hi all 17:03:13 adrian_otto and vijendar are out today 17:03:24 and I haven't seen datsun180b as well 17:03:39 so it might be only four of us today 17:03:42 here is the agenda: 17:03:48 #link https://wiki.openstack.org/wiki/Meetings/Solum#Agenda_for_2015-11-17_1700_UTC 17:04:11 #topic Announcements 17:04:22 1) Solum Liberty release 17:04:32 #link https://etherpad.openstack.org/p/solum-liberty-release 17:04:38 #link https://review.openstack.org/#/c/245963/ 17:04:43 #link https://launchpad.net/solum/+milestone/4.0.0 17:04:49 #link https://launchpad.net/python-solumclient/+milestone/1.2.7 17:05:02 let me give some background and explaining what is going on on the release front 17:05:38 so upstream has modified the ways releases are done (basically decoupling projects to be in-sync with each other from release pov) 17:06:13 doug hellmann and ttx wanted us to come up with a bullet list of steps for making the release 17:06:27 I created these steps on that etherpad mentioned above 17:06:45 doug and ttx then provided guidance on what steps were required, what were optional, etc. 17:06:58 they also recommended that the version for solum that we should use is 4.0.0 17:07:10 this is also part of the new changes to the release process 17:07:28 then, I had to submit a review to openstack/releases repository 17:07:45 that review is mentioned above 17:07:46 sounds a plan 17:07:59 after that, there was some launchpad work to be done 17:08:41 basically, we had to create a 'milestone' in liberty series and tag all the bugs and blueprints that we fixed to that milestone 17:08:48 I have done that as well 17:08:54 nice! 17:09:00 #link https://launchpad.net/solum/+milestone/4.0.0 17:09:04 yes, saw all the changes you made 17:09:12 #link https://launchpad.net/python-solumclient/+milestone/1.2.7 17:09:21 we have fixed several bugs 17:09:30 some of which were actually features 17:09:35 ok 17:09:49 so now we are waiting for ttx to help us with the next steps 17:10:11 he has been considerate and has volunteered to do the liberty release for us 17:10:21 from our side, we have completed all the steps 17:10:32 the client will be released to pypi as well 17:10:39 I think there is a gate job which does it 17:10:51 ttx is traveling this week 17:11:05 but he said he would be checking his emails 17:11:21 so hopefully, by the end of the week we would have solum's liberty release cut 17:11:39 so that is all on that topic 17:11:59 if you happen to look through lp and find a bug which should be tagged to 4.0.0 release 17:12:05 please feel free to do that 17:12:28 set the status of that bug as 'Fix Released' 17:12:54 ttx mentioned that when we cut a final release, all the bugs need to be marked as 'Fix Released' 17:13:24 alright 17:13:34 next announcement is 17:13:41 2) Virtual hackday tomorrow (Wednesday, November 18th) 17:13:47 #link http://lists.openstack.org/pipermail/openstack-dev/2015-November/079161.html 17:13:53 #link https://etherpad.openstack.org/p/solum-hackday-nov18-2015 17:14:16 so as you may recall, we had discussed about holding such a hack day in last two meetings 17:14:35 I have created etherpad (linked above) with relevant details 17:14:45 I'll try to cut it in the coming hours 17:14:57 ttx: nice !! 17:15:34 ttx: quick question about the release-docs job failing on my patch: https://review.openstack.org/#/c/245963/ 17:15:42 any suggestions on how to fix it? 17:16:30 ok, continuing with the hackday discussion 17:16:55 please add yourself to the etherpad even if you would be participating for a few hours 17:17:15 also, may be the times when you would be around 17:17:37 will be good with the exposure for others 17:18:07 our vagrant environment should be good for you to try out all the new features 17:18:19 devkulkarni: you should ask on #openstack-release 17:18:23 thoughts/comments/questions? 17:18:28 ttx: ok, will do 17:21:01 alright, continuing to next topic 17:21:09 #topic Review Action Items 17:21:17 devkulkarni to figure out how to retire solum readthedocs 17:21:29 #action devkulkarni to figure out how to retire solum readthedocs 17:21:31 devkulkarni: I'll likely have to wait until the patch is fixed before cutting the release 17:21:40 I'll look into that failure see if I see why it fails 17:21:42 ttx: yeah, that's what I thought 17:21:58 ttx: that would be super helpful 17:22:26 ttx: also, after our irc meeting is over, I will get on to openstack-release to discuss about it 17:23:00 #topic Blueprint/Bug Review and Discussion 17:23:08 1) devstack plugin 17:23:14 #link https://review.openstack.org/#/c/236212/ 17:23:21 that's merged now :) 17:23:24 looks like this patch is merged 17:23:29 dimtruck: nice!! 17:23:35 so little background on that patch 17:24:01 actually, no it's not...looks like it's missing a verification? 17:24:20 dimtruck: it should merge hopefully 17:24:26 ok 17:24:31 the verification gates run before merging 17:24:38 going back to the background on this patch 17:24:50 it started with this email from sdague 17:24:53 #link http://lists.openstack.org/pipermail/openstack-dev/2015-November/079135.html 17:25:31 the email identifies all the projects for which the devstack gate jobs would start failing unless we change our gate job to use devstack plugin model 17:25:44 notice that we are on that list 17:25:57 james_li, even designate on that list 17:26:09 don't know if you guys are on top of it already or not 17:26:31 if not, I would recommend making that as a priority as no patches will merge 17:26:48 after December 1st (I think) until this is fixed 17:26:59 so going back to our situation.. 17:27:27 the way to use devstack plugin on the gate job is to create that plugin as part of our repository 17:27:39 we have known about this requirement for a while 17:28:12 an independent contributor, venkatamahesh had submitted a patch to add this plugin in our repository 17:28:23 dimtruck worked from that patch 17:28:31 and tested it yesterday 17:28:37 right dimtruck? 17:28:43 correct 17:29:25 so now that we have got this patch merged 17:29:49 the next thing is to submit a patch to openstack/project-config to change our gate job configuration to use this plugin 17:30:04 dimtruck: are you planning to submit that patch as well? 17:30:13 yes sir 17:30:17 awesome 17:30:38 i wanted to check with venkatamahesh if that was on his roadmap since he submitted the original patch 17:30:43 but yeah - that's the next step 17:30:54 dimtruck: I would suggest you do it 17:30:58 ok 17:31:10 add venkatamahesh as a reviewer 17:31:19 but I haven't been able to get hold of him on irc yet 17:31:33 since this is time critical, it will be good if one of us does it 17:31:59 cool. so I will look forward to your patch sometime soon :) 17:32:01 ok, i'll have that in 17:32:20 next one is 17:32:22 2) Adding Reno for managing release notes 17:32:27 #link https://review.openstack.org/#/c/243295/6 17:32:33 #link https://review.openstack.org/#/c/243301/ 17:34:10 dimtruck, muralia1: don't know if magnum has added reno yet, but if not you can check out above patche 17:34:13 patches 17:34:52 thanks 17:35:30 ok 17:36:02 the next one is: 17:36:12 oslo-incubator went away recently. What do we need to do? 17:36:18 #link http://lists.openstack.org/pipermail/openstack-dev/2015-November/079343.html 17:36:24 so some background on this 17:36:55 above email mentions that oslo-incubator is no longer a thing 17:37:07 oh… 17:37:12 all the patches from incubator has been moved over in their own libraries 17:37:15 devkulkarni : you essentially take over that code you have and move it into your own namespace/package structure. remove things you don't need 17:37:29 dims: was about to ping you about this :) 17:37:37 we have this in our repo: https://github.com/openstack/solum/tree/master/solum/openstack 17:38:05 devkulkarni most of those files you can find in different oslo libraries 17:38:16 so based on what you mentioned above, we have to move this code in our own namespace/package 17:38:20 if you choose to use them 17:38:35 dims: yeah, makes sense 17:38:49 my preference is for you to use the official oslo libraries first, any missing files, use the copy you have 17:39:06 dims: as a step-by-step process, do you recommend that we first move those in our package, and then replace them/remove unused? 17:39:13 looking at that list, you are way behind in oslo adoption 17:39:18 dims: oh I see 17:39:30 dims: that is true, unfortunately :( 17:39:45 devkulkarni : it does not make sense to move them first as it really does not matter 17:40:17 dims: yeah, you are right.. 17:40:35 devkulkarni : probably because you don't have a liaison for oslo yet https://wiki.openstack.org/wiki/CrossProjectLiaisons#Oslo 17:41:00 dims: what is the the best way for us to move forward on this? would the gates start failing anytime soon because we have not yet moved over? 17:41:09 dims: yes, that is true 17:41:10 nope 17:41:24 in fact I was going to check with the team about oslo liaison today 17:41:30 while discussing about your email 17:41:42 :) 17:42:23 dims: let me check with others in the team 17:42:36 in any case, we definitely want to be on top of this 17:42:56 so at least I would start attending oslo meetings from next time 17:43:02 ++ thanks devkulkarni 17:43:48 cool 17:43:54 so that is on that topic 17:44:07 next one is 17:44:13 3) Mitaka Roadmap discussion 17:44:18 #link https://wiki.openstack.org/wiki/Solum/HighLevelRoadmap#Milestone:_Mitaka 17:44:30 we had discussed about this in last week's meeting 17:44:47 any thoughts/comments after a week? 17:45:22 no 17:46:18 alright.. we can always discuss/debate on what specific items we want to prioritise 17:46:30 or even add to the roadmap 17:46:38 as things evolve 17:47:06 right now, we can use the above list as a guiding set of features on where we want to go next 17:47:13 devkulkarni, i think we should include one more to the list. move app config from app create to app deployment time 17:47:42 muralia1: you mean, application parameters? 17:47:47 yes 17:48:30 muralia1: sure, we can add that.. although, I think we had said that there is value in having app parameters both at the app create and app deploy 17:48:52 sure. as long as we can update params during deployment 17:48:58 the parameters set at 'app create' can be overridden at 'app deploy' 17:49:00 yeah 17:49:31 I can take an action item to update the roadmap to add this 17:49:31 do we already support that? 17:49:41 no, we don't support that right now 17:49:58 ah ok. i thought i missed that patch :) 17:50:05 dimtruck: your patch has been merged 17:50:13 saw that :) 17:50:28 muralia1: no, you haven't missed much patches.. thanks for all the reviews :) 17:50:57 dimtruck: now you can submit your project-config patch 17:51:02 yup! 17:51:08 dimtruck: I am wondering how would we test it though? 17:51:17 in the gate ;) 17:51:38 i'm assuming that once we update the project.config, it'll run our tests? 17:51:55 for that to happen 17:52:03 won't we have to submit a patch to our repo 17:52:06 some patch 17:52:14 so may be what we could do is: 17:52:36 retrigger one of our existing patches (or submit a new patch) which has a dependency on the project-config patch 17:53:06 would that cause the new project-config changes to be used on the gate? 17:53:21 dimtruck: ^^ 17:53:56 #action: devkulkarni to update Mitaka roadmap to include a feature for setting app parameters both at app create time and app deploy time 17:54:16 we are almost at the end of our meeting 17:54:25 let me move to open discussion 17:54:30 #topic Open Discussion 17:54:40 makes sense 17:59:30 alright, thanks for joining today folks 17:59:35 thanks devkulkarni 17:59:41 will see you tomorrow in the virtual hack day 17:59:42 see you all 17:59:46 or next week 17:59:55 #endmeeting