Tuesday, 2014-12-02

*** russellb has joined #openstack-relmgr-office00:04
*** david-lyle is now known as david-lyle_afk01:03
*** asalkeld has left #openstack-relmgr-office04:29
*** flaper87 has quit IRC08:20
*** flaper87 has joined #openstack-relmgr-office08:20
* mikal lurks09:06
*** ttx has left #openstack-relmgr-office09:06
*** ttx has joined #openstack-relmgr-office09:07
ttxoops.09:07
ttxwaiting for asalkeld, looks like a miss.09:07
mikalIsn't nova now?09:09
mikalOr am I confused?09:09
ttxit's in one min09:09
ttxSchedule at https://wiki.openstack.org/wiki/Release_Cycle_Management/1:1_Syncs09:09
ttxzz_johnthetubagu: around ?09:10
ttx#startmeeting ptl_sync09:10
openstackMeeting started Tue Dec  2 09:10:33 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.09:10
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:10
openstackThe meeting name has been set to 'ptl_sync'09:10
ttxLet's wait for John or Angus :)09:11
mikalWorks for me09:11
mikalI'm just lurking really09:11
mikalI see this as a John meeting now09:11
*** zz_johnthetubagu is now known as johnthetubaguy09:15
ttxjohnthetubaguy: o/09:16
johnthetubaguyttx: hey, sorry, bit late out the shower this morning09:16
ttxNo pb09:16
ttx#topic Nova09:16
ttx#link https://launchpad.net/nova/+milestone/kilo-109:17
ttxTwo weeks to milestone09:17
johnthetubaguyyeah, I didn't do the pushing out of stuff thats not in review yet09:17
johnthetubaguyI should do that this morning09:17
ttxTime to push back the stuff obviously not started, at least09:17
mikalI think some of the stuff marked as in review is actually implemented09:17
mikalhttps://blueprints.launchpad.net/nova/+spec/hyper-v-host-power-actions for example09:17
* ttx checks09:17
johnthetubaguymikal: yeah, I plan to do a sweep, people tend not to update there blueprints much09:18
ttxor anti-affinity-on-migration09:18
ttxwell, if our system was fully integrated, they wouldn't need to09:18
ttxvmware-spbm-support might be completed too09:19
johnthetubaguyttx: agreed09:19
johnthetubaguyabout the middle statement, need to check the others09:19
ttxprotip: I use http://status.openstack.org/release/ to spot them09:20
ttxblueprints that have all green dots have all the linked reviews in09:20
ttxthat doesn't mean they are complete, but they are generally good candidates09:20
*** asalkeld has joined #openstack-relmgr-office09:20
johnthetubaguyttx: not see that one before, neat09:20
ttxThe report actually fetches reviews that are linked from the blueprint whiteboard and gets status from them09:21
ttxso it relies on a weak association (gerrit adding a note to the whiteboard)09:22
ttxbut it's better than nothing09:22
mikaljohnthetubaguy: https://blueprints.launchpad.net/nova/+spec/log-request-id-mappings is interesting. The outstanding review at the end is an unapproved spec, I think that one shouldn't be approved?09:22
johnthetubaguymikal: its not approved, as such09:23
mikalOh, pending approval09:23
mikalThe "approver" being set confused me09:23
ttxremember that the blueprint page is now more of an external communication tool, so deferring a BP to k2 is just saying "that's where it looks like it will land". We can move the BP back to k1 if it suddenly makes progress09:23
johnthetubaguymikal: I don't reset that one when I un approve, takes too long09:23
mikalFair enough09:24
johnthetubaguyttx: yeah, agreed09:24
mikalWe should definitely unassign milestones for the unapproved specs then09:24
ttx"this is our best guess at what's coming in the short term"09:24
mikalWhich is ttx's script, yes?09:24
johnthetubaguymikal: they mosty are, its the ones that got into kilo, somehow, that mess things up :(09:24
ttxmikal: well, sometimes you're pretty sure the spec will make it, so you still want to track it as a milestone objective09:25
ttx(we mark them as blocked)09:25
ttx(but don't think that's the case for this one)09:25
mikalAnother one is https://blueprints.launchpad.net/nova/+spec/nova-pagination -- most recent review is a spec, is marked approved.09:25
mikal(I read the right field this time)09:25
johnthetubaguyttx: I keep wondering about doing that for stuff related to priority blueprints, so its easier to track the spec reviews, but not done that09:25
johnthetubaguymikal: not done my friday updating of specs yet09:26
ttxyes, sounds like a good way to track "priority blueprints"09:26
ttxlets them emerge from noise09:26
ttxjohnthetubaguy: I'll let you update the list off-sync09:27
johnthetubaguyyeah, meant to do that yesterday, but I am slammed right now :(09:27
ttxFor the meeting today, remember it's a cross-project meeting and we announce it the day before now... so if you have topics to discuss, you should post them beforehand09:28
ttxdirectly on https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting09:28
ttxwe'll discuss "Convergence on specs process" today09:28
ttxwhich you proposed last week09:28
johnthetubaguyyeah… not done the ground work for that, but I can add some links to nova things09:29
ttxjohnthetubaguy: anything else ?09:29
johnthetubaguyttx: nothing from me09:29
ttxjohnthetubaguy: ok, ttyl!09:29
ttxasalkeld: still around ?09:29
asalkeldhi09:29
ttxmikal: thanks for lurking!09:30
asalkeldsorry i missed09:30
ttxasalkeld: np09:30
ttx#topic Heat09:30
mikalttx: NP, although I feel I said too much09:30
ttxmikal: you should improve your lurking.09:30
ttxhttps://launchpad.net/heat/+milestone/kilo-109:30
ttx2 weeks to go, this looks in relatively good shape09:31
asalkeldyeah09:31
ttxAll started, most done or in review09:31
asalkeld2 to follow up on09:31
asalkeldthe "started" ones09:31
asalkeldthe patches are in review, i'll try see what is going on with those09:31
ttxyes, you should basically defer them to k2 once you're convinced they won't make it in k109:31
asalkeldok, makes sense09:32
ttxas I told John before, the idea is to use those pages to communicate when things are likely to land09:32
asalkeldsure09:32
ttxmostly to people external to your project09:32
ttxour best guess09:32
asalkeldyeah, i'll ping the author of those 2 bp's and see what's happening09:33
asalkeldwe are doing a bug cleanup today09:33
ttxasalkeld: nice09:33
asalkeldso we are having quite a bit of bug changes09:33
ttxNo other questions from me, did you have any ?09:33
asalkeldtrying to figure out what is happening with old bugs09:33
asalkeldttx, no all good from my pov09:33
ttxasalkeld: awesome, thanks for your time!09:34
asalkeldnp09:34
*** asalkeld has left #openstack-relmgr-office09:35
*** thingee has quit IRC10:24
*** thingee has joined #openstack-relmgr-office10:27
*** thingee has quit IRC10:49
*** thingee has joined #openstack-relmgr-office10:51
*** thingee has quit IRC12:50
*** thingee has joined #openstack-relmgr-office12:52
*** eglynn has joined #openstack-relmgr-office12:55
eglynnttx: knock, knock ... ready when you are13:00
ttxeglynn: o/13:01
ttx#topic Ceilometer13:01
eglynn#link https://launchpad.net/ceilometer/+milestone/kilo-113:01
eglynnfurther progress on the kilo-1 roster13:01
eglynn... but still a couple of BPs blocked on specs landing13:01
ttxnice progress13:01
eglynnI'm most concerned about instance-autorestart13:01
eglynnsince there hasn't been much recent traction on the reviews13:01
eglynnI've emailed the author13:01
ttxwell, two more weeks13:02
eglynn(she doesn't normally hang out on IRC)13:02
eglynnyeap13:02
ttxOnce you're reasonably sure it won't make it, just move it to the k2 roster13:02
eglynnyeap, will do13:02
ttxThe two Blocked are waiting for spec to be approved, right?13:02
eglynnyep13:02
eglynnthere are enough stake-holders in the other blocked spec (RBAC) to ensure it'll land, IMO13:03
ttxIs that likely to happen soon?13:03
eglynnyeah, the rbac one is mostly a question of careful scoping13:03
ttxok13:03
ttxcareful speccing :)13:03
eglynn(it currently includes some language about keystone v3 domains which are unused in the actual implementation)13:03
ttxLooks like you're in great shape, no other question from me13:04
eglynncool13:04
eglynn2014.2.1 due out this week also13:04
ttxyes, we'll mention it during the meeting today13:04
eglynn#link https://launchpad.net/ceilometer/+milestone/2014.2.113:04
ttxso... 5 backports you'd like to include in it ?13:04
eglynnyeap, I've a 5 freeze exceptions requested, but happy to go with just the landed backported if necessary13:05
eglynnlanded *backport13:05
eglynnlanded *backports13:05
ttxok, I suspect they are all on apevec radar ?13:05
eglynnyeap, on the etherpad, spoke to him about it this morning13:05
ttxok great13:06
ttxOther questions ?13:06
eglynnnope, nothing else from me13:06
ttxeglynn: ok, have a great day then13:06
eglynncool, thanks for your time!13:06
ttxSergeyLukjanov: ready when you are13:06
SergeyLukjanovttx, ready13:07
SergeyLukjanovttx, hi13:07
ttx#topic Sahara13:07
SergeyLukjanov#link https://launchpad.net/sahara/+milestone/kilo-113:07
ttxhttps://launchpad.net/sahara/+milestone/kilo-113:07
ttxnice green13:07
SergeyLukjanovttx, mostly all of the features are now in review/gating state13:07
ttxchecking for some completion13:08
ttxevent-log might be completed already ?13:08
SergeyLukjanovhttps://blueprints.launchpad.net/sahara/+spec/indirect-vm-access is implemented, but spec isn't completely approved13:09
ttxexceptions-improvement might be completed too13:09
SergeyLukjanovevent-log will be most probably postponed to kilo-2, too many patch sets to review13:09
ttxoh ok13:09
SergeyLukjanovexceptions-improvement already implemented13:09
ttxSergeyLukjanov: ok13:10
ttxmy script ran a few minutes ago :)13:10
SergeyLukjanovttx, :)13:10
ttxYour buglist looks a bit wide13:10
ttxlike, too many unassigned things13:10
ttxAre they all bugs you intend to fix before k1 ?13:10
SergeyLukjanovttx, I think nope, need to bug scrub them13:11
SergeyLukjanovthere are some very low prio or on-going things13:11
ttxok13:11
ttxFor the meeting today, remember it's a cross-project meeting and we announce it the day before now... so if you have topics to discuss, you should post them beforehand13:11
ttxdirectly on https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting13:12
ttxThat's all I had. Questions ?13:12
SergeyLukjanovttx, yup, thanks for the reminder13:12
SergeyLukjanovttx, I have a small note - we're migrating to the data-processing endpoint type13:12
SergeyLukjanov(from data_processing)13:12
SergeyLukjanovfor consistency13:12
ttx#info migrating to the data-processing endpoint type (from data_processing) for consistency13:13
SergeyLukjanovthat's all from my side13:13
ttxdoes that break existing users ?13:13
SergeyLukjanovttx, nope, client has backward compat handler13:13
ttxok13:14
ttxSergeyLukjanov: thx!13:14
SergeyLukjanovttx, tempest and devstack are configurable13:14
SergeyLukjanovttx, thx!13:14
ttxdhellmann: ready when you are13:14
dhellmannttx: hi!13:14
ttx#topic Oslo13:14
ttxo/13:14
ttxhttps://launchpad.net/oslo/+milestone/kilo-113:14
ttxhttps://launchpad.net/oslo/+milestone/next-kilo13:15
dhellmanna couple of those for k1 are going to need to move to k2, but we have a review sprint on the 4th so I'd like to wait and see how far we get then before I move them13:15
dhellmanncertainly that one that's blocked can move now13:15
ttxok13:15
ttxdhellmann: for the oslo.rootwrap release, do I need to do anything ?13:16
ttxI'm fine running the script if you walk me through it13:17
dhellmannyou wrote the script! :-)13:17
ttxah. Hm.13:17
dhellmannheh13:17
ttxthere is some extra things to do though iirc13:17
dhellmannI can do it, if you're busy, but I thought I'd check with you before13:17
dhellmannoh, yeah, the new release notes script13:17
ttxyes, that;13:17
dhellmannoslo-incubator/tools/release_notes.sh13:18
ttxok, will try to run that today13:18
dhellmannhttp://git.openstack.org/cgit/openstack/oslo-incubator/tree/tools/release_notes.sh13:18
ttxwill ping you if I have issues13:18
dhellmannthat generates most of the body of the email you'd send to -dev13:18
dhellmannsure, let me know if you run into trouble13:18
ttxit's usually a good thing to get more people to run your scripts :)13:19
dhellmannI'll take it off of my list13:19
dhellmanndefinitely13:19
ttxwill try to do it today, otherwise first thing tomorrow. Will that work ?13:19
dhellmannbnemec found some issues with my release process directions (I forgot about having to auth with launchpad)13:19
dhellmanntoday or tomorrow is fine. I would wait until next week if you can't do it tomorrow, but that depends on whether you're available for the weekend to solve problems.13:19
ttxok13:20
ttxThat's all I had... question on your side ?13:20
ttx+s13:20
dhellmannI'm approving some specs, and discovering that the filenames don't match blueprint names13:20
dhellmannhow hard is it to check for that sort of thing in the gate? if I wrote a script, are there credentials for the jenkins user?13:21
ttxhmm, Gerrit has, since it runs a number of bug/blueprint updates13:21
ttxnot sure about Jenkins those days13:22
dhellmannactually, I wonder if I could run a query without authenticating13:22
ttxthere was one for sure13:22
ttxyou probably could.13:22
dhellmannI just need to know if a blueprint exists matching the filename, I don't have to change it13:22
dhellmannok, I'll experiment with that13:22
ttxanonymous is a lot simpler13:22
dhellmanndo you have any rootwrap reviews you want us to prioritize for the sprint?13:23
ttxno, the roster is pretty empty13:23
ttxthe next stage is to get neutron to use the new daemon mode stuff13:23
dhellmannok, good. I'm looking forward to seeing how far we can get with clearing out our backlog13:23
dhellmannah, is there a bp for that work?13:23
ttxthe guy who was working on it moved to something else13:24
dhellmannfigures13:24
ttxsomeone else proposed to take it over13:24
ttx(in neutron)13:24
ttxlet me check if there is a spec for it13:24
ttxBlueprint would be https://blueprints.launchpad.net/neutron/+spec/rootwrap-daemon-mode13:25
ttxYuriy moved on, Miguel proposed to take it over13:25
* dhellmann nods13:27
ttx(Miguel Angel Ajo Pelayo)13:27
ttxcan't find spec13:27
ttxhmm13:27
ttxhttps://review.openstack.org/#/c/93889/13:28
ttxactually in better shape than I thought13:28
ttxI think there is potential in future oslo.rootwrap to include some of the client code, as it will be a bit common among consumers13:29
dhellmannmakes sense13:29
ttxbut I'd like to let neutron shape it13:29
ttxso that would be the next step for oslo.rootwrap, but today it's blocked13:29
ttxanything else ?13:30
dhellmannnothing from me this week13:30
ttxshouldn't "tooz adoption" be "Implemented" now ?13:30
dhellmannwas that done?13:30
ttxfeels like all things merged13:30
ttxat least the two reviews linked in the bp13:31
dhellmannthe repo needs to be renamed I think13:31
ttxah! ok13:31
dhellmannI added a work item and set the status to "slow progress" to nudge jd__13:32
dhellmannwe might actually be waiting for infra to schedule downtime, and if that's true I'll set it to blocked13:32
ttxor "needs infra"13:32
ttxwhich is like the best use ever for this status13:32
dhellmannhaha, yeah, updated13:33
ttxok, have a good day!13:33
dhellmannyou, too!13:33
*** zbitter is now known as zaneb13:45
*** thingee has quit IRC13:57
*** thingee has joined #openstack-relmgr-office13:58
*** kiall_ has joined #openstack-relmgr-office14:28
*** thingee has quit IRC14:50
*** thingee has joined #openstack-relmgr-office14:53
*** kiall_ is now known as Kiall14:55
*** Kiall has quit IRC14:55
*** Kiall has joined #openstack-relmgr-office14:55
mesteryttx: Here and at the ready sir.15:05
ttxmestery: o/15:06
ttx#topic Neutron15:06
ttxhttps://launchpad.net/neutron/+milestone/kilo-115:07
ttxso.. only 4 ?15:07
mesteryYEs, it looks very low I know15:07
mesteryWe have been reviewing some huge BPs this cycle, and most are landing for Kilo-215:07
mesteryThe refactoring is taking a lot of review time in the specs process15:08
ttxok, nothing will just get spec-approved and fasttracked in ?15:08
mesteryThe team is spending the time up front to make sure things go smoothly15:08
mesteryThere may be a few yet, I'm talking to some folks today/tomorrow15:08
mesteryThe flavors stuff may15:08
ttxwell, I won't mind a peak at k2, that would change from the usual x3 peak15:08
mesteryAnd some of the core refactoring will be done next week, so may land yet in Kilo-115:09
mesteryRight15:09
mesteryThat's our hope15:09
ttxas long as the page reflects what you think will get done, that's good15:09
ttxanyone working on https://bugs.launchpad.net/bugs/1323658 ?15:09
* mestery looks15:09
mesteryNot at the moment no, we've worked on this one off and on for a while now.15:10
ttxwas rtated critical adn targeted, although it's hardly new15:10
mesteryRight15:10
mesteryI know me, salv, and armax have spent time on it off and on during Juno15:10
mesteryI can priortize this one again15:10
ttxmaybe that can be downgraded to high, and removed from milestone until someone is assigned to it ?15:11
mestery++15:11
ttxcurrently it looks as if it's a milestone-critical issue without an assignee :)15:11
ttxwhich triggers all kind of weird flags15:12
mestery:)15:12
mesteryDone15:12
ttxbut if it survived the last 6 months it hardly qualifies at critical in my book15:12
mestery++15:12
mesteryAt various times it's been a nova and/or neutron issue.15:12
ttxis there more to do on drop-rpc-compat ?15:12
ttxI see 5 landed changes15:13
mesteryYes, I spoke to russellb today, he has a few patches left, it should land in Kilo-1 though.15:13
ttxok15:13
ttxthat's all I had15:13
ttxremember to file your topics for the cross-project meeting ahead of this sync now that it is cross-project we need to announce agenda with a bit of advance notice15:14
mestery++15:14
mesteryThanks for the reminder ttx15:14
ttxpage is https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting15:14
ttxthat's all I had15:14
ttxquestions on your side ?15:14
ttxoh. How are the new repos coming up ?15:15
mesteryThey are coming.15:15
mesteryWe have some new plugin repos approved15:15
mesteryAnd the services ones will be done next week while at the mid-cycle15:15
mesteryWe have a spec close to approval there15:15
ttxwe didn't discuss impact for release management15:15
mesterySo we can do the work next week15:15
ttxwhat release model would that use ?15:16
ttxI remember not panicking reading the original email, so maybe that was covered there15:16
mesteryThere are notes in the spec on that, let me grab the link, would be good to get your commenst in gerrit15:16
ttx++15:16
mesteryhttps://review.openstack.org/#/c/136835/15:17
ttxok, will read and comment there15:17
ttx#action ttx to read and comment on split spec https://review.openstack.org/#/c/136835/15:17
mesteryThanks ttx!15:17
ttxthanks, have a great day !15:17
*** nikhil_k|vacay is now known as nikhil_k15:18
ttxnikhil_k: ready when you are15:18
nikhil_kttx: o/15:18
ttx#topic Glance15:18
ttxhttps://launchpad.net/glance/+milestone/kilo-115:18
ttxAll appear to be in review15:18
ttxstore-capabilities is missing a priority15:19
ttxI guess that was a recent addition15:19
ttxyep, 4 hours ago15:19
nikhil_kttx: yeah, was at vacation past few days and could not get a chance to look into it15:19
nikhil_kthere may be 1 more15:19
nikhil_kor 2 (small ones)15:19
nikhil_kwill take a look at this today/tomorrow15:20
ttxsounds good15:20
ttxThings look in good shape oevrall. Will PM you about security issue when we are done15:20
ttxquestions on your side ?15:20
nikhil_k:)15:21
nikhil_knothing, still catching up15:21
ttxok then, I won't keep you more15:22
*** thingee has quit IRC15:22
*** david-lyle has joined #openstack-relmgr-office15:23
ttxdavid-lyle: we can talk now if you want, or you can go at your usual time (in 15min)15:25
david-lylettx: now is fine15:26
ttx#topic Horizon15:26
ttxhttps://launchpad.net/horizon/+milestone/kilo-115:26
ttxA few undefined/unknown to clear up there15:26
ttxbut otherwise looks good15:26
ttx2 weeks from target15:26
david-lyleyes, most work is on track15:27
ttxinstance-details-add-host-server is missing an assignee too15:27
david-lyleI may just pick that up, it's a fairly small change15:27
ttxok15:28
david-lylewas waiting to see if the author of the bp started work15:28
ttxis separate-horizon-from-dashboard still likely to land for kilo-1 ?15:28
ttxtrying to anticipate the release artifact impact15:29
david-lyleI doubt it. More likely early K-215:29
david-lyleI'll confirm in the Horizon meeting and move if my inclination is correct15:30
ttxsounds good15:30
ttxhorizon_lib would be published a library on Pypi ?15:30
ttxas a*15:30
david-lyleyes, there is still some contention around naming15:30
david-lylewhich seems to be the main roadblock15:31
ttxok, so I guess apart from making the release artifact smaller, that shouldn't affect release management that much15:31
david-lyleno, just adding another dependency really15:31
ttxThat's all I had. Questions on your side ?15:32
david-lyleare you aware of any issues with the icehouse and juno neutron gate jobs?15:32
david-lyleI can raise in infra as well15:33
ttxhmm, nothing in particular -- which doesn't mean there isn't one.15:33
* ttx gave up on knowing everything a few years ago15:33
*** thingee has joined #openstack-relmgr-office15:34
ttxdavid-lyle: anything else ?15:34
david-lyleno worries, I'll continue to try and track down the cause15:34
david-lyleno I'm good15:34
ttxdavid-lyle: ok, have a great day!15:34
ttxthingee: around?15:34
david-lylettx: thanks, you too15:35
thingeettx: sorry was having connection problems here15:35
ttx#topic Cinder15:35
ttxthingee: np15:36
ttxhttps://launchpad.net/cinder/+milestone/kilo-115:36
thingeenow tethered to my phone :)15:36
ttxdid you get to the bottom of the "not started" stuff ?15:36
ttxonly two weeks to go, so I suspect they should at least have started work15:37
ttxespecially the brand-new drivers :)15:37
ttx...15:38
thingeeI have sent emails out, but haven't heard back from people. Going to be punting things this week.15:40
thingeeSame goes for drivers from people that haven't responded back to my emails.15:40
thingeeshould be a smaller list the next time we talk15:41
thingeeagreed15:41
thingeeI've been making a point to tell people this is your only chance for Kilo, so no surprises.15:41
thingeemercy there is a lot :)15:41
thingeewe finally got another one merged last week. there are others that are close.15:41
thingeethat's it for me.15:41
ttxok great15:41
ttxthingee: no more questions from me15:41
ttxthingee: have a godo day15:42
ttxgood*15:42
thingeeyou too15:42
thingeeevening that is :)15:42
*** david-lyle has quit IRC15:50
*** thingee has quit IRC16:11
*** Kiall has quit IRC16:13
*** kiall_ has joined #openstack-relmgr-office16:13
*** kiall_ has quit IRC16:13
*** thingee has joined #openstack-relmgr-office16:13
*** Kiall has joined #openstack-relmgr-office16:14
*** Kiall is now known as Guest699216:14
*** Guest6992 has quit IRC16:15
*** Guest6992 has joined #openstack-relmgr-office16:15
*** Guest6992 is now known as Kiall16:16
*** Kiall has quit IRC16:24
*** Kiall has joined #openstack-relmgr-office16:25
*** Kiall is now known as Guest4528616:26
*** thingee has quit IRC16:26
*** thingee has joined #openstack-relmgr-office16:26
*** Guest45286 has quit IRC16:35
*** Guest45286 has joined #openstack-relmgr-office16:35
*** Guest45286 is now known as Kiall16:35
*** david-lyle has joined #openstack-relmgr-office16:49
*** david-lyle has quit IRC16:49
ttxnotmyname: ready when you are16:49
notmynamettx: good morning/evening16:49
ttx#topic Swift16:49
notmynameI see you put me on the project meeting schedule16:49
notmynameabout client dev work16:50
notmynamewhat do you want to cover there?16:50
ttxwell, you and morganfainberg16:50
notmynameright16:50
notmynamesummary or ....?16:50
ttxI want to discuss the approach, see if there is a trend there16:50
notmynameok16:50
ttx(I think there is)16:50
notmynamegreat. looking forward to it16:50
ttxIt's more of a "should other projects also consider it if they find themselves in the same situation" thing16:51
notmynamehonestly the one thing that concerns me about "openstack-sdk" is the one-tool thing. trying to make one tool that works for all the openstack projects.16:51
notmynameok16:51
ttxplanning christmas holiday -- do you plan a swift release before end of year ?16:52
notmynamebut I want to address that if/when it's a problem16:52
notmynameI was just looking at that16:52
ttxor rather January+16:52
*** david-lyle_afk is now known as david-lyle16:52
notmynamewe could either do something the week of the 15th (2 weeks from now) or we could wait until january. we haven't had anything major land, just a lot of smaller fixes16:52
notmynamewhat works best for you?16:52
ttxShould be around that December week. Your call16:53
ttxEarly in Jnaury works too. Maybe we can wait one more week and see how it goes ,16:54
ttx?16:54
ttxJust avoid the weeks of the 22 and the 2916:54
ttx:)16:55
notmynamettx: ok, let's propose 2.2.1 RC between dec 11 and 15 and final by the end of the week. does that work?16:55
ttxThat works. I should be around on the 22nd if we need to push it then.16:55
notmynameok, great16:55
notmynameI'll put it on the agenda for tomorrow's swift meeting16:55
ttx#info proposed plan to do 2.2.1 RC between dec 11 and 15 and final by the end of the week16:55
ttxnotmyname: great, thx16:56
notmynameanything else?16:56
ttxnothing from me16:56
notmynameok, thanks.16:56
ttxhave a great day!16:56
notmynameyou too16:56
ttxmorganfainberg: ready when you are16:56
morganfainbergttx: mostly here.16:56
morganfainberg:)16:56
ttx#topic Keystone16:56
ttxmorganfainberg: turkey issues ?16:57
ttxhttps://launchpad.net/keystone/+milestone/kilo-116:57
morganfainbergPost holiday crud issues. Yay family! ;)16:57
ttxtoken-provider-cleanup -> not started, still on track for dec 18 ?16:57
morganfainbergToken provider cleanup is being punted to k216:58
ttxok16:58
ttxthe rest looks reasonable16:58
morganfainbergHm is being merged / has been merged to master with 1-2 outstanding patches.16:58
morganfainbergThat are being rebased today.16:58
morganfainbergI'll sweep through and make sure nothing else is missing.16:59
ttxmorganfainberg: remember we'll discuss the technique of openstack-sdking your incompatible client changes at the cross-project meeting today at 21:0016:59
ttx(utc)16:59
morganfainberg++16:59
ttxnothing else from me16:59
ttxquestions ?16:59
morganfainbergNoting else on this end.16:59
ttxalright then16:59
ttxhave a good day!16:59
morganfainbergNext week though I will be delegating this to Dolph16:59
ttxthat is a fine thing to do17:00
dolphm\o/17:00
morganfainbergWanted you to have a heads up17:00
dolphmeek, i won't be available next tuesday, probably at all17:00
ttxI'll prepare myself17:00
ttxit's fine to skip17:00
morganfainbergOk I will find someone else or let you know we have a skip17:00
ttxack17:01
ttxdevananda: around ?17:01
devanandattx: g'morning!17:01
ttxdevananda: fine with syncing a bit early ?17:02
devanandasure17:02
ttx#topic Ironic17:02
ttxhttps://launchpad.net/ironic/+milestone/kilo-117:02
ttxso.. elephant in the room17:02
ttxnew-ironic-state-machine, how is the spec going ? Who will be working on that ?17:03
devanandaright now, everyone is17:03
devanandawe have a bit of too-many-cooks-spoiling-the-soup going on, IMO17:03
devanandaI spent most of yesterday, and will probably spend several hours today, trying to sort this out with the team17:04
ttxok17:04
devanandawe also have several things slated for k2, k3 which depend on this17:04
ttxeverything else looks good17:04
devanandagetting progress on that is going to be my main focus for a bit17:05
ttxno more questions from me -- did you have any ?17:05
devanandahmm. nope!17:05
devanandajust one comment - the new spec2bp is fantastic17:05
ttxthe v2 one ?17:06
devanandaya17:06
ttxfeel free to +1 it :)17:06
devananda:)17:06
ttxAlso remember to file your topics for the cross-project meeting ahead of this sync now that it is cross-project we need to announce agenda with a bit of advance notice17:06
devanandaah, thanks17:07
ttxthat's all I had.17:07
ttx(agenda for crossproject lives at https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting)17:07
devanandai dont think i have any cross-project agenda items, but appreciate the reminder17:07
ttxI just won't be asking for topics during the sync anymore17:07
ttxso just edit the wiki yourself17:07
devananda:)17:07
ttxdevananda: have a great day!17:07
ttxSlickNik: ready when you are.17:08
SlickNikttx: o/17:09
ttx#topic Trove17:09
ttxhttps://launchpad.net/trove/+milestone/kilo-117:10
SlickNikI'm working on cleaning up the BPs/bugs targeted to kilo-117:10
ttxwell, that sounds rather reasonable to me already17:10
ttx2 weeks leftr, so next week it will probably be unreasonable to keep in k1 stuff not proposed for review yet17:11
SlickNikThere are a few bugs that I know won't make it that I'd like to move to k2.17:11
SlickNikYes, exactly.17:11
ttxthe idea being, to use that page to communicate what you think will happen, to the best of your prediction abilities17:11
ttxSlickNik: your status looks good at this point, I don't really have more questions17:12
ttxQuestions on your side ?17:13
SlickNikttx: None from my side either.17:13
ttxSlickNik: alright then, quick and easy17:13
ttxhave a great day!17:13
SlickNikttx: Thanks — see you at the cross project meeting!17:13
ttxsee you there!17:14
ttx#endmeeting17:14
openstackMeeting ended Tue Dec  2 17:14:05 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:14
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-12-02-09.10.html17:14
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-12-02-09.10.txt17:14
openstackLog:            http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-12-02-09.10.log.html17:14
morganfainbergttx: let's assume a skip on next week keystone.17:16
ttxmorganfainberg: ok17:16
morganfainbergttx: I'll be in austin talking with Mark collier and jontathan. So figure I prob won't be online as much.17:16
morganfainbergI'll make sure some keystone cores at the project meeting (fiairly certain bkundson is there anyway)17:18
morganfainbergThat week that is to say.17:18
*** eglynn has quit IRC18:30
*** johnthetubaguy is now known as zz_johnthetubagu19:13
*** Kiall has quit IRC19:18
*** Kiall has joined #openstack-relmgr-office19:18
*** Kiall is now known as Guest4042519:18
*** Guest40425 has quit IRC19:36
*** Kiall_ has joined #openstack-relmgr-office19:37
*** Kiall_ has quit IRC19:42
*** Kiall_ has joined #openstack-relmgr-office19:42
*** thingee has quit IRC19:49
*** thingee has joined #openstack-relmgr-office19:49
*** asalkeld has joined #openstack-relmgr-office20:53
*** asalkeld has left #openstack-relmgr-office22:00
*** thingee has quit IRC23:47
*** thingee has joined #openstack-relmgr-office23:47

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