In the capabilities section of capabilities_and_extra_specs.rst,
the description of dedupe and compression all say that drivers
cannot report to the scheduler both support and non-support,
like [True, False].
But since Mitaka, this kind of specifying is allowed.
So change the doc contents to fit the actual logic.
Change-Id: Ie871abc49bd1bc58566111f85d89228046865b5c
Closes-Bug: #1621707
Current implementation of share migration works only if we use
local shell executor. So, refactor approach for it to make work
with both shell executors - local and remote (SSH).
Change-Id: Ibe31bf52006040ea26badfa7236ed67559f7aded
Closes-Bug: #1620502
Neutron ML2 mechanisms allows multiple network segments. A net-show
call with a multi-segment setup won't return a single network-type
or segmentation id. Instead it returns a list of it with a certain
hierarchy.
Co-Authored-By: Daniel Gonzalez <daniel@gonzalez-nothnagel.de>
Change-Id: I3570752920d897c11cacb9e4a0b0d012ae2ce13a
Partially-Implements: bp manila-hpb-support
In order to do port binding of physical ports it must be
specified which switch and switch_port are used. It is
expected for HPB that the neutron driver handles the
logic of dependent core switches.
Co-Authored-By: Daniel Gonzalez <daniel@gonzalez-nothnagel.de>
Change-Id: I08a889a3bff6289397aaed59846e893ba5df36e3
Partly-implements: bp manila-hpb-support
Share drivers to support NexentaStor4 and NexentaStor5 via
NFS protocol. Supports all minimal required features.
Implements: blueprint nexenta-manila-driver
DocImpact
Change-Id: Ib8b8525397626162968458ec837f9239ff5dbb2b
This change implements the 'update_access' method within the Windows
SMB driver with respect to the semantics specified in the base driver.
The 'allow_access' and 'deny_access' methods are now removed.
Closes-Bug: #1618556
Change-Id: I2b52c48331a2c94ec4dcf34779cac5d1b73a121b
When setting access rules, we first set the rules per share,
execute the cmdlet which will update the filesystem ACLs based on
the share ACLs, and then use icacls to set filesystem ACLs again.
This is redundant and the last step can be dropped.
Change-Id: I3a5db71c697605e74243df0cf1d184d0b0fd4e8e
Add support of share migration feature to ZFsonLinux driver.
Implements BP zfsonlinux-share-migration
Change-Id: If9e1fec9a6d4f96d2bb5c176c6249fafc7e3e891
This patch adds a 'new_share_type_id' parameter to Share Migration,
where the destination share can be provisioned under a different
share type of choice.
Host-assisted migration handles it by creating a totally new share,
as before.
Driver-assisted migration handles by creating the destination
instance model with the new share type, the driver is responsible
for making the necessary changes to satisfy the provided model.
In order to accomplish this, a database change was required,
transferring the 'share_type_id' field from the 'shares' table
to the 'share_instances' table.
APIImpact
Partially implements: blueprint newton-migration-improvements
Change-Id: I3200eaaa5b66d9b8ce1cbd16c1658db8516c70fb
3PAR driver so far did not support multiple pools per backend.
This patch aims to allow support for multiple pools per backend.
The configuration now accepts multiple pool entries per backend.
In manila.conf, hpe3par_fpg was used to represent one pool (FPG in
terms of 3PAR) under a backend. Now, hpe3par_fpg can be used multiple
times within a backend, each entry will represent a pool (FPG name).
Sample configuration to supply pools 'testfpg' and 'sharenetfpg':
hpe3par_fpg = sharenetfpg, 10.50.158.8
hpe3par_fpg = testfpg, 10.50.158.7
Note that the configuration now also accepts IP address of share
server. 3PAR supports up to 4 IP addresses per share server. So the
format to supply multiple share server IP addresses per pool:
hpe3par_fpg = fpgname, IPaddress1, IPaddress2, IPaddress3, IPaddress4
If the share server is already setup and configured with IP address,
it need not be passed with hpe3par_fpg.
When DHSS=True, the format remains same as above, except the IP
address of share server is silently ignored if provided.
Obsoletes: hpe3par_share_ip_address from config
Release note added.
Change-Id: Ic08452f3ddf6b7b2f2dc1ba5ee32b4ebe5ae2614
Implements: blueprint hpe3par-pool-support
At Austin 2016 summit there were several improvements to
Share migration feature discussed. This patch implements
these changes.
Changes are:
- Added 'Writable' API parameter: user chooses whether share must
remain writable during migration.
- Added 'Preserve Metadata' API parameter: user chooses whether
share must preserve all file metadata on migration.
- Added 'Non-disruptive' API parameter: user chooses whether
migration of share must be performed non-disruptively.
- Removed existing 'Notify', thus removing 1-phase migration
possibility.
- Renamed existing 'Force Host Copy' parameter to 'Force
Host-assisted Migration'.
- Renamed all 'migration_info' and 'migration_get_info' entries to
'connection_info' and 'connection_get_info'.
- Updated driver interfaces with the new API parameters, drivers
must respect them.
- Changed share/api => scheduler RPCAPI back to asynchronous.
- Added optional SHA-256 validation to perform additional check if
bytes were corrupted during copying.
- Added mount options configuration to Data Service so CIFS shares
can be mounted.
- Driver may override _get_access_mapping if supports a different
access_type/protocol combination than what is defined by default.
- Added CIFS share protocol support and 'user' access type
support to Data Service.
- Reset Task State API now allows task_state to be unset using
'None' value.
- Added possibility to change share-network when migrating a share.
- Bumped microversion to 2.22.
- Removed support of all previous versions of Share Migration APIs.
APIImpact
DocImpact
Implements: blueprint newton-migration-improvements
Change-Id: Ief49a46c86ed3c22d3b31021aff86a9ce0ecbe3b
This patch consolidates NFS file system creation
and share creation in one rest call.
Change-Id: I513ec9d4bd54e9c741caed4e94e115b0fe44dd0f
Closes-bug: #1618824
When an exception is caught and rethrown,
it should call 'raise' without any arguments
because it shows the place where an exception
occured initially instead of place where
the exception re-raised
Change-Id: I7e11d11ee07fcc6e149d1349e4aba9f86b890c49
Closes-Bug: #1616696
By default, when a Windows SMB share is created, 'Everyone' will
have read access.
This is a problem, since we call 'Set-SMBPathAcl', which will apply
the share ACE at the filesystem as well. This means that anyone
that can log in to the share server will have read access to the
share.
We'll avoid this by granting read access to the 'NULL SID' when
creating the share, avoiding the default access to 'Everyone'.
Closes-Bug: #1612746
Change-Id: I913a887f24db7f1354008aacebcd0f477887aeef
Some of tests use different method of assertTrue(isinstance(A, B))
The correct way is to use assertIsInstance(A, B) provided by testtools
Change-Id: Ie21fb409edf558409aa4bf5dfe59893c5b544aa8
Tempest tests were not appropriate for driver-assisted migration,
so this was fixed.
Also, improved docstrings and fixed workflow for drivers when
implementing 2-phase migration to be accurate with tempest and
handle AZs, which were previously locked to the source share's
AZ.
Driver-assisted migration now creates an additional
share instance to better handle and support driver methods.
Updated allow_access and deny_access APIs to allow users to mount
migrating shares before issuing 'migration-complete'.
APIImpact
Closes-bug: #1594922
Change-Id: If4bfaf7e9d963b83c13a6fea241c2eda14f7f409
Manila HNAS driver splits the path to manage a share by ':', so when
passing a path with two colons the last part is ignored, it causes the
possibility to manage a share twice. For example:
manila manage --name test1 --share-type hds ubuntu@hnas#Hitachi nfs
172.24.49.26:/shares/f5b21612-9841-42c8-bec4-ca32ba70a9ae
and
manila manage --name test2 --share-type hds ubuntu@hnas#Hitachi nfs
172.24.49.26:/shares/f5b21612-9841-42c8-bec4-ca32ba70a9ae:1
Changing the split to search for ':/shares/' prevents a share to be
managed twice.
Change-Id: Ie97f749d7093db69a757db7c04041f6f649c7ce9
Closes-Bug: #1613683
In Scenario job, tests consist of VMs mounting shares
provided by share servers.
Admin network is used by share migration tests and is
by default used in other tests as well. Previously it
used the same network address range as tenant networks
(used by VMs) and there was no conflict.
Recently some unknown change broke connectivity between
VMs and share server in scenario job. It seems as there
is now a conflict between those network addresses ranges.
This patch changes the admin network address range,
removing the existing conflict.
Closes-bug: #1616115
Change-Id: I5bdb70cae4eab2930f3f559a621643ad732909bb
Existing 'ip route list proto kernel match <subnet>' may match
subnets different than the one specified when specific CI
nodes are selected to run CI job. This patch changes the command
to prevent unrelated subnets from being listed.
Change-Id: Ibb59a8098a1b86429651c25a3b641eda9b44c8fa
Depends-On: I62da6f14eb53c6d3c74442a626b7ea0fd37a7cad
Closes-bug: #1617417
This patch set modifies lines which are importing objects
instead of modules. As per openstack import guide lines, user should
import modules in a file not objects.
http://docs.openstack.org/developer/hacking/#imports
Change-Id: I4e5a3a2637594e95b1d9e870752bc6ca690144af
