Oh, and a final option is to split out the Plug-specific code into the extras repo, and commit only changes to other bits of CloudStack.
DL > -----Original Message----- > From: Donal Lafferty [mailto:donal.laffe...@citrix.com] > Sent: 31 January 2013 22:17 > To: cloudstack-dev@incubator.apache.org > Subject: RE: Redistributing 3rd party code licensed under Apache License 2.0 > > Calling WMI from Python is a short term solution to allow for proof of > concept. > > In the immediate term, the Python code in the repo can be changed out for a > derivative of Cloud.com's work. This would allow the owners of Cloud.com's > IP to donate the code assuming the owners are Citrix and able to release the > IP. > > Chiradeep, you might know better what position the Cloud.com > contributions to OpenStack are in. I'm thinking of the OpenStack Hyper-V > driver in the Diablo branch > > For next release, the WMI calls are to be carried out directly from Java. > Microsoft have suggested a Java stack for access to WMI via WS-Man. > > > DL > > > > -----Original Message----- > > From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com] > > Sent: 31 January 2013 21:56 > > To: cloudstack-dev@incubator.apache.org > > Subject: Re: Redistributing 3rd party code licensed under Apache > > License 2.0 > > > > I'd like Donal to offer up an alternative implementation if possible. > > Is this the long-term supportable implementation? Or is it just a hack > > to get things moving? > > > > > > On 1/31/13 10:16 AM, "David Nalley" <da...@gnsa.us> wrote: > > > > >On Thu, Jan 31, 2013 at 1:11 PM, Donal Lafferty > > ><donal.laffe...@citrix.com> wrote: > > >> As a non-committer, developing in the Apache repository was never > > >>an option. > > >> > > >> Would Citrix want the Hyper-V driver it bought with Cloud.com? > > >> > > >> Is there a NOTICE-based means of including Apache Licence 2.0 code > > >>in the repository that originated with the OpenStack project? > > >> > > >> Should I put the driver in the 'extras' folder? > > >> > > >> I'm not sure what procedures are available. > > >> > > > > > >So, quite honestly, we don't know either. We've sought out advice > > >from mentors and they've pointed us to legal-discuss, and that > > >conversation is happening there now. Lets not get too concerned until > > >we find out what the folks who do know say and we can figure a path > from there. > > > > > >--David
