LICENSE question - Openstack Masakari
Hello, I would like to implement the option to use the OpenStack project Masakari together with HashiCorp Consul. Currently, Corosync is used, but it has a limitation of 32 hosts. However, my question is, if I develop a way to build the image (OpenStack project Kolla) and orchestration (OpenStack project Kolla-Ansible) of the Consul project as a necessary tool in connection with Masakari, is it possible to merge such code? I am asking because Consul is under the BSL 1.1 license and according to https://governance.openstack.org/tc/reference/licensing.html, such questions need to be consulted on this mailing list. Consul license https://github.com/hashicorp/consul/blob/main/LICENSE The BSL 1.1 text includes the sentence: "The Licensor hereby grants you the right to copy, modify, create derivative works, redistribute, and make non-production use of the Licensed Work. The Licensor may make an Additional Use Grant, above, permitting limited production use." and in the Consul License, this passage is defined as follows: Additional Use Grant: You may make production use of the Licensed Work, provided Your use does not include offering the Licensed Work to third parties on a hosted or embedded basis in order to compete with HashiCorp's paid version(s) of the Licensed Work. For purposes of this license: Does this mean that it meets the requirements of OpenStack Governance? Even though it is not an OSI-approved license? Thank you very much Michal Arbet Openstack Engineer Ultimum Technologies a.s. Na Poříčí 1047/26, 11000 Praha 1 Czech Republic +420 604 228 897 michal.arbet@ultimum.io *https://ultimum.io <https://ultimum.io/>* LinkedIn <https://www.linkedin.com/company/ultimum-technologies> | Twitter <https://twitter.com/ultimumtech> | Facebook <https://www.facebook.com/ultimumtechnologies/timeline>
On 2024-08-08 17:11:39 +0200 (+0200), Michal Arbet wrote:
I would like to implement the option to use the OpenStack project Masakari together with HashiCorp Consul. Currently, Corosync is used, but it has a limitation of 32 hosts.
However, my question is, if I develop a way to build the image (OpenStack project Kolla) and orchestration (OpenStack project Kolla-Ansible) of the Consul project as a necessary tool in connection with Masakari, is it possible to merge such code? [...]
I'm a little confused and would appreciate some clarification. You state that Masakari can presently be used with Corosync (which, as an aside, is BSD-licensed). You talk about making Consul "a necessary tool in connection with Masakari" but to what extent would it be necessary? Are you implying a removal of Corosync support from the project, so that Masakari only works with Consul in the future? You also talking about building container images and orchestrating Consul via Kolla/Kolla-Ansible, but are you wanting the project to distribute images which embed copies of (parts/all of) Consul, or merely images that could be used in conjunction with it? Thanks in advance. -- Jeremy Stanley
Hi Jeremy, Let me clarify this a bit. I am specifically asking about adding support for installing Consul in Kolla projects (images) and Kolla-Ansible (orchestration). Currently, Kolla only supports the installation of Corosync and Pacemaker, and in conjunction with Masakari, this is usable on a maximum of 32 hosts. Using Consul could allow for more. So, to reiterate, I only want to modify the Kolla and Kolla-Ansible code; I do not want to touch Masakari. I am also a core developer for these two projects, and there are various opinions on licensing within the team. Since these OpenStack projects fall under governance, I wrote here to ensure that it doesn't violate anything. A similar situation is currently with Redis – we have support in Kolla and Kolla-Ansible, but Redis changed its license only recently. In any case, I believe it is possible to provide this to users since it is not directly a sold product to a third party but only part of the architecture, not the service itself (similar to Redis for caching). Please, if there are any ambiguities, feel free to ask. Thank you very much for your response. https://governance.openstack.org/tc/reference/licensing.html On Thu, Aug 8, 2024, 18:35 Jeremy Stanley <fungi@yuggoth.org> wrote:
On 2024-08-08 17:11:39 +0200 (+0200), Michal Arbet wrote:
I would like to implement the option to use the OpenStack project Masakari together with HashiCorp Consul. Currently, Corosync is used, but it has a limitation of 32 hosts.
However, my question is, if I develop a way to build the image (OpenStack project Kolla) and orchestration (OpenStack project Kolla-Ansible) of the Consul project as a necessary tool in connection with Masakari, is it possible to merge such code? [...]
I'm a little confused and would appreciate some clarification. You state that Masakari can presently be used with Corosync (which, as an aside, is BSD-licensed). You talk about making Consul "a necessary tool in connection with Masakari" but to what extent would it be necessary? Are you implying a removal of Corosync support from the project, so that Masakari only works with Consul in the future?
You also talking about building container images and orchestrating Consul via Kolla/Kolla-Ansible, but are you wanting the project to distribute images which embed copies of (parts/all of) Consul, or merely images that could be used in conjunction with it?
Thanks in advance. -- Jeremy Stanley _______________________________________________ legal-discuss mailing list -- legal-discuss@lists.openstack.org To unsubscribe send an email to legal-discuss-leave@lists.openstack.org
On Thu, Aug 8, 2024 at 11:28 AM Michal Arbet <michal.arbet@ultimum.io> wrote:
Hello,
I would like to implement the option to use the OpenStack project Masakari together with HashiCorp Consul. Currently, Corosync is used, but it has a limitation of 32 hosts.
However, my question is, if I develop a way to build the image (OpenStack project Kolla) and orchestration (OpenStack project Kolla-Ansible) of the Consul project as a necessary tool in connection with Masakari, is it possible to merge such code?
I am asking because Consul is under the BSL 1.1 license and according to https://governance.openstack.org/tc/reference/licensing.html, such questions need to be consulted on this mailing list.
Consul license https://github.com/hashicorp/consul/blob/main/LICENSE
The BSL 1.1 text includes the sentence: "The Licensor hereby grants you the right to copy, modify, create derivative works, redistribute, and make non-production use of the Licensed Work. The Licensor may make an Additional Use Grant, above, permitting limited production use." and in the Consul License, this passage is defined as follows:
Additional Use Grant: You may make production use of the Licensed Work, provided Your use does not include offering the Licensed Work to third parties on a hosted or embedded basis in order to compete with HashiCorp's paid version(s) of the Licensed Work. For purposes of this license:
Does this mean that it meets the requirements of OpenStack Governance? Even though it is not an OSI-approved license?
Are you proposing to actually have OpenStack distribute code that is under BSL 1.1? Because I think that clearly should not be done. Richard
No, Kolla and kolla-ansible are projects for "install openstack" including components which are necessary as for example mariadb, rabbitmq. This Kolla and kolla-ansible projects are Apache2 licence - I am just asking if I can add the code which will actually install BSD license software. Because on the end it's user choice and his responsibility. As example I can point you to redis Kolla - https://github.com/openstack/kolla/tree/master/docker/redis Kolla-ansible - https://github.com/openstack/kolla-ansible/tree/master/ansible/roles/redis Redis was open-source AGPL , but now they changed - https://medium.com/@darioajr/the-new-redis-licensing-and-its-market-impact-6... For example in Kolla we had also discussion about redis removal. So I would like to know how it is, can Kolla as openstack project provide a path to *install* a software which is BSD and for example add a note to the documentation. Thanks On Thu, Aug 8, 2024, 19:10 Richard Fontana <rfontana@redhat.com> wrote:
On Thu, Aug 8, 2024 at 11:28 AM Michal Arbet <michal.arbet@ultimum.io> wrote:
Hello,
I would like to implement the option to use the OpenStack project
Masakari together with HashiCorp Consul. Currently, Corosync is used, but it has a limitation of 32 hosts.
However, my question is, if I develop a way to build the image
(OpenStack project Kolla) and orchestration (OpenStack project Kolla-Ansible) of the Consul project as a necessary tool in connection with Masakari, is it possible to merge such code?
I am asking because Consul is under the BSL 1.1 license and according to
https://governance.openstack.org/tc/reference/licensing.html, such questions need to be consulted on this mailing list.
Consul license https://github.com/hashicorp/consul/blob/main/LICENSE
The BSL 1.1 text includes the sentence: "The Licensor hereby grants you
the right to copy, modify, create derivative works, redistribute, and make non-production use of the Licensed Work. The Licensor may make an Additional Use Grant, above, permitting limited production use." and in the Consul License, this passage is defined as follows:
Additional Use Grant: You may make production use of the Licensed Work,
provided Your use does not include offering the Licensed Work to third parties on a hosted or embedded basis in order to compete with HashiCorp's paid version(s) of the Licensed Work. For purposes of this license:
Does this mean that it meets the requirements of OpenStack Governance?
Even though it is not an OSI-approved license?
Are you proposing to actually have OpenStack distribute code that is under BSL 1.1? Because I think that clearly should not be done.
Richard
I see. This is not a straightforward question of legal compliance or (AFAIK) interpretation of existing OpenStack licensing policy. FWIW CNCF has been wrestling with similar issues. I think they will be publishing some guidance on the topic in the near future. On Thu, Aug 8, 2024 at 1:35 PM Michal Arbet <michal.arbet@ultimum.io> wrote:
No,
Kolla and kolla-ansible are projects for "install openstack" including components which are necessary as for example mariadb, rabbitmq.
This Kolla and kolla-ansible projects are Apache2 licence - I am just asking if I can add the code which will actually install BSD license software.
Because on the end it's user choice and his responsibility.
As example I can point you to redis
Kolla - https://github.com/openstack/kolla/tree/master/docker/redis
Kolla-ansible - https://github.com/openstack/kolla-ansible/tree/master/ansible/roles/redis
Redis was open-source AGPL , but now they changed - https://medium.com/@darioajr/the-new-redis-licensing-and-its-market-impact-6...
For example in Kolla we had also discussion about redis removal.
So I would like to know how it is, can Kolla as openstack project provide a path to *install* a software which is BSD and for example add a note to the documentation.
Thanks
On Thu, Aug 8, 2024, 19:10 Richard Fontana <rfontana@redhat.com> wrote:
On Thu, Aug 8, 2024 at 11:28 AM Michal Arbet <michal.arbet@ultimum.io> wrote:
Hello,
I would like to implement the option to use the OpenStack project Masakari together with HashiCorp Consul. Currently, Corosync is used, but it has a limitation of 32 hosts.
However, my question is, if I develop a way to build the image (OpenStack project Kolla) and orchestration (OpenStack project Kolla-Ansible) of the Consul project as a necessary tool in connection with Masakari, is it possible to merge such code?
I am asking because Consul is under the BSL 1.1 license and according to https://governance.openstack.org/tc/reference/licensing.html, such questions need to be consulted on this mailing list.
Consul license https://github.com/hashicorp/consul/blob/main/LICENSE
The BSL 1.1 text includes the sentence: "The Licensor hereby grants you the right to copy, modify, create derivative works, redistribute, and make non-production use of the Licensed Work. The Licensor may make an Additional Use Grant, above, permitting limited production use." and in the Consul License, this passage is defined as follows:
Additional Use Grant: You may make production use of the Licensed Work, provided Your use does not include offering the Licensed Work to third parties on a hosted or embedded basis in order to compete with HashiCorp's paid version(s) of the Licensed Work. For purposes of this license:
Does this mean that it meets the requirements of OpenStack Governance? Even though it is not an OSI-approved license?
Are you proposing to actually have OpenStack distribute code that is under BSL 1.1? Because I think that clearly should not be done.
Richard
On 2024-08-08 19:35:18 +0200 (+0200), Michal Arbet wrote: [...]
This Kolla and kolla-ansible projects are Apache2 licence - I am just asking if I can add the code which will actually install BSD license software. [...] So I would like to know how it is, can Kolla as openstack project provide a path to *install* a software which is BSD and for example add a note to the documentation. [...]
To be clear, you're asking about implementing support for Consul which is under the Business Source License (abbreviated BSL), and you mentioned that it serves a similar function to Corosync (distributed under a BSD license). BSD-licensed things are generally fine as dependencies or even for direct inclusion in OpenStack projects[*], as the BSD license is considered to be compatible with the Apache License. Whether it's okay for an OpenStack project to implement support for BSL software seems like the topic up for debate. It's worth noting, though, that current versions of Vault are distributed under the BSL and OpenStack Barbican retains support for it[**], at least for the time being. [*] https://governance.openstack.org/tc/reference/licensing.html [**] https://docs.openstack.org/barbican/2024.1/install/barbican-backend.html#vau... -- Jeremy Stanley
After consulting foundation legal counsel, this type of integration should not be a problem from a licensing perspective as long as no BSL licensed code is added into OpenStack code and as long as use of the HashiCorp product remains optional.
Adding openstack discuss mailing list [Kolla] On Mon, Aug 12, 2024, 22:11 <wes@openinfra.dev> wrote:
After consulting foundation legal counsel, this type of integration should not be a problem from a licensing perspective as long as no BSL licensed code is added into OpenStack code and as long as use of the HashiCorp product remains optional. _______________________________________________ legal-discuss mailing list -- legal-discuss@lists.openstack.org To unsubscribe send an email to legal-discuss-leave@lists.openstack.org
Hello Folks, Thank you very much for your time. I am glad that it's clear now, also as a reference for others contributing to the kolla project. Regards, Michal Arbet Openstack Engineer Ultimum Technologies a.s. Na Poříčí 1047/26, 11000 Praha 1 Czech Republic +420 604 228 897 michal.arbet@ultimum.io *https://ultimum.io <https://ultimum.io/>* LinkedIn <https://www.linkedin.com/company/ultimum-technologies> | Twitter <https://twitter.com/ultimumtech> | Facebook <https://www.facebook.com/ultimumtechnologies/timeline> po 12. 8. 2024 v 22:11 odesílatel <wes@openinfra.dev> napsal:
After consulting foundation legal counsel, this type of integration should not be a problem from a licensing perspective as long as no BSL licensed code is added into OpenStack code and as long as use of the HashiCorp product remains optional. _______________________________________________ legal-discuss mailing list -- legal-discuss@lists.openstack.org To unsubscribe send an email to legal-discuss-leave@lists.openstack.org
participants (4)
-
Jeremy Stanley
-
Michal Arbet
-
Richard Fontana
-
wes＠openinfra.dev