Tuesday, 2016-04-05

*** bdemers has quit IRC00:02
*** bdemers has joined #openstack-release00:03
*** thinrichs has joined #openstack-release00:25
*** sdake has joined #openstack-release00:59
*** kzaitsev_mb has quit IRC01:03
*** thinrichs has quit IRC01:05
*** Qiming has joined #openstack-release01:07
*** ekcs has quit IRC01:17
*** sridhar_ram has quit IRC01:47
*** cody-somerville has quit IRC01:55
*** cody-somerville has joined #openstack-release01:55
*** kzaitsev_mb has joined #openstack-release02:28
*** kzaitsev_mb has quit IRC02:34
*** amrith is now known as _amrith_02:58
*** sdake has quit IRC03:02
*** sekrit has joined #openstack-release03:17
*** ekcs has joined #openstack-release03:22
*** kzaitsev_mb has joined #openstack-release03:30
*** ekcs has quit IRC03:49
nikhilnotmyname: ah cool, thanks!03:51
notmynamenikhil: it's all about timburke ;-)03:52
nikhilhahah03:52
*** kzaitsev_mb has quit IRC04:18
*** kzaitsev_mb has joined #openstack-release05:14
*** kzaitsev_mb has quit IRC05:19
*** cody-somerville has quit IRC05:31
*** armax has quit IRC05:35
*** cody-somerville has joined #openstack-release05:44
*** vgridnev has joined #openstack-release06:08
*** kzaitsev_mb has joined #openstack-release06:15
*** kzaitsev_mb has quit IRC06:20
*** sheeprine has quit IRC06:22
*** sheeprine has joined #openstack-release06:25
*** vgridnev has quit IRC06:47
*** vgridnev has joined #openstack-release06:47
ttxflwang1: that would be the Foundation staff working on the website. There is a feedback button at the bottom of that page07:01
ttxor I can pass a message if you prefer07:01
ttxflwang1: the 1/8 score is calculated from the "meets maturity requirements" column07:02
ttxso I guess 1% of deployment is not enough to meet deployment requirements07:03
ttxsame for 3 SDKs07:03
ttxand yes, this is derived from the ops-tags work07:04
ttxflwang1: about https://review.openstack.org/#/c/301380/ I think that can wait post-release (and land as one of the first stable/mitaka patches)07:06
patchbotttx: patch 301380 - zaqar (stable/mitaka) - Fix tempest tests list07:06
*** kzaitsev_mb has joined #openstack-release07:16
AJaegerttx, thanks for your nice wording in the Install Guide thread. I stole a few lines in the updated spec from it: https://review.openstack.org/#/c/30128407:19
ttxAJaeger: you're welcome :)07:20
*** kzaitsev_mb has quit IRC07:21
openstackgerritMerged openstack/releases: Add release RC3 to Congress  https://review.openstack.org/30120107:28
*** pcaruana has joined #openstack-release07:37
*** cody-somerville has quit IRC07:38
*** dtantsur|afk is now known as dtantsur07:49
*** ihrachys has joined #openstack-release07:54
openstackgerritMerged openstack/releases: Astara 8.0.0.0rc3 mitaka release candidate  https://review.openstack.org/30129207:57
Qimingttx, around?08:03
ttxQiming: yes08:07
openstackgerritThierry Carrez proposed openstack/releases: Re-add tarball links for Congress and Astara  https://review.openstack.org/30150508:07
Qimingttx, a beginner's question08:07
Qimingwe want to bump python-senlinclient version to 0.4.208:08
Qimingwhat is the procedure?08:08
ttxQiming: why do you need to bump it ?08:09
Qimingjust propose a patch openstack/releases?08:09
ttx(currently we freeze all releases since this is mitaka release week)08:09
ttx(you can issue point release starting next week)08:09
ttx(unless the issue is somehow release-critical)08:09
Qimingokay, that is a timing issue I understand08:09
ttx(hence me asking why)08:10
openstackgerritSergey Lukjanov proposed openstack/releases: Sahara Mitaka release is ready  https://review.openstack.org/30150608:10
ttxdepending on what issue leads you to bump to 0.4.2 it should be done pre or post-release08:10
Qimingwe are introducing some exception wrappers to the interface funtions08:10
SergeyLukjanovttx Sahara Mitaka release - https://review.openstack.org/30150608:10
ttxSergeyLukjanov: we don't need to request those, we'll handle that on Thursday08:10
Qimingso we believe it's better we do that in a separate version08:10
SergeyLukjanovttx ooops, sorry, automatically createda CR :)08:11
ttxQiming: sounds like something that can wait post-release08:11
Qimingokay, ttx, we can wait, it is not that urgent08:11
ttxQiming: so you can submit the tag request, but we'll likely sit on it for one week08:11
Qimingjust want to know, if we are bumping versions, we are not supposed to do 'git tag -s' by ourselves, right?08:12
Qimingtag will be managed by the release team, iiuc08:12
ttxQiming: yes08:12
ttxQiming: another aspect to the question is... is this for Mitaka or for Newton08:12
Qiminggreat, that helps, thanks!08:12
Qimingit is newton08:12
ttxIf it's featureful you should land those patches in master, and tag a 0.5.0 there08:12
ttxkeep 0.4.x for stable/mitaka patch releases (like a security fix)08:13
ttxQiming: so yeah, it's likely to be 0.5.008:13
Qimingthere are some small changes, not that significant, after we released 0.4.108:13
Qimingif we are introducing 0.5.0, there will be some major changes08:14
Qimingso I'm not sure where 0.4.2 should be proposed, into mitaka or newton08:14
Qiming0.5.0 is definitely a newton one08:14
ttxversion numbers are cheap. You can do a 0.5.0 over minor changes08:15
Qiminghahah, understood08:15
Qimingthanks for your time, sir08:15
ttxit is semantic versioning, not marketing versioning08:15
ttxQiming: np08:15
Qimingokay, got it08:15
ttxjroll: we'll need a bifrost 1.0.1 tag request for http://lists.openstack.org/pipermail/openstack-dev/2016-April/091241.html08:17
*** kzaitsev_mb has joined #openstack-release08:17
ttx(so that we get a tarball properly built for it)08:17
ttxif you propose it I can approve it.08:17
openstackgerritThierry Carrez proposed openstack/releases: Re-add tarball links for Congress and Astara  https://review.openstack.org/30150508:21
*** kzaitsev_mb has quit IRC08:21
*** vgridnev has quit IRC08:24
skraynevttx: hi. I have a question about stable branches for projects. Is it necessary to propose new tags for old stable branches? if yes - how often we need to do it? (as example in heat we have stable liberty branch with tag 5.0.1 at Jan 19 and after that we have a lot of commits with bug fixes)08:28
ttxskraynev: It becomes necessary when a security fix hits. It is a good practice to regularly issue point releases though, to get the other fixes out there and not build too long a queue08:30
*** daemontool has joined #openstack-release08:31
ttxI'd say every 2 months is a good idea08:31
ttxYou can ask on #openstack-stable for advice08:31
skraynevttx: aha. got it. thank you08:31
*** ihrachys has quit IRC08:31
*** dtantsur is now known as dtantsur|brb08:49
*** ajo_ is now known as ajo09:06
*** kzaitsev_mb has joined #openstack-release09:17
*** vgridnev has joined #openstack-release09:20
*** ihrachys has joined #openstack-release09:37
dimsttx : not sure what you feel about https://review.openstack.org/#/c/301337/ - they essentially fixed a test case and want a 0.13.1 release09:56
patchbotdims: patch 301337 - releases - Release glance_store 0.13.1 for stable/mitaka09:56
ttxI do not see why we absolutely need it pre-release, sounds like a post-release thing10:02
ttxdims: "Anything that can be released post-release should wait"10:03
ttxunless I'm misunderstanding the fix10:04
ttxdoesn't sound like "just a test case", it prevents co-installability ?10:04
ttxActually I'm more worried by the "increase of the cap of requirement version", since that would trigger other releases10:06
*** sdague has joined #openstack-release10:07
ttxhmm, maybe just glance10:08
*** Qiming has quit IRC10:09
ttxdims: so we could release it, bump requirements and then get a new Glance RC to include the requirement bump10:12
ttxbut if the only thing that happens is that tests can fail in a corner case scenario, I think it's post-release material10:15
*** kzaitsev_mb has quit IRC10:15
*** dtantsur|brb is now known as dtantsur10:16
ttxhmm, not corner case, our gate showed it too10:18
jokke_ttx: do we still roll for translations or should we wait until Mitaka is released and merge after that? there is Zanata PS 5 lines changed for Glance10:18
ttxjokke_: if we end up doing a RC to catch the glance-store requirement bump, we would include translations yes10:19
ttxjokke_: I'll approve that one just so that we have it in in case we need it10:19
jokke_ttx: I don't think that bump is requred based on our guidelines10:19
ttxjokke_: we kinda want to have the requirements all aligned at release team10:20
ttxtime*10:20
jokke_ttx: the glance_store does not bring any new functionality in that would warrant the bump10:20
ttxor are you saying we wouldn't need to bump requirements to >=0.13.1 ?10:20
jokke_yes ... releasing the glance_store should be enough10:21
ttxjust an upper-constraints bump ?10:21
jokke_let me double check that10:21
ttxhmm, ok, then no Glance RC, and we would not pick up translations (we do not reroll RCs for translations this week)10:21
dimsttx : my feeling is to get through Thu and release it on friday or monday10:22
dimsttx : since only the test case is affected and they already patched stable/mitaka branch10:23
ttxyeah, the "other CIs might get broken" rationale is a bit weak10:23
jokke_ttx: so yes upper constraints would need bump, all the other runs should just pick that glance store up even without the requirements bump10:23
ttxdistros can carry the patch if they end up being broken10:23
*** ihrachys has quit IRC10:24
dimsttx : so zigo who does other debian work routinely nixes tests especially when it comes to py3x etc10:24
dimsin oslo.* for sure10:24
ttxyeah, I think we can sleep on this one10:24
dimsyep10:24
dimscool thanks10:24
dimsi'll take care of it early next week10:25
*** _amrith_ is now known as amrith10:38
*** ihrachys has joined #openstack-release10:53
*** sdake has joined #openstack-release11:00
zigodims: Don't rely too much on me! :)11:05
zigottx: dims: Any chance to get some final releases today? Or I should expect it at the last hour of Friday? :)11:06
zigodisclosure: I'd very much prefer if everything was released early so I could go on holiday.11:06
*** cgalan has joined #openstack-release11:11
dimszigo : Thu AM EU time :)11:21
zigodims: FYI, I'm already uploading all to Sid, as for me, Mitaka works quite well already. IMO, not a bad release at all.11:26
zigoI don't know who I can thank for it... :P11:26
dimszigo : ack thanks11:26
dimszigo : everybody :)11:27
*** Qiming has joined #openstack-release11:34
openstackgerritJim Rollenhagen proposed openstack/releases: bifrost 1.0.1  https://review.openstack.org/30159611:40
jrollttx: ^11:40
*** sdake_ has joined #openstack-release11:54
*** kzaitsev_mb has joined #openstack-release11:55
*** sdake has quit IRC11:55
ttxjroll: thx12:02
*** cgalan has quit IRC12:03
*** bdemers has quit IRC12:09
*** cgalan has joined #openstack-release12:43
openstackgerritMerged openstack/releases: bifrost 1.0.1  https://review.openstack.org/30159612:45
*** gordc has joined #openstack-release12:46
*** sdake_ has quit IRC12:57
mugsiettx: quick question about a backport to stable/mitaka ... https://review.openstack.org/#/c/301614/ adds a new explicit requirement to designate (retrying). we already install it as a transitive dependancy - is this an issue for backporting?12:59
patchbotmugsie: patch 301614 - designate - Handle async Tooz calls appropriately12:59
ttxmugsie: not 100% sure. You should ask on #openstack-stable (since that would be released post-release that would fall under stable maint rules)13:00
mugsiei am looking at this as a posible RC3 backport13:00
mugsieit fixes issues that can occur where zk is slower than it is in CI envs13:01
ttxmugsie: we don't really take new RCs this week, unless the bug really can't be fixed post-release13:01
mugsieah, OK. I thought this week was more open. Will push to post release then13:02
ttxif it's a performance thing then a point release sounds good13:02
ttx(point release after the mitaka release)13:03
mugsieits not a perfomance thing, services will fail to start under some condidions13:03
ttxThat said, adding a dep might be a no-no in stable13:03
ttxso this might be a case where we'd rather fix it pre-release13:03
jrolldoesn't look like this adds a dep?13:03
mugsieyeah. its not an absolute requirement, but I would *like* to fix it pre release13:04
ttxyeah, it's a bit unclear how that change adds a dep13:04
jrollhttps://review.openstack.org/#/c/301614/ right?13:04
patchbotjroll: patch 301614 - designate - Handle async Tooz calls appropriately13:04
mugsiejroll: you are correct13:04
mugsiei cpoy pasted the wrong link  -_-13:04
mugsiehttps://review.openstack.org/#/c/298989/13:04
patchbotmugsie: patch 298989 - designate - Partitioner - Rety on failure to get members13:04
jrollheh13:04
ttxah, that might make more sense13:05
jrollmugsie: so if it's already a transitive dep, I feel like it might be okay, but I'd probably check with tonyb or mriedem_away to be safe13:05
mugsiecool. will ping -stable13:06
ttxmugsie: if for some reason they would rather not have that in stable post-release we can discuss doing a RC to roll that in pre-release13:06
ttxmugsie: we have a stable team meeting in one hour, so that would be a good time to ask13:07
ttxif you can't reach them before13:07
ttxmugsie: if we want to fix pre-release I'd rather do that today13:07
openstackgerritThierry Carrez proposed openstack/releases: Re-add tarball links for bifrost  https://review.openstack.org/30163513:09
mugsiettx: yeap, me too. Will start pinging people to get reviews.13:10
*** wendar_ has joined #openstack-release13:14
*** mriedem_away has quit IRC13:21
*** dougwig has quit IRC13:21
*** wendar has quit IRC13:21
*** mihgen has quit IRC13:21
*** pleia2 has quit IRC13:21
*** markmcclain has quit IRC13:21
*** daemontool has quit IRC13:21
*** mtreinish has quit IRC13:21
*** dstanek has quit IRC13:21
*** ajo has quit IRC13:21
*** odyssey4me has quit IRC13:21
*** tonyb has quit IRC13:21
*** bswartz has quit IRC13:21
*** sileht has quit IRC13:21
*** cp16net has quit IRC13:21
*** yarkot has quit IRC13:21
*** johnthetubaguy has quit IRC13:21
*** jroll has quit IRC13:21
*** EmilienM has quit IRC13:21
*** kzaitsev_mb has quit IRC13:21
*** kong has quit IRC13:21
*** onovy has quit IRC13:21
*** krotscheck has quit IRC13:21
*** slashme has quit IRC13:21
*** sigmavirus24_awa has quit IRC13:21
*** flaper87 has quit IRC13:21
*** tristanC has quit IRC13:21
*** Kiall has quit IRC13:21
*** SergeyLukjanov has quit IRC13:21
*** gordc has quit IRC13:21
*** sdague has quit IRC13:21
*** pcaruana has quit IRC13:21
*** openstackgerrit has quit IRC13:21
*** tsufiev has quit IRC13:21
*** amrith has quit IRC13:21
*** jhesketh has quit IRC13:21
*** dims has quit IRC13:21
*** redrobot has quit IRC13:21
*** mordred has quit IRC13:21
*** dansmith has quit IRC13:21
*** andreaf has quit IRC13:21
*** jokke_ has quit IRC13:21
*** HenryG has quit IRC13:21
*** patchbot has quit IRC13:21
*** AJaeger has quit IRC13:21
*** clarkb has quit IRC13:21
*** notmyname has quit IRC13:21
*** stevebaker has quit IRC13:21
*** jd__ has quit IRC13:21
*** smcginnis has quit IRC13:21
*** zigo has quit IRC13:21
*** bknudson has quit IRC13:21
*** sekrit has quit IRC13:21
*** ChanServ has quit IRC13:21
*** david-lyle has quit IRC13:21
*** jeblair has quit IRC13:22
*** lifeless has quit IRC13:22
*** mestery has quit IRC13:22
*** kzaitsev_ws has quit IRC13:22
*** mugsie has quit IRC13:22
*** v12aml has quit IRC13:22
*** ttx has quit IRC13:22
*** stevemar has quit IRC13:22
*** SlickNik has quit IRC13:22
*** igorbelikov has quit IRC13:22
*** mhayden has quit IRC13:22
*** dtantsur has quit IRC13:22
*** jgriffith has quit IRC13:22
*** njohnston has quit IRC13:22
*** Qiming has quit IRC13:22
*** vgridnev has quit IRC13:22
*** peterstac has quit IRC13:22
*** Daviey_ has quit IRC13:22
*** bnemec has quit IRC13:22
*** anteaya has quit IRC13:22
*** abramley has quit IRC13:22
*** coreycb has quit IRC13:22
*** vipul has quit IRC13:22
*** morgan has quit IRC13:22
*** freerunner has quit IRC13:22
*** robcresswell has quit IRC13:22
*** cgalan has quit IRC13:22
*** sheeprine has quit IRC13:22
*** devananda has quit IRC13:22
*** skraynev has quit IRC13:22
*** fungi has quit IRC13:22
*** bauzas has quit IRC13:22
*** kragniz has quit IRC13:22
*** dougshelley66 has quit IRC13:22
*** SamYaple has quit IRC13:22
*** mihgen_ has joined #openstack-release13:22
*** mihgen_ is now known as mihgen13:22
*** dougwig_ has joined #openstack-release13:24
*** mriedem has joined #openstack-release13:24
*** gordc has joined #openstack-release13:24
*** cgalan has joined #openstack-release13:24
*** kzaitsev_mb has joined #openstack-release13:24
*** Qiming has joined #openstack-release13:24
*** sdague has joined #openstack-release13:24
*** daemontool has joined #openstack-release13:24
*** pcaruana has joined #openstack-release13:24
*** sheeprine has joined #openstack-release13:24
*** sekrit has joined #openstack-release13:24
*** david-lyle has joined #openstack-release13:24
*** zigo has joined #openstack-release13:24
*** bswartz has joined #openstack-release13:24
*** openstackgerrit has joined #openstack-release13:24
*** kong has joined #openstack-release13:24
*** stevemar has joined #openstack-release13:24
*** bauzas has joined #openstack-release13:24
*** devananda has joined #openstack-release13:24
*** dims has joined #openstack-release13:24
*** mtreinish has joined #openstack-release13:24
*** sileht has joined #openstack-release13:24
*** patchbot has joined #openstack-release13:24
*** dstanek has joined #openstack-release13:24
*** redrobot has joined #openstack-release13:24
*** skraynev has joined #openstack-release13:24
*** peterstac has joined #openstack-release13:24
*** onovy has joined #openstack-release13:24
*** krotscheck has joined #openstack-release13:24
*** jeblair has joined #openstack-release13:24
*** ajo has joined #openstack-release13:24
*** Daviey_ has joined #openstack-release13:24
*** pleia2 has joined #openstack-release13:24
*** SlickNik has joined #openstack-release13:24
*** AJaeger has joined #openstack-release13:24
*** EmilienM has joined #openstack-release13:24
*** anteaya has joined #openstack-release13:24
*** igorbelikov has joined #openstack-release13:24
*** sigmavirus24_awa has joined #openstack-release13:24
*** slashme has joined #openstack-release13:24
*** fungi has joined #openstack-release13:24
*** markmcclain has joined #openstack-release13:24
*** abramley has joined #openstack-release13:24
*** lifeless has joined #openstack-release13:24
*** cp16net has joined #openstack-release13:24
*** flaper87 has joined #openstack-release13:24
*** mhayden has joined #openstack-release13:24
*** tsufiev has joined #openstack-release13:24
*** dtantsur has joined #openstack-release13:24
*** odyssey4me has joined #openstack-release13:24
*** morgan has joined #openstack-release13:24
*** tristanC has joined #openstack-release13:24
*** mestery has joined #openstack-release13:24
*** mordred has joined #openstack-release13:24
*** dansmith has joined #openstack-release13:24
*** Kiall has joined #openstack-release13:24
*** SamYaple has joined #openstack-release13:24
*** kzaitsev_ws has joined #openstack-release13:24
*** clarkb has joined #openstack-release13:24
*** bnemec has joined #openstack-release13:24
*** yarkot has joined #openstack-release13:24
*** jgriffith has joined #openstack-release13:24
*** andreaf has joined #openstack-release13:24
*** mugsie has joined #openstack-release13:24
*** njohnston has joined #openstack-release13:24
*** jokke_ has joined #openstack-release13:24
*** SergeyLukjanov has joined #openstack-release13:24
*** johnthetubaguy has joined #openstack-release13:24
*** jroll has joined #openstack-release13:24
*** amrith has joined #openstack-release13:24
*** notmyname has joined #openstack-release13:24
*** vipul has joined #openstack-release13:24
*** kragniz has joined #openstack-release13:24
*** stevebaker has joined #openstack-release13:24
*** jd__ has joined #openstack-release13:24
*** HenryG has joined #openstack-release13:24
*** tonyb has joined #openstack-release13:24
*** v12aml has joined #openstack-release13:24
*** robcresswell has joined #openstack-release13:24
*** ttx has joined #openstack-release13:24
*** bknudson has joined #openstack-release13:24
*** smcginnis has joined #openstack-release13:24
*** dougshelley66 has joined #openstack-release13:24
*** coreycb has joined #openstack-release13:24
*** freerunner has joined #openstack-release13:24
*** jhesketh has joined #openstack-release13:24
*** ChanServ has joined #openstack-release13:24
*** wolfe.freenode.net sets mode: +o ChanServ13:24
*** openstackstatus has quit IRC13:24
*** openstackstatus has joined #openstack-release13:27
*** ChanServ sets mode: +v openstackstatus13:27
*** dougwig_ is now known as dougwig13:29
ttxdims: I'm trying to determine if monasca-ceilometer would trigger a tarball now that the jobs are defined. COuld you check that it has the required venv stuff (so that it doesn't fail the way monasca-log-api failed)13:29
ttxI'll check the zuul job definition13:29
dimsack13:29
dimsttx : it will fail. let me file a review for them13:30
*** vgridnev has joined #openstack-release13:31
dimsttx : filed 2 reviews master and stable/mitaka - https://review.openstack.org/#/q/I72df080b222596c35e982c14ca2a5b5501f4a1bf,n,z13:34
*** Kiall has quit IRC13:36
*** Kiall has joined #openstack-release13:37
dimspinging folks on #openstack-monasca13:38
*** bdemers has joined #openstack-release13:42
ttxHopefully Roland will show up13:47
ttxwas waiting for him to ask for a new tag13:48
ttxwe probably need the jobs added in zuul too13:50
*** gordc has quit IRC13:50
ttxLooking at zuul/layout.yaml it's missing openstack-server-publish-jobs13:51
ttx(or publish-to-pypi)13:51
ttxshould have openstack-server-release-jobs probably13:54
ttxAt this stage I'm wondering if we should further fix them since they don't seem to care that much13:55
*** sigmavirus24_awa is now known as sigmavirus2413:56
*** gordc has joined #openstack-release13:57
*** hongbin has joined #openstack-release13:57
*** bdemers has quit IRC14:01
dimsttx : ack14:02
dimsttx : +1 to drop it14:02
ttxyeah, I'll go as far as asking them to tag 0.0.3 on monasca-log-api14:02
*** bdemers has joined #openstack-release14:04
*** sdake has joined #openstack-release14:15
dimsttx : looks like they +2A'ed the tox.ini changes on monasca-ceilometer. let me go look in their repo to see what they have in there14:17
ttxhmm14:18
dimsttx : monasca-ceilometer is not ready - http://paste.openstack.org/show/493004/14:21
ttxdims: bah14:21
dimsi ran "tox -evenv python setup.py sdist" which is what the tar ball job does14:21
ttxlet's keep it no-tarballed14:22
AJaegerdims, thanks for checking14:22
dimsttx : and NOT upload to pypi either14:22
dimsAJaeger :)14:23
ttxRoland is up for reviews but not on IRC (nor reacting to ML posts)14:24
ttxanteaya: if you have some magic intra-HP way to contact rhochmuth, please point him to http://lists.openstack.org/pipermail/openstack-dev/2016-April/091387.html14:25
ttxAJaeger: I think we have everything set up to generate tarballs for monasca-log-api, but wouldn't mind an extra check to be sure14:26
ttxdims: ^14:26
dimsttx : y let me check that too14:26
ttxused to fail for lack of venv14:27
ttxfixed in https://review.openstack.org/#/c/299936/14:27
patchbotttx: patch 299936 - monasca-log-api - Adds [testenv:venv] section to tox.ini (MERGED)14:27
dimsttx : y looks decent http://paste.openstack.org/show/493007/14:27
ttxhmm, not backported14:27
dimsttx : ouch, you are right14:28
anteayattx: I don't even know who rhochmuth is14:28
AJaegerttx, I get monasca-log-api-0.0.3.dev3.tar.gz which looks fine - on master14:28
dimsfiled one https://review.openstack.org/#/c/301707/14:28
patchbotdims: patch 301707 - monasca-log-api (stable/mitaka) - Adds [testenv:venv] section to tox.ini14:28
anteayattx: so I'm uncertain how much help I'll be14:29
ttxanteaya: ok, thanks anyway :)14:29
dimsanteaya : Roland Hochmuth14:29
anteayadims: I think that is supposed to help me14:30
anteayathat still doen'st help me14:30
dimsLOL. no worries. anteaya14:31
anteayaI could fire off an email to roland.hochmuth and hope for the best14:31
anteayabut I don't know that person14:31
anteayaI can do that14:31
openstackgerritRoland Hochmuth proposed openstack/releases: Add new tag for monasca-ceilometer Mitaka deliverables  https://review.openstack.org/30170914:31
ttxThey don't appear to use their IRC channel at all14:31
* ttx adds monasca to the list to clean up14:32
anteayaperson is online apparently14:32
anteayaI'll track that patch for an email14:32
anteayaold company name14:32
ttxcommunicating with him through Gerrit14:33
AJaeger;/14:34
ttxhttps://review.openstack.org/#/c/301709/114:34
patchbotttx: patch 301709 - releases - Add new tag for monasca-ceilometer Mitaka delivera...14:34
*** kzaitsev_mb has quit IRC14:35
anteayashould I cc -dev?14:35
anteayaI'm think I should cc dev14:35
anteayaor should I not send the email if you are talking to him?14:36
* anteaya stand sy14:36
anteayas/sy/by14:36
* anteaya releases sy14:36
ttxHe reads Gerrit but not email, so let's see if my comment there works14:36
anteayaokay let me know to send or to delete14:38
anteayaif I send should I cc -dev?14:38
ttxanteaya: no need, I use Gerrit comments to discuss with him14:38
* anteaya deletes14:39
anteayathanks14:39
*** thinrichs has joined #openstack-release14:43
*** kzaitsev_mb has joined #openstack-release14:43
ttxok, he is on irc now14:48
ttxPMing14:48
ttxso he tagged 0.0.3 on master :/14:52
ttx(for monasca-ceilometer)14:52
* AJaeger hugs ttx14:52
ttxAJaeger: we might need to destroy their stable/mitaka branch and redo it now14:53
AJaeger;(((14:53
ttxAlternative is to be stuck with a stable/mitaka branch we can't release out of14:54
*** sdake_ has joined #openstack-release14:54
ttxcould go both ways14:55
ttxAJaeger: do you have magic powers or should I ask fungi ?14:56
*** sdake has quit IRC14:57
AJaegerttx, ask fungi, I have no magic powers14:57
ttxfungi: monasca-ceilometer tagged 0.0.3 on master, preventing further stable/mitaka releases. We could let that be (given its a corner repo) or delete/rebranch stable/mitaka from 0.0.314:58
fungichecking to see which incantations are being requested14:58
fungittx: yeah, i think dhellmann had a similar request a couple weeks ago though i don't recall which project it was14:58
ttxdid I mention I can't wait until no official project can tag directly ?14:59
openstackgerritTim Hinrichs proposed openstack/releases: Disable links for Congress in Liberty  https://review.openstack.org/30173915:00
fungii can do it. won't be fast-forward updatable for anyone following that branch, however since we haven't released mitaka yet that seems like something we should avoid guaranteeing anyway15:00
fungijust a sec15:00
* ttx switched to bi-meeting mode15:00
ttxfungi: let me know when branch is deleted and I'll recreate it15:00
fungiit's gone now15:01
fungittx: ^15:01
*** dtantsur is now known as dtantsur|brb15:03
*** pcaruana has quit IRC15:06
dimsfungi : thanks15:14
fungiany time15:14
*** vgridnev has quit IRC15:18
*** vgridnev has joined #openstack-release15:19
*** Qiming has quit IRC15:21
*** sdake_ has quit IRC15:27
*** sdake has joined #openstack-release15:27
openstackgerritRoland Hochmuth proposed openstack/releases: Request new tag on Mitaka monasca-log-api  https://review.openstack.org/30176215:29
*** armax has joined #openstack-release15:36
*** dtantsur|brb is now known as dtantsur15:39
*** armax has quit IRC15:41
openstackgerritThierry Carrez proposed openstack/releases: Request new tag on Mitaka monasca-log-api  https://review.openstack.org/30176215:42
*** sigmavirus24 is now known as sigmavirus24_awa15:43
*** sigmavirus24_awa is now known as sigmavirus2415:43
*** daemontool has quit IRC15:45
zigottx: dims: We're having an issue with glance-store 0.13.0 and swiftclient 3.0.0.15:50
zigoThe latest version of swiftclient (ie: 3.0.0) breaks glance-store.15:51
dimszigo : https://review.openstack.org/#/c/301337/15:51
patchbotdims: patch 301337 - releases - Release glance_store 0.13.1 for stable/mitaka15:51
zigoI've heard from upstream that you don't really wish to have a release for glance-store.15:51
zigoOh, good ! :)15:51
zigodims: Why -1 for this?15:51
*** kzaitsev_mb has quit IRC15:51
dimszigo : we'll cut that after Thu15:51
dimssince it's just a test case that is being fixed.15:52
zigodims: I'd prefer if it was done ASAP, but ok.15:52
zigodims: This delays pushing swiftclient 3.0.0 for us.15:52
dimszigo : trying to minimize churn.15:52
zigochurn ?15:53
zigodims: What's that? :)15:53
dimsif we release 0.13.1 then we have to fix global requirements, then that would trigger other projects to merge new requirements.txt which then means we have to release them too15:53
dimsand so on15:54
dimsthere's no functional difference between 0.13.0 and 0.13.1 in the runtime code15:55
zigodims: The only project that (build-)depends on glance-store is glance itself, as much as I can see, so that will only trigger *ONE* update.15:55
zigodims: It'd be better to let Glance final to get such an update, IMO.15:55
zigo(I just did a grep glance-store */*/debian/control in my laptop to check...)15:56
onovy+1 for releasing it before final release15:56
dimszigo : you have in the other oslo projects commented out tests that break, what's the difference between that and fixing glance_store locally?15:56
*** kzaitsev_mb has joined #openstack-release15:56
zigodims: I'm not sure what you're referring to with the oslo projects.15:57
zigodims: For fixing glance-store in Debian with a patch, I've already asked in #openstack-glance, and I still don't have a confirmation that the patch I was pointing at fixes the issue.15:57
zigodims: If it does fully, then no problem, we'll use the patch and shut up.15:58
zigodims: FYI, onovy currently takes care of all Swift stuff in Debian, which is why he's included in the discussion! :)15:58
dimszigo : nikhil mentioned that the stable/mitaka of glance_store has the fix you need15:58
onovymy point of view: if i download all released mitaka source code and want to build it myself, it should work. and it's not true now15:59
zigodims: stable/mitaka is a branch, which isn't what we upload. We upload *tags*, plus cherry-picked patches. It's just bad to upload a random trunk commit, as we can't really tell upstream what we're using, and have no point of reference.15:59
dimsonovy : it's a question of timing, i'd prefer to wait16:00
zigoWhich is why I'd prefer to be pointed at the specific patch (or in this case, just a confirmation that the patch I want to include is enough).16:00
dimsit's not trunk commit, it's a stable/mitaka branch commit16:00
zigodims: Sorry, yes.16:00
zigoEquivalent, for me.16:00
onovyzigo: it's only commit in stable/mitaka branch after glance_store release16:00
zigoJust a branch random toplevel commit.16:00
dimsif it's not there in the stable/ branch then there's no point i us making a release either16:00
zigoonovy: There's a *single* patch on top of 0.13.0 ?16:01
dimsyes16:01
zigoOh...16:01
dimsone stupid test case that uses private methods16:01
onovy2 patches:16:01
onovyhttps://github.com/openstack/glance_store/commit/4600adb85aebb0402728fd7b053b0e61d0d586c216:01
zigoonovy: In this case, let's just include the patch and stop bothering dims, obviously, it's going to be enough.16:01
onovyhttps://github.com/openstack/glance_store/commit/33c08d8dec495dca2d7a9a7c44d23670aacf29d916:01
onovyone is "useless" for us16:01
dimsyou don't really need the gitreview patch16:01
zigoRight! :)16:02
onovy:)16:02
onovyzigo: yep, that was my suggestion, just build 0.13.0+git...16:02
zigoonovy: Ok, let's go back and discuss in #debian-openstack.16:02
dimswe can cut 0.13.1 right after the big release....not before16:02
zigodims: Thanks for the clarification.16:02
onovydims: ok, thanks!16:02
zigoAnd feel free to ignore it, it's fine for us now.16:02
dimsthanks zigo onovy16:03
dimsno hard feelings please16:03
*** vgridnev has quit IRC16:04
onovyi think we are fine with it16:04
zigodims: *never* ! :)16:04
onovy:]16:04
dimsLOL16:04
* zigo sends lots of love to dims16:04
dimsthanks a bunch :)16:04
zigodims: You're always happy to help, it always feels warm.16:05
*** thinrichs has quit IRC16:05
dimsawww.16:05
*** kzaitsev_mb has quit IRC16:06
*** kzaitsev_mb has joined #openstack-release16:09
*** thinrichs has joined #openstack-release16:10
*** cgalan has quit IRC16:24
*** armax has joined #openstack-release16:30
*** cgalan has joined #openstack-release16:39
*** wendar_ is now known as wendar16:45
armaxttx: ping16:48
armaxI seem to get a 500 on http://design-summit-prep.openstack.org/ is it just me? I tried to clean cookies etc16:48
armaxit worked yesterday16:48
*** sridhar_ram has joined #openstack-release16:57
*** cody-somerville has joined #openstack-release17:01
*** vgridnev has joined #openstack-release17:02
*** cody-somerville has quit IRC17:04
*** cody-somerville has joined #openstack-release17:05
*** cody-somerville has joined #openstack-release17:05
*** cody-somerville has quit IRC17:08
*** cody-somerville has joined #openstack-release17:09
*** sdake_ has joined #openstack-release17:10
*** sdake has quit IRC17:10
*** morgan is now known as notnotmyname17:21
*** notnotmyname is now known as morgan17:21
*** mriedem1 has joined #openstack-release17:22
*** mriedem has quit IRC17:23
dimsarmax : does your browser have a incognito mode? url works for me17:29
armaxdims: I tried incognito mode, but it didn’t seem to work either17:29
armaxdims: hence I am puzzled17:29
dimsarmax : the name resolves to 23.253.125.21917:30
armaxdims: don’t get me wrong, I can get it to work with another browser17:32
dimsah ok17:32
armaxdims: I was simply puzzled that after clearing cookies, etc that would still happen17:33
armaxdims: I suppose a 500 could be solved server side if there was any interest17:33
dimsarmax : no clue. as long you are unblocked i am happy :)17:33
armaxdims: so am I :)17:35
armaxdims: thanks for the feedback17:35
*** vgridnev has quit IRC17:39
*** TravT has quit IRC17:48
*** TravT has joined #openstack-release17:50
*** mriedem1 is now known as mriedem17:59
*** bdemers has quit IRC18:03
*** ihrachys has quit IRC18:04
*** vgridnev has joined #openstack-release18:05
*** dtantsur is now known as dtantsur|afk18:08
*** kzaitsev_mb has quit IRC18:14
*** bdemers has joined #openstack-release18:15
*** bdemers has quit IRC18:19
openstackgerritThierry Carrez proposed openstack/releases: Request new tag on Mitaka monasca-log-api  https://review.openstack.org/30176218:34
ttxarmax: should be good now18:43
ttxarmax: some problem with the summit schedule API server18:43
armaxttx: ack18:44
armaxthanks18:44
openstackgerritMerged openstack/releases: Add new tag for monasca-ceilometer Mitaka deliverables  https://review.openstack.org/30170918:48
openstackgerritMerged openstack/releases: Request new tag on Mitaka monasca-log-api  https://review.openstack.org/30176218:51
stevemardhellmann: we may have another release blocker... i'll let you know soon18:51
*** ihrachys has joined #openstack-release18:52
dhellmannttx: how are things looking?18:53
ttxdhellmann: fixed most of the tarballs situation18:53
ttxwe'll likely just keep monasca-ceilometer and monasca-thresh as no-tarball18:54
ttxsince those are further away18:54
dhellmanngood18:54
dhellmannwere the others just issues with names, or did we end up adding jobs? I saw a couple of re-tags18:54
ttxdhellmann: been holding fast, but now stevemar seems to have something for us18:55
ttxdhellmann: jobs added, tox venv added...18:55
stevemarttx: dhellmann we're determining if https://bugs.launchpad.net/keystone/+bug/1566282 is a blocker18:55
openstackLaunchpad bug 1566282 in OpenStack Identity (keystone) "Returning federated user fails to authenticate with HTTP 500" [Undecided,In progress] - Assigned to Boris Bobrov (bbobrov)18:55
dhellmannttx: good, I'm glad you got those sorted out18:56
dhellmannttx: leave it to stevemar to cause trouble ;-)18:56
ttxstevemar: if it can be fixed post-release, we'll likely just wait. Only case we'd take it pre-release is if it's completely broken and can't be fixed post-release /and/ the fix is totally safe18:56
dhellmannif it's something we can handle via a release note, you could commit the fix with the note18:57
stevemarttx: it can be fixed post release, yes.18:57
dhellmannand we'd just hold off on tagging18:57
*** dolphm has joined #openstack-release18:58
dhellmanngood18:58
ttxstevemar: then it depends on how broken it is, and how safe the fix is18:58
ttxstevemar: I'll let you assess more precisely18:58
stevemarttx: i'd say it's pretty broken without the fix, dolphm agreed?18:59
stevemarthe fix should be pretty safe, minimal code: https://review.openstack.org/#/c/301795/118:59
patchbotstevemar: patch 301795 - keystone - Update federated user display name with shadow_use...18:59
ttxstevemar: does the new test cover the issue ? i.e. it would have uncovered the problem if it was there before ?19:01
ttxgiven the fix is safe and keystone is a bit critical, I'm fine with re-RCing19:01
ttxdhellmann: ?19:02
stevemarttx: yes it does. i'm just checking now to see if it happens on update or all the time19:02
ttxstevemar: first step would be to get the fix in master anyway, before we commit to anything19:02
* ttx will be back in a few19:02
stevemaryep, for sure19:03
dhellmannstevemar, ttx: how broken can it be if we're just discovering the issue now?19:07
dimsstevemar : y seems pretty safe fix19:07
dhellmannstevemar, ttx: that said, if you're confident of the fix then I'm OK with a new RC19:08
*** thinrichs has quit IRC19:08
stevemardhellmann: it happens with our federation APIs, which is a core code path but not the most popular code, and we have no functional tests for it19:09
dhellmannstevemar: ah19:09
dimsstevemar : shows up only in federation19:09
stevemardhellmann: it also is a result of work that went merged in mitaka-319:10
dimsstevemar : how much of federation do we test in gates?19:10
stevemardims: unit tests only19:10
dhellmannttx, dims: for the projects that fixed their build setup and now have deliverables, do we care that the links to old versions are broken?19:10
dimsdhellmann : personally no :)19:11
dhellmannttx, dims: for example in https://review.openstack.org/#/c/301635/1/deliverables/mitaka/bifrost.yaml19:11
patchbotdhellmann: patch 301635 - releases - Re-add tarball links for bifrost (MERGED)19:11
dhellmanndims: :-)19:12
dimsdhellmann : we can worry about it next week :)19:13
*** vgridnev has quit IRC19:15
*** vgridnev has joined #openstack-release19:16
sridhar_ramttx: dhellmann: looking for some guidance on removing an old / unused feature in tacker. This is in the context of https://review.openstack.org/#/c/282386/19:21
patchbotsridhar_ram: patch 282386 - tacker - [WIP] Remove nova infra_driver from master19:21
sridhar_ramttx: dhellmann: Tacker, before it was for NFV, used to support an option to go directly to Nova. We have switched to use Heat for while now (starting Kilo). We no longer support Nova / have any tests at this time. AFAIK, there is no body using this option any more.19:21
sridhar_ramttx: dhellmann: However we have so far tried to stick to the spirit of "assert:follow-standard-deprecation" as a best practice even though we are not claiming that tag. But we missed landing the deprecation patchset in mitaka - https://review.openstack.org/29972419:21
stevemarttx: dhellmann okay, so the bug seems happen when a federated user authenticates twice, which is super sucky. luckily the fix is small, already up and ready to be merged into master19:22
stevemari'll proposed a backport to mitaka and if it's okay with you both, i think we need an rc319:22
sridhar_ramttx: dhellmann: As a project, we really like to get this code out...is it okay to go ahead and remove it ?19:22
dhellmannstevemar: yep, go ahead19:23
dimsstevemar : +1 from me as well19:23
dhellmannsridhar_ram: you should go over that with the stabile maintenance team19:24
dhellmannsridhar_ram: talk with tonyb for example19:24
*** bdemers has joined #openstack-release19:25
sridhar_ramdhellmann: okay, do they have a channel ?19:25
dimssridhar_ram : #openstack-stable19:25
sridhar_ramdims: cool, thanks!19:25
dhellmannttx, dims: I'm dropping offline again. Thanks for keeping things moving!19:26
dimsdhellmann : safe travels19:26
*** sdake_ has quit IRC19:31
*** gordc has quit IRC19:33
*** sdake has joined #openstack-release19:40
*** sdake has quit IRC19:44
stevemardims: as a heads up, i approved the backport: https://review.openstack.org/#/c/301878/19:46
patchbotstevemar: patch 301878 - keystone (stable/mitaka) - Update federated user display name with shadow_use...19:46
*** sdake has joined #openstack-release19:46
dimsstevemar : ack19:46
*** thinrichs has joined #openstack-release19:47
openstackgerritThierry Carrez proposed openstack/releases: Restore monasca-log-api tarball link  https://review.openstack.org/30188419:51
openstackgerritSteve Martinelli proposed openstack/releases: release keystone-rc3  https://review.openstack.org/30188519:52
stevemardims: this https://review.openstack.org/#/c/301885/ should have the right commit #, just needs to be merged19:52
patchbotstevemar: patch 301885 - releases - release keystone-rc319:52
ttxstevemar: playing two moves forward I see19:53
stevemarttx: :)19:54
*** gordc has joined #openstack-release19:54
*** sdake_ has joined #openstack-release19:58
*** sdake has quit IRC20:01
*** sdake_ has quit IRC20:12
*** sdake has joined #openstack-release20:13
*** kzaitsev_mb has joined #openstack-release20:18
*** david-lyle_ has joined #openstack-release20:28
*** david-lyle has quit IRC20:29
*** david-lyle_ is now known as david-lyle20:29
*** vgridnev_ has joined #openstack-release20:32
*** ihrachys has quit IRC20:39
*** sridhar_ram has quit IRC20:39
*** vgridnev_ has quit IRC20:42
amrithi believe that Trove's stable/mitaka branch is still controlled by the release team. would someone please approve https://review.openstack.org/#/c/301726/ ... I'm unable to. cp16net has approved.20:42
patchbotamrith: patch 301726 - trove (stable/mitaka) - Fixes migrations for MySQL 5.6.* and MariaDB 10.1.*20:42
*** rockyg has joined #openstack-release20:48
stevemarttx: dims the change is gating now, let's hope it doesn't fail20:58
*** vgridnev_ has joined #openstack-release21:01
ttxdims: please approve https://review.openstack.org/#/c/301884/21:01
patchbotttx: patch 301884 - releases - Restore monasca-log-api tarball link21:01
ttxamrith: we'll revert the ACLs by Thursday21:02
amrithttx, thanks21:02
ttxamrith: that sounds like something you can't fix post-release ?21:03
ttxi.e. changing db migrations21:03
amrithttx, let me give you a detailed explanation of why it is.21:03
amrithI'll paste bomb it here, give me 2m21:03
ttxamrith: if it can be fixed post-release then we'll probably sit on it until we revert the acl and you can include it in stable/mitaka21:04
amrithI would love to fix it pre-release but I figure that this boat has sailed21:04
ttxwe only fix pre-release stuff that can't really be fixed post-release21:05
amrithttx, I would be hard pressed to make that case. so this is post release.21:05
ttxhere you push the fix to stable/liberty too so I assume it /can/ be fixed post-release21:05
ttxok21:06
amrithdo you still want to know why this fix is safe?21:06
ttxso, frozen for 40 more hours21:06
amrith:)21:06
ttxamrith: I think I'll get my evening back instead :)21:06
amrithttx, good call.21:06
dims+2A https://review.openstack.org/#/c/301884/21:06
patchbotdims: patch 301884 - releases - Restore monasca-log-api tarball link21:06
amrithhave a good evening ...21:06
dimsttx : ^^21:06
ttxdims: thx21:07
flwang1ttx: thank you21:07
ttxstevemar: I'll process the RC3 early tomorrow morning. Just make sure the patch lands in master and stable/mitaka. Then if you're bored you can recheck https://review.openstack.org/#/c/301885/21:08
patchbotttx: patch 301885 - releases - release keystone-rc321:08
ttxit won't pass until the change merges21:08
stevemarttx: yep21:09
stevemarttx: dims might beat you to it ;)21:09
stevemarit should be fully baked in an hour or two, i'll recheck it when it's done21:09
stevemarbiab21:09
dims:) i'll try to stay awake stevemar21:09
openstackgerritMerged openstack/releases: Restore monasca-log-api tarball link  https://review.openstack.org/30188421:09
*** vgridnev has quit IRC21:15
*** kong has quit IRC21:18
*** kong has joined #openstack-release21:19
*** kzaitsev_mb has quit IRC21:21
flwang1ttx: not sure i fully followed all your points about https://review.openstack.org/#/c/301380/ (backporting a small fix for tempest zaqar to facilitate puppet zaqar test), so did you mean for this kind of patch, we could wait mitaka landed/released, and then backport it,  right?21:23
patchbotflwang1: patch 301380 - zaqar (stable/mitaka) - Fix tempest tests list21:23
flwang1and we don't have to propose a RC3, is it?21:23
kongttx: we have a critical bug need to be fixed for stable mitaka today, I wonder if we can still make the rc3 release application?21:27
*** sdake_ has joined #openstack-release21:30
dimskong : is the fix merged in stable/mitaka?21:30
kongdims: going to be merge, not yet21:30
dimskong : url?21:30
kongdims: I just want to make sure we are not touch the deadline21:30
kongdims: for master: https://review.openstack.org/#/c/301588/21:31
patchbotkong: patch 301588 - mistral - Fixing issue with different versions of oslo_messa...21:31
dimskong : let me look at what you have :)21:31
kongI'll cherry pick it for mitaka21:31
dimsflwang1 : https://review.openstack.org/#/c/301380/ is just a fix needed in a test environment right? so +1 to fix the branch, don't see a need for a RC321:32
patchbotdims: patch 301380 - zaqar (stable/mitaka) - Fix tempest tests list21:32
flwang1dims: yep, it's just a small fix for tempest code21:33
*** sdake has quit IRC21:33
dimsflwang1 : ack21:33
dimskong : looking21:33
flwang1dims: so do you mean we can merge it but don't have to propose a RC3?21:33
dimsflwang1 : y21:33
dimskong : so i see 4.5.0 iof oslo.messaging in g-r - http://git.openstack.org/cgit/openstack/requirements/tree/global-requirements.txt#n10821:35
dimskong : why do you need this?21:36
dimskong : trying to understand21:36
dimsas there isn't enough info in the commit message and no bug link21:36
flwang1dims: got, thanks21:37
*** sdake_ has quit IRC21:37
dimskong : pong21:37
dimsoops ping21:37
*** sdake has joined #openstack-release21:38
kongdims: i'm not sure the library version for stable mitaka is fixed or we can use the latest version in g-r?21:38
dimskong : oops my bad. branch has http://git.openstack.org/cgit/openstack/requirements/tree/global-requirements.txt?h=stable/mitaka#n10721:38
kongdims: exactly21:38
dimsone sec21:39
*** sdake has quit IRC21:39
kongthere are some changes since 4.4.0 that affect mistral HA feature21:40
hongbinHi all. A question: do anyone know which person/team is responsible for producing Ubuntu package (Ubuntu package for Magnum is missing so I want to find the right person to talk to).21:41
konghongbin: i found this before: https://qa.debian.org/developer.php?login=openstack-devel@lists.alioth.debian.org21:42
clarkbhongbin: canonical/ubuntu do it themselves21:42
dimshongbin : see http://markmail.org/message/2mrenckrq7jyuxsv21:42
clarkband debian does their own21:42
hongbinThanks all21:43
dimsdebian you can talk to zigo onovy but channels are there in the email thread21:43
dimsyw21:43
zigoo/21:43
dimskong : trying to figure out what to do21:43
dimsgive me a few21:43
kongdims: sure, thanks21:43
*** mriedem has quit IRC21:44
zigohongbin: Ubuntu does *not* package Magnum. I do it in Debian though, and also produce some Trusty backports. Feel free to use these.21:45
zigohongbin: You can try to ping Canonical guys so that they sync the package from Debian if you care for that (I don't care about it so much...).21:45
hongbinzigo: Thanks. Another question21:46
hongbinzigo: How often you produced a package update (each release? each milestone?)21:46
zigohongbin: Basically, each time upstream is producing a tag.21:47
zigohongbin: So, each beta release, rc, final release, or point release.21:47
hongbinzigo: I see. Get that21:47
zigoWell, point release, I wish I had more time to do these... :/21:47
zigoTruth is, I used to, but now I don't so much.21:48
hongbinI will try to release on the upstream schedule if you like21:48
zigoContribution for that would be very much welcome, it's also very easy to do.21:48
zigohttp://packages.ubuntu.com/search?keywords=python-magnum <--- Gosh, that's lame, they took the Magnum package from 4 months ago in Debian, and didn't update it since !!! :(21:49
zigoI'd prefer if they didn't take it at all...21:49
hongbin.....21:49
dimskong : so you need that to acknowledge?21:52
dimskong : the code you have will work with existing released versions of oslo.messaging (till 4.6.1), you will have to raise a red flag to the oslo team about the DispatcherExecutorContext they are going to make that simpler by having a dispatch method in DispatcherBase21:56
dimskong : folks to ping are harlowja/sileht/dukhlov and change i am talking about is  I5f23e23644e90919cb67f81fc306ee85c5e09974 in master21:57
dimskong : so am ok with the review you have merging into stable/mitaka and doing another RC21:58
dimskong : i'd not seen your use case in mistral at all earlier....21:59
kongdims: there was a looong discussion about the ack mode in Mistral, it's heavily used for task execution, we need that feature to achieve HA, which is required by some mistral users22:01
dimskong : right, i remember the discussion, had not seen the code :)22:01
*** sigmavirus24 is now known as sigmavirus24_awa22:01
kongthat's why we have it implemented in mistral ourselves22:02
dimskong : so net, +1 to RC with this change, let's make sure to follow up with those folks to get back compat you will need22:02
kongdims, ok22:03
dimskong : y, it's just that it's likely to break :(22:03
*** bdemers has quit IRC22:03
kongdims: that's right. just a workround for now, maybe someday oslo will support that and we can remove our code22:03
kong:-)22:04
dimskong : you really need to run a job against oslo-messaging master and yell at them22:04
kongdims: haha~22:04
dimsy, that too22:04
kongdims: so, anyway, i'll merge that patch today, and make a new release application22:04
kongdims: thanks22:04
dimssounds good kong22:05
dimskong : if you have a devstack job, just throwing in a LIBS_FROM_GIT=oslo.messaging is enough. So i am serious about you proposing a new job22:07
kongdims: got that, will forward it in mistral team, and do that asap22:08
*** rockyg has quit IRC22:08
dimscool ttyl22:08
*** vgridnev_ has quit IRC22:09
*** gordc has quit IRC22:19
*** thinrichs has quit IRC22:24
*** rockyg has joined #openstack-release22:28
*** thinrichs has joined #openstack-release22:51
*** rockyg has quit IRC22:54
*** mriedem has joined #openstack-release22:54
*** thinrichs has quit IRC23:04
*** hongbin has quit IRC23:06
*** sdague has quit IRC23:07
*** sdake has joined #openstack-release23:23
*** thinrichs has joined #openstack-release23:39
dimsstevemar : https://review.openstack.org/#/c/301885/ looks ready23:47
patchbotdims: patch 301885 - releases - release keystone-rc323:47
stevemardims yes sir!23:48
dimsstevemar : want me to cut it?23:49
stevemardims sure, let me just check the changes23:49
dimsack23:49
stevemardims, just the one expected change, lgtm23:50
stevemardims, would be nice to close the chapter on Keystone23:50
dimsstevemar : ok let me cut it now23:51
stevemarkk23:53
*** Qiming has joined #openstack-release23:53
*** sdake_ has joined #openstack-release23:53
*** sdake has quit IRC23:56
openstackgerritMerged openstack/releases: release keystone-rc3  https://review.openstack.org/30188523:57

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