The value reported to the scheduler by the iSCSI driver is
hardcoded and is different from the netapp_storage_protocol config
option (which is used to select which NetApp driver to load)
This patch adds a note to avoid the above confusion.
Change-Id: I3f63e86eb2b2eb27ea321c11df10d02432144655
Closes-Bug: #1775988
Although Inspur AS13000 cinder driver has been merged,
some small issues have been left there, and this patch
is a follow-up for https://review.openstack.org/#/c/562977.
Change-Id: I3544c4ab3bf78feea36fed63a6d799ed4bb43d5a
Closes-Bug: #1810709
We are moving LINBIT DRBDManage driver to maintenance
mode and will be removed from the tree in T Release.
Change-Id: Ib8c4079429d1fea00be4e3993f48185da733d2c0
Driver was incorrectly moved to a different place in the TOC since it
still had the non-Dell naming. This moves it back and renames it to
hopefully prevent this kind of mistake from happening again.
Change-Id: I797c7cf86dcb2598c04a3697093c458e64d84ae1
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
This patch introduces Hedvig cinder volume driver along with unit tests
implements: blueprint hedvig-cinder
Change-Id: Ib701edb733567831ee80a317d0e3b3945a312760
Signed-off-by: Dhinesh Balasubramaniam <dhinesh@hedviginc.com>
With this patch it'll become possible to limit max performance of volume
even when qos is set per_gb. As a result operator will be able to set
min and max options, with per gb increment, until the max value.
Change-Id: I3c6c9e1c50100cfa56dcadf6445729484cdd616d
Features that Inspur AS13000 Driver support:
Create, list, delete, attach (map), and detach (unmap) volumes
Create, list, and delete volume snapshots
Copy an image to a volume
Copy a volume to an image
Clone a volume
Extend a volume
Create a volume from a snapshot
ThirdPartySystems: INSPUR CI
Change-Id: Ib18ffb38f87747805a3aaf0c3837d5b8bb71b101
Implements: Blueprint inspur-as13000-driver
The RST file introducing the sample policy file in the docs directory
has gotten out of sync with etc/cinder/README-policy.generate.md
Change-Id: Ic43c631bb7af0b4d888e539d4ca50e379f693b3c
Partial-bug: #1805550
query_volume_filters was deprecated in Pike with
Icee6c22621489f93614f4adf071329d8d2115637 and it should be safe to
remove it now.
Change-Id: Icd311db7f88c3c274d9a362eb96519e46c7e4d17
During the rocky cycle, there was a docs-spec approved [0] with the goal
of having a recommended consistent documentation landing page for all
projects.
This updates our docs landing page to follow the structure described in
that recommendation.
[0] http://specs.openstack.org/openstack/docs-specs/specs/rocky/front-page-template.html
Change-Id: I0f31c59e6b39ab8d9c0009f72967c793dadbed64
Addresses some issues with this command:
1) When used without the --max-count option, the summary table will
always show zero migrations run, because it only accounts for the
last batch, and the loop only exits when the last batch does no work.
2) "remaining" counts cannot be accurate, given the way migrations are
implemented, because the "found" count refers to the number of rows
that exist in the database, not the number that still need the
migration applied.
3) In the case where no migrations are successful, but some raise
exceptions, the command was exiting with status zero, which usually
indicates "success". This can cause issues that cause migration
failures to go unnoticed, especially when automated.
4) When exceptions do occur, a minimally useful message is output, and
no detail about the exception is available to the user. The exception
detail should be logged.
5) Inaccuracies in the documentation - "--max_number" should be
"--max-count", and stale references to the "--ignore_state" option,
which was removed in [1]
The solution for (3) introduces a new exit status, 2. See release note
for details.
These changes are aligned with equivalents [2][3] for the nova-manage
command, except for the calculation of "Total Needed" - nova seems to
interpret the "found" count differently/inconsistently.
[1] https://review.openstack.org/510201
[2] https://review.openstack.org/605828
[3] https://review.openstack.org/608091
Change-Id: I878480eb2359625cde839b073230844acc645cba
Closes-Bug: #1794364
Closes-Bug: #1796192
This adds the cinder-status CLI for performing upgrade checks as part of
the Stein cycle upgrade-checkers goal. It only includes a placeholder
for actual checks. Follow up patches will need to be added for anything
we identify as needing specific checking.
Story: 2003657
Task: 26123
Change-Id: I2e532d313d12e60848b17e869882e52ec456929b
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Sphinx 1.6 deprecated using the application object to perform logging
and it will be removed in the upcoming 2.0 release. This updates our
extensions to use the recommended sphinx.util.logging instead.
Change-Id: I3b44e096c62a081e195ea22bc953d1752d7ff4b7
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
As part of further refactoring work, this pulls out common driver code
into its own file to better organize the code.
Change-Id: Ib5b52b638e27743d86106cc9859f8adeab2aab08
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Since we have a CLI reference and specific doc subtree the
cinder-manage docs should live there. This moves the cinder-manage
page from man/ to cli/ and adds a redirect link.
Change-Id: If99416e8a382d2a6571412742276dccc591d180c
