| 1 |
--- |
| 2 |
features: |
| 3 |
- | |
| 4 |
Fujitsu ETERNUS DX driver: Add fragment capacity information of RAID Group. |
| 5 |
|
| 6 |
ETERNUS DX driver have two types of storage pools: RAID Group and |
| 7 |
ThinProvisioning Pool. Volumes can not be created in RAID Groups for |
| 8 |
the following situations: |
| 9 |
|
| 10 |
* The maximum sequential physical free space is smaller than the volumes to |
| 11 |
be created. |
| 12 |
|
| 13 |
* 128 volumes have already been created in the RAID Group. |
| 14 |
|
| 15 |
For the above reasons, to monitor the maximum sequential physical free |
| 16 |
space and total volumes in the RAID Group, when updating pool information |
| 17 |
using ``Get Volume Stats``, also update parameter ``total_volumes`` |
| 18 |
(volumes already created in the RAID Group) and introduce |
| 19 |
``fragment_capacity_mb`` (maximum sequential physical capacity) to the |
| 20 |
backend pool information if the backend pool is a RAID Group. |
| 21 |
|
| 22 |
Meanwhile, since creating volumes on ThinProvisioning Pool does not |
| 23 |
encounter the above restrictions, parameter ``fragment_capacity_mb`` will |
| 24 |
not be added into the information, and remove the ``total_volumes`` |
| 25 |
parameter from the backend pool information when the type of backend pool |
| 26 |
is ThinProvisioning Pool. |
| 27 |
|
| 28 |
These two parameters can be utilized in future implementations of functions |
| 29 |
related to ``filter_function``. |
| 30 |
|
| 31 |
This patch also enabled the ``multiattach`` in the driver information. |