The autosupport functionality of the NetApp cDOT driver is not working
with Python 2.7.12, the default in Xenial. Root cause is a deep copy
of the controller connection context, which includes some SSL context
stuff that doesn't play well with copy.deepcopy. So we can do a shallow
copy instead.
Change-Id: Ia2adc4ce27834e384e6d994fcb012ebf1d97c85c
Closes-Bug: #1621260
Currently, huawei driver will use the "AllocType" configuration
or default "thick" type to create share, if "thin-provisioning"
not specified in share_type, but scheduler default uses thin
type in this situation, so huawei driver isn't consistent with
scheduler.
This patch removes the "AllocType" configuration from huawei
driver configuration file and default use "thin" type if
"thin-provisioning" not given.
Depend on change I238a7962425ea35c356c5ed2e31b8f68462b3769.
DocImpact
Change-Id: I5b7128657e089113da44bc862e9c864de2ec59b2
Closes-Bug: #1609718
Change http://review.gluster.org/14931,
debuting in GlusterFS 3.7.14 has changed the
XML output emitted by the gluster command
line interface. Here we implement parsing
for the new variant as well.
Change-Id: Ia9f340f1d56c95d5ebf5577df6aae9d708a026c0
Closes-Bug: 1609858
Currently 'provisioned_capacity_gb' is expected from
the drivers as part of capability reporting.
If driver does not provide it, it defaults to 'allocated_capacity_gb'.
But if driver does not provide both 'allocated_capacity_gb' and
'provisioned_capacity_gb' then 'provisioned_capacity_gb' defaults to 0.
Which affects later calculation of 'provisioned_ratio'.
Hence fixing it by summing up sizes of all the shares of
that host and taking that as 'provisioned_capacity_gb',
in such case.
Change-Id: I844d176eb6f0f5e7b0eb3cbd66c4b413b6757f51
Closes-Bug: #1606691
In order to support automatically updating the release notes when we
create stable branches, we want the pages to be in a standard order.
This patch updates the order to be reverse chronological, so the most
recent notes appear at the top.
Change-Id: Ib364dcc8eb31275a31c83b68d7914263b183e393
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Generic driver updates routes on host according to the tap
interfaces created for use by share servers. That code
should be within a lock to prevent a thread failing to delete
a route previously listed and already deleted by another thread.
This change moves an existing lock to the function that
performs route changes while also covering the function
that had the lock before.
Closes-bug: #1617461
Change-Id: I798e5d9b0bc9ebefc8661d0ade720c60303cf484
Currently, when we set share-state to 'manage-error', share-size
is set to 1 at all places except this one. Which results in error
logged during delete-share, w.r.t quota.
This fix sets share-size to 1 when share state is
set to 'manage_error'.
Change-Id: I96343ffd4f273b01c0376713717cdc89ea9a873a
Closes-Bug: #1587636
Currently, Manila api-ref is configured with logABug feature.
When users click "Report bug" button, it leads to "openstack-manuals"
which is default. We should change it to "manila".
Change-Id: I15d9ce4cc6f9648f49f6ad66de766aa55cab6cbb
NetApp cDOT SnapMirrors cannot be established from one
FlexVol to itself, however, the cDOT driver issues ZAPIs to
delete/release SnapMirrors between the volume and itself.
Avoid this behavior and add unit test coverage.
Change-Id: I8ca096dfe8463511595a67cbea3ca31a80c0e5fb
Closes-Bug: #1578328
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
Tempest 12.2.0 was recently released and manila tempest plugin runs
just fine with it.
Update tempest in our CI to use tempest at the commit corresponding to
this tag.
Change-Id: Ia00670a5cf0b52a41fa0d3cd9a82cd81f7802155
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
