Updates to the administrator and configuration metadata to address
the new configuration option, which allows administrators to
specify metadata items that should not be updated by less
privileged users.
Signed-off-by: silvacarloss <ces.eduardo98@gmail.com>
Partial-Bug: #2057707
Change-Id: If8d51d50630f0581d588e07c3c086442b451c360
There's a new driver mode supported since
Antelope (introduced in Zed) that supports
ceph orchestrator deployed CephFS NFS clusters.
We were missing documentation regarding this.
Also consolidate the admin/configuration references
for this driver; this deletes all the outdated
information in the existing config guide.
Partially-implements: bp use-cephadm-nfs-ganesha
Change-Id: I43952d890629e60465059a5b4242817becb198b1
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
Export locations are usually too difficult to memo
rize.Currently, there is no way to determine the
export location before the share is created, so
users wait until the share creation request gets
completed, and then they check the export
locations to mount the share. The generated
export locations are often not human readable
and it is hard to memorize and control them.
Implements: bp/human-readable-export-locations
Change-Id: I72ac7e24ddd4330d76cafd5e7f78bac2b0174883
This feature was added and maintained by Cloudbase as part of effort to
support Windows-only OpenStack but Winstackers project was retired and
there seems to be no on requiring this deployment architecture now.
Because the driver hasn't been get any meaningful update for some time
and we no longer have Hyper-V CI active, this proposes deprecating
the driver so that we can retire it in 2024.2 at the earliest.
[1] d9c0bda0b7
Change-Id: Icec29f5512d4c4ce8c8d7ccb1f2d3823bffa7ed9
CI of these drivers has been broken since migration to Ubuntu Jammy
and no one has shown interest to fix it so far.
Because these drivers haven't been update for some time, we can assume
these drivers are no longer used.
Related-Bug: #1998493
Change-Id: I9df5b7289dcec3a0de321169e892512571e7c006
This removes support for using "vmax" backends, which was translated
to "powermax" backends. This behavior was expected to be removed during
Wallaby cycle.
Also replace the remaining reference to EMC VMAX.
Change-Id: Id1187a9a99d87abefe3549e70df768f41494145f
The following services were removed some time ago.
- nova-objectstore
- nova-consoleauth
- glance-registry
Change-Id: Ida5b570eae34243a82f1bebe48b563f8076e83b0
Minor change to allow multiple data VIP addresses
to be specified in the `flashblade_data_vip` parameter.
Each data VIP will be used to define the file system
export address for shares created. The first address in
the list will be clasified as the Preferred export
address, but this is not enforced.
Change-Id: Ia3bfdd5ce1bfd31d10193d1f222bf27b38c8ef43
- Dell EMC driver had an issue with mocking an object
and sending it forward.
- Some of the create table statements in the database
migrations didn't have the charset specified. That seemed
to trick the DB engine while defining foreign keys and
adding a name to them, as the default charset was defined
in the schema, but not in the tables. This behavior was also
noted in different places, like [1]. Fix this issue by
adding the charset to all create table statements, so they
match the engine default charset.
[1] https://github.com/apache/superset/issues/8808
Change-Id: I7cd6fa0cc8e054af112493746e753fef2024000f
Access rules rules allow API will now take three additional
parameters:
- lock_visibility: when True, only services, administrators and
the same user will be able to see the content of ``access_to`` and
access_key.
- lock_deletion: when True, the access rule will be locked for
deletion. Only services, administrators or the user that placed
the lock will be able to drop the access rule.
- lock_reason: a reason for the lock. This parameter should only
be provided in the presence of at least one of the former
parameters.
In order to delete an access rule that is currently locked, the
requester will need to specify ``unrestrict=True`` in the request.
In case a service placed the restrictions, only the own service or
the system administrator will be able to release it.
This change also implements filters to the access list API. It is
now possible to filter access rules based on `access_to`,
`access_type`, `access_level` and `access_key`.
DocImpact
Change-Id: Iea422c9d6bc99a81cd88c5f4b7055d6a1cf97fdc
Adds a new Manila driver to support Dell PowerFlex storage backend.
It will include the minimum set of Manila features.
Implements: blueprint dell-powerflex-manila-driver
Change-Id: I4dc81bf75135b32f1971ca21eee298bca33441cf
Add CRUD APIs for resource locks with support
for preventing deletion of shares (applies to
soft-deletions and unmanage operations as well).
Change-Id: I146bc09e4e8a39797e22458ff6860346e11e592e
Implements: bp/allow-locking-shares-against-deletion
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
Adds a new Manila driver to support Dell PowerStore storage backend.
It will support NFS share operations and snapshot operations.
Implements: blueprint dell-powerstore-manila-driver
Change-Id: If0d0a7820a1ae2392e5e0e4a4b65c4e631f4c3d4
Allows set max share extend size that can be created in extra_specs
for each share_type. At API level as part of share extend for admin,
max share extend size will be checked whereas for non-admin users,
max share size will be checked.
New extra_specs key is added to set max extend size of share
i.e.'provisioning:max_share_extend_size'
Closes-Bug: #1987253
Change-Id: I61e590ed1851e8fa15996dc61e8e17e9413a9d91
This change addresses some limitations for considering this
driver in a production deployment of OpenStack Manila.
Closes-Bug: #1867950
Change-Id: If45d1eabb33b57440c8946a56b5af39447514792
These doc enhancements still use the "manila"
CLI/shell utility. It makes it easier to
backport to older branches. A future commit
will update all documentation to use OSC.
Change-Id: I18c4ac2d4134314da9df0d3e0b7d45acafce2b22
Closes-Bug: #1941057
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
This should help new contributors have an easier
on-ramp to certain kinds of manila development.
Change-Id: I55a43cccec2f8a1987042398c9f8057a95f44d8f
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
Update the step for the user account as mentioned
in the official Infinidat documentation.
Signed-off-by: Alexander Deiter <adeiter@infinidat.com>
Change-Id: I3f733682c8805e6258c945c81ce012badaf80796
Fixed an issue in Infinidat driver to support host assisted migration.
And added new configuration options:
* `infinidat_snapdir_accessible` to configure access to the `.snapshot`
directory on the client side.
* `infinidat_snapdir_visible` to configure visibility of the `.snapshot`
directory on the client side.
Closes-Bug: #1992443
Signed-off-by: Alexander Deiter <adeiter@infinidat.com>
Change-Id: I29b51fcec28dd5110de6ad196ff8b67c875ce8fa
Share Server limits must be ignored in case the new share is
from a snapshot and same host as the parent, since they must
be in the same server.
Closes-bug: #1918845
Change-Id: I1c611f4a7f3590b571f75ceca17c2fc3d8f3ad7a
Incremented driver version to 1.1 and updated documentation
with SSL options, added by commit 52dac7619.
Closes-Bug: #1989283
Change-Id: Icc567a50b8498c06c2cfc76f6ae82731df63cafd
Signed-off-by: Alexander Deiter <adeiter@infinidat.com>
The override file now supports yaml format. While
JSON formatting is absolutely fine, the file suffix
".json" will confuse our tooling.
Change-Id: I01ce4ab3e879a8dbbc7377997f7e497f15c9b15e
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
Add a section about NeutronBindNetworkPlugin on shared file systems
network plugins doc resource.
Closes-Bug: #1617490
Change-Id: I4bdd2c04ce6ee05b7d9bc6526f9aa13d07803bb7
This change gives the Container driver the ability to create share
servers that span multiple subnets in the same availability zone, where
previously it was only possible to do so with one subnet per
availability zone. It also enables the driver to create new subnets on
share networks that already have shares exported on them.
Some relevant changes in the driver behavior:
- container creation is now separate from its start
- containers no longer use the default Docker network; instead,
dedicated networks are created (one for each subnet)
- fetch_container_addresses now returns a list of addresses
- find_container_veth, _get_veth_state, _get_corresponding_veth were
removed
- these new methods were written:
- start_container
- fetch_container_interfaces
- create_network
- remove_network
- connect_network
- disconnect_network
- get_container_networks
- get_container_veths
- get_network_bridge
- get_veth_from_bridge
- _setup_server_network
DocImpact
Depends-On: I7de9de4ae509182e9494bba604979cce03acceec
Partially-Implements: blueprint multiple-share-network-subnets
Signed-off-by: Eduardo Santos <eduardo.experimental@gmail.com>
Change-Id: I81a616b57c95508f30d872383f5c2d68718950d7
This change fixes the wrong instruction in admin guide which enables
ratelimit in the keystone_nolimit pipeline. To use a pipeline with
ratelimit, [DEFAULT] api_rate_limit should be set to True.
Change-Id: I0cfde1c5a18eeb6ace5bc96e728e58954d0ac046