Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <5017A7F5.9060208@widodh.nl>
References: 
 <C66C814C1ABFA8449FF65CB44953A8B4012CB9B1EF77@SJCPMAILBOX01.citrite.net>
	<C66C814C1ABFA8449FF65CB44953A8B4012CB9B1EF92@SJCPMAILBOX01.citrite.net>
	<5017A7F5.9060208@widodh.nl>
Date: Tue, 31 Jul 2012 09:06:25 -0400
Message-ID: 
 <CA+96GG4Mhv=BO0O5crcLVHCQXQGw3PgGgJRrVXhaTZz6H3uH7w@mail.gmail.com>
Subject: Re: KVM code will be moved to plugin folder
From: Chip Childers <chip.childers@sungard.com>
To: cloudstack-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Jul 31, 2012 at 5:40 AM, Wido den Hollander <wido@widodh.nl> wrote:
>
>
> On 07/31/2012 12:03 AM, Edison Su wrote:
>>
>> KVM code is moved to plugins/hypervisor/kvm, a new jar, cloud-kvm.jar is
>> created for all the java classes used by kvm code.
>
>
> Why cloud-kvm.jar? As KVM is also a plugin shouldn't it be named
> consistently like cloud-plugin-netapp.jar, cloud-plugin-f5.jar and
> cloud-plugin-netscaler.jar?
>
> Something like:
> * cloud-plugin-kvm.jar
> * cloud-plugin-hypervisor-kvm.jar
>
> I think the second name could be a bit long, but since most of the stuff
> goes automated for building classpaths I wouldn't mind.
>
> Wido

+1 for the name change.  I'd prefer "cloud-plugin-hypervisor-kvm.jar",
because that correctly namespaces it as a HV plugin.

-chip