Currently our code and contributor documentation doesn't mention the
difference between the two different UUIDs we can have and how drivers
should use them.
This patch tries to provide a brief description about it in multiple
places to reduce the number of bugs that happen around it.
Change-Id: I946ead7547571ccd1b2df55ac1f3d4689d1f8089
Migration from and to RBD devices works for in-use volumes since
Ussuri release. Also as of now a migration of in-use volumes for
non-active VMs is prohibited for any backends.
Related-Bug: #1673090
Related-Bug: #1868996
Closes-Bug: #1969913
Change-Id: Id639c412a6f5ad24ab9c80416c56c1d99b3f104c
cinder/docs directory has a references to the Dell EMC company name.
Rename all Dell EMC references to Dell, except for those references where there are paths.
When the user will read the documentation he will see the new company name.
These changes are due to the company’s rebranding.
Closes-Bug: #1970208
Change-Id: I60e06b1b42974ce7ef4d790f050d706dc1a8a7a3
This doc change aims at creating a checklist of points which would
help reviewers provide useful feedback while reviewing patches.
Change-Id: I1af1ea6b1dab2bc2e5420076ffe7977f11a4aa75
Cinder has multiple drivers reporting the same storage_protocol in their
stats but with different strings:
For example we have the following variants:
- nfs and NFS
- nveof, NVMe-oF, NVMeOF
- iSCSI, iscsi
- FC, fc, fibre_channel
This patch documents the right values (to use existing constants) and
makes the scheduler treat all variants as if they were equal.
This is done by changing the storage_protocol into a list in the
scheduler upon reception of the stats from the volume. Most of the code
in the scheduler is already able to handle this, the only changes
necessary are on the filter and goodness function code, which will now
run the respective functions for all the different protocol alternatives
and select the right one, but only when the function actually uses the
storage_protocol.
The API will now report the preferred protocol name in operations like
"cinder get-pools --detail".
Closes-Bug: #1966103
Change-Id: I07d74078dbb102490dd722029e32c74cec3aa44c
I just spent a while chasing phantom OOM crashes in the backup
agent; I'm hoping this comment will help future users avoid
my problem.
Change-Id: I58ff10d212283b032cabf623021d3955111ff8f0
the compression value in get_volume_stats should be ["True", "False"]
and not dependent on the
configuration: "lightos_default_compression_enabled"
if the flag is false, we can not create volume type with
compression=True. the backend is filtered in the scheduler.
Closes-Bug: #1962221
Signed-off-by: Yuval Brave <yuval@lightbitslabs.com>
Change-Id: I09fe872eca1b112f67bad7297de5893696f83373
Virtualize user guide
This change is in order to include all of the new
products that are coming out for SVC 8.5.0.0
Change-Id: I3d798f0f880b4cccec918807acfcce7f70d7d1d7
These are in the cinder doc tree so of course they're block
storage-related.
Change-Id: Ic1950ff89021a89de397619eef17f8100eb3d847
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Alembic does lots of new things. Provide docs for how to use this. This
doesn't actually work that well at the moment because it appears our
database migrations are not in sync with the models. Those issues will
have to be resolved separately.
Change-Id: I6645ca951114b94ce9ed5a83e5e11d53879a7cd5
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
This shouldn't be in the root of the docs: it's not easily discoverable
and it doesn't belong there. We also modify the header style to better
match the OpenStack style guide [1] and set things up for a future guide
on writing database migrations.
[1] https://docs.openstack.org/doc-contrib-guide/rst-conv/titles.html#cg-titles
Change-Id: I277b9ad8d275aa21d2c3ce478d2a30e4f6e5f0ba
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Use whereto to test that the redirect rules do what we expect. This has
been used in nova-land for years and is helpful as things move around.
Change-Id: I4697c4ce53eb8d67d2f7593085e3eb88f239d1dd
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
We've expanded it to include appropriate non-cinder-core people,
so update the description to reflect that.
Change-Id: If9e6d841ada5938a6c42f9fc75b5e11313dd3bcf
Inclusion of a project_id in API URLs is now optional, and no longer
required. Removing the project_id requirement facilitates supporting
Secure RBAC's notion of system scope, in which an API method is not
associated with a specific project.
The API v3 routing is enhanced to provide duplicate routes for API
methods that traditionally required a project_id in the URL:
- The existing route for which a project_id is in the URL
- A new route for when the URL does not include a project_id
To test both routes and ensure there are no regresssions, the "API
samples" functional tests include a project_id in the URLs, and the
rest of the functional tests do not include the project_id. This is
handled by changing the 'noauth' WSGI middleware to no longer add the
project_id, and adding a new 'noauth_include_project_id' middleware
filter that implements the legacy behavior.
A new microversion V3.67 is introduced, but it only serves to inform
clients whether the project_id is optional or required. When an API
node supports mv 3.67, the project_id is optional in all API requests,
even when the request specifies a earlier microversion. See the spec
Ia44f199243be8f862520d7923007e7182b32f67d for more details on this
behavior.
Note: Much of the groundwork for this is based on manila's patch
I5127e150e8a71e621890f30dba6720b3932cf583.
DocImpact
APIImpact
Implements: blueprint project-id-optional-in-urls
Change-Id: I3729cbe1902ab4dc335451d13ed921ec236fb8fd
- add info about reporting common config options
- update python version testing info for third party CI
- add info about unit test discovery
- add warning about a child driver reporting parent capabilities
that it may not have
Change-Id: Ife214328cdb08ea9a3939b61469fd70b100ed3c7
Move the "how to review" note to the "Getting your patch merged"
section of the new contributor doc, add some info about project
priorities and milestones/freezes, and the importance of having
a +1 from Zuul.
Change-Id: Ia184482946a0afda783004c7902c682141ed9278
