16:00:29 <xarses> #startmeeting fuel
16:00:29 <xarses> #chair xarses
16:00:29 <xarses> Todays Agenda:
16:00:29 <xarses> #link https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda
16:00:29 <xarses> Who's here?
16:00:29 <openstack> Meeting started Thu Mar 24 16:00:29 2016 UTC and is due to finish in 60 minutes.  The chair is xarses. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:31 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:33 <openstack> The meeting name has been set to 'fuel'
16:00:34 <openstack> Current chairs: xarses
16:00:47 <angdraug> o/
16:00:49 <evgenyl> hi
16:00:49 <fzhadaev> Hi!
16:00:55 <mihgen> hi
16:00:57 <HeOS> Hi!
16:00:57 <srwilkers> hello
16:01:11 <holser_> o/
16:01:28 <monester> hi
16:01:31 <kozhukalov> hi
16:01:39 <yottatsa> ^_^
16:01:58 <ashtokolov> hi
16:01:59 <warpc> Hi
16:02:16 <pzhurba> hi
16:02:40 <akislitsky_> hi
16:02:54 <xarses> #topic Action items from last meeting
16:02:54 <mwhahaha> hi
16:02:57 <akasatkin> hi
16:03:02 <xarses> asaprykin will follow up on fuel master node idempotentcy for 10
16:04:05 <xarses> asaprykin is not with us today
16:04:11 <xarses> akislitsky_: romcheg to update on fuel-web deadlocks issue
16:04:11 <ikalnitsky> o/
16:04:37 <holser_> xarses: as far as I know romcheg sent email
16:04:55 <xarses> ok
16:05:00 <holser_> there was a discussion between kozhukalov and romcheg
16:05:01 <mihgen> there was email thread from ikalnitsky and I've prepared a patch https://review.openstack.org/#/c/294976/
16:05:08 <romcheg> yup
16:05:30 <xarses> ashtokolov will follow up on scheduling demo for enhancements team features
16:05:42 <ashtokolov> https://etherpad.openstack.org/p/unlock_settings_demos
16:05:43 <ikalnitsky> mihgen: nice work ;)
16:06:06 <xarses> akscram to update ML and bug regarding FFE for in-place upgrade code
16:06:52 <akscram> the bug report was updates and a letter was sent
16:07:00 <xarses> ok
16:07:18 <akscram> The feature has two +2 and it's ready to be merged.
16:07:23 <xarses> now for the main event
16:07:32 <xarses> #topic Driving consistent UX across fuel-ui and python-fuelclient (holser)
16:08:31 * angdraug prods holser_
16:08:47 <angdraug> #link https://review.openstack.org/287508
16:08:54 <angdraug> holser_: raised a valid concern in the review ^
16:09:11 <angdraug> we don't have anyone to make sure UX between fuel-ui and python-fuelclient remains consistent
16:09:37 <xarses> and by proxy, how the API changes impact them
16:09:41 <angdraug> in the same time, many people objected to solving this problem by having a single component lead for both
16:10:06 <angdraug> which also makes sense, component leads have enough to worry about as it is
16:10:25 <romcheg> angdraug: web UI and cli provide defferent UX
16:10:28 <angdraug> I think we need to borrow yet another OpenStack collaboration technique and assign/volunteer a UX tzar
16:10:43 <romcheg> how can someone make is consistent?
16:10:59 <angdraug> consistent doesn't mean exactly the same
16:11:12 <xarses> angdraug: +1
16:11:13 <holser_> I think the difference is so huge as horizon and nova cli
16:11:30 <holser_> so nova PTL is responsible for nova CLI
16:11:38 <romcheg> excacly
16:11:50 <holser_> I guess for now Nailgun CL should be responsible for fuel-client
16:12:25 <ikalnitsky> wow, easy
16:12:26 <romcheg> in the future, when we finish separating components, we may end up with a cli client/api wrapper for every one of them
16:12:33 <holser_> and collaborate with UI CL to make a consistency
16:13:25 <xarses> so what is the action from this?
16:13:41 <xarses> we merged 287508
16:13:47 <angdraug> I propose a role of cross-component UX liaison
16:14:02 <angdraug> if there's no objections, I can announce it on openstack-dev and call for volunteers
16:14:03 <holser_> +!
16:14:12 <romcheg> angdraug: what they are going to be responsible for?
16:14:16 <holser_> make action item :)
16:14:39 <angdraug> romcheg: keeping track of UX changes in both ui and fuelclient and reminding people when they grow too far apart
16:14:40 <kozhukalov> angdraug: too many roles
16:14:51 <angdraug> we're a big project
16:14:52 <ikalnitsky> kozhukalov: +1
16:15:07 <angdraug> if there's no consensus, lets bump the whole discussion to ML and move on
16:15:13 <romcheg> CLI is an API wrapper
16:15:25 <romcheg> the only UX it can provide is cover 100% of API
16:15:32 <kozhukalov> openstack itself even does not have CL, it should be up to a component team if they need CL or not
16:15:35 <ikalnitsky> i think every single person must watch that and raise questions if there's inconsistence
16:15:43 <xarses> romcheg: that is false
16:15:51 <xarses> it has to also be usable
16:15:55 <holser_> +1 to ikalnitsky
16:16:00 <angdraug> ikalnitsky: when everyone's responsible, nobody's accountable
16:16:06 <romcheg> xarses: it is usable by covering API
16:16:15 <holser_> meritocracy should win
16:16:24 <mihgen> we need it to be awesome UX, not just useful
16:16:44 <ikalnitsky> UX is a part of spec
16:16:45 <mihgen> components have to stive to have awesome UX
16:16:46 <angdraug> mihgen: even useful would be an improvement over usable
16:17:02 <ikalnitsky> we have plenty of engineers, why engineers aren't going to decide what's useful ?
16:17:04 <romcheg> mihgen: for that we should design an awesome API, not just cover it by a nice wrapper
16:17:12 <mihgen> no matter how good API is if major use cases over CLI and CLI is terrible
16:17:13 <xarses> romcheg: no, we have had issues where the CLI is not working with the user well
16:17:38 <angdraug> 17 minutes in and at the first topic
16:17:42 <angdraug> lets move this to ML
16:17:45 <romcheg> +1
16:17:47 <xarses> yep
16:17:47 <mihgen> ok
16:17:56 <xarses> #topic FFEs status (angdraug) - http://lists.openstack.org/pipermail/openstack-dev/2016-March/088311.html
16:17:59 <romcheg> at least we agreed on smth :)
16:18:07 <angdraug> lets review the state of our feature freeze exceptions:
16:18:07 <angdraug> #link http://lists.openstack.org/pipermail/openstack-dev/2016-March/088311.html
16:18:09 <angdraug> UCA: merged on 3/10, fix for bug #1556011 merged on 3/17
16:18:09 <angdraug> multipath disks: merged on 3/4
16:18:09 <angdraug> LCM readyness for all deployment tasks: merged on 3/16
16:18:09 <openstack> bug 1556011 in Fuel for OpenStack "UCA specific data must be moved into separate release in openstack.yaml" [High,Fix committed] https://launchpad.net/bugs/1556011 - Assigned to Matthew Mosesohn (raytrac3r)
16:18:09 <angdraug> HugePages: merged on 3/18
16:18:10 <angdraug> Numa: merged on 3/17
16:18:12 <angdraug> SR-IOV: merged on 3/15
16:18:14 <angdraug> Decouple Fuel and OpenStack tasks: missed the deadline of 3/20, one commit left and ready for merge:
16:18:17 <angdraug> #link https://review.openstack.org/283332
16:18:19 <angdraug> Remove conflicting openstack module parts: missed the deadline of 3/20, one commit left and failing CI:
16:18:22 <angdraug> #link https://review.openstack.org/296668
16:18:24 <angdraug> DPDK: one commit left and failing CI:
16:18:26 <angdraug> #link https://review.openstack.org/293981
16:18:28 <angdraug> Unlock "Settings" Tab: missing the deadline of 3/24, a number of unmerged commits
16:18:30 <angdraug> ConfigDB: missing the deadline of 3/24, a number of unmerged commits
16:18:32 <angdraug> Osnailyfacter refactoring for Puppet Master compatibility: merged on 3/23
16:18:33 <xarses> #action angdraug holser_ will raise UX tzar ML
16:18:34 <angdraug> owners of remaining FFEs, please comment
16:18:48 <angdraug> xarses: you're first on the list
16:18:56 <xarses> #link https://review.openstack.org/#/c/283332/
16:18:56 <xarses> .Is the last one of mine that is open, is ready to land, and is waiting for puppet CI to recover from ruby gem jwt 1.5.3 being removed
16:19:16 <mwhahaha> should be good to +A now
16:19:26 <mwhahaha> 1.5.4 was released and other items are passing puppet CI now
16:19:43 <xarses> mwhahaha: thanks
16:19:44 <angdraug> lets land it then
16:20:00 <dklenov> angdraug: confirmed for NFV, thanks
16:20:02 <mwhahaha> same for the status on the conflicting openstack module parts, the recheck is running now
16:20:09 <mwhahaha> it'll land shortly
16:20:27 <xarses> https://review.openstack.org/#/c/296668/
16:20:49 <fzhadaev> https://review.openstack.org/293981 will be landed today
16:20:55 <xarses> angdraug: next
16:20:59 <angdraug> fzhadaev: thanks
16:21:12 <angdraug> that leaves ashtokolov
16:21:22 <ashtokolov> Hi folks! We are very close to landing all our features Unlock Settings. But we still have a set of reviews to be merged. I would like to request extra time till Monday to land them.
16:21:30 <angdraug> ogelbukh_: you're next, don't fall asleep this time )
16:21:30 <ashtokolov> https://review.openstack.org/#/q/branch:master+topic:bp/store-deployment-tasks-history 3 patches to be merged
16:21:37 <ashtokolov> https://review.openstack.org/#/q/status:open++branch:master+topic:bp/save-deployment-info-in-database  2 patches to be merged
16:21:42 <ashtokolov> https://review.openstack.org/#/q/branch:master+topic:bp/custom-graph-execution+NOT+status:abandoned 5 patches to be merged
16:21:48 <ashtokolov> https://review.openstack.org/#/q/status:open+branch:master+topic:bp/computable-task-fields-yaql 5 patches to be merged
16:21:53 <ashtokolov> https://review.openstack.org/#/q/status:open+branch:master+topic:bp/unlock-settings-tab 2 patches to be merged
16:22:04 <angdraug> yikes, that's a lot of patches
16:22:07 <ogelbukh_> I'm here, yes
16:22:17 <xarses> o.O
16:22:26 <ashtokolov> some of them should be landed today
16:22:35 <aglarendil> ... ashtokolov is typing ...
16:22:37 <ashtokolov> but we have CI issues with fuel-web repo
16:22:45 <ashtokolov> *had
16:22:48 <angdraug> how many of the 17 are ready to land?
16:22:59 <angdraug> are these 17 it, or will there be more?
16:23:33 <aglarendil> ... ashtokolov is counting and typing ...
16:23:33 <ashtokolov> 7 or 8 are ready to be merged
16:23:41 <ashtokolov> others are on review
16:23:57 <xarses> there appears to be a lot of -1 from ci
16:24:19 <angdraug> personally, I think this is a hugely important feature and worth some risk
16:24:21 <ashtokolov> afaik due to python27-db gate issues
16:24:49 <ashtokolov> ikalnitsky fixed it today
16:24:50 <angdraug> but if we keep merging more feature code next week, we'll put SCF date at risk, again
16:25:10 <ashtokolov> I would like to request extra time till Monday to land them.
16:25:28 <xarses> ashtokolov: will we work to land them over the weekend?
16:25:50 <angdraug> xarses: I don't see how we can land that much code without it :(
16:25:58 <ashtokolov> we will
16:25:59 <xarses> otherwise I'm not sure Monday is not realistic
16:26:20 <angdraug> objections to extending FFE to 3/28?
16:26:37 <mihgen> we need to strive getting these in
16:26:46 <angdraug> 3/28 is going to be the final deadline, we simply can't push it further
16:26:52 <xarses> we need 2 cores from each fuel-web, python-fuelclient and fuel-lib to support them this weekend
16:26:52 <mihgen> I think we need to support ashtokolov and folks as much as we can
16:26:57 <angdraug> whatver isn't ready by then will have to be left out
16:27:25 <aglarendil> dibs!
16:27:28 <xarses> If we have that, then I think we can maybe do that
16:27:30 <angdraug> ashtokolov: are there outstanding fuelclient/library patches?
16:27:31 <holser_> I can handle that
16:27:44 <angdraug> holser_: aglarendil: thanks!
16:28:02 <xarses> (there is one library, and one client by the looks
16:28:20 <ashtokolov> angdraug nope, only these I mentioned
16:28:28 <angdraug> romcheg: can you keep an eye on that client patch over the weekend?
16:28:35 <angdraug> or help it land tomorrow :)
16:28:47 <romcheg> I will try to make myself free tomorrow
16:28:50 <romcheg> :)
16:28:57 <angdraug> ashtokolov: sounds like the bulk of patches is on python side
16:29:07 <angdraug> unfortunately we're fairly short on fuel-web cores :(
16:29:08 <ashtokolov> romcheg was working with us all this week. Thank you!
16:29:50 <romcheg> ashtokolov: I will take a look at all of them one more time today
16:30:00 <romcheg> after I'm done with some other stuff
16:30:09 <ashtokolov> one of them, Bulat was working on patches and can not merge them
16:30:22 <ashtokolov> one of fuel-web core I mean
16:30:29 <angdraug> ikalnitsky: looks like you'll have to be the one to merge it
16:30:39 <ikalnitsky> i'll try to help
16:30:53 <angdraug> we need a 1-2 volunteers to help ikalnitsky
16:31:08 <evgenyl> I will try to help too.
16:31:14 <fzhadaev> Telco team will help with review :) At least tomorrow
16:31:31 <angdraug> thanks, looks like this can work out
16:31:33 <akasatkin> I'll try to help as well
16:31:41 <ashtokolov> Thank you so much, guys!
16:31:48 <angdraug> thanks everyone for volunteering, much appreciated, you're all awesome!
16:32:08 <angdraug> ogelbukh_: lets talk about ConfigDB
16:32:14 <mihgen> 8)
16:32:17 <ogelbukh_> sure
16:32:26 <yottatsa> :popcorn:
16:32:47 <ogelbukh_> configdb status:
16:32:47 <ogelbukh_> 1. API extension being finalized
16:32:47 <ogelbukh_> - Code is in openstack/tuning-box repo, available for review
16:32:47 <ogelbukh_> - Packaging in progress, integration and dependencies solved, spec pending
16:32:47 <ogelbukh_> 2. Deployment task for data upload is in progress in Puppet Master plugin source code tree
16:32:47 <ogelbukh_> - Integrated with main plugin body
16:32:47 <ogelbukh_> - Tested against mock backend
16:32:48 <ogelbukh_> 3. For auth, decided to let the user create service creds and pass to plugin
16:33:11 <ogelbukh_> #link https://git.openstack.org/openstack/tuning-box
16:34:06 <xarses> ogelbukh_: what is still waiting on fuel internals if anything?
16:34:12 <ogelbukh_> so it seems that we won't use the benefits of the FFE and everything will be separated from the fuel core
16:34:22 <ogelbukh_> xarses: from configdb standpoint, no
16:34:42 <xarses> sounds good
16:34:43 <ogelbukh_> xarses: for the end-to-end solution, we depend on osnailyfacter refactoring
16:34:57 <angdraug> ogelbukh_: that's all merged since yesterday
16:34:59 <ogelbukh_> so we could test puppet-master integration
16:35:05 <ogelbukh_> yes, I'm aware of that
16:35:24 <ogelbukh_> we plan to start integration tests from Monday
16:35:38 <ogelbukh_> the configdb extension will be finalized by then
16:35:44 <angdraug> cool, that's a relief
16:35:57 <xarses> moving?
16:36:02 <angdraug> yup
16:36:04 <ogelbukh_> well, we still expect many raw endge
16:36:07 <ogelbukh_> *edges
16:36:10 <xarses> #topic Revisiting FFE for Reassigning Nodes without Re-Installation (akscram) - https://review.openstack.org/280067
16:36:19 <akscram> This change is ready to be merged, I'm waiting for +A.
16:37:06 <xarses> do we have agreement from QA to extend the testing scope to prevent regressions?
16:37:26 <angdraug> I looked at this yesterday, it looks like the non-extention impact is just a few lines of code
16:37:52 <xarses> angdraug: that was my impression also
16:37:52 <angdraug> nurla: ^?
16:38:07 <akscram> I'm not sure but this change has backward compatibility with the old reassigning mechanism.
16:38:39 <angdraug> xarses: akscram: can you describe testing scope changes that you want QA to confirm?
16:39:15 <akscram> It's very hard because there is no yet the upgrade procedure from 8.0 to 9.0 in the upstream.
16:39:15 <xarses> angdraug: I just want to feel warm and fuzzy that QA is fine with adding any features at this point
16:39:24 <angdraug> I'd rather we merge it today to reduce the chance of it interfering with unlock settings tab related work
16:40:32 <angdraug> I think we're 3 weeks too late for warm and fuzzy
16:41:04 <angdraug> with the number of FFEs we've had pending until today,
16:41:19 <xarses> yep
16:41:27 <angdraug> I'm pretty sure QA wasn't going to start proper acceptance testing until SCF anyway
16:41:57 <angdraug> lets just merge this one tiny commit and move on
16:42:08 <akscram> Heh, thanks.
16:42:27 <xarses> #topic Tag mitaka-3 in fuel git repos (angdraug)
16:42:33 <angdraug> I'll be quick
16:42:45 <angdraug> lets tag our repos with "mitaka-3" tag when we're done with all FFEs
16:43:04 <angdraug> we didn't do mitaka-1 and mitaka-2 because we've started late
16:43:14 <angdraug> but we should start using the beta tags, and now is a good time
16:43:36 <xarses> angdraug: +1
16:43:56 <angdraug> great, lets move on before anyone objects :)
16:44:13 <xarses> #topic Fuel Telco Team Status (fzhadaev)
16:44:27 <fzhadaev> Two main activities of Telco team on this week were:
16:44:27 <fzhadaev> 1) Finishing work on DPDK feature (done)
16:44:27 <fzhadaev> 2) Fixing bugs (8 fixed, 10 in progress)
16:44:27 <fzhadaev> Any questions?
16:45:04 <xarses> awesome, keep up the work
16:45:12 <xarses> #topic Fuel Network team status (akasatkin)
16:45:29 <akasatkin> We work on NFV and other two stories.
16:45:29 <akasatkin> NFV status was provided already. Other tickets:
16:45:29 <akasatkin> https://blueprints.launchpad.net/fuel/+spec/allow-any-vip
16:45:29 <akasatkin> QA is almost done: Manual testing complete. Auto tests are complete.
16:45:29 <akasatkin> https://blueprints.launchpad.net/fuel/+spec/external-lbs
16:45:30 <akasatkin> QA is in progress: Manual testing complete. Auto tests are in progress.
16:45:30 <akasatkin> No serious bugs for the moment.
16:45:54 <xarses> akasatkin: great to hear those are going well
16:46:07 <xarses> #topic UI Team status (vkramskikh)
16:46:12 <vkramskikh> Hi! Here is our status for 9.0 features:
16:46:12 <vkramskikh> 1) https://blueprints.launchpad.net/fuel/+spec/remove-vendor-code - implemented.
16:46:12 <vkramskikh> 2) NFV stuff - implemented. There are a few known bugs which we've already started fixing. The most important one is to fix bond type for DPDK-enabled bonds - currently it's "linux" but should be "ovs".
16:46:12 <vkramskikh> 3) https://blueprints.launchpad.net/fuel/+spec/unlock-settings-tab - progress for UI part is about 70%, for further progress working backend is needed.
16:46:13 <vkramskikh> As for the bugs, there are 38 UI bugs, 10 of them are High.
16:46:15 <vkramskikh> Questions?
16:46:58 <xarses> and urgent issues outside unlock settings?
16:47:26 <vkramskikh> don't remember any
16:47:35 <xarses> ok, thanks
16:47:38 <yottatsa> For NFV we have one major high bug, that has to be fixed by downstream patch in neutron #link https://bugs.launchpad.net/fuel/+bug/1558613
16:47:38 <openstack> Launchpad bug 1558613 in Fuel for OpenStack "[SR-IOV] Instance creation fails if there are few sriov nics with same physical network name" [High,Confirmed] - Assigned to MOS Neutron (mos-neutron)
16:48:08 <yottatsa> other seems good so far
16:48:16 <xarses> thanks
16:48:19 <xarses> #topic Fuel-mixed team status (pzhurba)
16:48:34 <pzhurba> Hi
16:48:42 <pzhurba> Mixed team was working on bugfixing ,reviews and other duty staffs.
16:48:56 <pzhurba> All features merged, but We still have a bug in progress,
16:49:04 <pzhurba> related to conflict between LVM and multipath:
16:49:12 <pzhurba> https://bugs.launchpad.net/fuel/+bug/1559197
16:49:12 <openstack> Launchpad bug 1559197 in Fuel for OpenStack "lvm broke multipath on provisioned systems" [High,In progress] - Assigned to Sergey Slipushenko (sslypushenko)
16:49:19 <pzhurba> Now we are working on fixing it
16:49:31 <pzhurba> Also We have demos scheduled for this week: today for idempotency and insurability
16:49:40 <pzhurba> and tomorrow for multipath
16:50:02 <xarses> thanks
16:50:03 <pzhurba> Any  questions?
16:50:31 <xarses> #topic Austin Design Summit topics - prepare agenda (holser, angdraug)
16:50:54 <angdraug> holser_: you go first :)
16:51:05 <holser_> yeah
16:51:15 <holser_> I wanted to remind about summit and topics
16:51:28 <holser_> We should start working on agenda and topics
16:51:50 <kozhukalov> #link https://etherpad.openstack.org/p/fuel-austin-agenda
16:51:52 <holser_> as there will be limited time and participants
16:52:04 <kozhukalov> we just need to make it better structured
16:52:12 <holser_> better structured
16:52:18 <holser_> and pick topics
16:52:26 <kozhukalov> yes
16:52:26 <angdraug> we've got 3 fishbowl (large) and 11 workroom (small) sessions approved
16:52:30 <holser_> and get the rest offline
16:52:39 <angdraug> also a full-day contributor meetup on Friday
16:52:42 <holser_> I can spent time with PTL to make it clean
16:53:01 <kozhukalov> but we still don't know who is going to attend this summit
16:53:35 <angdraug> we should know who can attend by tomorrow
16:53:58 <xarses> I think we will have to follow up offline and maybe collaborate on it before next week
16:54:12 <holser_> Action item?
16:54:50 <xarses> #action holser_ angdraug with collaborate on https://etherpad.openstack.org/p/fuel-austin-agenda
16:55:08 <xarses> #topic open discuss
16:55:15 <xarses> hey we haven't had this one in a while
16:55:19 <angdraug> wow, whole five minutes left :D
16:55:30 <xarses> we have 5 min left, anyone have something to raise?
16:55:43 <mwhahaha> glance makes me sad
16:55:55 <angdraug> mwhahaha: how so?
16:56:07 <xarses> the CI issue I'm guessing
16:56:12 <holser_> CI failures …
16:56:13 <mwhahaha> yea the TestVM thing
16:56:27 <xarses> has that been active today?
16:56:27 <holser_> guys are digging into this
16:56:48 <mihgen> ikalnitsky: hey have we enabled performance tests for every single patch?
16:56:48 <kozhukalov> i like the format of infra summit agenda https://etherpad.openstack.org/p/infra-newton-summit-planning
16:57:01 <ikalnitsky> mihgen: not yet
16:57:10 <ikalnitsky> i'll work on it tomorrow
16:57:15 <kozhukalov> are they green now?
16:57:23 <ogelbukh_> any chance to insert some lcm/upgrade agenda in that list?
16:57:40 <kozhukalov> which list?
16:57:43 <kozhukalov> fuel?
16:57:44 <mwhahaha> the galera stuff seems to be fixed as of this morning so that should clean up the CI a bit, but we still have the TestVM failures out there
16:58:06 <xarses> ogelbukh_: put it in so it can be evaluated
16:58:12 <angdraug> kozhukalov: yup, good format, holser_ please have a look
16:58:31 <holser_> I am looking
16:58:34 <kozhukalov> ogelbukh_: sure, just put what you think is important here https://etherpad.openstack.org/p/fuel-austin-agenda
16:58:35 <holser_> Good format
16:58:41 <holser_> that can be sent to community
16:58:43 <angdraug> ogelbukh_: it's #1 on the list atm
16:58:52 <ogelbukh_> got it
16:59:11 <angdraug> lets be good neighbours and finish on time :)
16:59:19 <ogelbukh_> (I used to read lists from the bottom up)
16:59:23 <xarses> #endmeeting