Friday, 2016-04-22

*** armax has joined #openstack-release00:07
*** sdague has quit IRC00:44
*** sdake has quit IRC01:20
*** TravT has joined #openstack-release01:47
*** TravT has quit IRC01:48
*** TravT_ has joined #openstack-release01:48
*** nikhil has quit IRC01:49
*** TravT_ has quit IRC01:49
*** nikhil has joined #openstack-release01:49
*** TravT has joined #openstack-release01:50
*** TravT has quit IRC01:51
*** TravT_ has joined #openstack-release01:51
*** TravT has joined #openstack-release01:54
*** TravT_ has quit IRC01:55
*** TravT has quit IRC01:56
*** TravT_ has joined #openstack-release01:56
*** TravT_ has quit IRC01:57
*** TravT has joined #openstack-release01:57
*** TravT has quit IRC01:58
*** TravT has joined #openstack-release02:13
*** sdake has joined #openstack-release02:16
*** amotoki has joined #openstack-release02:18
*** TravT has quit IRC02:18
*** sdake has quit IRC02:20
*** sdake has joined #openstack-release02:20
*** TravT has joined #openstack-release02:22
*** amotoki has quit IRC02:23
*** sdake_ has joined #openstack-release02:26
*** TravT has quit IRC02:28
*** mriedem has quit IRC02:28
*** TravT has joined #openstack-release02:29
*** sdake has quit IRC02:29
*** amrith is now known as _amrith_02:30
*** TravT has quit IRC02:34
*** TravT has joined #openstack-release02:38
*** amotoki has joined #openstack-release02:39
*** TravT has quit IRC02:43
*** amotoki has quit IRC02:50
*** TravT has joined #openstack-release02:52
*** TravT has quit IRC02:56
*** TravT has joined #openstack-release02:57
*** amotoki has joined #openstack-release02:58
*** TravT_ has joined #openstack-release03:01
*** TravT has quit IRC03:02
*** TravT has joined #openstack-release03:06
*** TravT_ has quit IRC03:06
*** TravT has quit IRC03:11
*** TravT has joined #openstack-release03:11
*** TravT has quit IRC03:15
*** TravT has joined #openstack-release03:16
*** amotoki has quit IRC03:18
*** TravT has quit IRC03:20
*** TravT has joined #openstack-release03:20
*** TravT has quit IRC03:25
*** TravT has joined #openstack-release03:25
*** morgan has quit IRC03:28
*** TravT has quit IRC03:30
*** TravT has joined #openstack-release03:30
*** TravT has quit IRC03:34
*** TravT has joined #openstack-release03:34
*** TravT has quit IRC03:41
*** TravT_ has joined #openstack-release03:42
*** amotoki has joined #openstack-release03:42
*** kzaitsev_mb has joined #openstack-release03:45
*** TravT_ has quit IRC03:46
*** TravT has joined #openstack-release03:46
*** TravT has quit IRC03:51
*** TravT has joined #openstack-release03:51
*** amotoki has quit IRC03:53
*** amotoki has joined #openstack-release03:53
*** dtantsur|afk has quit IRC03:59
*** dtantsur has joined #openstack-release04:03
*** yushiro has joined #openstack-release04:12
yushiroHi, good evening.  I have a question about release process and stable branch.04:14
yushiroCurrently, I'm managing 'networking-fujitsu' repository.04:17
yushiro2 days ago, our repository has changed 'not official'. https://review.openstack.org/#/c/303026/3/reference/projects.yaml04:18
patchbotyushiro: patch 303026 - governance - Update reference list for Neutron projects (MERGED)04:18
yushiroIn this situation, I'd like to create new branch named 'stable/mitaka' but I don't know how to create it.04:21
yushiroI've read this https://github.com/openstack/releases/blob/master/README.rst  but maybe this is for 'official project'.04:22
amotokiyushiro: have you read http://docs.openstack.org/infra/manual/drivers.html04:23
amotokiparticularly release management section04:23
amotokiif you have the appropriate right, you can push a stable branch and push signed tags for releases.04:24
yushiroamotoki, Thanks. I don't read it. I'll read it.04:26
yushiroamotoki, However, I don't have an authority(+2, -2) for refs/heads/stable/*04:29
*** kzaitsev_mb has quit IRC04:30
amotokiyushiro: i think you need to wait for a while until https://review.openstack.org/#/c/303039 is merged.04:31
amotokiyushiro: and each team is set up properly with initial members.04:31
yushiroamotoki, Ah, I see. after this patch is merged, we'll be able to do about it.04:33
*** kzaitsev_mb has joined #openstack-release04:35
yushiroamotoki, Thanks for your kindness !!04:35
yushiro:) :)04:38
*** kzaitsev_mb has quit IRC04:41
yushirosee you.04:45
*** yushiro has left #openstack-release04:45
*** yushiro has quit IRC04:45
*** dave-mccowan has quit IRC04:51
*** dtantsur has quit IRC05:18
*** dtantsur has joined #openstack-release05:36
*** dtantsur has quit IRC06:04
*** sdake_ is now known as sdake06:08
*** dtantsur has joined #openstack-release06:08
*** ianw has quit IRC06:10
*** david-lyle has quit IRC06:16
*** amotoki has quit IRC06:22
*** amotoki has joined #openstack-release06:28
*** sdake has quit IRC06:35
*** sdake has joined #openstack-release06:42
*** sdake has quit IRC06:46
*** cody-somerville has quit IRC07:01
*** matrohon has joined #openstack-release07:21
*** ianw has joined #openstack-release07:24
*** amotoki has quit IRC07:24
*** bauzas is now known as bauwser07:26
-openstackstatus- NOTICE: Logs are failing to be uploaded causing jobs to be marked as UNSTABLE. We are working on repairing the log filesystem and will update when ready. Please do not recheck before then.07:30
*** ChanServ changes topic to "Logs are failing to be uploaded causing jobs to be marked as UNSTABLE. We are working on repairing the log filesystem and will update when ready. Please do not recheck before then."07:30
*** shardy has joined #openstack-release07:55
*** amotoki has joined #openstack-release08:02
*** amotoki has quit IRC08:57
*** amotoki has joined #openstack-release08:58
openstackgerritIhar Hrachyshka proposed openstack/releases: release networking-ofagent 2015.1.6 (kilo)  https://review.openstack.org/30895509:13
*** openstackstatus has quit IRC09:24
*** openstackstatus has joined #openstack-release09:26
*** ChanServ sets mode: +v openstackstatus09:26
openstackgerritIhar Hrachyshka proposed openstack/releases: release networking-bgpvpn 3.0.1  https://review.openstack.org/30896209:26
*** david-lyle has joined #openstack-release09:28
*** amotoki has quit IRC09:28
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/releases: Release OpenStack-Ansible Mitaka/13.0.1  https://review.openstack.org/30931709:33
odyssey4medims ttx dhellmann My apologies for requesting a release today - unfortunately due to the OpenStack-CI issues earlier this week our final Mitaka patches only got to merge early this morning. I would appreciate it if you could process https://review.openstack.org/309317 today asap.09:35
odyssey4medims_ ^09:35
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/releases: Release OpenStack-Ansible Liberty/12.0.11  https://review.openstack.org/30932309:47
openstackgerritJesse Pretorius (odyssey4me) proposed openstack/releases: Release OpenStack-Ansible Kilo/11.2.14  https://review.openstack.org/30932409:47
*** shardy has quit IRC09:54
*** ianw has quit IRC09:58
*** v12aml has quit IRC09:59
*** v12aml has joined #openstack-release10:05
*** krotscheck_dcm is now known as krotscheck10:19
*** amotoki has joined #openstack-release10:22
*** ianw has joined #openstack-release10:31
*** _amrith_ is now known as amrith10:32
dims_odyssey4me : are there some critical problems the .1 is addressing?10:35
*** sdague has joined #openstack-release10:42
*** amotoki has quit IRC10:47
-openstackstatus- NOTICE: Log server has been repaired and jobs are stable again. If necessary please recheck changes that have 'UNSTABLE' results.10:53
*** rhallisey has joined #openstack-release11:01
odyssey4medims_ yeah, as we were stuck on the independent tag were had to release 13.0.0 on OpenStack RC1 SHA's. 13.0.1 is our actual Mitaka release.11:07
odyssey4me13.0.0 is a bit broken, and we're having to field questions around the broken bits that are fixed in 13.0.111:08
odyssey4meI would have done the request sooner, but the CI system was quite broken most of the week, so merges took awfully long11:09
*** sdague has quit IRC11:11
*** sdague has joined #openstack-release11:13
*** amotoki has joined #openstack-release11:13
*** ianw has quit IRC11:18
*** amotoki has quit IRC11:20
*** gordc has joined #openstack-release11:28
*** TravT_ has joined #openstack-release11:50
*** TravT has quit IRC11:51
*** ianw has joined #openstack-release11:52
*** dave-mccowan has joined #openstack-release12:01
*** flwang has quit IRC12:07
*** kzaitsev_mb has joined #openstack-release12:13
*** kzaitsev_mb has quit IRC12:20
dims_odyssey4me : ack. sounds serious. will wait a bit to see if dhellmann/ttx weighs in. otherwise will cut it later today12:21
odyssey4methanks dims_ - I appreciate that we all need a break and that the timing is unfortunate. Hopefully we can make it go regardless.12:21
*** kzaitsev_mb has joined #openstack-release12:26
*** Kiall has quit IRC12:28
dims_odyssey4me : ack no worries12:28
*** Kiall has joined #openstack-release12:28
dims_odyssey4me : safe travels. see you in austin12:28
*** amrith is now known as _amrith_12:33
*** kzaitsev_mb has quit IRC12:34
*** inc0 has joined #openstack-release12:35
*** flwang has joined #openstack-release12:35
mordreddhellmann: with reno, is there any ability to include historical data? for instance, jim asked me to migrate the info from the NEWS file to reno in my patch to add it to zuul: https://review.openstack.org/#/c/262597/12:37
patchbotmordred: patch 262597 - openstack-infra/zuul - Use reno for release notes12:37
mordreddhellmann: of course, without rewriting git history that would be hard12:37
*** doug-fish has joined #openstack-release12:41
*** doug-fish has quit IRC13:12
*** doug-fish has joined #openstack-release13:13
*** matrohon has quit IRC13:14
dhellmannmordred : there is no facility for that in reno itself. we had projects that wanted to import their history just put it in the rst files directly so it would be published online. dunno if that helps in this case?13:25
*** _amrith_ is now known as amrith13:29
mordreddhellmann: OH - like in the ... yeah. duh. that makes total sense13:35
*** nikhil_ has joined #openstack-release13:40
*** nikhil_ is now known as Guest501513:40
*** Guest5015 is now known as nikhil_k13:40
openstackgerritIhar Hrachyshka proposed openstack/releases: new_release: use sha from corresponding stable branches  https://review.openstack.org/29670113:41
*** cody-somerville has joined #openstack-release13:44
*** cody-somerville has quit IRC13:44
*** cody-somerville has joined #openstack-release13:44
*** dansmith is now known as superdan13:48
*** mriedem has joined #openstack-release13:50
odyssey4medhellmann will it be possible to process https://review.openstack.org/309317 today? as discussed with dims_ earlier, we apologise for the timing but it is rather urgent13:58
*** mriedem has quit IRC14:00
*** mriedem has joined #openstack-release14:01
dhellmannodyssey4me : I can do that now.14:01
odyssey4medhellmann thank you very, very much14:02
dhellmannodyssey4me : I assume the patch releases for the other branches are less urgent?14:02
*** sigmavirus24_awa is now known as sigmavirus2414:03
odyssey4medhellmann yeah, no massive rush there14:05
openstackgerritMerged openstack/releases: Release OpenStack-Ansible Mitaka/13.0.1  https://review.openstack.org/30931714:06
dims_thanks dhellmann14:08
* dhellmann looks at the list of ansible repos and wonders if he can make his yubikey send his gpg password14:08
odyssey4mesorry dhellmann ://14:09
dhellmannodyssey4me : nah, not your fault14:09
dhellmannpaste is working fine :-)14:10
odyssey4metime to get that extra automation built into the gate :)14:10
dhellmannindeed14:10
*** sdake_ has joined #openstack-release14:10
dhellmannand it turns out I can, and now have, so that's nice14:18
odyssey4meI see the tag on the integrated repo. All done dhellmann ?14:26
dhellmannodyssey4me : yep, all done14:26
odyssey4meexcellent, thank you very much!14:26
*** doug-fis_ has joined #openstack-release14:30
*** doug-fish has quit IRC14:33
*** cody-somerville has quit IRC14:45
*** sdake_ has quit IRC14:50
*** skraynev has quit IRC14:51
*** skraynev has joined #openstack-release14:52
dhellmanndims_ : did you hear from sdake about a kolla release?15:00
-openstackstatus- NOTICE: Log server was repaired as of 10:50 UTC and jobs have been stable since. If necessary, please recheck changes that have 'UNSTABLE' results.15:01
*** nikhil has quit IRC15:08
*** sdake has joined #openstack-release15:10
*** bnemec is now known as beekneemech15:13
*** sdake_ has joined #openstack-release15:19
*** sdake has quit IRC15:19
*** openstack has joined #openstack-release15:26
dims_dhellmann : nope15:27
*** amotoki has joined #openstack-release15:27
dhellmanndims_ : ok, we'll wait and see15:28
*** amotoki has quit IRC15:40
*** pabelanger has joined #openstack-release15:41
*** amotoki has joined #openstack-release15:55
*** TravT_ is now known as TravT16:06
*** sdake_ has quit IRC16:07
*** doug-fis_ has quit IRC16:13
*** doug-fis_ has joined #openstack-release16:17
*** TravT has quit IRC16:17
*** TravT has joined #openstack-release16:18
*** armax has quit IRC16:18
*** armax has joined #openstack-release16:19
*** doug-fis_ has quit IRC16:27
*** nikhil has joined #openstack-release16:40
*** gordc has quit IRC16:48
*** amotoki has quit IRC17:09
*** mattoliverau has quit IRC17:13
*** matt6434 has joined #openstack-release17:14
*** dave-mccowan has quit IRC17:14
*** dtantsur is now known as dtantsur|afk17:19
*** dave-mccowan has joined #openstack-release17:21
*** amotoki has joined #openstack-release17:24
*** amotoki has quit IRC17:28
*** kzaitsev_mb has joined #openstack-release17:29
*** armax has quit IRC17:32
inc0dhellmann, dims_ waiting for one patch to clear the gate and we are good to tag kolla17:46
dims_inc0 : ack17:49
*** mriedem1 has joined #openstack-release17:49
*** mriedem has quit IRC17:51
*** sdake has joined #openstack-release17:56
*** armax has joined #openstack-release18:01
*** AJaeger has joined #openstack-release18:10
*** doug-fish has joined #openstack-release18:10
AJaegerdhellmann, FYI, we've removed now from most projects that had both publish-to-pypi and openstack-release-server the extra openstack-release-server. Still open are aodh and gnocchi.18:11
dhellmannAJaeger : ok, thanks for the heads up. The release validation job will block releases for those until it's cleaned up so we won't forget. :-)18:11
AJaeger;)18:14
*** SlickNik has quit IRC18:16
*** AJaeger has left #openstack-release18:16
inc0sdake, dims_ dhellmann we're good to tag18:16
dims_inc0 : got a review up?18:17
sdakeinc0 let me get the review up18:17
sdakehang tight dims_18:17
sdakeinc0 if ou would like the honors i can point you a t the patch18:17
inc0sdake, yup, I actually would;)18:17
*** SlickNik has joined #openstack-release18:17
*** vipuls has joined #openstack-release18:18
*** vipul has quit IRC18:18
sdakeinc0 looks like i talready merged18:18
sdakegit clone http://github.com/openstack/kolla18:18
sdakefind _independent18:18
sdakerather18:18
sdakeopenstack/releaes18:18
sdakeor release18:18
sdakedims_ i know you want one point of contact but i am training a coupoel folks in our team on how to tag in my absence (like when i had  the dental medical emergency in november)18:21
sdakeso inc0 is going  to do this review, rhallisey will do 1.1.0 then I'l ldo the future releases18:22
sdakeunless i send a note to the emaiing list as noted in the releasses documentation18:22
sdakedims_ sound good?18:22
dims_sdake : let's add/keep an entry in the wiki (https://wiki.openstack.org/wiki/CrossProjectLiaisons) so anyone from release who needs to ping can ping a specific person in an urgent situation18:24
sdakedims_ I will be the liason unless there is some type of emergency18:24
sdakebuti'll add that now18:24
dims_thanks sdake18:24
openstackgerritMichal Jastrzebski (inc0) proposed openstack/releases: Release Kolla 2.0.0  https://review.openstack.org/30954818:27
*** dstanek has quit IRC18:46
*** dstanek has joined #openstack-release18:47
*** mriedem1 is now known as mriedem18:59
*** sdake_ has joined #openstack-release19:00
*** doug-fish has quit IRC19:02
*** sdake has quit IRC19:03
*** inc0 has quit IRC19:03
*** inc0 has joined #openstack-release19:04
*** kzaitsev_mb has quit IRC19:13
*** inc0 has quit IRC19:17
*** inc0 has joined #openstack-release19:18
*** doug-fish has joined #openstack-release19:21
*** inc0 has quit IRC19:21
*** doug-fish has quit IRC19:22
*** doug-fish has joined #openstack-release19:22
*** inc0 has joined #openstack-release19:24
dhellmannsdake_, inc0 : I assume all of those patches on stable/mitaka are already on master, too?19:28
sdake_dhellmann yes of course mster first19:28
sdake_master->mitaka->liberty19:29
dhellmannok, well, given the liberty rebranch I didn't want to make any assumptions without asking19:29
sdake_right19:29
sdake_ya liberty was fail on our part19:29
sdake_we have a good plan in place or managing backports19:29
sdake_what we were missing before was prpoer launchpad tracking of backport bugs19:30
dims_dhellmann : do you have some time for doing the release?19:30
dhellmanndims_ : yeah, I'm looking at it now19:31
sdake_dhellmann there will lbe some cases where stable/mitaka will have variance from master19:31
sdake_let me provide the one  example19:31
dims_ack thanks dhellmann19:31
dhellmannsdake_ : does 629990ebcbde724e6276040129324f84840c945c imply that as new stable releases are cut you'll have to update that file?19:31
sdake_in mitaka, we install centos-release-mitaka19:31
sdake_in master we install a different rdoprojectrepo19:31
sdake_update which file?19:32
dhellmannsdake_ : after today, the stable team will do the reviews for releases off of mitaka and liberty19:32
sdake_well we haen't released liberty 1.1.0 yet but wfm19:32
dhellmannthere's a list of references to versioned tarballs in kolla/common/config.py19:32
sdake_they are nearly all backports unless they point to specific upstream locations19:32
sdake_right, those are the "spcials" that dont go in master19:32
sdake_therer is that config.py file19:33
sdake_as well as docker/base/Dockerfile.j2 which points toa different upstream repo19:33
dhellmannwhat I'm worried about is it looks like you're hard-coding versions of things that are likely to be updated semi-regularly19:33
sdake_if they went in master first, they would break master19:33
dhellmannare you planning to keep up as, for example, glance has new stable releases?19:33
sdake_we are planning z streams every 45 days19:33
dhellmannok19:34
sdake_with a reduction from 45 to hit a tuesday rtag day19:34
dhellmannit might be worth looking at automating updates to that file by looking at the deliverable files in the releases repo19:34
sdake_so if 45 days is friday, it may be 42 days instead19:34
sdake_dhellmann yup its been discussed19:34
sdake_we want to do that19:34
sdake_-enotenughbandwidth ;)19:35
dhellmannyep19:35
sdake_the mian reaon being so we don't haeto mmaintain that fie19:35
sdake_the aprt about stble maintenance team looking at backports, that wfm, but for liberty i'd like to get our liberty branch functional first19:36
sdake_atm it deploys mitaka until inc0's patch merges19:36
sdake_we are only backporting critical and high bugs19:37
sdake_also we will release z streams off schedule if a security vulenrability is found19:37
sdake_i'd like to get our vulnerabilities under vmt management19:37
*** sdake_ is now known as sdake19:38
sdakedhellmann all tht sound good to you?19:38
openstackgerritMerged openstack/releases: Release Kolla 2.0.0  https://review.openstack.org/30954819:39
dhellmannsdake : I just mean that for stable branches the stable team signs off on the release before we cut it19:41
sdakeoh got it19:41
*** dstanek has quit IRC19:42
sdakeare there guidelines i shouod lfollow as to not trigger a situation in which the stable maint team wont sign off on it?19:42
*** dstanek has joined #openstack-release19:42
*** inc0 has quit IRC19:42
*** inc0 has joined #openstack-release19:43
dhellmannit'll depend on what sorts of assertions you're making about stable branches, but if you're not strictly following stable yet I think as long as you aren't backporting features it would be considered ok19:43
sdakeabsolutey o ffeatures19:43
dhellmannwe tend to frown on changing requirements, too19:43
sdakeno eatures19:43
*** dstanek has quit IRC19:43
dhellmannotherwise, http://governance.openstack.org/reference/tags/stable_follows-policy.html covers the strict rules19:44
sdakereading19:44
*** dstanek has joined #openstack-release19:44
dhellmannand there are likely more details in the project team guide19:44
dhellmannhttp://docs.openstack.org/project-team-guide/stable-branches.html19:44
dhellmannyour tag is in place and the tarball has built. it looks like we're waiting for zuul to catch up before starting the pypi upload and announce jobs19:45
sdakeWhether the fix is already on master and all consequent stable branches: a change must be a backport of a change already merged onto master, unless the change simply does not make sense on master.19:46
sdakethe unless part there - that applies to our usptream repo locations19:46
sdakedhellmann thanks :)19:46
* dhellmann steps afk for a while19:50
*** amrith is now known as _amrith_19:53
*** inc0 has quit IRC20:00
*** inc0 has joined #openstack-release20:01
*** inc0 has quit IRC20:35
*** _amrith_ is now known as amrith21:19
*** bauwser is now known as bauzas21:30
*** dave-mccowan has quit IRC21:39
*** mriedem has quit IRC21:44
*** mriedem has joined #openstack-release21:46
*** hongbin has joined #openstack-release21:51
*** mriedem has quit IRC21:51
*** sdake has quit IRC22:17
*** sigmavirus24 is now known as sigmavirus24_awa22:23
*** sdake has joined #openstack-release22:42
sdaketonyb around?22:44
sdakewanted to discuss stable maintenance with you22:45
*** sdague has quit IRC23:06
*** matt6434 is now known as mattoliverau23:19
*** cody-somerville has joined #openstack-release23:32
*** cody-somerville has quit IRC23:32
*** cody-somerville has joined #openstack-release23:32
*** nikhil has quit IRC23:58
*** nikhil_k is now known as nikhil23:58

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