Open Stack

We are glad to announce the release of:

oslo.metrics 0.1.0: Oslo Metrics API

This is the first release of oslo.metrics. This release is part of the
wallaby release series.

The source is available from:

    https://opendev.org/openstack/oslo.metrics

Download the package from:

    https://pypi.org/project/oslo.metrics

Please report issues through:

    https://bugs.launchpad.net/oslo.metrics/+bugs

For more details, please see below.

0.1.0
^^^^^

Other Notes

* Add reno for managing release notes.

Changes in oslo.metrics 5fbeb3dbf18651ccaf6818deb7878701d3a9a7c6..0.1.0
-----------------------------------------------------------------------

47e03c0 Improve Socket for oslo.metrics
0046d0a bump py37 to py38 in tox.ini
22bb046 Add basic tests for message processing
d9c4bc5 Add a basic test framework for oslo.metrics
274e5bf Configure zuul
94723d9 add lower-constraints
703e73d fix pep8 issues
760b1a0 Add releasenotes
a7076f4 Add project documentation
9a52cdd Setup base test environment
a0b0816 Add an entrypoints to launch oslo.metrics
b569635 Add a couple of gitignore rules
e851773 Sample oslo.metrics codes
2f817c3 Trivial change to test replication
23c6fc6 Add date for expected initial code drop
6144c69 Base content, waiting for initial code drop




Requirements updates
--------------------

diff --git a/requirements.txt b/requirements.txt
new file mode 100644
index 0000000..dbf2789
--- /dev/null
+++ b/requirements.txt
@@ -0,0 +1,13 @@
+# 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!=2.1.0,>=3.1.1 # Apache-2.0
+
+# General
+oslo.utils>=3.41.0
+oslo.log>=3.44.0
+oslo.config>=6.9.0
+
+# Metrics Exporter
+prometheus-client>=0.6.0
diff --git a/test-requirements.txt b/test-requirements.txt
new file mode 100644
index 0000000..0ca55ed
--- /dev/null
+++ b/test-requirements.txt
@@ -0,0 +1,8 @@
+# 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.
+hacking>=3.0.1,<3.1.0 # Apache-2.0
+oslotest>=3.2.0 # Apache-2.0
+# Bandit security code scanner
+bandit>=1.1.0,<1.6.0 # Apache-2.0
+stestr>=2.0.0 # Apache-2.0