openstack/openstack-manuals
Code Issues Proposed changes

Merge "Adding IQN to the glossary"

Browse Source
This commit is contained in:
Jenkins 2015-10-19 03:00:03 +00:00 committed by Gerrit Code Review
commit 90a28702f5
5 changed files with 22 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/admin-guide-cloud/source/blockstorage-manage-volumes.rst
View File

@ -27,7 +27,7 @@ to a server instance.
#. Use the :command:`cinder create` command to create a volume. This
command creates an LV into the volume group (VG) ``cinder-volumes``.
#. Use the nova :command:`volume-attach` command to attach the volume
to an instance. This command creates a unique iSCSI IQN that is
to an instance. This command creates a unique :term:`IQN` that is
exposed to the compute node.
* The compute node, which runs the instance, now has an active

2
doc/admin-guide-cloud/source/ts-duplicate-3par-host.rst
View File

@ -7,7 +7,7 @@ Problem
This error may be caused by a volume being exported outside of OpenStack
using a host name different from the system name that OpenStack expects.
This error could be displayed with the IQN if the host was exported
This error could be displayed with the :term:`IQN` if the host was exported
using iSCSI::
Duplicate3PARHost: 3PAR Host already exists: Host wwn 50014380242B9750 \

2
doc/admin-guide-cloud/source/ts_cinder_config.rst
View File

@ -107,7 +107,7 @@ these suggested solutions.
The OpenStack Block Storage uses ``tgtd`` as the default iSCSI helper
and implements persistent targets. This means that in the case of a
``tgt`` restart or even a node reboot your existing volumes on that node
will be restored automatically with their original IQN.
will be restored automatically with their original :term:`IQN`.
In order to make this possible the iSCSI target information needs to
be stored in a file on creation that can be queried in case of

4
doc/admin-guide-cloud/source/ts_non_existent_host.rst
View File

@ -7,8 +7,8 @@ Problem
This error could be caused by a volume being exported outside of
OpenStack using a host name different from the system name that
OpenStack expects. This error could be displayed with the IQN if the
host was exported using iSCSI.
OpenStack expects. This error could be displayed with the :term:`IQN`
if the host was exported using iSCSI.
::

17
doc/glossary/glossary-terms.xml
View File

@ -4771,6 +4771,23 @@
</glossdef>
</glossentry>
<glossentry>
<glossterm>IQN</glossterm>
<indexterm class="singular">
<primary>iSCSI Qualified Name (IQN)</primary>
</indexterm>
<glossdef>
<para>iSCSI Qualified Name (IQN) is the format most commonly used
for iSCSI names, which uniquely identify nodes in an iSCSI network.
All IQNs follow the pattern iqn.yyyy-mm.domain:identifier, where
'yyyy-mm' is the year and month in which the domain was registered,
'domain' is the reversed domain name of the issuing organization, and
'identifier' is an optional string which makes each IQN under the same
domain unique. For example, 'iqn.2015-10.org.openstack.408ae959bce1'.</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>iSCSI</glossterm>
<indexterm class="singular">