Remove files from master, as development will no longer occur there.
The stable branches continue to be supported while they are in
Maintained status.
Updated the README to indicate this change.
Depends-on: Ib186ac5830e5920e264d79be946995e63e960426
Depends-on: I081cd363117671eaab6a3193094d5872f9820354
Depends-on: If2b9a82cddb20543b176ee22765049db257c89b9
Depends-on: I1143e5e5ccf8103e386fe1ce614a554e7f152d9a
Change-Id: I4722b869033ad1bd357e36c4a258b6d3ea61f5d6
Make a few cleanups:
- Remove python 2.7 stanza from setup.py
- Add requires on python >= 3.6 to setup.cfg so that pypi and pip
know about the requirement
- Remove obsolete sections from setup.cfg:
* Wheel is not needed for python 3 only repo
* Some other sections are obsolete
- Update classifiers
Change-Id: Ib1a0622e256b91d2d217e0406967b05f432418e3
The project now supports Pike, Queens, Rocky, and Master, so we set the
library to accept any version from Pike onwards.
We also change the Cinder development requirements to use Cinder master
branch instead of Pike.
Our install_requires in setup.py is passing the requirements for cinder
without a comma to separate the higher and lower boundaries of the
requirement. This patch fixes it.
Use NOS-Brick project to setup OS-Brick for our Non-OpenStack use case.
This way we no longer have to care about how to setup privsep, how to
workaround the RBD connector, etc.
Github doesn't support the "include" directive, so when we fixed the
readme for the PyPi package we broke the github readme. Now it's only
presenting the demo.
To fix this we revert to having the whole readme in the README.rst file
and in setup.py we hardcode the removal of the demo section.
Besides cinderlib and cinderlib.persistence we were also including a
"tests" package we shouldn't be including.
This patch corrects this by fixing the exclude pattern in the
`setuptools.find_packages` call.
This patch adds 2 new metadata storage options based on Cinder's
SQLAlchemy support:
- DB (db entrypoint)
- SQLite in memory DB (db_memory entrypoint)
Using the DB metadata storage we can use any of the DBMSs supported by
the Cinder project.
The benefit of using the "db_memory" plugin is that some drivers that
may fail with the default "memory" plugin may work with it if the driver
is accessing the DB directly from the driver and Cinderlib hasn't mokey
patched those DB calls.
The JSON serialization mechanism that got broken when we introduced the
metadata plugin mechanism has not been fixed in this patch.
Until now we only supported storing resources in memory, and that
mechanism was tightly coupled with everything else.
This patch decouples the metadata storing into a plugin mechanism using
'Python entrypoints. The default storing mechanism is still in memory,
and for now it's the only mechanism available.
The JSON serialization mechanism has not yet been adapted to the
metadata plugin mechanism, so it will only work with the default plugin.
Adds the required infraestructure to run functional tests:
- With multiple backends, giving meaningful name to the tests
- With externally defined backends configuration
- Automatic cleanup of attachments, connections, volumes, and snapshots.
Additionally provides a basic LVM configuration for the functional tests
and a script to set things up in the system before running the actual
tests.
The tests have been validated using a configuration that included 3
backends:
- LVM
- XtremIO
- Kaminario
Adds Cinder Driver's Python dependencies as setuptools extras to
facilitate their dependency control.
The libraries and version have been extracted from the
driver-requirements.txt file in Cinder's Pike branch.