[openstack-dev] [kolla] Committing proprietary plugins to OpenStack

Eduardo Gonzalez dabarren at gmail.com
Mon Sep 17 12:10:52 UTC 2018

Hi Shyam,

We offer methods [0] to allow users add their plugins during build time
through template overrides.
This allows extends dockerfiles with custom content as may be your use case.

Also we offer a method to add an external directory into the buildable list
of Dockerfiles with ``--config-dir /mydockerfiles/``

With this two methods you can provide your users the images or the
mechanism to customize their docker images.

In kolla's repository there is a contrib/ folder [1] for
template-overrides, not tested in CI nor supported by the team. Only
examples of things that may work or not about how to extend dockerfiles for
specific use cases.

As example, a patch under review to add overrides for cisco plugins [2]


[1] https://github.com/openstack/kolla/tree/master/contrib/template-override
[2] https://review.openstack.org/#/c/552119/

El vie., 14 sept. 2018 a las 15:20, Steven Dake (stdake) (<stdake at cisco.com>)

> ​Shyam,
> Our policy, decided long ago, is that we would work with third party
> components (such as plugins) for nova, cinder, neutron, horizon, etc that
> were proprietary as long as the code that merges into Kolla specifically is
> ASL2.
> What is your plugin for?  if its for nova, cinder, neutron, horizon, it is
> covered by this policy pretty much wholesale.  If its a different type of
> system, some debate may be warranted by the core team.
> Cheers
> -steve
> ------------------------------
> *From:* Shyam Biradar <shyam.biradar at trilio.io>
> *Sent:* Wednesday, September 12, 2018 5:01 AM
> *To:* Andreas Jaeger
> *Cc:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [kolla] Committing proprietary plugins to
> OpenStack
> Yes Andreas, whatever deployment scripts we will be pushing it will be
> under apache license.
> [image: logo]
> *Shyam Biradar*  * Software Engineer | DevOps*
> M <M%20617.308.9017>+91 8600266938 | shyam.biradar at trilio.io | trilio.io
> On Wed, Sep 12, 2018 at 5:24 PM, Andreas Jaeger <aj at suse.com> wrote:
>> On 2018-09-12 13:21, Shyam Biradar wrote:
>>> Hi,
>>> We have a proprietary openstack plugin. We want to commit deployment
>>> scripts like containers and heat templates to upstream in tripleo and kolla
>>> project but not actual product code.
>>> Is it possible? Or How can we handle this case? Any thoughts are welcome.
>> It's first a legal question - is everything you are pushing under the
>> Apache license as the rest of the project that you push to?
>> And then a policy of kolla project, so let me tag them
>> Andreas
>> --
>>  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
>>   SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nür
>> <https://maps.google.com/?q=E+LINUX+GmbH,+Maxfeldstr.+5,+90409+N%C3%BCr&entry=gmail&source=g>nberg,
>> Germany
>>    GF: Felix Imendörffer, Jane Smithard, Graham Norton,
>>        HRB 21284 (AG Nürnberg)
>>     GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
> __________________________________________________________________________
> 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/20180917/6b304066/attachment.html>

More information about the OpenStack-dev mailing list