When the CLI command execution encounters an error, the storage
returns an error code.
However, only some error codes could be parsed, resulting the
inability to view specific error information in the log.
To fix this issue, the parsing of error codes has been added when
the CLI encounters an error, allowing the error information to be
viewed in the log.
In addition, this patch also adds support for SSH keys,
allowing connections to the storage using SSH key.
Closes-Bug: #2048850
Change-Id: I204f3889e3401b142dd7c9a6e11585639585abfc
Currently Admin user will create the qos policy in the lightbits side
and add the policy UUID to the volume type.
Creation of new volume using the volume type will be created with the
qos policy.
Change-Id: Id0332c5c6a70d63c87bf63cdf4c8bd71e672a148
The cinder-rally-task job is failing with:
Validation error: There is no 'cinderv3' service in your environment
Change-Id: Ideae7b290c639ae1a79d29eeaf156de38777ae8d
Stop depending on modules `storpool` and `storpool.spopenstack` for
access to the StorPool API and reading the StorPool configuration from
files. Use the new new in-tree implementation introduced in `os-brick`.
Change-Id: Ieb6be04133e1639b3fa6e3a322604b366e909d81
In get_volume_stats response, below 3 values are returned,
along with some other values.
total_capacity, provisioned_capacity and free_capacity.
All these 3 values were calculated independently;
and in some cases, the sum of provisioned_capacity (PC) and
free_capacity (FC) was not equal to total_capacity (TC).
Ideally PC + FC should be equal to TC.
After checking wsapi guide and executing those calls we found that,
total_capacity and provisioned_capacity are calculated correctly.
Thus, free_capacity is now calculated as below:
free_capacity = total_capacity - provisioned_capacity
Change-Id: I89e36219f9e3adfaf626f25cd06e7a46d3fe813c
The retype operation from thin volume to deco volume
(dedup + compression) fails.
RESP BODY: {"code":46, "desc":"invalid input: bad enum value"}
This patch fixes the retype operation by using updated
functions and parameters.
Closes-Bug: #2080927
Change-Id: Id2a515ad64c62552dc211078080cfdef6dc87540
Add the "maximum" marker for 2023.2 at microversion 3.70, which was
introduced by change I459f06504e90.
Add the "maximum" marker for 2024.1 and 2024.2 at microversion 3.71,
which was introduced by change I4aaa5da1ad67.
Change-Id: If889a3c2cb5eefc8e1ec7fb0963684fb30b8795b
After logging in to WSAPI with getWsApiVersion(),
ensure you call logout() to prevent
exhausting the server's connection limit.
This patch corrects a regression introduced
by I30f105ee619386f52bc907f5115c08e0fafb9e42
Change-Id: Iec30d048b4b18cb2013005fb36484b2808030690
Earlier the call to getWsApiVersion() worked without login.
Now with new wsapi of 2024, login is required.
This patch makes call to client_login() before getWsApiVersion().
Change-Id: I334d91c978a8d0d1cff1edeb6c8cdd5aedf4acfe
Previously, the check for multipath used to happen while fetching
connector information. The downside of this was we didn't know
what kind of connection (iSCSI, FC, NVMe) will be created and
it was not possible to handle the multipath checks for different
connectors.
With change[1], the check was moved to the connect_volume method
but that led to another problem that the connection information
returned from cinder didn't contain the ``enforce_multipath``
parameter.
The purpose of this patch is to include the ``enforce_multipath``
parameter in the connection information based on the value fetched
from the connector.
[1] https://review.opendev.org/c/openstack/os-brick/+/933250
Partial-Bug: #2085013
Change-Id: I4ea618a44b37cce5dd0b131ffac55bce51d08c0a
During a NFS volume snapshot of an attached volume, a QCOW2 snapshot is
created and is made the active volume for the instance. The associated
volume attachment is however not updated, resulting in an unbootable
instance after a stop/start.
This adds an update to the volume format and attachment connection_info
format during the snapshot.
Closes-Bug: #1989514
Change-Id: I3c638dab2f0b5a2128eaeeea533450d7cdfa1577
This patch added a global lock for detach/attach operation
to prevent the race conditions caused by multiple detach
requests.
It also improved trace logs for PowerMax RESTAPI requests.
Closes-Bug: #2089656
Change-Id: I7de66d96cec4bc3a4f6f1e9423dc3e9b47e9df95
olso.policy 4.5.0[1] changed the config options policy_file
default value to 'policy.yaml', which means it is changed
for all the OpenStack services and they do not need to
override the default anymore.
NOTE: There is no change in behaviour here, oslo.policy provides
the same configuration that services have overridden till now.
[1] https://review.opendev.org/c/openstack/releases/+/934012
[2] https://review.opendev.org/c/openstack/requirements/+/934295
Change-Id: I3e3d0aaaece99120d276ff44dcdb3151855c8fe5
Update the 2023.1 (Antelope) release notes configuration to build
from the 2023.1-eom tag, which is the last point at which the cinder
project team had responsibility for the branch.
Change-Id: I6677eb3f6f5abf181426e968d29036c03da9c5c4
The httlib2 library was added to be used by google backup driver[1],
but it was then replaced by google-auth-httplib2 .
[1] cf5653c17c1dce2a85ced8b6969a0503d5cca416
[2] 79d7a4e8da6f1118b5c235928876cf78085f4332
Change-Id: I1635ee8e5bd3b257ed64070a590a3820a2682667