12:44:15 <ttx> #startmeeting incub_sync 12:44:16 <openstack> Meeting started Thu Jul 10 12:44:15 2014 UTC and is due to finish in 60 minutes. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:44:17 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 12:44:20 <openstack> The meeting name has been set to 'incub_sync' 12:44:23 <ttx> #topic Designate 12:44:26 <Kiall> No problem 12:44:29 <Kiall> I missed the first one ;) 12:45:06 <ttx> so I updated the PTL guide 12:45:13 <ttx> to reflect current state 12:45:23 <Kiall> I saw, thank you. 12:45:33 <ttx> Also updated the Branch model 12:45:42 <ttx> https://wiki.openstack.org/wiki/Branch_Model 12:45:52 <Kiall> I started reading it yesterday - but got sidetracked by an issue 12:46:10 <ttx> https://launchpad.net/designate/+milestone/juno-2 12:46:21 <ttx> Looks good, two remarks 12:46:41 <ttx> "Undefined" priorities: you should set a priority there 12:47:03 <ttx> In most reporting we ignore blueprints that don't have a priority set 12:47:12 <ttx> since it's the only field the PTL and other drivers control 12:47:17 <Kiall> Sure - I'll update those after out meeting 12:47:25 <ttx> so it lets us make sure you blessed it 12:47:32 <ttx> and it wasn't just added by some random bystander 12:47:33 <Kiall> Ahh - Okay, so it's more important than simple priority then :) 12:47:51 <ttx> if "Undefined" we consider it's not really approved, basically 12:48:03 <ttx> we play tricks around Launchpad limitations :) 12:48:14 <Kiall> Noted - I'll make sure the core team knows this and update the current BPs 12:48:21 <ttx> Second remark is about zone-migration-between-tenants 12:48:29 <ttx> it's not started but targeted to j2 12:48:44 <ttx> so unless it's really small, it probably will miss the mark 12:48:47 <Kiall> Ah - I expect Graham will have that up for review before Monday 12:48:59 <ttx> ok, so he probably started working on it :) 12:49:03 <Kiall> while DNSupdate API - simplified DDNS update does need to be pushed 12:49:05 <ttx> so status shall be "Started" 12:49:34 <Kiall> I'll give him a slap on the wrist for not keeping it updated ;) 12:50:06 <ttx> does taht list reflect all that's being currently added ? 12:50:47 <Kiall> Not quite - I believe there is 1 "MiniDNS" BP not targeted to j2 which rackspace surprised us with a review for last night. 12:50:59 <ttx> ok, so probably worth a add 12:51:03 <ttx> As far as J2 goes, it's just about giving the milestone release manager a SHA that you're comfortable with to mark the milestone 12:51:24 <ttx> (at the same time, defer incomplete bugs and features to next milestone) 12:51:26 <Kiall> yes, during release week - preferably not on the day I believe :) 12:51:39 * ttx shall create juno-" milestone there 12:51:42 <ttx> juno-3 12:51:59 <Kiall> I was just trying to do that - I guess I lost permission when I reassigned to Openstack Admins? 12:52:12 <ttx> no, you should be able to do that as a Designate driver 12:52:22 <ttx> but don't worry i'll do it 12:52:25 <Kiall> Then LP just has me confused - it usually does. 12:53:50 <Kiall> Should I be able to create it from here? https://launchpad.net/designate/juno (Just looking for future reference) 12:53:59 <ttx> yes 12:54:13 <ttx> there should be a "create milestone" link somewhere 12:54:28 <Kiall> Ctrl+F "create" .. 0 results.. weird 12:54:51 <ttx> do you see the Milestones and releases" list ? 12:55:01 <Kiall> yes 12:55:13 <ttx> Just below it is a "Create milestone Create release" line? 12:55:21 <ttx> (I suspect there isn't for you) 12:55:28 <Kiall> There isn't :) 12:55:43 <ttx> Hmm, are you logged in ? How about going to https://launchpad.net/designate/juno/+addmilestone directly ? 12:55:51 <Kiall> Not allowed here 12:55:56 <Kiall> I think I see it though 12:56:06 <Kiall> I'm a member of drivers via the included designate-core group 12:56:16 <Kiall> I can fix that later, I'm still admin on the groups 12:56:56 <ttx> hmm, still a bit weird 12:57:10 <Kiall> And.. That didn't do it 12:57:33 <Kiall> Funny enough.. https://launchpad.net/designate/+addseries works.. So.. I expect it's a LP bug 12:57:49 <ttx> Hmm. On https://launchpad.net/~designate-drivers does it make you a member of the team ? 12:58:02 <ttx> should show "you are a member" or something 12:58:20 <Kiall> Owner: 12:58:20 <Kiall> Kiall Mac Innes 12:58:21 <Kiall> and direct members list includes me 12:58:31 <Kiall> "You own this team." 12:58:51 <ttx> hmm 12:59:44 <Kiall> I suspect it's LP being .. LP, It'll probably work in an hour :) 13:00:16 <ttx> hmm, no, in fact you need to stay maintainer 13:00:22 <ttx> that's what the other projects di 13:00:24 <ttx> do 13:00:26 <Kiall> doh :) 13:00:28 <ttx> let me check something first 13:01:07 <ttx> ah. got it 13:01:31 <ttx> so the project shall have designate-drivers as maintainers, but designate-drivers shall be owned to openstack-admins 13:01:39 <ttx> the openstack-admins removes itself from the group 13:01:58 <ttx> but can still assume admin in case we need to maintain the group content for some reason 13:02:08 * ttx fixes 13:02:47 <ttx> Kiall: can you change owner on https://launchpad.net/~designate-drivers ? (to ~openstack-admins) ? 13:02:57 * ttx fixes maintainer on designate project itself 13:03:38 <Kiall> Done - should I do the same for designate-core? 13:03:42 <ttx> Kiall: you can add yourself as direct member and "admin" before changing owner 13:03:48 <Kiall> Already done 13:03:50 <ttx> Kiall: yes 13:04:12 <ttx> basically all groups are owned by openstack-admins so that we can fix stuff (without being part of the groups themselves) 13:04:31 <ttx> sorry I made you grant te wrong perms last week :) 13:04:54 <Kiall> No problem -core and -drivers changed 13:05:00 * ttx removes openstack-admins from the members list 13:05:20 <ttx> so we can assume admin, but you'll see if we do :) 13:05:43 <ttx> Kiall: ok, you should see the "create milestone" thing now 13:06:00 <Kiall> Yes, that works now :) 13:06:07 <ttx> ...and that will be enough for this week :) 13:06:13 <ttx> Talk to you next week! 13:06:16 <Kiall> Thanks :) 13:06:26 <Kiall> (BTW I've started fixing the BPs etc @ https://launchpad.net/designate/+milestone/juno-2 ) 13:07:05 <ttx> ack 13:08:52 <Kiall> Note to self: enforce BP links in commit messages -_- 15:31:45 <ttx> jraim: around? 15:31:51 <jraim> yep 15:31:58 <ttx> #topic Barbican 15:32:26 <ttx> jraim: hi! 15:32:43 <ttx> I actually made you make wrong launchpad changes recently 15:32:55 <ttx> so I need to fix that 15:32:56 <jraim> ha, oh really? Which ones were those? 15:33:12 <ttx> apparently if you're not a "maintainer" you can't do some things on the project anymore 15:33:29 <ttx> so barbican-drivers needs to be project maintainer 15:33:41 <ttx> and openstack-admins needs to "own" it 15:33:51 <jraim> ahh, okay. That should be easy 15:34:13 <ttx> so I made the change to return the team as maintainer 15:34:36 <ttx> Douglas Mendiz�bal will need to set ownership of https://launchpad.net/~barbican-drivers to ~openstack-admins 15:34:46 <ttx> since he is the current owner 15:34:53 <jraim> okay, I'll let him know 15:35:15 <ttx> (fwiw I'll remove openstack-amdins from the team members, they just need to "own" the team 15:35:24 <ttx> sorry for the confusion 15:35:28 <jraim> no worries 15:35:41 <ttx> Looking at https://launchpad.net/barbican/+milestone/juno-2 15:36:33 <ttx> I see two "not started" blueprints still being targeted at j2 15:36:41 <ttx> is that smallish enough to make it in time ? 15:36:54 <jraim> We landed a _lot_ of stuff at the mid-cycle. We're catching Launchpad up today 15:37:08 <ttx> ok, just add stuff to it 15:37:19 <jraim> Will do 15:37:59 <ttx> Like I told Kiall earlier, I refreshed https://wiki.openstack.org/wiki/PTL_Guide, so it's current again 15:38:48 <jraim> oh great, I'll take a look 15:38:52 <ttx> As far as J2 goes, it will just be about giving the milestone release manager a SHA that you're comfortable with to mark the milestone, sometimes between Tuesday and Thursday on the J2 week 15:39:07 <ttx> (and at the same time, defer incomplete bugs and features to next milestone) 15:39:24 <jraim> perfect. We talked a bit about it at the mid-cycle. We're mostly in bug fix / clean up mode to be ready for the j2 15:39:29 <ttx> That's all I had... questions? 15:40:02 <jraim> Nothing from us right now 15:40:08 <ttx> ok, talk to you next week then 15:40:14 <ttx> kgriffs: around? 15:41:10 <kgriffs> yep 15:41:12 <ttx> #topic Marconi 15:41:26 <ttx> Just fixed permissions for marconi-drivers on the LP project 15:41:35 <ttx> should be all ok now 15:41:44 <kgriffs> cool 15:42:10 <ttx> https://launchpad.net/marconi/+milestone/juno-2 15:42:26 <ttx> Looks a bit behind, is the status there current? 15:42:48 <ttx> (juno-2 is in 12-14 days) 15:43:04 <kgriffs> I just started looking at it this morning. I've been on vacation the past week, so missed the last team meeting. 15:43:29 <kgriffs> But I agree, we need to get things moving and/or shift some priorities 15:43:44 <ttx> ok, will you have that cleanup done by next week? 15:43:51 <kgriffs> yep 15:43:56 <kgriffs> will do 15:44:01 <ttx> ok, we'll look at it then 15:44:22 <ttx> #info J2 plan to be cleaned up for review next week 15:44:52 <ttx> kgriffs: did you have questions about J2 and/or the milestone tagging process? 15:45:12 * ttx refreshed https://wiki.openstack.org/wiki/PTL_Guide and https://wiki.openstack.org/wiki/BranchModel to reflect new world order 15:45:40 <kgriffs> ttx: nope. I'm assuming the tagging process will be the same as for j-1 ? 15:45:48 <ttx> kgriffs: yes 15:46:06 <ttx> just shout a SHA and it will serve as the time milestone 15:46:13 <kgriffs> sounds like a plan 15:46:58 <ttx> kgriffs: I see project rename up there... what's your plan for that? Do you think it can be done for J2? 15:47:07 <ttx> Did you pick a new name already? 15:47:18 <ttx> (I know name vetting takes forver those days) 15:47:44 <kgriffs> for sure 15:47:49 <kgriffs> seems like all the best names are taken 15:48:07 <kgriffs> the team settled on a Hindi name, Naav. Means boat or something. 15:48:07 <ttx> the easiest is to come up with an imaginary name combo 15:48:24 <ttx> like HorseBatteryStaple. 15:48:27 <kgriffs> heh 15:48:44 <kgriffs> anyway, we may need to push the name change to j-3 so we can get api 1.1 squared away 15:48:50 <ttx> ok 15:48:55 <ttx> makes sense 15:49:06 <kgriffs> I was hoping the team would make some progress on the renaming while I was out but I don't see any patches. 15:49:19 <ttx> that's all I had... did you have questions? 15:50:58 <kgriffs> To be fully transparent, I wanted to let you know that I may be transitioning to a new role at Rackspace and may need to step down from the PTL role. Nothing for sure yet. 15:51:13 <kgriffs> but, we may need to do a mid-cycle election or however that works. 15:51:19 <ttx> kgriffs: oh, ok. no issue 15:51:29 <ttx> kgriffs: you can do it two ways 15:51:44 <ttx> you can name someone as your permanent delegate until the next election 15:51:52 <ttx> or you can run mid-term elections 15:52:00 <ttx> all depends how close you are from the end of the cycle 15:52:14 <ttx> both solutions are "acceptable" from our governance standpoint 15:52:29 <kgriffs> Got it. I just want to make sure the transition is done responsibly. 15:52:47 <ttx> ok. Talk to you next week, then! 15:52:49 <ttx> devananda: around? 15:52:53 <devananda> ttx: hi! 15:52:58 <kgriffs> kk, ttfn 15:53:00 <ttx> #topic Ironic 15:53:23 <ttx> https://launchpad.net/ironic/+milestone/juno-2 15:53:50 <devananda> so as you can see, we got a few specs approved this week and targeted 15:53:57 <devananda> the code for those is already under review 15:54:13 <devananda> one more spec that got approved is probably not ready in time -- https://blueprints.launchpad.net/ironic/+spec/send-data-to-ceilometer 15:54:16 <devananda> so i've set that for J3 15:54:20 <ttx> so shall I move from unknown to NeedsCodeReview ? 15:54:34 <devananda> ah - right. i'll fix 15:55:04 <ttx> If they are all under code review, looks like good progress 15:55:14 <ttx> expecting more to appear in that list ? 15:55:29 <devananda> possibly one or two in the next few days 15:55:57 <ttx> ok 15:56:01 <devananda> i think we are starting to get better with specs, but there's still many folks writing code and spec at the same time 15:56:16 <devananda> so the time lag between approving a spec and beign able to land the code is fairly small 15:56:29 <ttx> how is the ironic driver integration coming up in Nova? 15:56:33 <devananda> i'm not sure that's good or bad yet - it's certainly different than last cycle 15:56:44 <devananda> the code for that has been up for a few weeks now, without really getting feedback 15:57:05 <ttx> do you have links I could try to make more popular? 15:57:15 <devananda> #link https://review.openstack.org/#/c/103165/ 15:57:21 <devananda> #link https://review.openstack.org/#/c/103167/ 15:57:54 <devananda> I will be porting several more commits from ironic into the second patch set above 15:58:07 <devananda> as we've been continuing to fix things and work on tempest coverage 15:58:24 <devananda> another large effort in the last week or two has been by adam_g and Shrews, working with the -qa team 15:58:39 <ttx> hmm, ok. Hopefully the nova midcycle sprint will help iterate on that 15:58:40 <devananda> to get things into shape where Ironic can pass a full tempest/api/compute run 15:59:06 <devananda> that's led to adding feature flags to tempest and to fixing several things in our driver code 16:00:14 <devananda> that work is being tracked here https://etherpad.openstack.org/p/IronicCI 16:00:15 <ttx> ok 16:00:28 <ttx> that's all I had -- questions? 16:00:57 <devananda> not for J2 - i feel pretty comfortable with our progress, though it's still slower than I'd like, but i'm getting used to that 16:01:15 <ttx> heh, ok 16:01:28 <ttx> I think that concludes the day 16:01:31 <ttx> #endmeeting