21:04:49 <mriedem> #startmeeting nova
21:04:49 <openstack> Meeting started Thu Apr 23 21:04:49 2015 UTC and is due to finish in 60 minutes.  The chair is mriedem. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:04:50 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:04:52 <openstack> The meeting name has been set to 'nova'
21:04:56 <jroll> someone should publish scripts for this :P
21:05:03 <mriedem> who's around?
21:05:04 <mriedem> no one?
21:05:05 <bauzas> sooooo \o
21:05:08 <melwitt> o/
21:05:10 <n0ano> o/
21:05:10 <jogo> o/
21:05:10 <tjones1> hi
21:05:12 <alaski> o/
21:05:13 <edleafe> o/
21:05:22 <beagles> o/
21:05:23 <andreykurilin__> o/
21:05:27 <mriedem> ok, meeting agenda https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
21:05:30 <alex_xu> o/
21:05:37 <bauzas> ping abhishekk mikal tjones cburgess jgrimm adrian_otto funzo mjturek jcookekhugen irina_pov krtaylor danpb alexpilotti flip214 jaypipes gilliard garyk edleafe dims moshele anteaya Nisha sileht claudiub lxsli neiljerram markus_z swamireddy alevine tonyb andreykurilin ndipanov sc68cal akuriata
21:05:39 <mriedem> release stuff - rc2 was out today
21:05:42 <lennyb> hi
21:05:55 <mriedem> i don't know of plans for an rc3
21:05:59 <mriedem> sdague: dansmith: ^?
21:06:31 <mriedem> this was the rc2 content anyway https://launchpad.net/nova/+milestone/kilo-rc2
21:06:32 <johnthetubaguy> hi
21:06:40 <mriedem> well well well
21:06:54 <bauzas> https://bugs.launchpad.net/nova/+bugs?field.tag=kilo-rc-potential
21:06:56 <mriedem> this is the list of kilo-rc-potentials
21:06:56 <mriedem> https://bugs.launchpad.net/nova/+bugs?field.tag=kilo-rc-potential
21:06:57 <mriedem> yeah
21:07:14 <mriedem> are there open stable/kilo reviews/
21:07:15 <mriedem> ?
21:07:19 <mikal> Hi as well, sorry, I thought this was the early week for some reason
21:07:39 <mriedem> https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/kilo,n,z
21:08:05 <mriedem> anyone have rc questions/issues?
21:08:31 <mriedem> moving on
21:08:33 <dansmith> sorry, I'm late
21:08:38 <mriedem> like everyone
21:08:39 <jroll> so I'm curious if https://review.openstack.org/#/c/176396/ is worth getting into rc3
21:08:40 <mriedem> sheesh
21:08:46 <jroll> small simple fix
21:08:51 <mriedem> jroll: i don't think so
21:08:55 <dansmith> nope
21:08:55 * johnthetubaguy just back from my rehearsal, running
21:08:56 <mriedem> there are many small simple fixes
21:09:06 <mriedem> jroll: stable/kilo backport is fine
21:09:09 <mriedem> but not holding up rc
21:09:12 <mriedem> *release
21:09:22 <jroll> how often do backports release?
21:09:22 <bauzas> is there any big issue needing an RC3 ? really ?
21:09:25 <dansmith> nothing up is worth an rc3 at this point, IMHO
21:09:31 <johnthetubaguy> jroll: best for backporting I suspect now
21:09:36 <mriedem> jroll: there is a wiki for that somewhere
21:09:41 <mriedem> the stable maintainers plan those out i think
21:09:57 <jroll> yeah, that's fine, just cringing at thinking about all the people asking why that doesn't work :P
21:09:59 <jroll> thanks
21:10:01 <johnthetubaguy_w> kilo-backport-potential is the tag I think
21:10:01 <mriedem> https://wiki.openstack.org/wiki/Releases
21:10:08 <bauzas> mriedem: https://bugs.launchpad.net/nova/+bugs?field.tag=kilo-rc-potential sees nothing critical
21:10:11 <jroll> johnthetubaguy_w: yeah, it's tagged
21:10:16 <bauzas> mriedem: we can just say no RC3
21:10:35 <bauzas> and do backporting to kilo if needed later
21:10:42 <mriedem> yeah
21:10:49 <mriedem> moving on?
21:10:51 <johnthetubaguy> bauzas: will have to be critical to trigger RC3 I would suspect, something might come up, but lets hope not
21:10:52 <mriedem> blueprints for liberty are open
21:10:57 <mriedem> https://blueprints.launchpad.net/nova/liberty
21:11:06 <mriedem> specs are under review
21:11:07 <bauzas> johnthetubaguy: agreed, just not atm :)
21:11:23 <johnthetubaguy> so please target for liberty if you want to merge code in liberty
21:11:31 <mriedem> https://launchpad.net/nova/+milestone/liberty-1
21:11:48 <johnthetubaguy> mriedem: so we might stop using milestones like we used to
21:11:55 <johnthetubaguy> there is a wiki page on the new plan
21:11:59 <mriedem> i can't live w/o an integrated release
21:12:05 <mriedem> https://wiki.openstack.org/wiki/Release_Cycle_Management/Liberty_Tracking
21:12:14 <johnthetubaguy> basically, just going to use milestones to say what shipped
21:12:20 * sc68cal is moving to a different room, brb
21:12:37 <johnthetubaguy> we never could predict when, so lets give up messing around with that, basically
21:12:42 <dansmith> +1
21:13:05 <jogo> +1
21:13:12 <bauzas> cool
21:13:14 <alaski> sounds great
21:13:30 <johnthetubaguy> so summit ideas, there is a plan for a nova-drivers meeting on monday, 21.00UTC I think
21:13:45 <johnthetubaguy> the time might change, but thats the general idea
21:13:46 <mriedem> https://etherpad.openstack.org/p/liberty-nova-summit-ideas
21:13:52 <mriedem> https://etherpad.openstack.org/p/liberty-nova-priorities
21:14:02 <johnthetubaguy> so please get your ideas in, so we can do a first pass
21:14:32 <johnthetubaguy> we need to pick deadlines etc, etc, and advertise them, but yeah, usual things really
21:15:11 <johnthetubaguy> I think we might try ask for pre-reading like we did last time, if that helped people?
21:15:40 <mikal> I think that's a good idea
21:15:45 <alaski> seemed to help
21:15:45 <mikal> It makes the session more efficient
21:16:01 <johnthetubaguy> cool, I think it did too, lets do it
21:16:29 <johnthetubaguy> for feature discussion, I am thinking at least an outline of a spec, but lets see what suggestions we have for sessions I guess, and see what they each need
21:16:47 <johnthetubaguy> I guess people saw the timetable?
21:17:16 <johnthetubaguy> Tuesday: cross project/ops Wed, Thursday: Nova all day, Friday: meetup style
21:17:30 <johnthetubaguy> wed + thurs^
21:17:39 <mriedem> thurs afternoon being a 2 block session on prioriites?
21:17:45 <mriedem> *priorities even
21:18:01 <mriedem> we didn't use the whole time in paris but it was helpful leading into friday
21:18:07 <johnthetubaguy> so we might have to move that down by one session and finish with nova-network, but yeah, that really helped
21:18:33 <johnthetubaguy> scroll down to the bottom I sketched a few idea in there, but they are random at this point
21:18:40 <mriedem> some of these are obvious 2 block sessions, like nova-network/neutron
21:18:46 <mriedem> but with topics like quotas,
21:18:59 <mriedem> that seems like a mess so not sure if it'll be 1 or 2 sessions worth
21:19:11 <mriedem> 'we know there are problems, go!'
21:19:13 <johnthetubaguy> mriedem: we can splill over into the meetup at least
21:19:30 <mriedem> yeah...i'm just thinking, more prep work is needed there for a productive outcome
21:19:32 <johnthetubaguy> mriedem: I hope we get a bit more on the table for those, but lets see :)
21:19:42 <johnthetubaguy> mriedem: exactly what I was thinking
21:19:54 <jogo> quotas one should have some pre-reading as based on what Vek says I think we can simplify things significantly
21:20:02 <bauzas> eh, sounds like Thrusday is already planned :)
21:20:56 <mriedem> yeah idk about some of these in https://etherpad.openstack.org/p/liberty-nova-priorities
21:21:10 <mriedem> i mean, they are good, but some just sound like they are going to be a mess,
21:21:11 <johnthetubaguy> mriedem: yeah, +1
21:21:18 <johnthetubaguy> so the way I was thinking
21:21:22 <mriedem> e.g. pulling out virt drivers and/or scaling out reviews
21:21:28 <johnthetubaguy> Wednesday lets to non-ops related
21:21:36 <johnthetubaguy> Thursday, more ops-ey
21:21:39 <bauzas> oh ok
21:21:43 <johnthetubaguy> as there are no ops sessions on Thursday
21:21:52 <johnthetubaguy> but thats just a random scheduling idea
21:22:18 <bauzas> sounds a good idea - some issues are not related to only one component - like error logging
21:22:40 <mriedem> well, tuesday is cross-project day right?
21:22:44 <mriedem> monday is operators meetup
21:22:49 <mriedem> wed-thurs is project specifi
21:22:51 <mriedem> *specific
21:22:55 <mriedem> friday is pants off dance off
21:22:59 <sc68cal> woo!
21:23:11 <johnthetubaguy> mriedem: roughly, but ops have stuff on Wed as well now
21:23:17 <johnthetubaguy> let me find the link...
21:23:30 <johnthetubaguy> https://docs.google.com/spreadsheets/d/1VsFdRYGbX5eCde81XDV7TrPBfEC7cgtOFikruYmqbPY/edit?usp=sharing
21:23:49 <johnthetubaguy> anyways, I guess we should move on, ideas please on the etherpads
21:24:10 <mriedem> i can't tell if it's better to do the nebulous / controversial talks earlier in the week or later
21:24:13 <johnthetubaguy> if you are wanting to lead something, do put your name down
21:24:50 <johnthetubaguy> mriedem: its tempting to leave some to friday afternoon, but they are more important than that really
21:25:13 <dansmith> last time, I think friday was full of things we found during the week, right?
21:25:24 <johnthetubaguy> yeah, we sure need to leave time for that
21:25:26 <dansmith> so I'm hestitant to plan to much so we don't lose that time to discuss things that come up
21:25:29 <dansmith> *too
21:25:37 <johnthetubaguy> thats fair
21:25:50 <johnthetubaguy> but its an excuse for only using one slot earlier in the week I guess
21:26:06 <johnthetubaguy> but hopefully that all becomes obvious
21:27:25 <johnthetubaguy> any more on liberty release stuff?
21:28:24 <johnthetubaguy> mriedem: is it time for bug chat?
21:28:37 <mriedem> yeah
21:28:38 <mriedem> gate is fine
21:28:39 <mriedem> http://status.openstack.org/elastic-recheck/gate.html
21:28:44 <mriedem> busted yesterday, fixed today
21:28:53 <mriedem> there isn't anything in the agenda about bugs
21:29:03 <johnthetubaguy> hmm, there was
21:29:13 <johnthetubaguy> https://wiki.openstack.org/wiki/Meetings/Nova
21:29:14 <dansmith> that was probably old
21:29:34 <mriedem> yeah it's blank now
21:29:37 <johnthetubaguy> dansmith: I updated it, honest, mostly deleted stuff
21:29:45 <johnthetubaguy> oh I see, yeah, nothing more in there
21:29:49 <jogo> still working in getting shelving working better for multinode
21:30:00 <jogo> https://bugs.launchpad.net/nova/+bug/1445569
21:30:00 <openstack> Launchpad bug 1445569 in OpenStack Compute (nova) "No dhcp lease after shelve unshelve" [Undecided,Confirmed]
21:30:12 <johnthetubaguy> jogo: how is multinode generally?
21:30:20 <jogo> johnthetubaguy: that is the last big issue actually
21:30:24 <jogo> getting close to being able to gate on it
21:30:28 <dansmith> multinode is rocking
21:30:29 <johnthetubaguy> sweet
21:30:29 <jogo> and make it default
21:30:36 <jogo> http://jogo.github.io/gate/multinode.html
21:30:39 * johnthetubaguy group hug
21:30:40 <jogo> very very rough numbers
21:30:46 <jogo> looks really stable today
21:31:00 <mriedem> shelve was the last failure i saw on it too
21:31:06 <mriedem> (un)shelve
21:31:15 <mriedem> also, the cells job was green earlier in the week
21:31:16 <jogo> possible fix https://review.openstack.org/#/c/85249/18
21:31:23 <mriedem> alaski: any regressions on the cells job?
21:31:30 <dansmith> so I think alaski was going to bring up making cells voting here
21:31:33 <johnthetubaguy> cells starting to pass, multi-node starting to pass, what is this strange planet I have landed on?
21:31:39 <dansmith> from what I've seen it's pretty stable
21:31:42 <alaski> there have been a few failures in the cells job
21:31:45 <alaski> not many though
21:31:53 <dansmith> alaski: are they cells-related or normal failures?
21:31:53 <mriedem> actual cells problems though?
21:31:59 <dansmith> jinx
21:32:01 <jogo> alaski: failures as in instabilities in the test?
21:32:13 <alaski> likely race conditions, haven't had a chance to dig
21:32:14 <jogo> how far are we from voting on cells?
21:32:20 <jogo> ahh
21:32:25 <mriedem> i guess we can check logstash
21:32:28 <bauzas> alaski: race conditions related the one we know ?
21:32:32 <dansmith> jogo: the point is, we're close
21:32:37 <bauzas> alaski: like on instance.save() ?
21:32:39 <jogo> dansmith: \o/
21:32:42 <alaski> bauzas: very likely, need some time to confirm
21:32:55 <bauzas> alaski: okay, sounds like we need to bust it
21:33:02 <bauzas> anyway
21:33:05 <dansmith> so maybe plan for next week at the meeting, after we've had time to digest them?
21:33:20 <alaski> yes, that would be good
21:33:21 <dansmith> plan to revisit and maybe make it voting, that is
21:33:34 <bauzas> +1
21:33:36 <alaski> I have an idea for a fix as well, just need to do it
21:33:47 <alaski> if it's what I think it is
21:34:59 <dansmith> so, moving on?
21:35:07 <johnthetubaguy> +1
21:35:17 <mriedem> yeah, only open discussion was a review request for https://review.openstack.org/#/c/174764/
21:35:20 <mriedem> which isn't a stuck revivew
21:35:28 <mriedem> well, maybe
21:35:32 <mriedem> mikal: -1'ed
21:35:52 <dansmith> no
21:35:57 <dansmith> I don't think it's stuck
21:36:20 <johnthetubaguy> it might need a -2 due to an non-approved spec, but that seems harsh on a first time contribution
21:36:27 <dansmith> it's a spec
21:36:35 <bauzas> +1
21:36:40 <johnthetubaguy> I can't read, sorry
21:36:41 <bauzas> we need to digest it
21:36:43 <dansmith> but it might need a  -2 based on the thing it's trying to do :)
21:37:01 <dansmith> I think this is, yet again, something we don't want to do in nova
21:37:02 <mriedem> it wants nova to do health monitoring of compute nodes to automatically fence them i think based on hw failures
21:37:15 <dansmith> not fencing,
21:37:24 <johnthetubaguy> dansmith: I am going to attempt a dev ref doc to describe those
21:37:24 <dansmith> just reporting health and scheduling based on it I think
21:37:42 <dansmith> johnthetubaguy: to describe what?
21:37:43 <mriedem> ok, didn't read the details, just mikal's response
21:38:09 <bauzas> johnthetubaguy: speaking of the sched efforts ?
21:38:12 <dansmith> we've been through this before with previous attempts to schedule based on link state, etc
21:38:29 <bauzas> that's all related to extensibility
21:38:37 <johnthetubaguy> dansmith: things like, not keen on orchestration in nova, etc, trying to describe the project scope a little, and keep a list of examples for when this stuff comes back around
21:38:43 <bauzas> atm, sounds hard to do that easily
21:38:44 <alaski> it sounds like we could use some documentation on what is appropriate to feed into the scheduler
21:38:45 <dansmith> johnthetubaguy: ah, cool
21:39:02 <johnthetubaguy> alaski: yeah, thats very true
21:39:18 <alaski> johnthetubaguy: sounds like it falls under what you just described
21:39:24 <dansmith> yep
21:39:29 <dansmith> I'd like to -2 with a url to why :)
21:39:41 <johnthetubaguy> dansmith: you are reading my mind
21:39:43 <dansmith> this falls under section 4 of "we don't do this"
21:40:11 <dansmith> devref/things-we-don't-do.rst
21:40:14 <johnthetubaguy> I will try do something like that, I think we might need it soon
21:40:17 <johnthetubaguy> lol
21:40:18 <dansmith> cool
21:40:44 <bauzas> well, that's actually a fair question ? what's a resource that the RT needs to track ?
21:40:59 <bauzas> but let's discuss that in the devref change :)
21:41:53 <dansmith> yep
21:42:00 <dansmith> so, what else?
21:42:09 <andreykurilin__> I have a topic/request for discussion.
21:42:10 <johnthetubaguy> I think the agenda has run dry
21:42:19 <mikal> So to summarize that review, dansmith agrees with me?
21:42:26 * sc68cal has a topic for open discussion
21:42:28 <mikal> I'll get some sort of commemorative plague made immediately
21:42:31 <dansmith> mikal: and not even because I have to anymore!
21:42:44 <alaski> I hope you meant plaque
21:42:49 <dansmith> haha
21:42:51 <jogo> lol
21:42:54 <johnthetubaguy> lol
21:42:55 <mikal> alaski: possibly, I need a dictionary
21:42:56 <dansmith> alaski: maybe not
21:43:19 <alaski> dansmith: yeah, I'm not assuming
21:43:21 <beagles> just a little plague.. like the sniffles and a localized rash
21:43:26 <dansmith> hah
21:43:34 <mriedem> so andreykurilin and sc68cal had things
21:43:44 <mriedem> andreykurilin: you're first
21:43:49 <andreykurilin__> thanks)
21:43:52 <dansmith> bonus points for brevity
21:43:56 <andreykurilin__> There is a chain of patches in novaclient related to support of microversion. Can I ask you to review them? They are already finished, just waiting for review and small fix in nova.
21:44:11 <mriedem> so that's not controversial this week?
21:44:12 <dansmith> I think we talked about this in a recent week, right?
21:44:13 <mriedem> it was last week
21:44:28 <johnthetubaguy> andreykurilin__: you got the link to those now?
21:44:33 <andreykurilin__> last patch in chain https://review.openstack.org/#/c/136458/
21:44:45 <andreykurilin__> and thread in mailing http://lists.openstack.org/pipermail/openstack-dev/2015-April/061183.html
21:46:15 <mriedem> speaking of microversions, i've been wondering about testing with those in tempest...
21:46:17 <andreykurilin__> functional job is failed in last patch due to small bug in nova api side
21:46:18 <mriedem> but i'll wait
21:47:11 <mikal> andreykurilin__: does that bug fix need a back port to kilo?
21:47:31 <mriedem> moving on?
21:47:34 <andreykurilin__> mikal: it should be merged to master at first:)
21:47:35 * mriedem looks at clock
21:47:37 <andreykurilin__> mikal: https://review.openstack.org/#/c/176817/
21:47:50 <dansmith> mriedem: yes
21:47:57 <johnthetubaguy> its tagged so thats cool
21:48:05 <mriedem> sc68cal: you're up
21:48:11 * sc68cal prepares paste
21:48:14 <sc68cal> If we could take a look at https://review.openstack.org/#/c/168701/ ? It's the last patch before we can merge the dual stack testing change (https://review.openstack.org/#/c/160856/), that'd be great.
21:48:17 <lennyb> I know its not in agenda, but I would like to bring up http://lists.openstack.org/pipermail/openstack-dev/2015-March/058779.html
21:48:39 <sc68cal> and then
21:48:39 <sc68cal> Cross-project coordination
21:48:39 <sc68cal> http://lists.openstack.org/pipermail/openstack-dev/2015-April/062327.html
21:48:46 * sc68cal is finished
21:49:05 <mriedem> sc68cal: has anyone said they'd be the nova counterpart there?
21:49:17 * mriedem nominates beagles
21:49:32 <sc68cal> mriedem: i'll check the ml, but not to my knowledge
21:49:53 <mriedem> beagles has had some specs for redoing the neutronv2 api in nova, so that's why i threw him under the bus
21:50:24 <mriedem> ok, lennyb?
21:50:25 <beagles> mriedem, I was thinking of stepping forward, but I wanted to make sure I have support from the PTB before doing so... as it happens my PTBs happen to be on holiday the last couple of days
21:50:32 <mriedem> PTB?
21:50:37 <beagles> powers that be
21:50:38 <lennyb> mriedem, yeah
21:50:50 <mriedem> beagles: understandable
21:51:04 <beagles> in any case... I'd like to play part regardless
21:51:11 <mriedem> lennyb: i'm all for pci ci
21:51:12 <mriedem> in nova
21:51:20 <mriedem> we have intel ci so what's the difference with mellanox pci ci?
21:51:43 <dansmith> tests their adapters, I assume
21:51:46 <dansmith> they have a different vif driver, right?
21:51:52 <lennyb> We are asking to permit us non voting nova ci.
21:52:04 <n0ano> mriedem, that'd be my guess, Intel CI only tests intel NICs
21:52:08 <anteaya> to clarify they just want permission to comment
21:52:08 <mriedem> yeah, i was wondering if there was some non-vendor pci code that the mellanox job hits which the intel one doesn't
21:52:36 <dansmith> yes
21:52:37 <mriedem> b/c it's my understanding that the intel pci ci is pretty limited to the configuration it tests
21:52:38 <anteaya> I think the email might have been interpreted as them requesting voting permissions, which they aren't at the moment
21:52:39 <dansmith> the vif driver
21:52:40 <lennyb> we have our own cards and drivers
21:52:45 <dansmith> anteaya: it says commenting
21:52:48 <johnthetubaguy> lennyb: I guess you publish the list of tempest tests you run?
21:52:52 <anteaya> dansmith: yes
21:52:58 <mriedem> lennyb: is it even tempest?
21:53:23 <mriedem> intel pci ci isn't *tempest* per se, it's their own tests in a tempest framework
21:53:27 <mriedem> and i don't know if those tests are on github
21:53:48 <mriedem> lennyb: so is your test code in the open somewhere?
21:53:56 <lennyb> mriedem, it's tempest
21:54:09 <johnthetubaguy> perfect, sounds like we want it then
21:54:25 <jogo> how do tempest tests test the PCI bits?
21:54:25 <mriedem> but is it http://git.openstack.org/cgit/openstack/tempest/ ?
21:54:29 <dansmith> hopefully it's tempest plus some pci bits right?
21:54:38 <mriedem> yes, i assume that's what it is ^
21:54:43 <dansmith> I didn't think we had much if any tempest pci tests
21:54:47 <mriedem> we don't
21:54:55 <mriedem> i'm wondering if the extra bits are on github
21:54:58 <lennyb> and we are working to add more tests to SRiOV
21:54:59 <dansmith> so if not, then it's not testing much
21:55:04 <johnthetubaguy> is that not just boot a VM sorts of tests? if its SRiOV
21:55:35 <dansmith> johnthetubaguy: depends on the flavor and configuration I guess
21:55:48 <johnthetubaguy> very true
21:55:50 <dansmith> how about this,
21:55:59 <lennyb> there are also different port configurations like direct
21:56:16 <dansmith> lennyb: can you post to the ML about what you're running now, what it's covering other than what we have with infra, what your plans are for the future, and links to code and reports?
21:56:18 <johnthetubaguy> dansmith: do we have that list of test requirements still?
21:56:31 <dansmith> I think we don't need to spend time on the meeting discussing this, we just need to have details to look at
21:56:43 <dansmith> johnthetubaguy: it's probably very out of date
21:56:58 <dansmith> johnthetubaguy: and not quite aimed at this specifically
21:57:09 <anteaya> just for perspective, this is why they begin commenting, so that you can look at what they provide and they can fill in gaps as they go along
21:57:27 <dansmith> anteaya: I think we just want some indication that it's testing useful things
21:57:34 <dansmith> anteaya: but also, that's why we don't really need to discuss it here I think
21:57:39 <anteaya> dansmith: that's fine
21:57:46 <dansmith> let's just get some more details, and plan to follow up on the ML
21:58:01 <johnthetubaguy> sounds like we ask questions on the ML thread, which is cool
21:58:05 <anteaya> they have just been trying to get some response for 2 months is all
21:58:06 <dansmith> and anteaya and lennyb can poke johnthetubaguy mriedem and myself if it's not answered in a few days, okay?
21:58:14 <anteaya> dansmith: can do, thank you
21:58:20 <lennyb> dansmith: I will post to ML.
21:58:23 <johnthetubaguy> cool
21:58:27 <dansmith> johnthetubaguy: mriedem cool with that?
21:58:29 <lennyb> thanks
21:58:31 <mriedem> yes
21:58:34 <johnthetubaguy> dansmith: +1
21:58:35 <mriedem> 2 min left
21:58:36 <mriedem> let's close
21:58:43 <dansmith> please :)
21:58:47 <johnthetubaguy> +1
21:58:49 <mriedem> #endmeeting