b88212e062
Generate the config tables with the autohelp script and include the new tables in the config ref sections. For consistency, use the 'database' and 'auth_token' keywords in all projects. Split the LBaaS tables. Closes-Bug: #1327802 Closes-Bug: #1331180 Closes-Bug: #1331175 Closes-Bug: #1330279 Closes-Bug: #1323946 Closes-Bug: #1323437 Closes-Bug: #1322075 Closes-Bug: #1321621 Closes-Bug: #1319564 Closes-Bug: #1318081 Closes-Bug: #1311474 Change-Id: I5602dda76fdf929d9124f5aa67d31ca4ac17c6d5
25 lines
1.4 KiB
XML
25 lines
1.4 KiB
XML
<section xml:id="section_configuring-database-connections"
|
|
xmlns="http://docbook.org/ns/docbook"
|
|
xmlns:xlink="http://www.w3.org/1999/xlink"
|
|
xmlns:xi="http://www.w3.org/2001/XInclude"
|
|
version="5.0">
|
|
<title>Database configuration</title>
|
|
<para>You can configure OpenStack Compute to use any
|
|
SQLAlchemy-compatible database. The database name is
|
|
<literal>nova</literal>. The <systemitem
|
|
class="service">nova-conductor</systemitem> service is the
|
|
only service that writes to the database. The other Compute
|
|
services access the database through the <systemitem
|
|
class="service">nova-conductor</systemitem> service.</para>
|
|
<para>To ensure that the database schema is current, run the following command:</para>
|
|
<screen><prompt>#</prompt> <userinput>nova-manage db sync</userinput></screen>
|
|
<para>If <systemitem class="service">nova-conductor</systemitem>
|
|
is not used, entries to the database are mostly written by the
|
|
<systemitem class="service">nova-scheduler</systemitem>
|
|
service, although all services must be able to update
|
|
entries in the database.</para>
|
|
<para>In either case, use the configuration option settings documented in
|
|
<xref linkend="config_table_nova_database"/> to configure the connection
|
|
string for the nova database.</para>
|
|
</section>
|