Wednesday, 2016-05-11

*** crinkle has joined #openstack-stable01:03
*** mriedem has quit IRC01:45
*** armax has quit IRC03:27
*** pcaruana has joined #openstack-stable04:02
*** Qiming has quit IRC04:09
*** Qiming has joined #openstack-stable04:46
*** mrunge has quit IRC04:46
*** rcernin has joined #openstack-stable04:58
tonybHmmm a bunch of jobs just failed with "No matching distribution found for oslo.config<1.10.0,>=1.9.3"06:16
tonybwhich is 1.9.3 is aproximately the current kilo branch, it's "tagged" in the released repo06:16
tonyband was there yesterday .... http://logs.openstack.org/periodic-stable/periodic-sahara-docs-kilo/8a109ec/console.html#_2016-05-10_06_07_55_04806:17
tonybOh it's still there, possibly released to pip 8.1.206:23
*** david-lyle has quit IRC06:23
*** david-lyle has joined #openstack-stable06:27
-openstackstatus- NOTICE: pip 8.1.2 broke our local python mirror, some jobs will fail with "No matching distribution found". We're investigating. Do not "recheck" until the issue is solved07:07
*** ChanServ changes topic to "pip 8.1.2 broke our local python mirror, some jobs will fail with "No matching distribution found". We're investigating. Do not "recheck" until the issue is solved"07:07
*** rcernin has quit IRC07:09
*** rcernin has joined #openstack-stable07:10
*** e0ne has joined #openstack-stable07:11
kashyapHeya tonyb - you took a look at this the other day for the Mitaka backport, here's the Liberty one -- https://review.openstack.org/#/c/314012/407:30
kashyapI'd also like a quick look at it from Dan Smith from a unit tests POV, but you can feel free to look at it if you have time.07:31
*** derekh has joined #openstack-stable08:51
*** tesseract has joined #openstack-stable09:20
*** dtantsur|afk is now known as dtantsur09:30
tonybkashyap: Will do.  I was hoping to get to it today but my afternoon didn't go as planned.09:44
*** apevec has joined #openstack-stable09:52
*** apevec has quit IRC09:52
*** apevec has joined #openstack-stable09:52
*** Qiming has quit IRC10:09
*** stevemar has quit IRC10:13
*** stevemar has joined #openstack-stable10:15
DavieyAnyone remmeber where the eol process is documented ?10:20
Davieyis it just tag and ask infra to delete the branches?10:20
kashyaptonyb: No worries; thanks10:27
*** amrith is now known as _amrith_10:38
apevecDaviey, process is "ask fungi" :)10:45
apeveche has scripts to push RELEASE-eol tags where needed and to delete branches10:46
odyssey4meit might be good to ask fungi to add those scripts to the release repo?11:00
DavieyAP thanks11:02
Davieyapevec: Thanks11:02
apevecodyssey4me, yeah, they are probably in git somewhere and just not documented11:03
apevecit take infra super power to drop branch I guess11:03
kashyapapevec: Hi, when you get a moment -- you've approved the Mitaka backport, mind taking a look at the Liberty one too? -- https://review.openstack.org/#/c/314012/411:05
apevecI don't mind - backup does get uglier as you back into older releases, doesn't it11:08
apeveckashyap, so is that adding performance hit?11:10
kashyapapevec: No performance hit, it fixes a proper bug, even in Liberty.  Some folks expressed this as a blocker for deployment.11:10
apevecor is utils.get_image_from_system_metadata(instance.system_metadata) cached?11:10
kashyapapevec: Yes, it's cached, as near as I read the code11:11
*** Qiming has joined #openstack-stable11:12
kashyapapevec: If you feel uncomfortable ACKing the change, can understand.11:12
kashyapI can let Dan Smith or Matt Ridemann (who tried to backport this to Liberty before me) comment on the unit test change too.11:12
*** mrunge has joined #openstack-stable11:20
apeveckashyap, +2 after RTFSing11:34
kashyapapevec: Thanks! First me too delving in this area.  (You can tell that from the master review.) :-)11:35
apevecbut yes, I'm leaving +W to someone from nova-maint11:35
kashyapUnderstood, Tony said above, he'll take a look.  Or Matt, when he's back.11:35
*** _amrith_ is now known as amrith11:51
*** ChanServ changes topic to "reviews: http://tiny.cc/os-stable-dash | issues: https://etherpad.openstack.org/p/stable-tracker"11:59
-openstackstatus- NOTICE: We have a workaround for our mirrors to attempt to translate package names if a match isn't immediately obvious. A more complete fix is yet to come. It is now safe to 'recheck' any jobs that failed due to "No matching distribution found". Please join #openstack-infra if you discover more problems.11:59
*** takedakn has joined #openstack-stable12:11
*** eharney has joined #openstack-stable12:39
*** jamielennox is now known as jamielennox|away12:45
*** takedakn has quit IRC12:47
*** jamielennox|away is now known as jamielennox12:53
*** Nakato has quit IRC13:08
*** Nakato has joined #openstack-stable13:08
fungiapevec: Daviey: it's not really that i have "scripts" i just usually compose a shell one-liner to push tags and delete branches for whatever list of repos i'm given. most of the effort involved is carefully double-checking everything worked correctly13:16
*** mriedem has joined #openstack-stable13:16
fungiit's just git commands13:16
fungier, odyssey4me ^13:16
fungiand yeah, it mainly needs a gerrit admin so that the branches can be deleted. we could in theory delegate the tagging part via acls (though we can't restrict tagging to specific branches)13:18
fungianyway, doesn't have to be me. can really be any of our ~dozen gerrit admins on the infra team13:19
fungii just happen to have done it for the past few (5?)13:21
fungiyeah, looking at nova's tag history at least, ttx eol'd diablo and essex, i started doing it with folsom13:21
odyssey4mefungi dhellmann perhaps the EOL process should fall into line with the release process and be handled through a review to the releases repo?13:23
fungipossibly, though as i said we'd need an account with gerrit admin privileges to be able to do part of it13:24
odyssey4mefungi the release team already have the branch and tag ACL's afaik so it makes sense for it to fall in with them13:25
fungisure, but they don't have branch deletion access because gerrit doesn't let you delegate that via an acl13:26
fungifor some reason they've chosen to conflate it with the ability to bypass access restrictions and code review13:27
*** eharney has quit IRC13:33
Davieyfungi: I have ACL for git tags, but guessing i don't to delete branches?13:34
fungiDaviey: right13:34
Davieyfungi: Shall i push the eol tags, and you delete then?13:35
Daviey(does that mirror across to GH automatically?)13:35
fungiDaviey: sounds great. i'm happy to let the stable release team own as much of the eol process as they want, and just give infra a list of projects where you want that branch deleted when you're done13:35
fungiDaviey: and yeah, it mirrors auomatically13:36
Davieyfungi: pucka13:36
*** eharney has joined #openstack-stable13:45
*** sigmavirus24_awa is now known as sigmavirus2414:01
Davieyfungi: can you delete stable/kilo for: ceilometer cinder glance heat horizon ironic keystone neutron neutron-lbaas nova sahara neutron-vpnaas trove14:03
Davieyta14:03
fungiDaviey: that seems like a waaaaay shorter list than we've been eol'ing in the past14:06
fungiwe usually also did libraries, branched dev tools, et cetera14:06
fungiis this just an initial batch?14:06
fungii can pull up the juno eol announcement where i listed the ones i did that time around14:07
fungiDaviey: http://lists.openstack.org/pipermail/openstack-announce/2015-December/000869.html14:09
*** Qiming_ has joined #openstack-stable14:17
*** Qiming has quit IRC14:18
*** xhku has joined #openstack-stable14:30
dhellmannodyssey4me , Daviey, fungi : it would be cool to add support for eol tags to the release repo. I think the validator would need to be taught that the named tags are valid, since it restricts to something that looks like a valid version right now14:39
*** e0ne has quit IRC14:49
*** Qiming_ has quit IRC14:53
*** mugsie has joined #openstack-stable15:16
mugsietonyb: any chance of a o/requirements review on 2 stable branches? https://review.openstack.org/#/q/Ib3849cd5c0f4908c0b19787ed84891d7a49f63e115:19
mugsietrying to fix the issue we saw last night in the periodic jobs for designate15:19
*** amrith is now known as _amrith_15:31
*** armax has joined #openstack-stable15:32
*** _amrith_ is now known as amrith15:33
*** armax has quit IRC15:40
*** rcernin has quit IRC15:47
*** e0ne has joined #openstack-stable15:49
apevecDaviey, fungi - yeah, I think all stable/kilo should be tagged and killed otherwise it's not proper EOL15:49
*** armax has joined #openstack-stable15:53
*** dtantsur is now known as dtantsur|afk15:56
*** armax has quit IRC15:57
fungialso we'll want openstack-infra/project-config to stop running periodic jobs on stable/kilo for the projects that got eol'd and maybe some related cleanup to job configs there16:20
fungias those will begin reporting failures the next time they try to run after the branches are deleted16:21
*** armax has joined #openstack-stable16:21
mugsieany stable team around to give https://review.openstack.org/#/q/Ib3849cd5c0f4908c0b19787ed84891d7a49f63e1 an OK on the 2 stable branches? it is blocking our stable/liberty+mitaka gates16:33
Davieysorry chaps.. real life got in the way16:37
Davieyfungi, apevec, dhellmann: should i push tags for all the projects on http://lists.openstack.org/pipermail/openstack-announce/2015-December/000869.html ?16:39
fungiDaviey: well, each time i've gone through this, i've had to put together a list of candidate repos based on ever-changing criteria. last time it was based on some of the release management tags (methodology for building the lists noted in that e-mail)16:41
dhellmannDaviey : I think so? There may be a few more repos for kilo, actually.16:41
dhellmannyeah, there's a script in the release-tools repo that makes querying the governance yaml file pretty easy16:42
fungiyeah, basically need to go through a similar exercise16:42
dhellmannalthough now there's no "has-stable-branches" tag so it might be harder for that reason16:42
fungisince this list changes every time16:42
dhellmannthis might actually be justification for having series-specific stable tags in governance, to make it easier to produce the list of things the stable team deals with for a given release even if the rules for that change over time16:43
fungidhellmann: amusingly, i just had a vulnerability:managed tag discussion which reminded me that we probably need series-specific details for that as well16:44
dhellmannfungi : that makes it a pattern, right? seems legit, let's do it.16:44
fungitotally16:45
dhellmannin all seriousness, it's worth experimenting with. tonyb, what do you think?16:46
fungii have a feeling the use cases are similar. the vmt supports projects' stable branches starting with a particular release, so for example we'll only expect kolla security fix backports on stable/newton (once it exists, and if they meet the other requirements) and later, but not earlier branches16:53
fungihaving that tracked in governance would be a big improvement16:54
fungiright now we're getting by because we haven't officially added vulnerability management on a new deliverable going back to before the currently existing stable branches16:54
*** derekh has quit IRC16:55
dhellmannthat's a similar situation with stable, where it's useful to know not just that a project followed the policy but for which releases17:05
dhellmannthe all-or-nothing plan we came up with the other day feels a bit lacking in flexibility, really17:05
*** mriedem1 has joined #openstack-stable17:27
*** mriedem has quit IRC17:28
*** mriedem1 is now known as mriedem17:31
*** e0ne has quit IRC17:31
*** sileht has quit IRC17:37
*** sileht has joined #openstack-stable17:44
*** e0ne has joined #openstack-stable17:46
*** e0ne has quit IRC17:59
odyssey4medhellmann fungi it makes sense to me that some tags should be per-series - some projects may only opt-in for the tags at a point in time onwards, and some may opt-out at some point for whatever reasons18:07
odyssey4medhellmann also worth consideration is the effect of the cycle-trailing tag on EOL processes... do the cycle-trailing projects have the extra two weeks to complete an EOL cycle?18:08
dhellmannthat's a great question. I'd say no, since they should only need that 2 weeks when the initial release of their dependencies is created18:09
odyssey4medhellmann in our case we fix SHA's every two weeks18:14
odyssey4meour current tag release is scheduled for next week - then we'll bump SHA's to the EOL tags, and release that two weeks later... so we effectively are going to EOL a bit later than the services18:15
odyssey4methere is some risk in that for Kilo, but for Liberty onwards (due to upper-constraints) we have a very low risk of problems caused by the services no longer being tested in OpenStack-CI18:15
fungiif teh trailing release projects want to do eol on a different cadence, that seems reasonable to me18:19
fungialso the process is easy enough for non-managed (including unofficial) projects to follow on their own18:19
fungii'm happy to handle branch deletion requests as long as they abandon any open changes for those branches first18:20
dhellmannok, I'm willing to be outvoted :-)18:21
fungii also agree this probably changes somewhat for liberty and later, since we don't have coordinated stable point releases18:23
fungiso there's not necessarily a release immediately prior to eol18:23
fungithe process likely needs to evolve to projects making their final stable point release requests (where needed) by x date, and then we'll eol on x+N date18:23
fungiand if N is sufficiently long for the trailing release projects to get their releasing done, then maybe actual eol still happens at the same point in time for all of them18:25
odyssey4medhellmann does it make sense to evolve the EOL process into using the release repo?18:28
odyssey4meie EOL's are requested by review, and the EOL tag and branch deletions are automated (eventually)18:29
dhellmannodyssey4me : yes, I think so18:40
*** e0ne has joined #openstack-stable18:44
*** e0ne has quit IRC18:45
*** tesseract has quit IRC18:51
*** amrith is now known as _amrith_19:16
*** e0ne has joined #openstack-stable19:39
*** e0ne has quit IRC19:41
*** e0ne has joined #openstack-stable20:11
*** e0ne has quit IRC20:13
*** _amrith_ is now known as amrith20:19
*** pcaruana has quit IRC20:42
*** rcernin has joined #openstack-stable20:44
*** xhku has quit IRC20:45
*** eharney has quit IRC21:08
*** mriedem has quit IRC21:47
*** apevec has quit IRC21:53
*** sigmavirus24 is now known as sigmavirus24_awa22:19
*** jamielennox is now known as jamielennox|away23:02
*** zigo has quit IRC23:14
*** Daviey has quit IRC23:15
*** Daviey has joined #openstack-stable23:15
*** zigo has joined #openstack-stable23:15
tonybmugsie: I'll look at those today.23:37
tonybdhellmann: I'm not certain I understand your proposal, but I'm in favour of moving as much state into public places as possible.23:39
*** Qiming_ has joined #openstack-stable23:39
*** mriedem has joined #openstack-stable23:45
*** jamielennox|away is now known as jamielennox23:51
*** Qiming_ has quit IRC23:58

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