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
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
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
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
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
This driver exploits a container as a share server instead
of a virtual machine. The container acts as a NFS/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. Currently NFS is limited to v3 since the
only userspace NFS server that works in a container out of the box
seems to be unfs3. Later it will be replaced with nfs-ganesha.
Co-Authored-By: Alexey Ovchinnikov <aovchinnikov@mirantis.com>
Implements: blueprint lxc-driver
Depends-On: Ib1896997f2e7a505b5bf8ec0c9e5ee35942f79a6
Change-Id: Iea73bd34b94919d77ebe17cf054dde1f580384be
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
Having a driver in the top level of the drivers
directory was against source tree placement
conventions. It was especially weird because
all other GlusterFS related code lived in
a dedicated subdirectory.
Partially implements bp gluster-code-cleanup
Change-Id: I52d717ab6396454c2e7a9b62aa00ea443b26d5cc
This change adds share shrink and extend features to Oracle ZFSSA
Manila driver.
Change-Id: I09cd9bd3002007bd30e6a2e22bfd3f3f711b2bd9
Implements: blueprint oracle-zfssa-share-shrink-extend
Modify following configuration:
Add the new features that Huawei driver support.
Add the corresponding configuration for "create
share from snapshot".
Modify the abilities Huawei driver report.
Change-Id: I74d55c0ba75a7908d8ba346bfe0b4e853e1c66df
Closes-Bug: #1549657
