You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Donal Lafferty <do...@citrix.com> on 2013/05/30 03:17:37 UTC
Hyper-V plugin - IP Dependencies
WRT to which IP dependencies on the Agent side are build-time and which are deploy time:
AFAIK, packages with a licence explicitly mentioned below are build time dependencies. E.g. code under MICROSOFT ASP.NET MODEL VIEW CONTROLLER 4 EULA, MIT License, and Apache License, Version 2.0. These files could be distributed or if need be downloaded form NuGet.
In addition, the agent builds against the .NET Framework 4.5. The agent would not distribute .NET Framework 4.5, as these binaries would be installed before deploying the agent.
Finally, the WMI subsystem and the Hyper-V 2012 hypervisor are deploy time dependencies.
DL
> h2. IP Dependencies
>
> The C# source code and configuration files that are input for code generate are in the process of being marked with the Apache header ([http://www.apache.org/legal/src-headers.html#headers]) to indicate that Apache CloudStack will hold the copyright.
>
> Third party binaries used by the solution are the Microsoft .NET Framework 4.5, NuGet packages, and AWS .NET SDK. The AWS SDK is used to access S3 storage. The NuGet packages provide logging, JSON serialisation, and a light weight HTTP stack. The background to NuGet is that it is akin to a Maven repo, but each packages has a corresponding web page that includes details of the license for use of the package.
>
> Licenses for the NuGet packages are enumerated below. I do not have the .NET Framework 4.5 EULA to hand.
>
>
> Apache License, Version 2.0 ([http://logging.apache.org/log4net/license.html)]:
>
> AWS .NET SDK ([http://aws.amazon.com/sdkfornet/faqs/#13])
> Log4net 2.0.0 ([http://nuget.org/packages/log4net/])
>
>
> The MIT License (MIT):
>
> Newtonsoft.Json 4.5.11 [http://json.codeplex.com/license]
>
>
> MICROSOFT ASP.NET MODEL VIEW CONTROLLER 4 EULA
> ([http://www.microsoft.com/web/webpi/eula/mvc_4_eula_enu.htm])
>
> Microsoft ASP.NET Web API Core Libraries 4.0.20710.0 [http://nuget.org/packages/Microsoft.AspNet.WebApi.Core/4.0.20710.0] NuGet id="Microsoft.AspNet.WebApi.Core" version="4.0.20710.0"
> Microsoft ASP.NET Web API Client Libraries 4.0.20710.0 [http://nuget.org/packages/Microsoft.AspNet.WebApi.Client/4.0.20710.0] NuGet id="Microsoft.AspNet.WebApi.Client" version="4.0.20710.0"
> Microsoft .NET Framework 4 HTTP Client Libraries 2.0.20710.0 [http://nuget.org/packages/Microsoft.Net.Http/2.0.20710.0] NuGet id="Microsoft.Net.Http" version="2.0.20710.0"
> Microsoft ASP.NET Web API Self Host 4.0.20918.0 [http://nuget.org/packages/Microsoft.AspNet.WebApi.SelfHost/4.0.20918.0] NuGet id="Microsoft.AspNet.WebApi.SelfHost" version="4.0.20918.0"
Re: Hyper-V plugin - IP Dependencies
Posted by David Nalley <da...@gnsa.us>.
On Wed, Jul 3, 2013 at 5:18 PM, Donal Lafferty
<do...@citrix.com> wrote:
> Could I get some more clarity on how to deal with Microsoft dependencies?
>
> ".NET Framwork V4.5" is straightforward. It's like a JDK and a JRE, because after installation you can build and run against it. It comes with a separate install, so ".NET Framework v4.5" is easy to install independently, and it would show up in a list of steps for setting up a build environment or deploying the Hyper-V agent.
This doesn't worry me at all. It's a system dependency.
>
> However, I'm confused about how to treat "ASP.NET MVC4". It meets build / platform criteria. I've sub classed some of its types, and merely constructed others. Unlike the .NET Framework v4.5, it is not designed to be installed independently of the application that uses it. If we distributed source, builders would be expected to download the binaries involved. If I was writing an installer, I'd include the binaries in my install.
>
> The license is here: MICROSOFT ASP.NET MODEL VIEW CONTROLLER 4 EULA at
> http://www.microsoft.com/web/webpi/eula/mvc_4_eula_enu.htm Will there be any problem with distributing code that builds
> against it?
This I have some concerns about; and think it's worth asking on
legal-discuss about
>
> Also, I've added a dependency. For compression and decompression of bz2, I'm using http://dotnetzip.codeplex.com/license. The binary is used in a similar fashion to the "ASP.NET MVC4 binaries. Will there be any problem with distributing code that builds against it?
I don't see anything inherently wrong with it - MSPL is a category B
license. So no.
>
> Finally, what does "CI" in " an appropriate CI environment running for this code" mean?
>
Continuous integration - think Jenkins or something similar (but
really, for us, Jenkins)
RE: Hyper-V plugin - IP Dependencies
Posted by Donal Lafferty <do...@citrix.com>.
Could I get some more clarity on how to deal with Microsoft dependencies?
".NET Framwork V4.5" is straightforward. It's like a JDK and a JRE, because after installation you can build and run against it. It comes with a separate install, so ".NET Framework v4.5" is easy to install independently, and it would show up in a list of steps for setting up a build environment or deploying the Hyper-V agent.
However, I'm confused about how to treat "ASP.NET MVC4". It meets build / platform criteria. I've sub classed some of its types, and merely constructed others. Unlike the .NET Framework v4.5, it is not designed to be installed independently of the application that uses it. If we distributed source, builders would be expected to download the binaries involved. If I was writing an installer, I'd include the binaries in my install.
The license is here: MICROSOFT ASP.NET MODEL VIEW CONTROLLER 4 EULA at http://www.microsoft.com/web/webpi/eula/mvc_4_eula_enu.htm Will there be any problem with distributing code that builds against it?
Also, I've added a dependency. For compression and decompression of bz2, I'm using http://dotnetzip.codeplex.com/license. The binary is used in a similar fashion to the "ASP.NET MVC4 binaries. Will there be any problem with distributing code that builds against it?
Finally, what does "CI" in " an appropriate CI environment running for this code" mean?
> -----Original Message-----
> From: Chip Childers [mailto:chip.childers@sungard.com]
> Sent: 03 July 2013 3:40 PM
> To: dev@cloudstack.apache.org
> Subject: Re: Hyper-V plugin - IP Dependencies
>
> On Tue, Jul 02, 2013 at 02:26:50PM -0700, Kevin Kluge wrote:
> > Donal, I could not find a response to this.
> >
> > The dependencies that are Apache or MIT licensed are fine.
>
> +1
>
> >
> > I think the .NET run time dep is fine as well. I expect it will be pre-installed,
> just like ESXi is today. We just have to document that in the install guide.
> >
>
> +1, but not exactly like ESXi. This is more like the mysql-connector.
> It's a "system dependency" and "build dependency". We shouldn't plan on
> distributing it in binary or source form, and should simply document that it
> needs to be on the system for the build and / or runtime configuration.
>
> > I know there was some discussion about the build dep for the .NET
> framework. I understand the Hyper V code will not build without this .NET
> dependency present on the build machine. I think this is OK since it is similar
> to VMware again, but can anyone confirm? I expect other developers would
> require a separate build target for Hyper V, but we should have that anyway.
> >
>
> A separate build target for this code is the right way to go IMO.
>
> Other ASF projects have .NET code. Again, as stated above, this is a build and
> system dependency that we just have to document.
>
> Moving away from the legal part of the discussion, we do need to figure out
> how to get an appropriate CI environment running for this code.
>
> > -kevin
> >
> > [1] http://www.openoffice.org/tools/build_env_conf.html
> >
> >
> >
> > > -----Original Message-----
> > > From: Donal Lafferty [mailto:donal.lafferty@citrix.com]
> > > Sent: Wednesday, May 29, 2013 6:18 PM
> > > To: dev@cloudstack.apache.org; Chip Childers
> > > <ch...@sungard.com>
> > > (chip.childers@sungard.com)
> > > Subject: Hyper-V plugin - IP Dependencies
> > >
> > > WRT to which IP dependencies on the Agent side are build-time and
> > > which are deploy time:
> > >
> > > AFAIK, packages with a licence explicitly mentioned below are build
> > > time dependencies. E.g. code under MICROSOFT ASP.NET MODEL VIEW
> > > CONTROLLER 4 EULA, MIT License, and Apache License, Version 2.0.
> > > These files could be distributed or if need be downloaded form NuGet.
> > >
> > > In addition, the agent builds against the .NET Framework 4.5. The
> > > agent would not distribute .NET Framework 4.5, as these binaries
> > > would be installed before deploying the agent.
> > >
> > > Finally, the WMI subsystem and the Hyper-V 2012 hypervisor are
> > > deploy time dependencies.
> > >
> > > DL
> > >
> > >
> > > > h2. IP Dependencies
> > > >
> > > > The C# source code and configuration files that are input for code
> > > > generate
> > > are in the process of being marked with the Apache header
> > > ([http://www.apache.org/legal/src-headers.html#headers]) to indicate
> > > that Apache CloudStack will hold the copyright.
> > > >
> > > > Third party binaries used by the solution are the Microsoft .NET
> > > > Framework
> > > 4.5, NuGet packages, and AWS .NET SDK. The AWS SDK is used to
> > > access S3 storage. The NuGet packages provide logging, JSON
> > > serialisation, and a light weight HTTP stack. The background to
> > > NuGet is that it is akin to a Maven repo, but each packages has a
> > > corresponding web page that includes details of the license for use of the
> package.
> > > >
> > > > Licenses for the NuGet packages are enumerated below. I do not
> > > > have the
> > > .NET Framework 4.5 EULA to hand.
> > > >
> > > >
> > > > Apache License, Version 2.0
> > > ([http://logging.apache.org/log4net/license.html)]:
> > > >
> > > > AWS .NET SDK ([http://aws.amazon.com/sdkfornet/faqs/#13])
> > > > Log4net 2.0.0 ([http://nuget.org/packages/log4net/])
> > > >
> > > >
> > > > The MIT License (MIT):
> > > >
> > > > Newtonsoft.Json 4.5.11 [http://json.codeplex.com/license]
> > > >
> > > >
> > > > MICROSOFT ASP.NET MODEL VIEW CONTROLLER 4 EULA
> > > > ([http://www.microsoft.com/web/webpi/eula/mvc_4_eula_enu.htm])
> > > >
> > > > Microsoft ASP.NET Web API Core Libraries 4.0.20710.0
> > >
> [http://nuget.org/packages/Microsoft.AspNet.WebApi.Core/4.0.20710.0]
> > > NuGet id="Microsoft.AspNet.WebApi.Core" version="4.0.20710.0"
> > > > Microsoft ASP.NET Web API Client Libraries 4.0.20710.0
> > > [http://nuget.org/packages/Microsoft.AspNet.WebApi.Client/4.0.20710.
> > > 0] NuGet id="Microsoft.AspNet.WebApi.Client" version="4.0.20710.0"
> > > > Microsoft .NET Framework 4 HTTP Client Libraries 2.0.20710.0
> > > [http://nuget.org/packages/Microsoft.Net.Http/2.0.20710.0] NuGet
> > > id="Microsoft.Net.Http" version="2.0.20710.0"
> > > > Microsoft ASP.NET Web API Self Host 4.0.20918.0
> > > [http://nuget.org/packages/Microsoft.AspNet.WebApi.SelfHost/4.0.2091
> > > 8.0] NuGet id="Microsoft.AspNet.WebApi.SelfHost"
> > > version="4.0.20918.0"
> >
Re: Hyper-V plugin - IP Dependencies
Posted by Chip Childers <ch...@sungard.com>.
On Tue, Jul 02, 2013 at 02:26:50PM -0700, Kevin Kluge wrote:
> Donal, I could not find a response to this.
>
> The dependencies that are Apache or MIT licensed are fine.
+1
>
> I think the .NET run time dep is fine as well. I expect it will be pre-installed, just like ESXi is today. We just have to document that in the install guide.
>
+1, but not exactly like ESXi. This is more like the mysql-connector.
It's a "system dependency" and "build dependency". We shouldn't plan on
distributing it in binary or source form, and should simply document
that it needs to be on the system for the build and / or runtime
configuration.
> I know there was some discussion about the build dep for the .NET framework. I understand the Hyper V code will not build without this .NET dependency present on the build machine. I think this is OK since it is similar to VMware again, but can anyone confirm? I expect other developers would require a separate build target for Hyper V, but we should have that anyway.
>
A separate build target for this code is the right way to go IMO.
Other ASF projects have .NET code. Again, as stated above, this is a
build and system dependency that we just have to document.
Moving away from the legal part of the discussion, we do need to figure
out how to get an appropriate CI environment running for this code.
> -kevin
>
> [1] http://www.openoffice.org/tools/build_env_conf.html
>
>
>
> > -----Original Message-----
> > From: Donal Lafferty [mailto:donal.lafferty@citrix.com]
> > Sent: Wednesday, May 29, 2013 6:18 PM
> > To: dev@cloudstack.apache.org; Chip Childers <ch...@sungard.com>
> > (chip.childers@sungard.com)
> > Subject: Hyper-V plugin - IP Dependencies
> >
> > WRT to which IP dependencies on the Agent side are build-time and which are
> > deploy time:
> >
> > AFAIK, packages with a licence explicitly mentioned below are build time
> > dependencies. E.g. code under MICROSOFT ASP.NET MODEL VIEW
> > CONTROLLER 4 EULA, MIT License, and Apache License, Version 2.0. These
> > files could be distributed or if need be downloaded form NuGet.
> >
> > In addition, the agent builds against the .NET Framework 4.5. The agent would
> > not distribute .NET Framework 4.5, as these binaries would be installed before
> > deploying the agent.
> >
> > Finally, the WMI subsystem and the Hyper-V 2012 hypervisor are deploy time
> > dependencies.
> >
> > DL
> >
> >
> > > h2. IP Dependencies
> > >
> > > The C# source code and configuration files that are input for code generate
> > are in the process of being marked with the Apache header
> > ([http://www.apache.org/legal/src-headers.html#headers]) to indicate that
> > Apache CloudStack will hold the copyright.
> > >
> > > Third party binaries used by the solution are the Microsoft .NET Framework
> > 4.5, NuGet packages, and AWS .NET SDK. The AWS SDK is used to access S3
> > storage. The NuGet packages provide logging, JSON serialisation, and a light
> > weight HTTP stack. The background to NuGet is that it is akin to a Maven repo,
> > but each packages has a corresponding web page that includes details of the
> > license for use of the package.
> > >
> > > Licenses for the NuGet packages are enumerated below. I do not have the
> > .NET Framework 4.5 EULA to hand.
> > >
> > >
> > > Apache License, Version 2.0
> > ([http://logging.apache.org/log4net/license.html)]:
> > >
> > > AWS .NET SDK ([http://aws.amazon.com/sdkfornet/faqs/#13])
> > > Log4net 2.0.0 ([http://nuget.org/packages/log4net/])
> > >
> > >
> > > The MIT License (MIT):
> > >
> > > Newtonsoft.Json 4.5.11 [http://json.codeplex.com/license]
> > >
> > >
> > > MICROSOFT ASP.NET MODEL VIEW CONTROLLER 4 EULA
> > > ([http://www.microsoft.com/web/webpi/eula/mvc_4_eula_enu.htm])
> > >
> > > Microsoft ASP.NET Web API Core Libraries 4.0.20710.0
> > [http://nuget.org/packages/Microsoft.AspNet.WebApi.Core/4.0.20710.0]
> > NuGet id="Microsoft.AspNet.WebApi.Core" version="4.0.20710.0"
> > > Microsoft ASP.NET Web API Client Libraries 4.0.20710.0
> > [http://nuget.org/packages/Microsoft.AspNet.WebApi.Client/4.0.20710.0]
> > NuGet id="Microsoft.AspNet.WebApi.Client" version="4.0.20710.0"
> > > Microsoft .NET Framework 4 HTTP Client Libraries 2.0.20710.0
> > [http://nuget.org/packages/Microsoft.Net.Http/2.0.20710.0] NuGet
> > id="Microsoft.Net.Http" version="2.0.20710.0"
> > > Microsoft ASP.NET Web API Self Host 4.0.20918.0
> > [http://nuget.org/packages/Microsoft.AspNet.WebApi.SelfHost/4.0.20918.0]
> > NuGet id="Microsoft.AspNet.WebApi.SelfHost" version="4.0.20918.0"
>
RE: Hyper-V plugin - IP Dependencies
Posted by Kevin Kluge <Ke...@citrix.com>.
Donal, I could not find a response to this.
The dependencies that are Apache or MIT licensed are fine.
I think the .NET run time dep is fine as well. I expect it will be pre-installed, just like ESXi is today. We just have to document that in the install guide.
I know there was some discussion about the build dep for the .NET framework. I understand the Hyper V code will not build without this .NET dependency present on the build machine. I think this is OK since it is similar to VMware again, but can anyone confirm? I expect other developers would require a separate build target for Hyper V, but we should have that anyway.
-kevin
[1] http://www.openoffice.org/tools/build_env_conf.html
> -----Original Message-----
> From: Donal Lafferty [mailto:donal.lafferty@citrix.com]
> Sent: Wednesday, May 29, 2013 6:18 PM
> To: dev@cloudstack.apache.org; Chip Childers <ch...@sungard.com>
> (chip.childers@sungard.com)
> Subject: Hyper-V plugin - IP Dependencies
>
> WRT to which IP dependencies on the Agent side are build-time and which are
> deploy time:
>
> AFAIK, packages with a licence explicitly mentioned below are build time
> dependencies. E.g. code under MICROSOFT ASP.NET MODEL VIEW
> CONTROLLER 4 EULA, MIT License, and Apache License, Version 2.0. These
> files could be distributed or if need be downloaded form NuGet.
>
> In addition, the agent builds against the .NET Framework 4.5. The agent would
> not distribute .NET Framework 4.5, as these binaries would be installed before
> deploying the agent.
>
> Finally, the WMI subsystem and the Hyper-V 2012 hypervisor are deploy time
> dependencies.
>
> DL
>
>
> > h2. IP Dependencies
> >
> > The C# source code and configuration files that are input for code generate
> are in the process of being marked with the Apache header
> ([http://www.apache.org/legal/src-headers.html#headers]) to indicate that
> Apache CloudStack will hold the copyright.
> >
> > Third party binaries used by the solution are the Microsoft .NET Framework
> 4.5, NuGet packages, and AWS .NET SDK. The AWS SDK is used to access S3
> storage. The NuGet packages provide logging, JSON serialisation, and a light
> weight HTTP stack. The background to NuGet is that it is akin to a Maven repo,
> but each packages has a corresponding web page that includes details of the
> license for use of the package.
> >
> > Licenses for the NuGet packages are enumerated below. I do not have the
> .NET Framework 4.5 EULA to hand.
> >
> >
> > Apache License, Version 2.0
> ([http://logging.apache.org/log4net/license.html)]:
> >
> > AWS .NET SDK ([http://aws.amazon.com/sdkfornet/faqs/#13])
> > Log4net 2.0.0 ([http://nuget.org/packages/log4net/])
> >
> >
> > The MIT License (MIT):
> >
> > Newtonsoft.Json 4.5.11 [http://json.codeplex.com/license]
> >
> >
> > MICROSOFT ASP.NET MODEL VIEW CONTROLLER 4 EULA
> > ([http://www.microsoft.com/web/webpi/eula/mvc_4_eula_enu.htm])
> >
> > Microsoft ASP.NET Web API Core Libraries 4.0.20710.0
> [http://nuget.org/packages/Microsoft.AspNet.WebApi.Core/4.0.20710.0]
> NuGet id="Microsoft.AspNet.WebApi.Core" version="4.0.20710.0"
> > Microsoft ASP.NET Web API Client Libraries 4.0.20710.0
> [http://nuget.org/packages/Microsoft.AspNet.WebApi.Client/4.0.20710.0]
> NuGet id="Microsoft.AspNet.WebApi.Client" version="4.0.20710.0"
> > Microsoft .NET Framework 4 HTTP Client Libraries 2.0.20710.0
> [http://nuget.org/packages/Microsoft.Net.Http/2.0.20710.0] NuGet
> id="Microsoft.Net.Http" version="2.0.20710.0"
> > Microsoft ASP.NET Web API Self Host 4.0.20918.0
> [http://nuget.org/packages/Microsoft.AspNet.WebApi.SelfHost/4.0.20918.0]
> NuGet id="Microsoft.AspNet.WebApi.SelfHost" version="4.0.20918.0"