openstack
/
murano
Code Issues Proposed changes

"notification_driver" from group "DEFAULT" is deprecated 

Option "notification_driver" from group "DEFAULT" is deprecated.
Use option "driver" from group "oslo_messaging_notifications"

Reference link:
[1] https://github.com/openstack/oslo.messaging/blob/master/
    oslo_messaging/notify/notifier.py#L34
Closes-Bug: #1535611

Change-Id: Iaf88167e18e2b212323cdb7b0f0945906c57aa4d
This commit is contained in:
LiuNanke 2016-01-19 18:42:47 +08:00
parent 502d44b062
commit 636e1903dc
4 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
devstack/plugin.sh
View File

@ -150,7 +150,7 @@ function configure_murano {
configure_murano_rpc_backend
# Configure notifications for status information during provisioning
iniset $MURANO_CONF_FILE DEFAULT notification_driver messagingv2
iniset $MURANO_CONF_FILE oslo_messaging_notifications driver messagingv2
# configure the database.
iniset $MURANO_CONF_FILE database connection `database_connection_url murano`

2
doc/source/articles/debug_tips.rst
View File

@ -60,7 +60,7 @@ You can see steps of the deployments and the one that failed would have red colo
Go to the spawned virtual machine and open */etc/murano/agent.conf* or *C:\Murano\Agent\agent.conf* on Windows-based machine.
Also, you can examine agent logs, located by default at */var/log/murano-agent.log*
The first part of the log file will contain reconnection attempts to the rabbit - since the valid rabbit address and queue have not been obtained yet.
* Check that *notification_driver* option is set to `messagingv2`
* Check that *driver* option is set to `messagingv2`
* Check that linux image name is not starts with 'w' letter
* ``[exceptions.EnvironmentError]: Unexpected stack state NOT_FOUND`` - problem with heat stack creation, need to examine Heat log file.

4
doc/source/draft/admin-guide/admin_troubleshooting.rst
View File

@ -145,7 +145,7 @@ Workarounds:
:file:`/var/log/murano-agent.log` The first part of the log file contains
reconnection attempts to the RabbitMQ since the valid RabbitMQ address
and queue have not been obtained yet.
* Verify that the ``notification_driver`` option is set to ``messagingv2``
* Verify that the ``driver`` option is set to ``messagingv2``
**murano.engine.system.agent.AgentException**
@ -176,7 +176,7 @@ There are no messages, provided in applications themselves:
2015-09-21 11:14:58 — Action deploy is scheduled
2015-09-21 11:16:43 — Deployment finished successfully
To fix the problem, set the ``notification_driver`` option in the :file:`murano.config`
To fix the problem, set the ``driver`` option in the :file:`murano.config`
file to ``messagingv2``.

2
doc/source/install/manual.rst
View File

@ -161,7 +161,7 @@ Install the API service and Engine
rabbit_userid = %RABBITMQ_USER%
rabbit_password = %RABBITMQ_PASSWORD%
rabbit_virtual_host = %RABBITMQ_SERVER_VIRTUAL_HOST%
notification_driver = messagingv2
driver = messagingv2
...