mongodb installed by default to use it as a pool in tests with zaqar enabled as a part of devstack installation

Bug #1503221 reported by Venkata Mahesh Jonnalagadda on 2015-10-06
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

I configured zaqar and its backend as redis in local.conf with devstack installation. And observed, mongodb installed by default.

When I checked zaqar's script, it seems mongodb configured by default as a pool in tests!

Due to this seamless configuring of mongodb, I am seeing three issues -
1) If system already configured with mongodb seperately then it will overwrite or mislead existing mongodb server.
2) User is not aware of this secret installation of mongodb during devstack installation
3) Why there is no variable specified for pool in tests to use mongodb as backend

Any services (like mongodb, redis, zaqar client etc) to install as part of devstack installation for zaqar enabled then it has to be mentioned with variables (like ENABLED_SERVICES, ZAQAR_BACKEND etc) by the user only.

It is better to have a zaqar installation variable for pool db like ZAQAR_POOL_BACKEND. This way, user can specify required backend to install or else mongodb can be specified by default, if user didn't provided ZAQAR_POOL_BACKEND variable in local.conf.

Introduce code something like below in -

# Set up database backend as a pool in tests for zaqar

# Check pool backend and configure accordingly
if [ "$ZAQAR_POOL_BACKEND" = 'mongodb' ] ; then
     echo "Only mongodb is supported as a pool in tests"

summary: mongodb installed by default to use it as a pool in tests with zaqar
- enabled in devstack installation
+ enabled as a part of devstack installation
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers