14:36:41 <ttx> #startmeeting incub_sync
14:36:42 <openstack> Meeting started Thu Oct  2 14:36:41 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:36:43 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:36:45 <openstack> The meeting name has been set to 'incub_sync'
14:36:53 <ttx> #topic Designate
14:37:00 <ttx> Kiall: ping me when back
14:37:12 <Kiall> ttx: heya :)
14:37:21 <ttx> alright
14:37:49 <ttx> RC1 is out
14:37:56 <ttx> RC2 window is open
14:38:01 <Kiall> So - Q for you, we've found a bug in rc1 we need to fix.. We should submit to master, then proposed/juno, correct?
14:38:24 <ttx> yes, you get it fixed in master, it turns to "FixCommitted"
14:38:33 <ttx> then when you backport it, it should turn to FixReleased
14:39:03 <Kiall> It'll auto change to FixReleased once merged to proposed/juno?
14:39:22 <ttx> SlickNik: you can approve https://review.openstack.org/#/c/125113/ I think
14:39:28 <ttx> Kiall: in theory yes
14:39:35 <Kiall> ttx: Ah, ok...
14:40:01 <Kiall> 1 other question I had for you - Do we know when openstack/requirements will "open for kilo" changes?
14:40:03 <ttx> so now you ned to get both fixes in master
14:40:15 <ttx> then you backport them to proposed/juno
14:40:29 <ttx> and then we can tag rc2 and sing with the crowd
14:40:46 <ttx> requirements is unfrozen when all RC1s are out
14:40:58 <ttx> we are still missing swift, trove, horizon and neutron
14:41:17 <Kiall> K - I'll keep an eye out for those then, thanks :)
14:41:27 <Kiall> That's me out of questions, do you have any for me?
14:41:33 <ttx> nope
14:41:58 <ttx> all set
14:42:00 <Kiall> Okay, well, have a good day then!
14:42:34 <ttx> talk to you later
15:33:07 <ttx> jraim: around?
15:33:18 <jraim> yep.
15:33:20 <jraim> ping redrobot
15:33:21 <ttx> #topic Barbican
15:33:28 <redrobot> ohai
15:33:37 <ttx> https://launchpad.net/barbican/+milestone/juno-rc1
15:33:42 <ttx> Looks like you're close
15:33:45 <jraim> ttx: Not sure if you saw, but redrobot will be taking over PTL from me for Juno
15:33:50 <ttx> I saw.
15:33:53 <jraim> For Kilo, sorry
15:34:04 <ttx> Still respecting the order of succession :)
15:34:13 <jraim> So he's been working the cleanup / landing of RC1
15:34:18 <jraim> understood :)
15:34:31 <ttx> so once you're happy with all... you should push an open-kilo patch
15:34:31 <redrobot> yep, pretty close. waiting on one more review for a critical bug
15:34:43 <ttx> Somethign like https://review.openstack.org/#/c/125081/
15:34:56 * ttx checks that it applies to barbican
15:35:16 <ttx> it does.
15:35:26 <ttx> I can propose one, just -2 it until you're ready for RC1
15:35:51 <jraim> sounds good
15:36:15 <ttx> https://review.openstack.org/125678
15:36:30 <ttx> so that marks the opening of kilo
15:36:35 <ttx> I branch from previous commit
15:36:38 <ttx> and tag rc1 there
15:37:19 <jraim> okay
15:37:30 <ttx> running a few checks
15:37:34 <jraim> seems straight forward
15:37:43 <ttx> ok, I think we are good
15:37:54 <ttx> so once I spot that change merged i'll tag for you :)
15:38:04 <jraim> redrobot: okay with you?
15:38:09 <redrobot> yep, sounds good to me
15:38:28 <ttx> In theory the RC1 can be good for two weeks and released ~ release day
15:38:38 <ttx> if you spot a critical issue though, we should respin
15:38:47 <jraim> yep
15:38:50 <ttx> which means, creating a rc2 milestone in launchpad, and target a few bugs to it
15:38:57 <ttx> you get the bug fixed in master first
15:39:05 <ttx> then we backport the ones that are targeted to rc2
15:39:10 <ttx> to proposed/juno
15:39:18 <ttx> (which is created to support rc1 tag)
15:39:29 <jraim> makes sense
15:39:36 <ttx> just ping me when/if you want to open a RC2, I'll help
15:39:43 <jraim> great
15:39:49 <ttx> ok, that's all... other questions ?
15:39:52 <jraim> not from me
15:40:00 <ttx> design summit space maybe...
15:40:13 <redrobot> yeah, are we getting a pod?
15:40:28 <ttx> you get 4 scheduled slots on the Tuesday, plus a dedicated pod all week
15:40:31 <redrobot> also, any chance we can be next to the Keystone folks?  That was super helpful in Atlanta
15:40:36 <ttx> I avoided your conference conflict
15:40:48 <redrobot> the workshop?  awesome.
15:41:14 <ttx> Keystone won't have a designated pod. So just ask them to pick the free ones around you when they need one :)
15:41:25 <ttx> or you could just call yours the barbican/keystone pod :)
15:41:47 <ttx> flaper87: around?
15:41:51 <flaper87> o/
15:41:58 <flaper87> gosh, I've had that hand raised for a while
15:41:59 <flaper87> o.0
15:42:02 <flaper87> it started to hurt
15:42:06 <ttx> redrobot, jraim: thanks, ttyl
15:42:11 <ttx> #topic Zaqar
15:42:14 <ttx> o_
15:42:14 <redrobot> ttx thank you!
15:42:23 <flaper87> ttx: https://review.openstack.org/#/c/125681/
15:42:26 <flaper87> :)
15:42:52 <ttx> hah! I won't have a commit in Zaqar just yet :)
15:43:06 <flaper87> lol :D
15:43:17 <flaper87> so yeah, rc1 can be cut now, I think we're good
15:43:26 <ttx> ok, ping me when it lands, because I only follow the 'open-kilo' topic
15:43:44 <ttx> or maybe I can do it now, if it merges fast
15:43:58 <ttx> so same advice wrt: rc2, read above
15:44:04 <flaper87> ttx: it shouldn't take long
15:44:10 <flaper87> yeah, all clear
15:44:17 <ttx> ok, let's try this
15:44:51 <ttx> Design Summit: Zaqar has same allocation as Barbican, 4 scheduled slots on the Tuesday, dedicated pod all week
15:45:11 <flaper87> good to know, morning or afternoon?
15:45:17 <flaper87> do we know that already?
15:45:35 <ttx> yes, current setup is morning, until 3:30pm
15:45:51 <flaper87> ok, cool. I guess no parties on monday... damn ttx >.>
15:46:05 <ttx> can't really put you i afternoon, because that would create a conflict for redrobot
15:46:17 <flaper87> morning is great, np
15:46:19 <ttx> (who has a talk on Tue morning in conference
15:46:20 <flaper87> :)
15:46:39 <ttx> well, I /could/ place you in morning, but then you would get only 3 slots
15:46:42 <ttx> :)
15:46:52 <ttx> (I mean, afternoon)
15:47:02 <flaper87> no no no, we need the fourth one
15:47:05 <flaper87> :P
15:47:35 <flaper87> so, the patch will take longer than expected
15:47:41 <flaper87> i guess you can cut it later
15:47:48 <ttx> bah, no worry, I'll pick it up tomorrow morning
15:47:55 <flaper87> awesome, sounds good
15:47:57 <ttx> in the mean time, once it's merged, kilo is opened
15:48:05 <ttx> great, thx!
15:48:10 <flaper87> thank you, ttyl
15:48:11 <ttx> devananda: around?
15:48:49 <devananda> ttx: hi!
15:48:54 <ttx> #topic Ironic
15:49:06 <ttx> https://launchpad.net/ironic/+milestone/juno-rc1
15:49:13 <ttx> 4 bugs ! oh my
15:49:21 <ttx> are you getting closer ?
15:49:32 <devananda> yup. three of those are on me. fixes have been in flight for a few days
15:49:46 <devananda> at this point, there's concensus on landing them -- but we are hitting a strange bug in the gate
15:49:56 <ttx> that happens
15:49:58 <devananda> py26,27 are failing there, but not for us localy
15:50:24 <devananda> been working on solving that this morning
15:50:31 <devananda> once that's fixed, we should be able to close 3 of those 4 bugs
15:51:02 <ttx> pushing an open-kilo change, -2 it for the time being
15:51:05 <ttx> https://review.openstack.org/125693
15:51:11 <devananda> the 4th, https://bugs.launchpad.net/bugs/1367182, is a bug in one driver, so it's less important -- but we will probably land it today
15:51:17 <ttx> when you're happy with master, approve that
15:51:24 <ttx> I'll pick it up and tag/branch
15:51:24 <devananda> ttx: will do, ty
15:51:54 <ttx> just add the -2 to avoid someone crazy to approve it
15:51:54 <devananda> my goal is by the end of today
15:52:03 <ttx> ah, done
15:52:09 <devananda> but we'll see. i'm also out this afternoon for meetings
15:52:09 <ttx> questions?
15:52:27 <devananda> not about juno release :)
15:52:37 <devananda> i do have a question or two about the summit tho
15:52:48 <ttx> devananda: like, how am I going to survive Paris with my diet
15:52:55 <devananda> ttx: there's that
15:53:11 <ttx> I won't deny it will be a bit of a challenge
15:53:12 <devananda> ttx: i figure i'll be eating a lot of butter and fish
15:53:38 <devananda> and getting about half my calories from wine
15:53:39 <ttx> even getting vegetarian food is a challenge here
15:53:59 <devananda> hmm
15:54:15 <devananda> well, i'll be there for ~2 weeks, so I have plenty of time to lose weight!
15:54:19 <ttx> summit allocation: 5 scheduled slots, a half-day meetup
15:54:36 <devananda> ah, cool
15:54:47 <devananda> i haven't seen the schedule posted anywhere yet
15:54:58 <ttx> I need to enter it in sched
15:55:08 <ttx> unfortunately couldn't find eth time today
15:55:11 <devananda> ok. last year there was a spreadsheet too
15:55:22 <devananda> do you know yet what days?
15:55:24 <ttx> ah! I could give you access to /that/
15:55:28 <devananda> :)
15:55:32 <ttx> days...
15:55:52 <ttx> You have wed morning + one session Thu morning
15:56:00 <ttx> meetup is Friday afternoon
15:56:11 <devananda> k k
15:56:12 <ttx> (well, until 5:10pm)
15:56:29 <devananda> we're using a gDoc to collect ideas and start scheduling them
15:56:40 <devananda> I've also asked for a slot in the operators track on monday
15:56:59 <devananda> particularly given ironic's operator-focused mission, I am looking forward to that feedback
15:57:40 <ttx> right
15:57:44 <ttx> anything else ,
15:57:45 <ttx> ?
15:57:47 <devananda> nope
15:57:50 <devananda> thanks!
15:57:56 <ttx> alright then, have a good day!
16:27:56 <SlickNik> ttx: done on https://review.openstack.org/#/c/125113. Thanks!
18:07:48 <mestery> ttx: The "Open Kilo" commit merged in Neutron, I think you're good to package up neutron Juno-RC1 now. Thanks and sorry my travel made my availability limited this week.
18:45:53 <david-lyle> ttx, Horizon RC1 ready
19:41:32 <SlickNik> ttx: fyi https://review.openstack.org/#/c/125113/ merged
19:41:41 <SlickNik> ttx: Thanks!
09:29:51 <ttx> devananda: ironic RC1 is out: https://launchpad.net/ironic/juno/juno-rc1
10:20:14 <ttx> flaper87: zaqar RC1 is out: https://launchpad.net/zaqar/juno/juno-rc1
10:33:54 <sdague> ttx: so things you said we'd address for the rcs finished... the requirements readme, so it can been in the juno branch :)
11:21:12 <ttx> sdague: damn you and your memory!
11:22:24 * ttx reads
11:23:20 <flaper87> ttx: sweet, thanks!
11:25:59 <ttx> sdague: ok +2
16:13:08 <devananda> ttx: cheers, thanks!
12:26:08 <flaper87> ttx: ping
12:26:14 <ttx> flaper87: pong
12:26:18 <flaper87> ttx: 2 of zaqar's sessions overlap with 2 workshops
12:26:33 <flaper87> is there a chance we can re-order that to avoid the overlap?
12:26:36 <flaper87> for example
12:26:45 <ttx> flaper87: all zaqar sessions overlap with workshops
12:27:03 <flaper87> ttx: not the 14:50 one
12:27:30 <ttx> workshops run all Tuesday, and inclubated sessions are on Tuesday
12:28:02 <ttx> Look at the time on those cross-project sessions
12:28:09 <ttx> 14 h 00 - 16 h 20
12:28:21 <flaper87> ah
12:28:22 <flaper87> damn, ok
12:28:25 <flaper87> nevermind then
12:28:39 <flaper87> I assumed they lasted 1h
12:28:51 <ttx> that said, once we have the workshops decided, we can optimize them so that you can attend the ones you're interested in
12:28:58 <flaper87> +1
12:29:00 <flaper87> thanks
12:29:06 * flaper87 stfu
13:15:46 <ttx> dolphm: ping me when around
14:30:25 <dolphm> ttx: o/
14:30:57 <ttx> dolphm: in a meeting, will ping you when I'm out
14:31:04 <dolphm> ttx: sure
14:31:13 <ttx> dolphm: business summary: I opened a RC2 since you merged patches to proposed/juno
14:31:30 <ttx> (if something merges there, we are kinda forced to)
14:31:39 <dolphm> ttx: will get a couple more small things backported today
14:49:16 <ttx> dolphm: got 10min now
14:49:35 <dolphm> ttx: can we aim for tomorrow morning for rc2?
14:50:03 <dolphm> ttx: ~24 hours from now
14:50:14 <ttx> dolphm: sure -- just make sure they all have bugs attached
14:50:22 <ttx> and that they are low regression risk
14:50:40 <ttx> we can review them together if you prefer
14:50:41 <dolphm> ttx: ++
14:51:08 <dolphm> ttx: looking at these two on juno/proposed https://review.openstack.org/#/c/126307/ https://review.openstack.org/#/c/126308/
14:51:22 <dolphm> ttx: and then a backport of this after it lands https://review.openstack.org/#/c/125228/
14:52:25 * ttx looks
14:52:55 <ttx> 126307 looks good
14:53:27 <ttx> 126308 looks good too
14:54:06 <ttx> 125228 feels mor risky, but it's woirth it to mertge it pre-release (won't be able to merge that much post-release)
14:54:33 <ttx> dolphm: could you target the corresponding bugs to RC2 ? I created it earlier
14:55:54 <dolphm> ttx: done
14:57:38 <dolphm> ttx: that last patch actually fixes two bugs, but i wouldn't consider one to be an RC-blocker... should i target it to RC2 anyway, since it'll get fixed there?
14:58:10 <ttx> yes
14:58:15 <ttx> dolphm: ^
14:58:58 <dolphm> ttx: alright, done: https://bugs.launchpad.net/keystone/+milestone/juno-rc2
14:59:45 <dolphm> ttx: i also put up a backport for that last patch, but left it as WIP until the master patch is gating https://review.openstack.org/#/c/126314/
15:31:42 <ttx> nikhil_k: around?
15:33:44 <nikhil_k> ttx: hi
15:34:25 <ttx> nikhil_k: so.. rc2
15:34:43 <ttx> https://bugs.launchpad.net/glance/+bugs?field.tag=juno-rc-potential
15:35:26 <ttx> ideally you would add the juno-rc-potential tag to all the bugs in that etherpad
15:35:34 <ttx> so we can find them easily
15:35:43 <ttx> https://etherpad.openstack.org/p/glance-juno-release-bugs
15:35:52 <ttx> let's lok at them there
15:36:04 <ttx> https://bugs.launchpad.net/glance/+bug/1369581
15:36:31 <ttx> bah, let's open a RC2 that will be simpler
15:36:39 <nikhil_k> :)
15:37:18 <ttx> so that one is obviosuly safe
15:37:23 <ttx> and a good thing to have
15:37:34 <ttx> I added the milestone to it
15:37:49 <ttx> https://bugs.launchpad.net/glance/+bug/1367771
15:38:38 <ttx> probably good to have as well, adding
15:38:48 <nikhil_k> yeah
15:39:06 <nikhil_k> ttx: do you need importance on them?
15:39:13 <ttx> I set it
15:39:17 <nikhil_k> I see, thanks
15:39:55 <ttx> the DB ones are good to have prerelease as well
15:40:42 <nikhil_k> yes, they requested DB stuff specifically
15:41:04 <ttx> https://bugs.launchpad.net/glance/+bug/1371559
15:41:09 <ttx> patch looks safe to me
15:41:16 <ttx> added
15:42:17 <ttx> "Metadata Definitions Updated to be correct for final Juno features"
15:43:07 <ttx> those are all the JSON things
15:43:14 <ttx> sounds relatively safe as well
15:43:38 <nikhil_k> yeah
15:44:22 <ttx> https://bugs.launchpad.net/glance/+bug/1371728
15:44:42 <ttx> this one sounds more dangerous
15:44:56 <nikhil_k> hmm, it's been a issue for long time
15:45:12 <ttx> maybe we can reconsider once it's merged in master
15:45:18 <nikhil_k> the proposed change is to do by using timestamp and we don't have a consensus on it yet
15:45:25 <nikhil_k> yeah, that sounds good
15:45:26 <SergeyLukjanov> ttx, hello, could we discuss sahara's rc2 after?
15:45:34 <ttx> added the jujno-rc-potential tag to it
15:45:37 <ttx> SergeyLukjanov: yes
15:45:45 <nikhil_k> awesome
15:45:46 <ttx> https://bugs.launchpad.net/glance/+bug/1372564
15:46:20 <ttx> I put that one in the same bag
15:46:26 <nikhil_k> works
15:47:04 <ttx> the other ones, I would include https://bugs.launchpad.net/glance/+bug/1367432
15:47:14 <ttx> since it's merged already, and docs-only
15:47:36 <ttx> the others I'll mark rc-potential
15:48:52 <nikhil_k> ttx: I see those in the filter query https://bugs.launchpad.net/glance/+bugs?field.tag=juno-rc-potential
15:49:04 <nikhil_k> however, the bug itself does not show any tag yet
15:49:11 <ttx> nikhil_k: so this is your scoreboard: https://launchpad.net/glance/+milestone/juno-rc2
15:49:24 <ttx> nikhil_k: refresh maybe
15:49:51 <ttx> On that page, the ones that are marked FixCommitted are fixed in kilo/master
15:50:04 <nikhil_k> ttx: tried a couple of times say this one https://bugs.launchpad.net/glance/+bug/1367564
15:50:05 <ttx> The ones that are marked FixReleased are fixed in Kilo AND juno
15:50:24 <ttx> so all the ones which are InProgress you should get in master
15:50:31 <nikhil_k> milestone is empty still
15:50:44 <ttx> and the ones that are already in master (FixCommitted) you should propose a backport to proposed/juno branch
15:51:09 <ttx> https://wiki.openstack.org/wiki/GerritJenkinsGit#Authoring_Changes_for_proposed.2F.2A
15:51:38 <ttx> nikhil_k: which milestone?
15:52:25 <nikhil_k> ttx: should this one https://bugs.launchpad.net/glance/+bug/1367564 not say rc-potential?
15:52:39 <nikhil_k> juno-rc-potential i.e.
15:53:20 <ttx> yes it should
15:53:28 <nikhil_k> Milestone is still empty on that page
15:53:30 <nikhil_k> hmm
15:53:37 <ttx> looks fine to me
15:53:46 <ttx> it's tagged rc-potential, and not milestoned to rc2
15:54:07 <nikhil_k> gotcha
15:54:15 <nikhil_k> makes sense
15:54:29 <ttx> we'll revisit the rc-potential list for late addition to RC2 once we are done with all the targets
15:54:52 <ttx> If you prepare backports I can approve them
15:55:02 <ttx> but you need to get the fixed in master first!
15:55:07 <nikhil_k> and we've until Oct 16 for all of this?
15:55:08 <ttx> fixes*
15:55:40 <nikhil_k> do we've *
15:55:57 <ttx> no, we really need to do an RC2 asap
15:56:04 <nikhil_k> gotcha
15:56:06 <ttx> ideally in the 2 next days
15:56:11 <ttx> so that people can test it
15:56:18 <ttx> SergeyLukjanov: I have 5 minutes now
15:56:20 <nikhil_k> makes sense
15:56:24 <SergeyLukjanov> ttx, ack
15:56:30 <nikhil_k> ok, thanks ttx
15:56:31 <SergeyLukjanov> ttx, https://bugs.launchpad.net/sahara/+bugs?field.tag=juno-rc-potential
15:56:45 <SergeyLukjanov> ttx, I've prepared list of things we'd like to have in Juno
15:56:53 <SergeyLukjanov> ttx, 4 bug fixes and several doc changes
15:57:07 <SergeyLukjanov> ttx, everything is already merged into master
15:57:09 <ttx> yes, they seem warranted
15:57:23 <ttx> Let me create a RC2
15:57:44 <SergeyLukjanov> ttx, so, we should just cherry-pick them to proposed/juno?
15:58:05 <SergeyLukjanov> ttx, who should approve it and do we need a 2 x +2 for such changes?
15:58:25 <ttx> I can approve them all if you propose them and they are in master
15:58:50 <ttx> the trick is to check (1) they are in master (2) they have a bug attached and (3) they are targeted to RC2
15:59:29 <SergeyLukjanov> ttx, okay, we'll prepare all of them in proposed/juno today
15:59:45 <SergeyLukjanov> ttx, and I'll ask you to approve them at your tomorrow's morning
16:00:08 <ttx> https://launchpad.net/sahara/+milestone/juno-rc2
16:00:12 <ttx> all set
16:00:54 <SergeyLukjanov> ttx, thank you
16:01:01 <ttx> alrighty
16:01:05 <SergeyLukjanov> ttx, /me will return back tomorrow
16:02:20 <david-lyle> ttx: can you open an RC2 for Horizon as well
16:02:33 <david-lyle> final translations are due Oct 9
16:02:55 <david-lyle> there are a couple of other issues that we'll push as well
16:03:16 <david-lyle> https://bugs.launchpad.net/horizon/+bugs?field.tag=juno-rc-potential
16:03:22 <ttx> david-lyle: can we discuss that tomorrow ? In the mean time, make sure they get merged in master ;)
16:03:29 * ttx needs to run
16:03:58 <david-lyle> ttx: will be on a plane at our normal time, will try to ping you earlier
16:04:17 <david-lyle> talk to you tomorrow
16:04:20 <ttx> david-lyle: that works.
16:04:36 <ttx> but yeah, we'll open one for sure, to catch the translations
16:04:46 * ttx runs
16:04:46 <david-lyle> tt: thanks!
16:08:17 <nikhil_k> ttx: when you get a chance, another one https://review.openstack.org/#/c/107383/ for possible rc2 ?
16:08:56 <nikhil_k> fixes a security concern
20:14:56 <dolphm> ttx: master patches for these rc2 backports are either all merged or gating; i'm wondering if i should rubberstamp or wait for a second +2? https://review.openstack.org/#/c/126314/ https://review.openstack.org/#/c/126308/ https://review.openstack.org/#/c/126307/
20:15:15 <dolphm> nikhil_k: are you looking to block glance's rc2 with https://review.openstack.org/#/c/107383/ ?
20:19:07 <nikhil_k> dolphm: not sure about blocking atm
20:19:21 <nikhil_k> was thinking about the possibility of including it at this point
20:19:47 <nikhil_k> depending on the time availability
06:50:22 <ttx> dolphm: I can do the rubberstamping
06:51:27 <ttx> nikhil_k: adding the juno-rc-potential to it, needs to land in master first anyway
07:48:35 <ttx> mikal: going to the post office for 10min, should be back for our 1:1
08:03:59 <ttx> mikal: around?
08:26:59 <ttx> johnthetubaguy: we don't see to have mikal around
08:27:32 <johnthetubaguy> ttx: ah, sorry I am late as well
08:27:35 <johnthetubaguy> lots track
08:27:52 <johnthetubaguy> he was up early for another meeting, so maybe he fell asleep
08:28:05 <johnthetubaguy> ttx: we have some rc2 bugs I think
08:28:20 <openstack> ttx: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.
08:28:27 <ttx> #endmeeting