This patch updates the documentation for the Hitachi NAS Platform
File Services Driver for OpenStack.
Closes-bug: #1536812
Closes-bug: #1614833
Closes-bug: #1616618
Closes-bug: #1623105
Change-Id: I0291efcadf244b7911969cfb367387a5998f1a23
This driver exploits a Docker container as a share server instead
of a virtual machine. The container acts as a CIFS server
and shares logical volume attached to it. The volume gets created
simultaneously to the container on a host in a volume group
specified by the user.
DocImpact
Change-Id: I711813a2022d765ab7a70ed670e34f68f9cf1399
Implements: blueprint manila-container-driver
EMC Unity arrays are capable of support manila.
Add a new Unity plugin in manila which allows user to create NFS/CIFS
share with a Unity backend.
The plugin should support following APIs:
* connect: Connect to the Unity Storage.
* check_for_setup_error: No implementation.
* create_share: Create a share and export it based on the protocol used
(NFS or CIFS).
* create_share_from_snapshot: Create a share from a snapshot - clone a
snapshot.
* delete_share: Delete a share.
* extend_share: Extend the maximum size of a share.
* create_snapshot: Create a snapshot for the specified share.
* delete_snapshot: Delete the snapshot of the share.
* allow_access: Allow access of a user/host to a share.
* deny_access: Remove the access of a user/host to the share.
* ensure_share: Check whether share exists or not.
* update_share_stats: Retrieve share related statistics from Unity.
* get_network_allocatins_number: Returns number of network allocations
for creating VIFs.
* setup_server: Set up and configures share server with given network
parameters.
* teardown_server: Tear down the share server.
DocImpact
Co-Authored-By: Cedric Zhuang <cedric.zhuang@emc.com>
Change-Id: Ic520539341fa19ec5c6c6b85c3c1dcecf70e5141
Implements: blueprint emc-unity-manila-support
To be able to run tests based on following criteria:
- Only API is required and tested.
- API and share back-end required, API is tested.
- API and share back-end required, back-end is tested
Also, add doc with detailed description of running subset of tests.
Change-Id: I9ae105eaa527621c85d5038bba15edf4b065eaa3
Closes-Bug: #1587874
A lot of things have been changing with OpenStack's
documentation. As a community, we could do a better
job at catching up with these changes and
documenting our project well enough for the
benefit of all stakeholders.
Add instructions on where to document what and
provide tips to manila developers on documentation.
Change-Id: I660bfd5ac3d61c253e1e7b4b02c51424a03fa0a0
Partially-implements: bp improve-manila-developer-docs
Added some documentation for how and when to use commit message tags
in git commit messages. Also added a link to the new article in the
index for the dev ref.
Change-Id: I5aa4c128cd0e25fb12316de21eed262cca810e08
The Tegile driver will support the NAS shares and it will
include the minimum set of features.
[Supported Protocols]
- CIFS, NFS
The driver supports Manila driver mode
(driver_handles_share_servers = False).
Tegile has setup a CI. It will report as "Tegile Storage CI".
DocImpact
Implements: blueprint tegile-share-driver
Change-Id: I2e9154454e2a34f9a0653a173846ce554026f33b
This driver enables use of the Ceph filesystem for
Manila shares. Clients require a native CephFS
client to access the share. The interface
to Ceph is CephFSVolumeClient, included in
the 'Jewel' Ceph release and later.
APIImpact
The API microversion is bumped to 2.13 to add a
new access type, cephx, supported by the driver.
Co-Authored-By: Ramana Raja <rraja@redhat.com>
Implements: blueprint cephfs-driver
Change-Id: I33801215f64eacb9dade4d92f11f659173abb7f5
Add support for ZFS (on Linux) filesystem.
Following features are supported:
- Create/delete share
- Create/delete snapshot
- Create share from snapshot
- Extend/shrink share
- Update NFS IP-based access rules using new interface.
(SMB support planned for future).
- create/delete/update/promote share replica
ZFS-related notes:
- Any amount of ZFS zpools can be used by share driver.
- Allowed to configure default options for ZFS datasets that are used
for share creation.
- Any amount of nested datasets is allowed to be used.
- All share replicas are read-only.
- All share replicas are synched periodically, not continuously.
So, status 'in_sync' means latest sync was successful.
Time range between syncs equals to value of
config global opt 'replica_state_update_interval'.
Driver-related notes:
- Able to use remote ZFSonLinux storage as well as local.
Other made changes:
- updated driver private data DB methods removing filtering by host
as redundant operation. Replication requires some common metadata
storage and filtering by host breaks it. It is safe to do so, because
if driver gets some ID of entity then it is allowed to read its info
too.
Implements bp zfsonlinux-driver
DocImpact
Change-Id: I3ddd3767184e4843037de0ac75ff18dce709b6dc
This patch refactors the HP share driver to now be
the HPE share driver.
This is being done because the company responsible for
this driver is now Hewlett Packard Enterprise (HPE).
The driver is now located in the manila/share/drivers/hpe
folder.
DocImpact
Implements: blueprint rebrand-hp-3par-share-driver
Change-Id: I36efc04fa6da088ccb06070d8cd4fe29269cd7ca
This document consists of a list and explanation of minimum features
a driver must implement to be accepted into Manila code base.
Change-Id: I12d5bf60abad4a7146d5d596f03d96bf2605cbdc
Adding GPFS driver back as the third party CI system
for GPFS driver is up and running.
This is a revert of commit 720ec904456594b453cfd220b002bdc8c0d50e08
Change-Id: I86f9b7da21716346f96bae3ce30446589e4c4c37
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
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
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
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
Internationalization's abbreviation is i18n.
This patch renames l to one for il8n.rst.
Change-Id: Ibd588fee48565f78cdc953973012a8ec613ed058
Closes-Bug: #1477985
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
This adds the glusterfs_native driver developer doc,
specifying requirements, configuration instructions,
and limitations.
Change-Id: Ie42a43e2cdd88907914d5f7ddab26f417f1a3e99
Add the hdfs_native driver developer doc with requirements,
supported operations, configurations, and limitations.
Change-Id: Ifbe785f25e779be6871ebc8474f9fbb1d38af82b
Add doc for Dynamic Storage Pools for Manila scheduler dealing
with the need and impact of Pools with respect to Manila.
Change-Id: I1db2b56a6377775ef2f834179e603cd4f755d2f5
The Manila cDOT driver is a single file exceeding 1200 lines. It contains
multiple things (driver code, protocol helpers, ZAPI invocation code,
options) that should be split apart to allow for easier maintenance and
readability and add the potential for code sharing when we reintroduce
a 7-mode driver, add a single-SVM cDOT driver, etc.
We recently refactored NetApp's DOT Cinder drivers into a 4-layer
structure (interface, library, client, API) that separates concerns and
achieves the goals set forth above. This commit satisfies a plan to
do the same thing in Manila. The implementation steps are:
1. Update directory structure to match that of the Cinder NetApp drivers
2. Create driver interface shim
3. Move driver code to library (with base & C-mode classes, to allow for
7-mode code sharing later)
4. Move protocol helpers to separate files (already organized by base &
C-mode classes)
5. Split out ZAPI code to client layer (with base & C-mode classes, to
allow for 7-mode code sharing later)
6. Implement NetApp driver factory as in Cinder
7. Implement common NetApp options file as in Cinder
8. Implement cDOT API call optimizations
9. Update all unit tests as needed
Note that this patch appears to treble the total number of code lines.
This is due to the addition of many more unit tests plus a large amount
of fake controller API data to feed the API client tests.
Implements: blueprint netapp-manila-cdot-driver-refactoring
Closes-Bug: #1410317
Partial-Bug: #1396953
Closes-Bug: #1370965
Closes-Bug: #1418690
Closes-Bug: #1418696
Change-Id: I3fc0d09adf84a3708f110a89a7c8c760f4ce3588
Add doc for Huawei driver with descriptions on its requirements,
limitations, and configuration instructions.
Change-Id: I212ddf9f0b4b50d62970043405ea3cb59b83f03b
Add doc for EMC VNX driver with descriptions on its requirements,
limitations, and configuration instructions.
Change-Id: I5a8e9d62d0708b56aadfe85a83faaf5dc1557f6b
Add doc for an Introduction to Manila dealing with the fundamentals and basic
terminology used with respect to Manila.
Change-Id: I07b7442ed91f7fec7b87087499e5047aecc6389f
