Merge "[config-ref] Convert ibm-storwize-svc-driver to RST"
This commit is contained in:
Jenkins
@@ -1,3 +1,524 @@
|
|||||||
=========================================
|
=========================================
|
||||||
IBM Storwize family and SVC volume driver
|
IBM Storwize family and SVC volume driver
|
||||||
=========================================
|
=========================================
|
||||||
|
|
||||||
|
The volume management driver for Storwize family and SAN Volume
|
||||||
|
Controller (SVC) provides OpenStack Compute instances with access to IBM
|
||||||
|
Storwize family or SVC storage systems.
|
||||||
|
|
||||||
|
Configure the Storwize family and SVC system
|
||||||
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
|
Network configuration
|
||||||
|
---------------------
|
||||||
|
|
||||||
|
The Storwize family or SVC system must be configured for iSCSI, Fibre
|
||||||
|
Channel, or both.
|
||||||
|
|
||||||
|
If using iSCSI, each Storwize family or SVC node should have at least
|
||||||
|
one iSCSI IP address. The IBM Storwize/SVC driver uses an iSCSI IP
|
||||||
|
address associated with the volume's preferred node (if available) to
|
||||||
|
attach the volume to the instance, otherwise it uses the first available
|
||||||
|
iSCSI IP address of the system. The driver obtains the iSCSI IP address
|
||||||
|
directly from the storage system; you do not need to provide these iSCSI
|
||||||
|
IP addresses directly to the driver.
|
||||||
|
|
||||||
|
.. note::
|
||||||
|
|
||||||
|
If using iSCSI, ensure that the compute nodes have iSCSI network
|
||||||
|
access to the Storwize family or SVC system.
|
||||||
|
|
||||||
|
.. note::
|
||||||
|
|
||||||
|
OpenStack Nova's Grizzly version supports iSCSI multipath. Once this
|
||||||
|
is configured on the Nova host (outside the scope of this
|
||||||
|
documentation), multipath is enabled.
|
||||||
|
|
||||||
|
If using Fibre Channel (FC), each Storwize family or SVC node should
|
||||||
|
have at least one WWPN port configured. If the
|
||||||
|
``storwize_svc_multipath_enabled`` flag is set to True in the Cinder
|
||||||
|
configuration file, the driver uses all available WWPNs to attach the
|
||||||
|
volume to the instance. If the flag is not
|
||||||
|
set, the driver uses the WWPN associated with the volume's preferred
|
||||||
|
node (if available), otherwise it uses the first available WWPN of the
|
||||||
|
system. The driver obtains the WWPNs directly from the storage system;
|
||||||
|
you do not need to provide these WWPNs directly to the driver.
|
||||||
|
|
||||||
|
.. note::
|
||||||
|
|
||||||
|
If using FC, ensure that the compute nodes have FC connectivity to
|
||||||
|
the Storwize family or SVC system.
|
||||||
|
|
||||||
|
iSCSI CHAP authentication
|
||||||
|
-------------------------
|
||||||
|
|
||||||
|
If using iSCSI for data access and the
|
||||||
|
``storwize_svc_iscsi_chap_enabled`` is set to ``True``, the driver will
|
||||||
|
associate randomly-generated CHAP secrets with all hosts on the Storwize
|
||||||
|
family system. OpenStack compute nodes use these secrets when creating
|
||||||
|
iSCSI connections.
|
||||||
|
|
||||||
|
.. note::
|
||||||
|
|
||||||
|
CHAP secrets are added to existing hosts as well as newly-created
|
||||||
|
ones. If the CHAP option is enabled, hosts will not be able to
|
||||||
|
access the storage without the generated secrets.
|
||||||
|
|
||||||
|
.. note::
|
||||||
|
|
||||||
|
Not all OpenStack Compute drivers support CHAP authentication.
|
||||||
|
Please check compatibility before using.
|
||||||
|
|
||||||
|
.. note::
|
||||||
|
|
||||||
|
CHAP secrets are passed from OpenStack Block Storage to Compute in
|
||||||
|
clear text. This communication should be secured to ensure that CHAP
|
||||||
|
secrets are not discovered.
|
||||||
|
|
||||||
|
Configure storage pools
|
||||||
|
-----------------------
|
||||||
|
|
||||||
|
Each instance of the IBM Storwize/SVC driver allocates all volumes in a
|
||||||
|
single pool. The pool should be created in advance and be provided to
|
||||||
|
the driver using the ``storwize_svc_volpool_name`` configuration flag.
|
||||||
|
For more details, see the configuration flags and how to provide the flags to
|
||||||
|
the driver here: :ref:`config_flags`.
|
||||||
|
|
||||||
|
Configure user authentication for the driver
|
||||||
|
--------------------------------------------
|
||||||
|
|
||||||
|
The driver requires access to the Storwize family or SVC system
|
||||||
|
management interface. The driver communicates with the management using
|
||||||
|
SSH. The driver should be provided with the Storwize family or SVC
|
||||||
|
management IP using the ``san_ip`` flag, and the management port should
|
||||||
|
be provided by the ``san_ssh_port`` flag. By default, the port value is
|
||||||
|
configured to be port 22 (SSH).
|
||||||
|
|
||||||
|
.. note::
|
||||||
|
|
||||||
|
Make sure the compute node running the cinder-volume management
|
||||||
|
driver has SSH network access to the storage system.
|
||||||
|
|
||||||
|
To allow the driver to communicate with the Storwize family or SVC
|
||||||
|
system, you must provide the driver with a user on the storage system.
|
||||||
|
The driver has two authentication methods: password-based authentication
|
||||||
|
and SSH key pair authentication. The user should have an Administrator
|
||||||
|
role. It is suggested to create a new user for the management driver.
|
||||||
|
Please consult with your storage and security administrator regarding
|
||||||
|
the preferred authentication method and how passwords or SSH keys should
|
||||||
|
be stored in a secure manner.
|
||||||
|
|
||||||
|
.. note::
|
||||||
|
|
||||||
|
When creating a new user on the Storwize or SVC system, make sure
|
||||||
|
the user belongs to the Administrator group or to another group that
|
||||||
|
has an Administrator role.
|
||||||
|
|
||||||
|
If using password authentication, assign a password to the user on the
|
||||||
|
Storwize or SVC system. The driver configuration flags for the user and
|
||||||
|
password are ``san_login`` and ``san_password``, respectively.
|
||||||
|
|
||||||
|
If you are using the SSH key pair authentication, create SSH private and
|
||||||
|
public keys using the instructions below or by any other method.
|
||||||
|
Associate the public key with the user by uploading the public key:
|
||||||
|
select the "choose file" option in the Storwize family or SVC management
|
||||||
|
GUI under "SSH public key". Alternatively, you may associate the SSH
|
||||||
|
public key using the command line interface; details can be found in the
|
||||||
|
Storwize and SVC documentation. The private key should be provided to
|
||||||
|
the driver using the ``san_private_key`` configuration flag.
|
||||||
|
|
||||||
|
Create a SSH key pair with OpenSSH
|
||||||
|
----------------------------------
|
||||||
|
|
||||||
|
You can create an SSH key pair using OpenSSH, by running:
|
||||||
|
|
||||||
|
.. code-block:: console
|
||||||
|
|
||||||
|
$ ssh-keygen -t rsa
|
||||||
|
|
||||||
|
The command prompts for a file to save the key pair. For example, if you
|
||||||
|
select ``key`` as the filename, two files are created: ``key`` and
|
||||||
|
``key.pub``. The ``key`` file holds the private SSH key and ``key.pub``
|
||||||
|
holds the public SSH key.
|
||||||
|
|
||||||
|
The command also prompts for a pass phrase, which should be empty.
|
||||||
|
|
||||||
|
The private key file should be provided to the driver using the
|
||||||
|
``san_private_key`` configuration flag. The public key should be
|
||||||
|
uploaded to the Storwize family or SVC system using the storage
|
||||||
|
management GUI or command line interface.
|
||||||
|
|
||||||
|
.. note::
|
||||||
|
|
||||||
|
Ensure that Cinder has read permissions on the private key file.
|
||||||
|
|
||||||
|
Configure the Storwize family and SVC driver
|
||||||
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
|
Enable the Storwize family and SVC driver
|
||||||
|
-----------------------------------------
|
||||||
|
|
||||||
|
Set the volume driver to the Storwize family and SVC driver by setting
|
||||||
|
the ``volume_driver`` option in ``cinder.conf`` as follows:
|
||||||
|
|
||||||
|
.. code-block:: ini
|
||||||
|
|
||||||
|
volume_driver = cinder.volume.drivers.ibm.storwize_svc.StorwizeSVCDriver
|
||||||
|
|
||||||
|
.. _config_flags:
|
||||||
|
|
||||||
|
Storwize family and SVC driver options in cinder.conf
|
||||||
|
-----------------------------------------------------
|
||||||
|
|
||||||
|
The following options specify default values for all volumes. Some can
|
||||||
|
be over-ridden using volume types, which are described below.
|
||||||
|
|
||||||
|
.. list-table:: List of configuration flags for Storwize storage and SVC driver
|
||||||
|
:header-rows: 1
|
||||||
|
|
||||||
|
* - Flag name
|
||||||
|
- Type
|
||||||
|
- Default
|
||||||
|
- Description
|
||||||
|
* - ``san_ip``
|
||||||
|
- Required
|
||||||
|
-
|
||||||
|
- Management IP or host name
|
||||||
|
* - ``san_ssh_port``
|
||||||
|
- Optional
|
||||||
|
- 22
|
||||||
|
- Management port
|
||||||
|
* - ``san_login``
|
||||||
|
- Required
|
||||||
|
-
|
||||||
|
- Management login username
|
||||||
|
* - ``san_password``
|
||||||
|
- Required [1]_
|
||||||
|
-
|
||||||
|
- Management login password
|
||||||
|
* - ``san_private_key``
|
||||||
|
- Required
|
||||||
|
-
|
||||||
|
- Management login SSH private key
|
||||||
|
* - ``storwize_svc_volpool_name``
|
||||||
|
- Required
|
||||||
|
-
|
||||||
|
- Default pool name for volumes
|
||||||
|
* - ``storwize_svc_vol_rsize``
|
||||||
|
- Optional
|
||||||
|
- 2
|
||||||
|
- Initial physical allocation (percentage) [2]_
|
||||||
|
* - ``storwize_svc_vol_warning``
|
||||||
|
- Optional
|
||||||
|
- 0 (disabled)
|
||||||
|
- Space allocation warning threshold (percentage)
|
||||||
|
* - ``storwize_svc_vol_autoexpand``
|
||||||
|
- Optional
|
||||||
|
- True
|
||||||
|
- Enable or disable volume auto expand [3]_
|
||||||
|
* - ``storwize_svc_vol_grainsize``
|
||||||
|
- Optional
|
||||||
|
- 256
|
||||||
|
- Volume grain size in KB
|
||||||
|
* - ``storwize_svc_vol_compression``
|
||||||
|
- Optional
|
||||||
|
- False
|
||||||
|
- Enable or disable Real-time Compression [4]_
|
||||||
|
* - ``storwize_svc_vol_easytier``
|
||||||
|
- Optional
|
||||||
|
- True
|
||||||
|
- Enable or disable Easy Tier [5]_
|
||||||
|
* - ``storwize_svc_vol_iogrp``
|
||||||
|
- Optional
|
||||||
|
- 0
|
||||||
|
- The I/O group in which to allocate vdisks
|
||||||
|
* - ``storwize_svc_flashcopy_timeout``
|
||||||
|
- Optional
|
||||||
|
- 120
|
||||||
|
- FlashCopy timeout threshold [6]_ (seconds)
|
||||||
|
* - ``storwize_svc_connection_protocol``
|
||||||
|
- Optional
|
||||||
|
- iSCSI
|
||||||
|
- Connection protocol to use (currently supports 'iSCSI' or 'FC')
|
||||||
|
* - ``storwize_svc_iscsi_chap_enabled``
|
||||||
|
- Optional
|
||||||
|
- True
|
||||||
|
- Configure CHAP authentication for iSCSI connections
|
||||||
|
* - ``storwize_svc_multipath_enabled``
|
||||||
|
- Optional
|
||||||
|
- False
|
||||||
|
- Enable multipath for FC connections [7]_
|
||||||
|
* - ``storwize_svc_multihost_enabled``
|
||||||
|
- Optional
|
||||||
|
- True
|
||||||
|
- Enable mapping vdisks to multiple hosts [8]_
|
||||||
|
* - ``storwize_svc_vol_nofmtdisk``
|
||||||
|
- Optional
|
||||||
|
- False
|
||||||
|
- Enable or disable fast format [9]_
|
||||||
|
|
||||||
|
.. [1]
|
||||||
|
The authentication requires either a password (``san_password``) or
|
||||||
|
SSH private key (``san_private_key``). One must be specified. If both
|
||||||
|
are specified, the driver uses only the SSH private key.
|
||||||
|
|
||||||
|
.. [2]
|
||||||
|
The driver creates thin-provisioned volumes by default. The
|
||||||
|
``storwize_svc_vol_rsize`` flag defines the initial physical
|
||||||
|
allocation percentage for thin-provisioned volumes, or if set to
|
||||||
|
``-1``, the driver creates full allocated volumes. More details about
|
||||||
|
the available options are available in the Storwize family and SVC
|
||||||
|
documentation.
|
||||||
|
|
||||||
|
.. [3]
|
||||||
|
Defines whether thin-provisioned volumes can be auto expanded by the
|
||||||
|
storage system, a value of ``True`` means that auto expansion is
|
||||||
|
enabled, a value of ``False`` disables auto expansion. Details about
|
||||||
|
this option can be found in the ``–autoexpand`` flag of the Storwize
|
||||||
|
family and SVC command line interface ``mkvdisk`` command.
|
||||||
|
|
||||||
|
.. [4]
|
||||||
|
Defines whether Real-time Compression is used for the volumes created
|
||||||
|
with OpenStack. Details on Real-time Compression can be found in the
|
||||||
|
Storwize family and SVC documentation. The Storwize or SVC system
|
||||||
|
must have compression enabled for this feature to work.
|
||||||
|
|
||||||
|
.. [5]
|
||||||
|
Defines whether Easy Tier is used for the volumes created with
|
||||||
|
OpenStack. Details on EasyTier can be found in the Storwize family
|
||||||
|
and SVC documentation. The Storwize or SVC system must have Easy Tier
|
||||||
|
enabled for this feature to work.
|
||||||
|
|
||||||
|
.. [6]
|
||||||
|
The driver wait timeout threshold when creating an OpenStack
|
||||||
|
snapshot. This is actually the maximum amount of time that the driver
|
||||||
|
waits for the Storwize family or SVC system to prepare a new
|
||||||
|
FlashCopy mapping. The driver accepts a maximum wait time of 600
|
||||||
|
seconds (10 minutes).
|
||||||
|
|
||||||
|
.. [7]
|
||||||
|
Multipath for iSCSI connections requires no storage-side
|
||||||
|
configuration and is enabled if the compute host has multipath
|
||||||
|
configured.
|
||||||
|
|
||||||
|
.. [8]
|
||||||
|
This option allows the driver to map a vdisk to more than one host at
|
||||||
|
a time. This scenario occurs during migration of a virtual machine
|
||||||
|
with an attached volume; the volume is simultaneously mapped to both
|
||||||
|
the source and destination compute hosts. If your deployment does not
|
||||||
|
require attaching vdisks to multiple hosts, setting this flag to
|
||||||
|
``False`` will provide added safety.
|
||||||
|
|
||||||
|
.. [9]
|
||||||
|
Defines whether or not the fast formatting of thick-provisioned
|
||||||
|
volumes is disabled at creation. The default value is ``False`` and a
|
||||||
|
value of ``True`` means that fast format is disabled. Details about
|
||||||
|
this option can be found in the ``–nofmtdisk`` flag of the Storwize
|
||||||
|
family and SVC command line interface ``mkvdisk`` command.
|
||||||
|
|
||||||
|
.. include:: ../../tables/cinder-storwize.rst
|
||||||
|
|
||||||
|
Placement with volume types
|
||||||
|
---------------------------
|
||||||
|
|
||||||
|
The IBM Storwize/SVC driver exposes capabilities that can be added to
|
||||||
|
the ``extra specs`` of volume types, and used by the filter
|
||||||
|
scheduler to determine placement of new volumes. Make sure to prefix
|
||||||
|
these keys with ``capabilities:`` to indicate that the scheduler should
|
||||||
|
use them. The following ``extra specs`` are supported:
|
||||||
|
|
||||||
|
- ``capabilities:volume_back-end_name`` - Specify a specific back-end
|
||||||
|
where the volume should be created. The back-end name is a
|
||||||
|
concatenation of the name of the IBM Storwize/SVC storage system as
|
||||||
|
shown in ``lssystem``, an underscore, and the name of the pool (mdisk
|
||||||
|
group). For example:
|
||||||
|
|
||||||
|
.. code-block:: ini
|
||||||
|
|
||||||
|
capabilities:volume_back-end_name=myV7000_openstackpool
|
||||||
|
|
||||||
|
- ``capabilities:compression_support`` - Specify a back-end according to
|
||||||
|
compression support. A value of ``True`` should be used to request a
|
||||||
|
back-end that supports compression, and a value of ``False`` will
|
||||||
|
request a back-end that does not support compression. If you do not
|
||||||
|
have constraints on compression support, do not set this key. Note
|
||||||
|
that specifying ``True`` does not enable compression; it only
|
||||||
|
requests that the volume be placed on a back-end that supports
|
||||||
|
compression. Example syntax:
|
||||||
|
|
||||||
|
.. code-block:: ini
|
||||||
|
|
||||||
|
capabilities:compression_support='<is> True'
|
||||||
|
|
||||||
|
- ``capabilities:easytier_support`` - Similar semantics as the
|
||||||
|
``compression_support`` key, but for specifying according to support
|
||||||
|
of the Easy Tier feature. Example syntax:
|
||||||
|
|
||||||
|
.. code-block:: ini
|
||||||
|
|
||||||
|
capabilities:easytier_support='<is> True'
|
||||||
|
|
||||||
|
- ``capabilities:storage_protocol`` - Specifies the connection protocol
|
||||||
|
used to attach volumes of this type to instances. Legal values are
|
||||||
|
``iSCSI`` and ``FC``. This ``extra specs`` value is used for both placement
|
||||||
|
and setting the protocol used for this volume. In the example syntax,
|
||||||
|
note <in> is used as opposed to <is> used in the previous examples.
|
||||||
|
|
||||||
|
.. code-block:: ini
|
||||||
|
|
||||||
|
capabilities:storage_protocol='<in> FC'
|
||||||
|
|
||||||
|
Configure per-volume creation options
|
||||||
|
-------------------------------------
|
||||||
|
|
||||||
|
Volume types can also be used to pass options to the IBM Storwize/SVC
|
||||||
|
driver, which over-ride the default values set in the configuration
|
||||||
|
file. Contrary to the previous examples where the "capabilities" scope
|
||||||
|
was used to pass parameters to the Cinder scheduler, options can be
|
||||||
|
passed to the IBM Storwize/SVC driver with the "drivers" scope.
|
||||||
|
|
||||||
|
The following ``extra specs`` keys are supported by the IBM Storwize/SVC
|
||||||
|
driver:
|
||||||
|
|
||||||
|
- rsize
|
||||||
|
|
||||||
|
- warning
|
||||||
|
|
||||||
|
- autoexpand
|
||||||
|
|
||||||
|
- grainsize
|
||||||
|
|
||||||
|
- compression
|
||||||
|
|
||||||
|
- easytier
|
||||||
|
|
||||||
|
- multipath
|
||||||
|
|
||||||
|
- iogrp
|
||||||
|
|
||||||
|
These keys have the same semantics as their counterparts in the
|
||||||
|
configuration file. They are set similarly; for example, ``rsize=2`` or
|
||||||
|
``compression=False``.
|
||||||
|
|
||||||
|
Example: Volume types
|
||||||
|
---------------------
|
||||||
|
|
||||||
|
In the following example, we create a volume type to specify a
|
||||||
|
controller that supports iSCSI and compression, to use iSCSI when
|
||||||
|
attaching the volume, and to enable compression:
|
||||||
|
|
||||||
|
.. code-block:: console
|
||||||
|
|
||||||
|
$ cinder type-create compressed
|
||||||
|
$ cinder type-key compressed set capabilities:storage_protocol='<in> iSCSI' capabilities:compression_support='<is> True' drivers:compression=True
|
||||||
|
|
||||||
|
We can then create a 50GB volume using this type:
|
||||||
|
|
||||||
|
.. code-block:: console
|
||||||
|
|
||||||
|
$ cinder create --display-name "compressed volume" --volume-type compressed 50
|
||||||
|
|
||||||
|
Volume types can be used, for example, to provide users with different
|
||||||
|
|
||||||
|
- performance levels (such as, allocating entirely on an HDD tier,
|
||||||
|
using Easy Tier for an HDD-SDD mix, or allocating entirely on an SSD
|
||||||
|
tier)
|
||||||
|
|
||||||
|
- resiliency levels (such as, allocating volumes in pools with
|
||||||
|
different RAID levels)
|
||||||
|
|
||||||
|
- features (such as, enabling/disabling Real-time Compression)
|
||||||
|
|
||||||
|
QOS
|
||||||
|
---
|
||||||
|
|
||||||
|
The Storwize driver provides QOS support for storage volumes by
|
||||||
|
controlling the I/O amount. QOS is enabled by editing the
|
||||||
|
``etc/cinder/cinder.conf`` file and setting the
|
||||||
|
``storwize_svc_allow_tenant_qos`` to True.
|
||||||
|
|
||||||
|
There are three ways to set the Storwize ``IOThrotting`` parameter for
|
||||||
|
storage volumes:
|
||||||
|
|
||||||
|
- Add the ``qos:IOThrottling`` key into a QOS specification and
|
||||||
|
associate it with a volume type.
|
||||||
|
|
||||||
|
- Add the ``qos:IOThrottling`` key into an extra specification with a
|
||||||
|
volume type.
|
||||||
|
|
||||||
|
- Add the ``qos:IOThrottling`` key to the storage volume metadata.
|
||||||
|
|
||||||
|
.. note::
|
||||||
|
|
||||||
|
If you are changing a volume type with QOS to a new volume type
|
||||||
|
without QOS, the QOS configuration settings will be removed.
|
||||||
|
|
||||||
|
Operational notes for the Storwize family and SVC driver
|
||||||
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
|
Migrate volumes
|
||||||
|
---------------
|
||||||
|
|
||||||
|
In the context of OpenStack Block Storage's volume migration feature,
|
||||||
|
the IBM Storwize/SVC driver enables the storage's virtualization
|
||||||
|
technology. When migrating a volume from one pool to another, the volume
|
||||||
|
will appear in the destination pool almost immediately, while the
|
||||||
|
storage moves the data in the background.
|
||||||
|
|
||||||
|
.. note::
|
||||||
|
|
||||||
|
To enable this feature, both pools involved in a given volume
|
||||||
|
migration must have the same values for ``extent_size``. If the
|
||||||
|
pools have different values for ``extent_size``, the data will still
|
||||||
|
be moved directly between the pools (not host-side copy), but the
|
||||||
|
operation will be synchronous.
|
||||||
|
|
||||||
|
Extend volumes
|
||||||
|
--------------
|
||||||
|
|
||||||
|
The IBM Storwize/SVC driver allows for extending a volume's size, but
|
||||||
|
only for volumes without snapshots.
|
||||||
|
|
||||||
|
Snapshots and clones
|
||||||
|
--------------------
|
||||||
|
|
||||||
|
Snapshots are implemented using FlashCopy with no background copy
|
||||||
|
(space-efficient). Volume clones (volumes created from existing volumes)
|
||||||
|
are implemented with FlashCopy, but with background copy enabled. This
|
||||||
|
means that volume clones are independent, full copies. While this
|
||||||
|
background copy is taking place, attempting to delete or extend the
|
||||||
|
source volume will result in that operation waiting for the copy to
|
||||||
|
complete.
|
||||||
|
|
||||||
|
Volume retype
|
||||||
|
-------------
|
||||||
|
|
||||||
|
The IBM Storwize/SVC driver enables you to modify volume types. When you
|
||||||
|
modify volume types, you can also change these extra specs properties:
|
||||||
|
|
||||||
|
- rsize
|
||||||
|
|
||||||
|
- warning
|
||||||
|
|
||||||
|
- autoexpand
|
||||||
|
|
||||||
|
- grainsize
|
||||||
|
|
||||||
|
- compression
|
||||||
|
|
||||||
|
- easytier
|
||||||
|
|
||||||
|
- iogrp
|
||||||
|
|
||||||
|
- nofmtdisk
|
||||||
|
|
||||||
|
.. note::
|
||||||
|
|
||||||
|
When you change the ``rsize``, ``grainsize`` or ``compression``
|
||||||
|
properties, volume copies are asynchronously synchronized on the
|
||||||
|
array.
|
||||||
|
|
||||||
|
.. note::
|
||||||
|
|
||||||
|
To change the ``iogrp`` property, IBM Storwize/SVC firmware version
|
||||||
|
6.4.0 or later is required.
|
||||||
|
|||||||
Reference in New Issue
Block a user