9517be8ca6
Change If21a10c56f43a121d30aa802f2c89d31df97f121 modified nodepool to
not use the inbuilt TaskManager but use openstackapi's task handling
instead.
The statsd arguments added here don't actually do anything and are
ignored; an openstack.Connection() object doesn't setup the stats
configuration. Things are somewhat working because of the
STATSD_<HOST|PORT> environment variables -- openstacksdk notices these
and turns on stats reporting. However, it uses the default prefix
('openstack.api') which is a regression over the previous behaviour of
logging operations on a per-cloud basis.
I have proposed the dependent-change that will allow setting the
prefix for stats in the "metric" section of each cloud in the
openstacksdk config file. This will allow users to return to the
previous behaviour by setting each cloud with an individual prefix in
the cloud configuration (or, indeed keep the current behaviour by not
setting that). So along with removing the ineffective arguments, I've
updated the relevant documentation and added a release note detailing
this.
Depends-On: https://review.opendev.org/c/openstack/openstacksdk/+/786814
Change-Id: I30e57084489d822dd6152d3e5712e3cd201372ae
15 lines
741 B
YAML
15 lines
741 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
Nodepool 0.3.6 introduced an unintended behaviour change with
|
|
``openstacksdk`` ``statsd`` reporting. Due to a change in the way
|
|
nodepool manages OpenStack API calls, all API related statistics
|
|
created during interaction with clouds are now generated by
|
|
``openstacksdk`` and prefixed with ``openstack.api`` instead of
|
|
being created by nodepool and prefixed with
|
|
``nodepool.provider.<cloud>`` as in prior versions. If you wish
|
|
to revert to the prior behaviour, changes have been provided to
|
|
``openstacksdk`` to allow setting custom prefixes via the cloud
|
|
configuration file; see `statsd documentation
|
|
<https://zuul-ci.org/docs/nodepool/installation.html#statsd-and-graphite>`__
|