75e10b2a48
The current way to calculate rate of change is not precise at all and depends on the local host clock. So, we have good chance that the host clock derive a bit between each polling. Also the timestamp is polling cycle run and not the exact polled sample. This makes the rate of change transformer not accurate, and maybe wrong if the local clock have jumped to much or if a pollster make to much time to get the stats (libvirt reconnection, ...). A sample gets a new attribute monotonic_time, where we can store an accurate polling time using monotonic.monotonic(). In rate of change transformer, if the monotonic time is available we use to calculate the time delta between samples. For instance metrics, we set monotonic_time as soon as we poll it from libvirt, avoiding almost all precision issue. That makes the rate of change precise to the nanoseconds for polled samples, while keeping the timestamp identical for all samples polled during one cycle. Related-bug: #1527620 Change-Id: I40e14fb6aa595a86df9767be5758f52b7ceafc8f
54 lines
1.8 KiB
Plaintext
54 lines
1.8 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.
|
|
|
|
cachetools>=1.1.0 # MIT License
|
|
cotyledon>=1.3.0 #Apache-2.0
|
|
futures>=3.0;python_version=='2.7' or python_version=='2.6' # BSD
|
|
futurist>=0.11.0 # Apache-2.0
|
|
debtcollector>=1.2.0 # Apache-2.0
|
|
jsonpath-rw-ext>=0.1.9 # Apache-2.0
|
|
jsonschema!=2.5.0,<3.0.0,>=2.0.0 # MIT
|
|
kafka-python>=1.3.2 # Apache-2.0
|
|
keystonemiddleware!=4.1.0,>=4.0.0 # Apache-2.0
|
|
lxml>=2.3 # BSD
|
|
monotonic
|
|
msgpack-python>=0.4.0 # Apache-2.0
|
|
oslo.concurrency>=3.5.0 # Apache-2.0
|
|
oslo.config>=3.22.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.policy>=0.5.0 # Apache-2.0
|
|
oslo.reports>=0.6.0 # Apache-2.0
|
|
oslo.rootwrap>=2.0.0 # Apache-2.0
|
|
PasteDeploy>=1.5.0 # MIT
|
|
pbr>=1.6 # Apache-2.0
|
|
pecan>=1.0.0 # BSD
|
|
oslo.messaging>=5.12.0 # Apache-2.0
|
|
oslo.middleware>=3.0.0 # Apache-2.0
|
|
oslo.serialization>=1.10.0 # Apache-2.0
|
|
oslo.utils>=3.5.0 # Apache-2.0
|
|
pysnmp<5.0.0,>=4.2.3 # BSD
|
|
python-glanceclient>=2.0.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
|
|
python-neutronclient>=4.2.0 # Apache-2.0
|
|
python-novaclient!=2.33.0,>=2.29.0 # Apache-2.0
|
|
python-swiftclient>=2.2.0 # Apache-2.0
|
|
python-cinderclient>=1.6.0,!=1.7.0,!=1.7.1 # Apache-2.0
|
|
PyYAML>=3.1.0 # MIT
|
|
requests!=2.9.0,>=2.8.1 # Apache-2.0
|
|
six>=1.9.0 # MIT
|
|
SQLAlchemy>=1.0.10 # MIT
|
|
sqlalchemy-migrate>=0.9.6 # Apache-2.0
|
|
stevedore>=1.9.0 # Apache-2.0
|
|
tenacity>=3.2.1 # Apache-2.0
|
|
tooz[zake]>=1.47.0 # Apache-2.0
|
|
WebOb>=1.5.0 # MIT
|
|
WSME>=0.8 # MIT
|
|
# NOTE(jd) We do not import it directly, but WSME datetime string parsing
|
|
# behaviour changes when this library is installed
|
|
python-dateutil>=2.4.2 # BSD
|
|
os-xenapi>=0.1.1 # Apache-2.0
|