[DOC]Refactor Access Rules APIs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Won't Fix
|
Undecided
|
junboli |
Bug Description
https:/
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/manila" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.
commit 64a73b1419953bc
Author: Goutham Pacha Ravi <email address hidden>
Date: Tue Aug 23 15:33:21 2016 -0400
Refactor Access Rules APIs
- Pull up policy check to beginning of the APIs.
- Avoid making access rules changes when one or
more instances of the share are in an invalid state.
- Add back the per rule share instance access status.
This restoration provides better visibility for which
rules were applied successfully.
- Remove 'updating' and 'updating_multiple' as valid
states for the share instance access rules status.
- Deprecate the access rule state 'new' in favor of
'
status 'out_of_sync' in favor of 'syncing'.
In a new API micro-version:
- Allow access rule changes irrespective of the share's
- Expose new access rule states and share's
access_
Access rules for each share instance now transition
from 'queued_to_apply' to 'applying' to 'active' or 'error';
and from 'active', 'queued_to_apply', 'applying' or 'error'
to 'queued_to_deny' to 'denying' to 'deleted'.
APIImpact
DocImpact
Partially-
Co-Authored-By: Mike Rooney <email address hidden>
Change-Id: Ic25e63215b5ba7
Changed in manila: | |
assignee: | nobody → junboli (junboli) |
summary: |
- Refactor Access Rules APIs + [DOC]Refactor Access Rules APIs |
This refactor from 2016 is quite old. Significant additional refactors and cleanups to access-list api as well as doc updates have been done since so we don't need this DOCIMPACT tracker anymore.