Skip to content

Commit 3e10055

Browse files
committed
Added schema-only description
1 parent bc9a5d7 commit 3e10055

File tree

1 file changed

+24
-10
lines changed

1 file changed

+24
-10
lines changed

source/installguide/management-server/_database.rst

Lines changed: 24 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -333,8 +333,23 @@ same node for MySQL. See `“Install the Database on the Management Server Node
333333
334334
#. Return to the root shell on your first Management Server.
335335

336-
#. Set up the database. The following command creates the cloud user on
337-
the database.
336+
#. Set up the database.
337+
338+
The cloudstack-setup-databases script is used for creating the cloudstack
339+
databases (cloud, cloud_usage), creating a user (cloud), granting permissions
340+
to the user and preparing the tables for the first startup of the management
341+
server.
342+
343+
The following command creates the cloud user on the database.
344+
345+
.. parsed-literal::
346+
347+
cloudstack-setup-databases cloud:<dbpassword>@<ip address mysql server> \
348+
--deploy-as=root:<password> \
349+
-e <encryption_type> \
350+
-m <management_server_key> \
351+
-k <database_key> \
352+
-i <management_server_ip>
338353
339354
- In dbpassword, specify the password to be assigned to the cloud
340355
user. You can choose to provide no password.
@@ -364,14 +379,13 @@ same node for MySQL. See `“Install the Database on the Management Server Node
364379
cluster management server node IP. If not specified, the local IP
365380
address will be used.
366381

367-
.. parsed-literal::
368-
369-
cloudstack-setup-databases cloud:<dbpassword>@<ip address mysql server> \
370-
--deploy-as=root:<password> \
371-
-e <encryption_type> \
372-
-m <management_server_key> \
373-
-k <database_key> \
374-
-i <management_server_ip>
382+
- (Optional) There is an option to bypass the two initial steps of creating
383+
the databases and granting permissions to the user. This is useful if you
384+
don't want to expose your root credentials but still want the database to
385+
be prepeared for first start up. These skipped steps will have had to be
386+
done manually prior to executing this script. This behaviour can be
387+
envoked by passing the --schema-only flag. This flag conflicts with the
388+
--deploy-as flag so the two cannot be used together.
375389

376390
When this script is finished, you should see a message like
377391
“Successfully initialized the database.”

0 commit comments

Comments
 (0)