17:00:05 <devkulkarni> #startmeeting Solum Team Meeting
17:00:05 <openstack> Meeting started Tue Nov 10 17:00:05 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:06 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:10 <openstack> The meeting name has been set to 'solum_team_meeting'
17:00:14 <devkulkarni> #topic Roll Call
17:00:19 <devkulkarni> Devdatta Kulkarni
17:00:23 <datsun180b> Ed Cranford
17:00:31 <devkulkarni> Hi datsun180b
17:00:34 <datsun180b> howdy
17:00:52 <devkulkarni> hopefully folks will join in a few minutes
17:01:19 <james_li> james li
17:01:26 <devkulkarni> hey james
17:01:33 <james_li> Hi devkulkarni datsun180b
17:01:54 <muralia1> o/
17:01:58 <devkulkarni> hi muralia1
17:02:01 <muralia1> hi
17:02:06 <devkulkarni> we have james_li and datsun180b as well
17:02:36 <devkulkarni> here is the agenda for today's meeting
17:02:43 <devkulkarni> #link https://wiki.openstack.org/wiki/Meetings/Solum#Agenda_for_2015-11-03_1700_UTC
17:03:10 <devkulkarni> while we wait for a few minutes to see if other folks are going to join us today, please check it out
17:03:55 <devkulkarni> hi vijendar, pt_15
17:04:04 <vijendar> Hi devkulkarni
17:04:08 <vijendar> Hi All
17:04:15 <pt_15> devkulkarni: hi!
17:04:28 <devkulkarni> alright, we have a quorum.
17:04:42 <devkulkarni> thanks pt_15, vijendar, muralia1, datsun180b for joining in for today's meeting
17:04:46 <devkulkarni> lets begin
17:04:57 <devkulkarni> for those who just came in, here is the agenda for today
17:05:03 <devkulkarni> #link https://wiki.openstack.org/wiki/Meetings/Solum#Agenda_for_2015-11-03_1700_UTC
17:05:21 <devkulkarni> #topic Announcements
17:05:32 <devkulkarni> I have one announcement today
17:05:48 <devkulkarni> #success Logs resource moved over from assembly to workflow. This was the last remaining thing. This completes the implementation of the new api resources.
17:05:50 <openstackstatus> devkulkarni: Added success to Success page
17:06:03 <datsun180b> That's great news
17:06:09 <james_li> cool
17:06:23 <muralia1> nice.
17:06:30 <devkulkarni> this is indeed a great achievement for our team
17:06:51 <devkulkarni> thanks to everyone who pitched in with either the spec, the implementation, the reviews
17:07:02 <muralia1> is this the main thing we had for the liberty release?
17:07:02 <devkulkarni> it was a long road, but we made it
17:07:16 <devkulkarni> muralia1: this was one of the main things we had targeted for liberty
17:07:21 <muralia1> ok
17:07:32 <devkulkarni> there were couple of others, which we have not been able to finish
17:07:45 <devkulkarni> we got started on them
17:07:57 <devkulkarni> so we will just continue them in the next release
17:08:20 <devkulkarni> I have a bullet point today to discuss about Mitaka priorities
17:08:32 <devkulkarni> we can delve into this more when we get there
17:09:09 <muralia1> are we going to cut a liberty release?
17:09:14 <devkulkarni> muralia1: yes
17:09:27 <devkulkarni> let me jump ahead to those topics actually since we are talking about releases
17:09:32 <muralia1> saw thing review recently. https://review.openstack.org/#/c/242068/
17:09:47 <devkulkarni> oh!
17:09:52 <devkulkarni> I did not see that
17:10:17 <adrian_otto> o/
17:10:18 <devkulkarni> thanks for the pointer muralia1
17:10:22 <devkulkarni> hi adrian_otto
17:10:28 <devkulkarni> we just got started few minutes back
17:10:35 <muralia1> adrian_otto can give us some context into this patch. https://review.openstack.org/#/c/242068/
17:10:38 <adrian_otto> I will miss our team meeting next week due to a speaking engagement
17:10:44 <muralia1> we just discussed this in the magnum meeting
17:10:58 <devkulkarni> adrian_otto: ok, thanks for letting us know
17:11:16 <devkulkarni> muralia1: ok, cool
17:11:53 <adrian_otto> to address https://review.openstack.org/242068 all we nee to do is tag a final release for liberty, and submit a follow-up patch that effectively reverses the 242068 one.
17:12:23 <devkulkarni> adrian_otto: I see
17:12:44 <devkulkarni> adrian_otto: I will do that this week for solum
17:13:00 <devkulkarni> I have been keeping track of the new changes to release process
17:13:02 <adrian_otto> if you need any guidance, let me know. I'm happy to lend a hand with that.
17:13:24 <devkulkarni> adrian_otto: sure, that sounds good. will ping you
17:13:39 <devkulkarni> I submitted following yesterday
17:13:42 <devkulkarni> #link https://review.openstack.org/#/c/243295/
17:13:44 <adrian_otto> it might also be a good idea to get input from ttx as well, just to be sure what we do is meeting expectations.
17:13:48 <devkulkarni> #link https://review.openstack.org/#/c/243301/
17:14:00 <devkulkarni> sure, will check with ttx as well
17:14:24 <devkulkarni> I was planning to reach out to dhellmann today wrt to the release notes related patches ^^
17:14:27 <adrian_otto> I actually have backported code in magnum that needs to be released. I'm not sure if you have bug fixes for solum that need to be included for liberty.
17:15:41 <devkulkarni> I was thinking, since we have not yet cut liberty, is this required?
17:16:02 <devkulkarni> the current state of the repositories would be our liberty, no?
17:17:05 <adrian_otto> you just pick a release, branch it as stable/liberty,and then tag a release from that, and update openstack/releases/deliverables/liberty/solum.yaml with the associated git hash
17:17:14 <adrian_otto> I don't think there is any more to it.
17:17:24 <devkulkarni> ok, that sounds straightforward
17:17:30 <adrian_otto> but let me know what ttx says.
17:17:39 <devkulkarni> sure, sounds good
17:18:12 <devkulkarni> ok, so on the topic of releases I have couple more points
17:18:35 <devkulkarni> recently dhellmann has sent several emails to openstack-dev mailing list about changes to the release process
17:18:46 <devkulkarni> the main gist of those is the following
17:19:02 <devkulkarni> there is a new tool, called 'Reno' which the release team has introduced
17:19:30 <devkulkarni> this allows creating release notes directly from the source repository (we have to specify yaml files with the notes)
17:19:43 <devkulkarni> the ask from the release team is
17:20:24 <devkulkarni> we submit a patch to include reno in our repo (only one repo is fine; so I have included the reno setup in solum and not python-solumclient)
17:20:55 <devkulkarni> and second, we submit a patch to our project-config setup so that the release notes will be created as part of a gate job
17:21:05 <devkulkarni> the two patches for solum are:
17:21:09 <devkulkarni> https://review.openstack.org/#/c/243295/
17:21:14 <devkulkarni> https://review.openstack.org/#/c/243301/
17:21:20 <adrian_otto> oh, cool
17:21:32 <devkulkarni> I don't yet know if those patches are correct/complete
17:21:40 <devkulkarni> today I am planning to pick dhellmann
17:21:59 <devkulkarni> pick dhellmann's brain to understand more about this process
17:22:07 <devkulkarni> also get his feedback on the above patches
17:22:31 <devkulkarni> the main thing which I have not yet understood is, how do we relate the release notes to the releases
17:23:01 <devkulkarni> so that is regarding the changes to the release process
17:23:04 <muralia1> ok. let me know once you've made all changes. will review them
17:23:12 <devkulkarni> muralia1: sure, will do
17:23:20 <devkulkarni> one final thing regarding releases is
17:23:42 <devkulkarni> a question that I have for you adrian_otto.. what is the process of uploading to pypi?
17:23:42 <adrian_otto> where do the release notes show up when using reno?
17:24:04 <devkulkarni> adrian_otto: the gate job publishes them to online documentation using the sphinx plugin
17:24:10 <adrian_otto> devkulkarni: there is a pypi job in the gate already. When you tag a release it is uploaded to pypi automatically for you.
17:24:12 <devkulkarni> actually, the gate job is for that purpose
17:24:27 <devkulkarni> adrian_otto: oh !! nice
17:24:57 <adrian_otto> we needed to set up a trust between pypi and openstack-ci to get that working, but it did work last time I tagged a solum release.
17:25:28 <devkulkarni> I see. Hopefully that will work this time as well
17:25:31 <devkulkarni> cool
17:25:55 <devkulkarni> adrian_otto: is there anything more that I should be thinking about regarding releases?
17:26:23 <devkulkarni> my plan is to tag a release this week
17:26:38 <devkulkarni> also get the reno setup merged
17:27:08 <adrian_otto> you will need a GPG key to sign the tag
17:27:19 <devkulkarni> oh ok
17:28:08 <adrian_otto> mordred helped me figure that one out. At the time I needed to make one we did not have a written guide that explained how to do it.
17:28:17 <adrian_otto> perhaps we have one now
17:28:48 <devkulkarni> ok. thanks for the heads up. will ping you if I run into issues
17:29:01 <adrian_otto> ok
17:29:44 <devkulkarni> alright. I feel excited that we will have release with the new api resources merged
17:30:19 <devkulkarni> next one for today are patches to review
17:30:23 <devkulkarni> #link https://review.openstack.org/#/q/project:openstack/solum+status:open,n,z
17:30:30 <devkulkarni> #link https://review.openstack.org/#/q/project:openstack/python-solumclient+status:open,n,z
17:30:50 <devkulkarni> whenever you get a chance, please take a look at the open patches
17:31:19 <devkulkarni> I would like to merge the cli patches before tagging the release
17:31:40 <devkulkarni> vijendar: I have added comment to one of your cli patches
17:31:56 <vijendar> devkulkarni: sure. will take a look
17:32:01 <devkulkarni> hopefully you will be able to address the comment soon
17:32:29 <devkulkarni> pt_15: I have started looking at your trigger controller refactoring patch
17:33:01 <devkulkarni> james_li, datsun180b: would you mind taking a look at pt_15's patch
17:33:16 <james_li> sure
17:33:22 <datsun180b> i can look
17:33:24 <devkulkarni> if you have any feedback on the unit tests that would be helpful
17:33:36 <devkulkarni> thanks james_li, datsun180b
17:33:56 <devkulkarni> datsun180b: I have one more request for you
17:34:21 <devkulkarni> mind looking at venkatamahesh's patch for devstack plugin change?
17:34:36 <datsun180b> the one that removes slugtester?
17:34:48 <devkulkarni> this one: https://review.openstack.org/#/c/236212/
17:35:17 <devkulkarni> basically, this changes our devstack setup to work in the new plugin model of devstack world
17:35:26 <datsun180b> I'm not up to date on that plugin model
17:35:36 <devkulkarni> ah, ok
17:35:44 <devkulkarni> nm then
17:35:59 <devkulkarni> we need this patch merged soon
17:36:07 <datsun180b> i'll do what i can
17:36:17 <devkulkarni> and we need to follow this up with another patch to project-config
17:36:29 <devkulkarni> which will change our devstack gate setup to use the plugin model
17:36:53 <devkulkarni> basically, very soon (in few more weeks), the devstack gate will stop working with our current setup
17:37:10 <devkulkarni> the openstack-infra team had announced this before the summit
17:37:23 <datsun180b> i remember hearing about that
17:37:24 <devkulkarni> so this one is a top priority for us
17:37:49 <devkulkarni> james_li: has designate already converted over to use plugin model in the devstack gate?
17:37:56 <devkulkarni> datsun180b: yep
17:38:01 <pt_15> devkulkarni: ok, great, thanks :)
17:38:14 <james_li> devkulkarni: no
17:38:33 <james_li> as far as I know
17:38:39 <devkulkarni> james_li: are you guys planning on doing it anytime soon?
17:39:00 <james_li> no idea about that
17:39:05 <devkulkarni> hmm.. ok
17:39:29 <devkulkarni> let me know if you find it out. will be nice to have another team which is also working on the transition
17:39:58 <devkulkarni> ok
17:40:09 <devkulkarni> the next one on the agenda is:
17:40:19 <devkulkarni> Mitaka Roadmap discussion
17:40:34 <devkulkarni> #link https://wiki.openstack.org/wiki/Solum/HighLevelRoadmap#Milestone:_Mitaka
17:41:04 <devkulkarni> so, I looked through our roadmap for liberty and moved over items which we have not yet completed to Mitaka
17:41:40 <james_li> devkulkarni: yeah
17:41:44 <devkulkarni> what do you all feel about the identified items?
17:42:18 <devkulkarni> some of the items we have already started
17:42:32 <devkulkarni> things like: Non-destructive app updates (app keeps same IP across successive app deployments)
17:42:38 <devkulkarni> Convert bash scripts to python for more reliability and easier debugging (tech debt reduction)
17:43:07 <devkulkarni> will be nice to get these completed in this cycle
17:44:00 <james_li> devkulkarni: so you heard from people in the summit that the main missing feature for solum is the micro-service support
17:44:04 <devkulkarni> any feature that you think we should specifically target for this cycle?
17:44:32 <devkulkarni> james_li: good point. we should add that. yes, that was what I took away from the summit
17:44:58 <vijendar> devananda: I was about to ask about that (micro-serivice support) as well
17:45:04 <vijendar> devkulkarni: ^^
17:45:07 <james_li> do we want to do anything towards that in this cycle?
17:45:09 <devkulkarni> vijendar: yep
17:45:17 <devkulkarni> james_li: yes, I think we should
17:45:44 <devkulkarni> james_li, vijendar: thanks for bringing that up. I had missed it. let me update the milestone list
17:46:24 <vijendar> devkulkarni: thanks
17:46:33 <james_li> cool
17:46:45 <devkulkarni> added it
17:46:53 <devkulkarni> good call james_li, vijendar
17:47:15 <devkulkarni> note that the list is not in priority order
17:47:33 <devkulkarni> those are all the things we would like to do in this cycle
17:47:46 <james_li> very nice!
17:48:19 <devkulkarni> are there any other items for review/discussion?
17:48:49 <james_li> about the hack day?
17:48:56 <devkulkarni> james_li: yes, was about to come to that
17:49:03 <devkulkarni> #topic Open Discussion
17:49:29 <devkulkarni> Last week we discussed about holding a virtual hackday for Solum
17:49:47 <devkulkarni> I had reached out to some of you about possibility of holding it on November 18th
17:50:13 <devkulkarni> are folks still interested in it?
17:50:28 <devkulkarni> basically, what I was thinking
17:50:41 <devkulkarni> we could go through the bug list, which I have tagged recently
17:50:51 <devkulkarni> and triage them
17:50:55 <james_li> I will attend
17:51:01 <devkulkarni> also, exercise the new functionality
17:51:04 <devkulkarni> james_li: great
17:51:26 <devkulkarni> james_li: I will be there too
17:51:38 <muralia1> dev, i might not be available after all. i've got some other thing to wrap up before i take time off for thanksgiving
17:51:49 <devkulkarni> muralia1: sure, no worries
17:52:24 <devkulkarni> vijendar, pt_15: I think you were expressed interest as well, right?
17:52:31 <devkulkarni> s/were/had/
17:52:41 <vijendar> devkulkarni: yes. I am in
17:52:59 <pt_15> devkulkarni: yes, definitely
17:53:09 <devkulkarni> cool
17:53:16 <devkulkarni> thanks vijendar, pt_15
17:53:25 <devkulkarni> that will make at least 4 of us
17:54:03 <devkulkarni> I will setup an etherpad for us for the event
17:54:28 <devkulkarni> November 18th is next Wednesday
17:54:48 <devkulkarni> so we can use the Tuesday meeting to finalize the details about the hackday
17:55:05 <devkulkarni> allocate bugs to triage, try out new functionality, etc.
17:55:18 <devkulkarni> one last point for today
17:55:31 <devkulkarni> 2) Solum-provenance (https://github.com/devdattakulkarni/solum-provenance)
17:55:49 <devkulkarni> I have been keeping track of the git shas of all the dependent services that solum depends on
17:56:17 <devkulkarni> I started doing this because many times one of the services may change something causing solum to break (in the devstack setup)
17:56:39 <devkulkarni> you can use this repo in two ways
17:57:22 <devkulkarni> if in your devstack setup, something fails in some service. you can check the commit of the failing service for which solum is known to work from the above repo
17:57:40 <devkulkarni> revert that service to that commit and then re-try
17:58:06 <devkulkarni> second way you can use this repo is send a pr to it with
17:58:19 <devkulkarni> the commits of the services which worked for you
17:58:42 <vijendar> devkulkarni:  this helps in going back to last working devstack state. correct?
17:58:48 <devkulkarni> yes
17:58:53 <devkulkarni> that is correct vijendar
17:59:00 <vijendar> devkulkarni: nice
17:59:09 <devkulkarni> as an evidence of usefulness of this
17:59:18 <devkulkarni> recently devstack merged a change to add zookeeper
17:59:31 <devkulkarni> for some reason this is not working for us
17:59:50 <devkulkarni> so I went to above repo, and reverted devstack to the commit for which we know solum works
18:00:05 <devkulkarni> and that allowed me to get back to a working devstack setup
18:00:20 <devkulkarni> alright, we are at the end of today's meeting
18:00:29 <devkulkarni> thanks everyone for joining today
18:00:36 <devkulkarni> see you in solum channel
18:00:45 <devkulkarni> #endmeeting