removed unnecessary spaces
Change-Id: I4c6e2bebaf7cbdf21a5fe7053008783ce2f4409d
This commit is contained in:
parent
e2f2e6dbca
commit
25dc03f85f
@ -49,7 +49,7 @@
|
||||
uuid: 3f57699a-e773-4650-a443-b4b37eed5a06
|
||||
...
|
||||
task_state: NULL
|
||||
... </computeroutput></screen></step>
|
||||
...</computeroutput></screen></step>
|
||||
</procedure>
|
||||
<procedure>
|
||||
<title>Recover the VM</title>
|
||||
|
@ -29,7 +29,7 @@
|
||||
exporting its metadata will allow you to restore the volume on a
|
||||
completely different Block Storage database, or even on a different
|
||||
cloud service. To do so, first import the backup metadata to the Block
|
||||
Storage database and then restore the backup. </para>
|
||||
Storage database and then restore the backup.</para>
|
||||
<para>To import backup metadata, run the following command as an
|
||||
OpenStack <literal>admin</literal>:</para>
|
||||
<screen><prompt>$</prompt> <userinput>cinder backup-import <replaceable>metadata</replaceable></userinput></screen>
|
||||
|
@ -73,7 +73,7 @@
|
||||
<listitem>
|
||||
<para><emphasis>The OpenStack Image Service is used to manage
|
||||
the virtual machine images in an OpenStack cluster, not
|
||||
store them. </emphasis> Instead, it provides an
|
||||
store them.</emphasis> Instead, it provides an
|
||||
abstraction to different methods for storage - a bridge to
|
||||
the storage, not the storage itself.</para>
|
||||
</listitem>
|
||||
|
@ -39,7 +39,7 @@
|
||||
<td>conn_timeout = 0.5</td><td>Connection timeout to external services</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>allow_versions = false</td><td>Enable/Disable object versioning feature </td>
|
||||
<td>allow_versions = false</td><td>Enable/Disable object versioning feature</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>auto_create_account_prefix = .</td><td>Prefix to use when automatically creating accounts</td>
|
||||
|
@ -43,7 +43,7 @@
|
||||
</tr>
|
||||
<tr>
|
||||
<td>account_suppression_time = 60</td><td>Seconds to suppress updating an account that has generated an
|
||||
error (timeout, not yet found, etc.) </td>
|
||||
error (timeout, not yet found, etc.)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>recon_cache_path = /var/cache/swift</td><td>Directory where stats for a few items will be stored</td>
|
||||
|
@ -35,7 +35,7 @@
|
||||
<tr>
|
||||
<td>process = 0</td><td>(it will actually accept(2) N + 1). Setting this to one (1) will
|
||||
only handle one request at a time, without
|
||||
accepting another request concurrently. </td>
|
||||
accepting another request concurrently.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
Loading…
Reference in New Issue
Block a user