Open Stack

From: "Fox, Kevin M" <Kevin.Fox at pnnl.gov<mailto:Kevin.Fox at pnnl.gov>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Friday, July 3, 2015 at 12:28 PM
To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Cc: Greg DeKoenigsberg <greg at ansible.com<mailto:greg at ansible.com>>
Subject: Re: [openstack-dev] [kolla][tc] Plans for using Pre-2.0 Ansible modules

Please consider forwarding this to the legal list. The gpl is a bit c specific and can be tricky to apply to other languages, but I would expect the modules under gplv3 to require all others in process to be gpl compatable, which apache should be, but will prevent any nonopen to be used. That might be ok, but something to carefully consider.

Kevin,

I don’t grok your concern.

I don’t care about non-open source implementations of configuration bits for Kolla.

I care about GPL license contamination within the Kolla code base, which placing the libraries in a third party downloadable library package solves (#3).

This is one of many reasons distros don’t permit bundled libraries.

Regards
-steve



Thanks,
Kevin

________________________________
From: Steven Dake (stdake)
Sent: Friday, July 03, 2015 11:53:00 AM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Greg DeKoenigsberg
Subject: [openstack-dev] [kolla][tc] Plans for using Pre-2.0 Ansible modules

Kolla Devs as well as the Technical Committee,

I wanted to get the TC’s thoughts on this plan of action as we intend to apply for big tent once our Ansible code has completed implementation.  If the approach outlined in this email seems like a blocker and we should just start with #4 instead, it would be immensely helpful to know now.

The problem:
A whole slew of OpenStack modules exist upstream in the Ansible core directory.  Kolla wants to use these modules.  These files are licensed under the GPLv3.  They will be released with Ansible 2.0 but Ansible 2.0 is not yet available.  In the meantime we need these modules to execute our system.  The repo in question is:

https://github.com/ansible/ansible-modules-core

The possible solutions:
1. Mordred suggested just merging the code in our repo, but I thought this might trigger license contamination so I am not hot on this idea.
2. Relicense the upstream modules in ASL short term.  Mordred tried this but thinks its not possible because of the varied contributors.
3. Fork the repo In question, remove everything except cloud/openstack directory and turn this into a pip installable library.
4. Make a hacky solution that doesn’t use any upstream modules but gets the job done.

For the moment we have settled on #3, that is creating a repo here:

https://github.com/sdake/kolla-pre-ansible-2-openstack/

And installing these in the deployment system.  Once Ansible 2.0 is available, we would deprecate this model, and rely on Ansible 2.0 exclusively.

Thoughts or concerns on this approach?

Thanks
-steve
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150703/1c7bb0c2/attachment.html>