Tuesday, 2014-08-19

*** arnaud__ has quit IRC02:01
*** morganfainberg is now known as morganfainberg_Z02:14
*** arnaud has quit IRC02:35
*** arnaud has joined #openstack-relmgr-office02:41
*** markmcclain has quit IRC03:24
*** Azher has joined #openstack-relmgr-office03:42
*** arnaud has quit IRC05:00
notmynamettx: I will be available as close to our sync time as possible, but if I'm a few minutes late I'll preemptively blame SF Muni. but I will be online, and I've got a proposed rest-of-juno plan to go over with you05:12
*** arnaud has joined #openstack-relmgr-office05:26
*** arnaud has quit IRC05:31
*** morganfainberg_Z is now known as morganfainberg05:41
*** arnaud has joined #openstack-relmgr-office06:04
*** arnaud__ has joined #openstack-relmgr-office06:16
*** arnaud has quit IRC06:40
*** arnaud__ has quit IRC06:40
ttxnotmyname: ack06:58
mikalttx: we're on for a 1:1 in a minute?07:57
* ttx grabs a coffee07:57
mikaljohnthetubaguy: le ping07:57
ttxmikal: yes07:57
mikalCool07:57
ttxok08:01
ttx#startmeeting ptl_sync08:01
openstackMeeting started Tue Aug 19 08:01:24 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.08:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:01
openstackThe meeting name has been set to 'ptl_sync'08:01
ttx#topic Nova08:01
mikalHi08:01
ttxhi!08:01
ttx#link https://launchpad.net/nova/+milestone/juno-308:01
mikalSo, I emailed openstack-dev and mentioned in our meeting last week that we should be reviewing the high prio ones08:02
mikalThere's been some review, but none have landed08:02
mikalThe object ones look good to me08:02
mikalAs does the ironic one08:02
ttx#info 3 implemented, 36 in review, 23 in progress, 10 not started/unknown08:02
mikalThe scheduler one is going slow, as is vmware08:02
ttxLast week you had 2 Implemented, 33 under review, 27 in progress and 11 Not started/Unknown08:03
mikalScheduler is slow because of review attention (or the lack of it)08:03
mikalVMWare is because minesweeper is broken08:03
* mikal is confused that not-started has grown08:03
ttxit went down by 108:03
mikalOh, I see08:04
mikalOther order08:04
ttxyep08:04
mikalSo, I am worried that we're not landing enough BPs08:04
mikalBut I am unsure what else to do apart from personally reviewing all the code08:04
ttxmaybe single out a few blueprints that are 99% there, in addition to High/Essential stuff?08:05
ttxdo you feel like the call to focus on High prio worked?08:06
mikalTo be honest no08:06
mikalSome got reviews08:06
mikalBut it feels like thigns which were being reviewed already08:06
mikalI haven't generated any data on it though, its more an instinct08:06
ttxthis week the focus is obviously on FPF which shall hit on Thursday08:07
mikalThat's possibly true08:07
mikalPeople frantically finishing their own things instead of reviewing08:07
ttxtheer are 33 blueprints that will disappear from the list at this point08:07
mikalOr will be finished in time...08:08
mikalNot all 33 will go away nessesarily08:08
ttxMaybe review prioritization will work better once we are past that08:08
mikalOne can hope08:08
mikalI don't know if this is a new problem or not08:08
mikalBut it feels like we're not focussing well08:08
ttxDo you think that blueprint proposers are well aware of the FPF deadline ?08:08
mikalHmmm08:09
mikalI am sure they could do with another reminder08:09
ttx(if they are not they will pile up exception requests)08:09
mikalI will send out a reminder after this 1:108:09
ttxyou can also clarify when "Thursday" will be08:10
mikalYep, presumably midnight Thursday UTC08:10
johnthetubaguymikal: ttx: morning08:11
johnthetubaguymikal: I often choose midnight pacific08:12
ttxAlso maybe contact (or have someone contact) the medium-prio blueprint holders that still don't have code proposed (there are 5 of them) to make sure they are aware of the deadline08:12
ttxjohnthetubaguy: the trick is you want extra time on Friday to handle the inevitable exception requests08:12
mikalI can email them as well08:12
johnthetubaguyttx: yes, good point08:12
johnthetubaguymikal: are we deleting the specs too?08:13
mikalI'm also travelling Friday my time through the weekend08:13
ttxmikal: you seem in good shape FPF-wise if you look at the prioritized list -- most of the things that would fall off the map are Low08:13
mikalBut I will tyr to keep on top of email as much as possible08:13
mikaljohnthetubaguy: we talked about kilo specs in the release meeting last week08:13
mikaljohnthetubaguy: the concensus seemed to be we should open kilo now, but I haven't done it08:13
mikaljohnthetubaguy: I guess we move the unimplemented specs from juno into an "unimplemented" folder when we do that?08:13
johnthetubaguymikal: I think we can propose a move, then drivers asses if we want that or not?08:14
mikaljohnthetubaguy: as in implied approval for kilo for juno specs?08:15
johnthetubaguymikal: no, as, a help to get approval for juno08:15
ttxjohnthetubaguy: clarifying the "unknown" statuses would also be a good idea before FPF -- some may just be proposed already08:15
mikaljohnthetubaguy: oh I see, as in have drivers vote on how we archive?08:15
johnthetubaguyttx: yeah, I need to sift through those, quite a few often have all their code up, but don't update too08:15
mikaljohnthetubaguy: I kind of feel like we don't need to bikeshed everything08:16
mikaljohnthetubaguy: archival could be just a ptl mandate or something08:16
* mikal is very tired of the flame wars at the moment08:16
johnthetubaguymikal: we agreed not to auto-approve, but I don't want to just delete the spec, thats all08:16
mikaljohnthetubaguy: yeah, I get that08:16
mikaljohnthetubaguy: so, no auto approval08:16
ttxmikal: my last question would be about the midcycle meetup. What do you think made it so much more productive compared to design summit08:16
johnthetubaguymikal: cool, so anything that meets that idea works for me08:16
mikaljohnthetubaguy: and juno approved specs which miss get moved to a "unimplemented" subdir in juno08:16
ttxis the the limited audience? the "stuck in one room" setup ?08:17
mikalttx: ahh, interesting question08:17
mikalI'm not sure I'd say "more" productive08:17
mikalCertainly more "focussed"08:17
mikalWe had elastic timeslots for topics08:17
mikalAnd could change the agenda based on what came up08:17
mikalPeople were focussed by there being no competing events08:17
mikalI don't think it replaces a summit08:18
mikalI do think they're important efficiency tools though08:18
ttxI'd like to fix the design summit so that it's more useful08:18
johnthetubaguymikal: thats a little like what we did with more unconference style slots in hong kong, that worked well08:18
johnthetubaguyttx: I think we need to get better at picking sessions08:18
mikaljohnthetubaguy: I felt the HK unconference slots were mostly just people who didn't get an accepted session though08:18
mikalAgreed08:18
mikalI think we also need to not run 8 hour days for nova08:19
ttxI think the main reason it was so badly needed this time around is that the design summit didn't work as well, so somethign was needed by mid-cycle (rather than 6 months after08:19
johnthetubaguymikal: yeah, but it meant we could reject more slots08:19
mikalI'd rather five half days than three full days for example08:19
mikalttx: I feel like Atlanta was as productive as other summits I've been to08:19
johnthetubaguyttx: we didn't spend enough time following through on the important stuff post summit, at least that was my feeling08:19
ttxI'm considering having some "open time" where we would not schedule specific "sessions"08:19
mikalIts more than six months is a long time without being able to sit down and solve the hard problems we get bogged down on in email08:19
johnthetubaguyttx: and maybe needed a bit more time on overarching topics, that no one proposed as a slot08:19
johnthetubaguyttx: mikal: and yeah, more face time is good, if we can get it08:20
mikalYeah, the approach was different08:20
mikalWe started with a list of important things08:20
mikalAnd then found people to speak to them08:20
ttxmikal: Like I said in my post, we can have more face time to work on specific issues, but ideally we would go over the cultural alignment at the summit, so that no extra travel is "required"08:20
mikalInstead of letting things people submitted define the agenda08:20
mikalSo maybe we should do that for Paris08:21
johnthetubaguymikal: yeah, we tried to do more of that in HKG summit picking, but yeah need to do more of that for paris08:21
mikalttx: yeah, I get that08:21
mikalI think perhaps its just where nova is at08:21
mikalIt feels like we have more contentious things happening now than we did a year or two ago08:21
mikalAnd face time is awesome for nailing down consensus08:22
mikalI'd be happy to replace the face time with something else08:22
mikalBut nothing else has been proposed that I think would work08:22
mikalWe don't even get most people to our IRC meetings08:22
ttxmikal: do you feel the audience can be an issue ? Having only key contributors in the room let you expose problems ?08:22
mikalThe mid-cycle was definitely better attended than our weekly IRC meetings08:22
mikalttx: we didn't filter attendees though08:22
mikalttx: we definitely had single issue people (merge my scheduler) in the room08:22
ttxmikal: right, it's filter by nothing else around08:22
ttxhmm08:23
mikalWell, I guess you could say its filter by travel budget08:23
mikalBut we could address that by asking the foundation for travel funding08:23
ttxIn the summits we just filter by "so many other interesting things around"08:23
mikalTrue08:23
johnthetubaguymikal: some people just couldn't make that date though08:23
mikalTrue08:23
ttxIt's not just budget08:24
mikalI don't think its great that we make people travel08:24
ttxit's also will to travel08:24
mikalWe just haven't found anything better yet08:24
mikalttx: have you seen the mid-cycle summary posts I'm doing by the way?08:24
ttxok, well, discussion to be continued08:24
mikalWe covered a _lot_08:24
ttxmikal: they are on my reading list. Just came back from a break yesterday08:24
mikalttx: heh, its a lot of text08:24
johnthetubaguyhonestly, more use of video chat for drivers would help08:24
ttxI expect to read them tomorrow.08:24
mikalttx: and I'm not done yet08:25
mikaljohnthetubaguy: yeah, I think trying to get drivers into a hangout is a good idea08:25
mikaljohnthetubaguy: scheduling is hard though08:25
johnthetubaguyttx: yeah, I just got back to work 20 mins ago08:25
ttxok well. I'll let you go back to work then :)08:25
johnthetubaguymikal: yeah, I think we need to alternate bad times or something08:25
ttxDiscussion to be continued08:25
mikaljohnthetubaguy: yep, like the IRC meetings08:26
ttxmikal, johnthetubaguy: anything to discuss at meeting today?08:26
mikalNup08:26
mikalNot that I can think of08:26
johnthetubaguynothing from me08:26
ttxmikal, johnthetubaguy: OK, thanks! Talk to you later08:26
mikalThanks!08:26
*** Azher has quit IRC10:59
ttxSergeyLukjanov: around?12:04
*** sdague has joined #openstack-relmgr-office12:04
SergeyLukjanovttx, yup12:06
SergeyLukjanovmorning12:06
ttx#topic Sahara12:06
ttx#link https://launchpad.net/sahara/+milestone/juno-312:07
ttx#info 6 implemented, 3 in review, 3 in progress, 2 not started12:07
ttx(compared to 2 implemented, 4 udner review, 8 in progress, 1 not started last week)12:08
ttxSo that's a pretty good landing rate12:08
ttxhttps://blueprints.launchpad.net/sahara/+spec/swift-url-proto-cleanup-deprecations in unassigned12:08
ttx(and not started)12:08
SergeyLukjanovyup, a bunch of long going things ended12:09
SergeyLukjanovit's very simple thing, mostlycleanup12:09
SergeyLukjanovit'll be discussed on the meeting this week12:09
ttxLast week you said you might make use of FPF to kick out stuff that's not proposed -- given your progress so far I don't think that's really necessary12:10
ttx(FPF is in two days)12:10
SergeyLukjanovagreed12:10
ttxhttps://blueprints.launchpad.net/sahara/+spec/edp-swift-trust-authentication is progressing well?12:11
SergeyLukjanovI think yes, it's going well12:11
ttxOK, you seem to have a good handle on things. Please assign someone to swift-url-proto-cleanup-deprecations soon, so that we know who to blame12:12
ttxAnythign you want to discuss at meeting?12:12
SergeyLukjanovI think nope12:13
SergeyLukjanovI'll assign someone on it this week12:13
ttxSergeyLukjanov: ok great. talk to you later, then12:14
SergeyLukjanovthx12:14
*** gordc has joined #openstack-relmgr-office12:14
ttxgordc: hi! let me know when you're ready12:20
gordcttx: hey, just pulling up eglynn's email. i'm available now.12:22
ttx#topic Ceilometer12:22
ttxgordc: Thanks for coming so early12:23
ttx#link https://launchpad.net/ceilometer/+milestone/juno-312:23
gordcnp. metro was running on time. :)12:23
ttx#info 3 implemented, 5 under review, 3 in progress12:23
gordcso we hashed out all our bps for juno3... they've all been started or have code up for review12:23
ttxLast week it was 2 implemented, 4 under review, 6 in progress12:23
gordcone low priority item (https://blueprints.launchpad.net/ceilometer/+spec/ipmi-support) yet to have code posted by eoghan followed up over the weekend and the item is apparently complete internally and they will post code soon (i will check with llu again since it's an intel bp)12:24
ttxSo that's good progress12:24
gordcyep. we had a few code items (specifically xenapi bp) added recently.12:24
gordclast meeting, we decided pushed gnoochi/ceilometer dispatcher work to post-juno as we didn't have resources and gnocchi work remains decoupled from ceilometer work.12:25
ttx#info Juno-3 progress looks good12:25
gordcone issue that came up was grenade work. Chris Dent is working on that item and is talking with QA folks on how to properly implement upgrade testing. current work is being debated.12:25
gordclet me dig up list item on grenade work12:25
ttxYou also have all of the high-prio and most of the mediupm-prio stuff already up for review12:25
ttxwhich is good12:25
gordchttps://review.openstack.org/#/c/102354 grenade work that is currently being discussed12:26
ttxNow it's more a question of turning those "under review" into "implemented" things :)12:26
gordcyeah. i'll need to bug some of the cores to get reviewing now that eglynn is offline for a week. but we have sileht back this week so that's good.12:26
ttxif you get most of the "high" prio stuff implemented and out of the way, it will simplify the last weeks12:27
gordcagreed. we have code pretty much finalised for 2 of 3 three remaining high priority items12:28
ttxIf I remember correctly you don't plan to use a FeatureProposalFreeze this week to drop all blueprints that won't have code proposed by Thursday12:28
gordccentral agent partitioning bp is actively being worked on and i don't have any concerns there.12:28
gordchmm. i don't recall regarding featureproposalfreeze. i guess we have code for all bps currently and i don't intend on adding any during the time eglynn is away12:29
ttxright12:29
gordcaside from very very small items i don't see any new features being added.12:30
gordcbut we'll just say no new items are expected.12:30
ttxOK, well that's all I had -- did you have anything you wanted to discuss at the cross-project meeting later today?12:30
gordcno, i think i should be ok for cross-project meeting. eglynn mentioned a few items we had to track.12:31
gordci assume people know eglynn is on holiday so hopefully there isn't much new items against ceilometer12:31
ttxgordc: ok then. talk to you later, and thanks again for filling in12:32
gordcnp. thanks for pushing time back a bit :)12:32
*** gordc has left #openstack-relmgr-office12:57
*** zaneb has joined #openstack-relmgr-office13:19
ttxjgriffith: around?14:02
*** markmcclain has joined #openstack-relmgr-office14:07
ttxdolphm: around?14:18
dolphmttx: o/14:19
ttx#topic Keystone14:21
ttx#link https://launchpad.net/keystone/+milestone/juno-314:21
ttx#info 5 under review, 1 in progress, 3 blocked and 1 not started14:21
ttxlast week it was 4 Under review, 2 in progress, 6 Blocked/Not started14:21
ttxso i guess that counts as progress14:22
ttxAre you still uncertain on the Blocked ones?14:22
ttxFPF is Thursday :)14:22
dolphmone that's blocked is actually blocked...14:22
dolphmwell, two, but i'm working on one14:23
dolphmkeystone to keystone needs an openstack/requirements review14:23
dolphmhttps://review.openstack.org/#/c/113294/14:23
ttxI may be able to help there14:23
*** david-lyle has joined #openstack-relmgr-office14:24
dolphmhttps://blueprints.launchpad.net/keystone/+spec/endpoint-policy should have been recently unblocked - fixed14:24
dolphmand i swear there's an implementation already in review, but i can't find it, so i'm leaving it as Not Started until our meeting today. if it's not in review today, i'm planning for it to be dropped14:24
dolphmDeprecated Functionality is "Not Started" but only because i don't know that we actually have anything we want to deprecate this release - going to have a last minute discussion today in our meeting about that14:25
dolphmotherwise, i guess i'll repurpose that for kilo14:25
ttxok +2ed14:26
dolphmand then, i just bumped non-persistent tokens from Slow to Good Progress, it cutting it really close though14:27
dolphmttx: thanks!14:27
ttx#info keystone-to-keystone-federation blocked by requirements' https://review.openstack.org/#/c/113294/14:27
ttxaudit-support-for-federation is blocked waiting on keystone-to-keystone-federation itself?14:28
ttxAs far as FPF is concerned, Deprecated functionality can get an exception14:29
ttxDo you still plan to enforce FPF on Thursday? That would probably threaten non-persistent-tokens and endpoint-policy14:30
dolphmaudit support is actually pending support in pycadf, and yeah, the implementation is partly dependent on k2k14:31
ttxdolphm: i would say you're in good shape, you just need to get features landed earlier, to avoid the last-week rush14:32
dolphmstill planning to enforce FPF, yes14:32
dolphmwe're far enough behind on bp reviews that FPF will be critical for us14:32
ttxOK, maybe raise the need for requirements review at the meeting today?14:33
ttxAnything else you want to discuss there ?14:33
dolphmi don't believe so14:35
dolphmand yeah - we need to get that requirements patch in so we can start landing k2k patches14:35
ttxdolphm: ok great. Don't forget to mention it at the meeting, that should unblock it14:36
ttxdavid-lyle: around?14:36
ttxdolphm: thx!14:36
david-lylettx: o/14:36
ttx#topic Horizon14:36
ttx#link https://launchpad.net/horizon/+milestone/juno-314:36
ttx#info 8 implemented, 33 under review, 20 in progress, 2 unknown14:37
ttx(last week was: 7 implemented, 28 under review, 24 in progress, 4 unknown)14:37
ttxSo that's progressing14:37
ttxdavid-lyle: you mentioned having a FPF last week, but I still see blueprints with code not being proposed yet, so we may not agree on what FPF means14:38
*** mestery_afk is now known as mestery14:39
david-lylethat could be14:40
ttxdavid-lyle: the "no new blueprints" deadline is called SpecProposalDeadline14:40
ttxFPF is: "all code must be up for review"14:40
ttxso basically at FPF you should only have "under review" or "implemented" blueprints14:41
ttxMost projects observe it on August 21, two days from now14:41
david-lyleok, hmm14:42
ttxIt usually makes sense to remove stuff from the bottom of the pile, reduce noise and increase focus14:43
ttxBut then it's difficult to push on unsuspecting contributors two days before it hits :)14:44
david-lylettx: makes sense, my terminology was off, and in the past in Horizon we've taken bps up til the end14:44
ttxright14:44
david-lyleI'm trying to reign that in14:44
david-lyleI had been announcing the freeze in meetings 3 weeks prior14:45
david-lylehorizon meetings14:45
david-lyleI understand not everyone attends or reads the logs, of course14:45
ttxOf the "high" blueprints, only https://blueprints.launchpad.net/horizon/+spec/launch-instance-ux-enhancement is not under review yet14:45
david-lylettx: I'll have a status update on that in an hour or so14:46
ttxlast week you said you considered moving it out.14:46
ttxok, let's see how that goes14:46
david-lyleit may miss, code was up, but usability feedback required large changes14:46
ttxAnythign for the meeting later today?14:46
david-lylethe owner is assessing if they can make the changes14:47
david-lyleno items for later14:47
ttxok. Please update status on launch-instance-ux-enhancement when you know if you keep it14:47
ttxdavid-lyle: thx!14:47
david-lylethank you14:47
ttxmestery: around?14:47
mestery\o/14:47
ttx#topic Neutron14:48
ttx#link https://launchpad.net/neutron/+milestone/juno-314:48
* mestery was on vacation Friday/Monday over the past week.14:48
mesteryRecovering from a 4-day weekend while preparing to fly to Chicago for Linuxcon today14:49
ttx#info 3 Implemented, 43 under review, 12 in progress, 26 Unknown/Blocked14:49
mesteryI expect to drop the 26 unknown/blocked by 8-21 this week.14:49
ttxLast week was: 3 implemented, 39 under review, 11 in progress, 32 unknown/blocked14:49
mesterySome people voluntarily removed their BPs, which helped. :)14:49
ttxright, that makes 43 blueprints in jeopardy due to FPF observance14:49
ttxerr14:50
ttxthat use to make14:50
mesteryThose 43 have code proposed14:50
mesteryI think 38 are in jeopardy right?14:50
ttx38 in jeopardy now14:50
mesterycool14:50
ttxyes14:50
mestery:)14:50
mesteryI am most happy that the L3 HA reviews are now getting some airtime, that's a critical piece for us in Juno.14:51
ttxThis is moving a bit too slow though, even if we cut down the BPs on Thursday.. we need more landing14:51
mesteryI expect those to start landing this week, carl_baldwin is working with the the L3 HA team to make that happen.14:51
mesteryAgreed.14:51
ttxespecialy as i wouldn't hold too much hope on the gate status for FF week14:51
mesteryYes, agreed.14:51
ttxland while you can!14:52
mestery++14:52
ttxShall we mark https://blueprints.launchpad.net/neutron/+spec/neutron-ovs-dvr "implemenetd" now?14:52
*** markmcclain has quit IRC14:52
mesteryI think we can, yes, I'll verify with armax and carl_baldwin today, but I think we can do that.14:53
ttxAnd track last remaining bugs in juno-3 bugs targeting?14:53
mesteryYes14:53
ttxThat would make that list look a lot better :)14:53
mestery:)14:53
*** markmcclain has joined #openstack-relmgr-office14:53
ttxThe other two "high" that are in jeopardy right now would be:14:53
ttxhttps://blueprints.launchpad.net/neutron/+spec/ml2-hierarchical-port-binding14:53
ttxand https://blueprints.launchpad.net/neutron/+spec/lbaas-refactor-haproxy-namespace-driver-to-new-driver-interface14:54
mesteryYes14:54
ttxHow is progress looking on those 2?14:54
mesteryFirst one is iffy14:54
ttxmay stil make it ? Would get an exception (sshh, don't tell) ?14:54
mesterySecond is also iffy14:54
mesteryI think the first one may get an exception14:54
mesteryI'll work with rkukura on that14:55
ttxok14:55
ttxCan't wait we get rid of all those unknowns on Thursday14:55
mesteryI am very excited to do that yes :)14:55
ttxOK, I don't think I have much more to add14:56
ttxHow is the incubator proposal going those days?14:56
mesteryMe either, next week will look much cleaner.14:57
mesteryI think we're going to do the incubator14:57
mesteryGBP folks are pretty much on board now14:57
ttxWould you observe feature freeze in it in the same way you do for the neutron repo ?14:57
mesteryWe're still working on that14:57
ttxI think it makes sense for them to not have one that early*14:57
mesteryAgreed on that14:57
ttxthe aggressive deadlines on the integrated release are to make sure no project screws up the others14:58
mestery:)14:58
ttxthere are some benefits in being out of it14:58
ttxthey should have them14:58
mesteryYes, I agree14:58
ttxAnything you'd like to discuss at the meeting ?14:58
mesteryNope, I will only be there 30 minutes due to travel14:59
ttxNothing was posted on the agenda yet, so it might be a short one14:59
ttxOK, talk to you later, enjoy LinuxCon15:00
mesterythanks!15:00
*** mestery is now known as mestery_afk15:01
*** markmcclain has quit IRC15:12
notmynamettx: I'm here. I need just a few minutes please. just got to the office15:29
ttxack, no pb15:29
notmynamettx: ready15:35
ttxnotmyname: o/15:35
ttx#topic Swift15:36
ttxSo, did you clarify your plans wrt. the last intermediary swift release?15:36
notmynamettx: 2 more, actually, as we had discussed a while back. or maybe that's what you mean. one before juno and then one at juno15:36
ttxone intermediary and one final, yes15:37
notmynamefirst can I confirm with you that juno is oct 1615:37
ttxyes it is15:38
notmynameok, thanks15:38
notmyname2.1.0 rc next week (aug 25). final on sept 115:38
notmynameand 2.next RC on oct 6 with the final at or near oct 16 for juno15:39
*** mestery_afk has quit IRC15:39
notmynamehow does that work with you?15:39
ttxnotmyname: that would work15:41
notmynamettx: ok, great15:41
notmynameas normal, I'll send you the SHA15:41
notmynameie I;ll send you one this weekend and you can cut the rc at your leisure on monday15:41
ttxack, hopefully we'll not have to backport this time around )15:42
ttx:)15:42
notmynamealways :-)15:42
ttxAny specific feature there ? Or mostly a bugfix release?15:42
ttx#info 2.1.0 rc next week (aug 25). final on sept 115:42
ttx#info next RC on oct 6 with the final at or near oct 16 for juno15:42
notmynamettx: some smaller changes, but enough to have 2.1.0 (rather than 2.0.1): https://review.openstack.org/#/c/115167/2/CHANGELOG15:43
ttxWant me to create the 2.1.0 milestone?15:43
notmynamebut mostly polish rather than HUGE NEW FEATURE15:43
notmynameyes, please15:43
ttxok, will do15:43
ttxAny topic for the meeting today?15:44
notmynameno, I don't think so15:44
notmynamewe are working on the gap analysis questions. I hope to review those at the wednesday swift team meeting15:44
ttxok then, will ping you when I have the milestone up15:44
notmynameie reviewing various oslo libraries15:44
ttxnotmyname: thx, and ttyl15:45
*** SlickNik has joined #openstack-relmgr-office15:46
ttxzaneb: around?15:47
zanebttx: yes, but I'm at the Heat mid-cycle meetup today15:48
ttxzaneb: oh, ok. Maybe we should skip then15:48
ttxand talk another day15:48
zanebyeah, that would be good if we could15:48
ttx(I suspect your status is in flux anyway)15:48
ttxzaneb: enjoy your meetup.15:49
zanebsorry, forgot to warn you in advance15:49
zanebthanks, ttyl15:49
ttxno problem15:49
jgriffithttx: ruh roh15:51
ttxjgriffith: o/15:51
ttxI have a free slot now :)15:51
jgriffithhow fortuitous for me15:51
ttxnotmyname: https://launchpad.net/swift/+milestone/2.1.0 up for your targeting pleasure15:51
ttx#topic Cinder15:52
ttx#link https://launchpad.net/cinder/+milestone/juno-315:52
jgriffithOnly one I'm unclear on is Vincent's15:52
ttx#info 2 implemented, 8 in review, 4 in progress, 1 unknown15:52
jgriffithit's in progress15:53
ttxjgriffith: IIRC you plan to observe FPF on Thursday?15:53
jgriffithI'll update it manually15:53
jgriffithttx: that's correct15:53
jgriffithttx: mostly wanted to use it as a driver submission cut off15:53
ttxSo that makes 5 in jeopardy, including https://blueprints.launchpad.net/cinder/+spec/secure-nfs15:53
jgriffithright15:54
jgriffithI'll get the word out to make sure everyone's clear15:54
jgriffithI'd like to see NFS fixed up but honestly I'm not sure it's going to happen anyway (even if they had another week)15:55
ttxthat one blueprint I just linked is the one trying to plug that security issue in NFS support, right15:55
jgriffithttx: correct15:55
ttxright, would be nice to have15:55
jgriffithttx: I'll talk to Glenn and would certainly do an exception for it15:55
*** sdague has quit IRC15:55
ttxYou also want it to actually be safe, which takes extra time to review15:55
jgriffithttx: yeah, so that's the ONLY one I see that I would let go longer15:56
ttxSo you don't seem in a bad situation, but you definitely should merge as much as you can this week, to avoid the rush15:56
jgriffithttx: I'll just call it a bug :)15:56
jgriffithsince it is15:56
ttxyeah, it's a bug but it probably requires featury things like new config options15:56
ttxwhich make it impact documentation15:57
jgriffithyeah, that's why we moved it.15:57
ttxso I'd prefer it to follow the exception procedure, if only so that people are aware it's coming15:57
jgriffithI'll get with Glenn and see where he's at with it15:57
ttxOK, anything else?15:57
ttxAny topic for the meeting today?15:57
jgriffithttx: I agree, I'll get it formalized and out on the ML if it happens15:57
jgriffithor when it happens15:58
jgriffithI do not15:58
* ttx might just add the meetup vs. design summit discussion there15:58
ttxbut that sounds like a recipe for getting to bed late15:58
jgriffithttx: I have a lot of thoughts on that, but I hate to open that can of worms without having better ideas in mind :)15:58
jgriffithttx: yes, it would be a very long night for you I suspect15:58
jgriffithttx: I'm thinking of proposing a different format for Cinder this time around15:59
jgriffithbut thought I should go via ML when I have something in mind15:59
ttxjgriffith: ah. Let's discuss it at the meeting :)15:59
jgriffithttx: works for me15:59
jgriffithI'll spit ball my ideas/thoughts15:59
jgriffithsee what we can come up with15:59
ttxyeah, mostly brainstorming16:00
ttxjgriffith: thx!16:00
jgriffithttx: thank you... see ya later16:01
ttxSlickNik: ready when you are16:02
ttxNo Glance person there yet16:02
*** sdague has joined #openstack-relmgr-office16:03
*** arnaud has joined #openstack-relmgr-office16:05
ttxarnaud: o/16:08
ttxrepresenting Glance again?16:08
SlickNikttx: I'm at the Trove Day, and the Trove mid-cycle meetup this week — so won't be able to talk much.16:11
SlickNikttx: trying to get closure on the multiple open reviews we have in progress: https://launchpad.net/trove/+milestone/juno-316:11
ttxSlickNik: I'm fine with skipping, you seem in pretty good shape16:11
ttxSlickNik: Enjoy your meetup16:11
* ttx waits a bit more to see if arnaud is representing Glance this week, otherwise I'll close the 1:1 syncs for today16:12
ttxOK, let's call it a day.16:15
ttx#endmeeting16:15
openstackMeeting ended Tue Aug 19 16:15:16 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:15
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-08-19-08.01.html16:15
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-08-19-08.01.txt16:15
openstackLog:            http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-08-19-08.01.log.html16:15
*** arnaud has quit IRC16:24
*** markmcclain has joined #openstack-relmgr-office16:34
*** markmcclain has quit IRC16:49
*** arnaud has joined #openstack-relmgr-office16:54
*** markmcclain has joined #openstack-relmgr-office16:55
*** arnaud has quit IRC17:02
*** johnthetubaguy is now known as zz_johnthetubagu17:10
*** markmcclain has quit IRC17:25
*** markmcclain has joined #openstack-relmgr-office17:25
*** david-ly_ has joined #openstack-relmgr-office18:50
*** david-lyle has quit IRC18:51
*** david-ly_ is now known as david-lyle19:13
*** markmcclain has quit IRC19:17
*** markmcclain has joined #openstack-relmgr-office19:50
*** stevebaker has quit IRC20:00
*** stevebaker has joined #openstack-relmgr-office20:00
*** stevebaker has quit IRC20:41
*** stevebaker has joined #openstack-relmgr-office20:41
*** mestery has joined #openstack-relmgr-office20:49
*** mestery has quit IRC20:49
*** mestery has joined #openstack-relmgr-office20:50
*** mestery_ has joined #openstack-relmgr-office21:36
*** mestery has quit IRC21:37
*** mestery_ is now known as mestery21:40
*** mestery has quit IRC21:45
*** mestery has joined #openstack-relmgr-office21:46
*** mestery has quit IRC22:01
*** markmcclain has quit IRC22:26
*** mestery has joined #openstack-relmgr-office22:53
*** arnaud has joined #openstack-relmgr-office22:59
*** mestery_ has joined #openstack-relmgr-office23:02
*** mestery has quit IRC23:02
*** mestery_ has quit IRC23:07
*** mestery has joined #openstack-relmgr-office23:07
*** mestery has quit IRC23:12
*** mestery has joined #openstack-relmgr-office23:13
*** zaneb has quit IRC23:36
*** mestery has quit IRC23:41
*** mestery has joined #openstack-relmgr-office23:44
*** david-lyle has quit IRC23:44
*** david-lyle has joined #openstack-relmgr-office23:45
*** david-lyle has quit IRC23:45
*** mestery has quit IRC23:45

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