Re: [openstack-dev] [cinder] moving driver to open source
Erlon, There are exceptions to this rule ((e.g. libraries used for testing), but the general result of the thread is that all python libraries imported by the drivers must conform to OpenStack licensing. That includes Apache and several other licenses (e.g. MIT, LGPL). Alon On Tue, Sep 20, 2016 at 5:23 AM, Thierry Carrez wrote: Alon Marx wrote: > Thank you ALL for clearing up this issue. > > To sum up the discussion (not going into too many details): > From legal stand point, if one uses python libraries they should be part > of the community or confirming with the relevant licenses > (http://governance.openstack.org/reference/licensing.html). Alon, Its not clear to me what you mean with this sentence. You mean, 'all python library that is included from the drivers must conform to OpenStack licensing (i.e. Apache License)'? Erlon If one is > not using python libraries (e.g. rest, command line, etc.) the > non-python executable is considered legitimate wherever it is running. > From deployment stand point the desire is to have any piece of code that > is required on an openstack installation would be easily downloadable. > > We understand the requirements now and are working on a plan taking both > considerations into account. I wouldn't say that the situation is cleared up -- we still need to get our act together and present a more uniform response to that question across multiple projects. But AFAICT your summary accurately represents the current Cinder team position on that matter. I hope we'll be able to hold a cross-project workshop on that question in Barcelona, so that we further clear up what is appropriate in-tree, as a separate project team and as an external project, across all of OpenStack. -- Thierry Carrez (ttx) __ 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 Alon Marx Infrastructure and OpenStack Team Leader Cloud Storage Solutions IBM Systems Phone: (+972) 3 689 7824 | E-mail: alo...@il.ibm.com __ 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] [cinder] moving driver to open source
Thank you ALL for clearing up this issue. To sum up the discussion (not going into too many details): >From legal stand point, if one uses python libraries they should be part of the community or confirming with the relevant licenses ( http://governance.openstack.org/reference/licensing.html). If one is not using python libraries (e.g. rest, command line, etc.) the non-python executable is considered legitimate wherever it is running. >From deployment stand point the desire is to have any piece of code that is required on an openstack installation would be easily downloadable. We understand the requirements now and are working on a plan taking both considerations into account. Thanks, Alon __ 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-dev] [cinder] moving driver to open source
I want to share our plans to open the IBM Storage driver source code. Historically we started our way in cinder way back (in Essex if I'm not mistaken) with just a small piece of code in the community while keeping most of the driver code closed. Since then the code has grown, but we kept with the same format. We would like now to open the driver source code, while keeping the connectivity to the storage as closed source. I believe that there are other cinder drivers that have some stuff in proprietary libraries. I want to propose and formalize the principles to where we draw the line (this has also been discussed in https://review.openstack.org/#/c/341780/) on what's acceptable by the community. Based on previous discussion I understand that the rule of thumb is "as long as the majority of the driver logic is in the public driver" the community would be fine with that. Is this acceptable to the community? Regards, Alon __ 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-dev] [3rd-party-ci] Cinder CI and CI accounts
Hi All, In IBM we have several cinder drivers, with a number of CI accounts. In order to improve the CI management and maintenance, we decided to build a single Jenkins master that will run several jobs for the drivers we own. Adding the jobs to the jenkins master went ok, but we encountered a problem with the CI accounts. We have several drivers and several accounts, but in the Jenkins master, the Zuul configuration has only one gerrit account that reports. So there are several questions: 1. Was this problem encountered by others? How did they solve it? 2. Is there a way to configure Zuul on the Jenkins master to report different jobs with different CI accounts? 3. If there is no way to configure the master to use several CI accounts, should we build a Jenkins master per driver? 4. Or another alternative, should we use a single CI account for all drivers we own, and report all results under that account? We'll appreciate any input. Thanks, Alon ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [cinder][FFE] request for exceptions in xiv_ds8k driver
Hi, Please consider the following code changes as Feature Freeze Exceptions. The first code change is needed to support the latest XIV release (version 11.5.0) and is very important for us, and the second code change is simply support for backups. Add domain support for XIV with multitenancy https://review.openstack.org/#/c/118290/ Add support for backups to xiv_ds8k driver https://review.openstack.org/#/c/118298/ Both changes were uploaded, reviewed and all relevant changes made by Juno-3 date. Both changes are very small and simple. Both changes affect only the xiv_ds8k driver. Because the changes are small and simple and have no general affect the risk is negligible. Thank you, Alon Marx mobile +972549170122, office +97236897824 email alo...@il.ibm.com IBM XIV, Cloud Storage Solutions (previously HSG) ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] AUTO: Alon Marx is out of the office (returning 04/20/2014)
I am out of the office until 04/20/2014. I will be out of the office August 9 to August 12. I will have no email connectivity and no phone connectivity. For any urgent matters please contact Ohad Atia. Note: This is an automated response to your message "OpenStack-dev Digest, Vol 24, Issue 44" sent on 16/04/2014 0:14:16. This is the only notification you will receive while this person is away. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
