[openstack-dev] [tc][kolla] Ansible module with GPLv3

Steven Dake (stdake) stdake at cisco.com
Fri Nov 4 23:31:43 UTC 2016


I didn’t even know ansible had a BSD licensed example module.  As we have a module expertise in our community already, I suspect we will start from zero code rather than introduce a BSD license addendum to the Kolla repo.


From: Jeremy Stanley <fungi at yuggoth.org>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>
Date: Friday, November 4, 2016 at 4:05 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

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:


So yes, as long as you don't fork or copy from a GPL'd plug-in, your
plug-in could be implemented in other licenses and could even copy
from Ansible's BSD-licensed basic module example.
Jeremy Stanley

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20161104/15b89e91/attachment.html>

More information about the OpenStack-dev mailing list