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
-----Original Message-----
From: Edison Su [mailto:edison...@citrix.com]
Sent: Wednesday, July 25, 2012 6:00 PM
To: cloudstack-dev@incubator.apache.org
Subject: KVM code will be moved to plugin folder
As kvm code depends on libvirt-java, which is incompatible with Apache
license. I want to move it to plugin folder as we already did for other
hypervisors, and add a compile option to turn on/off KVM compilation.
By default, it's turned off.
If you have any patches against agent/kvm code, please check them in
ASAP. I want to start the moving in Friday.
Any comments?
