Adds create share from snapshot functionality to
CephFS drivers.
Depends-On: https://review.opendev.org/c/openstack/manila-tempest-plugin/+/778188
Co-Authored-By: Victoria Martinez de la Cruz <victoria@redhat.com>
Co-Authored-By: Ramana Raja <rraja@redhat.com>
Co-Authored-By: Tom Barron <tpb@dyncloud.net>
DocImpact
Partially-Implements: blueprint create-share-from-snapshot-cephfs
Change-Id: I825ab15af934cb37dfda48ea26ec1af9de8dd293
Allows set min/max share size that can be created in
extra_specs for each share_type.the share size will
be checked at API level as part of share create,
extend, shrink, migration_start. when manage share,
check it after get true size of share at manager layer.
new extra_specs keys are supported for set min/max
size of share.
'provisioning:max_share_size'
'provisioning:min_share_size'
Implements: blueprint share-size-limited-by-share-type
Change-Id: I5ce0fabf59bfca5ebaf0be5ffe9986e2b0480295
The profiler integration with the shared file system service(Manila)
allows to trace commands issued using both manila-client and
openstack-client.
Note that osprofiler should be run from admin user name & tenant.
Closes-Bug: #1915116
Change-Id: Ic16bc3cb03b851003c189450b398f8dd5dde8160
As of API version 2.60, a project_id is no
longer needed in the API URLs.
Fix the docs to indicate that.
Also fix up a few quota parameters that use
project_id in a different place in the API path.
Change-Id: I24b32c8521805a7d67d512d36d644c0f07c532ea
Implements: bp remove-project-id-from-urls
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
MANILA_MULTI_BACKEND has been deprecated for five years now, we should remove
it from our code base.
This variable was removed from the settings scripts along with:
MANILA_BACKEND1_CONFIG_GROUP_NAME and MANILA_SHARE_BACKEND1_NAME;
MANILA_BACKEND2_CONFIG_GROUP_NAME and MANILA_SHARE_BACKEND2_NAME.
Because they work in the same context.
Instead of them, the already implemented and in use,
MANILA_ENABLED_BACKENDS variable was placed to garantee the successful
back-end setup. The same replacement was made in the contribution
samples scripts.
Apart from this, we avoid configuring generic1 and generic2 if
another backend/s are selected.
Closes-Bug: #1898791
Closes-Bug: #1878477
Change-Id: I67036a65da9255694a00a9c8d56cfdefbdf23c05
Adds a missing cap to access mgr and be able to list subvolumegroups
and subvolumes in a cephfs volume
Change-Id: Ie9849ed875b996cf33aeb296f258ec84c8b720ef
Closes-Bug: #1907467
It currently refers to the old openstack repository and as written
downloads redirect information rather than the image itself.
Add a '-L' argument to the ``curl`` command to handle redirects and
update the URL to use the opendev repository.
Related-bug: #1908838
Change-Id: I48509e5c9be41c04d00aa86efd4d657b067d9521
Include Wallaby (master) support matrix and
some extra considerations to consider on manila
with cephfs backends.
Change-Id: Iad7cb229151b8dd707a59553cb6e966090d0eeae
Updates the developer reference with informations regarding the
share server migration feature implemented during Victoria release.
Change-Id: Ia72cf037d2b7dc9fb9d4f19ce141cc044206d6fc
Partial-bug: #1897903
The openstack Ussuri and Victoria versions no longer support the
Centos7 and pyrhon2 environment packages. Correct the missing
problems in the latest document
Change-Id: If139927730071448abc04e1ea7ebb615749e7e3d
As per the community goal of migrating the policy file
the format from JSON to YAML[1], we need to do two things:
1. Change the default value of '[oslo_policy] policy_file''
config option from 'policy.json' to 'policy.yaml' with
upgrade checks.
2. Deprecate the JSON formatted policy file on the project side
via warning in doc and releasenotes.
Also convert manila/tests/policy.json to manila/tests/policy.yaml
using oslopolicy-convert-json-to-yaml tool and replace
policy.json to policy.yaml ref from doc and tests.
[1]https://governance.openstack.org/tc/goals/selected/wallaby/migrate-policy-format-from-json-to-yaml.html
Change-Id: I3748313912b2527c43c9b16a6ba3e3ccd4cf5221
to make user devstack deployment a bit easier.
Since snapshot_support is now on by default for Ceph
backends, enable it in the default share type extra
specs.
Also specify the SHARE_DRIVER so the manila devstack
plugin doesn't think we're running the generic driver
and try to install kernel NFS and samba servers.
Change-Id: I636a047cacba7c5960df15a99fc79a35a818f45d
Added paragraph to the NFS-Ganesha docs with a brief
explanation of the role of ``dbus`` messaging when doing
dynamic updates of exports. Key point is that ``dbus-send``
and NFS-Ganesha must be in the same namespace even if NFS-ganesha
runs in a container.
Close-bug: #1883961
Change-Id: I57b916b16d07a8373143f396b42ea34bf80330a6
This patch adds the admin and user documentation for share revert to
the latest available snapshot.
Change-Id: Id35b99fdb47bb9de38f42034818fb4a29370bf36
Closes-Bug: #1657322
The driver inflated total and available capacity
due to an incorrect calculation. The driver was
also ignoring the configuration option
"reserved_share_percentage" that allows
deployers to set aside space from scheduling
to prevent oversubscription.
While this bugfix may have an upgrade impact,
some things must be clarified:
- Inflating the total, free space will allow
manila to schedule workloads that may run
out of space - this may cause end user
downtime and frustration, because shares are
created (empty subvolumes on ceph occupy no
space) easily, but they could get throttled
as they start to fill up.
- CephFS shares are always thinly provisioned
but, the driver does not support oversubscription
via manila. So, real free space is what
determines capacity based scheduler decisions.
Users however expect share sizes to be honored,
and manila will allow provisioning as long
as there is free space on the cluster. This
means that Ceph cluster administrators
must manage oversubscription outside of manila
to prevent misbehavior.
Depends-On: Ic96b65d2caab788afca8bfc45575f3c05dc88008
Change-Id: I6ab157d6d099fe910ec1d90193783b55053ce8f6
Closes-Bug: #1890833
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
This patch improves the access rules API documentation
to include IPv6 information that was missing.
It includes a note on user guide and changes an access list
example to IPv6.
Change-Id: I5a9ff4e3c8a70cb0b14caa39f5f17740b17b719a
Closes-Bug: #1705045
Signed-off-by: Douglas Viroel <viroel@gmail.com>
This is the basic user guide for manila:
- Update examples and outputs
- Add limits and metadata examples
- Add descriptions about common concepts
including share type extra specifications
- Add contents for easy navigation
Change-Id: Idf374866a63e0da2c4af3157ac5f471af6173d5e
Closes-Bug: #1652375
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
Some content in the admin docs was incomplete,
and irrelevant to administrators.
Also add notes on a couple of missing common
capabilities:
- mount_snapshot_support
- availability_zones
Partial-Bug: #1816486
Change-Id: Ie55fd5bf80ca2ebacdb652c701aa9c213f758963
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
This patch adds the behavior described in the bug #1713060
as known restriction in the generic driver.
Change-Id: Ic70fcd9f6cf159a960e0d75b4081c88af3d8973e
Closes-Bug: #1713060
This patch add some notes regarding the use of scheduler when
creating share from snapshot in another pool or backend.
Change-Id: I8d904cb3aab4d653178948284571f471bd59ac1b
Closes-Bug: #1878244
Updates user guide documentation to provide metadata info
to an access rules. Also add two new operations for access
rule metadata: 'access-metadata set' and 'access-metadata unset'
Change-Id: Ib6008c9dd4284b8c3434ffce61fb74f1db6c3d35
Closes-Bug: #1782859
Extend docs on running manila API with a web server (Apache, NGINX)
Add samples for mod_wsgi
Partially-implements: blueprint wsgi-web-servers-support
Change-Id: Ic756466e65ffd8b5fc6b8e8fb3eef4b8535b46d6
Added some samples on uWSGI config and some docs
on how to run manila with uWSGI for contributors.
Partially-implements: blueprint wsgi-web-servers-support
Change-Id: I8e68619b00255197b3d3cf6796c60d1a3a04ff36
This was missing for manila, and is required
for us to apply for the assertion that the
service supports accessible upgrades.
Change-Id: Ib3f4c917bdd22209e6b76e2175e3b4b28f05bdba
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
The CephFS driver optionally advertised snapshot
support to manila, based on a configuration
option "cephfs_enable_snapshots". Manila does not
provide snapshots by default to users, unless an
administrator chooses to set the "snapshot_support"
extra-spec in the share type they're using. So this
configuration option is really an unnecessary safeguard
at this point.
Moreover, CephFS snapshots are fully supported from
Ceph Nautilus, and with Id847b1b5e6623172f2600afd69e51182067444cb,
manila added a support statement for the Victoria
release that indicates that Nautilus is the minimum
version of ceph supported. So let's default this
option to True, and deprecate this option at the same
time to eliminate this duplicate safeguard.
Partially-implements: bp update-cephfs-drivers
Depends-On: I885ff78586540d01590f98cca2a00d55161dbe04
Change-Id: I1ef42b414f8af0b8f9a912655757ec200a75c309
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
The manila discussed cephfs futures
during the Victoria cycle PTG [1]. To support newer
features in ceph, we'll need to start using the
ceph-mgr interface that debuted in Nautilus.
When we start adopting ceph-mgr, we can no longer
support Mimic, Luminous and older releases of Ceph
without maintaining code workarounds and a continuous
integration system to ensure they're not broken.
This takes considerable effort from community members.
We've supported the Luminous release since OpenStack
Queens, and there have been at least
three other major releases of Ceph in the meantime,
let's add a release note and adjust the ceph driver
documentation calling out our support/testing stance.
[1] http://lists.openstack.org/pipermail/openstack-discuss/2020-June/015494.html
Partially-implements: bp update-cephfs-drivers
Change-Id: Id847b1b5e6623172f2600afd69e51182067444cb
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
The mock third party library was needed for mock support in py2
runtimes. Since we now only support py36 and later, we can use the
standard lib unittest.mock module instead.
Change-Id: Iac98e1abac61757ff143e33f0094babe42cc2e60
