Change-Id: I2200ce6f554df0c988eb39521ce4defd75998a85 introduced [extras] to setup.cfg. This section contains support for drivers and their dependency requirements. This allows a user to pip install cinder and optionally install a driver's required pypi based library.
We also maintain driver-requrements.txt, which most driver maintainers know about.
A few things here:
(1) There's an 'all' defined in [extras] that should include all the requirements for all drivers, but it doesn't.
(2) The versions listed in setup.cfg should be the same as driver-requirements.txt, but some of them aren't.
(3) Should probably put a comment in setup.cfg saying what's going on in there, particularly about how to name the section for a new driver (i guess it's the not-fully-qualified module name?)
(4) Check the "new driver review guide" and make sure it mentions setup.cfg
(5) there are instructions somewhere for introducing a new driver, should make sure they mention setup.cfg
(6) need to decide if driver-requirements.txt is still needed, or if we should *only* be putting this info in setup.cfg. If no driver-requirements.txt any more, revise the above. Otherwise:
(7) Should probably put a comment in driver-requrements.txt reminding people about the [extras] section of setup.cfg (both 'all' and their driver-specific section)
(8) would be nice to have a test to make sure driver-requirements.txt and setup.cfg are consistent
(9) would be nice to have a job that makes sure all the stuff in setup.cfg is in fact pip-installable
This is a lot of stuff, so feel free to split this up into additional bugs as necessary.
Fix proposed to branch: master
Review: https:/