openstack/openstack-manuals
Code Issues Proposed changes

Replace references to nova-volume

Browse Source 
Change all places that used nova-volume to cinder-volume.

Change-Id: I69af849bcbe2a8aa5702ad13cf8493f7888a4c21
Closes-Bug: #1289054
This commit is contained in:
Stephen Gordon 2014-03-08 17:08:28 -05:00 committed by Andreas Jaeger
parent a93463247d
commit 0598ab8aa0
4 changed files with 14 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/admin-guide-cloud/section_ts_attach_vol_fail_not_JSON.xml
View File

@ -2,13 +2,13 @@
<section xmlns="http://docbook.org/ns/docbook"
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
xml:id="section_ts_attach_vol_fail_not_JSON">
<title>Nova volume attach error, not JSON serializable</title>
<title>Volume attach error, not JSON serializable</title>
<section xml:id="section_ts_attach_vol_fail_not_JSON_problem">
<title>Problem</title>
<para>When you attach a nova volume to a VM, you will see the
error with stack trace in
<filename>/var/log/nova/nova-volume.log</filename>.
The JSON serializable issue is caused by an RPC response
<para>When you attach a volume to a VM, you will see the error
with stack trace in
<filename>/var/log/cinder/volume.log</filename>. The
JSON serializable issue is caused by an RPC response
timeout.</para>
</section>
<section xml:id="section_ts_attach_vol_fail_not_JSON_solution">

9
doc/config-reference/block-storage/drivers/ibm-storwize-svc-driver.xml
View File

@ -107,9 +107,12 @@
the port value is configured to be port 22
(SSH).</para>
<note>
<para>Make sure the compute node running the
nova-volume management driver has SSH network
access to the storage system.</para>
<para>
Make sure the compute node running the <systemitem
class="service">cinder-volume</systemitem>
management driver has SSH network access to the
storage system.
</para>
</note>
<para>To allow the driver to communicate with the Storwize
family or SVC system, you must provide the driver with

3
doc/user-guide/section_dashboard_launch_instances.xml
View File

@ -1,4 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE section [
<!-- Some useful entities borrowed from HTML -->
<!ENTITY ndash "&#x2013;">
@ -20,7 +21,7 @@
an instance from an image that you have copied to a
persistent volume</link>. The instance boots from the
volume, which is provided by <systemitem class="service"
>nova-volume</systemitem> through iSCSI. When you launch
>cinder-volume</systemitem> through iSCSI. When you launch
an instance from a volume, especially note the following
steps:</para>
<itemizedlist>

2
doc/user-guide/section_dashboard_launch_instances_from_volume.xml
View File

@ -64,7 +64,7 @@
that has been copied to the volume. The
instance is booted from the volume, which is provided
by <systemitem class="service"
>nova-volume</systemitem> through iSCSI. To launch
>cinder-volume</systemitem> through iSCSI. To launch
an instance from the volume, see <xref
linkend="dashboard_launch_instances_from_image"
/>.</para>