Use CK_DBUSER for the mysql user in the documentation

Use CK_DBUSER for the mysql user in the documentation.

Change-Id: I0e55dc4a1306280e33f6705133f2f22ee6baf9dd
Closes-Bug: #1743741
This commit is contained in:
Christophe Sauthier 2018-01-17 11:37:32 +01:00
parent 949f18a613
commit c89a3435c5
1 changed files with 5 additions and 5 deletions

View File

@ -65,7 +65,7 @@ For keystone (identity) API v2 (deprecated)
auth_plugin = password
[database]
connection = mysql://cloudkitty:CK_DBPASSWORD@DB_HOST/cloudkitty
connection = mysql://CK_DBUSER:CK_DBPASSWORD@DB_HOST/cloudkitty
[storage]
backend = sqlalchemy
@ -126,7 +126,7 @@ The following shows the basic configuration items:
auth_section = ks_auth
[database]
connection = mysql://cloudkitty:CK_DBPASSWORD@DB_HOST/cloudkitty
connection = mysql://CK_DBUSER:CK_DBPASSWORD@DB_HOST/cloudkitty
[keystone_fetcher]
auth_section = ks_auth
@ -197,11 +197,11 @@ the ``mysql`` client::
mysql -uroot -p << EOF
CREATE DATABASE cloudkitty;
GRANT ALL PRIVILEGES ON cloudkitty.* TO 'cloudkitty'@'localhost' IDENTIFIED BY 'CK_DBPASSWORD';
GRANT ALL PRIVILEGES ON cloudkitty.* TO 'CK_DBUSER'@'localhost' IDENTIFIED BY 'CK_DBPASSWORD';
EOF
If you need to authorize the cloudkitty mysql user from another host you have
to change the line accordingly.
If you need to authorize the mysql user associated to cloudkitty from another host you
have to change the line accordingly.
Run the database synchronisation scripts::