436bc6d74b
CI fails to run on Tox v4 complaining about spaces in pass_env and not being able to run special_install.sh. Those are easy to fix and this patch fixes them in tox.ini: - Using multiple lines for the different environmental variable values in pass_env. - Allowing running tools/special_install.sh and tools/generate_uc.sh as an external commands. There is also an issue with the cinderlib entry points not being available during unit tests. This issues is not reproducible locally even using the same tox and python version as the gate, so the patch limits the tox version to v3 and prevents jobs from using v4 to unblock the gate. The patch also updates the values of the constraints branch from antelope to 2023.1 since antelope doesn't exist and without this change the patch cannot merge. Change-Id: I14ea8821aeccc43b5ddcc83862d59b1bbf4094be
Cinder Library
Introduction
The Cinder Library, also known as cinderlib, is a Python library that leverages the Cinder project to provide an object oriented abstraction around Cinder's storage drivers to allow their usage directly without running any of the Cinder services or surrounding services, such as KeyStone, MySQL or RabbitMQ.
- Free software: Apache Software License 2.0
- Documentation: https://docs.openstack.org/cinderlib/latest/
The library is intended for developers who only need the basic CRUD functionality of the drivers and don't care for all the additional features Cinder provides such as quotas, replication, multi-tenancy, migrations, retyping, scheduling, backups, authorization, authentication, REST API, etc.
The library was originally created as an external project, so it didn't have the broad range of backend testing Cinder does, and only a limited number of drivers were validated at the time. Drivers should work out of the box, and we'll keep a list of drivers that have added the cinderlib functional tests to the driver gates confirming they work and ensuring they will keep working.
Features
- Use a Cinder driver without running a DBMS, Message broker, or Cinder service.
- Using multiple simultaneous drivers on the same application.
- Basic operations support:
- Create volume
- Delete volume
- Extend volume
- Clone volume
- Create snapshot
- Delete snapshot
- Create volume from snapshot
- Connect volume
- Disconnect volume
- Local attach
- Local detach
- Validate connector
- Extra Specs for specific backend functionality.
- Backend QoS
- Multi-pool support
- Metadata persistence plugins:
- Stateless: Caller stores JSON serialization.
- Database: Metadata is stored in a database: MySQL, PostgreSQL, SQLite...
- Custom plugin: Caller provides module to store Metadata and cinderlib calls it when necessary.
Demo
