17:00:32 <devkulkarni> #startmeeting Solum Team Meeting
17:00:39 <openstack> Meeting started Tue Mar  1 17:00:32 2016 UTC and is due to finish in 60 minutes.  The chair is devkulkarni. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:40 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:43 <openstack> The meeting name has been set to 'solum_team_meeting'
17:00:46 <devkulkarni> #topic Roll Call
17:00:50 <devkulkarni> Devdatta Kulkarni
17:01:00 <vijendar> o/
17:01:11 <devkulkarni> hi vijendar
17:01:27 <vijendar> hi devkulkarni
17:01:35 <devkulkarni> lets wait for few minutes to see if anyone else is joining us today
17:01:41 <vijendar> sure
17:01:42 <devkulkarni> here is the agenda for today
17:01:49 <devkulkarni> https://wiki.openstack.org/wiki/Meetings/Solum#Agenda_for_2016-01-01_1700_UTC
17:02:43 <james_li> james li
17:02:47 <devkulkarni> hi james_li
17:02:52 <james_li> Hi devkulkarni
17:02:53 <devkulkarni> we have vijendar as well
17:02:59 <devkulkarni> good to see you james_li
17:03:05 <devkulkarni> here is the agenda for today:
17:03:08 <vijendar> hi james_li
17:03:10 <devkulkarni> https://wiki.openstack.org/wiki/Meetings/Solum#Agenda_for_2016-01-01_1700_UTC
17:03:38 <james_li> Hi vijendar
17:04:20 <devkulkarni> I will proceed in a minute
17:04:50 <devkulkarni> alright.. lets begin
17:04:56 <devkulkarni> #topic Announcements
17:05:02 <devkulkarni> I have none prepared
17:05:24 <devkulkarni> #topic Action Items
17:05:33 <devkulkarni> Space for OpenStack summit
17:05:41 <devkulkarni> For Tokyo we had 1 Fishbowl, what should we have for Austin? Options are Fishbowl slots (Wed-Thu), Workroom slots (Tue-Thu), Contributors meetup (Fri)
17:05:46 <devkulkarni> Please add your choices with name to https://etherpad.openstack.org/p/solum-austin-design-summit-space-needs (deadline March 6)
17:05:52 <devkulkarni> let me give some background about this
17:06:29 <devkulkarni> the openstack folks who work towards arranging the summit reached out to all the PTLs recently with question regarding space for Austin summit
17:06:47 <devkulkarni> there are three types of activities that happen during the summit
17:07:02 <devkulkarni> fishbowl, workrooms, contributor's meetup
17:07:18 <devkulkarni> if you check the etherpad, I have added details about each of these
17:07:36 <devkulkarni> a fishbowl session is more of a presentation session
17:07:53 <devkulkarni> workroom session is more about design and discussion
17:08:10 <devkulkarni> I am thinking that we should request 1 fb and 1 workroom session
17:08:19 <james_li> sounds good to me
17:08:25 <devkulkarni> the fb session can be used to showcase current capabilities of solum
17:08:27 <vijendar> make sense
17:08:44 <devkulkarni> workroom session will be where we can get together and plan and discuss features etc.
17:08:47 <devkulkarni> cool
17:08:56 <vijendar> how long workroom session will be?
17:09:12 <devkulkarni> vijendar: good question
17:09:30 <devkulkarni> I think fb slots are 40 minutes and workroom sessions are also 40 minutes
17:09:42 <devkulkarni> at least that is how it was for Tokyo summit
17:10:15 <vijendar> ok
17:10:32 <devkulkarni> the deadline for me to send this info to the organizers is March 6
17:10:39 <devkulkarni> I will check with others as well
17:10:54 <vijendar> may be we need more time for workroom session, but 40mins is OK
17:10:57 <devkulkarni> at the minimum, I will request 1 fb and 1 workroom session
17:11:00 <james_li> we are not sure if we can get both, right?
17:11:08 <devkulkarni> james_li: yes, that is correct
17:11:19 <devkulkarni> there is no guarantee that we will get both
17:11:21 <james_li> if there will be only one for us, which should we go?
17:11:40 <devkulkarni> good question james_li
17:12:04 <devkulkarni> in that case, there are advantages to have a fishbowl session over workroom session
17:12:13 <james_li> agree
17:12:20 <devkulkarni> what do you think vijendar?
17:12:56 <vijendar> probably fb is good
17:13:57 <james_li> devkulkarni: we need to prepare some demos for the fb?
17:14:23 <devkulkarni> james_li: yes, we should
17:14:35 <james_li> and how about our talks?
17:14:48 <devkulkarni> once we start getting closer to the date of the summit, I will pull you all in to discuss what kind of demo we want to do
17:14:55 <devkulkarni> james_li: no word on the talks yet
17:15:12 <devkulkarni> I am guessing that sometime in next couple of weeks we will know
17:15:38 <james_li> for the demos, I'd suggest not to use devstack, but run solum on a cloud server, and maybe deploy apps to real carina prod.
17:15:52 <devkulkarni> ++ james_li
17:15:58 <james_li> thats the best from my point of view
17:16:04 <vijendar> +1 james_li
17:16:07 <devkulkarni> I agree
17:16:20 <devkulkarni> we should do that
17:16:33 <james_li> cool
17:16:57 <devkulkarni> good discussion
17:17:11 <devkulkarni> let me move on to the next topi
17:17:14 <devkulkarni> topic
17:17:24 <devkulkarni> #topic Bug Review
17:17:44 <devkulkarni> I thought we can discuss about some recent new bugs
17:17:51 <devkulkarni> lets start with
17:18:02 <devkulkarni> 1) Separate app-data from param-data
17:18:04 <devkulkarni> https://bugs.launchpad.net/solum/+bug/1531609
17:18:04 <openstack> Launchpad bug 1531609 in Solum "Separate app-data and param-data" [Low,New]
17:18:24 <devkulkarni> ciello just pinged us on solum irc channel about this bug
17:18:40 <devkulkarni> seems like ciello is interested in working on it
17:18:50 <devkulkarni> vijendar: this is the bug that you had created
17:19:08 <devkulkarni> could you weigh in on the bug and answer questions that ciello might have
17:19:21 <vijendar> sure
17:19:47 <devkulkarni> on solum irc channel ciello mentioned that the bug is not reproducible
17:20:44 <devkulkarni> thanks vijendar
17:21:07 <devkulkarni> 2) App delete receiving stack not found
17:21:12 <devkulkarni> https://bugs.launchpad.net/solum/+bug/1548382
17:21:12 <openstack> Launchpad bug 1548382 in Solum "app-delete-receiving-stack-not-found" [Critical,New]
17:21:29 <vijendar> I am setting up my dev env to repro this issue
17:21:35 <devkulkarni> vijendar: cool
17:21:47 <devkulkarni> I can assign it to you?
17:22:16 <vijendar> sure
17:22:51 <devkulkarni> cool
17:23:28 <devkulkarni> there are few other bugs
17:23:44 <devkulkarni> 3) Cleanup output of app show
17:23:48 <devkulkarni> https://bugs.launchpad.net/python-solumclient/+bug/1545829
17:23:48 <openstack> Launchpad bug 1545829 in python-solumclient "clean-up-output-of-solum-app-show" [Undecided,New]
17:24:30 <devkulkarni> this one is to clean up output of app show
17:24:39 <devkulkarni> should be easy to fix
17:24:44 <devkulkarni> I can take care of it
17:25:20 <devkulkarni> 4) Create admin api to set per tenant limits
17:25:25 <devkulkarni> https://bugs.launchpad.net/solum/+bug/1546271
17:25:25 <openstack> Launchpad bug 1546271 in Solum "create-admin-api-to-set-per-tenant-limits" [Wishlist,New]
17:25:54 <devkulkarni> this one came about from our need to limit the number of apps and then number of instances of an app that can be created
17:26:35 <devkulkarni> where else we might want admin api?
17:26:53 <devkulkarni> dynamically changing deployer configuration?
17:27:03 <devkulkarni> say for instance, using heat vs. using carina?
17:27:17 <vijendar> sure. that makes sense
17:28:15 <vijendar> may be an endpoint to list all the users apps… something similar to heat admin api
17:28:18 <devkulkarni> in our current architecture, we will have to restart the deployer to take this effect
17:28:55 <devkulkarni> vijendar: good point.. although I think we can just use 'solum app list' with admin token to do this
17:28:57 <vijendar> to support this, we need to re-architect
17:29:39 <devkulkarni> agree — to support dynamically changeable deployer backends we might need to re-architect our code
17:30:16 <devkulkarni> vijendar: good discussion
17:30:22 <devkulkarni> I will add this to the bug description
17:30:37 <devkulkarni> 5) Keystone changes affecting devstack plugin
17:30:41 <devkulkarni> https://bugs.launchpad.net/solum/+bug/1544286
17:30:41 <openstack> Launchpad bug 1544286 in Solum "keystone-changes-affecting-devstack-plugin" [High,New] - Assigned to Dimitry Ushakov (dimalg)
17:31:09 <devkulkarni> this one is related to keystone changes that might break our plugin
17:31:43 <devkulkarni> dimtruck was going to look into it, I will ping him to see if there is any progress on this
17:32:19 <devkulkarni> vijendar: are there any bugs that you want to bring to team's attention?
17:32:44 <devkulkarni> even if you have not yet filed them but have encountered, we can discuss about them
17:32:59 <vijendar> no
17:33:12 <devkulkarni> alright
17:33:19 <vijendar> wait
17:33:23 <devkulkarni> ok
17:33:30 <vijendar> may be the vagrant setup
17:33:37 <devkulkarni> vijendar: ok, makes sense
17:33:51 <devkulkarni> we have several bugs related to vagrant setup
17:33:59 <devkulkarni> some of them are obsolete
17:34:17 <devkulkarni> I will go through them and check
17:34:22 <vijendar> ok
17:34:54 <devkulkarni> for the current setup issues — I will send a PR to the vagrant repo and link it to a bug if one exists
17:35:06 <devkulkarni> otherwise I will create a new bug and add the PR to it
17:35:22 <devkulkarni> note that vagrant related bugs won't be managed by gerrit
17:35:30 <devkulkarni> as the vagrant repo is not managed by gerrit
17:36:15 <devkulkarni> #topic Patches for Review
17:36:29 <devkulkarni> 1) Validate app schema
17:36:29 <devkulkarni> https://review.openstack.org/#/c/282544/
17:36:44 <devkulkarni> vijendar: let me review this right now
17:36:51 <vijendar> devkulkarni: thanks
17:37:01 <vijendar> james_li: please take a look when you get a chance
17:38:50 <devkulkarni> vijendar: added a comment
17:39:09 <devkulkarni> the enum should contain "unittest" instead of "test"
17:39:23 <vijendar> devkulkarni: sure. will update the ptach
17:39:26 <vijendar> *patch
17:39:35 <devkulkarni> sounds good.. rest looks good
17:40:00 <devkulkarni> 2) Solum Mitaka releases
17:40:01 <devkulkarni> https://review.openstack.org/#/c/284200/
17:40:14 <devkulkarni> I had submitted this last week
17:40:30 <devkulkarni> I will update this to include the latest commits
17:40:53 <devkulkarni> are there any other patches to review?
17:41:24 <devkulkarni> there was a patch that changed the tempest lib import .. it unblocked the devstack gate
17:41:30 <vijendar> https://review.openstack.org/#/c/257002/
17:41:42 <vijendar> can we get this merged one line doc change
17:41:55 <devkulkarni> vijendar: makes sense
17:41:58 <vijendar> this is hanging there for a long time
17:42:18 <devkulkarni> agreed
17:42:27 <vijendar> we need one +2 from james_li or murali
17:42:34 <devkulkarni> vijendar: yep
17:42:50 <vijendar> devkulkarni: or you can +2
17:42:58 <devkulkarni> I had submitted it to test the setup of my other account
17:43:19 <vijendar> ok
17:43:24 <devkulkarni> I think one of the other cores can quickly approve it
17:43:46 <vijendar> sure
17:43:49 <devkulkarni> vijendar: I was looking at your patch to validate if lp exists or not
17:43:59 <devkulkarni> it seems to be failing functionaltests
17:44:00 <vijendar> I need to fix tests for that
17:44:05 <vijendar> yeah
17:44:09 <devkulkarni> haven't looked into the details
17:44:12 <devkulkarni> ok
17:44:13 <vijendar> I am setting up environment to fix those tests
17:44:42 <vijendar> will update the patch soon (hopefully today)
17:44:56 <devkulkarni> sounds good
17:45:06 <devkulkarni> alright
17:45:13 <devkulkarni> lets move to Open discussion
17:45:23 <devkulkarni> #topic Open Discussion
17:45:46 <devkulkarni> Here are the major updates from upstream in the last week
17:45:52 <devkulkarni> 1) Request ID tagging
17:45:56 <devkulkarni> http://lists.openstack.org/pipermail/openstack-dev/2016-March/087878.html
17:46:03 <devkulkarni> vijendar: you might be interested in this
17:46:21 <vijendar> devkulkarni: sure
17:46:28 <devkulkarni> this is discussion about how to add a request id to track requests across different services
17:46:46 <devkulkarni> I know you had some ideas about this
17:47:42 <vijendar> yeah…I was thinking about using open repose to solve this issue
17:47:52 <devkulkarni> oh cool
17:48:17 <devkulkarni> we could integrate that with solum
17:48:45 <vijendar> sure
17:48:56 <devkulkarni> cool
17:49:21 <devkulkarni> second update is basically the continued discussion about separation of the design summit from the main conference
17:49:50 <devkulkarni> I am sure we will hear about this topic a lot in the Austin summit
17:50:42 <devkulkarni> third update is related to the CORS patch
17:51:16 <devkulkarni> check this: http://lists.openstack.org/pipermail/openstack-dev/2016-March/087944.html
17:52:01 <devkulkarni> I need to go back and check the discussion.. this email goes back to how CORS support was added
17:52:15 <devkulkarni> we have already merged the original patch that added CORS support in Solum
17:52:35 <devkulkarni> we don't use paste.ini
17:52:48 <devkulkarni> so probably we don't have to do anything
17:53:10 <devkulkarni> will have an update once I go through the discussion
17:54:20 <devkulkarni> that is all I had for major upstream updates
17:55:12 <devkulkarni> anything else we should discuss today
17:55:13 <devkulkarni> ?
17:55:44 <vijendar> none from me
17:56:22 <devkulkarni> alright then
17:56:30 <devkulkarni> thanks vijendar and james_li for joining today
17:56:34 <devkulkarni> see you next week
17:56:40 <devkulkarni> #endmeeting