Open Stack

I read what you say Steven;) strategy plugin is not module, we don't use
popen there. Also it will require importing GPL code from Ansible itself.
Clint is right in this context. Writing it from scratch is not an option to
(way to complex than docker stuff we did). Imho only option will be to
write GPL driver that will be run with popen. Question is whether this
driver can sit in Kolla repo or not, and if not, where?

On Nov 4, 2016 6:51 PM, "Steven Dake (stdake)" <stdake at cisco.com> wrote:

> Michal,
>
>
>
> Have you read nothing I’ve said?  If its new code, write it as ASL2.0.
> The fact that it plugs in or uses GPLv3 code is totally irrelevant since it
> is isolated by a network layer (specifically popen).
>
>
>
> Regards
>
> -steve
>
>
>
>
>
> *From: *Michał Jastrzębski <inc007 at gmail.com>
> *Reply-To: *"OpenStack Development Mailing List (not for usage
> questions)" <openstack-dev at lists.openstack.org>
> *Date: *Friday, November 4, 2016 at 5:54 PM
> *To: *"OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev at lists.openstack.org>
> *Subject: *Re: [openstack-dev] [tc][kolla] Ansible module with GPLv3
>
>
>
> So as Clint mentioned, strategy plugins probably will be tainted by GPL.
> One of alternatives would be to create separate project for this single
> plugin, but I'd rather avoid that.
>
> Any other alternatives comes to mind?
>
>
>
> On Nov 4, 2016 5:18 PM, "Fox, Kevin M" <Kevin.Fox at pnnl.gov> wrote:
>
> Must be gplv3 compatible. not necessarily gpl. apache license is
> compatible.
>
> Thanks,
> Kevin
> ________________________________________
> From: Clint Byrum [clint at fewbar.com]
> Sent: Friday, November 04, 2016 4:38 PM
> To: openstack-dev
> Subject: Re: [openstack-dev] [tc][kolla] Ansible module with GPLv3
>
> Excerpts from Jeremy Stanley's message of 2016-11-04 23:05:54 +0000:
> > On 2016-11-04 22:50:10 +0000 (+0000), Jeremy Stanley wrote:
> > [...]
> > > As I understand it, the challenge here is that plugins for Ansible
> > > will by definition be derivative works of Ansible and thus inherit
> > > their license choice. No amount of "clean room reimplementation"
> > > will solve that unless you also reimplement Ansible under a
> > > different license while you're at it.
> > [...]
> >
> > Further research suggests I'm wrong on this front. I was assuming
> > Ansible was providing a Python plug-in API here, in which case
> > coding to that would potentially create a derivative work. Instead
> > it looks like for at least some things they refer to as plug-ins
> > they pass around a JSON data structure which upstream Ansible has
> > said in the past they do not consider to result in plug-ins becoming
> > derivative works of Ansible. For example:
> >
> > https://github.com/ansible/ansible/blob/devel/lib/
> ansible/module_utils/basic.py
>
> Modules are not plugins.
>
> > https://groups.google.com/forum/#!topic/ansible-project/GLwe3vbwTQk
>
> Same here.
>
> > https://github.com/ansible/ansible/issues/8864
>
> This only refers to dynamic inventory, which is hardly even a plugin
> interface.
>
> Strategy plugins run in ansible itself and must import pieces of Ansible,
> and thus must be GPLv3:
>
> https://github.com/ansible/ansible/tree/devel/lib/ansible/plugins/strategy
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20161104/50d6a340/attachment.html>