Monday, 2016-03-07

*** Qiming has quit IRC00:02
*** shwetaap has joined #openstack-stable00:32
*** Qiming has joined #openstack-stable01:07
*** dims has quit IRC01:26
*** shwetaap has quit IRC01:43
*** nikhil has joined #openstack-stable02:25
*** niedbalski has quit IRC04:18
*** niedbalski has joined #openstack-stable04:20
*** shwetaap has joined #openstack-stable04:30
*** rcernin has joined #openstack-stable05:47
*** rcernin has quit IRC05:57
-openstackstatus- NOTICE: gerrit is going to be restarted due to bad performance07:24
*** ChanServ changes topic to "gerrit is going to be restarted due to bad performance"07:24
*** armax has joined #openstack-stable07:25
*** ChanServ changes topic to "reviews: http://tiny.cc/os-stable-dash | issues: https://etherpad.openstack.org/p/stable-tracker"07:27
*** shwetaap has quit IRC07:39
*** shwetaap has joined #openstack-stable07:39
*** shwetaap has quit IRC07:44
*** unlaudable has joined #openstack-stable07:46
*** pcaruana has joined #openstack-stable08:25
*** shwetaap has joined #openstack-stable08:40
*** shwetaap has quit IRC08:44
*** shwetaap has joined #openstack-stable09:40
*** shwetaap has quit IRC09:44
*** derekh has joined #openstack-stable09:44
*** apevec has joined #openstack-stable09:46
*** apevec has quit IRC09:46
*** apevec has joined #openstack-stable09:46
*** dtantsur|afk is now known as dtantsur09:50
*** apevec has left #openstack-stable09:58
*** ihrachys has joined #openstack-stable10:00
*** e0ne has joined #openstack-stable10:15
*** Qiming has quit IRC10:16
*** shwetaap has joined #openstack-stable10:40
*** dims_ has joined #openstack-stable10:41
*** shwetaap has quit IRC10:45
*** Qiming has joined #openstack-stable11:05
*** e0ne has quit IRC11:06
*** e0ne has joined #openstack-stable11:06
*** dims_ has quit IRC11:09
*** dims_ has joined #openstack-stable11:22
*** shwetaap has joined #openstack-stable11:41
*** shwetaap has quit IRC11:45
*** daemontool has joined #openstack-stable11:54
daemontoolhi11:54
daemontoolcan anyone take a look please at https://jenkins02.openstack.org/job/gate-freezer-api-requirements/3/console11:55
daemontoolin particular11:55
daemontool2016-03-07 11:32:06.269 |   File "/usr/local/jenkins/slave_scripts/project-requirements-change.py", line 260, in <module>11:55
daemontool2016-03-07 11:32:06.270 |     main()11:55
daemontool2016-03-07 11:32:06.270 |   File "/usr/local/jenkins/slave_scripts/project-requirements-change.py", line 231, in main11:55
daemontool2016-03-07 11:32:06.271 |     if req.extras:11:55
daemontool2016-03-07 11:32:06.272 | AttributeError: 'Requirement' object has no attribute 'extras'11:55
daemontool bknudson, ^^11:56
*** slashme has joined #openstack-stable11:57
daemontoolplease disregard the previous lines, the issue was resolved at our end, thanks12:17
daemontoolbknudson,  ^^12:17
*** shwetaap has joined #openstack-stable12:41
*** shwetaap has quit IRC12:45
*** takedakn has joined #openstack-stable12:53
*** nikhil has quit IRC12:58
*** Kiall has quit IRC13:03
*** Kiall has joined #openstack-stable13:03
*** Kiall has quit IRC13:03
*** Kiall has joined #openstack-stable13:03
*** takedakn has quit IRC13:18
*** dims_ has quit IRC13:25
*** shwetaap1 has joined #openstack-stable13:32
bknudsondaemontool: when we hit this problem on keystonemiddleware stable/kilo it was because the requirements job didn't update the requirements files properly, so check on that.13:43
*** shwetaap1 has quit IRC13:45
daemontoolbknudson,  ty13:45
*** e0ne has quit IRC13:58
*** e0ne has joined #openstack-stable14:00
*** eharney has joined #openstack-stable14:20
*** ihrachys has quit IRC14:40
*** shwetaap has joined #openstack-stable14:42
*** mriedem has joined #openstack-stable14:42
*** dims has joined #openstack-stable14:54
*** sigmavirus24_awa is now known as sigmavirus2414:56
*** ihrachys has joined #openstack-stable14:56
*** unlaudable has quit IRC15:32
*** Qiming has quit IRC15:36
*** sigmavirus24 is now known as sigmavirus24_awa15:57
*** sigmavirus24_awa is now known as sigmavirus2415:57
*** xhku has joined #openstack-stable15:58
*** xhku_ has joined #openstack-stable16:05
*** nikhil has joined #openstack-stable16:06
*** xhku has quit IRC16:06
*** xhku_ is now known as xhku16:21
*** xhku has quit IRC16:30
*** xhku has joined #openstack-stable16:30
*** xhku has quit IRC16:31
*** xhku has joined #openstack-stable16:31
*** david_lyle has quit IRC16:46
*** david_lyle has joined #openstack-stable16:46
*** e0ne has quit IRC16:49
*** armax has quit IRC16:56
*** eharney has quit IRC17:12
*** ihrachys has quit IRC17:25
*** eharney has joined #openstack-stable17:26
*** armax has joined #openstack-stable17:40
*** eharney_ has joined #openstack-stable17:51
*** eharney has quit IRC17:55
*** eharney_ is now known as eharney18:00
*** doug-fish has quit IRC18:07
*** doug-fish has joined #openstack-stable18:08
*** dtantsur is now known as dtantsur|afk18:11
*** doug-fish has quit IRC18:13
*** ihrachys has joined #openstack-stable18:14
*** xhku has quit IRC18:20
*** doug-fish has joined #openstack-stable18:27
*** thingee has joined #openstack-stable18:32
thingeemriedem: any decision with stable team's summit room allocation?18:32
mriedemthingee: i emailed ttx, dhellmann, mtreinish and fungi about that this morning18:33
mriedemtrying to see if we're going to do a joint session18:34
mriedemotherwise i wasn't really planning on doing a stable team specific session18:34
fungii'm in the process of replying now18:34
thingeemriedem: cool kids just do something informal in the dev lounge anyways18:35
mriedemi thought cool kids smoked in the bathroom?18:35
mriedemor is lung cancer no longer cool?18:35
thingeevape now I'm afraid18:35
*** sigmavirus24 is now known as sigmavirus24_awa18:37
*** ihrachys has quit IRC18:39
mriedemfungi: can you give me a rough idea of what the infra impacts are for stable branch maintenance? beyond just having more jobs running. i know that project-config gets messy with filters and such in zuul/layout.yaml. are there other things?18:54
fungimriedem: it increases requirements for platform diversity. while we're not using centos 6 or ubuntu precise in any stable branches now, we're probably going to end up testing mitaka on ubuntu xenial, so the longer we support kilo, liberty and mitaka the longer it will be before we can stop maintaining trusty workers18:57
fungier, i mean testing newton on xenial18:57
*** sigmavirus24_awa is now known as sigmavirus2418:57
mriedemyeah, so at one time we had precise and trusty workers18:58
mriedemseems we've been mostly in solely trusty for awhile18:58
fungiright, xenial releases around the mitaka release18:58
mriedemi think precise went out with icehouse? and py26 went out with juno18:58
fungiyep18:58
mriedemwell, we'll still be running trusty for stable/liberty18:59
fungiand it's possible we'd end up growing a dependence on centos 7 for testing certain features not in ubuntu sometime between now and when centos 8 is out18:59
mriedemso i'd think it shouldn't be any different to keep stable/kilo at least around for as long as stable/liberty, even if things get weird if they were to both EOL at the same time...18:59
mriedemfungi: yeah, but that's newton+ right?18:59
fungimriedem: right, i wasn't responding on kilo specifically but on policy in general18:59
mriedemi'm not sure what those features are18:59
mriedemprobably doesn't matter19:00
mriedemfor me i mean19:00
fungithings like test matrixing also get far more complex, regular expressions skipping/adding releases get longer, number of additional periodic jobs increases, fallback behaviors in devstack-gate and zuul-cloner grow more conditionals...19:01
mriedemyes, so there is technical debt in the tooling19:01
*** rockyg has joined #openstack-stable19:02
mriedemi think we'd only run periodic stable jobs for projects that have the stable:follows-policy tag19:02
fungiso more surface area to grow problems on19:02
mriedemand the periodic jobs are just running unit tests (as far as i'm aware)19:02
mriedemwell, fwiw, no projects have the stable:follows-policy tag yet :)19:02
fungigrenade gets especially worse to deal with when we have issues which need backporting to all supported stable branches (as you've experienced plenty first hand)19:03
mriedemi'm assuming you're referring to the problems with wedges due to pip resolver?19:03
*** doug-fis_ has joined #openstack-stable19:03
fungiso in general it's not a significant infra concern, rather that i hope there's an upper bound on the number of branches we'd be supporting in parallel19:03
mriedemok, that's good to know19:04
mriedemi think i'm really just wanting to extend kilo another cycle,19:04
mriedemso that makes the oldest branch 2 years old when it goes EOL19:04
*** doug-fi__ has joined #openstack-stable19:04
fungimriedem: really any issue that needs a fix in kilo so that the fix can be landed in liberty, so that upgrades from liberty to mitaka can be tested, so that the fix can be applied to mitaka, so that upgrades from mitaka to newton can be tested, so that the fix can be applied in newton19:04
mriedemthere are implications for lifeless' dependency spec, but that's been mostly idle19:04
mriedemfungi: yeah19:05
mriedemi honestly can't remember one of those since we axed juno19:05
fungithe more stable branches you add, the longer that chain gets19:05
*** doug-f___ has joined #openstack-stable19:05
fungianyway, i'm not opposed to the longer kilo support suggested, which is why i said 2-3 stable branches19:06
*** doug-fish has quit IRC19:06
*** doug-fish has joined #openstack-stable19:06
fungijust make sure you give yourself an out in case nobody steps up to keep kilo working in a couple months when it falls apart for some reason we're not capable of predicting right now19:06
mriedemso maybe in general, each branch has 18 months (as today), with an option for 24 months, unless exceptional circumstances bar a thing from going 24 months19:07
mriedemyeah that ^ you read my mind19:07
mriedemalso, once kilo is eol, that's the last mass release at the same time stable branch, so liberty becomes easier to eol b/c we can do it on a per-project basis19:07
*** doug-fis_ has quit IRC19:08
rockyg++19:08
fungimy objections from the vmt perspective have more to do with the fact that we need an ever increasing number of backports provided as attachments to private bugs and manually tested and reviewed there, possibly extending embargoes further19:08
mriedemif a change would break a project's oldest stable branch, it would break the stable policy for that project, so their only option would be to EOL the branch early19:08
*** doug-fi__ has quit IRC19:09
mriedemfungi: yeah...although, how hard are stable branch VMT reviews once there is agreement on the master branch fix? i know it's case by case depending on the fix.19:09
mriedemwe still support going back to grizzly internally, so i realize the backports become monsters19:09
*** doug-f___ has quit IRC19:10
fungifrequently quite hard. pretty often we have to make the call to not treat something as a vulnerability because it can't be fixed safely in a backward-compatible way in all "supported" stable releases19:10
fungiand the more supported releases we consider, the greater the risk that not all of them will be capable of being fixes as trivially as the most recent stable release19:11
fungier, being fixed19:11
mriedemfungi: so that might be a trigger for EOL19:11
mriedemfor the project in question anyway19:12
fungipremature eol is also not great for downstream users though, which is why making some attempt at predicting when you expect to cease being able to support a release is preferred19:12
mriedemi don't know about that too much, i expect most distros that are depending on stable branches have longer support contracts than what is upstream19:13
fungi"oh, look, everyone running kilo is vulnerable to this particular nasty thing but fixing it there would mean a non-backward-compatible behavior change. time to hang them out to dry and tell them to scramble on an unplanned upgrade to liberty"19:13
mriedemlike ibm, red hat at least19:13
fungiright, "use a distro with some long-term support guarantees and don't roll your own deployment from git"19:14
fungii suppose as long as we make sure the distros and the people doing installs from stable branches of git know that we could up and decide to eol them at any point without warning, then that's something the vmt can work with19:15
mriedembut to be fair, wasn't stable originally mostly supposed to be distro people?19:15
fungiyeop19:15
fungier, yep19:15
fungihowever, distro people have historically had little interest in keeping testing working upstream for stable branches, which means they don't really have anywhere to collaborate once it breaks19:16
mriedemyeah, i actually think your VMT example and the stable:follows-policy tag as the basis go together here19:16
mriedemif you have to make a backward incompatible change to a stable branch to fix a bug, that would break the stable policy, and end of life the branch19:16
mriedemfor that project19:17
fungiwhich is why the various discussions about cross-distro collaboration in the past have always seemed hollow to me19:17
mriedemsure, and i'm not really advocating for them either19:17
mriedemsome distro could maintain their stable branches in github if they wanted right?19:17
mriedemlike if ibm had a fork of openstack/nova and still maintained juno and icehouse in it19:18
rockygBut, at least with the projects more independent, there is a chance that you could roll forward with the just the eol'ed project and leave the rest of the install in place.19:18
rockygOnly works for a couple of the projects, but....better than none.19:18
fungiyep, it would be outside the openstack community infrastructure, and so would be considered unofficial from openstack's perspective, but they can certainly host whatever they want wherever they want if they choose to define "collaboration" as "not really tested, use at your own risk, kthxbai"19:19
mriedemfungi: yeah19:19
fungithat is below our quality assurance threshold as a community, so we can't really endorse it19:19
mriedemso, i guess we probably have enough meat on this bone that i should consider a session to talk through a proposal like this...19:19
fungii'll attend it if you slot it19:20
mriedemfishbowl style as ttx suggested19:20
mriedemok19:20
fungiand try to make sure we have good vmt/infra representation present19:20
rockygPlease!  I'll attend.  If I don't have other conflicts.  But I'll make the Huawei release guy attend, at least.19:20
fungisince i don't really want to be seen as assuming the opinions of others on those teams19:20
rockygSorry to barge in on this discussion, but I really am happy to see it.19:22
mriedemfungi: yeah, for sure. also, i know you're a busy guy so i appreciate your time to talk through this.19:23
fungimriedem: it's an important topic. especially if it means we reach a conclusion which makes me a less busy guy in the long run (or at least not even more busy)19:24
mriedemthingee: so i'm going to be looking for a fishbowl slot19:26
mriedemthingee: preferrably opposite a qa/vmt/infra slot if possible19:27
mriedemwell, opposite as not at the same time19:27
*** doug-fish has quit IRC19:38
*** rockyg has quit IRC19:50
*** doug-fish has joined #openstack-stable19:53
*** ihrachys has joined #openstack-stable19:55
*** rockyg has joined #openstack-stable20:04
*** doug-fish has quit IRC20:05
*** doug-fish has joined #openstack-stable20:06
*** rockyg has quit IRC20:09
*** doug-fis_ has joined #openstack-stable20:10
*** doug-fish has quit IRC20:11
*** david-lyle_ has joined #openstack-stable20:12
*** david_lyle has quit IRC20:13
*** david-lyle_ is now known as david-lyle20:26
*** sigmavirus24 is now known as sigmavirus24_awa20:58
*** stevemar has quit IRC20:59
*** shwetaap1 has joined #openstack-stable20:59
*** shwetaap has quit IRC21:01
*** stevemar has joined #openstack-stable21:01
*** dims has quit IRC21:07
*** e0ne has joined #openstack-stable21:10
*** sigmavirus24_awa is now known as sigmavirus2421:16
*** e0ne has quit IRC21:34
*** derekh has quit IRC21:36
*** sigmavirus24 is now known as sigmavirus24_awa21:41
*** sigmavirus24_awa is now known as sigmavirus2421:42
*** e0ne has joined #openstack-stable21:43
*** dims has joined #openstack-stable21:58
*** dims has quit IRC22:01
*** david-lyle has quit IRC22:02
*** david-lyle has joined #openstack-stable22:02
*** gnuoy_ has joined #openstack-stable22:07
*** e0ne has quit IRC22:11
*** gnuoy_ has quit IRC22:12
*** doug-fis_ has quit IRC22:20
*** doug-fish has joined #openstack-stable22:20
*** doug-fish has quit IRC22:23
*** doug-fish has joined #openstack-stable22:24
tonybfungi: A tangent to that discussion .... Now that we have Gerrit 2.11 deployed can we look at a "private" gerrit for VMT use?22:24
*** doug-fish has quit IRC22:26
*** doug-fish has joined #openstack-stable22:26
fungitonyb: yes, we can. zaro had a solution mostly designed for 2.8 but we held off until we could get production upgraded so that we didn't have two to upgrade22:26
fungisome additional infra bandwidth on that would be helpful22:27
tonybfungi: Clearly not infra but willing to help where I can.22:29
fungitonyb: we're all infra, there's just only so many of us who can approve patches or get shell access to the servers to troubleshoot oddities22:29
fungithat said, i'm continuing to grow the core reviewers and root sysadmins, so hopefully we'll find sufficient support among the ranks to finish that up22:30
tonybfungi: Sure.  Poorly choice of words on my behalf.22:30
*** jamielennox|away is now known as jamielennox22:38
*** ihrachys has quit IRC22:43
thingeemriedem: ack22:43
*** mriedem is now known as mriedem_away22:44
*** doug-fish has quit IRC22:53
*** doug-fish has joined #openstack-stable23:01
*** eharney has quit IRC23:05
*** mtreinish has quit IRC23:13
*** mtreinish has joined #openstack-stable23:14
*** shwetaap1 has quit IRC23:29
*** sigmavirus24 is now known as sigmavirus24_awa23:30
*** Qiming has joined #openstack-stable23:34
*** doug-fish has quit IRC23:37

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