virtualization benchmark suites

[Carl Trieloff]

On 09/22/2011 05:34 PM, Dor Laor wrote:
> On 09/23/2011 12:20 AM, Anthony Liguori wrote:
>> On 09/22/2011 04:11 PM, Itamar Heim wrote:
>>>
>>>
>>>> -----Original Message-----
>>>> From: project-planning-bounces at ovirt.org
>>> [mailto:project-planning-bounces at ovirt.org] On Behalf Of Michael D
>>>> Day
>>>> Sent: Friday, September 23, 2011 0:02 AM
>>>> To: project-planning at ovirt.org
>>>> Subject: virtualization benchmark suites
>>>>
>>>> Hi folks,
>>>>
>>>> I spoke with several financial customers interested in KVM earlier
>>>> this
>>> week and two topics we discussed
>>>> were KVM benchmarking and the oVirt community. Two of the customers
>>> suggested that we contribute
>>>> benchmarking suites to oVirt as projects, and that we form a
>>> benchmarking community under oVirt.
>>>>
>>>> IBM has successfully contributed a benchmark called DayTrader to the
>>> Apache foundation and formed a
>>>> community around that benchmark, which tests middleware using
>>> transaction and networking workloads.
>>>>
>>>> I'm not proposing DayTrader. But IBM does have some distributed
>>> benchmarks that may be interesting to the
>>>> community. And others of you probably also have similar test suites.
>>>>
>>>> What is the group's feeling about benchmarking projects? If there's
>>> interest I'll pursue things on our end
>>>> (no promises). But I think this is good feedback from our customers
>>>> and
>>> am interested to hear comments on
>>>> the idea.
>>>
>>> How would that differentiate from specvirt?
>>
>> specvirt is neither free as in beer nor free as in speech.  It's not
>> something that a customer can easily obtain and play around with
>> themselves.
>
> Does such benchmark ever existed (apart from kernel build)? :)
> As you pointed Anthony, let the ovirt project first focus on simplify
> the build process before we develop a competing benchmark suite to the
> one that we base lots of our marketing over.
>
> Sorry spilling cold water, just one thing at a time.


My view is build the eco-system. That means welcome any additional
complementary project. Having multiple projects under coordination means
that each project can build at it's own rate, yet we can have
integration. Additionally, not everyone can work on the same thing. We
have the concept of project maturity, so there is no risk as long as it
is well defined and complementary.

Additionally, if a project comes in and after a year or so gets no
traction we can sunset it. This provides a healthy model to have
community innovation in and around the oVirt core project.

regards
Carl.