Wednesday, 2016-03-02

*** sdake has joined #openstack-release01:03
*** sdake has quit IRC01:16
*** cody-somerville_ has joined #openstack-release01:23
*** cody-somerville has quit IRC01:24
*** sdake has joined #openstack-release01:31
*** sdake has quit IRC01:33
*** mriedem has quit IRC02:46
*** cody-somerville_ is now known as cody-somerville02:52
*** cody-somerville has joined #openstack-release02:52
*** dims has quit IRC03:15
*** sdake has joined #openstack-release03:15
*** david-lyle has joined #openstack-release03:24
*** sigmavirus24 is now known as sigmavirus24_awa03:34
*** sdake has quit IRC03:39
*** sdake has joined #openstack-release03:53
*** cody-somerville has quit IRC04:33
*** cody-somerville has joined #openstack-release04:35
*** sdake has quit IRC05:09
*** amotoki has joined #openstack-release05:16
*** pcaruana has joined #openstack-release05:36
*** pcaruana has quit IRC05:49
*** amotoki has quit IRC06:33
*** amotoki has joined #openstack-release06:34
*** amotoki has quit IRC06:36
openstackgerritSteve Martinelli proposed openstack/releases: release new liberty versions for keystone's projects  https://review.openstack.org/28701807:00
*** amotoki has joined #openstack-release07:14
*** amotoki has quit IRC07:35
openstackgerritSteve Martinelli proposed openstack/releases: release new liberty versions for keystone's projects  https://review.openstack.org/28701807:37
*** amotoki has joined #openstack-release07:43
*** amotoki has quit IRC07:48
*** pcaruana has joined #openstack-release08:02
*** onovy has quit IRC08:48
ttxdhellmann: when you have a minute, please review https://review.openstack.org/#/c/280356/ (project team guide) since it blocks a series of patches08:52
patchbotttx: patch 280356 - project-team-guide - Add 'Gate Status' section from stable branch wiki08:52
*** lane_kong is now known as lynn09:45
*** lynn is now known as Guest2997009:46
*** Guest29970 is now known as lynn_kong09:46
tonybttx: Can you have a quick look at: https://review.openstack.org/#/c/278180/ it's a pretty trivial change but I don't want to +W it becasue it's mine09:54
patchbottonyb: patch 278180 - openstack-infra/irc-meetings - Remove openstack-neutron-release from acceptable c...09:54
ttxsure, I'm on it09:54
ttxdone09:55
tonyb\o/09:57
*** cgalan has joined #openstack-release09:58
*** onovy has joined #openstack-release10:10
*** lynn_kong is now known as Larrie10:12
*** Larrie is now known as larrie10:12
*** amotoki has joined #openstack-release10:18
*** dtantsur|afk is now known as dtantsur10:25
*** larrie is now known as larrie_kong10:28
*** cgalan has quit IRC10:48
*** costingalan has joined #openstack-release10:48
*** dims_ has joined #openstack-release10:51
*** sdague has joined #openstack-release11:02
*** costingalan has quit IRC11:48
openstackgerritSergey Kraynev proposed openstack/releases: Release python-heatclient-1.0.0  https://review.openstack.org/28385211:55
*** doug-fish has joined #openstack-release11:56
*** sdake has joined #openstack-release12:03
*** sdake has quit IRC12:13
dhellmannttx: on my list for after this call12:56
openstackgerritFlavio Percoco proposed openstack/releases: Glance Mitaka-3 deliverables  https://review.openstack.org/28717513:08
*** pleia2 has quit IRC13:33
openstackgerritJohn Garbutt proposed openstack/releases: Release python-novaclient 3.3.0  https://review.openstack.org/28719113:34
ttxsmcginnis: hi! python-brick-cinderclient-ext is supposed to be released with intermediary releases during the cycle but there wasn't any release yet... What are your plans for that one ?13:51
smcginnisttx: I'm hoping we can do a release shortly after M-3 calms down.13:52
smcginnisttx: A couple patches outstanding that I want to get to but haven't been able to yet.13:53
ttxsmcginnis: so the issue is that we'll be under Requirements Freeze and that would be introducing a new thing13:54
ttxbasically forcing packagers to do some extra work13:54
*** doug-fish has quit IRC13:55
smcginnisttx: It's not a requirement for any existing cinder functionality.13:55
smcginnisttx: It's really just an extension for being able to do some non-Nova storage management.13:55
ttxoh, so nothing would depend on it ?13:55
smcginnisttx: Right, it's kind of something off to the side at the moment.13:55
ttxfinal release for non-client libs was still last week, but I guess an exception here would not cause too many issues13:56
ttxdue to the lib not actually being used anywhere13:56
smcginnisttx: Well, it is a client lib, but it's not _the_ client lib. If that makes any sense.13:57
smcginnisttx: It's just something someone could choose to add as a sort of plugin extension to python-cinderclient13:57
smcginnisttx: If they want to manage storage on say a bare metal server.13:57
ttxI see what you mean13:57
ttxthx for the precisions13:58
smcginnisttx: Good. Wasn't sure if I was explaining it well. ;)13:58
*** doug-fish has joined #openstack-release14:13
dims_ttx : dhellmann : would it be easy to add dates to the version/repo/commit tables? say http://releases.openstack.org/liberty/index.html#neutron14:17
ttxdims_: would be useful to see how old the last intermediary (or point release) is14:22
ttxwe don't have that info in the yaml, so we'd have to get it from the git repos.14:22
openstackgerritSean McGinnis proposed openstack/releases: Release python-cinderclient 1.6.0  https://review.openstack.org/28722214:23
ttxwe may clone them already anyway14:23
ttxdhellmann must know14:23
dims_ttx : yes14:25
ttxthe answer seems to be no, adding cloning to the docs generation would make it a lot heavier14:29
*** mriedem has joined #openstack-release14:31
dhellmannyeah, that's why I didn't include it14:31
ttxso... non-trivial14:31
ttxand adding it the the YAML grammar sounds a bit repetitive14:31
dhellmannwe have the local git commit date for the deliverable file, but that's not always associated with the version number (certainly not all of them)14:31
dhellmannI haven't explored using git blame to figure it out, that seemed like overkill14:32
dims_dhellmann : ack thanks14:32
ttxand error-prone14:32
dhellmannwe could add dates as an optional field, and write something to generate an update to the yaml14:32
dhellmannI agree that dates would be useful, it's just not clear how to get them easily14:32
ttxwe could fetch the tag date using curl to cgit as a shortcut too14:33
dhellmannoh, interesting14:33
dhellmannyeah, that might work14:33
ttxthat is how I manually do it when I want to check a date without cloning, after all14:33
dhellmannwould still be pretty slow, though. I wonder if we can get all of the tags for a repo at once somehow?14:33
dhellmannwhat does the url for that look like? I keep a copy of everything checked out locally...14:34
ttxhttp://git.openstack.org/cgit/openstack/nova/refs/14:34
ttxthough that doesn't really give you dates in one go14:35
dhellmannhmm, it's showing relative dates there14:35
dhellmannah, there's a proper date if you access one tag14:35
ttxat that point it's probably simpler to query git remotely14:35
dhellmannI think that's how I'm already checking in the validate code to see if the tag exists14:35
dhellmanncurl -s http://git.openstack.org/cgit/openstack/nova/tag/?h=2015.1.3 | grep 'tag date' | cut -f5 -d'>' | cut -f1 -d'<'14:44
dhellmanncurl -s http://git.openstack.org/cgit/openstack/nova/tag/?h=2015.1.3 | grep 'tag date' | cut -f5 -d'>' | cut -f1 -d' '14:44
ttxwould still generate a gazillion calls each time we refresh doc, but that may be a good tradeof14:46
ttxf14:46
dhellmannyeah, we could keep a little cache database locally. it would be interesting to see how big of a time hit that would add to ci though14:48
ttxdavid-lyle: django-openstack-auth-kerberos hasn't done a mitaka release yet. it's marked as following the cycle (although it never cut release or stable branches) -- what are the plans there ?14:48
dhellmannbbiab14:48
ttxjroll: coreos-image-builder and ironic-ui are supposed to make intermediary releases too, but haven't done a mitaka one yet. What are your plans there ?14:49
* ttx goes on a short break to chop wood (literally)14:50
*** sdake has joined #openstack-release14:51
*** doug-fish has quit IRC14:52
dims_ttx : whoa!14:52
*** doug-fish has joined #openstack-release14:54
*** doug-fish has quit IRC14:56
*** doug-fish has joined #openstack-release14:57
*** sigmavirus24_awa is now known as sigmavirus2415:08
jrollttx: let me chat with ironic-ui folks, coreos-image-builder I think is pretty dead15:09
jrollttx: what's the deadline look like for not-really-a-service-not-really-a-library things like this? e.g. ironic-ui is a horizon plugin?15:11
ttxjroll: same as ironic proper15:15
ttxjroll: ideally you would make one release asap and then maybe another closer to end date15:15
ttxso that we have something to fall back to just in case15:16
ttxmy back hurts15:16
jrollttx: yeah, just checked with ironic-ui folks, they should be landing code this week to make it actually functional15:16
jrollttx: so maybe next week if that's okay?15:17
ttxsounds good. I just get nervous when there is no previous intermediary release we can fall back to15:17
ttxand we approach the end15:18
jrollyeah, I hear you15:18
ttxbut if you have a plan we are good15:18
jrollcool, thanks :)15:18
jrollcoreos-image-builder, I'd like to figure out how to kill that off15:18
ttxwe can just remove it from the deliverables in project.yaml. Then it's non-official and not part of mitaka15:19
jrollttx: okay, checking with people who started that project first15:20
*** gordc has joined #openstack-release15:31
*** sdake_ has joined #openstack-release15:51
*** sdake has quit IRC15:52
*** sdake has joined #openstack-release15:55
*** sdake_ has quit IRC15:58
*** pcaruana has quit IRC16:05
*** sdake_ has joined #openstack-release16:12
*** bauzas_ has joined #openstack-release16:14
*** odyssey4me_ has joined #openstack-release16:15
*** larrie_kong has quit IRC16:15
*** bauzas has quit IRC16:15
*** larrie_kong has joined #openstack-release16:15
*** odyssey4me has quit IRC16:15
*** johnthetubaguy has quit IRC16:15
*** sdake has quit IRC16:15
*** bauzas_ is now known as bauzas16:15
*** johnthetubaguy has joined #openstack-release16:15
*** larrie_kong has quit IRC16:15
*** larrie_kong has joined #openstack-release16:15
*** sdake_ is now known as sdake16:21
openstackgerritdevdatta-kulkarni proposed openstack/releases: Solum mitaka releases  https://review.openstack.org/28420016:31
*** odyssey4me_ is now known as odyssey4me16:33
*** sdake has quit IRC16:35
*** david-lyle has quit IRC16:36
*** david-lyle has joined #openstack-release16:38
*** sdake has joined #openstack-release16:40
ttxgordc: o/16:40
gordcttx: hi16:41
ttxgordc: ceilometermiddleware is supposedly released with intermediary versions16:41
ttxgordc: but hasn't had one so far16:41
ttxany plan there ?16:41
gordcttx: no. we haven't modified it this cycle (if i recall)16:42
gordcit's in maintenance for now unless we get feature requests (and resources)16:42
ttxdhellmann: any idea how to handle that case ? ^16:43
ttxdhellmann: our process operates on the premise that there is at least one release per cycle. I guess we could retag it. Or even mention the same tag in multiple releases16:44
gordcttx: i could release one. but it's just requirement changes and a conf option default change.16:46
ttxgordc: that would be fine16:47
ttxgordc: let's wait for dhellmann thoughts on the matter though16:47
gordcttx: ack16:49
*** ttx has quit IRC16:54
david-lylettx: I don't believe it has had any changes, we could move it to independent I suppose. It shouldn't change much with time16:55
*** ttx has joined #openstack-release16:56
david-lylettx: I don't believe it has had any changes, we could move it to independent I suppose. It shouldn't change much with time re: django-openstack-auth-kerberos16:56
ttxdavid-lyle: ok, let me see with dhellmann what the best solution would be (same as ceilometerclient)16:57
openstackgerritDavid Lyle proposed openstack/releases: Releasing django_openstack_auth 2.2.0  https://review.openstack.org/28731916:58
david-lyleon a semi-related note16:59
ttxdhellmann: I've been nagging everyone on the cycle-with-intermediary not-reelased-yet list, except angdraug(fuel) who was not on IRC until now. Supposedly on US hours according to #fuel17:08
ttxso maybe you can try to ping him later in your day17:08
ttxask him about his python-fuelclient plans17:08
ttxdhellmann: we have an open question on what to do with things that don't really needed a release. Empty release, re-tag of the last tag, or have the releases yaml point to another release yaml sha17:09
*** pleia2 has joined #openstack-release17:12
*** sdake has quit IRC17:13
ttxdhellmann: Tomorrow I'll check who hasn't done b3 yet (in managed projects) and do some nagging too17:16
dhellmanngordc, ttx: if there are only requirements updates I don't think we need to do a release17:16
dhellmanngordc, ttx: changing the model to independent might make sense, if you're not actively developing it17:16
ttxdhellmann: we still kind need to reference a mitaka thing for ir17:16
ttxt17:16
ttxor change the model yes17:17
*** dtantsur is now known as dtantsur|afk17:17
skraynevhi all. I have a question: we have one BP, which is mostly finished except two patches: Release notes and Functional test. Do we need announce FFE for it or can just close BP and lan both patches after m3 ?17:17
*** sdake has joined #openstack-release17:17
dhellmannttx: yeah, a model change would address that, or refer to the existing release. I'm not sure it makes sense to create a release just for the sake of having one.17:17
skraynevttx: dhellmann ^17:17
dhellmannttx: I'll ask angdraug about fuel client17:17
gordcdhellmann: i'm ok with independent... just for reference what's the diff between intermediary and independent? one guarantees release(s) per cycle?17:18
dhellmanngordc : intermediary implies series-specific stable branches based on having a release each cycle17:18
ttxindependent things don't have stable branches17:18
dhellmannright17:18
ttxthey are not linked to the cycle at all17:18
gordcttx: dhellmann. ah ok17:18
ttxthey follow their own cycle17:18
gordcyeah, i'm ok with that.17:19
dhellmannskraynev: it sounds like the work isn't done if there aren't tests, so I would list it as a FFE to be clear17:19
skraynevdhellmann: ok. thank you17:21
ttxskraynev: yes, although "adding tests" is not technically a FF break, not having tests at all is pretty problematic17:21
skraynevttx: it has unittests, but has not functional17:22
ttxalso known as "broken"17:22
ttxskraynev: yeah, it's borderline then17:22
ttxIt's good to list as an FFE so that you're sure it's prioritized up17:22
skraynevttx: got it. We will process it in this way, then ;) thank you17:23
ttxdhellmann: I think the strategy boils down to stable branches. If you still do one you should stay in -intermediary, cut stable/mitaka from the last tag and reference that last tag in the release yaml17:24
*** mriedem has left #openstack-release17:24
ttxdhellmann: and if you don't want to do them anymore, switch to independent.17:24
*** mriedem has joined #openstack-release17:24
ttxIn the former case, basically both series use the same tag17:24
ttxwhich... shouldn't... break anything.17:25
dhellmannttx: that makes sense. we could even do the release with the requirements updates, I guess. seems a bit pointless to force that, though.17:25
dhellmannI would rather list the same release in 2 series, I think.17:25
ttxdhellmann: oh, it probably breaks one thing. The ability to do a point release on stable/liberty17:25
dhellmannah, yeah17:26
dhellmannsigh17:26
dhellmannso we need to go ahead and do a release to give us room for stable branch releases17:26
ttxalthough I guess it's not really broken until you do another release17:26
ttxyes, not only do a fake release but bump .y on it17:27
ttxalthough realigning requirements is probably a good reason to do that17:28
ttx(for ceilometermiddleware)17:28
ttxso yeah, options are probably, switch to -independent, or release at lest once per cycle even if taht makes a pretty empty release17:29
ttxgordc: for ceilometermiddleware I suspect you would pick the latter option17:29
dhellmanngordc, ttx: I agree17:29
ttxdavid-lyle: for django-openstack-auth-kerberos I suspect you would pick the former17:30
dhellmannyep, ++17:30
david-lylesounds good to me17:30
ttxok, dinner prep time17:32
ttxdhellmann: I can process some b3 releases requests tomorrow morning -- any warnings ?17:32
gordcttx: dhellmann: k, i'll make a release for mitaka based on HEAD.17:33
ttxdhellmann: just let me know here if there is anything special I should watch out for (before processing b3 requests backlog tomorrow morning)17:34
ttxand have a great evening :)17:34
* ttx disappears17:34
skraynevttx: do we note about FFE in release repo for m3 tag? or will be enough mail to openstack-dev with this information ?17:35
dhellmannttx: I'm just looking through the release requests right now. I'll leave comments on any that look troublesome, and we can discuss tomorrow before processing any for b3 (I'm doing client releases)17:36
dhellmannttx: the tools have been working pretty reliably, so other than watching to make sure the pypi upload works right processing the requests is fairly hands-off now17:37
dhellmannredrobot : your release request for barbican client needs attention: https://review.openstack.org/#/c/281573/17:38
patchbotdhellmann: patch 281573 - releases - Release python-barbicanclient 3.4.017:38
redrobotdhellmann ack17:39
dhellmannnotmyname : do you have the details you need for the swiftclient release request?17:39
dhellmannstevebaker: https://review.openstack.org/#/c/283852/ looks ready, except for the requirements update17:43
patchbotdhellmann: patch 283852 - releases - Release python-heatclient-1.0.017:43
*** sdake has quit IRC17:43
dhellmannjohnthetubaguy : the novaclient release looks fine, but we need the global-requirements patch too17:46
johnthetubaguydhellmann: ah, dam, good catch17:47
johnthetubaguydhellmann: found it: https://review.openstack.org/#/c/277050/117:48
patchbotjohnthetubaguy: patch 277050 - python-novaclient (stable/kilo) - Updated from global requirements17:48
dhellmannjohnthetubaguy : that's for kilo?17:49
johnthetubaguyoops17:49
dhellmannjohnthetubaguy : not for the new 3.3.0 release17:49
dhellmannI assumed you'd have to file a new one. I would do it, but if you do it then I can just approve it so that's why I ask everyone to do their own.17:49
johnthetubaguydhellmann: oh, sorry, I see what you mean now, my bad, I was thinking the requirments sync17:50
dhellmannjohnthetubaguy : ah, no, sorry I wasn't clear17:50
dhellmannsmcginnis : I left a question about compatibility on the cinderclient release request, when you have a minute17:50
*** robcresswell has joined #openstack-release17:55
skraynevdhellmann: patch for constraint was uploaded. Please re-review https://review.openstack.org/#/c/283852/417:57
patchbotskraynev: patch 283852 - releases - Release python-heatclient-1.0.017:57
dhellmannskraynev : looking now17:58
dhellmannskraynev : ok, I'll work on the release now17:59
skraynevdhellmann: ok. thank you17:59
openstackgerritSergey Kraynev proposed openstack/releases: Release M3 for Heat Mitaka  https://review.openstack.org/28419818:00
openstackgerritMerged openstack/releases: Release python-heatclient-1.0.0  https://review.openstack.org/28385218:01
johnthetubaguydhellmann: thats for the heads up, added a link to bump the upper-constraints file, and commented on https://review.openstack.org/#/c/287191. I don't think any project requires the newer version yet, so I left the global requirements unchanged, let me know if thats not correct.18:04
dhellmannjohnthetubaguy : sounds exactly right, thanks18:04
johnthetubaguydhellmann: cool, thanks18:04
dhellmannjohnthetubaguy : I'm processing the release right now, so keep an eye out for the new version to start showing up in tests later today18:07
openstackgerritMerged openstack/releases: Release python-novaclient 3.3.0  https://review.openstack.org/28719118:08
dhellmannjohnthetubaguy : there were quite a few changes in that release, maybe next cycle we can cut them more often?18:08
*** david-lyle has quit IRC18:12
*** sigmavirus24 is now known as sigmavirus24_awa18:12
*** david-lyle has joined #openstack-release18:13
johnthetubaguydhellmann: agreed, last release was jan 7th, we had planned way more often release, but sadly that slowed down again recently, mostly waiting for "one last thing"18:13
johnthetubaguywe should schedule those18:13
dhellmannjohnthetubaguy : yeah, I know the feeling. with the automation we have now, it's quite practical for us to release as often as weekly.18:14
dhellmannjust food for thought, you don't *have* to follow dims' lead :-)18:14
openstackgerritSteve Martinelli proposed openstack/releases: release keystone mitaka-3  https://review.openstack.org/28686618:15
johnthetubaguyyeah, we were thinking bi-weekly, but yeah, didn't happen18:15
dhellmannthat's a good goal18:15
*** mriedem has quit IRC18:18
stevemardhellmann: hey, just checking in for mitaka-3 release. keystone is ready to go, just wondering why it wasn't approved, is the release team doing all the server parts it in a fell swoop?18:18
dhellmannstevemar : yeah, I'm looking them over and then ttx and I are going to process them tomorrow18:19
stevemardhellmann: rgr that, i figured that was it18:20
smcginnisdhellmann: Good question. I responded on the patch.18:26
smcginnisdhellmann: Let me know if what I wrote doesn't make sense.18:26
dhellmannsmcginnis : ok, I'll check it after lunch, bbiab18:26
smcginnisdhellmann: Thanks!18:26
*** mriedem has joined #openstack-release18:29
*** doug-fish has quit IRC18:30
*** doug-fish has joined #openstack-release18:31
*** doug-fis_ has joined #openstack-release18:34
jrollttx: dropping coreos-image-builder here https://review.openstack.org/28737218:35
*** doug-fish has quit IRC18:35
*** doug-fis_ has quit IRC18:39
*** sdake has joined #openstack-release18:41
*** doug-fish has joined #openstack-release19:12
*** sigmavirus24_awa is now known as sigmavirus2419:22
openstackgerritgordon chung proposed openstack/releases: ceilometermiddleware 0.4.0 - mitaka  https://review.openstack.org/28740019:23
*** doug-fis_ has joined #openstack-release19:35
*** doug-fish has quit IRC19:36
*** doug-fish has joined #openstack-release19:46
*** doug-fis_ has quit IRC19:47
dhellmannstevemar : for your liberty releases, did you check the constraints file to see if it needs to be updated?19:52
*** sdake_ has joined #openstack-release19:59
openstackgerritDoug Hellmann proposed openstack/releases: run yamllint on deliverable files during validation  https://review.openstack.org/28412020:00
*** sdake has quit IRC20:00
jrolldhellmann: is there a non-client library release freeze exception process thing?20:00
jrollI have a contributor asking about it for a small ironic-lib patch20:00
dhellmannjroll : the issue is with freezing requirements as much as the libs themselves20:01
dhellmanndo you think you can get the patch in this week? is it a feature or a fix?20:01
jrolldhellmann: feature, and maybe20:01
dhellmannhow many projects depend on ironic-lib?20:02
jrollbut if the answer is "heck no", I can understand that and it's fine :)20:02
jrollironic and ironic-python-agent20:02
jrolland no projects depend on those20:02
dhellmannwould adding the feature require raising the minimum dependency on ironic-lib?20:02
*** sdake has joined #openstack-release20:03
jrolldhellmann: AIUI, yes20:04
dhellmannjroll : I don't actually see it listed in ironic-lib20:04
dhellmannI mean ironic-python-agent20:04
jrolldhellmann: that's in the works20:04
dhellmannok, so what you'd need to do is land the patch, release the lib, and update the minimum version of the dependency before we freeze requirements20:04
jrollright20:05
dhellmannor, we could figure out a ffe process for that dependency, if you consider it release critical20:05
jrollit isn't a blocker, no, but a very-nice-to-have20:05
dhellmannsince only ironic projects depend on ironic-lib, it's sort of an implementation detail that it's in a lib20:05
*** sdake_ has quit IRC20:06
dhellmannso I think it would be safe to tweak that minimum, but whether we do it depends on how important it is20:06
dhellmannis the feature ready to land?20:06
jrollit fixes a large gap in our driver feature matrix20:06
jrolllooks like it has a -1 for commit message, can probably land tomorrow20:06
jrollpatch is https://review.openstack.org/#/c/281045 btw20:06
dhellmannok, see how far you can get with it and I think I'd be comfortable with a requirements update very early next week if we have to do it20:07
jrollokay, sounds good. thank you :)20:07
dhellmannjroll : will ironic itself work with an older version of the lib without this patch?20:08
dhellmannor is there another patch in ironic to take advantage of it?20:08
jrolldhellmann: yeah, so there is an IPA patch out there somewhere20:09
jrollironic won't need the newer version, IPA will20:09
dhellmannok20:09
openstackgerritDouglas Mendizábal proposed openstack/releases: Release python-barbicanclient 3.4.0  https://review.openstack.org/28157320:12
*** doug-fis_ has joined #openstack-release20:17
*** doug-fish has quit IRC20:18
stevemardhellmann: nope! i didn't check the constraints file, let me take a second look, i think they capped properly20:25
stevemardhellmann: yeah, the constraints are way higher than what i'm proposing20:27
dhellmannstevemar : ok, cool20:28
stevemardhellmann: commented and added mriedem20:28
dhellmannstevemar : we'll just wait for mriedem to have a look, then20:28
stevemarwhen all else fails, there's always mriedem to save ours butts20:28
mriedemlink?20:28
dhellmannhttps://review.openstack.org/28701820:29
*** doug-fish has joined #openstack-release20:31
*** doug-fis_ has quit IRC20:33
*** TravT has joined #openstack-release20:33
mriedemok20:34
mriedemwould be nicer if these weren't all lumped in together, like the weekly oslo release dump which is a beast to review20:35
openstackgerritDoug Hellmann proposed openstack/releases: reno 1.5.1  https://review.openstack.org/28742220:39
dims_"when all else fails, there's always mriedem to save ours butts" << hear hear! +120:40
*** david-lyle has quit IRC20:45
*** david-lyle has joined #openstack-release20:47
mriedemstevemar: bknudson: this seems fishy for stable https://review.openstack.org/#/c/266022/20:48
patchbotmriedem: patch 266022 - keystone (stable/liberty) - Add audit IDs to revocation events (MERGED)20:48
bknudsonmriedem: it's a fix for a security bug20:48
mriedemthere is no api change here?20:48
bknudsonmriedem: sure there is.20:48
mriedemheh20:49
SergeyLukjanovdims, are you ok with tab in https://review.openstack.org/#/c/284120/5/tox.ini ?20:50
patchbotSergeyLukjanov: patch 284120 - releases - run yamllint on deliverable files during validation20:50
mriedembknudson: stevemar: so if the api is changing, shouldn't we bump the keystone version in liberty to 8.1.0?20:50
mriedemdhellmann: ^20:50
bknudsonmriedem: fine by me.20:51
mriedemi know i talked about that with ttx once on versions and now i can't remember what we decided20:51
stevemarmriedem: i just assumed we would always be doing minor releases, but yeah, there's no reason we can't do 8.1.020:53
stevemars/minor/point/20:53
mriedembknudson: stevemar: and this ksm change is related to the keystone one right? https://review.openstack.org/#/c/265988/20:54
patchbotmriedem: patch 265988 - keystonemiddleware (stable/liberty) - auth_token verify revocation by audit_id (MERGED)20:54
bknudsonmriedem: yes, they're all part of the same bug20:54
mriedemso does the keystone change break if you don't have a version of ksm with https://review.openstack.org/#/c/265988/ ?20:55
patchbotmriedem: patch 265988 - keystonemiddleware (stable/liberty) - auth_token verify revocation by audit_id (MERGED)20:55
mriedemor you just don't have the fix?20:55
bknudsonmriedem: auth_token and keystone work either way. You just don't have the fix20:55
dhellmannmriedem, stevemar, bknudson : it seems a bit odd to release 8.0.0.0b2 and then 8.1.0.0b320:56
TravTdhellmann: i followed an old set of instructions an tagged the searchlight client directly20:56
TravThttp://docs.openstack.org/infra/manual/drivers.html#tagging-a-release20:56
dhellmannmriedem, stevemar, bknudson : what was the version last cycle?20:56
TravTshould i put up a new review on a new version?20:57
dhellmannTravT : thanks for the reference, I'll update those20:57
stevemardhellmann: hmm? why are there b2 or b3 for liberty?20:57
dhellmannTravT : you can file a patch to releases with the existing tag info20:57
dhellmannstevemar : oh, sorry, liberty20:57
TravTok.20:57
dhellmannstevemar, bknudson, mriedem : how is the API change in a stable branch, then?20:58
stevemardhellmann: yeah for liberty we're going from 8.0.1 to 8.1.0; for mitaka we're going from 9.0.0.0b2 to 9.0.0.0b3 :)20:58
mriedemdhellmann: i guess it's a security fix...20:58
mriedemi don't know the details20:58
stevemardhellmann: it fixed a major security bug with pki tokens20:58
dhellmannis it a backwards-compatible API change?20:58
mriedemas far as i can tell it adds a thing to the response20:58
mriedemwhich is not the end of the world20:59
dhellmannyeah, that seems ok20:59
dhellmannstevemar : ^^?20:59
stevemardhellmann: https://bugs.launchpad.net/keystone/+bug/1490804, yep mriedem has the details20:59
openstackLaunchpad bug 1490804 in OpenStack Identity (keystone) kilo "[OSSA 2016-005] PKI Token Revocation Bypass (CVE-2015-7546)" [High,Fix committed]20:59
stevemarit adds to the response20:59
mriedemwell, i don't really have the details20:59
mriedembut that's what it looks like20:59
dhellmannstevemar : ok,  I have to try to not dig into every patch in order to answer questions myself, so I'm going to ask you the question :-)20:59
stevemarmriedem: i meant you ahve the right idea :)20:59
dhellmannok, if it's adding data then it's compatible I guess so 8.1.0 seems ok21:00
stevemardhellmann: yeah, on the server side we add bits to the response, and in middleware (the other half of the fix) checks if those bits exist21:01
stevemarso if someone upgrades and doesn't have the complete fix, they aren't toast (cc bknudson)21:01
bknudsonyep21:02
mriedemupper-constraints in liberty will work for the versions of keystoneclient, ksm and keystoneauth proposed,21:03
mriedemadmittedly those versions should probably not be in stable/liberty u-c21:03
mriedemand will at some point bite us in the arse21:03
mriedemstevemar: so -1 for the version change on keystone, should be 8.1.021:04
mriedemotherwise i think i could live with this21:04
stevemarmriedem: cool, i'll fix the version number21:05
stevemarmriedem: i'll remove the bits about bad oslo.messaging versions21:06
mriedemk21:06
openstackgerritSteve Martinelli proposed openstack/releases: release new liberty versions for keystone's projects  https://review.openstack.org/28701821:06
stevemarmriedem: dhellmann i'm also OK with postponing this til next week if there is too much going on right now?21:06
mriedemumm21:07
mriedemdoesn't matter to me21:07
dhellmannstevemar : I'm not sure it matters to me21:07
mriedemthe sooner the better on this kind of thing imo21:07
dhellmannwe might as well go ahead and do it, if it's ready21:07
stevemardhellmann: mriedem alrighty21:07
stevemarjust wanted to give you all the option21:07
mriedemif these client/lib releases break liberty,21:08
mriedemwell, you'll see the torch and pitchforks soon enough21:09
stevemar:|21:09
*** doug-fish has quit IRC21:09
stevemarmriedem: excellent motivation for releasing often!21:09
stevemar:)21:09
openstackgerritTravis Tripp proposed openstack/releases: Release python-searchlightclient 0.2.0  https://review.openstack.org/28743921:14
*** doug-fish has joined #openstack-release21:15
*** doug-fis_ has joined #openstack-release21:16
*** doug-fish has quit IRC21:20
openstackgerritMerged openstack/releases: run yamllint on deliverable files during validation  https://review.openstack.org/28412021:20
*** doug-fish has joined #openstack-release21:23
*** doug-fis_ has quit IRC21:25
*** doug-fis_ has joined #openstack-release21:35
*** doug-fish has quit IRC21:38
*** doug-fish has joined #openstack-release21:43
*** doug-fis_ has quit IRC21:46
smcginnisdhellmann: That explanation in the python-cinderclient release patch make sense?21:47
*** _joes_ has quit IRC22:09
openstackgerritSean McGinnis proposed openstack/releases: Release Cinder Mitaka-3  https://review.openstack.org/28747522:09
*** doug-fis_ has joined #openstack-release22:10
*** doug-fish has quit IRC22:11
*** sdake_ has joined #openstack-release22:15
*** rockyg has joined #openstack-release22:17
*** sdake has quit IRC22:18
dims_dhellmann : so no more updates to global-requirements.txt after friday? we would still be ok with bot proposed upper-constraints.txt?22:22
dims_dhellmann : trying to see which oslo libs would need updates (bug fixes, finalize requirements.txt)22:23
*** doug-fis_ has quit IRC22:39
*** doug-fish has joined #openstack-release22:42
*** doug-fis_ has joined #openstack-release22:44
*** doug-fish has quit IRC22:47
*** mriedem has quit IRC22:48
*** doug-fis_ has quit IRC22:48
*** yarkot_ has joined #openstack-release22:53
*** dims_ has quit IRC22:56
*** yarkot_ has quit IRC22:57
*** yarkot_ has joined #openstack-release22:57
*** yarkot_ has quit IRC22:59
openstackgerritErno Kuvaja proposed openstack/releases: Release glance-store 0.13.0  https://review.openstack.org/28749523:05
*** gordc has quit IRC23:09
*** sigmavirus24 is now known as sigmavirus24_awa23:15
*** rockyg has quit IRC23:22

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