Heya,
Just noticed that the systemvm image (still) depends on cloud-vmware.jar, if we
strip this from the distribution we need to change the storage VM to not use
the premium storage service but the regular nfs storage service. See
https://reviews.apache.org/r/6320/
https://reviews.apache.org/r/5804/
What to do?
Cheers,
Hugo
-----Original Message-----
From: David Nalley [mailto:[email protected]]
Sent: Friday, August 10, 2012 3:19 PM
To: [email protected]
Subject: Re: [DISCUSS] VMware support was: Re: vijava - some additional thoughts
On Fri, Aug 10, 2012 at 6:51 AM, Tamas Monos <[email protected]> wrote:
> Hi,
>
> Do vmware libraries really need to be removed and re-added manually?
> Could ASF not acquire permission from Vmware to redistribute their freely
> available sdk for this project?
> This 4.0 would be the first big ASF release and you want to cripple vmware
> support?
>
It's a bit more complicated than removing and re-adding. You also need to
recompile CloudStack (or at least the vmware plugin + vmware base), but if you
are going to that trouble you might as well just compile the entire thing from
source.
The problem is also more complicated than that - there are two files that are
freely redistributable (for certain constrained definitions of freely
redistributable that involve, among other things, agreeing to indemnify VMware)
vim.jar and vim25.jar. However the current implementation also makes use of
vmware-apputils.jar (and another open source-based library) which is not freely
redistributable based on my reading.
The ASF could likely get permission to redistribute those files, but that
permission wouldn't extend to other folks. Besides there are at least two other
potential solutions to the problem that don't have the same license problems.
(We are after all an open source software
project)
--David
