Tuesday, 2017-08-01

*** yamamoto has quit IRC00:01
*** yamamoto has joined #openstack-release00:05
*** ricolin has joined #openstack-release00:14
*** mriedem has quit IRC00:30
*** armax has quit IRC00:34
*** mriedem has joined #openstack-release00:38
*** harlowja has quit IRC00:38
*** zhurong has joined #openstack-release00:43
*** thorst_afk has joined #openstack-release00:46
*** rajathagasthya has quit IRC00:53
*** thorst_afk has quit IRC00:54
*** liujiong has joined #openstack-release01:08
*** sdague has quit IRC01:08
*** yamamoto has quit IRC01:25
*** thorst_afk has joined #openstack-release01:29
*** yamamoto has joined #openstack-release01:29
*** gcb has joined #openstack-release01:30
*** ekcs has quit IRC01:33
*** ricolin has quit IRC01:34
*** gcb has quit IRC01:37
*** thorst_afk has quit IRC01:38
*** thorst_afk has joined #openstack-release01:38
*** gcb has joined #openstack-release01:39
*** thorst_afk has quit IRC01:43
*** https_GK1wmSU has joined #openstack-release01:50
*** https_GK1wmSU has left #openstack-release01:50
*** yamamoto has quit IRC01:51
*** armax has joined #openstack-release01:52
*** thorst_afk has joined #openstack-release01:55
*** thorst_afk has quit IRC01:55
*** yamamoto has joined #openstack-release01:56
*** yamamoto has quit IRC02:07
*** yamahata has quit IRC02:08
*** mriedem has quit IRC02:10
*** thorst_afk has joined #openstack-release02:11
*** rajathagasthya has joined #openstack-release02:17
*** yamamoto has joined #openstack-release02:19
*** hongbin has joined #openstack-release02:21
*** harlowja has joined #openstack-release02:22
*** thorst_afk has quit IRC02:25
*** bobh has joined #openstack-release02:26
*** rajathagasthya has quit IRC02:34
*** ricolin has joined #openstack-release02:42
*** harlowja has quit IRC02:44
*** liujiong has quit IRC02:50
*** liujiong has joined #openstack-release02:51
*** hongbin_ has joined #openstack-release02:55
*** prometheanfire has joined #openstack-release02:55
prometheanfiredon't know if tony asked already, but can we get an [n]ack for a FFE on https://review.openstack.org/48937602:56
*** hongbin has quit IRC02:57
*** hongbin has joined #openstack-release02:59
*** hongbin_ has quit IRC03:00
*** yamamoto has quit IRC03:01
*** yamamoto has joined #openstack-release03:06
*** lbragstad_ has joined #openstack-release03:14
*** lbragstad has quit IRC03:14
*** yamamoto has quit IRC03:21
*** bobh has quit IRC03:23
*** yamamoto has joined #openstack-release03:24
*** yamamoto has quit IRC03:36
*** harlowja has joined #openstack-release03:38
*** udesale has joined #openstack-release03:43
*** yamamoto has joined #openstack-release03:44
*** dave-mcc_ has quit IRC03:48
*** yamamoto has quit IRC04:04
*** hongbin has quit IRC04:05
*** yamamoto has joined #openstack-release04:09
*** ekcs has joined #openstack-release04:16
*** ekcs has quit IRC04:23
*** thorst_afk has joined #openstack-release04:26
*** thorst_afk has quit IRC04:31
*** udesale__ has joined #openstack-release04:32
*** udesale has quit IRC04:34
*** harlowja has quit IRC05:10
*** jtomasek has joined #openstack-release05:20
*** https___GK1wmSU has joined #openstack-release05:25
*** https___GK1wmSU has left #openstack-release05:26
*** gcb has quit IRC05:29
*** gcb_ has joined #openstack-release05:29
*** harlowja has joined #openstack-release05:51
*** yamahata has joined #openstack-release06:01
*** wolverineav has joined #openstack-release06:18
*** wolverineav has quit IRC06:22
*** thorst_afk has joined #openstack-release06:28
*** thorst_afk has quit IRC06:32
ttxprometheanfire: lgtm06:48
*** harlowja has quit IRC06:51
prometheanfirethanks06:52
*** alexchadin has joined #openstack-release06:56
*** dtantsur|afk is now known as dtantsur07:01
*** pcaruana has joined #openstack-release07:06
*** dtantsur is now known as dtantsur|bbl07:47
*** clarkb has quit IRC08:04
*** clarkb has joined #openstack-release08:17
*** lucas-afk is now known as lucasagomes08:26
*** thorst_afk has joined #openstack-release08:27
*** thorst_afk has quit IRC08:32
*** pbandark has joined #openstack-release08:40
*** electrofelix has joined #openstack-release08:44
*** ricolin has quit IRC08:51
*** alexchadin has quit IRC08:53
*** alexchadin has joined #openstack-release08:56
*** yamahata has quit IRC09:17
*** sdague has joined #openstack-release09:20
*** tosky has joined #openstack-release09:24
*** coolsvap has joined #openstack-release09:32
*** yamamoto has quit IRC09:37
*** udesale__ has quit IRC09:56
*** yamamoto has joined #openstack-release09:57
*** wolverineav has joined #openstack-release09:59
*** yamamoto has quit IRC10:08
*** dtantsur|bbl is now known as dtantsur10:11
*** liujiong has quit IRC10:12
*** mugsie has quit IRC10:22
*** mugsie has joined #openstack-release10:25
*** mugsie has quit IRC10:25
*** mugsie has joined #openstack-release10:25
*** yamamoto has joined #openstack-release10:25
*** thorst_afk has joined #openstack-release10:28
*** mugsie has quit IRC10:31
*** thorst_afk has quit IRC10:32
*** mugsie has joined #openstack-release10:33
*** mugsie has quit IRC10:33
*** mugsie has joined #openstack-release10:33
*** alexchadin has quit IRC10:35
*** alexchadin has joined #openstack-release10:36
dimsttx : dhellmann : smcginnis : o/10:51
*** tellesnobrega has quit IRC10:51
*** alexchadin has quit IRC11:08
*** alexchadin has joined #openstack-release11:12
*** yamamoto has quit IRC11:17
*** alexchadin has quit IRC11:22
ttxdims, dhellmann, smcginnis: o/11:30
*** yamamoto has joined #openstack-release11:32
*** tellesnobrega has joined #openstack-release11:33
*** thorst_afk has joined #openstack-release11:40
*** efried has quit IRC11:40
*** yamamoto has quit IRC11:49
*** lucasagomes is now known as lucas-hungry11:52
*** efried has joined #openstack-release11:52
*** claudiub has joined #openstack-release12:06
*** thorst_afk has quit IRC12:22
*** udesale has joined #openstack-release12:23
ttxRecent group-based-policy-tarball job fail is a weird job timeout 1 hour after the task completed12:25
ttxcould be unrelated infra issues12:26
*** mriedem has joined #openstack-release12:27
*** tellesnobrega has quit IRC12:45
*** tellesnobrega has joined #openstack-release12:45
*** yamamoto has joined #openstack-release12:49
*** lucas-hungry is now known as lucasagomes12:50
*** electrofelix has quit IRC12:52
*** dave-mccowan has joined #openstack-release12:54
*** mriedem has quit IRC12:57
*** thorst_afk has joined #openstack-release12:57
*** electrofelix has joined #openstack-release12:58
*** yamamoto has quit IRC12:59
*** mriedem has joined #openstack-release13:06
openstackgerritLance Bragstad proposed openstack/releases master: Release oslo.policy 1.25.1  https://review.openstack.org/48959913:20
lbragstad_dhellmann: looks like those backports to oslo.policy landed - i've proposed a release of oslo.policy stable/pike13:22
lbragstad_https://review.openstack.org/#/c/489599/13:22
*** claudiub has quit IRC13:25
*** tosky has quit IRC13:31
*** hongbin has joined #openstack-release13:38
smcginniso/13:45
smcginnislbragstad_: Issue with one part of that release patch.13:47
*** liujiong has joined #openstack-release13:48
smcginnisttx: WRT that group-based-policy-tarball failure - what needs to be done when a job like that fails?13:50
openstackgerritLance Bragstad proposed openstack/releases master: Release oslo.policy 1.25.1  https://review.openstack.org/48959913:54
lbragstad_smcginnis: good catch - thanks!13:54
*** lbragstad_ is now known as lbragstad14:04
dhellmanndims, ttx, smcginnis : o/14:08
dhellmannsmcginnis : for that case, since it's not an official project, we don't do anything unless they come to ask for help14:09
dhellmannsmcginnis : for official projects, we debug the failure and either retrigger the job (ask infra to), or work with the team to fix the issue and tag a new release with a new number14:09
dhellmannttx: did you have a chance to look at the yaml normalization patches? topic "queens-indentation"14:09
smcginnisdhellmann: Thanks. Yeah, wasn't sure how to retrigger a job like that. Makes sense.14:10
dhellmannsmcginnis : fungi usually does that, although some of the other infra cores can do it, too. I forget exactly which superpower you need to do it.14:11
fungiany of the infra-root sysadmins can. it's just a tool you have to run from the command-line on the zuul.openstack.org server (the main scheduler for the ci system)14:12
smcginnisdhellmann, fungi: Nice, thanks for the info. Learning what I can. ;)14:12
dimssmcginnis : don't know if you know, "infra-root" is a keyword on the -infra channel which all the folks with super powers watch for14:12
fungiwhich tool depends on the situation (whether you need to retrigger just a single job or want to reenqueue an entire ref)14:12
fungiso for example if a tarball build in the release pipeline fails, we would want to reenqueue that tag ref into the release pipeline so that all the jobs for it get rerun properly14:13
smcginnisdims: That the magic incantation. :)14:14
fungihowever if the release announcement job fails in that situation, we would want to just retrigger that job because the tarballs/wheels were already built and uploaded to pypi so can't be rerun14:14
dhellmannfungi : it would be pretty cool to have a way to let us propose retriggering jobs like that, with infra approving, instead of having to take manual action. Is there anything like that on the zuul3 roadmap?14:15
* dhellmann feels like he may have asked that question once before14:15
*** liujiong has quit IRC14:15
funginot that i'm aware of (and there's not much roadmap left for zuul v3 anyway, we're talking about go-live right before/at the ptg)14:15
fungibut there are a lot more options we can leverage in v3 to more easily implement something like that14:16
dhellmanncool, maybe that's a conversation to have in denver, then14:17
fungihowever, that sort of runs counter to our design philosophy. if jobs fail often enough that you need to do something to address that situation, spend your time making the jobs more robust rather than designing elegant workarounds for broken things14:18
fungibecause making the brokenness less painful just gives you more excuses not to address the root cause14:19
fungiand leads to crappy software14:19
dhellmannsure, that makes sense. maybe we should review the way we have some of these jobs chained, so we can retrigger them by landing another patch in the releases repo14:22
fungiso it's a balance to strike between problems we can solve in software and problems outside our control (like external to the environment or intrinsic to standard protocols)14:22
dhellmannwe could avoid a lot of the release announce failures by testing that in the validation job in the releases repo14:23
dhellmannthat one has been on my todo list for a while14:23
ttxdhellmann: looking14:24
dhellmannttx: I'm trying to address the indentation issue that trips us up periodically because of differences in tools and in our existing data files14:25
ttxok14:25
dhellmannthat should make it easier to have commands to do batch operations like adding a bunch of branches or tagging the final release14:25
*** udesale has quit IRC14:26
fungidhellmann: what angle are you taking? just straight-up parser correctness addressable by something like yamllint or do you need schema validation a la voluptuous?14:26
dhellmannfungi : we have both in place, but the linter was not configured to enforce the same indentation everywhere so it was only enforcing consistency within a file. That means some files have lists with members that are not indented, and others have lists with members that are indented.14:27
fungiahh14:28
dhellmannadding an element to the list then either resulted in incorrect indentation (when we treated the file as text and just appended to it) or reindented the entire file (when we treated the file as a serialized data structure and reserialized it)14:28
fungigot it, so you mostly have a solution implemented and just need to tweak it to catch some things it currently misses14:29
dhellmannthis series of patches nudges us down the road toward serialized data structures14:29
dhellmannyeah14:29
dhellmannthere's a jsonschema check and a linter check they're just incomplete14:29
openstackgerritDoug Hellmann proposed openstack/releases master: add new-release and edit-deliverable to helpers list in readme  https://review.openstack.org/48940514:30
openstackgerritDoug Hellmann proposed openstack/releases master: add release-notes URLs for some pike deliverables  https://review.openstack.org/48940314:30
ttxreviewed half, jumped on a call, will finish after14:35
jeblairsmcginnis: oh hi!  /me wakes up and checks infra-root bat-signal14:41
fungijeblair: no emergency, mostly zuul(v3) details/discussion14:44
dhellmannttx: thanks14:45
*** tellesnobrega has quit IRC14:48
smcginnisjeblair: :)14:50
*** bobh has joined #openstack-release15:06
*** pcaruana has quit IRC15:22
ttxdhellmann: all reviewed15:24
ttxdhellmann approve before it merge-conflicts :)15:24
ttxclarkb, dhellmann: do you need me around the infra team meeting tonight ? I can probably attend if needed15:26
dhellmannttx: maybe smcginnis or dims can do the approvals15:29
ttxmaybe, yes :)15:29
dhellmannttx, clarkb : if it's just a matter of when it's safe to take gerrit down for an upgrade, we could talk about that now and I can relay15:29
*** claudiub has joined #openstack-release15:29
clarkbttx: only if you are particularly concerned about the scheduling of a downtime and upgrade15:30
dhellmannclarkb : do you have a proposed date?15:30
clarkbbasially trying to find a good spot between enough lead time for announing to community, release, and ptg15:30
ttxdhellmann: what's the status on stable/pike branch creation ?15:31
* dhellmann notes the PTG date is not on https://releases.openstack.org/pike/schedule.html15:31
ttxThe only big train of things we have is that large patchseries15:31
clarkbdhellmann: week before ptg and week after ptg are what I think may be easiest on everyone but is quite a ways out15:31
dhellmannttx: all of the libs are branched. We wait for the services rc1 to branch.15:31
ttxso this week is probably the best moment anyway15:31
dhellmannptg is sept 11, right?15:31
ttxas long as it's off any releases repo change15:31
ttxyes15:31
ttxIt appears in the Queens schedule15:31
ttx(tentative)15:32
dhellmannah15:32
* smcginnis pulls up dhellmann's list of patches...15:32
dhellmannoh, right, since it's the queens ptg15:32
smcginnisRight, I thought I saw it in the queens schedule.15:32
dhellmannI may add a cross-reference anyway15:32
smcginnisI wonder if those we should try to mention in both? Maybe overkill.15:32
dhellmannsmcginnis : yeah, that's what I was thinking15:32
dhellmannI suppose the danger is that we'd end up with it in the ical file twice15:32
dhellmannmaybe I can make it not do that15:33
smcginnisdhellmann: Not the end of the world if there's two cal entries.15:33
ttxI think it should only be on the queens one15:33
smcginnisAt least my calendar is a mess anyways. :)15:33
ttxsince it's a queens thing15:33
dhellmannclarkb : before or after the ptg seem like good timing15:33
dhellmannttx: that's fair15:33
smcginnisttx: True.15:33
dhellmannI was thinking of a cross-reference, since there's overlap between the calendars15:34
dhellmannbut it's not a big deal15:34
dhellmannwe don't technically need gerrit for the final release, but I would hate to have it down if we had a critical bug to fix in that timeframe15:35
clarkband no concerns with it early in queens?15:35
* dims peeks15:35
*** armax has quit IRC15:36
smcginnisdhellmann: We don't have a risk of any automation seeing these deliverable merges and kicking off something because they appear to be changes, right?15:37
dhellmannclarkb : early in the cycle is usually better for something like this, right?15:38
dhellmannclarkb : smcginnis should weigh in, since he's ptl for queens :-)15:38
smcginnisdhellmann: Well, not yet. Could have a dark horse. :)15:38
smcginnisclarkb, dhellmann: But yeah, I think early in queens would be safer.15:39
openstackgerritMerged openstack/releases master: fix format-yaml to work with python 3  https://review.openstack.org/48860615:39
smcginnisNo need to shoot ourselves in the foot if something goes wrong and we are without it.15:39
*** pcaruana has joined #openstack-release15:40
openstackgerritMerged openstack/releases master: use yamlutils.dumps() in new-release command  https://review.openstack.org/48884515:40
openstackgerritMerged openstack/releases master: use yamlutils.dumps() in init-series  https://review.openstack.org/48884615:40
openstackgerritMerged openstack/releases master: add wrapper for yamllint  https://review.openstack.org/48938015:40
openstackgerritMerged openstack/releases master: ensure version numbers always have quotes  https://review.openstack.org/48938115:40
*** armax has joined #openstack-release15:40
clarkbsmcginnis: dhellmann ok that is what I figured but wanted to make double sure15:41
openstackgerritMerged openstack/releases master: use yes/no for boolean values in reformatter  https://review.openstack.org/48938215:41
dhellmannclarkb : do you still need us in the meeting today?15:42
clarkbdhellmann: I don't think so, not if either of those weeks work for you. Will ping if that doesn't work for infra for some currently unknown reason and we can go from there15:43
dhellmannclarkb : wfm, thanks15:43
smcginnis++15:44
ttx++15:55
*** claudiub has quit IRC16:08
*** ricolin has joined #openstack-release16:17
*** lucasagomes is now known as lucas-afk16:23
*** rajathagasthya has joined #openstack-release16:30
*** yamahata has joined #openstack-release16:31
*** ragasthya has joined #openstack-release16:33
openstackgerritMerged openstack/releases master: do not add line wraps to text when reformatting  https://review.openstack.org/48938316:34
*** rajathagasthya has quit IRC16:35
openstackgerritMerged openstack/releases master: normalize independent deliverable files  https://review.openstack.org/48938416:35
smcginnisdhellmann: Want to send something brief to the ML letting folks know about the deliverable format changes?16:40
smcginnisdhellmann: Just thinking next time around we might have people confused why something that worked that last few releases suddenly doesn't.16:40
dhellmannsmcginnis : makes sense16:40
smcginnisdhellmann: Or I can mention it. Just thinking it should be noted somewhere.16:41
dhellmannyes, definitely16:45
*** bobh has quit IRC16:47
openstackgerritMerged openstack/releases master: normalize oslo deliverable files  https://review.openstack.org/48938516:48
openstackgerritMerged openstack/releases master: normalize client deliverable files  https://review.openstack.org/48938616:48
smcginnisdhellmann: Quick question on here: https://review.openstack.org/#/c/489401/316:50
openstackgerritMerged openstack/releases master: normalize tripleo deliverable files  https://review.openstack.org/48938716:50
openstackgerritMerged openstack/releases master: normalize puppet deliverable files  https://review.openstack.org/48938816:54
openstackgerritMerged openstack/releases master: normalize misc deliverable files  https://review.openstack.org/48938916:54
openstackgerritMerged openstack/releases master: standardize indentation at 2 spaces  https://review.openstack.org/48860716:54
openstackgerritMerged openstack/releases master: add linter rules for vertical whitespace  https://review.openstack.org/48860816:54
openstackgerritMerged openstack/releases master: remove obsolete tool script for adding team names  https://review.openstack.org/48940016:54
*** tellesnobrega has joined #openstack-release16:58
*** bobh has joined #openstack-release16:58
*** pcaruana has quit IRC16:58
*** dtantsur is now known as dtantsur|afk17:13
*** ragasthya has quit IRC17:34
*** yamahata has quit IRC17:43
*** electrofelix has quit IRC17:43
openstackgerritDoug Hellmann proposed openstack/releases master: treat deliverable files as utf-8 in edit-deliverable  https://review.openstack.org/48968417:44
*** rajathagasthya has joined #openstack-release17:48
openstackgerritMerged openstack/releases master: add edit-deliverable command  https://review.openstack.org/48940117:49
openstackgerritMerged openstack/releases master: use edit-deliverable in script to set the release notes URLs  https://review.openstack.org/48940217:50
openstackgerritMerged openstack/releases master: add release-notes URLs for some pike deliverables  https://review.openstack.org/48940317:52
openstackgerritMerged openstack/releases master: add new-release and edit-deliverable to helpers list in readme  https://review.openstack.org/48940517:53
openstackgerritMerged openstack/releases master: treat deliverable files as utf-8 in edit-deliverable  https://review.openstack.org/48968417:54
openstackgerritLance Bragstad proposed openstack/releases master: Release oslo.policy 1.25.1  https://review.openstack.org/48959917:55
*** ekcs has joined #openstack-release18:03
dhellmannsmcginnis : http://lists.openstack.org/pipermail/openstack-dev/2017-August/120423.html18:07
smcginnisdhellmann: Excellent!18:09
*** EmilienM is now known as emacchi18:14
*** emacchi is now known as EmilienM18:14
smcginnislbragstad: Hey, was there discussion on IRC or the ML about releasing that new oslo.policy? Just looking for background and reason for doing it past lib freeze.18:14
lbragstadsmcginnis: yeah - dhellmann and i were talking about it last week in -dev, let me see if i can find it18:17
lbragstadsmcginnis: http://eavesdrop.openstack.org/irclogs/%23openstack-dev/%23openstack-dev.2017-07-28.log.html#t2017-07-28T15:58:2318:17
smcginnislbragstad: Thanks18:18
lbragstadsmcginnis: no problem18:20
*** yamahata has joined #openstack-release18:20
smcginnislbragstad: Sorry, I know you're in your team meeting right now, so no rush.18:23
smcginnislbragstad: Is this needed now? Seems safe enough to release after the freeze is over.18:23
*** pbandark has quit IRC18:42
lbragstadsmcginnis: the main reason we saw the importance of backporting those fixes was because it would allow us to use the show-policy directive supplied by oslo.policy to render our policy documentation in the configuration reference (for the doc-migration) work18:56
lbragstadsmcginnis: for example - https://review.openstack.org/#/c/488508/18:57
lbragstadsmcginnis: https://bugs.launchpad.net/keystone/+bug/1707246 contains a bunch of context too if you haven't already seen it18:57
openstackLaunchpad bug 1707246 in OpenStack Identity (keystone) "Configuration guide references configuration options for policy instead of sample policy file" [Low,In progress] - Assigned to Lance Bragstad (lbragstad)18:57
smcginnisDoes seem very low risk. dhellmann, dims: what has been our stance on something like this in the past?18:58
*** bobh has quit IRC18:58
dhellmannsmcginnis, lbragstad : we try to minimize risk. in this case, the change is only in the doc tool, and it would be easy enough to block the constraint update if it causes problems, so I think this risk is relatively low compared to the benefit we get from having those docs in place.19:01
dhellmannwe should coordinate with the team in #openstack-requirements, too, though19:01
smcginnisProbably still a little early for tonyb.19:02
smcginnisIt does seem very low risk.19:02
dhellmannI left a +2 on the release patch, but didn't approve it since we should have consensus first19:03
dimssmcginnis : let's talk to tonyb also, as this has to get into u-c. i like the fact that it's just 2 commits that matter and they are not changing any code that is likely to hit at runtime - http://logs.openstack.org/99/489599/3/check/gate-releases-tox-list-changes-ubuntu-xenial/5bc688d/console.html#_2017-08-01_17_58_59_87298719:04
dimslbragstad : better drop an FFE email as well to -dev mailing list19:04
lbragstaddims: sounds good - FFE tagged with [oslo] only?19:10
lbragstaddims: or should i include release in there, too?19:10
dims[release][requirements] too19:10
dhellmanndims,. smcginnis : maybe we want to document our ffe process this time around?19:16
smcginnisdhellmann: We really should have that somewhere. Thoughts on location for that?19:20
dhellmannsmcginnis : project team guide?19:20
dhellmannwe do have a release section there19:21
dhellmannit just doesn't have a ton of process info19:21
smcginnis+1 that makes sense.19:21
dhellmannI think we do have a section that talks about a typical release cycle? that might be a good place19:22
smcginnisdhellmann: Probably under the "Feature Freeze -1" section here? https://docs.openstack.org/project-team-guide/release-management.html#typical-development-cycle-schedule19:25
dhellmannyes, that would be a good spot19:26
smcginnisdhellmann: https://review.openstack.org/#/c/489723/19:41
*** rosmaita has joined #openstack-release19:43
dhellmannsmcginnis : I think I'm still not quite clear what you're trying to say in that second sentence19:47
dhellmannare you saying that raising the minimum version is another reason a release may be required?19:48
rosmaitadhellmann: smcginnis: are you talking about glance_store by any chance?19:48
smcginnisdhellmann: Yes, since that would not be allowed later if a stable release is done.19:48
dhellmannrosmaita : heh, no, we're trying to write down a policy :-)19:49
smcginnisrosmaita: No, actually just trying to better document how all that works when we need to bump a lib after the freeze.19:49
dhellmannsmcginnis : ok19:49
smcginnisdhellmann: Maybe I should just remove that sentence?19:49
rosmaitasorry i joined in media res ... i have a question when you're done, no hurry19:49
dhellmannthat situation doesn't necessarily require a new release, it may require a g-r update during the freeze period19:50
dhellmannso maybe those are separate concerns?19:50
smcginnisrosmaita: No problem, what's up?19:50
dhellmannseparate but related19:50
smcginnisdhellmann: Well, we had the issue with os-brick where we needed to raise the minimum.19:50
smcginnisAnd stable does not allow the mins to be raised after a stable release has gone out.19:50
rosmaitait's about this patch that just merged raising the minimum of os_brick: https://review.openstack.org/#/c/489603/19:50
rosmaitait merged in master19:50
smcginnisSpeak of the devil. :)19:51
rosmaitaafter stable/pike was cut19:51
rosmaitaso i guess i need to propose a backport to stable/pike ?19:51
dhellmannsmcginnis : yes, I guess the key thing there was that the feature release was deemed "critical" for the rest of the projects, so we had to approve the release and the g-r change together19:51
dhellmannrosmaita: we haven't branched requirements yet, but when we do the bot will propose the update19:51
rosmaitaoh, ok, so nothing for me to do yet19:52
smcginnisdhellmann: Yes, it was just extra ammo that if we did not do it before release, we would not be able to rely on consumers having the right version after the release as they could still grab the old (broken) version.19:52
* dhellmann verifies that we haven't branched requirements yet19:52
dhellmannrosmaita : yes, not yet19:52
smcginnisrosmaita: Good question! :)19:52
dhellmannsmcginnis : true. maybe that case needs to be explained in more detail to make that clear.19:53
dhellmanncase 1: there is a critical bug fix19:53
rosmaitaok, cool ... one last thing, is this the kind of thing we'd need to add a release note for, so people know why the new release?19:53
dhellmanncase 2: there is a feature deemed critical for a service, which means a feature release and a g-r min change to ensure it is present19:53
*** wolverineav has quit IRC19:53
smcginnisdhellmann: Or maybe I should just remove it. If it confused you, then I think my chances of confusing others reading it will be pretty high. :)19:53
dhellmannrosmaita : a release note in glance? or os-brick? or both?19:53
*** wolverineav has joined #openstack-release19:54
dhellmannsmcginnis : true, we could just be really general here19:54
dhellmann"impacting project releases" should cover us19:54
smcginnisdhellmann: Yeah, I think they'll figure it out based on their specific scenario.19:54
smcginnisUpdate coming..19:54
rosmaitawell, i was thinking glance_store, glance rc-1 hasn't been cut yet, so it should get the correct version of glance_store, so i didn't think it worth mentioning for glance19:54
smcginnisrosmaita: Yeah, I don't think a release note should be needed for that.19:55
rosmaitaeven better!  thanks19:55
smcginnisrosmaita: g-r will get updated to have the minimum version. Not sure if anything extra needs to be called out on that.19:56
rosmaitasmcginnis: works for me19:56
smcginnisdhellmann: When is requirements typically branched?19:56
dhellmannsmcginnis : "after all cycle-with-milestone projects have their branches created"19:59
*** bobh has joined #openstack-release20:00
dhellmannhmm, those instructions say to create the branch by hand20:01
dhellmannwe have openstack_requirements in the deliverables files though20:01
smcginnisThose artisinal branch instructions are everywhere. :)20:02
smcginnisThat's one concern I had changing those feature branch instructions - if it every changes again it will be a pain to track down all references.20:03
smcginnisBut I suppose at least now they point to the README, so even if the source page is wrong, there's a chance they will get to the correct current info.20:03
*** wolverineav has quit IRC20:17
*** wolverineav has joined #openstack-release20:17
*** wolverineav has quit IRC20:17
*** jtomasek has quit IRC20:20
openstackgerritDave McCowan proposed openstack/releases master: Release python-barbicanclient 4.5.2  https://review.openstack.org/48972920:20
dave-mccowandims fyi ^^20:21
dimsdave-mccowan : can you please throw a quick email to -dev for an FFE? "[release][requirements]" tags please20:25
smcginnisdave-mccowan: And if you have the time, provide feedback on here if the instructions make sense: https://review.openstack.org/#/c/489723/20:25
dave-mccowandims sure.  i'll need a patch to global requirements first, right? since that will be the exemption we need?20:26
openstackgerritDoug Hellmann proposed openstack/releases master: update directions for branching requirements repo  https://review.openstack.org/48973420:31
openstackgerritDoug Hellmann proposed openstack/releases master: make openstack_requirements cycle-with-intermediary  https://review.openstack.org/48973520:31
openstackgerritDoug Hellmann proposed openstack/releases master: teach edit-deliverable to add stable branch data  https://review.openstack.org/48973620:31
openstackgerritDoug Hellmann proposed openstack/releases master: add deliverable argument to discover_branch_points.py  https://review.openstack.org/48973720:31
openstackgerritDoug Hellmann proposed openstack/releases master: update import_branch_points.sh to use edit-deliverable  https://review.openstack.org/48973820:31
dhellmanndave-mccowan : you need the exception for the release and for the constraint update, so start with the email pointing to the release20:32
dhellmanndave-mccowan : do you need to raise the minimum version for barbicanclient in global requirements?20:33
dave-mccowandhellmann i think we should block 4.5.0 and 4.5.1 as bad20:34
dhellmanndave-mccowan : ok, include that info in the email20:34
lbragstaddhellmann: smcginnis dims done - http://lists.openstack.org/pipermail/openstack-dev/2017-August/120434.html20:36
smcginnislbragstad: Perfect. I'll respond on there with my opinion.20:39
openstackgerritMerged openstack/releases master: update directions for branching requirements repo  https://review.openstack.org/48973420:40
openstackgerritDoug Hellmann proposed openstack/releases master: fix typos in yamlutils  https://review.openstack.org/48974520:52
openstackgerritDoug Hellmann proposed openstack/releases master: do not let yamlutils emit alias references  https://review.openstack.org/48974620:52
openstackgerritDoug Hellmann proposed openstack/releases master: have propose-final-releases use yamlutils instead of appending to the file  https://review.openstack.org/48974720:52
openstackgerritDoug Hellmann proposed openstack/releases master: Release tooz 1.48.2 for Ocata  https://review.openstack.org/48610820:55
*** ekcs has quit IRC21:01
*** yamamoto has joined #openstack-release21:17
openstackgerritDoug Hellmann proposed openstack/releases master: remove unused data from new-release  https://review.openstack.org/48975221:18
openstackgerritDoug Hellmann proposed openstack/releases master: use yamlutils.loads() everywhere instead of yaml.safe_load()  https://review.openstack.org/48975321:18
*** yamamoto has quit IRC21:21
*** yamamoto has joined #openstack-release21:21
*** rosmaita has left #openstack-release21:22
*** yamamoto has quit IRC21:26
*** dave-mccowan has quit IRC21:27
jeblairheads up that the pypi mirrors haven't updated since 2:15 UTC due to a bug on pypi.python.org.  i reported it and they fixed the problem; mirror updates are currently in progress.21:27
dhellmannjeblair : thanks21:48
openstackgerritDoug Hellmann proposed openstack/releases master: use yamlutils.loads() everywhere instead of yaml.safe_load()  https://review.openstack.org/48975321:51
openstackgerritDoug Hellmann proposed openstack/releases master: remove unused data from new-release  https://review.openstack.org/48975221:51
*** ekcs has joined #openstack-release21:57
tonybwhich change are we talking about? oslo.policy 1.25.1 ?21:58
*** thorst_afk has quit IRC22:05
*** ekcs has quit IRC22:12
*** bobh has quit IRC22:16
jeblairthe pypi mirror is up to date now22:16
*** thorst_afk has joined #openstack-release22:19
*** yamamoto has joined #openstack-release22:23
*** thorst_afk has quit IRC22:24
*** yamamoto has quit IRC22:25
*** yamamoto has joined #openstack-release22:25
*** sdague has quit IRC22:35
*** dave-mccowan has joined #openstack-release22:44
dhellmanntonyb : both oslo.policy and python-barbicanclient have asked for FFE releases22:44
dhellmannjeblair : thanks22:44
clarkbhello release team. We are currently looking at a september 18 gerrit upgrade to get that done before everyone returns to work from the ptg. In the infra meeting we were wondering if that is something that the release team would want to advertise on the release schedule? its not a confirmed hard date but the one we are looking at so no rush. More something to think about22:58
*** https_GK1wmSU has joined #openstack-release23:02
*** https_GK1wmSU has left #openstack-release23:02
smcginnisclarkb: Not sure if we should publish that on the schedule. At a minimum though, I think several ML posts would be good leading up to it. ;)23:03
clarkbsmcginnis: yup definitely intend on giving people lots of warning on the mailing list23:04
clarkbonce we firm up the schedule the first notice will go out23:04
clarkb(hopefully tomorrow evening)23:04
smcginnisclarkb: Awesome. Is there a convenient list of differences somewhere with the new version? Like a release notes page or something?23:05
* smcginnis hasn't been keeping up with upstream gerrit23:05
clarkbsmcginnis: https://www.gerritcodereview.com/releases/2.12.md and https://www.gerritcodereview.com/releases/2.13.md for end users it should largely be the same. 2.14 will be a big change so we aren't jumpign to it just yet23:06
smcginnisclarkb: Cool, thanks for the links.23:06
clarkbmobile browsers work a little better under 2.13. You don't have to remove approvals and reapply them if a change already has a positive verified vote, you can just recheck and it will now do the right thing23:06
clarkbminor stuff like that23:07
clarkbsmcginnis: you can test your workflow at https://review-dev.openstack.org too23:07
smcginnisclarkb: Hmm, if mobile works better (actually works) that's more than minor to me. ;)23:07
clarkbno it doesn't actually work unfortunately23:08
clarkbit just works better :)23:08
smcginnisHaha, fair enough.23:08
clarkbyou still can't inline comment with it at least not on my phone but the rendering is much more readable for diffs on small screens23:08
smcginnisclarkb: Well, that is something at least.23:09
clarkbthe metrics stuff is potentially a useful new feature as well23:09
smcginnisThe most important question - can I press 'f' again to get a pop up of the file list?23:10
clarkbno23:10
clarkbnot that fortunate23:10
smcginnisThat's it, I quit.23:10
smcginnis:)23:11
clarkb2.14 adds proper support for the polygerrit interface which is yet another rewrite of the UI23:11
smcginnisI saw an earlier preview of that I think. Looked promising.23:11
clarkbI think it has gotten all of the UI attention for several releases so 2.13 doesn't really have much23:11
clarkbits a lot more like the old change screen23:11
clarkband written with proper javascript rather than gwt23:11
smcginnisI think that will make a lot of folks happy.23:11
clarkblet me find a link for you23:13
clarkbhttps://gerrit-review.googlesource.com/c/11253123:13
clarkbit has gone back to a change oriented change screen instead of patchset oriented23:13
clarkband has single page diff (hit the show diffs button)23:14
smcginnisA little different, but shouldn't take too long to get used to.23:14
clarkbwe decided not to go to that version right away because it introduces an entire new database system, requires java 8 (an os upgrade for us), polygerrit, etc. Went with easier upgrade to build momentum but hope to move on to 2.14 in the not too distant future23:15
smcginnisYeah, makes sense.23:16
clarkbalso it has built in CI comment hiding so we can drop our hacky javascript23:16
smcginnisOh nice!23:17
*** hongbin has quit IRC23:30
tonybdhellmann: okay.  I'm looking at both of them now.  I'll reply on list23:38
-openstackstatus- NOTICE: osic nodes have been removed from nodepool due to a problem with the mirror host beginning around 22:20 UTC. please recheck any jobs with failures installing packages.23:48
dimstonyb : when you wake up, please take a look at the oslo.policy and python-barbicanclient FFE/release request23:58
tonybdims: :) Sure23:59
dimsah there you are :)23:59
dimsgood morning23:59
* tonyb tries not to point out I just said that to dhellmann ;P23:59
tonybdims: morning23:59

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