Re: [openstack-dev] [kolla] Committing proprietary plugins to OpenStack
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]
Regards
[0]
https://docs.openstack.org/kolla/latest/admin/image-building.html#dockerfile-customisation
[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) ()
escribió:
> 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
> *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 +91 8600266938 | shyam.bira...@trilio.io | trilio.io
>
> On Wed, Sep 12, 2018 at 5:24 PM, Andreas Jaeger 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=gmail=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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [kolla] Committing proprietary plugins to OpenStack
?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
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.
[logo]
Shyam Biradar Software Engineer | DevOps
M +91 8600266938 |
shyam.bira...@trilio.io<mailto:shyam.bira...@trilio.io> |
trilio.io<http://trilio.io/>
On Wed, Sep 12, 2018 at 5:24 PM, Andreas Jaeger
mailto:a...@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<http://suse.com>,opensuse.org<http://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=gmail=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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
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 +91 8600266938 | shyam.bira...@trilio.io | trilio.io
On Wed, Sep 12, 2018 at 5:24 PM, Andreas Jaeger 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
> 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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [kolla] Committing proprietary plugins to OpenStack
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ürnberg, 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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
