From: Mark Nelson <mnelson@redhat.com>
To: Konstantin Danilov <kdanilov@mirantis.com>
Cc: ceph-devel@vger.kernel.org, Ben England <bengland@redhat.com>,
Ben Turner <bturner@redhat.com>, Kyle Bader <kbader@redhat.com>,
tyler Brekke <tbrekke@redhat.com>, cbt <cbt@ceph.com>
Subject: Re: Block storage performance test tool - would like to merge into cbt
Date: Tue, 14 Jul 2015 06:22:31 -0500 [thread overview]
Message-ID: <55A4F0F7.20204@redhat.com> (raw)
In-Reply-To: <CACxKWaw_YA=SNKuA47emK1_QVwsrehWtYaLL7no9dQEPaZ3YaA@mail.gmail.com>
Probably depends how much time it will take. I'd say if we think it
might be more than 15 minutes of discussion we should wait until the end
of the performance meeting and then talk about it. If it's fairly quick
though we could probably add it to the perf meeting itself.
Mark
On 07/14/2015 03:11 AM, Konstantin Danilov wrote:
> Mark,
>
> does Wednesday performance meeting is a good place for discussion, or
> we need a separated one?
>
> On Mon, Jul 13, 2015 at 6:16 PM, Mark Nelson <mnelson@redhat.com> wrote:
>> Hi Konstantin,
>>
>> I'm definitely interested in looking at your tools and seeing if we can
>> merge them into cbt! One of the things we lack right now in cbt is any kind
>> of real openstack integration. Right now CBT basically just assumes you've
>> already launched VMs and specified them as clients in the yaml, so being
>> able to spin up VMs in a standard way would be very useful. It might be
>> worth exploring if we can use your tool to make the cluster base class
>> "openstack aware" so that any of the eventual cluster classes (ceph, and
>> maybe some day gluster, swift, etc) can use it to launch VMs or do other
>> things. I'd really love to be able to create a cbt yaml config file and
>> iterate through parametric configuration parameters building multiple
>> different clusters and running tests against them with system monitoring and
>> data post processing happening automatically.
>>
>> The data post processing is also something that will be very useful. We
>> have a couple of folks really interested in this area as well.
>>
>> Mark
>>
>>
>>
>>
>> On 07/11/2015 03:02 AM, Konstantin Danilov wrote:
>>>
>>> Hi all,
>>>
>>> We(Mirantis ceph team) have a tool for block storage performance test,
>>> called 'wally' -
>>> https://github.com/Mirantis/disk_perf_test_tool.
>>>
>>> It has some nice features, like:
>>>
>>> * Openstack and FUEL integration (can spawn VM for tests, gather HW info,
>>> etc)
>>> * Set of tests, joined into suit, which measures different performnce
>>> aspects and
>>> creates joined report, as example -
>>> http://koder-ua.github.io/6.1GA/cinder_volume_iscsi.html,
>>> VM running on ceph drives report example -
>>> http://koder-ua.github.io/random/ceph_example.html
>>> * Data postrocessing - confidence intervals, etc
>>>
>>> We would like to merge our code into cbt. Do you interesting in it?
>>> Can we discuss a way to merge?
>>>
>>> Thanks
>>>
>>
>
>
>
next prev parent reply other threads:[~2015-07-14 11:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-11 8:02 Block storage performance test tool - would like to merge into cbt Konstantin Danilov
2015-07-13 15:16 ` Mark Nelson
2015-07-14 8:11 ` Konstantin Danilov
2015-07-14 11:22 ` Mark Nelson [this message]
2015-07-14 12:54 ` Konstantin Danilov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55A4F0F7.20204@redhat.com \
--to=mnelson@redhat.com \
--cc=bengland@redhat.com \
--cc=bturner@redhat.com \
--cc=cbt@ceph.com \
--cc=ceph-devel@vger.kernel.org \
--cc=kbader@redhat.com \
--cc=kdanilov@mirantis.com \
--cc=tbrekke@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.