fbc2b4d289
*) 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-manilaclient with this patch: https://review.opendev.org/#/c/769731 Run any command with --profile SECRET_KEY $ manila --profile SECRET_KEY create NFS 1 --name <share> \ --description <share_description> --share-network <network> \ --share-type default # 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 manila-os-profiler Change-Id: I3bce1f04d1cfebfacd78ed135a949a068c78987d
15 lines
646 B
YAML
15 lines
646 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 manila.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 manila.conf configuration
|
|
file. To allow cross-project tracing user should use the key, that is
|
|
common among all OpenStack services they want to trace.
|
|
|