Enabling zaqar is different as compared with other openstack services in local.conf during devstack installation

[Venkata Mahesh Jonnalagadda]

I tried to configure Zaqar as below in local.conf as part of devstack installation but it didn't installed or configured!

ENABLED_SERVICES+=zaqar
or
ENABLED_SERVICES+=,zaqar-websocket,zaqar-wsgi

To enable Zaqar in local.conf during devstack installation, I observed a different or out of sync compared with other openstack services configuring as below -

enable_service zaqar
Link: https://github.com/openstack/zaqar/blob/bfcc60c170369b3a3e3ab116e477d7a6e706e1be/devstack/settings

enable_service zaqar-websocket zaqar-wsgi
Link: https://github.com/openstack/zaqar/blob/master/devstack/settings

But, other openstack services (like horizon, nova, neutron, key, rabbit, mysql, cinder, trove etc) follow same procedure as below with variable ENABLED_SERVICES

ENABLED_SERVICES=rabbit,mysql,key
ENABLED_SERVICES+=,n-api,n-crt,n-obj,n-cpu,n-cond,n-sch,n-novnc,n-cauth
ENABLED_SERVICES+=,neutron,q-svc,q-agt,q-dhcp,q-l3,q-meta,q-lbaas

It would be great to follow the same enable procedures in local.conf even for ZAQAR with ENABLED_SERVICES variable

[Eva Balycheva (ubershy)]

Hello. I think it's not a bug. =)
Working directly with ENABLED_SERVICES environment variable inside local.conf is now deprecated.
Soon you will be unable to use ENABLED_SERVICES at all.
See: https://github.com/openstack-dev/devstack/blob/master/functions-common#L1899

New manuals suggest to use "enable_service" and "disable_service" commands.
You can rewrite your local.conf to use these commands to run your services.
See: http://docs.openstack.org/developer/devstack/configuration.html

Example for neutron from your local.conf:
enable_service neutron q-svc q-agt q-dhcp q-l3 q-meta q-lbaas

[Eva Balycheva (ubershy)]

Sorry for making noise. maybe it's not that deprecated.
And also my example will not work.
To make it work the line must be split like described here:
https://wiki.openstack.org/wiki/NeutronDevstack.

[Venkata Mahesh Jonnalagadda (vj884x)]

Currently, all openstack services (like horizon, nova, neutron, key, rabbit, mysql, cinder, trove etc) using ENABLED_SERVICES (local.conf variable) to enable the service with devstack installation. But Zaqar is not supporting it and instead it uses enable_service. Due to this, users will be out of sync and see the installation issue with Zaqar.

It would be better to support ENABLED_SERVICES variable for Zaqar until it is deprecated with other openstack services for devstack installation.

[Venkata Mahesh Jonnalagadda (vj884x)]

One more important information for devstack configuration settings ie., stackrc & localrc

stackrc is the primary configuration file for DevStack. It contains all of the settings that control the services started and the repositories used to download the source for those services. stackrc sources the localrc section of local.conf to perform the default overrides.

For more information - http://docs.openstack.org/developer/devstack/stackrc.html

Openstack service has to be mentioned in ENABLED_SERVICES to launch by default. These generally correspond to screen tabs. Other services that are not enabled by default can be enabled in localrc using enable_service.

So, if a user want to enable Zaqar service to launch by default then he has to mention it with ENABLED_SERVICES. But it is not working!

This has to be resolved for users w.r.to devstack configuration settings.

[Victoria Martinez de la Cruz (vkmc)]

As Eva mentioned, this is not a bug. ENABLED_SERVICES is being deprecated in favor to the usage of the enable_service function (which we currently do). We also support plugins (add to your local.conf enable_service zaqar <git-repo>). Feel free to ask Devstack developers about this and ask other services to deprecate the variable usage in order to achieve consistency and avoid confusion. Thanks for your report!