059a940392
This patch provides a refactoring of the metric configuration model (and file description) to improve genericity, maintainability and usage for non-openstack deployment. The new metric yaml format is defined in the attached story task and is validated on load with voluptuous. Now, a processor is dedicated to one collector and one storage backend. Thus, collector and storage configuration go back to the cloudkitty oslo conf. Collectors have been refactored to have a code as similar as possible, in order to ease comprehension for new contributors. Story: 2001883 Task: 14354 Task: 14355 Task: 14431 Change-Id: I948dd9cd5c113bdaa4e49c532354938ffb45f0e7
31 lines
1.0 KiB
Plaintext
31 lines
1.0 KiB
Plaintext
# The order of packages is significant, because pip processes them in the order
|
|
# of appearance. Changing the order has an impact on the overall integration
|
|
# process, which may cause wedges in the gate later.
|
|
pbr>=1.6 # Apache-2.0
|
|
alembic>=0.8.0 # MIT
|
|
eventlet!=0.18.3,>=0.18.2 # MIT
|
|
keystonemiddleware!=4.1.0,>=4.0.0 # Apache-2.0
|
|
gnocchiclient>=2.5.0 # Apache-2.0
|
|
python-monascaclient>=1.7.0 # Apache-2.0
|
|
python-keystoneclient!=1.8.0,!=2.1.0,>=1.6.0 # Apache-2.0
|
|
keystoneauth1>=2.1.0 # Apache-2.0
|
|
iso8601>=0.1.9 # MIT
|
|
PasteDeploy>=1.5.0 # MIT
|
|
pecan>=1.0.0 # BSD
|
|
WSME>=0.8 # MIT
|
|
oslo.config>=3.7.0 # Apache-2.0
|
|
oslo.context>=2.9.0 # Apache-2.0
|
|
oslo.concurrency>=3.5.0 # Apache-2.0
|
|
oslo.db>=4.1.0 # Apache-2.0
|
|
oslo.i18n>=2.1.0 # Apache-2.0
|
|
oslo.log>=1.14.0 # Apache-2.0
|
|
oslo.messaging!=5.25.0,>=5.24.2 # Apache-2.0
|
|
oslo.middleware>=3.27.0 # Apache-2.0
|
|
oslo.policy>=0.5.0 # Apache-2.0
|
|
oslo.utils>=3.5.0 # Apache-2.0
|
|
SQLAlchemy<1.1.0,>=1.0.10 # MIT
|
|
six>=1.9.0 # MIT
|
|
stevedore>=1.5.0 # Apache-2.0
|
|
tooz>=1.28.0 # Apache-2.0
|
|
voluptuous>=0.11.1,<1.0.0 # BSD-3
|