[openstack-dev] [kolla][tc] Plans for using Pre-2.0 Ansible modules

Sam Yaple samuel at yaple.net
Wed Jul 8 12:15:36 UTC 2015


I went ahead and wrote the temp module that will fill the gaps that the
GPLv3 modules will eventually solve. It appears that upstream Shade still
doesn't have merge the capability to create roles, even though mordred has
the reviews up. This means even if we solve the licensing issue, we will
still be lacking role usage support until shade is updated upstream.

The review listed below has a 'kolla_keystone.py' module. As well as two
modules that are licensed ASL2.0 and I have permission from the author to
use in our repo (there is a link in each module with a git commit
referencing where they were pulled from with the appropriate license).


Sam Yaple

On Tue, Jul 7, 2015 at 9:21 PM, Steven Dake (stdake) <stdake at cisco.com>

> On 7/7/15, 2:05 PM, "Robert Collins" <robertc at robertcollins.net> wrote:
> >On 4 July 2015 at 06:53, Steven Dake (stdake) <stdake at cisco.com> wrote:
> >> 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:
> >
> >As I understand our current license situation, you won't be eligible
> >for big-tent if you depend on GPLv3 code.
> >
> >From the requirements "    * Project must have no library dependencies
> >which effectively restrict
> >      how the project may be distributed or deployed
> >"
> >
> >So I'm also strongly inclined to recommend you speak to the legal list
> >about the implications here. Using a GPLv3 tool via the CLI is very
> >different (by the GPL's design) to using it as a library.
> Rob,
> I pinged legal-discuss on this matter.  I am hopeful the experts can
> provide guidance for the Technical Committee and our project as to how to
> proceed.
> Regards
> -steve
> >
> >-Rob
> >
> >
> >--
> >Robert Collins <rbtcollins at hp.com>
> >Distinguished Technologist
> >HP Converged Cloud
> >
> >__________________________________________________________________________
> >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/20150708/f3f965e3/attachment.html>

More information about the OpenStack-dev mailing list