Updating Manila Hitachi HNAS driver to support shares using CIFS protocol.
It accepts 'user' as access type and both rw and ro as access level.
Change-Id: I18fd5afcea6f91d870bbfc256c71a92aad014c91
Implements: blueprint hnas-driver-cifs-support
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
Implement 'manage snapshot' feature in ZFSonLinux share driver.
Prerequisites:
- snapshot being managed should exist.
Details:
- snapshot being managed will be renamed by share driver based on
taken ID.
- size for managed snapshot will be taken either from
REST API (--driver_options size=5) or
from its "used" attribute.
Implements BP zfsonlinux-manage-snapshot
DocImpact
Change-Id: If240ecde5676c334d39faaccd5703e93544aaa06
Depends-On: Ifc762a882a78159adacfe168a4edbe824178301a
The tox/Sphinx job does not use this makefile and
the README refers to some unrelated/cookiecutter
information.
TrivialFix
Change-Id: Ic9dc7818dd5f0e2a6d2f691046f6c1fb30cf0cd0
Co-Authored-By: Sean McGinnis <sean_mcginnis@dell.com>
Adding support for reporting disk type of pool in huawei manila
driver. When creating share we can specify the disk type of the
pool we want to use ssd/sas/nl_sas/mix, manila driver will report
the disk type of the pools.
Implements: blueprint huawei-pool-disktype-support
Change-Id: I1f694e8c93f79851f838d226830d9ab5344cf35a
Add a new list option 'emc_interface_ports' to configure the network
devices that can be used by share servers. And refined managed pools
selection method to use a new utility method.
DocImpact
Change-Id: Id44ca5e3e64b5a540c91119698e5191366cabfc5
Closes-Bug: #1600117
Data in the file system consists of fixed-length disk blocks.
The size of the blocks (also known as file system sector size)
affects disk space usage and performance.
The value of blocks can be 4 KB, 8 KB, 16 KB, 32 KB, or 64 KB.
Change-Id: I95a9aa7e071c470c21dc0fa009ba96a7c7439ce6
Implements: blueprint huawei-driver-block-size-config
- Manage share: ask Manila to take control of an existing ZFSSA share
not managed by Manila driver. Current share size will be rounded up
to the nearest whole GB value.
- Unmanage share: ask Manila to release control of a ZFSSA share
managed by the driver.
Change-Id: I0d4a46211dfd15cb7a261eddfa8c14be26adcfc3
Implements: blueprint oracle-zfssa-share-manage
Implement 'manage share' feature in ZFSonLinux share driver.
Prerequisites:
- share being managed should exist.
- share being managed should not be part of any replication relations.
- share being managed should not have redefined mountpoint.
Details:
- share being managed will be renamed by share driver based on taken ID.
- share being managed will get "quota" attribute set based on provided
value in API (--driver_options size=5) or it will set quota
to nearest bigger rounded integer of already
used space (2,4 -> 3, 3.6 -> 4).
Implements blueprint zfsonlinux-manage-share
DocImpact
Change-Id: I03eab5e02835fe660dde0020601c02c0136bddeb
With snapshot manage / unmanage in Manila core, we can
support that in the NetApp single-SVM driver.
Implements: blueprint netapp-cdot-snapshot-manage-unmanage
Change-Id: I7c6c005fb3fd8613da9e9ac04b9dd832781e35ca
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
The tool reno is used to generate yaml releasenotes files.
This patch adds doc info, how to use venv of tox to use reno, if
reno is not installed globally on your system.
TrivialFix
Change-Id: Id1d2e8969db60f78eb6b4aebdff3329c5b35bc5b
The Module Index link points to a non-existing page.
So, the link is removed to avoid confusions.
Change-Id: I2ed9d04a347eec2399dfd8e4276533e5ea706614
Closes-Bug: #1566818
Formatting errors have crept into the manila devref
and have been accumulating over time. It would
be nice to fix these as part of the devref cleanup.
Closes-Bug: #1583850
Partially-implements: bp improve-manila-developer-docs
Change-Id: I7ec954e720b4b88a21e265cd71ea598ea9a5213b
In manila/api/openstack/rest_api_version_history.rst,
underscores were used instead of hyphens to underline version '2.14'.
Fix to remove visual incongruity.
In doc/source/devref/scheduler.rst, not all drivers were added or
updated. Fix to include all drivers.
Partially-implements bp improve-manila-developer-docs
Change-Id: I513a4b51ab5f3d8c0cdb5aa013c93ecd07a85a20
References for base and simple scheduler drivers must
reference to the right location in drivers folder.
Change-Id: I7698efd9c656c1204641567b1009ad270a20aa21
To allow for our developer reference to be consistent with
the rest of the openstack documentation, we need to import
and render this theme on our developer reference.
This gives users a consistent experience as they may
be acquainted with the rest of the OpenStack documentation
(Admin Guide, User Guide, API Guide etc.)
before perusing the Manila developer reference.
It also provides our devref the "log-a-bug" feature so
readers may bring any mis-information to our attention.
This patch is part of a series of commits to improve
in-tree documentation.
Change-Id: I0e4686a273c5bf45c1d57764cd4c312870b06d6e
Partially-implements: bp improve-manila-developer-docs
Add more details about driver specific concepts and usage.
Also, add known restrictions of the Mitaka version and license
details.
Change-Id: I03e767454a0f69fce9aebb10aa9866520acc1413
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
When building packages if git is absent, then we should not set
html_last_updated_fmt. It can still be set via the -D switch
when building with sphinx-build.
Change-Id: I02a6bcb43c8283848fb3866bb52cc4c0f50f4c92
Closes-Bug: #1552251
With the Mitaka release multiple changes have been made to the
Manila driver:
- Access rules changes for both NFS and CIFS shares.
- IP and user access rules changes for both NFS and CIFS shares.
- Client version bump.
- Deleting of file tree for nested shares.
Change-Id: I09fbaad15e18c5babdbe8a419737ffc7b23d0d7d
This commit updates the development environment devref document's
instructions of package installation on Fedora-based releases.
Change-Id: Ia35f8632c45a77fce92f48a8dd7c654a20037c9d
Add a new matrix to the share backends feature support mapping page
in the developer reference to indicate which backends support which
common capabilities, such as QoS and Thin Provisioning.
The Driver Handles Share Servers capabilities I retrieved from the
share creation column earlier in the same page. Other common
capabilities are currently filled in with information gathered from
the _update_share_stats() methods for each driver.
Change-Id: I5dfff0a62c91a047fc142018ece5f65edab3866a
Fix some information about ZFSonLinux share driver to make it
up-to-date with Mitaka version.
TrivialFix
Change-Id: I286ad6e603f1fd0afa069178f0a603174a988544
This reverts commit 466a19f18f12cb77b45aa7c7a272fae7c45c4c93.
Also this reverts commit 4f74b224fad7bf9ca665d70a66c79c98cf8d5674.
Manila has decided to remove LXD from the Mitaka release.
http://lists.openstack.org/pipermail/openstack-dev/2016-March/089522.html
Change-Id: I3c4b15e8c9d92c874be754205b0b981151809cc1
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
