Tuesday, 2016-02-02

*** dims has quit IRC00:10
*** stevebaker has quit IRC00:52
*** stevebaker has joined #openstack-release00:52
*** doug-fish has quit IRC01:10
*** doug-fish has joined #openstack-release01:10
*** doug-fis_ has joined #openstack-release01:12
*** doug-fi__ has joined #openstack-release01:14
*** doug-fish has quit IRC01:14
*** doug-fi__ has quit IRC01:15
*** doug-fish has joined #openstack-release01:16
*** doug-fish has quit IRC01:16
*** doug-fis_ has quit IRC01:16
*** jgriffith is now known as jgriffith_away01:50
*** jgriffith_away is now known as jgriffith01:53
*** jgriffith is now known as jgriffith_away02:04
*** dims has joined #openstack-release02:11
openstackgerritBen Swartzlander proposed openstack/releases: Release python-manilaclient 1.6.1  https://review.openstack.org/27083402:46
*** amotoki has quit IRC03:10
*** jgriffith_away is now known as jgriffith03:26
*** amotoki has joined #openstack-release03:35
*** dims has quit IRC03:53
*** amotoki has quit IRC04:01
*** mriedem has left #openstack-release04:15
*** aukhan has joined #openstack-release04:55
*** amotoki has joined #openstack-release05:05
*** AzherKhan has joined #openstack-release05:44
*** aukhan has quit IRC05:44
*** sileht has quit IRC05:44
*** amotoki_ has joined #openstack-release06:51
*** amotoki has quit IRC07:03
*** sileht_ has joined #openstack-release07:29
*** sileht_ is now known as sileht07:35
*** sileht has quit IRC07:50
*** sileht has joined #openstack-release07:50
*** amotoki_ is now known as amotoki08:03
*** amotoki has quit IRC09:40
*** amotoki has joined #openstack-release09:55
*** amotoki has quit IRC10:10
openstackgerritBoris Pavlovic proposed openstack/releases: WIP: Setup release mechanism for OSprofiler  https://review.openstack.org/27057110:17
*** openstackgerrit has quit IRC10:17
*** openstackgerrit has joined #openstack-release10:17
*** amotoki has joined #openstack-release10:24
*** amotoki_ has joined #openstack-release10:30
*** amotoki has quit IRC10:31
*** AzherKhan has quit IRC10:42
*** amotoki_ has quit IRC10:42
*** amotoki has joined #openstack-release10:45
*** dtantsur|afk is now known as dtantsur10:54
*** dims_ has joined #openstack-release11:02
openstackgerritMerged openstack-infra/release-tools: don't require launchpad milestone for stable branch  https://review.openstack.org/27313311:17
openstackgerritThierry Carrez proposed openstack/releases: import some known EOL dates  https://review.openstack.org/27155811:20
*** amotoki has quit IRC11:30
openstackgerritMerged openstack/releases: rearrange content in preparation to move to new vhost  https://review.openstack.org/27155011:33
*** amotoki has joined #openstack-release12:20
*** bnemec has joined #openstack-release12:26
*** gordc has joined #openstack-release12:35
*** bswartz has quit IRC12:36
*** deva_ has joined #openstack-release12:50
*** deva_ has quit IRC12:58
*** anteaya has joined #openstack-release13:00
*** amotoki has quit IRC13:00
*** anteaya has quit IRC13:06
*** doug-fish has joined #openstack-release13:07
*** bdemers_ has quit IRC13:15
*** amotoki has joined #openstack-release13:16
bauzasdhellmann: heya13:31
bauzasdhellmann: so we had some discussion yesterday in Nova because some CD guys missed that we were adding a new DB even if we provided the relnotes in Kilo and Mitaka13:31
bauzasdhellmann: given that there is a communication problem with that, I was wondering two things13:32
bauzasdhellmann: #1 having http://docs.openstack.org/releasenotes/nova/unreleased.html pointing to the latest git commit13:32
bauzasdhellmann: #2 having a RSS feed for the relnotes13:32
bauzasdhellmann: so I'm about to provide the same kind of patch like yours for https://github.com/openstack/nova-specs/commit/8c0a70ec54c3e4c764fdf34cd0db59fa9c6cd09513:33
bauzasdhellmann: but my 2 points would need some -infra disucssions13:33
bauzasdhellmann: opinions ?13:33
sdaguebauzas: it does seem a little odd that CDing people aren't reading the renos13:34
bauzassdague: yeah, totally agreed13:34
bauzasbut you know...13:34
bauzasit was a yesterday's discussion13:35
sdagueyeh, I saw bits of it this morning13:35
bauzasand we were even joking on that - but some CD guys were thinking it was sarcasm13:35
bauzasso13:35
bauzasgiven all that13:35
bauzasat least having the reno notes being in a frontend looks fine13:36
sdagueyeh, sure, that's fine13:36
bauzasbecause http://docs.openstack.org/releasenotes/nova/unreleased.html is just having the liberty notes13:36
sdaguesure, that is a little odd13:36
bauzasoh wait, what ?13:36
bauzasjust rechecked the site, and now it's mitaka13:36
bauzasmeh13:36
sdagueoh, is that getting stomped back and forth each time a reno lands?13:37
bauzasI dunno13:37
bauzaswe still have a reno bug13:37
bauzashttps://bugs.launchpad.net/reno/+bug/153745113:37
openstackLaunchpad bug 1537451 in reno "notes missing/overridden in latest version" [High,In progress] - Assigned to Doug Hellmann (doug-hellmann)13:38
sdaguegotcha13:38
sdagueyeh, that's a bit odd13:38
bauzasbut it seems that the frontend site is having the latest git commit yeah13:38
sdagueright13:39
bauzasis *now* having the commit, because yesterday evening, it was not the case - unless I was blind13:39
sdagueperhaps basing this on branch is the wrong model. Because I might want to see the running release notes from all versions of openstack13:39
sdagues/openstack/nova/13:40
sdaguewhich is kind of impossible with the current model it seems13:40
bauzaswe only base on branches for the releases13:40
sdaguesure, but we could just not use branch and instead use directory13:40
bauzasthe unreleased.py sphinx call just asks for the git commits without branching13:40
bauzaswell, it mirrors our nova source13:41
bauzasunless I misunderstood your point13:41
sdaguesure, but I pull the git tree13:41
bauzashttps://raw.githubusercontent.com/openstack/nova/master/releasenotes/source/unreleased.rst13:41
sdagueor, sorry, I have a tarball13:41
sdagueI only have access to release notes from this release13:42
bauzascompared to https://raw.githubusercontent.com/openstack/nova/master/releasenotes/source/liberty.rst13:42
sdaguevs. http://eventlet.net/doc/changelog.html13:42
sdaguewhere I can ctrl+F for things that are important to me13:42
bauzasoh I see13:43
bauzaswell, you still can13:43
sdaguewhere? where do I have the whole history of a project in a single page13:43
bauzasmeh no13:43
bauzasyeah you're right13:43
bauzashttp://docs.openstack.org/releasenotes/nova/index.html13:43
bauzasmmm, good point13:43
bauzaswhat I was thinking is to have the same RSS feed like http://specs.openstack.org/openstack/nova-specs/rss.xml13:45
bauzasso operators could use that RSS to see the changes13:45
bauzasbut it could be needing the aggregated file13:45
sdaguesure, that's a thing which would be good as well, but again it should be the whole history, right?13:46
bauzasyeah, sorry if I was unclear13:47
bauzas(14:45:31) bauzas: so operators could use that RSS to see the changes13:47
bauzas(14:45:50) bauzas: but it could be needing the aggregated file13:47
bauzasaggregated file == whole history13:47
*** jgriffith is now known as jgriffith_away13:58
*** tsufiev has joined #openstack-release14:08
tsufievdims_, hi! Indiscreet maintainers continue to attack Horizon's integration tests, here https://review.openstack.org/#/c/275155/ is another workaround fix until we understand problem better/ communicate with maintainer14:10
dims_tsufiev : +214:11
tsufievdims_, thanks!14:11
tsufievis sdague usually around this time of day?14:12
sdaguetsufiev: yes14:13
tsufievsdague, thank you for the quick response! you both are my firefighters team of this month :)14:13
sdagueno prob, happy to help14:14
*** bdemers has joined #openstack-release14:37
*** mriedem has joined #openstack-release14:43
*** sigmavirus24_awa is now known as sigmavirus2415:10
*** bswartz has joined #openstack-release15:20
dims_tsufiev :)15:23
dims_mriedem : need your eye on oslo releases please - https://review.openstack.org/#/c/274719/ https://review.openstack.org/#/c/274719/ and https://review.openstack.org/#/c/274726/15:24
*** amotoki has quit IRC15:24
dims_mriedem : i already -2'ed oslo.config https://review.openstack.org/#/c/274746/15:24
mriedemdims_: 2 of those are the same review15:28
mriedemwere there supposed to be 3?15:28
dims_oops - https://review.openstack.org/#/c/274719/ https://review.openstack.org/#/c/274765/ https://review.openstack.org/#/c/274726/15:29
*** bdemers has quit IRC15:39
*** bdemers has joined #openstack-release15:42
mriedemdims_: man, lots of changes for oslo.messaging15:45
mriedemscares me15:45
dims_mriedem : y i have been holding it back15:45
dims_mriedem : did not want to rock m215:46
mriedemlooks like a zmq stuff, is there a job for oslo.messaging + zeromq?15:46
mriedemyeah i guess there is15:47
mriedemat least on master15:47
dims_mriedem : yep15:47
mriedemnot sure how pep8 passed on this https://review.openstack.org/#/c/262205/2/oslo_messaging/tests/functional/test_functional.py15:48
mriedemdoes pep8 not run on the tests dir in oslo.messaging?15:49
mriedemyup https://github.com/openstack/oslo.messaging/blob/master/tox.ini#L4815:49
mriedemreported a bug for that https://bugs.launchpad.net/oslo.messaging/+bug/154098115:51
openstackLaunchpad bug 1540981 in oslo.messaging "Should run pep8 on oslo_messaging/tests" [Undecided,New]15:51
*** dims has joined #openstack-release15:54
*** dims_ has quit IRC15:54
mriedemdims: so, -1 on https://review.openstack.org/#/c/274765/ just to add highlights, since there were a lot of changes that should porobably be doc'ed15:55
mriedemdims: i'd also urge someone to test trunk oslo.messaging + zmq backend on stable/liberty, but that's just me15:55
dimsmriedem : we did not have this driver in stable/liberty15:55
dimsmriedem : there was no expectation of backward compat in the spec we approved for this new zmq driver15:56
mriedemoh i thought it was in liberty15:56
mriedemif it wasn't, then nevermind on that15:56
mriedemthere are still new config options and behavior changes that should be in highlights IMO15:56
dimsy, we were working on a branch15:56
dimsright, will let oleksii rework that15:57
dhellmannbauzas : an rss feed for release notes makes some sense. You'd need one per branch, because of the way the scanner works.16:00
dhellmannsdague , bauzas : after mitaka, the "unreleased" page scanning the master branch will include mitaka and newton notes, until I update reno to not do that. It won't include point releases from the mitaka series, though.16:01
*** david-lyle has joined #openstack-release16:02
dhellmannsdague , bauzas : that said, we can have a page that has multiple directives to scan different series and they can all be on the same page16:02
dimsdhellmann : mriedem : i'll get oslo.context and oslo.concurrency releases out now https://review.openstack.org/#/c/274719/ and https://review.openstack.org/#/c/274726/16:03
openstackgerritMerged openstack/releases: oslo.context 2.0.0  https://review.openstack.org/27471916:05
openstackgerritMerged openstack/releases: oslo.concurrency 3.4.0  https://review.openstack.org/27472616:06
dhellmanndims : ack16:06
bauzasdhellmann: yeah, I was thinking of providing a changelog.rst with all the release calls16:12
bauzasuntil reno was supporting some RSS feeds16:12
bauzasdhellmann: I tried to use yasfb but the outcome was just one item for each release with the HTML description for all the notes in the description16:13
dhellmannbauzas : yeah, that's a very-specific feed builder, one entry per page16:18
bauzasI see16:18
dhellmannbauzas : we could add rss generation to reno, and then add that step to the doc build separately or with sphinx integration16:18
bauzasyeah, it could be nice16:19
bauzasI can see reno reporting16:19
dhellmannbauzas : there's already a report command, so we could add a format option or a separate rss command16:19
bauzasexactly what I thought16:19
dhellmanncool, sounds good. do you want to throw together an etherpad with some notes about the plan?16:19
dhellmannlike if we need to roll out changes to the sphinx config in projects, we would need to know that, etc.16:20
bauzasdhellmann: well, I can play the Product Manager, but not really sure I have time for working on it :)16:20
bauzasbut I dunno16:20
*** fesp has joined #openstack-release16:29
openstackgerritBen Swartzlander proposed openstack/releases: Release manila-ui 1.3.0  https://review.openstack.org/27531016:29
mriedemdims: thanks, can you close out bug 1540981 with that?16:37
openstackbug 1540981 in oslo.messaging "Should run pep8 on oslo_messaging/tests" [Undecided,New] https://launchpad.net/bugs/154098116:37
dimsmriedem : ah i didn't see :)16:37
*** fesp has quit IRC16:42
*** dims_ has joined #openstack-release16:47
*** dims has quit IRC16:49
*** bnemec has quit IRC16:53
*** fesp has joined #openstack-release17:11
*** fesp has quit IRC17:12
*** dtantsur is now known as dtantsur|afk17:13
*** openstackgerrit has quit IRC17:32
*** openstackgerrit has joined #openstack-release17:32
*** sigmavirus24 is now known as sigmavirus24_awa18:03
*** anteaya has joined #openstack-release18:15
openstackgerritgordon chung proposed openstack/releases: ceilometerclient 1.5.2 - liberty  https://review.openstack.org/27536718:32
*** rhochmuth has joined #openstack-release19:07
*** coreycb` has joined #openstack-release19:11
*** bswartz has quit IRC19:12
*** mordred has quit IRC19:12
*** coreycb has quit IRC19:12
*** thingee has quit IRC19:12
*** mordred has joined #openstack-release19:16
*** thingee has joined #openstack-release19:26
*** bswartz has joined #openstack-release19:30
*** deva_ has joined #openstack-release19:31
*** rhochmuth has quit IRC19:34
*** deva_ has quit IRC19:36
*** rhochmuth has joined #openstack-release19:38
rhochmuthdhellmann: So, I meant to check back with you on https://review.openstack.org/#/c/274884/ and https://review.openstack.org/#/c/274898/19:40
rhochmuthIt looks like things are in good shape now, but I still have that doubt that I actually got it right19:41
rhochmuthI also assumed that I would be able to bump the verions and hashes in https://review.openstack.org/#/c/274898/, when Mitaka gets locked down19:42
*** jgriffith_away is now known as jgriffith20:21
*** mriedem is now known as mriedem_machell20:53
*** jgriffith is now known as jgriffith_away20:56
dhellmannrhochmuth : looking now...21:08
dhellmannrhochmuth : to add new releases, you would extend those files (don't replace the existing values). That way we have the complete history for the deliverables.21:10
rhochmuthok21:11
openstackgerritMerged openstack/releases: Adding Monasca deliverables for Mitaka release  https://review.openstack.org/27489821:12
rhochmuthi just selected the latest top of master branch to add to the deliverabls21:12
rhochmuthwhich should be in good shape21:12
*** Guest40848 has joined #openstack-release21:23
openstackgerritBoris Pavlovic proposed openstack/releases: Setup release mechanism for OSprofiler  https://review.openstack.org/27057121:29
dims_dhellmann : i can pick up https://review.openstack.org/#/c/270571/ when the ci finishes21:34
openstackgerritMerged openstack/releases: Setup release mechanism for OSprofiler  https://review.openstack.org/27057121:50
dims_duh! osprofiler permissions are wrong21:53
dhellmanndims_ : revert the patch?22:03
dims_dhellmann : got the permissions fixed. now ran into a failure in upload - https://jenkins.openstack.org/job/osprofiler-pypi-both-upload/3/console22:03
dhellmanndims_ : so now we have a tag, but the release failed?22:04
*** bdemers has quit IRC22:04
dims_dhellmann : y22:04
dhellmannok. I guess I need to figure out how to automate that check.22:04
dhellmannwe'll have to get boris-42 to fix the permissions, and then ask infra to run the release job again22:04
dims_dhellmann : he added oslo-release already to osprofiler-release group22:05
dims_dhellmann : now it's a upload failure - http://logs.openstack.org/7a/7a428885ddb138f3d3a388e72bca276cfa2a5299/release/osprofiler-pypi-both-upload/5c2c80a/console.html#_2016-02-02_22_01_26_31322:05
dhellmanndims_ : he has to do something on pypi22:05
*** rhochmuth has quit IRC22:05
dhellmannoh, wait, 500 error22:05
dhellmannthat's not a permission issue22:05
dhellmannI thought you meant we didn't have permission to upload the wheels22:06
dims_sorry, my bad :)22:06
dhellmannnah, I should have looked at the log22:06
dhellmannmaybe infra can just re-run the job22:06
dims_y, let me ask fungi22:07
fungiyou just did22:07
fungi(ask me, i mean)22:07
funginow looking to see what you asked ;)22:07
dims_haha :)22:07
dims_thanks fungi22:07
fungiyes, for some reason the fastly cdn fronting pypi.python.org sometimes returns a 500 isr _after_ the apparent successful upload of a wheel, so our script thinks the upload failed (and then short-circuits the job and doesn't go on to upload the tarball)22:09
dhellmannhmm22:09
fungiif the wheel uploaded then it's just a matter of me manually reuploading the tarball22:09
fungiunfortunately we can't retrigger the job in those situations, because it will want to upload the wheel again, and pypi will reject it if it's already there22:10
fungiyep, wheel is there with today's date, so i'll upload the tarball22:11
dims_thanks fungi !22:12
fungidone22:14
fungilooks like the sdist is there on pypi now22:15
dims_awesome!22:15
fungithat's the sdist which was built by the tarball job (luckily the upload to pypi step is a separate job)22:15
dhellmannfungi : thanks!22:16
fungiyw22:16
dims_dhellmann : we need a way for the job to tell us that it failed...instead of us watching it22:17
dhellmanndims_ : yeah, maybe we can have it post the results here in channel?22:19
dims_dhellmann : would be a great start22:19
dhellmannfungi : are there any facilities for posting from jobs to irc? I can't remember how the review bot works, if that's part of a job or not.22:20
dims_dhellmann : fungi : i remember when console logs are not available i see some bot messages somewhere22:23
fungithe bot watches the gerrit event stream, unfortunately post job results are not reported into gerrit22:23
fungioh, those messages are a different bot22:23
dims_fungi : ah22:23
fungiyou're thinking of the elastic-recheck bot22:23
fungiit's also watching the gerrit event stream though22:23
fungian "irc reporter" for zuul might be an interesting feature. suggest it to jeblair (might be pretty easy to add after zuul v3)22:24
dims_fungi : ack will do22:25
fungiafaik the current focus on reporting for jobs that run in the post-merge and tag-based pipelines is a dashboard of some sort22:25
fungiwhich would also serve as a frontend to the log archives22:26
dhellmanna dashboard would be great, I thought irc might be a simple solution for now22:27
*** gordc has quit IRC23:33

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