This commit is part of a series to retire the Packaging Deb
project. Step 2 is to remove all content from the project
repos, replacing it with a README notification where to find
ongoing work, and how to recover the repo if needed at some
future point (as in
https://docs.openstack.org/infra/manual/drivers.html#retiring-a-project).
Change-Id: I129f344c6ee18797445ad33b1e0a2b6a3b430544
There were a number of issues with dosctring issues
in the ibm_storage driver. The issues were causing
Sphinx to produce WARNINGs. This patch correct
those issues.
Change-Id: I0a616ff1f5ce2b26a450f0336be59dacf1f2515f
There were a number of docstring issues in the Hitachi HNAS
driver were causing Sphinx WARNINGs to be produced during
a build. A number of the issues could be resolved by putting
code examples into ".. code:: python" blocks. This patch
fixes those issues.
Change-Id: Ib0e7caca0ab72ff89748eac434396d15c5af47d5
There were a couple of formatting issues in dosctrings causing
the Sphinx to produce WARNINGs when processesing the falconstor
driver. This patch corrects them.
Change-Id: Ie66da44e7e26a25c500ff752ad9b9a7b7b7eefbf
As with other drivers the version history at the top of the
dothill driver was causing Sphinx build WARNINGs to be issued.
This changes puts the version history in a text box for better
readability and to avoid the WARNING.
Change-Id: I387ae425e3a2a1e37264589bb33a0acdcf61ca9a
The docstring for version history at the top of the disco
driver wasn't properly formatted. I put it in a text
code block to make it look better and to remove the
Spinx build WARNING.
Change-Id: Iebdc92fe155d634f61d29d099b3a216f9e173f0f
It's great that the commit[1] brought in volume type filter. But the
commit made `test_scheduler_stats` didn't test anything for some
module call errors. The patch fixes it and lets all the tests in the module
work normally.
[1]d5a3fdabca
Change-Id: Iba22549ce2c78b3aa2af5f23f9e93299ee91c770
This patch adds consistent replication group capabilities for VNX
driver.
Supported operations:
* Create volume and add to replication group
* Add volume to existing replication group
* Enable replication on group
* Disable replication on group
* Fail over replication group back and forth
DocImpact
Implements: blueprint replication-cg-vnx
Change-Id: Iead8d2fd5581a70afb481239199fcbb1246aa27e
There are dosctring errors in the VMAX driver that were causing
the Sphinx build process to generate WARNINGS. This patch
fixes those errors and improves the generated documentation.
Change-Id: I774bd17a61404b0939b1444dac37ec3f7e0da0b0
In the volume manager, the group status is updated before the
group_id is set/unset in the volumes during update_group.
This is wrong because there's a slight chance that the group
could be modified after it becomes 'available' but before
group_id is updated in all the volumes.
This patch fixes it by updating the group status after the
group_id in all volumes are updated.
Closes-Bug: #1704810
Change-Id: I451db1c8c49c4319323e5e0328c89c115d6047d1
There were formatting errors causing sphinx to throw
a WARNING when processing the doc string in driver.py.
This patch updates those formatting errors so they do
not cause a WARNING to be thrown.
Change-Id: Ib40fc7f0927e175079f97583663510627342d767
In some circumstances (such as after a reboot),
especially with thin LVM, the LV may not be activated, so
creating a target from it will fail.
Activate the LV before creating a target.
When using permanent=True for activation, don't supply
the -K/ignoreskipactivation argument. This is rejected
by LVM 2.02.171, and is not a reasonable request, since
it asks to simultaneously unset a flag, and also to ignore
the flag (which should now be unset) during the same
activation operation.
This fixes a failure to clone a volume from another thin
LVM volume in the same pool.
Closes-Bug: #1701545
Change-Id: I925ece8833cc99a95c4cf693804ca3698f8cb114
when lvm_type=thin in cinder.conf, merges a snapshot will
result in other snapshots cannot be merged
Change-Id: Ife3d57b6fe3717af02e7dfa440b1510058bfab40
Closes-Bug: #1702820