14:00:32 <devkulkarni> #startmeeting Solum Team Meeting
14:00:38 <openstack> Meeting started Wed Mar  8 14:00:32 2017 UTC and is due to finish in 60 minutes.  The chair is devkulkarni. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:39 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:41 <openstack> The meeting name has been set to 'solum_team_meeting'
14:01:09 <devkulkarni> hi zhurong
14:01:22 <zhurong> hi devkulkarni
14:01:36 <devkulkarni> I just started our meeting
14:01:46 <devkulkarni> here is the agenda
14:01:52 <devkulkarni> https://wiki.openstack.org/wiki/Meetings/Solum#Agenda_for_2017-03-08_1400_UTC
14:02:38 <devkulkarni> lets wait to see if caowei or vijendar or others join today
14:05:25 <devkulkarni> alright, lets start
14:05:29 <zhurong> seems they missing today meeting
14:05:33 <devkulkarni> right
14:05:59 <devkulkarni> we can go over the agenda items and discuss
14:06:14 <devkulkarni> #topic Discussion
14:06:38 <devkulkarni> So I wanted touch base about some recent emails on the dev mailing list
14:06:47 <devkulkarni> 1) Devstack to make glance version 2 as default
14:07:07 <devkulkarni> http://lists.openstack.org/pipermail/openstack-dev/2017-March/113314.html
14:08:29 <devkulkarni> we are using glance version 1 in some places https://github.com/openstack/solum/blob/master/contrib/lp-cedarish/docker/build-app#L55
14:08:35 <zhurong> seems not affect us too much
14:08:56 <devkulkarni> https://github.com/openstack/solum/blob/master/contrib/lp-cedarish/docker/build-lp#L31
14:09:18 <devkulkarni> these are the two places where we explicitly depend on glance version 1
14:09:58 <devkulkarni> In the email they have mentioned how to enable glance version 1 by setting some config variable
14:10:30 <zhurong> yep, we just enable v1 in the settings
14:10:40 <devkulkarni> right
14:10:54 <devkulkarni> although, the recommended approach is to convert to using glance v2
14:11:02 <devkulkarni> let me create a bug to track this work
14:11:47 <zhurong> cool
14:13:11 <devkulkarni> https://bugs.launchpad.net/solum/+bug/1671115
14:13:11 <openstack> Launchpad bug 1671115 in Solum "glance-v1-to-v2" [Undecided,New]
14:13:49 <devkulkarni> we can check with pt_15 if she wants to take up that
14:14:13 <devkulkarni> so the second thing was about Tempest making Keystone v3 as default
14:14:22 <devkulkarni> http://lists.openstack.org/pipermail/openstack-dev/2017-March/113487.html
14:14:48 <zhurong> agree
14:15:55 <devkulkarni> zhurong: it will also be a good idea to check if someone from your org/team wants to take up the glance bug. It is small enough and provides a easy way to get started with solum
14:16:29 <devkulkarni> *reading back on the tempest email*
14:17:25 <zhurong> If no one fix this, I will take over this
14:18:03 <devkulkarni> zhurong: looks like devstack is going to change keystone version to v3 for tempest: https://review.openstack.org/#/c/441531/
14:18:41 <devkulkarni> your v3 patch is important
14:18:56 <devkulkarni> https://review.openstack.org/#/c/439427/
14:19:13 <devkulkarni> I am just waiting on caowei to give a +1 on it
14:19:34 <devkulkarni> if you see him, can you ping me about it
14:19:39 <devkulkarni> then we can merge your patch
14:19:39 <zhurong> we can wait for the tempest v3 patch merged, and check our gate
14:20:15 <devkulkarni> good point.. I was wondering if there is anything on our server side that we need to change to enable keystone v3 support?
14:22:12 <zhurong> I think there should have some change to enable keystone v3 in server side
14:22:57 <devkulkarni> I see. Looks like we might need some investigation to figure out what the server-side changes would be.
14:23:14 <devkulkarni> Let me make a note of this on the keystone v3 bug that you have referenced in your patch
14:23:18 <zhurong> yep, agree with this
14:26:50 <devkulkarni> zhurong: added a comment to the bug: https://bugs.launchpad.net/solum/+bug/1662457
14:26:50 <openstack> Launchpad bug 1662457 in Solum "solum devstack keystone v3 support" [High,New] - Assigned to zhurong (zhu-rong)
14:27:32 <zhurong> OK, thanks
14:27:57 <devkulkarni> cool, lets then talk about the heat deployer patch
14:28:22 <devkulkarni> 3) Change heat client auth way: https://review.openstack.org/#/c/425001/
14:29:13 <devkulkarni> what are your thoughts on this? does my comment make sense?
14:29:39 <zhurong> yes, I agree with your comment
14:29:57 <zhurong> And just now, I have no idea about this. :(
14:30:12 <devkulkarni> *re-reading the comments*
14:32:43 <devkulkarni> okay, so this particular patch is referenced in the replace-nova-docker blueprint..is the replacement (zun) working when using solum cli? (i.e. when using zun as the driver, are we able to deploy apps using the cli?)
14:34:05 <zhurong> I am using dashboard, If change like the patch, it can deploy apps, and I think, cli it also can
14:35:04 <devkulkarni> ah I see. so the patch will not make github triggers to work
14:35:40 <zhurong> I this it is not releated
14:35:49 <zhurong> I think it is not releated
14:37:02 <devkulkarni> it is sort of related actually.. see the heat client that we generate need to have appropriate permissions to perform heat operations
14:37:40 <devkulkarni> when using the context token, as long as it is the user token, the heat client would have these permissions
14:38:26 <zhurong> yep, no need to auth and generate another token
14:38:27 <devkulkarni> but when a trigger is received from github web hook, the token is not user token
14:40:29 <devkulkarni> your suggestion of asking for username/password on the dashboard for registering github trigger
14:40:50 <devkulkarni> but we can do that in a follow-up patch
14:41:09 <zhurong> yes, when using github trigger, this need special deal with
14:41:50 <devkulkarni> so right now, what do you think of using a special header that is passed when the request comes from the dashboard
14:42:11 <devkulkarni> we can use that header to generate the heat client using the context token
14:42:41 <devkulkarni> if that header is not present, we continue using the previous approach (of using username/password in generating heat client)
14:43:03 <devkulkarni> this will ensure that app deployment will work from command line and from dashboard
14:43:33 <devkulkarni> it will also ensure that apps that are registered from the cli and for which we have setup github triggers, will work
14:43:56 <zhurong> I think cli will also have the token, let me conform this
14:44:24 <devkulkarni> the cli workflow also has the token -- that is not the issue actually
14:45:48 <zhurong> when using github triggers, all cli and dashboard need provider the username/password, and the username/password only used for github triggers
14:46:19 <zhurong> heat client auth with the token in the context
14:47:32 <devkulkarni> sure, so another way would be to detect that app deployment is actually coming from github trigger (https://github.com/openstack/solum/blob/master/solum/api/controllers/v1/trigger.py#L76)
14:47:47 <devkulkarni> and then generate the heat client using username/password
14:48:04 <devkulkarni> yeah, probably that can be done as well
14:49:26 <devkulkarni> zhurong: just to confirm you have tested that this change https://review.openstack.org/#/c/425001/5/solum/deployer/handlers/heat.py works from dashboard and cli when using zun, right
14:49:57 <zhurong> I will conform with cli
14:50:04 <zhurong> dashboard I have confirmed
14:50:07 <devkulkarni> ok, cool.
14:52:08 <devkulkarni> lets do this then.. once you confirm that the change works with cli as well, we can merge it with slight modification -- the modification being, lets leave the get_heat_client method as it is.. we can add a note that we will need that method for handling github triggers. will add detail comment on the patch.
14:53:11 <zhurong> sure
14:53:16 <devkulkarni> cool
14:53:29 <devkulkarni> lets quickly talk about releases..
14:53:38 <devkulkarni> any upcoming release deadlines for pike?
14:53:57 <zhurong> for pike?
14:54:37 <devkulkarni> https://releases.openstack.org/pike/schedule.html
14:54:38 <zhurong> we need  release deadlines for pike now?
14:54:55 <devkulkarni> just checking if there are any upcoming deadlines
14:55:19 <devkulkarni> for ocata we have released all the artifacts, right?
14:56:00 <devkulkarni> zhurong: for pike, p-1 is when we have acknowledge the community-wide goals
14:56:03 <devkulkarni> https://releases.openstack.org/pike/schedule.html#p-1
14:56:04 <zhurong> yes, are the repo have the stable/ocata
14:56:50 <devkulkarni> yep, all our repos have ocata
14:56:58 <devkulkarni> good job on it
14:57:30 <devkulkarni> zhurong: for acknowledging community goals, I would encourage you to take a look at https://governance.openstack.org/tc/goals/pike/index.html
14:57:44 <devkulkarni> there is a patch that we need to submit for each of the goals
14:58:07 <devkulkarni> the patch needs to essentially list what we have completed, what is remaining, tentative timeline
14:58:35 <devkulkarni> oh, looks like we are at the end of our meeting time almost
14:58:45 <zhurong> yep
14:58:49 <devkulkarni> any thing that you wanted to discuss?
14:59:05 <devkulkarni> we can continue in our channel anyways
14:59:08 <zhurong> np
14:59:35 <devkulkarni> alright
14:59:47 <devkulkarni> let me know how the zun deployment goes from the cli then
14:59:58 <zhurong> ok, I will
15:00:02 <devkulkarni> good discussion today
15:00:09 <devkulkarni> see you next week for the meeting
15:00:13 <devkulkarni> #endmeeting