Let's remove the docker container created with Jaeger Tracing when
unstacking, this avoid `./stack.sh` to fail when recreating the
environnement mentioning that a docker container named jaeger already
exists.
Signed-off-by: Sahid Orentino Ferdjaoui <sahid.ferdjaoui@industrialdiscipline.com>
Change-Id: I785c7b23be92eb5bc4da0366f705a77c3910d5c2
When enabled, manila conf options need
to be set as well for the profiler to
work on devstack.
Depends-On: I3bce1f04d1cfebfacd78ed135a949a068c78987d
Change-Id: Ibdbcad7cf5b19442a36ff06b935153960200b96d
The placement service has a separate config file that also needs to be
modified if osprofiler is enabled in devstack.
Change-Id: I7fa963b20498549d4241ccb16cfbca8ddf70eef5
This patch adds a new type of collector "sqlalchemy".
To enable it, add the following line into DevStack local.conf:
OSPROFILER_COLLECTOR=sqlalchemy
OSProfiler DevStack plugin creates database for traces and
configures all services to use it.
SQLAlchemy driver is extend to be able to list traces.
Zuul job is added to run Tempest tests with sqlalchemy driver enabled.
Change-Id: Ia943d311d78f6dfd2e6bb884c8dca725b3b2a36b
There was hardcoded "stack" user used in install_jaeger
function in devstack plugin.
Now it will use Devstack's variable $STACK_USER.
Change-Id: I15e783786440e6516dbbf01d7aa61c3854d29662
In DevStack Keystone is configured and started within the same phase
(while other services allow to be configured before starting). To apply
osprofiler configuration, Keystone needs to be reloaded.
Change-Id: Icf69c4e7f602702cf68986a6073b2cd4c0c3abe8
With I8e45888968cde8ca29548447d0b0bc00ae569fc1 osprofiler is
in the default api-paste pipeline and is installed in DevStack.
Change-Id: Ieaf6d4f543b650c8426ec5aeb1a7f173c041faef
This patch adds a new type of collector "jaeger".
To try this patch out add following lines into local.conf:
enable_plugin osprofiler https://git.openstack.org/openstack/osprofiler refs/changes/67/611067/4
OSPROFILER_BRANCH=refs/changes/67/611067/4
OSPROFILER_COLLECTOR=jaeger
Jaeger UI can be accessed on port 16686.
Change-Id: I29031764290106570a1d358f6fd653c5367ca587
System package name depends on Python version, while pip library name
is uniform for both py2 and py3.
Change-Id: I7ba7db61d2b07af4b880393bc0463d733f34f8cf
Default Tempest jobs only execute tests, but do not configure
osprofiler library. This patch adds a job that executes full
Tempest with enabled osprofiler. Currently the job is non-voting.
Depends-on: I64f30c36adbf7fb26609142f22d3e305ac9e82b5
Change-Id: Ib0ad4d22b62dba7cfea76283be2d87574f010c87
This patch adds a new configuration variable OSPROFILER_TRACE_SQLALCHEMY
with default value `True`.
Change-Id: I72c782872dac370d6d1620cf734a293f998ed7f1
Our current Ceilometer driver relies on old version of ceilometer client,
which is in deprecated state and not compatible with the latest Telemetry
projects (Panko, Gnocchi). The functionality of the driver is not tested
automatically and most probably broken. So it's time to let it go and
clean the code.
This patch leaves "messaging" driver as default for notification and
makes "connection-string" a required parameter in CLI. In the future
we may consider to change default notification driver, though it
requires proper release note handling in all affected projects.
Change-Id: Id8442c4ff13c5cc33fd909b4757757cc5f396f50
Nova Cell conductor has its own config file and Devstack plugin
should update it when osprofiler is enabled.
Change-Id: Iaa6a8de9ab9d8a27ff9bf9d56ee62cd8d290609a
Closes-Bug: #1731856
In DevStack OSProfiler is by default configured to use messaging
driver with Ceilometer backend. User can change the driver, but
still needs to install collector/storage manually. This patch
introduces configuration option `OSPROFILER_COLLECTOR` which is
used to specify which collector/storage to install into DevStack.
Currently 2 values are supported:
* `redis` to install Redis server and use Redis driver
* <empty> to keep the default behavior and use messaging driver
To test the patch on DevStack, the following lines are needed in local.conf:
enable_plugin osprofiler https://git.openstack.org/openstack/osprofiler refs/changes/06/527406/5
OSPROFILER_BRANCH=refs/changes/06/527406/5
OSPROFILER_COLLECTOR=redis
Change-Id: Ia9763605db95b3f35c8b0e51211f96ee0dd3a82d
With this patch the user can select which OSProfiler driver to use
in DevStack. The configuration parameter is `OSPROFILER_CONNECTION_STRING`.
Default empty value refers to Ceilometer-based driver (value `messaging://`).
DevStack plugin's README is updated to explain new option.
Change-Id: I608cd3e7bafd29db72e9e3e4cb8eb7437cd81ab2
OpenStack project configuration files may be stored elsewhere not in the
default /etc directory or with a different filename. Better relying on
existing environment variables set by each project devstack plugin.
Change-Id: I253739c765b469901d0bc6e0c82922645fb92545
Let the Devstack users override the default value of option
`hmac_keys` by the means of the environment variable set in
local.conf.
Change-Id: I0241abc4129f2d0130246723b78c584d448870a2
The order to enable devstack plugins is ommited which causes a
failure during the stack execution. This patch specifies this
requirement.
Change-Id: Id59072c1c17530addb45b24ccec6b3c6fe6cc6df
Closes-Bug: #1656373