Currently, manila doesn't support user controlled way to encrypt the
shares. This spec intends to make this possible.
Implement: blueprint share-encryption
Change-Id: I0245e89e4dedcdb6afd1cbfb992ff3b80f7d06e2
During delete, free the used share/share-snapshot quotas immediately
and process deferred share/share-snapshot deletion in share manager.
This will reduce the waiting time of new share/share-snapshot creation
blocked on quota limit.
Partially-Implements: blueprint deferred-deletion
Change-Id: Ia7591f036f975a0610a45c5ebbc54696d8244fd0
Design of better visibility and manipulation protections
to access rules of a share.
APIImpact
Partially-Implements: bp protect-access-rules
Change-Id: Ib184995f6fce2a9aaa60f8251513d58c5b663112
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
A proposal to introduce "resource locks" that
can be placed by project users against project
resources and specific resource actions that
they intend to prevent. In the 2023.2 Bobcat
cycle, the share deletion resource locks will
be implemented.
Partially-Implements: bp allow-locking-shares-against-deletion
APIImpact
Change-Id: Icdc909c43459730c8e35a677779d842e36dc7b1b
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
Adds the spec-lite for the integration between NetApp ActiveIQ
software with Manila Scheduler weigher phase.
It also adds the bobcat release directory specs.
Change-Id: I7ecbad25660f10170172fc2a07507000bfafde75
Currently, manila doesn't support backup and restore share features in
manila itself. This spec intends to make this possible.
Implement: blueprint share-backup
Change-Id: I3b345f396e581575a403c728136eb644565c5928
The documentation is writting the date in its copyright. This is
considered bad practice, because this kills reproducibility. If
you don't know about reproducible build, please read on:
https: //reproducible-builds.org/
Change-Id: I6e379661079aecc53035f329e4cc3c91fd420362
Switch to openstackdocstheme 2.2.1 version. Using
this version will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems
Update Sphinx version as well.
Change pygments_style to 'native' since old theme version always used
'native' and the theme now respects the setting and using 'sphinx' can
lead to some strange rendering.
openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.
See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html
Change-Id: I9843c6b66d4411857cb19c5d176d39b200423257
This cleans up stuff so users and documentation
folks can be sure that targeted specifications
have been implemented in one form or another.
Change-Id: I0a8daab3ba55ff43b3db8433077eb667b84a5ee2
And fix a few inconsistencies with test
scenario #7 and call for new contributions
Change-Id: I760d22cb6ef90d05eaabd8aeddfbc2e145cee1c9
Partially-implements: bp scenario-tests
With the move to zuulv3, the openstack-tox-py* job definitions
ignore doc only changes so we do not get spec
linters run as part of the py27 and py35 targets any more.
Run doc8 from the pep8 target. Also drop the spell check job
since the way it is implemented causes the doc8 job to fail and
the optional spellcheck job was not useful as a practial quick
check anyways since it reported over 1000 "misspellings" because
OpenStack vocabulary contains many words and acronyms not in its
dictionary.
Corresponding changes have been proposed for nova [1] and
cinder [2].
[1] Ic87e79db6a8881398d670148b609e0b81658dfd1
[2] Ida20764edde3a07c89703d82b41958c96548b239
Change-Id: I82c8dbec713fc5575fd03c0ae290bf190bbdf8ca
and its family of diagrams [1]: blockdiag, actdiag, seqdiag,
and nwdiag.
These enable block, sequence, activity, and logical network
diagrams, defined in a simple text format, and with this patch
can be easily embedded in our specs. For examples, see [2].
[1] http://blockdiag.com
[2] https://specs.openstack.org/openstack/neutron-specs/specs/juno-incubator/example.html
Change-Id: I999d8f5211266c4ce6d991ff92fe73e3843b5596
so that we can run 'tox' locally and properly validate our spec
docs.
* Update tox minversion and requirements
* Clean out build directory before new docs build
* Run doc8 validation
* Fix numerous incidental errors in the specs and templates
so that doc8 now passes
* Setup both py35 and py27 environments
* Turn off yasfb extension until it can work with python 3
Change-Id: I722a9ad852cdfa0974322fbe29db37956dab3ee0
For some reason, gerrit merger does not consider same logic
of adding Ocata specs imports to index page as the same and does not fail
with merge conflict. It just duplicates it. So, remove it.
Change-Id: I7e002af2a761ee91f0ad644309c2929c8bde2f7a
In Manila, the only thing users can do with snapshots is to create new
shares from them. Alternate snapshot semantics were discussed in Tokyo
and Austin. At the Austin Summit, the community agreed one of the new
snapshot semantics would be to revert a share (in place) by restoring
the most recent snapshot of that share taken by Manila.
APIImpact
Partially implements: blueprint revert-to-snapshot
Change-Id: Id79c0f6eae25f8380dadde3d65241a56aafa18a8
This spec defines the addition of a new optional extra spec,
create_share_from_snapshot_support, which removes the overload
from snapshot_support. This is needed prior to the addition of
new snapshot semantics, such as revert-to-snapshot.
APIImpact
DocImpact
Partially implements: blueprint add-create-share-from-snapshot-extra-spec
Change-Id: I4d95fe3609b7728ea7d9ed8be6e96241307f0002
It's enough to just show the spec headline - like in all other
spec repos. Otherwise it list also sub-heading within the documents
(which is basically the same for all documents).
TrivialFix
Change-Id: I01c1412a0fe15f309a3d19ce8b8af5a4225aad49
Add sym link to specs otherwise the build doesn't work and add a section
for each release (like in cinder).
Change-Id: I0e6685ea556a1905636219503c1339cdedf7d179
Kiran Pawar