12:29:01 #startmeeting incub_sync 12:29:02 Meeting started Thu Jul 3 12:29:01 2014 UTC and is due to finish in 60 minutes. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:29:03 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 12:29:05 The meeting name has been set to 'incub_sync' 12:29:06 #topic Designate 12:29:11 Kiall: hi! 12:29:33 Heya :) So, first time doing one of these. Could you give me an intro? :) 12:30:08 Well, it's more to ensure you have time to ask questions, and so that we sync on juno status 12:30:28 the latter becomes more important as you start to have your mielstones published by release management rather than yourself 12:30:57 basically, we gradually make sure you handle releases and the release cycle in the common way 12:31:14 and have opportunity to learn and ask questions while doing so 12:31:34 At this point, designate always did its own release work 12:31:47 Okay - sure.. I guess that leads to my first question then :) When do we start having you handle releases? I'm guessing it's not "now" - but sometime soon? 12:31:49 although it's already aligned with the release series 12:32:05 Yea, our process is 99% identical. Although, we did miss/skip j1 12:32:29 what do you want to do with j1 ? Should we mark is done/inactive? 12:32:37 it* 12:33:28 I was considering simply cutting a j1 release sometime in the next few days - But, not sure it's worth it. We have very little user facing changes so far - it's all been core work. 12:33:53 alternatively we can move everything to j2 and "cancel" j1 12:34:09 your call 12:34:26 Okay - That sounds like as good a plan, we'll migrate all the bugs/bps and close j1 on launchpad. 12:34:51 we can switch to release-management managed releases for j2 12:35:03 if you think you can hit the deadline 12:35:13 the tooling should be mostly ready 12:35:33 we'll just have to adjust a few permissions in LP 12:35:42 Okay, that depends on what you need from us :) We should be following the process pretty closely already, but there may be a few small things. 12:35:55 if we do that now I can use scripts to move everything to j2 and cancel j1 for you 12:35:58 I actually believe you should already have access - the designate LP projects are marked as part of openstack 12:36:23 that's unfortunately not enough ;) You need to set openstack-admins as maintainer of https://launchpad.net/designate 12:36:25 So - you should inherit perms via that, correct? 12:36:37 and then add the openstack-release group in the designate-drivers group 12:36:48 Okay. I'll do that straight after our meet. 12:37:28 So - Is there anything else we might need to change before j2 for you to be able to handle the releases? 12:37:34 you'll keep rights over the project via the designate-drivers group still being the "drivers" of the project 12:37:46 I don't think so 12:38:03 I shall inherit everything needed from "all projects" in gerrit 12:38:09 Okay - Excellent. 12:38:28 could you set the Lp perms now ? Then i can use my scripts to move bugs around 12:38:31 Sure 12:38:42 that way you won't have to manually do it and we can agree o nthe result 12:39:08 Done on both designate and python-designateclient 12:39:22 then it's just a question of you letting me know of a master SHA you'd like to tag as juno-2, ideally during the juno-2 common week 12:39:39 and i'll run the script to make it happen 12:39:51 Okay - That's no problem 12:40:28 ok, let me try the defer bug script 12:40:33 So, another question. We have a in-tree DevStack plugin, and HP has a (currently not open source) Horizon plugin. We'd like to get these merged to devstack/horizon - is that something we can do yet? 12:41:24 it's a bit of a chicken-and-egg, and the TC resolved that it's something you shall do during your first integrated cycle (between the time you graduated to integrated and the first release as integrated) 12:41:38 so for example sahara is doing it during the Juno cycle 12:41:49 * SergeyLukjanov lurking 12:41:56 but then you need to opensource it first ;) 12:41:56 Okay, so that's a "not yet" then? 12:42:15 yes, not yet, but I'd work (1) on opensourcing it and (2) in getting horizon devs feedback on it 12:42:23 SergeyLukjanov can let you know how he did it 12:42:23 Yea - our Horizon team are not wanting to maintain it in two places, so really want to push it into horizon rather than another repo. 12:42:44 Kiall: at this point you should probably publish it in a git repo under the designate program 12:42:55 and maintain it there until horizon can take it 12:43:11 like sahara did with openstack/sahara-dashboard 12:43:31 yup, and then you could ask horizon devs to take a look on it 12:43:32 Yea, that's plan B :) I have Endre extracting it from our internal horizon fork at the moment, then we'll need to pass it through our open source process. 12:43:47 and when you'll be integrated you'll start merging hell 12:43:57 :) 12:45:04 Kiall, the super huge pros of such approach - ability to easy hack your dashboard code 12:45:14 it'll be impossible after merging into horizon 12:45:24 Okay - So, another question, beyond looking after the project itself, are they any other expectations for PTLs? 12:45:37 Kiall: small note, you should not be using "Juno" series in your bugs, like in https://bugs.launchpad.net/designate/+bug/1271493 12:45:39 (+ beyond this weekly sync up :)) 12:45:41 just use the default series 12:45:49 otherwise most scripts are confused 12:46:04 Oh. Okay, I think all our bugs are like that 12:46:25 no only 3 of them were 12:46:34 (from the j-1 targeted things at least) 12:46:46 the default series means 'the series under development" 12:46:50 Ah - Yea, there is piles more which aren't on j1. 12:47:00 juno series is a bit of a corner case in Lp 12:47:08 https://launchpad.net/designate/+milestone/juno-1 is now empty 12:47:14 shal I just delete it now ? 12:47:22 Sur 12:47:23 Sure* 12:47:43 OK, so we are good 12:48:00 Should we fix any bugs targeted to Juno BTW? 12:48:15 bah don't bother 12:48:25 we'll catch them when the scripts fail 12:48:25 Okay 12:48:46 fwiw development milestoes are just point in time 12:49:09 a common time reference, handy for rough targeting estimates 12:49:20 it's not supposed to be a lot better or worse than any point in master 12:49:29 although we try to avoid tagging when it's utterly broken 12:49:58 Makes sense. 12:50:15 So, another question, beyond looking after the project itself, are they any other expectations for PTLs? 12:50:19 OK, that's all i had for today. like I said, next week we'll have a look at the j-2 targeted content and try to see if it makes any sense 12:50:40 Kill: did you read https://wiki.openstack.org/wiki/PTLguide ? 12:50:52 Kiall: ^ 12:51:00 Hmm, looks like I need to update it a bit 12:51:15 the whole milestone-proposed thing is a bit outdated now 12:51:16 ttx: Aha - I was looking for a page like that, and missed it. 12:51:36 I will update it, but I suspect most of it will still be current 12:51:50 I'll have it updated before next week sync point 12:51:56 Okay - I've watched the page, once you have updated I'll review it 12:51:58 #action ttx to update https://wiki.openstack.org/wiki/PTLguide 12:52:15 Ok, that's enough for a first contact :) 12:52:21 talk to you next week! 12:52:28 Thanks ttx - cya :) 12:52:30 (unelss you have another question) 12:52:41 No, that's it for now :) 12:52:53 OK! have a good day! 12:53:18 same to you :) 15:20:53 bu28 15:20:55 ops 15:31:03 jraim: around? 15:39:50 devananda: ready when you are 15:40:01 ttx: hi! 15:40:16 looks like you're the only one around again :) 15:40:21 huh 15:40:23 #topic Ironic 15:40:28 well, I had kiall this morning 15:40:46 only real news from last week is http://lists.openstack.org/pipermail/openstack-dev/2014-June/039031.html 15:41:04 * flaper87 is around for Marconi 15:41:15 ironic core team did a hangout, looked at our notes from the summit, and tried to evaluate where we are on accomplishing them 15:41:18 that email summarizes it 15:41:39 oh, and one other news 15:42:09 Nova approved the spec for an ironic virt driver 15:42:16 devananda: cool 15:42:23 so I'm quickly prepping the code for landing it there. 15:42:38 devananda: is https://launchpad.net/ironic/+milestone/juno-2 up to date with the plan described in the Google spreadsheet ? 15:42:49 no 15:42:50 Looks a bit thin 15:42:51 ok 15:43:02 You use specs iirc 15:43:11 yes, however many of them haven't landed 15:43:42 You can use http://git.openstack.org/cgit/openstack-infra/release-tools/tree/spec2bp.py to keep spec in line with spec state 15:43:48 I'm hoping to corralle the spec review team into landing them by next week, then i'll target. it seems a bit rushed 15:44:22 fwiw, we've also got 33 open specs right now 15:44:24 as long as the spec and the blueprint have the same name, you can run the script when the spec is approved 15:44:50 as long as you're incubated it's not a big deal if the bleuprint plan lags a bit 15:45:22 since it's not published as part of http://status.openstack.org/release/ 15:45:22 ack 15:45:54 it's a bit awkward to be incubated and also juggling not just early adopters but a few companies' product plans :) 15:46:03 but as you get closer to j-2 it's good to bring the blueprint landscape in sync 15:46:29 will do 15:46:29 incubated is not really about stability or maturity, it's really about integration 15:46:40 and process convergence 15:46:42 yes 15:46:50 the name is a bit of a misnomer 15:46:58 i'm well aware of that 15:47:12 learning-integration is a mouthful though 15:47:47 planning to tag j-2 on the common j2 week? 15:48:28 that's the current plan 15:48:30 #info Ironic planning to do j2 on integrated j2 week 15:48:45 #info j2 plans will be refined as we get closer to j2 date 15:48:59 OK, that's all I had, anything else you wanted to mention ? 15:49:05 nope - thanks! 15:49:11 #info Nova approved the spec for an ironic virt driver 15:49:27 devananda: many thanks! 15:50:08 jraim: last call 15:50:17 ttx: I'm here 15:50:20 sorry about that 15:50:21 hah! 15:50:26 IRC client didn't notify me for some reason 15:50:26 no pb, deva was early 15:50:33 #topic Barbican 15:51:47 are you waiting on me? Or is my IRC client being weird again? 15:51:54 no, thinking 15:52:07 jraim: how do you want to handle juno-2 ? Should I take over the release management ? 15:52:51 I think I would be fine with that. Our plan was to just do the release like we've done previously 15:52:54 (mostly means you would just confirm a SHA to tag, ideally during the common juno-2 week, and I would do the rest) 15:53:11 That seems good to me 15:53:18 well, except i'm not around at juno-� so proobably someone else would do it, but that's the plan 15:53:22 juno-2* 15:53:59 jraim: let me check the launchpad rights 15:54:35 jraim: to align with other projects, you should rename https://launchpad.net/~barbican-core to barbican-drivers 15:54:40 and add openstack-release in it 15:54:49 so that we can change bug status at release time 15:55:22 barbican drivers? that's the normal name for the core reviewers? 15:55:22 that way we can handle the Launchpad end of things 15:55:38 those are actually two different groups 15:55:45 COre reviewers are defined in gerrit 15:56:04 the launchpad driver group is for blueprint targeting and such 15:56:14 ahh okay, we can change that stuff 15:56:17 currently you have two things named barbican-core 15:56:21 and probably out of sync 15:56:28 https://launchpad.net/~barbican-core 15:56:29 and 15:56:44 https://review.openstack.org/#/admin/groups/178,members 15:56:48 those are not synced 15:56:55 so keeping the same name is a bit confusing 15:57:08 fair enough 15:57:11 we'll get that cleaned up 15:57:22 that's why the Launchpad driver group is usually called $PROJECT-drivers 15:57:32 makes sense 15:57:43 and in order for us to set milestones on fixed bugs etc. openstack-release has to be added to it 15:58:02 okay, we'll get that group added 15:58:09 well, rrenamed 15:58:25 yeah, rename the main group and add -release 15:58:29 you don't need a new group, just rename the Launchpad "barbican-core" 15:58:36 will avoid further confusionb 15:58:39 -b 15:58:54 ok, once that's done we should be able to do releasing 15:58:59 great 15:59:04 I'll get that done today 15:59:19 Is https://launchpad.net/barbican/+milestone/juno-2 representative of your j-2 goals ? 15:59:26 or astill a bit incomplete ? 15:59:47 my guess is that it is still incomplete 15:59:52 I'll run through it today to get caught up 16:00:08 #action jraim to rename ~barbican-core in LP to ~barbican-drivers and add ~openstack-release to it 16:00:17 We have our mid-cycle next week, so we'll get that cleaned up with everyone there 16:00:26 jraim: no hurry, just needs to be more..; accurate as we get closer to the milestone 16:00:50 but then, communicating what's likely to be landed is a good exercise 16:00:55 cool. should be easy with everyone in the same room to get it all cleaned up 16:00:56 yeah 16:01:05 we use the launchpad blueprint page as a tool for communicating likely-landing features 16:01:27 once integrated, your input is aggregated to http://status.openstack.org/release/ 16:01:44 which presents the whole integrated picture 16:01:51 right. 16:02:03 jraim: ok, that's all I had for today -- anything you wanted to mention, any question ? 16:02:34 not too much, we've been getting ready for the mid-cycle next week 16:03:10 rigth 16:03:32 if you have a wikipage fr that event, you can add it to 16:03:36 https://wiki.openstack.org/wiki/Sprints 16:03:43 currently points to a TBD 16:03:50 we have an eitherpad set up so I'll go link it 16:03:54 cool 16:04:08 well, have a great July 4 weekend 16:04:14 you too, thanks! 16:04:21 * ttx works tomorrow 16:04:43 * ttx realizes he works on French and US holidays 16:04:51 something needs to be fixed here 16:05:09 anyway, that concludes our 1:1s for today 16:05:13 Thanks everyone! 16:05:19 #endmeeting