14:31:10 <j^2> #startmeeting Openstack-Chef
14:31:11 <openstack> Meeting started Thu Mar 26 14:31:10 2015 UTC and is due to finish in 60 minutes.  The chair is j^2. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:31:12 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:31:15 <openstack> The meeting name has been set to 'openstack_chef'
14:31:17 <j^2> hey everyone!
14:31:34 <sc`> o/
14:32:43 <markvan> hello
14:33:38 <cmluciano> o/
14:33:49 <j^2> :)
14:34:09 <j^2> with the blueprint movement, i think it's safe to say we have a first pass at what we'd like done for kilo
14:34:22 <cmluciano> \o/
14:34:30 <cmluciano> Did you get my emails?
14:34:56 <sc`> unrelated, i've been talking with coworkers about upstreaming things that make sense, starting small to get over the learning curve
14:35:33 <cmluciano> Looks like Sahara is a no go unless someone here wants to step up and lead. Also Pierre does not have time to finish those tests. I think @markvan said that he might finish them up.
14:35:47 <j^2> cmluciano: cool, that works
14:35:57 <j^2> sc`: nice!
14:36:26 <markvan> yup, I'll talke a look at the tests at some point, I'll update the blueprint to take effect
14:37:24 <openstackgerrit> Ma Wen Cheng proposed stackforge/cookbook-openstack-image: Use 'identity_uri' to configure admin URI for kilo  https://review.openstack.org/168015
14:39:45 <sc`> j^2: one change already came out of those discussions, too
14:40:53 <j^2> we need to continue with the reviews like always
14:41:13 <j^2> @core please if you have time check the patches and +2 or +WF where you can
14:41:13 <os-chef-bot> @j^2 @markvan @mattray @wenchma @jklare @cmluciano please if you have time check the patches and +2 or +WF where you can
14:42:37 <sc`> as we get more aligned to how things work and should work wrt code style and project goals, more patches should bubble up
14:42:41 <markvan> Yeah, for patches, as you can see, with the moveto kilo, there are a bunch of cleanups in progress.   I wish I could share my "starred" list easily.
14:43:15 <markvan> For example, there are several repo related ones that are ready.
14:43:28 <markvan> https://review.openstack.org/#/q/status:open+project:stackforge/openstack-chef-repo,n,z
14:44:56 <markvan> And to hightlight a few others that are ready: https://review.openstack.org/#/q/status:open++branch:master+topic:bug/1433405,n,z   most of the test is already in.
14:45:31 <markvan> And one critical patch that currently is breaking tests is: https://review.openstack.org/#/c/167891/
14:46:12 <sc`> though i know all new work goes into master, is stable/icehouse completely frozen to changes? i don't have anything in mind, but just to satisfy curiosity
14:46:53 <j^2> sc`: more or less, yeah.
14:47:04 <j^2> unless you find crazy breaking changes, we can backport
14:47:09 <j^2> we try to do n-1
14:47:10 <j^2> support
14:47:11 <sc`> ok, cool
14:47:24 <sc`> i thought that was the case
14:47:26 <markvan> Checkout the wiki for branch status.  Usually we have last stable release open, and in fact we have already patched stable/juno once: https://review.openstack.org/#/c/164788/
14:47:43 <markvan> https://wiki.openstack.org/wiki/Chef/GettingStarted at bottom
14:48:12 <sc`> for some reason my bookmark for that disappeared
14:48:22 <sc`> bookmarked again, thanks
14:49:13 <markvan> yeah, trying to make the wiki a good place for general info, any comments on it are welcome!
14:51:19 <j^2> oh, so next week
14:51:23 <j^2> it's ChefConf
14:51:46 <j^2> I can't run the meetings on monday or thursday being unavailable
14:51:56 <cmluciano> I will also be away
14:52:21 <markvan> I can help with running the meetings
14:52:38 <sc`> i'll be at chefconf as well, with a contingent of my colleagues
14:52:46 <j^2> nice!
14:52:58 <j^2> markvan: sounds good
14:53:02 <sc`> one of our guys is presenting, too
14:53:25 <cmluciano> def all should meetup
14:53:34 <j^2> seems like something that needs to happen
14:53:39 <cmluciano> Just need @markvan
14:53:43 * markvan wow, i have to push harder to make chefconf travel happen...
14:53:47 <j^2> heh
14:54:34 <j^2> markvan: ibm is suppsode to be there in force too
14:54:48 <j^2> maybe you can offer you services to fill in :)
14:57:13 <markvan> bummer, yeah would like to meet some of those ibmers in person...
14:57:31 <j^2> i think it's all do to the POWER work
14:57:41 <j^2> i could be wrong though
14:58:54 <markvan> ah, ok Power is always a fun topic
15:00:08 <j^2> cool, any one would like to take the floor for a topic?
15:01:23 <markvan> I have a few...
15:01:28 <j^2> go ahead
15:01:35 <sc`> i don't know if this is necessarily a whole topic in and of itself, but how do i keep up with changes in the pipeline? i want to start shifting my efforts more in the direction of working off of master, and want a better grasp of how it's currently done
15:01:56 <markvan> #topic  new "service" role  https://review.openstack.org/#/q/status:open++branch:master+topic:bug/1436050,n,z
15:03:26 <markvan> Just a quick update on this one.  We have been using a "service" user for a long time with the default "admin" role.   Now keystone has changed to by default have a new "service" role.   So, these patches are to use that new role, we should notice no differences in our tests.
15:04:06 <sc`> awesome. the least privilege that can be given, the better
15:04:42 <markvan> yup, exactly, and you will see in the keystone policy.json, that the service role is now being used to separate admin from service a bit
15:05:17 <markvan> #topic  remove api-paste.ini   https://review.openstack.org/#/q/status:open+branch:master+topic:bug/1433152,n,z
15:05:41 <sc`> moving things out of admin will make my security guys very happy
15:05:56 <markvan> Another quick update.  As i was trying to get conf's sync'd with latest kilo changes, I noticed that many of the api-paste.ini were out of date.
15:06:46 <markvan> Also, we had a tempate for them that had no logic or templates, so I think it best to just remove these templates until such a time as we truely need them, that will reduce our release to release sync work.
15:07:05 <markvan> (we did the same for the policy files in icehouse)
15:07:26 <markvan> the api-paste.ini files are shipped with the packages straight from the base openstack source.
15:08:12 <wenchma> yeah,
15:08:24 <wenchma> there is no need duplciate them
15:08:28 <sc`> makes sense
15:08:52 <markvan> k, cool.
15:09:01 <markvan> #topic  identity_uri   https://review.openstack.org/#/q/status:open+branch:master+topic:bp/identity-uri,n,z
15:10:04 <markvan> I also started on this blueprint.   After reviewing the existsing code, I decided to make the recipes clean by creating a new helper method in Common since the identity_uri is slightly different from the endpoint.
15:10:23 <wenchma> identity_uri affects all components
15:10:29 <markvan> I have updated the blueprint and put out the starting patches, I think they are fairly straight forward.
15:11:06 <markvan> yup, I started with block-storage as an example to go with the common patch I did.  Once those are done, I will push up all the others
15:11:15 <wenchma> need the openstack-common lib patch merged first
15:11:26 <wenchma> for other patches jenkins pass
15:11:41 <markvan> yes
15:12:26 <markvan> btw, I working on a new version of the testing repo patch script to allow multiple patches to be pulled in, like in this case where a Common + component patch is needed.  Will make it very easy to test these out.
15:12:49 <wenchma> looks better that  add a method identity_uri_transform
15:13:31 <markvan> yeah, I think that's the right design for what the cookbooks are doing now with regards to the other public uri,   auth_uri.
15:16:24 <markvan> sc`: did you want to discuss how to keep up with changes in the pipeline?
15:29:16 <markvan> j^2: my last topic was about reviews, since were knee deep in kilo changes, we need a bit more focus on reviews to keep the back log down to a reasonable size.   I would like to suggest again that we come up with some "Office hours" where at least the cores go at the reviews
15:30:27 <j^2> i think the challange is to get everyone available
15:30:29 <markvan> maybe twice a week for an hour or so?   And allow folks to come in an help explain their review needs/coments/qyuestions
15:31:19 <j^2> it’s a great idea in theory; we’d have to make it Wednesday, i’m betting
15:31:21 <markvan> yeah, but we could try maybe a morning session and an evening session?  with at least 2 cores present to make it work...
15:32:22 <markvan> Maybe can poll on the ML to get more feedback on that...
15:32:27 <j^2> yeah
15:32:36 <markvan> I'll start that thread.
15:34:01 <markvan> btw, I've been meaning to ask....if there a way to have our ML updates (summary/title line) posted here, like is done with the patches?
15:34:44 <markvan> might make it easier to link the ML to a wider audience here in the irc...
15:38:51 <j^2> yeah
15:38:57 <j^2> so i think there’s a way
15:39:02 <j^2> but it’s not great not atm
15:39:08 <j^2> #endmeeting