Tuesday, 2015-09-15

*** dims_ has joined #openstack-relmgr-office00:48
*** sigmavirus24 is now known as sigmavirus24_awa01:31
openstackgerritBen Swartzlander proposed openstack/releases: Release of python-manilaclient 1.3.0  https://review.openstack.org/22328102:06
*** dims_ has quit IRC02:11
*** dims_ has joined #openstack-relmgr-office03:12
*** dims_ has quit IRC03:19
*** sigmavirus24_awa has quit IRC03:27
*** isviridov_away has quit IRC03:28
*** jroll has quit IRC03:28
*** mattoliverau has quit IRC03:29
*** mattoliverau has joined #openstack-relmgr-office03:29
*** jroll has joined #openstack-relmgr-office03:31
*** sigmavirus24_awa has joined #openstack-relmgr-office03:32
*** jroll has quit IRC03:41
*** sigmavirus24_awa has quit IRC03:41
*** mattoliverau has quit IRC03:41
*** mattoliverau has joined #openstack-relmgr-office03:42
*** david-lyle has joined #openstack-relmgr-office03:50
*** jroll has joined #openstack-relmgr-office04:04
*** sigmavirus24_awa has joined #openstack-relmgr-office04:05
*** wshao has joined #openstack-relmgr-office04:07
*** isviridov_away has joined #openstack-relmgr-office04:10
*** dims_ has joined #openstack-relmgr-office04:16
*** wshao has quit IRC04:17
*** dims_ has quit IRC04:22
*** armax has quit IRC04:30
*** TravT has quit IRC06:37
*** TravT_ has joined #openstack-relmgr-office06:37
*** TravT has joined #openstack-relmgr-office06:41
*** wshao has joined #openstack-relmgr-office06:42
*** TravT_ has quit IRC06:43
*** TravT has quit IRC06:43
*** TravT has joined #openstack-relmgr-office06:44
*** TravT_ has joined #openstack-relmgr-office06:53
*** TravT has quit IRC06:54
*** wshao has quit IRC07:10
*** dims_ has joined #openstack-relmgr-office08:20
*** dims_ has quit IRC08:53
ttxKiall, flaper87, johnthetubaguy, SergeyLukjanov: ping me if around09:01
flaper87ttx: I am09:02
ttxQuick check on zaqar status for release09:02
ttxhttps://launchpad.net/zaqar/+milestone/liberty-rc109:02
ttxshows one standing FFE09:02
ttxhow close is this ? Is there any other FFE standing ?09:03
ttxhttps://blueprints.launchpad.net/zaqar/+spec/fine-grained-permissions09:03
flaper87ttx: It's complete, as of yday09:04
flaper87I need to update the bp09:05
* flaper87 does that09:05
ttxflaper87: cool, so no more FFE in zaqar ?09:05
flaper87as far as those bugs go, we're reviewing them and it should be all done in time for the rc1 release09:05
flaper87no more FFEs09:05
flaper87Zaqar liberty is closed feature wise09:05
ttxok, the bug list is up-to-date with RC1 blockers ?09:05
flaper87it is09:05
ttx(at least known ones)09:05
ttxok, great, looks like you're in great shape09:06
flaper87I checked it yda09:06
flaper87w000h0009:06
ttxflaper87: Thx for the quick update09:06
flaper87np, my pleasure09:06
openstackgerritErno Kuvaja proposed openstack/releases: Release of python-glanceclient 1.1.0  https://review.openstack.org/22271609:09
*** dims_ has joined #openstack-relmgr-office09:52
*** dims_ has quit IRC09:57
*** dims_ has joined #openstack-relmgr-office10:44
*** gordc has joined #openstack-relmgr-office11:34
openstackgerritMerged openstack/releases: Release of python-glanceclient 1.1.0  https://review.openstack.org/22271611:54
ttxgordc: ping me when available11:57
ttxKiall, johnthetubaguy, SergeyLukjanov: same ^11:57
gordcttx: o/11:57
ttxgordc: Quick check on Ceilo release status11:57
ttxhttps://launchpad.net/ceilometer/+milestone/liberty-rc111:57
ttxshows that you're done with FFEs, is that correct ?11:58
*** bdemers has quit IRC11:58
gordcttx: yes. we closed off our remaining FFE items last week so we're just testing/documenting currently.11:58
ttxgreat!11:58
gordcwe're also aiming to tag ceilometerclient 1.5.0 as our liberty cilent11:58
ttxgordc: you only have 2 RC bugs on the list -- are those all the known blockers ?11:59
gordcttx: the first one is.11:59
gordci actually haven't been targetting bugs for rc1...11:59
ttxfeels like you could go and tag RC1 soon, and unfreeze master11:59
gordci'll start doing that.12:00
ttxwell, you should have all the RC1 blockers on this list, so that we know how far you are12:00
openstackgerritMerged openstack/releases: Release of python-manilaclient 1.3.0  https://review.openstack.org/22328112:00
gordcttx: i'll take a look at existing bugs and tag for rc1 as appropriate12:00
ttxideally you would tag the RC1 sometimes next week12:00
ttxso that you don't freeze master for too long12:01
gordckk, i think next week is a doable target for us12:01
ttxcool. The important step is to list the blockers on the RC1 page so that you know how far you are12:01
ttxgordc: thx!12:01
gordcttx: sure makes sense.12:01
ttxdhellmann: hi! Looking at docs.o.o/releases I was wondering why we had neutronclient cliff starting with folsom and no other libs until icehouse12:34
ttxshould we try to map the others ? or remove those ?12:34
dhellmannttx: yeah, it's a matter of importing their history from git12:50
dhellmannI can make a note to do that12:50
dhellmannthere's a tool for it, I just have to run it on all the libs12:51
ttxok, yeah that would be good, for completeness12:51
dhellmannnoted12:52
dhellmannttx: this looks like a reasonable constraints change for tempest-lib, do you want to approve? https://review.openstack.org/#/c/223523/12:52
ttxack done12:54
dhellmanngordc: are you set for ceilometer library releases for liberty? http://docs.openstack.org/releases/releases/liberty.html#library-projects12:56
dhellmannmorgan: are you set for keystone library releases for liberty? http://docs.openstack.org/releases/releases/liberty.html#library-projects12:56
gordcdhellmann: we're looking to set ceiloemeterclient 1.5.0 as our min version for liberty https://review.openstack.org/#/c/222386/13:00
gordcdhellmann: for ceilometermiddleware, we may need a release today/tomorrow13:01
dhellmannack13:01
dhellmannttx: a requirements bump for ceilometer client: https://review.openstack.org/#/c/222386/213:05
ttxack13:10
dhellmannthingee: do we need a cinder client release to wrap up liberty? http://paste.openstack.org/show/462959/13:10
dhellmannKiall: do we need a designate client release to wrap up liberty? http://paste.openstack.org/show/46296713:12
ttxdhellmann: started to work on Mitaka release schedule, you can see options at https://www.dropbox.com/s/qdh8v3tffdds3mb/Schedule.pdf?dl=013:17
ttxQuick comments: ideally we have two full weeks between release week and summit week, that's better for everyone's sanity13:17
ttxThen we have the option to shorten the period between FF and final from 6 weeks to 5 weeks13:18
ttxsquares in yellow is where I'm likely to be off13:18
ttxsome proposals account for the dead period around Christmas13:18
* ttx adds another pption13:20
*** dims_ has quit IRC13:21
dhellmannmorgan: more details for keystone owned libs: http://paste.openstack.org/show/462977/13:22
*** dims_ has joined #openstack-relmgr-office13:22
ttxdhellmann: options 1/2 only have one empty week between release and summit. options 3/4 place FF on a week I'm likely not to be around. options 5/6 shorten the FF-to-release period by one week.13:23
dhellmannttx: looking now13:24
ttxIf we do our release management simplification right, I think the most painful option would be 1/213:24
ttxI'm tempted to reduce FF-to-release.13:25
dhellmannso option 5?13:26
dhellmann6 might be better, with a longer m213:26
ttxoptions 5/6. I think I prefer 6 since it accounts for the ghost week around christmas)13:26
dhellmannyeah13:26
ttxdo you think it's doable to shorten FF-to-release by one week ? (compared to this cycle)13:27
ttx(we still have the same time between FF and summit)13:27
dhellmannI'm likely to be gone around jan 13 for our 20th anniversary trip, though we might take it later in the year, too13:27
ttxOK, let's give it a bit more thought before deciding. Maybe see how the RC1s go this cycle, see how optimistic the shortened one is13:29
dhellmannthat seems like a good idea13:29
dhellmannI'd like to figure out a way to eliminate the release period log jam13:30
dhellmannmestery: is neutronclient 3.0.0 the final expected release this cycle?13:32
ttxnikhil_k, redrobot, thingee: ping me when available for a quick release status check13:32
ttxKiall, johnthetubaguy, SergeyLukjanov: same ^13:33
johnthetubaguyttx: sure13:33
mesterydhellmann: I believe it is, yes, that's why I never pushed a patch.13:33
ttxjohnthetubaguy: looking at https://launchpad.net/nova/+milestone/liberty-rc113:33
dhellmannmestery: ok, just making sure, thanks13:33
mesterydhellmann: Thanks for keeping me honest :)13:34
ttxjohnthetubaguy: I see one standing FFE, how close is that one ?13:34
ttxjohnthetubaguy: any other FFE not listed there ?13:34
ttxmestery: we need to sync too, whenever is good for you13:34
dhellmannmestery: it has been a pleasure serving with you this cycle13:34
mesteryttx: Ack! Can you give me about 20 minutes or so? Is that too late or will that work?13:35
ttxmestery: sure, i should be around13:35
dhellmannnotmyname: do you need another swiftclient release for liberty? http://paste.openstack.org/show/46299313:35
mesterydhellmann: Thanks! The same for you and ttx! I hope people tell both of you this, but you do an excellent job at what you do, you really make the life of all PTLs so much easier. :)13:35
mesteryttx: Will ping you soon!13:35
ttxdhellmann: starting to think this channel is popular and has a bit of a weird name. We should probably rename to #openstack-release, but that's painful13:35
dhellmannttx: but I just got the place decorated to my satisfaction!13:36
dhellmannseriously, a rename may be in order13:36
ttxcurrent name was OK when it was a specialized channel for office hours13:37
ttxbut now that it's almost part of the process for all teams, not so much13:37
dhellmannflaper87: do you need a zaqarclient release to wrap up liberty? http://paste.openstack.org/show/46299413:37
dhellmannttx: yeah, it would make sense to follow the team naming convention used elsewhere13:38
flaper87dhellmann: sadly, no. We'll likely cut one in early M, though.13:38
dhellmannflaper87: ack, we'll create the stable branch from 0.1.1 then13:38
flaper87dhellmann: sounds good13:38
johnthetubaguyttx: we are arguing over the last patch13:39
ttxjohnthetubaguy: but it's close and it's the only one ?13:39
johnthetubaguyttx: we have a few other possible blockers, but nothing seems important enough to block on right now13:39
johnthetubaguyttx: worried we don't really have anyone raising bugs or testing, honestly13:40
ttxjohnthetubaguy: on the bugs side... did you go through the nova bugs list and come up with the blockers there ?13:40
johnthetubaguyusing liberty-rc-potential bug tag for the maybe blockers13:40
ttxok13:41
ttxso the list is the current known blockers, even if you may add a couple more13:41
johnthetubaguynot personally been through them all, folks have been through some, and triage folks are looking out for them13:41
ttxand should ask Nova folk to more actively file blockers if they have some they find in testing13:41
johnthetubaguyttx: yeah, we have the known ones, but it seems too small13:42
ttxjohnthetubaguy: you seem to be on track for a RC1 next week anyway, little point in freezing master for a lot longer if you have so little things to fix in it13:42
ttxjohnthetubaguy: ok, thx for the update13:42
ttxjohnthetubaguy:  the FFE is actually not a FFE, it's a doc task, right13:43
johnthetubaguyttx: yeah, that one is a doc only task, and its a developer only doc13:43
ttxack13:44
johnthetubaguyttx: we still have about 80 odd bug fixes waiting for a review, but just rechecking them, but nothing makes we want to hold up the release right now13:45
morgandhellmann: should be ready for another release of the libs tomorrow. Need to check with people14:07
ttxmorgan: would you be availble for a quick release status check ?14:08
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: automatically submit constraints updates for new releases  https://review.openstack.org/20168214:08
dhellmannmorgan: ok, we're down to the wire so be aggressive about not waiting for stuff if you can14:09
morganttx: sure14:10
mesteryttx: I'm back now!14:10
ttxmorgan: looking at https://launchpad.net/keystone/+milestone/liberty-rc114:10
morgandhellmann: mostly i just woke up14:10
* mestery waits for morgan and ttx to finish14:10
morgandhellmann: like minutes ago14:10
ttxmorgan: I see two BPs there and a few RC1-targeted bugs14:10
ttxare those two BPs for standing FFEs ?14:11
dhellmannmorgan: sure, get yourself awake, I just meant we should not delay for FFE14:11
morganBPs will be punted today / code gating14:11
ttxmorgan: and/or are there more FFEs standing for Keystone ?14:11
ttxmorgan: ok, I'll let you adjust the list of BPs there accordingly once that is done14:11
morganFFEs should be decided at our meeting in a few hours14:11
ttxIs the bug list current with known RC1 blockers ? Or do you still have to go through the bug list and target them ?14:12
morganBugs should be gating soonish14:12
morganI need to check for new bugs but I think those are mostly nice to haves and should land14:12
morganA couple are blockers14:13
ttxok, so you should be on track for a RC1 sometimes next week14:13
morganYeah14:13
ttxcool. Thx for the update!14:13
ttxmestery: you're on14:13
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: automatically submit constraints updates for new releases  https://review.openstack.org/20168214:13
* mestery buckles in14:13
ttxhttps://launchpad.net/horizon/+milestone/liberty-rc114:13
morganI will also be defering some final rc stuff to the new PTL once election has completed14:13
morganFwiw14:13
*** sigmavirus24_awa is now known as sigmavirus2414:13
ttxShows 4 standing FFEs, is that correct ?14:13
morganRc2, release and beyond14:14
ttxmorgan: ack14:14
mesteryttx: That's correct, we went over them in the neutron meeting yesterday and ended up with those 4.14:14
ttxhow far are they ?14:14
mesteryLBaaS one just needs a devstack patch, it's basically done14:14
mesteryWSIG framework will merge back into master tomorrow14:14
mesteryExternal DNS is one small patch that needs to be re-spun14:14
mesteryFlavor frameowkr template is the one which has a handful of patches left14:15
mesteryIt's the long pole14:15
mesterySo14:15
mesteryThey are all looking awesome :)14:15
*** armax has joined #openstack-relmgr-office14:15
ttxSure, I just fear they distract your team from the long list of RC1-targeted bugs14:15
mesteryI think the only one which may is the flavor one14:15
mesteryThe other 3 are basically ready and just require sheparding a bit14:15
ttxok14:15
ttxwhat would be your ETA for the flavor one ?14:16
mesteryI'd like to see those patches merged by the end of the week14:16
ttxyeah, that would be good if we want to hit RC1 in a reasonable time14:17
ttxTalking about the targeted bug list, it's a bit long14:17
ttxany chance you could split it between real RC1 blockers, and using a tag for nice-to-haves ?14:17
mesteryttx: I will do that today, yes.14:18
ttxI just don't see how you would complete the current list in the next two weeks14:18
mesteryttx: I agree, I think some things have been slipped in as "wishful thinking"14:18
ttxok14:18
mesteryAgreed14:18
mestery:)14:18
ttxsure and that's fine if they make it14:18
mesteryPeople are optimistic :)14:18
ttxok, I think I have what I needed14:18
ttxmestery: thx14:18
mesteryttx; Cool!14:19
mesteryttx dhellmann: There is one potential client patch for a 3.0.1 (https://review.openstack.org/#/c/219455/)14:19
mesteryI'm having folks look at it now.14:19
mesteryIf it doesn't merge by today, then 3.0.0 is it, otherwise we may want to cut 3.0.1 with that one (and one other patch which merged into the client last week).14:19
*** david-lyle has quit IRC14:20
ttxKiall, SergeyLukjanov, nikhil_k, redrobot, thingee: ping me when available for a quick release status check14:26
nikhil_kttx: hi14:30
nikhil_kjust back from a irc meeting, sorry I meant to reply earlier about the timing.14:31
nikhil_kttx: I have a few bugs and couple of small FFEs in progress.14:32
nikhil_kwe are tracking them here:14:32
nikhil_khttps://etherpad.openstack.org/p/glance-liberty-rc-reviews14:33
ttxnikhil_k: sorry was afk for a minute14:35
ttxI'm trying to crosscheck with https://launchpad.net/glance/+milestone/liberty-rc114:35
ttxnikhil_k: do you have a BP for scrub-images-in-parallel ?14:36
*** bdemers has joined #openstack-relmgr-office14:36
nikhil_kttx: sure14:36
ttxshould image-signing-and-verification-support be taregetd to liberty-rc1 too ?14:38
nikhil_kttx: it's been added to liberty-rc1 page14:38
nikhil_kttx: not really, it's just waiting on tests14:38
nikhil_kthe code is there, some additional tests around libs are being added14:38
ttxah, ok14:39
ttxnikhil_k: ideally you would have all the feature work out of the way ASAP, so that you can concentrate on bugfixing14:39
ttxAlso ideally you would translate that etherpad you have into a set of targeted bugs and BPs, so that we know how close you are from a RC1 tag14:40
ttxit seems mostly in sync but it's hard to tell14:41
nikhil_kttx: I see, I created the etherpad fot that purpose but I guess it was overused14:41
nikhil_kfor*14:41
dhellmannmestery: ack, we can consider a backport, too14:42
ttxthe etherpad is often useful to easily list the reviews you're actually waiting on for each of those blockers14:42
mesterydhellmann: I think that's the best approach14:42
nikhil_kttx: the features that exists -- one of them is just marked feature so document the perf improvement (parallel scrubbing) and because we have config on it14:42
ttxnikhil_k: but keeping the list of blockers (FFEs and bugs) on the Launchpad page helps us making sense of if everything is under control14:42
dhellmannmestery: let's see if it merges today, first14:42
openstackgerritKaitlin Farr proposed openstack/releases: Remove Castellan from deliverables  https://review.openstack.org/22362414:43
nikhil_kttx: sure, I will cross-check LP with the etherpad. I am not sure if people have added bugs for each of the imp commit so will do that14:43
ttxFor example https://review.openstack.org/#/c/217370/ is listed, points to  https://bugs.launchpad.net/glance/+bug/1444767 which is not on the RC1 page14:44
openstackLaunchpad bug 1444767 in Glance "scrubber edge cases orphan objects and records" [Medium,In progress] - Assigned to Hemanth Makkapati (hemanth-makkapati)14:44
nikhil_kttx: hope that helps14:44
ttxand other changes in the etherpad just don't refer a bug nor a blueprint so they exist only in the etherpad14:45
nikhil_kttx: people seem to have abused the etherpad, I will remove it14:45
ttxnikhil_k: ack14:45
ttxnikhil_k: so try to list the remaining open FFEs and RC1 blocker bugs on the LP page (you may have to file a few bugs to account for things in the list)14:46
nikhil_kttx: that was my worry too, thanks.14:46
nikhil_ksure, I will file those bugs14:46
ttxthat will help figure out how far you are from the RC1 tag14:46
ttxWe'll sync again toward the end of week.14:46
nikhil_ksure, that works14:46
nikhil_kThanks ttx !14:49
openstackgerritKaitlin Farr proposed openstack/releases: Remove Castellan from deliverables  https://review.openstack.org/22362414:59
*** TravT_ is now known as TravT15:02
*** jhesketh has quit IRC15:03
*** jhesketh has joined #openstack-relmgr-office15:04
SergeyLukjanovttx, sorry, I'm here now, IRC client crashed quietly15:10
*** david-lyle has joined #openstack-relmgr-office15:13
SergeyLukjanovso, we have https://etherpad.openstack.org/p/sahara-liberty-ffes to track FFEs15:14
SergeyLukjanovin addition to it we have bunch of bug fixes needed and huge bunch of dock updates in the queue15:14
SergeyLukjanovhttps://launchpad.net/sahara/+milestone/liberty-rc115:14
SergeyLukjanovI will cleanup the spare bugs from it next week15:14
SergeyLukjanovso far, it seems like sahara is in a good shape for rc1 on Sept 21-25 week15:15
ttxSergeyLukjanov: sorry was on a call15:32
ttxchecking15:32
ttxhttps://launchpad.net/sahara/+milestone/liberty-rc115:33
ttxshows 3 FFEs left, how far are they from landing ?15:33
ttx(at this stage it's a good idea to complete them to be able to focus on bugs and RC1)15:34
ttxSergeyLukjanov: also, any chance you could refine the bug list this week instead ? i'd like to have a clean slate entering next week15:34
ttxdavid-lyle: ping me when you have 5 minutes for a horizon release status check15:35
*** bdemers has quit IRC15:37
*** bdemers has joined #openstack-relmgr-office15:45
*** bdemers has quit IRC15:46
david-lylettx: o/15:55
ttxhttps://launchpad.net/horizon/+milestone/liberty-rc115:55
ttxdavid-lyle: this lists 4 open FFEs, is that correspnding to the reality ?15:56
ttxor do you have more or less ?15:56
david-lyle3 should merge out of those, one is wishlist essentially15:56
david-lylebut does not interfere with stability15:57
ttxdavid-lyle: how far are they ? We should purge the FFEs asap to concentrate on bugfixes15:57
david-lylenetwork topology is blocked by someone reporting an issue, others trying to reproduce15:57
david-lyleotherwise ready15:57
ttxok15:57
david-lylethe Sahara BP should be ready, just trying to get through review15:58
ttxOn the bugs side, would be great to refine the list to true RC1 blockers, and move nice-to-haves to some tag15:58
david-lyleand Database clustering is a 1700 line review needing more time to review15:58
ttxbecause I don't think all those bugs will be fixed before the end of times15:58
david-lylettx: will pare doen the list15:58
david-lyle*down15:58
ttxdavid-lyle: ok, general goal being to tag the RC1 next week, but I usually cut some slack for Horizon since it sits on top of features that just appeared15:59
ttxwould still like all FFEs purged by end of week though15:59
david-lylettx: understood. will move them forward16:00
ttxso we would drop that wishlist one if it happens to not be completed16:00
ttxso we'll sync again around end of week16:01
ttxdavid-lyle: thx!16:01
david-lylesure, will do, I wanted to give it some slack16:01
david-lylebut hasn't materialized yet16:01
ttxSergeyLukjanov, Kiall, redrobot: around?16:02
david-lylethanks ttx16:02
*** bdemers has joined #openstack-relmgr-office16:06
redrobotttx o/16:10
*** bdemers_ has joined #openstack-relmgr-office16:11
*** bdemers has quit IRC16:12
*** bdemers_ is now known as bdemers16:12
ttxredrobot: o/16:17
ttxhttps://launchpad.net/barbican/+milestone/liberty-rc116:18
ttxredrobot: that page lists one standing FFE, how close is it from being merged ?16:19
redrobotttx waiting on one more patch16:20
redrobotttx I'm guessing 1-2 days16:20
ttxok16:20
ttxredrobot: you don't have any RC1 blocker bug listed on that page -- does that mean you're bug-free ?16:20
ttxor taht you haven't parsed the bug reports for any blocker you'd like to fix before RC116:20
redrobotttx no, it means we've done a bad job of triaging16:20
ttxredrobot: any chance that can happen early this week ? We'd like to reach RC1 stage next week, and it's difficult if you don't know what the blockers are16:21
redrobotttx yes, I can definitely make that a priority16:21
ttxredrobot: cool, we'll talk again near the end of the week for a new status check16:22
redrobotttx sounds good16:22
ttxredrobot: I hope the FFEs will be in by then and the bug list curated, so that we can draft an ETA for RC116:22
ttxredrobot: thx!16:22
* ttx takes a 3-hour dinner break16:23
openstackgerritgordon chung proposed openstack/releases: python-ceilometerclient 1.1.1 - stable/kilo  https://review.openstack.org/22368416:28
openstackgerritMerged openstack/releases: Remove Castellan from deliverables  https://review.openstack.org/22362416:33
dhellmannttx: when you're back, this should update constraints for the libs we have already: https://review.openstack.org/#/c/223596/16:38
SergeyLukjanovttx, okay, I'll review bugs by the end of this week16:54
*** TravT has quit IRC16:58
*** TravT_ has joined #openstack-relmgr-office16:58
vipuldhellmann: hello, so here's the issue i'm having with registering python-cueclient17:00
vipulhttp://paste.openstack.org/show/463232/17:00
vipulDo i need to update the ownership info in setup.cfg?17:03
dhellmannvipul: looking17:13
*** bswartz has joined #openstack-relmgr-office17:15
bswartzttx: I'm here now17:15
dhellmannvipul: I see the same error. I'm asking in infra to see if dstufft can help us17:15
vipuldhellmann: ok thanks for looking17:16
dhellmannvipul: is there any chance someone else has already registered that name?17:20
dhellmannvipul: I have registered projects in the past few days, including today, so I think there's something special with the name17:20
vipuldhellmann: shouldn't it show up in the search?  I don't recall if it's been registered by anyone17:21
dhellmannvipul: I would expect to find it by search, too, but maybe not if there is no version provided, yet? I don't know how that works.17:21
dhellmannvipul: what do you see if you navigate to https://pypi.python.org/pypi/cueclient17:22
dhellmannI just registered that name17:22
vipulPackage Index Owner: doughellmann -- seems like that worked17:22
dhellmannok, so there may be something wrong with an existing record, or it may be something else17:23
dhellmannI suggest reporting the issue through the pypi bug reporting system to see if someone there can help17:23
vipulOk will go that route too..17:23
vipuldhellmann: anything else i need to do to get a release out?17:23
vipulsubmit a patch to openstack/releases?17:23
jrolldhellmann: when you have a moment, do you mind creating an "Ironic 4.2.0" milestone in launchpad so I can target bugs to it?17:24
dhellmannvipul: for an unmanaged project you'll push a tag yourself when this is working17:24
dhellmannjroll: sure, do you not have permission to do that?17:24
jroll(or teach me to fish)17:24
vipuldhellmann: ok sounds good17:24
jrolldhellmann: I'm looking at https://launchpad.net/ironic/+milestones and don't see a button for it17:24
dhellmannjroll: is that liberty?17:24
jrollI'm part of ironic-drivers17:24
jrollyes17:24
jrollwill be stable/liberty17:24
dhellmannok, to create a milestone you do it from the series page: https://launchpad.net/ironic/liberty17:25
jrollaha!17:25
jrollthanks17:25
dhellmannjroll: I would expect the next liberty release to be 4.1.x17:25
dhellmann4.2 implies new features17:25
jrolldhellmann: pretty sure there will be a g-r update in there, which you told me warrants a minor bump17:26
jrollalso, there are new features in there17:26
dhellmannjroll: stable branches shouldn't get requirements updates17:27
jrolldhellmann: I mean a requirements update between 4.1.0 and 4.2.0 (which will be stable/liberty)17:27
dhellmannjroll: and for the rare cases where we do need that, when we have messed up their requirements, we call those bug fixes and increment the patch level17:27
dhellmannoh, I see, you don't have a 4.2 tag yet, so yeah, that would be ok17:27
jrollyeah :)17:28
jrollcool thanks17:28
dhellmannI thought you meant this would be the next release in the stable series, but it's the *first* release in the stable series, my mistake17:28
dhellmannvipul: did you spot the "support" link near the top of https://pypi.python.org/pypi for reporting the problem? it took me a while to find it, and I knew it was there, so I wanted to make sure you'd found it17:29
jrollheh, correct17:29
vipuldhellmann: I was able to find their Jira, and filed https://bitbucket.org/pypa/pypi/issues/340/unable-to-register-a-package-403-python17:32
vipuldhellmann: i suppose i should also use their support link17:32
dhellmannvipul: you probably only need one or the other, I'm not sure which is actually better17:33
*** TravT_ is now known as TravT17:34
bswartzdhellmann: where is it documented what happens when we do the g-r freeze?17:42
dhellmannbswartz: I'm not sure what you mean?17:43
bswartzthe g-r freeze just means that, for the rest of liberty, we cannot increase the minimum version of anything, right?17:44
bswartzor does it mean we set maximum versions too?17:44
dhellmannwe're trying to avoid capping this cycle17:45
dhellmannso we would rather not raise the minimums or change the constraints used in the gate, except for things we ourselves are releasing17:45
bswartzI'm trying to understand how we deal with bugs found in the client -- do we fix them, then make a new release, then rely on the fact that the latest release is used and g-r is irrelevant?17:46
dhellmannah, ok17:47
dhellmannafter you have a stable branch for the client, you can backport fixes to that and we can update the version used in the stable/liberty constraints list17:47
dhellmannthat's just like what we did last cycle, except that we're not introducing upper-bounds caps on the requirements lists to help with upgrades17:47
bswartzin that case what does the g-r freeze achieve? just a freeze on "other" things from outside openstack?17:48
dhellmannoutside dependencies are a big part of it, yes17:48
bswartzok17:49
bswartzwe're trying to figure out what cutoff dates exist for manila client work, if any17:49
bswartzalso manila-ui project, which is technically a library too17:50
dhellmannbswartz: ok. You should be in feature freeze already, and you should be planning a release this week to serve as the basis of the stable branch.17:52
bswartzdhellmann: so the release serves as the branching point for the stable branch?17:54
bswartzdhellmann: because in that case we need to make another release later this week17:55
dhellmannbswartz: that's right17:55
openstackgerritMatt Riedemann proposed openstack/releases: python-ceilometerclient 1.1.1 - stable/kilo  https://review.openstack.org/22368418:04
*** armax has quit IRC18:04
openstackgerritDoug Hellmann proposed openstack/releases: cliff 1.15.0  https://review.openstack.org/22373018:05
*** bdemers has quit IRC18:06
*** gordc has quit IRC18:11
*** gordc has joined #openstack-relmgr-office18:12
*** armax has joined #openstack-relmgr-office18:40
*** TravT_ has joined #openstack-relmgr-office18:41
*** TravT has quit IRC18:43
*** wshao has joined #openstack-relmgr-office18:50
ttxbswartz: around now19:12
bswartzttx: hey I saw you note but I had to run19:12
ttxbswartz: is now a good time ?19:12
bswartzsure19:13
ttxhttps://launchpad.net/manila/+milestone/liberty-rc119:13
ttxshows that you're done with FFEs, is that correct ?19:13
*** TravT has joined #openstack-relmgr-office19:15
*** TravT_ has quit IRC19:17
ttxbswartz: ?19:19
bswartzarg sorry19:20
bswartzyes we wrapped up FFEs 8 days ago19:20
bswartzwe're been working on bugs ever since19:20
ttxbswartz: same page lists 8 targeted bugs - is that the complete list of release-critical blockers ?19:20
bswartzyes19:20
bswartzthere are no others that we're aware of19:21
ttxbswartz: ok, looks like if you burn them down fast enough you should be on track for RC1 next week19:21
ttxbswartz: thx for the quick update!19:21
bswartzsome of these might even get pushed out or marked invalid after they're investigated19:21
bswartzyeah we're driving towards an early RC1 because our L3 milestone was incomplete due to the technical FFEs19:22
bswartzI want to get RC1 into testers hands this week if at all possible19:22
ttxSlickNik: around for a quick release status update ?19:22
bswartzthe main thing that plagues us is neutron bugs that we can't work around19:23
bswartzthat's a story for another time though19:23
ttxbswartz: I'm fine with this week, end of week so that we have time to cut the libs branches first19:23
ttxand to merge requirements updates19:24
ttxstevebaker: ping me when you are available for a quick release status update19:24
ttxKiall, thingee: same ^19:24
SlickNikttx: here now19:29
ttxSlickNik: https://launchpad.net/trove/+milestone/liberty-rc119:30
ttxthat shows that you're done with all FFEs, is that correct ?19:30
SlickNikttx: yes, that is correct.19:30
SlickNikWe're working purely on bugfixes now.19:30
ttxAlso shows 25 targeted bugs, and I suspect some of those are not release-critical... Any chance you could narrow down to true blockers, and use for example a tag to mark nice-to-haves ?19:31
ttxThat way we could focus and maybe reach RC1 state sometimes next week19:31
SlickNikttx: yes, these are not all release blockers — I will triage them later today to give us a better sense of what's definitely needed for rc119:32
SlickNikttx: that sounds like a good plan — I'll use a tag for "nice-to-haves"19:32
openstackgerritgordon chung proposed openstack/releases: ceilometermiddleware 0.3.0  https://review.openstack.org/22377819:33
SlickNikAnd I see a couple that I don't think are blockers at all that I think we should be able to safely punt to Mitaka.19:33
ttxSlickNik: yeah, some teams use "liberty-rc-potential"19:33
ttxSlickNik: ok, I'll be talking to you later in the week to see progress on the bug burning front19:34
ttxthx!19:34
bswartzI thought "liberty-rc-potential" was for after RC1 was tagged -- to flag things for RC219:34
SlickNikttx: sounds good. Thank you!19:34
ttxbswartz: it's a bit of a moving target19:34
bswartzbecause we *always* have an RC1, but later RCs are optional19:35
ttxit has been used to mark nice-to-haves pre-RC1 as well19:35
ttxbut tags are cheap I agree so we can use another one pre-rc119:35
bswartzI thought we just used the targeting system for RC1 since we know we have to create the milestone19:36
bswartzwe avoid creating milestones for rc2, etc until they are deemed necessary19:36
bswartzthus the tags help in the latter case19:36
ttxbswartz: true19:36
ttxmaybe "liberty-nice-to-have"19:37
bswartz=D19:37
ttxto not conflate with true release blockers19:37
*** TravT has quit IRC19:54
*** wshao has quit IRC20:08
*** TravT has joined #openstack-relmgr-office20:17
*** TravT has quit IRC20:17
*** TravT has joined #openstack-relmgr-office20:24
thingeettx: pong, multi-tasking at the moment. polling for blockers and preparing for cross project meeting20:34
thingeettx: current have a couple of blockers https://bugs.launchpad.net/cinder/+bug/1495764 and https://bugs.launchpad.net/bugs/149575820:38
openstackLaunchpad bug 1495764 in Cinder "Capability Filter doesn't work when create volume using no-admin user" [High,In progress] - Assigned to Xing Yang (xing-yang)20:38
openstackLaunchpad bug 1495758 in Cinder "Create Consistency Group with non-admin user failed" [High,In progress] - Assigned to Xing Yang (xing-yang)20:38
thingeettx: they're in progress20:38
*** wshao has joined #openstack-relmgr-office20:57
ttxthingee: ok, just keep the list updated with blockers (and use another tag for nice-to-haves) and we should be alright.21:02
thingeettx: ack21:03
openstackgerritMerged openstack/releases: ceilometermiddleware 0.3.0  https://review.openstack.org/22377821:13
ttxstevebaker: have 5 min to sync on Heat release status ?21:14
stevebakerttx: yes21:14
ttxstevebaker: https://launchpad.net/heat/+milestone/liberty-rc121:15
ttxshows 2 standing FFEs -- is that accurate or is there more ?21:15
ttxIf accurate, how far are they from completion ?21:15
stevebakerttx: there is indeed only 2. I would still like them in but they are both at medium risk of not being ready21:17
ttxstevebaker: I'm mostly concerned about how much of a diversion they are (and how untested the feature will be)21:17
ttxYou have a lot of RC1-targeted bugs, are they all release blockers ?21:18
ttxIf not, maybe refine the list to only list true blockers and move the rest to some nice-to-have tag21:18
ttxthat will look less scary21:18
ttxstevebaker: what deadline did you have in mind for those last 2 FFEs ?21:19
stevebakerttx: nested-validation just extends the existing returned validation data, so is low risk. rich-network-prop adds attributes to OS::Nova::Server - it is being reworked now to not change behaviour for template using existing attributes, so that lowers the risk21:20
openstackgerritDoug Hellmann proposed openstack/releases: git history import cleanups  https://review.openstack.org/22381821:20
openstackgerritDoug Hellmann proposed openstack/releases: history build cleanup  https://review.openstack.org/22381921:20
openstackgerritDoug Hellmann proposed openstack/releases: Import barbican client history  https://review.openstack.org/22382021:20
openstackgerritDoug Hellmann proposed openstack/releases: Import ceilometerclient history  https://review.openstack.org/22382121:20
openstackgerritDoug Hellmann proposed openstack/releases: Import cinderclient history  https://review.openstack.org/22382221:20
openstackgerritDoug Hellmann proposed openstack/releases: Import designateclient history  https://review.openstack.org/22382321:20
openstackgerritDoug Hellmann proposed openstack/releases: Import glanceclient history  https://review.openstack.org/22382421:20
openstackgerritDoug Hellmann proposed openstack/releases: Import heatclient history  https://review.openstack.org/22382521:20
openstackgerritDoug Hellmann proposed openstack/releases: Import ironicclient history  https://review.openstack.org/22382621:20
openstackgerritDoug Hellmann proposed openstack/releases: Import ironic-inspector-client history  https://review.openstack.org/22382721:20
openstackgerritDoug Hellmann proposed openstack/releases: Import keystoneclient history  https://review.openstack.org/22382821:20
openstackgerritDoug Hellmann proposed openstack/releases: Import manilaclient history  https://review.openstack.org/22382921:20
openstackgerritDoug Hellmann proposed openstack/releases: Import novaclient history  https://review.openstack.org/22383021:20
openstackgerritDoug Hellmann proposed openstack/releases: Import openstackclient history  https://review.openstack.org/22383121:20
openstackgerritDoug Hellmann proposed openstack/releases: Import saharaclient history  https://review.openstack.org/22383221:20
openstackgerritDoug Hellmann proposed openstack/releases: Import swiftclient history  https://review.openstack.org/22383321:20
openstackgerritDoug Hellmann proposed openstack/releases: Import troveclient history  https://review.openstack.org/22383421:20
openstackgerritDoug Hellmann proposed openstack/releases: Import zaqarclient history  https://review.openstack.org/22383521:20
stevebakerttx: I'm hoping they'll be ready to land this week.21:20
stevebakerttx: as for bugs, I'll do a prune to blockers only.21:21
ttxstevebaker: i'm fine with giving them until the end of the week, if your release-critical bug list is not 30-bugs deep. Otherwise I don't see how we can produce a RC1 before December :)21:21
stevebakerttx: there is a bug which may result in a sql schema change. How do we handle that during FFE?21:22
ttxIn theory that requires an exception too21:22
ttxthe sooner it gets in the sooner we can catch any weird regression due to the schema change21:23
ttxso I would prioritize fixing that one up21:23
stevebakersure thing21:23
stevebakerttx: can we talk heatclient too?21:24
ttxOk, we'll talk again at the end of the week. Let's get those last 2 FFEs in by then and distill that bug list down to true blockers.21:24
ttxstevebaker: sure21:24
stevebakerthere are still a couple of changes which need to land. https://bugs.launchpad.net/python-heatclient/+milestone/0.8.021:25
openstackstevebaker: Error: malone bug 0 not found21:25
ttxheh fun21:25
stevebakerttx: what is the story with when stable branching happens for heatclient?21:25
ttxso we create a release branch. We can still issue point releases on that branch21:26
ttxso bugfixes that only increment .Z are ok to backport21:26
openstackgerritMerged openstack/releases: cliff 1.15.0  https://review.openstack.org/22373021:26
stevebakerright, but we're still landing the client side changes for liberty features21:26
ttxthe idea is taht we need a tagged release to branch from21:27
ttxstevebaker: this is starting to be a bit late for that. The RC1 needs to icnlude the requirements for the lib, so the lib has to be available first21:27
stevebakersure21:28
ttxwhich is why the deadline for python-*client release branch was ... 1 week ago now21:28
ttxwe are still cutting the last ones21:28
ttxbut that means it becomes pretty urgent to push features in if you still have some21:29
ttxand cut a version we can make the liberty branch from21:29
ttxstevebaker: how far are you on those ?21:30
stevebakerthe features are all at the cli layer, so at least the lib is stable21:30
stevebakerI think they are close. 24-48 hours?21:30
ttxI guess as long as we can cut the stable branches this week we should be good, release-wise21:30
stevebakerok, thanks21:31
ttxmeans we can't tag RC1s on projects consuming heatclient before next week, but there aren't that many21:31
ttxstevebaker: ok, ttyl!21:33
dhellmannlifeless: can you take a peek at this change to update the constraints for some of our current libs? https://review.openstack.org/22359621:33
stevebakerttx: \o21:33
lifelesshttps://review.openstack.org/#/c/221157/ failed, we need to poke at that21:35
lifeless+A'd 59621:35
*** TravT has quit IRC21:43
openstackgerritMerged openstack/releases: python-ceilometerclient 1.1.1 - stable/kilo  https://review.openstack.org/22368421:47
*** TravT has joined #openstack-relmgr-office21:50
openstackgerritDoug Hellmann proposed openstack/releases: Import ceilometerclient history  https://review.openstack.org/22382121:52
openstackgerritDoug Hellmann proposed openstack/releases: Import barbican client history  https://review.openstack.org/22382021:52
openstackgerritDoug Hellmann proposed openstack/releases: Import designateclient history  https://review.openstack.org/22382321:52
openstackgerritDoug Hellmann proposed openstack/releases: Import cinderclient history  https://review.openstack.org/22382221:52
openstackgerritDoug Hellmann proposed openstack/releases: history build cleanup  https://review.openstack.org/22381921:52
openstackgerritDoug Hellmann proposed openstack/releases: git history import cleanups  https://review.openstack.org/22381821:52
openstackgerritDoug Hellmann proposed openstack/releases: Import keystoneclient history  https://review.openstack.org/22382821:52
openstackgerritDoug Hellmann proposed openstack/releases: Import manilaclient history  https://review.openstack.org/22382921:52
openstackgerritDoug Hellmann proposed openstack/releases: Import novaclient history  https://review.openstack.org/22383021:52
openstackgerritDoug Hellmann proposed openstack/releases: Import openstackclient history  https://review.openstack.org/22383121:52
openstackgerritDoug Hellmann proposed openstack/releases: Import glanceclient history  https://review.openstack.org/22382421:52
openstackgerritDoug Hellmann proposed openstack/releases: Import heatclient history  https://review.openstack.org/22382521:52
openstackgerritDoug Hellmann proposed openstack/releases: Import ironicclient history  https://review.openstack.org/22382621:52
openstackgerritDoug Hellmann proposed openstack/releases: Import ironic-inspector-client history  https://review.openstack.org/22382721:52
openstackgerritDoug Hellmann proposed openstack/releases: remove cruft from the import script  https://review.openstack.org/22383621:52
openstackgerritDoug Hellmann proposed openstack/releases: Import saharaclient history  https://review.openstack.org/22383221:52
openstackgerritDoug Hellmann proposed openstack/releases: Import swiftclient history  https://review.openstack.org/22383321:52
openstackgerritDoug Hellmann proposed openstack/releases: Import troveclient history  https://review.openstack.org/22383421:52
lifelessdhellmann: I think you should just +A all those :)21:52
dhellmannttx: every time we do a release, it introduces a merge conflict in that series ^^ so maybe we should merge it and then fix any errors?21:52
dhellmannlifeless: ++21:52
ttxdhellmann: yes, fasttrack it21:53
dhellmannlifeless: otoh, I like the slightly-off-phase beeping from both of my irc clients noticing the series of patches at the same time :-)21:53
dhellmannttx: ack, doing that now21:53
*** gordc has quit IRC22:16
*** TravT has quit IRC22:25
*** TravT has joined #openstack-relmgr-office22:29
openstackgerritMerged openstack/releases: git history import cleanups  https://review.openstack.org/22381822:35
openstackgerritMerged openstack/releases: history build cleanup  https://review.openstack.org/22381922:35
openstackgerritMerged openstack/releases: Import barbican client history  https://review.openstack.org/22382022:35
*** wshao has quit IRC23:01
*** openstackgerrit has quit IRC23:16
*** openstackgerrit has joined #openstack-relmgr-office23:16
*** david-lyle has quit IRC23:17
*** wshao has joined #openstack-relmgr-office23:59

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