cinder/doc/source/configuration
raghavendrat 25a9b4027a 3PAR: Add config for NSP single path attach
This fix aims to resolve below mentioned bugs:
https://bugs.launchpad.net/os-brick/+bug/1812665
https://bugs.launchpad.net/cinder/+bug/1809249
https://bugs.launchpad.net/cinder/+bug/1734917

Given a system connected to HPE 3PAR via FC and multipath is disabled.
When user tries to create bootable volume, it fails intermittently
with following error:

    Fibre Channel volume device not found

This happens when a zone is created using second or later target nsp
from 3PAR backend. In this case, HPE 3PAR client code picks up first
target nsp to form initiator target map.

To avoid above mentioned failure, user can specify target nsp in 3PAR
backend section of cinder.conf as follows:

    hpe3par_target_nsp = <n:s:p>

This target information is read from cinder.conf and respective
wwn information is fetched. Later initiator target map is created
using wwn information and bootable volume is created successfully.

Change-Id: I2da5d4a0334f07967af5ff7aaa39a0ecc4b12204
Closes-bug: #1809249
Closes-bug: #1812665
Closes-bug: #1734917
(cherry picked from commit 9e122f1166)
2019-08-30 14:12:27 +00:00
..
block-storage 3PAR: Add config for NSP single path attach 2019-08-30 14:12:27 +00:00
figures Move config-reference to configuration 2017-07-18 13:10:25 -05:00
tables Merge "Use new target_* options in documentation" 2019-03-01 21:56:56 +00:00
README.rst [Docs] Add documentation contribution docs 2017-08-10 15:52:46 -05:00
index.rst Add policy configuration howto 2018-12-20 15:31:17 -05:00

README.rst

Cinder Configuration Documentation (source/configuration)

Introduction:

This directory is intended to hold any documentation that relates to how to configure Cinder. It is intended that some of this content be automatically generated in the future. At the moment, however, it is not. Changes to configuration options for Cinder or its drivers needs to be put under this directory.

The full spec for organization of documentation may be seen in the OS Manuals Migration Spec <https://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html>.