Updated share_back_ends_feature_suport_mapping.rst
with the features that the EMC Isilon driver currently supports.
Change-Id: I8dd0966324d4a901eea1725e30bb5f7e1c30eb44
The community agreed it isn't a good idea to promise future driver
features in the share_back_ends_feature_support_mapping document.
This commit removes the implication that future features may be in
the document, and it removes one reference to Mitaka in one driver.
Change-Id: I953cb92edfca3bd54f3196d60b9e80589b5033d1
wating -> waiting
acknowledgement -> acknowledgment
occured -> occurred
Should never get here. If get, then error occurred.
->
Should never get here unless an error occurred.
Change-Id: Ibe89d652e7d76b3d8e6d7549140c50c88144036e
Signed-off-by: Zhao Lei <zhaolei@cn.fujitsu.com>
Change StoragePool to Thin_StoragePool and Thick_StoragePool
in driver configuration file.
Add Huawei driver feature info in
share_back_ends_feature_support_mapping.rst
Change-Id: I530cbc58377e3207813cac36498225e26578824e
Add a .rst documentation for Hitachi HNAS Manila driver in dev docs.
Also, update the new .rst document that lists per-driver
features adding Hitachi HNAS driver details.
Change-Id: I1421d88df5ddc2a13849c9657ec90f55303065d7
Update the new .rst document that lists per-driver feature support
with details for the NetApp cDOT driver, and update the cDOT-specific
driver document to cover features added in Liberty.
Change-Id: I53cf0ac1f2492cfba599276c5dc049b3ae19f4c3
The Manila community set a deadline of 3 Sep 2015 for all drivers
to have reporting CI systems, and there is no CI system for the
IBM GPFS driver. As agreed, the driver will be removed until such
time that a CI system exists.
Change-Id: I76f238a1a6eb039e4ddc1cb189115ab3e686c56b
Add the following new features description in
Huawei doc.
- Share level
- Manage CIFS/NFS share
- Support pools in one backend
- Extend share
- Shrink share
- Support multi RestURLs(<RestURL>)
Change-Id: Ibc7a7fd83400ca588427390be0bf055abf296fcd
Originally copied from the Nova implementation of microversions,
we have come to realize that being able to specify 'latest' for the
microversion is rarely useful and usually dangerous.
Allowing clients to request the "latest" microversion guarantees
undefined (and likely broken) behavior in every situation where a
client talks to a server that is newer than it.
Change-Id: I3a5ba0d45804e567aba710a20628539b0c284499
Closes-Bug: 1489583
The Manila community set a deadline of 3 Sep 2015 for all drivers
to have reporting CI systems, and there is no CI system for the
HDS SOP driver. As agreed, the driver will be removed until such
time that a CI system exists.
Change-Id: I628fbcbbef42c7a215e0cca027c31f88ee6740aa
To prevent a microversioned client from managing a non-microversioned
Manila server, Manila must update its REST endpoints by adding /v2 for
all microversioned APIs.
This commit does the following:
* Add /v2 to the URL map, connected to all the same /v1 API methods
* Renumber the microversion sequence starting from 2.0
* Update the versions API to reflect v2
* Publish the new endpoint to Keystone in the DevStack plug-in
* Update relevant documentation
* Update Tempest tests for microversions
APIImpact
Co-Authored-By: Andrew Kerr <andrew.kerr@netapp.com>
Closes-Bug: 1488624
Change-Id: I56a516b5f81914557dd2465746629431cfd6deac
The HP 3PAR share type extra-spec prefix needs
to be "hp3par". The decision to go with "hpe"
was premature and has been reversed. It needs
to be "hp3par" to be in sync with Cinder.
Change-Id: I616832c71d1797fc00da0d9e42c35c315381b6d9
Depends-On: I26dd32b1de8cceeaa6dc674092efec683df71889
Closes-bug: #1488662
In manila-manage.rst version is misspelled
it is corrected. In manage.py according to
help option I changed revision to version
Change-Id: Icc83b3dcfc31104a015c9e6929335daed5a8bb8b
Closes-Bug: #1487249
Manila uses API microversions to allow natural evolution of its REST APIs
over time. But microversions alone cannot solve the question of how to
ship APIs that are experimental in nature, are expected to change at any
time, and could even be removed entirely without a typical deprecation
period.
Working in conjunction with microversions, this commit adds a facility
for marking individual REST APIs as experimental.
Implements bp: manila-experimental-rest-apis
Change-Id: I263a0b5579a7eb2fe98ca810ad3dec6719d66e6f
Report dedupe, thin_provisioning and hp3par_flash_cache
capabilities for 3PAR. Also report provisioned_capacity_gb
when thin_provisioning is True.
Implements Blueprint: hp3par-capabilities
Change-Id: I9dcba1bff5eba21b9b4b8cd4ed78beab75c2a8b6
Documentation for capabilities and extra-specs.
This needs to describe the agreed upon common capabilities.
Vendor-specifics go in driver docs.
Change-Id: I2c5bdf5ef9bfd6c8e7e06dac1fde08ad56cc6af1
The OpenStack API working group recommends all projects adopt
Nova-style microversions for versioning their REST APIs. This
commit ports the Nova microversion code and docs to Manila.
With this patch, the API version is bumped to 1.1, and the
versions API (which has always returned horribly outdated
values) is the first API that is versioned. The 1.1 version
of the versions API includes the minimum and current API
version values.
Implements bp: manila-rest-api-microversions
Change-Id: Ifa8e394335a4eb3ad21f53a873530aee241c00e8
Remove URLs from jenkins.rst which is no longer exist
and fix incorrect URLs.
Change-Id: Ic7303ac3bdf8e7aceacc52ccc8461a24ace7c39d
Closes-Bug: #1480012
Internationalization's abbreviation is i18n.
This patch renames l to one for il8n.rst.
Change-Id: Ibd588fee48565f78cdc953973012a8ec613ed058
Closes-Bug: #1477985
The recently added HP 3PAR extra-specs for create share options
use the wrong prefix for scoping. The prefix should not have used
an underscore in it. In addition, the underscore used in the docs
was different than in the code.
The new scoping prefix will be "hpe3par" (to be followed by a colon
for scoping or underscore for future capabilities).
Fixes Bug: #1481106
Change-Id: Ibd326fc367c1845e56706969daf01359fa7b2dac
Add doc where we provide mapping of supported share features by each specific
share driver.
In this commit up-to-date information is provided only for Generic driver.
All other are expected to be updated afterwards.
Change-Id: I9645857b59563084b76a94308f4523e37b860201
With GlusterFS 3.7.x versions, the delete share operation fails when
deleting the contents of a GlusterFS volume, a share. This is because
two directories are auto-created within a GlusterFS volume when it's
started and GlusterFS refuses to unlink their paths. Fix this issue, by
not trying to remove the two directory paths, but remove their contents
and the rest of the contents of the volume.
Change-Id: I1675bbf593bf578301d6899ee3f9860320080956
Closes-Bug: #1473324
