manila

History

kpdev fbc2b4d289 Integrate OSprofiler and Manila ) 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		2021-02-25 04:59:19 +01:00
..
rootwrap.d	Add manage/unmanage implementation to Container Driver	2019-03-04 18:35:06 +00:00
api-paste.ini	Integrate OSprofiler and Manila	2021-02-25 04:59:19 +01:00
logging_sample.conf	Remove LegacyFormatter from logging_sample.conf	2015-09-24 18:43:40 +09:00
manila-policy-generator.conf	[policy in code] Add support for share instance export location resource	2017-11-16 04:39:00 +00:00
README.manila.conf	Fix couple of nit picks	2014-11-15 12:41:14 +00:00
rootwrap.conf	Fix typo in rootwrap.conf	2016-12-20 10:06:44 +00:00

README.manila.conf

To generate the sample manila.conf file, run the following
command from the top level of the manila directory:

tox -egenconfig