Wednesday, 2016-05-04

*** amrith is now known as _amrith_00:09
*** _amrith_ is now known as amrith00:24
*** amrith is now known as _amrith_00:59
*** armax_ has joined #openstack-release01:11
*** armax has quit IRC01:12
*** armax_ is now known as armax01:12
*** sdake has quit IRC01:13
*** armax has quit IRC01:14
*** armax has joined #openstack-release01:26
*** cody-somerville has joined #openstack-release02:43
*** mriedem has quit IRC02:47
*** dave-mccowan has quit IRC03:10
*** cody-somerville has quit IRC03:39
*** bnemec has quit IRC05:17
*** kzaitsev_mb has joined #openstack-release05:31
*** kzaitsev_mb has quit IRC06:04
*** david-lyle has quit IRC06:05
*** kzaitsev_mb has joined #openstack-release06:09
*** openstackgerrit has quit IRC06:17
*** openstackgerrit has joined #openstack-release06:18
*** kzaitsev_mb has quit IRC06:29
openstackgerritIhar Hrachyshka proposed openstack/releases: Release networking-odl 2.0.0 (mitaka) release  https://review.openstack.org/31233106:33
*** shardy has joined #openstack-release07:56
*** kzaitsev_mb has joined #openstack-release07:58
*** sdague has joined #openstack-release09:33
*** daemontool has joined #openstack-release09:35
*** flwang has quit IRC09:54
*** _amrith_ is now known as amrith10:08
*** flwang has joined #openstack-release10:08
openstackgerritDaniel Berrange proposed openstack/releases: Release os-vif 1.0.0  https://review.openstack.org/31242610:16
*** dave-mccowan has joined #openstack-release10:51
*** david-lyle has joined #openstack-release10:58
*** daemontool has quit IRC11:27
openstackgerritamrith proposed openstack/releases: Entered Trove release schedule information  https://review.openstack.org/31112311:31
*** rhallisey has joined #openstack-release11:40
*** amrith is now known as _amrith_11:42
openstackgerritDmitry Tantsur proposed openstack/releases: Release ironic-inspector 2.2.6 for Liberty  https://review.openstack.org/30884511:59
*** dave-mcc_ has joined #openstack-release12:24
*** doug-fish has joined #openstack-release12:27
*** dave-mccowan has quit IRC12:27
*** _amrith_ is now known as amrith12:57
*** krotscheck_dcm is now known as krotscheck13:10
*** mriedem has joined #openstack-release13:16
*** armax has quit IRC13:19
*** armax has joined #openstack-release13:20
*** inc0 has joined #openstack-release13:31
*** sdake has joined #openstack-release13:48
*** sdake has quit IRC13:48
*** sigmavirus24_awa is now known as sigmavirus2413:56
*** dave-mcc_ has quit IRC13:57
*** sdake has joined #openstack-release14:06
*** mugsie has joined #openstack-release14:07
*** gordc has joined #openstack-release14:09
*** hongbin has joined #openstack-release14:11
kzaitsev_mbdoes anyone know who runs data for this page http://www.openstack.org/software/project-navigator ?14:18
mugsiekzaitsev_mb: the foundation14:18
*** daemontool has joined #openstack-release14:19
kzaitsev_mboh, I got answered in #infra — they say, that the best way to communicate with the folks, who run it is through https://bugs.launchpad.net/openstack-org14:20
kzaitsev_mbthanks )14:20
dimskzaitsev_mb : it pulls data from the public repos, what was your concern?14:21
*** bnemec has joined #openstack-release14:21
kzaitsev_mbdims: I'm mostly concerned with murano =) and well, at the very least it's wrong about murano not having stable branches =)14:25
kzaitsev_mbalso it lists liberty as the latest release for all the projects14:25
dimskzaitsev_mb : did you check governance repo for murano?14:25
dimskzaitsev_mb : need to fix governance repo first14:26
kzaitsev_mbI believe, that the tag was changed to 'stable:follows-policy', wasn't it?14:27
dimskzaitsev_mb : http://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml#n230714:27
kzaitsev_mbnone of the projects is marked as having stable branches right now as far as I can see14:28
dimskzaitsev_mb : nova has that tag - https://governance.openstack.org/reference/tags/stable_follows-policy.html14:29
dimsso let's refresh the data in governance first14:29
kzaitsev_mbdims: yet the site says it doesn't http://www.openstack.org/software/releases/liberty/components/nova14:30
dimskzaitsev_mb : y, we should update our data first and then tell them to refresh14:31
*** armax has quit IRC15:17
*** armax has joined #openstack-release15:27
*** armax has quit IRC15:38
*** armax has joined #openstack-release15:38
*** sdake_ has joined #openstack-release15:40
*** sdake has quit IRC15:43
*** sdake_ has quit IRC15:46
*** kzaitsev_mb has quit IRC15:58
*** kzaitsev_mb has joined #openstack-release15:59
*** amotoki has joined #openstack-release16:02
*** dtantsur is now known as dtantsur|afk16:17
*** sdake has joined #openstack-release16:24
*** daemontool_ has joined #openstack-release16:27
*** daemontool_ has quit IRC16:28
*** daemontool has quit IRC16:28
*** daemontool has joined #openstack-release16:29
*** flwang has quit IRC16:39
*** sridhar_ram has joined #openstack-release16:43
*** kzaitsev_mb has quit IRC16:45
*** kzaitsev_mb has joined #openstack-release16:47
*** electrofelix has joined #openstack-release16:49
*** sdake has quit IRC16:55
*** AJaeger has joined #openstack-release16:58
AJaegerdims, dhellmann: Sorry, I broke requirements testing - could you fast-approve  https://review.openstack.org/312635, please? Not sure how my manual testing could have missed that ;(16:59
*** flwang has joined #openstack-release16:59
dhellmannAJaeger : +2a16:59
dhellmannthanks for finding the fix so quickly17:00
AJaegerdhellmann: I just run recheck on 311761 which is ready to land - and noticed the failure ;(17:00
AJaegerdhellmann: thanks!17:00
*** kzaitsev_mb has quit IRC17:12
openstackgerritBen Nemec proposed openstack/releases: tripleo-puppet-elements 3.0.0  https://review.openstack.org/30855517:15
openstackgerritBen Nemec proposed openstack/releases: Add tripleo-puppet-elements deliverable  https://review.openstack.org/30855417:15
dimsAJaeger : oops looks like dhellmann already approved.17:19
*** dave-mccowan has joined #openstack-release17:22
AJaegerdims: yes, thanks17:26
*** spzala has joined #openstack-release17:32
*** inc0 has quit IRC17:33
*** electrofelix has quit IRC17:36
*** mriedem has quit IRC17:52
*** mriedem has joined #openstack-release17:54
sridhar_ramdhellmann: release-team: folks from tacker and tosca-parser / heat-translator project are here.. to get some dependency question clarified ...17:57
dhellmannsridhar_ram : hi17:58
sridhar_ramspzala: bobh: ^^17:58
spzaladhellmann: Hi17:58
dhellmannhow can I help?17:58
sridhar_ramspzala: releases two libraries ... tosca-parser and heat-translator that tacker team consumes...17:59
sridhar_ramdhellmann: heat-translator has a dependency on tosca-parser17:59
dhellmannok18:00
spzalaso in global-req there is tosca-parser>=0.4.0 and heat-translator>=0.4.0 for now, for Tacker team can they enforce req in their project to a specific release?18:00
sridhar_ramdhellmann: however tacker project needs these two libraries to be available at the sametime to (a) no break any existing feature (b) start consuming new features in these libs18:00
spzalawe just had tosca-parser 0.5.0 released today, can Tacker still stay with 0.4.0 ?18:00
dhellmannspzala : no, we do not want projects to "pin" to a specific version of a dependency because that makes upgrades hard or impossible18:01
dhellmannspzala : Tacker can keep a requirement that says >=0.4.0 as long as they are not using any features in 0.5.0 and the global requirements list isn't updated18:01
dhellmannsridhar_ram : I'm not sure I understand that. You mean that you want to upgrade both libraries at the same time, or not at all?18:02
spzaladhellmann: OK, but that will automatically push Tacker to use 0.5.0 right? i.e. whatever is the latest release18:02
sridhar_ramdhellmann: yes, if we upgrade tosca-parser to 0.5.0 and heat-translator still stays in 0.4.0 .. that is out of sync and we are worried heat-translator might fail18:02
dhellmannsridhar_ram : if these libraries are maintaining backwards-compatibility through testing, you shouldn't have any problem. If there are no such tests, then they should be added.18:03
spzaladhellmann: well, we are not supporting backward compatibility for now :( but yes, agree with you18:04
sridhar_ramdhellmann: I see18:04
dhellmannspzala : if tacker follows the global requirements list and uses constraints, then the version in the constraints file will be used. Otherwise, yes, the most current version will be used18:04
spzaladhellmann: if that's the best way then I would keep it in mind going forward18:04
dhellmannspzala : ok, you should probably start handling backwards compatibility testing if you want folks to use what you're producing18:04
dhellmannif you've broken compatibility and that has broken tacker, then we can exclude the most current release, you can revert those changes, and then you can prepare another release with the new features added in a compatible way18:05
dhellmannor, tacker could decide not to use the libraries, I guess18:05
spzaladhellmann: Yup, agree. That was clear to me ever since we started to release, but since we are on point releases and iteratively releasing at shorter interval we thought it's ok not to worry about backward-compatibility for sometime18:05
spzaladhellmann: no I don't think it's needed at this moment18:06
dhellmannspzala : technically, yes, using versions < 1.0 allow breaks, although it seems you have a user who cares about that now :-)18:06
sridhar_ramdhellmann: spzala: that sounds little tricky to me.... heat-translator 0.4.0 is expected to work with a DOM object tree returned by tosca-parser 0.5.0 ?18:07
spzaladhellmann: we are already on track to have heat-translator release that will fix the issue, something I plan to release by tomorrow. sridhar_ram: hope that's fine at this point.18:07
dhellmannspzala : how are you using these libraries internally if the APIs are breaking?18:07
spzaladhellmann: :-) Yes, agree.18:07
spzaladhellman: so we update master (i.e. master for heat-translator) right away after pypi of tosca-parser18:08
spzalawith needed fix for sync18:08
spzalaand that way keep master usable18:08
sridhar_ramdhellmann: I'd like to explore excluding the version temporarily .. under the the second library is the two-pack gets released18:08
dhellmannok. that's not really optimal. if you have anyone deploying from master, you're breaking their production system every time you do that.18:09
spzalasridhar_ram: no,  heat-translator 0.4.0 is not expected to work with 0.5.0 of tosca-parser but ideally as I thought initially and as dhellmann said with backward-compatibility that's should be the case18:09
spzaladhellmann: yes, agree18:10
sridhar_ramspzala: sure, meanwhile.. can we work out a plan to have both tosca-parser and heat-translator to upversion at the same time.. by that..18:10
spzaladhellmann: so going forward we will keep backward-compatibility in mind, this's the right time to do that18:10
sridhar_ramspzala: .. after tosca-parser is release, use exclusion in the global-requirement until a new heat-translator gets pushed ?18:11
dhellmannsridhar_ram : there is no way to guarantee that the libraries are released at the same time. they are built via different jobs that run in parallel.18:11
sridhar_ramdhellmann: wondering whether we can manage it by using exclusions ?18:11
dhellmannand no, we won't be adding to the global requirements list review burden by excluding a release of one every time, either, that's just not something the community can support18:11
spzalasridhar_ram: yes, so that's why I am going to have heat-translator 0.5. soon out as possible with one fix that is needed and update to requirements18:11
spzalasridhar_ram: for the inconvenience for now until heat-translator is out, unless we break backward-compatibility in future there shouldn't be such problem going forward18:12
sridhar_ramspzala: I'm fine for this round .. but the concern I've is.. if this happens in the tail end of Newton during crunch item that would be major pain18:13
dhellmannwe can, this time, exclude the broken version of whichever library is causing the problem. that version will then not ever be allowed to be used. so you will need to produce a new version of the library that is not broken, and start using that.18:13
dhellmannwe cannot do that every time you prepare a release, it's just not reasonable to ask everyone else in the community to take on that work when you could solve the problem by not releasing libraries you know will break things.18:13
spzalasridhar_ram: yes, but with backward-compability in mind It should not be a problem in future18:14
sridhar_ramdhellmann: fair enough18:14
spzaladhellmann: I guess we are fine18:14
spzalasridhar_ram: for time being, you can wait for heat-translator 0.5.0 right?18:14
sridhar_ramspzala: yeah, looks striving for backward compatibility is the way to go..18:14
dhellmannso I recommend gating the libraries on the projects that use them, to ensure that no changes to master of the library break the projects18:14
spzalaas I mentioned on our earlier talk, tosca-parser 0.5 is not breaking heat-translator out of box, but failing few templates18:15
sridhar_ramspzala: I thing we are fine, bobh can you please confirm ?18:15
dhellmannI don't see bobh in this channel18:15
spzaladhellmann: sure, will keep the recommendation in mind :)18:16
sridhar_ramdhellmann: just poked' bobh.. I think we are fine this round18:16
sridhar_ramspzala: thanks for working out to push out a heat-translator release quickly18:17
spzalasridhar_ram: dhellmann: cool, thanks!!18:17
sridhar_ramdhellmann: thanks...18:17
openstackgerritBen Nemec proposed openstack/releases: Add tripleo-puppet-elements deliverable  https://review.openstack.org/30855418:17
spzalasridhar_ram: :) np at all18:17
sridhar_ramdhellmann: btw, learnt something new here... so exclusion are only for bad / buggy library releases and they need to be permanently skipped ?18:19
*** bobh has joined #openstack-release18:19
spzaladhellmann: thanks again. By end of Newton release, once we are stable with development (which we are pretty much), the plan is to use OpenStack release manager for our releases, something I will be getting in touch with you.18:22
*** inc0 has joined #openstack-release18:26
*** kzaitsev_mb has joined #openstack-release18:27
dhellmannsridhar_ram : yes, we don't want to toggle exclusions on and off frequently18:28
dhellmannspzala : sounds good, let me know when you're ready to talk about that18:29
spzaladhellmann: sure, absolutely18:31
*** shardy has quit IRC18:34
*** hongbin has quit IRC18:38
*** sdake has joined #openstack-release18:42
*** hongbin has joined #openstack-release18:43
*** sdake has quit IRC18:44
*** sdake has joined #openstack-release18:46
*** AJaeger has left #openstack-release19:04
*** rockyg has joined #openstack-release19:10
*** bdemers has joined #openstack-release19:14
*** sdake has quit IRC19:25
*** sdake has joined #openstack-release19:26
*** bdemers_ has joined #openstack-release19:35
*** bdemers has quit IRC19:37
*** bdemers has joined #openstack-release19:37
*** bdemers_ has quit IRC19:39
*** TravT has quit IRC19:42
*** kzaitsev_mb has quit IRC19:45
*** TravT has joined #openstack-release19:45
*** openstackgerrit has quit IRC19:48
*** openstackgerrit has joined #openstack-release19:48
*** bdemers_ has joined #openstack-release20:00
*** bdemers has quit IRC20:04
*** sdague has quit IRC20:07
*** harlowja has quit IRC20:09
*** sdague has joined #openstack-release20:14
*** amrith is now known as _amrith_20:28
*** bdemers has joined #openstack-release20:37
*** bdemers_ has quit IRC20:40
*** doug-fis_ has joined #openstack-release20:48
*** _amrith_ is now known as amrith20:48
prometheanfiredhellmann: you gonna send that email about requirements out?20:49
dhellmannprometheanfire : can you be more specific? I have a list of like 50 emails I'm supposed to be sending this week...20:49
dhellmann:-)20:49
dhellmannlooking for requirements reviewers?20:49
*** doug-fish has quit IRC20:50
prometheanfireya20:50
prometheanfirethat one :P20:50
dhellmannyeah, I'll bump that up the ol priority list20:50
prometheanfireit's fine as is, was just curious20:51
dhellmannI did mention it in the summit session wrap up email, but that was sort of long and covered several topics20:51
prometheanfireya, I did read that20:51
*** doug-fish has joined #openstack-release20:51
prometheanfireI have started doing some reviews, so hope that's helping20:51
dhellmannmaybe I should follow up to the older thread about that requirements session separately20:51
dimsdhellmann : i can literally picture you say this if i close my eyes - "If20:51
dimsthere's a project that wants to join, we should talk about that project20:51
dimsand whether it meets *all* of our criteria, not just what language it's20:51
dimsin" :)20:51
prometheanfirelol20:52
dims++ for bringing that up20:52
prometheanfireya, the go stuff, ugh20:52
dhellmanndims : yeah, it's easy to go off in the weeds on hypothetical cases :-/20:52
*** doug-fi__ has joined #openstack-release20:52
*** doug-fis_ has quit IRC20:52
dimsyep indeed. i have something brewing which may test that case. so shot off pointers to folks involved :)20:53
*** doug-fish has quit IRC20:55
*** doug-fi__ has quit IRC20:57
*** rhallisey has quit IRC20:59
*** harlowja has joined #openstack-release21:10
*** bobh has quit IRC21:28
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: change email topic tags based on summit feedback  https://review.openstack.org/31276221:38
*** inc0 has quit IRC21:40
*** amrith is now known as _amrith_21:47
*** inc0 has joined #openstack-release21:47
*** mriedem has quit IRC21:50
*** bauzas is now known as bauzas_off21:50
*** sdague has quit IRC21:51
*** rockyg has quit IRC21:56
*** bdemers has quit IRC21:58
*** bdemers_ has joined #openstack-release21:58
*** AJaeger has joined #openstack-release22:03
AJaegerdims, dhellmann: Once it has passed the testsuite, the Babel update for requirements is fine to merge IMHO: https://review.openstack.org/#/c/311761/ - it will help us moving forward...22:03
patchbotAJaeger: patch 311761 - requirements - Require Babel>=2.3.422:03
*** rockyg has joined #openstack-release22:04
*** gordc has quit IRC22:20
*** sigmavirus24 is now known as sigmavirus24_awa22:21
*** inc0 has quit IRC22:28
*** gordc has joined #openstack-release22:50
*** harlowja has quit IRC22:52
*** harlowja has joined #openstack-release22:53
*** _amrith_ is now known as amrith23:00
*** hongbin has quit IRC23:19
*** gordc has quit IRC23:20
*** sdake has quit IRC23:37
*** sridhar_ram has quit IRC23:47
*** bobh has joined #openstack-release23:47

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