Thursday, 2014-09-18

*** markwash__ has quit IRC00:58
*** markwash__ has joined #openstack-relmgr-office01:00
*** markwash__ has quit IRC01:46
*** markwash__ has joined #openstack-relmgr-office01:48
*** markwash__ has quit IRC01:48
*** markwash__ has joined #openstack-relmgr-office01:49
*** david-lyle has joined #openstack-relmgr-office02:16
*** markwash__ has quit IRC03:44
*** markwash__ has joined #openstack-relmgr-office03:48
*** markwash__ has quit IRC03:53
*** markwash__ has joined #openstack-relmgr-office03:59
*** markwash__ has quit IRC05:10
*** david-lyle has quit IRC05:55
*** morganfainberg has quit IRC05:58
*** morganfainberg has joined #openstack-relmgr-office06:13
*** flaper87|afk is now known as flaper8707:19
*** mestery has quit IRC07:30
*** mestery has joined #openstack-relmgr-office07:30
*** morganfainberg has quit IRC07:35
*** morganfainberg has joined #openstack-relmgr-office07:39
*** zz_johnthetubagu is now known as johnthetubaguy08:27
*** markwash__ has joined #openstack-relmgr-office08:59
*** markwash__ has quit IRC09:03
dhellmannttx: I've started the releases. I'm going to have to make a bunch of requirements updates as we go, so dependencies are correct. That's going to make this take a while.11:06
dhellmannttx: How do you feel about me self-approving the changes to global requirements, after tests pass?11:07
sdaguedhellmann: can you bunch all the requirements changes into a single patch?11:12
sdaguebecause the lands trigger patch submissions to all the projects11:13
dhellmannsdague: I need to update the dependencies of the libraries as I go11:13
sdagueso there is giant secondary load created11:13
dhellmannI think I need 6 patches11:13
sdaguedhellmann: there is no way for the tests to pass without that?11:13
dhellmannto cover the 10 libraries being released today11:13
dhellmannI need to update the requirements in oslo.messaging after I release oslo.config, for example11:14
sdaguebecause that means we're talking about 6 x 10 x 15 nodes consumed to do this11:14
sdagueso basically, the entire zuul capacity will be consumed11:14
dhellmannit's not all going to happen at once11:14
sdaguein secondary back scatter11:14
sdaguedhellmann: right, so the question is is there no way that oslo.messaging can pass once there is a new oslo.config11:16
dhellmannsdague: we could turn off the thing that automatically updates the other projects11:16
dhellmannsdague: don't we still have a job that checks the requirements changes in a project?11:16
dhellmannI don't think I can change a dependency to something not found in global-requirements, but maybe we changed that?11:17
sdagueno, that's probably true11:17
sdagueso I guess the root issue is there are a bunch of libraries which really have lock step dependencies with other libraries, but are versioned independently?11:18
sdagueok, I guess it's not doable to do this with less work11:19
dhellmannI don't think it's lockstep, but it is weird to release a final oslo.messaging that depends on an alpha of oslo.config11:19
sdaguedhellmann: I guess, though realistically, that's the truth, right?11:19
dhellmannwhat's the truth?11:19
sdaguethat you could work with the alpha11:19
dhellmannyeah, I'm tagging the same commits11:20
sdagueso, in that case, is there any reason to bump it prior to the release? because it is semantically the same11:21
dhellmannI would rather not leave the dependencies just because we think it's going to consume a bunch of tests triggered by a bot we could turn off11:22
sdaguewell, then coord with infra folks about turning it off before the proposes11:22
sdaguethis comes back to things like the trove client question the other day11:23
dhellmannI wasn't involved in that one11:23
sdaguewhere they wanted to bump min version because they release a library version11:23
sdaguebut that's not why we bump g-r11:23
sdaguewe bump it because we can't work with the minimum listed11:23
sdagueanyway... I'll let you get back to it, but I think we need a session about libraries at summit because the fact that this process requires 6 g-r updates 2 weeks in FF... I think exposes that there are issues with it, and we should figure out if there are better ways11:25
dhellmannI don't really see the problem, so maybe you should run that session.11:28
sdaguehmmm... you aren't concerned that there are a lot of extra moving releases parts 1 week before people are trying to get RC releases out?11:30
dhellmannI'm one of those people.11:30
dhellmannI do not consider oslo "other" or separate or whatever from the rest of the release.11:30
sdagueso... maybe when we were talking about 5 git trees to integrate11:31
sdaguebut we're talking about 20+ that are all trying to RC the same week that all impact each other11:31
sdaguethat's not a recipe for success11:31
dhellmannI agree that we need to address the scale problem. I don't have a good answer this morning.11:37
sdagueyep, that's fair, that's why I said summit :)11:37
sdagueanyway, the gate is pretty idle now, I'd plow forward with the first rounds regardless11:37
sdaguethe capacity is there11:37
dhellmannyeah, the first check job is passing so I'm going to approve the patch and get it into the merge queue before I go to the dentist11:38
sdaguesounds good11:38
sdaguewhere is it?11:38
sdagueI can +A11:38
dhellmannhttps://review.openstack.org/#/c/122388/1,publish11:38
dhellmannoh, hmm11:38
dhellmannyou know, I probably can't do all of these updates anyway11:39
sdague?11:39
dhellmannif I'm going back to tag the last alpha, and we've had changes since then that we are not going to release, there's no way for me to get the update in without releasing the changes we don't want11:39
dhellmannwe had 1-2 cases where things merged and we said it's too late for the release11:39
dhellmannso I should probably just leave the requirements as they are :-/11:40
sdagueok, right, because we're actually pulling and testing against git in the normal case?11:40
dhellmannI can go ahead and tag everything and update the global list in one (more) patch11:40
dhellmannthe integration test is, yeah, but these were new features not fixes11:40
dhellmannwe had a late merge for something that was approved and then jenkins/zuul did something weird and didn't actually land the patch and we didn't realize it until late11:41
sdagueright, I guess the danger is if projects start using those new features prior to their release11:41
dhellmannyeah, nothing should be using it, it would have required a new feature added to another project this week11:41
sdagueyou'd be surprised what's still landing ... :)11:41
dhellmannheh11:41
dhellmannwell, there can't be unit tests for it, I know that much :-)11:42
sdagueyep11:42
*** dhellmann is now known as dhellmann_11:52
*** dhellmann_ is now known as dhellmann13:19
*** david-lyle has joined #openstack-relmgr-office14:20
Kiallhey ttx - ready when you are..14:22
*** david-lyle has quit IRC14:27
ttxKiall: hey14:32
ttx#startmeeting incub_sync14:32
openstackMeeting started Thu Sep 18 14:32:20 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.14:32
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:32
KiallNow.. The Q is, where do we put the time.sleep(1) ..14:32
openstackThe meeting name has been set to 'incub_sync'14:32
ttx#topic Designate14:32
Kialloops - wrong room14:32
Kiall;)14:32
ttxhttps://launchpad.net/designate/+milestone/juno-rc114:32
ttxStill have one blueprint open -- how is zone-migration-between-tenants doing?14:33
KiallGood/Bad - Graham hasn't completed the rebase. If we can't have that in by mid-week next week, I'm going to push it to kilo.14:33
KiallThe good is re - it's just in need of a rebase, but everyone has been busy with other tasks!14:34
KiallYou suggested last week we might cut a rc1 once they merge, a number of new bugs have been found and are in progress - they're severe enough to warrant holding out.14:34
ttxyour call. If you were integrated, that would be too late, and too much of a distraction from bugfixing14:34
*** david-lyle has joined #openstack-relmgr-office14:35
Kiallttx: for integrated - what's the hard deadline?14:35
ttxend of this week for the last tragglers. We deferred most of the others earlier this week14:35
ttxstragglers*14:35
ttxas for RC1, the idea is to cut something you think will be your final release, not just another milestone14:36
ttxso if you have a set of targeted bugs, better wait for them to be fixed14:36
KiallOkay - I think we can stick to that (well, closer to that!) .. If it's not merged Monday, we'll push it. I'd like to get it in :)14:36
ttxrathet than cut a RC1 and open a RC2 window hours after14:36
Kiallttx: agreed14:36
ttxKiall: there is less risk involved with incubated projects, so feel free to push the deadline farther away14:37
ttxbasically, if you don't have a viable RC1 by October 16, you wouldn't make my life miserable. Only yours :)14:37
KiallHah - Yea, that won't happen - I won't allow it ;)14:38
ttxIs the bug list on the https://launchpad.net/designate/+milestone/juno-rc1 representative of all your release blockers ?14:38
ttxi.e. those 4 bugs left are the only ones you really need to fix before release ?14:38
KiallYes, although I haven't triaged 1370621 Bing9 PTR Zone error : multiple RRs of singleton type yet14:38
ttxok, you seem to have a good handle on things. Questions ?14:39
KiallNothing new this week :)14:40
Kiall(I'll have plenty once we open kilo, but they can all wait!)14:42
ttxKiall: sorry, got caught up in something. Thanks!15:32
Kiallttx: no problem :)15:32
*** jraim has joined #openstack-relmgr-office15:46
ttxjraim: o/15:48
ttx#topic Barbican15:48
jraimttx: here15:48
jraimredrobot: you there?15:48
redroboto/15:48
ttxI see two bluepritns still open15:49
ttxadd-ssl-ca-support15:49
ttxapi-orders-add-more-types15:49
redrobotapi-orders-add-more-types is just waiting on one more CR15:49
jraimCorrect. We landed one and the api-orders one is in final review15:49
ttxit would be good to complete or defer them at this point, to turn focus to bugfixing15:49
redrobotI think we should be landing it in the next couple of days15:49
ttxok15:49
redrobotadd-ssl-ca-support probably needs to slip to Kilo15:50
redrobotI have low confidence we can complete it by RC115:50
ttxyour call really, since you bear the consequences of failing to meet the release date15:50
ttxRC1 is not really a date on the calendar15:50
jraimWe're okay with slipping it if we have too...it seems like it won't make it at this point15:51
ttxthe idea is that when you have something you think would make a good release, we cut a branch and pusg a rc1 tag15:51
ttxideally it all happens befor ethe final release date so that you can release at the same time15:51
ttx(at release date we just take the latest release candidate and promote it15:52
ttx)15:52
jraimmakes sense15:52
ttxin my experience, it's good to get rid of all feature work before the end of this week -- so that you can turn undivided attention to bugfixing15:52
jraimSo we'll land the one that's almost done, but it looks like we'll push the SSL one to K15:52
ttxsound slike a good call15:53
jraimWe did want to ask about design sessions15:53
jraimDid we come to a resolution on how those are getting planned?15:53
ttxyeah15:53
ttxso you'll have a number of sessions on the Tuesday, something like half a day15:54
ttxthat's sessions that appear on the schedule15:54
ttxyou'll also have a designated pod (table) to continue the discussions throughout the rest of the week15:54
jraimOkay, so we need to plan the tues sessions, but the rest is ad hoc15:55
ttxright15:55
ttxso it's good to use the scheduled sessions for stuff you want to communicate out of the project, things you want operator feedback on, etc15:55
ttxand keep project-internal discussion at the pod15:55
jraimRight. That sounds good. We have an etherpad we've been using to get those rolling15:56
jraimLast question I think - when are we doing PTL nominations for Kilo?15:56
ttxjraim: you might want to reference your etherpad at https://wiki.openstack.org/wiki/Summit/Planning15:56
ttxstarting tomorrow15:56
jraimWill do15:56
ttx(PTL nominatins start tomorrow)15:56
jraimPerfect15:56
ttxjraim: any other question?15:57
jraimnope, we're good15:57
ttxok, talk to you next week then15:57
ttxflaper87: around?15:57
flaper87ttx: yes, sir15:58
ttxhttps://launchpad.net/zaqar/+milestone/juno-rc1 looks good15:58
ttxno FFE in progress15:58
flaper87yup, as for the 2 bugs. 1 fix is in the gate and the other one coming soon15:58
ttxfeel free to target more bugs to rc1, as we will tag (and open kilo) once the list is empty15:58
flaper87roger, I'm planing to go through the list of bugs tomorrow and see if there's anything that makes sense fixing in rc115:59
ttxFWIW I scheduled the next session with the TC the week after next -- I figured we could use a one-week break16:00
ttxand start a few constructive ML threads16:00
flaper87right16:00
ttxthe urgency of the decision being part of the problem we had, I think16:01
flaper87I sent one yday but I havne't seen any reply besides eglynn's16:01
ttxflaper87: any question on the RC1 / release ?16:01
flaper87ttx: nope16:01
ttxflaper87: I'm a bit late on -dev, been traveling lately16:01
flaper87no worries, I just hope it to help with the discussion16:01
ttxok great, talk to you later16:01
ttxdevananda: you around ?16:01
devanandattx: o/16:04
ttx#topic Ironic16:05
ttxdevananda: so as far as Juno is concerned, you're still incubated16:05
devanandattx: yep16:05
ttxhttps://launchpad.net/ironic/+milestone/juno-rc116:05
ttxAll FFEs done16:05
ttxand a small list of RC bugs16:05
ttxFeels like you could hit a RC1 sooner rather than later16:06
ttxor do you need to add more to the list ?16:06
devanandawe were going to collectively assess the bug sitaution today and see what, if anything, is really a blocker16:06
devanandawe're using targeting as a way to track what we want in right now, not necessarily release blockers16:07
devanandaand as I do not see any open Critical bugs, I would agree that we probably could tag now16:07
devanandabut if it's not an impediment, I'd rather tag next week to give a little time to close some of the High bugs16:08
devanandaalso, i'm goign to tag our final client release today16:08
ttxdevananda: ok, at this point you can add a lot, and starting next week, we'll start to cut down if necessary16:08
ttxthe "good enough" approach to release management16:08
devanandasounds good16:08
ttxdevananda: ok, just let me know if you have any question16:09
ttxotherwise we'll close shop16:09
devanandawhen can we start votign on nova :)16:09
devanandathough that's probably a question for the qa team, not you16:09
devanandattx: no more questions related to the release16:10
ttxdevananda: alrighty then16:10
ttx#endmeeting16:10
openstackMeeting ended Thu Sep 18 16:10:41 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:10
openstackMinutes:        http://eavesdrop.openstack.org/meetings/incub_sync/2014/incub_sync.2014-09-18-14.32.html16:10
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/incub_sync/2014/incub_sync.2014-09-18-14.32.txt16:10
openstackLog:            http://eavesdrop.openstack.org/meetings/incub_sync/2014/incub_sync.2014-09-18-14.32.log.html16:10
dhellmannttx: if you have a sec, I think we're ready to branch oslo-incubator16:11
dhellmanncommit eabe46630d53bd430361c9d9253864e473c567e116:12
ttxok, did we say proposed/juno or stable/juno ? I know we hesitated...16:12
dhellmannlet's go right to stable/juno16:12
ttxok.. HEAD ?16:12
dhellmannyeah, that SHA should be the same as head16:12
ttxhmm, do you want to tag 2014.2 on it ?16:13
dhellmannif that's what we usually do, sure16:13
dhellmannit does look like that's what we ususally16:13
dhellmanndo16:13
ttxwe usually place a tag, yes, even if that doesn't mean a lot for the incubator16:13
ttxstable usually starts from it16:13
dhellmannyeah, I see some rc1 tags in there, too, but I don't think we need that this time around16:13
dhellmannshould I tag, or do you want to do that all together?16:14
ttxyes, let's skip rc116:14
ttxdhellmann: no, please tag16:14
dhellmannoh, I wasn't sure if that release script worked for the incubator or not so I haven't run that yet either16:14
ttxI'll cut the branch from the tagged commit16:14
ttxwhich should all be HEAD.16:14
dhellmannttx: I can't push tags to oslo-incubator? :-|16:16
ttxhm.16:17
ttxwe should probably fix that. In the mean time let me do it for you16:17
dhellmannttx: https://review.openstack.org/122459 should fix the acls16:18
ttxhmm, I'll just use the regular script to do all this16:19
dhellmannok16:19
ttxdhellmann: can all oslo-incubator FixCommitted bugs be FixReleased ?16:19
dhellmannyes, if they are committed in the incubator we consider that released16:20
ttxhhhrm. so it's a bit more complicated than I thought16:21
dhellmannttx: how so?16:21
ttxthe scripts implement it the way we did it last cycles16:22
ttxso we tag a RC1 and push all FixCommitted stuff to it16:22
ttxthen we promote rc1 to final16:22
ttxand move all juno-* bugs and blueprints to the "final" page16:22
ttx(2014.2 milestone page)16:23
dhellmanncan we do those things back-to-back?16:23
ttxbasically mimicking the integrated release modus operandi16:23
dhellmannright16:23
ttxmaybe we can just tag the final, create the branch16:23
ttxand fix LP later16:23
ttxI'll have to run soon16:24
dhellmannI don't mind doing lp by hand16:24
dhellmannyeah, me, too :-)16:24
ttxok tagging16:24
ttxtag in16:25
ttxand stable branch created16:26
ttxdhellmann: we'll fix up LP tomorrow :)16:26
dhellmannttx: sounds good16:26
dhellmannttx: I'm going to unleash the team to delete graduated modules tomorrow at our meeting16:26
dhellmannI'll send email to the -dev list after we talk about it in the meeting, explaining that incubator fixes should go right to stable/juno if the module has been deleted from master16:27
dhellmannttx: thanks for your help today, ttyl16:28
ttxnp16:33
*** markwash__ has joined #openstack-relmgr-office17:09
*** johnthetubaguy is now known as zz_johnthetubagu17:16
*** dhellmann is now known as dhellmann_17:22
SergeyLukjanovttx, sahara needs bump of client version - https://review.openstack.org/#/c/121942/18:08
*** zaneb has quit IRC18:34
*** zaneb has joined #openstack-relmgr-office18:36
*** dhellmann_ is now known as dhellmann19:01
*** dhellmann is now known as dhellmann_19:01
*** dhellmann_ has quit IRC19:02
*** dhellmann has joined #openstack-relmgr-office19:02
*** markwash__ has quit IRC19:16
*** markwash__ has joined #openstack-relmgr-office19:27
*** skhamkar has joined #openstack-relmgr-office20:03
*** skhamkar has quit IRC20:03
*** david-lyle has quit IRC20:10
*** david-lyle has joined #openstack-relmgr-office20:47
*** fesp has joined #openstack-relmgr-office21:26
*** flaper87 has quit IRC21:27
*** fesp is now known as flaper8721:27
*** sdague has quit IRC21:28
*** sdague has joined #openstack-relmgr-office21:31
*** flaper87 is now known as flaper87|afk22:18
*** david-lyle has quit IRC23:55

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!