9541a29761
*) Add osprofiler wsgi middleware This middleware is used for 2 things: 1) It checks that person who want to trace is trusted and knows secret HMAC key. 2) It start tracing in case of proper trace headers and add first wsgi trace point, with info about HTTP request *) Add initialization of osprofiler at start of serivce. You should use python-designateclient with this patch: https://review.opendev.org/#/c/773575 Run any command with --os-profile SECRET_KEY $ openstack zone create --email <email_id> <zone_name> \ --os-profile SECRET_KEY # it will print <Trace ID> Get pretty HTML with traces: $ osprofiler trace show --html <Trace ID> --connection-string \ <connection_string> --out <output.html> e.g. --connection-string can be redis://localhost:6379 Note that osprofiler should be run from admin user name & tenant. Implements: blueprint designate-os-profiler Change-Id: I2a3787b6428d679555a9add3a57ffe8c2112b6d3
14 lines
652 B
YAML
14 lines
652 B
YAML
---
|
|
features:
|
|
- |
|
|
OSprofiler support was introduced. To allow its usage, the api-paste.ini
|
|
file needs to be modified to contain osprofiler middleware. Also
|
|
`[profiler]` section needs to be added to the designate.conf file with
|
|
`enabled`, `hmac_keys` and `trace_sqlalchemy` flags defined.
|
|
security:
|
|
- OSprofiler support requires passing of trace information
|
|
between various OpenStack services. This information is
|
|
securely signed by one of HMAC keys, defined in designate.conf
|
|
configuration file. To allow cross-project tracing user should use the key,
|
|
that is common among all OpenStack services they want to trace.
|