Create a tox environment for running the unit tests against the lower
bounds of the dependencies.
Create a lower-constraints.txt to be used to enforce the lower bounds
in those tests.
Add openstack-tox-lower-constraints job to the zuul configuration.
See http://lists.openstack.org/pipermail/openstack-dev/2018-March/128352.html
for more details.
Change-Id: I59d376c6da1afc0847a25893d80ca9a210bbe64b
Depends-On: https://review.openstack.org/555034
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Nova needs to check the architecture drivers like
"_connector_mapping_linux". To avoid accessing
private attribute, this adds a new function
"get_connector_mapping"
Change-Id: I66f37aace797eca54356b4aaf1bc1b655567c1e2
iscsiadm exits with code 21 (ISCSI_ERR_NO_OBJS_FOUND) when no nodes
exist. We must accept this as an empty result when attempting to get
node startup info, instead of producing a ProcessExecutionError.
Change-Id: I55f4b3b075bd7779e96777dee64bf577c45fddf1
Closes-Bug: 1756206
Removing the LinuxFibreChannelPPC64 class override, as the
rescan host functionality is now in sync with the base class.
Change-Id: I2b4a8a210c68280bed55cadbc7e4e3137fa5765d
Closes-Bug: 1754303
Implementing necessary mathods and rescaning storage
as necessary to support extending ScaleIO volumes
which are currently attached.
Change-Id: Icb9fc4fe1c16c34d8de9287046045d0837b7e80e
This change ensures that the retrieved disks are claimed by the
MPIO service, when multipath is requested.
At the same time, we're attempting to retrieve the disks only after
connecting all the requested targets.
Change-Id: I5e9e01d42aee1cedd59e620be35fe98b2085e5e9
Related-Bug: #1694671
This change will ensure that the connector attempts to retrieve
the according disk paths by using its SCSI VPD unique id when not
included in the mappings reported via the HBA API.
At the same time, if multipath is requested, we're ensuring that the
disk was already claimed by the MPIO service before reporting it back
to the caller in order to avoid situations in which the disk suddenly
disappears.
Depends-On: I86d953d000e6d0244e8e8f2aaf2cbd76305cb63b
Closes-Bug: #1694671
Change-Id: I0cb96c46ca75be3836981852e22437db63910f96
This patch enable extensions:
-[H204] Use assert(Not)Equal to check for equality.
-[H205] Use assert(Greater|Less)(Equal) for comparison.
Change-Id: I89efcab9993fcbb187249e32712fe00b86715e3a
The device path to a block device on Ubuntu using a ds8k LUN
differs from the device path for other storage systems.
This patch adds the new device path as third possibility.
Change-Id: I92f1e5a2c7203af6c01c4742067ced16a840eb04
In the case that a compute host with multiple NICs can be connectted to
iscsi storage network, we expect the storage traffic only be
transimitted via storage NIC. This need to define an custom iface and set the
iface.net_ifacename value to the storage interface name.
Unfortunately, the current iscsi connector does not support to use a
custom iface. The _validate_iface_transport will change it to default.
After add tcp to the supported_transports, it is possible to use a
custom iface.
Please get the details as below:
1. CMP001 has three NICs: NIC1 is for management network, NIC2 is
for tenant network, and NIC3 is for storage network. NIC3 can access
storage device via layer 2 network. And NIC1 can access storage device
too, but it can only access via layer 3 network. We hope all the storage
traffic only be transimitted via NIC3, because they are in the same
layer 2 network.
2. Get the NIC3 MAC:
fa:16:3e:79:fd:63
3. Add new iscsi iface:
# iscsiadm -m iface --op=new -I tcp.fa:16:3e:79:fd:63
# iscsiadm -m iface -I tcp.fa:16:3e:79:fd:63 --op=update
-n iface.hwaddress -v fa:16:3e:79:fd:63
4. Edit nova.conf, and change iscsi_iface value:
iscsi_iface = tcp.fa:16:3e:79:fd:63
5. Restart nova compute service:
# systemctl restart openstack-nova-compute
Without this change, _validate_iface_transport will change the
custom iface tcp.fa:16:3e:79:fd:63 to default due to it cannot find tcp
transport.
According to this change, we should have a corresponding change to the
nova docs, here is change to nova
https://review.openstack.org/#/c/524443/
Change-Id: I85a62cb6e7f8d8982e97e792d647d38ce5641060
Closes-Bug:#1722432
The pv_list of LVM object actually wanted to be a list of dict of
physical volumes' info, but in the routine of creating a new vg,
we assign a list of physical volumes' name to it, which is unnecessary,
and also confuse people.
Change-Id: I5f74200e6df954258f261a30e9f5a5b56c6def2f
python-subunit is not used directly anywhere
and it is dependency of both testrepository
and os-testr
(probably was used by some tox wrapper script before)
Change-Id: I3f54fdbe876b2dd052d15c90dfafecd8baa03c45
The Windows SMBFS connector returns VHD/x image paths exposed by
the Cinder SMBFS volume driver.
This is fine for Nova, which will just use those image paths when
attaching volumes to instances.
The issue is that during backups/migrations, Cinder expects a raw
disk path, opening it and attempting to read volume data.
This change adds an argument to the connector init method, allowing
a raw disk path to be explicitly requested. If this argument is set,
we'll mount the image and bring the disk offline, returning the
raw disk path. This will allow direct IO operations to be performed
against the volume.
Related-Blueprint: windows-smb-backup
Change-Id: I20f791482fb0912772fa62d2949fa5becaec5675
The Windows connectors do not include the 'device_info' argument
in the 'disconnect_volume' method.
This wasn't an issue for Nova as the Hyper-V driver doesn't pass
this argument, yet Cinder does pass it, which will lead to an
exception.
This change adds the missing argument, defaulting to "None" so that
it won't break the Nova Hyper-V driver.
Change-Id: Iaf8b57c97afc393862a61a7338a35f008b65c8c1
Closes-Bug: #1738390
We do not need tox_install.sh, pip can handle constraints itself
and install the project correctly. Thus update tox.ini and remove
the now obsolete tools/tox_install.sh file.
This follows https://review.openstack.org/#/c/508061 to remove
tools/tox_install.sh.
Change-Id: I43828f47711118eba8d835222586db4faac93180
os_brick updates node.startup values from default value to
"automatic" when it creates iscsi connection.
But existing target's node.startup values will be reverted from
"automatic" to default value in creating iscsi connection process
if multipath is used.
When using multipath with a discovery type of backend, the
"iscsiadm -m discovery -t sendtargets -p ..." command will recreate
all target information of specified node.[1] node.startup value wil
be reverted to default value of existing targets by recreating.
As a result, "automatic" targets and default value targets will be
mixed on the host.
So this patch recovers node.startup values after discovering.
[1]
This behavior was explained in following page:
https://github.com/open-iscsi/open-iscsi/issues/58
Change-Id: I30b736ae3b916f77fc0778f5364c5f6ed6fecc60
closes-bug: #1670237
Allow clients to attach and detach Cinder volumes stored on
a StorPool cluster.
Change-Id: I33cfd7ab9a1d201f6c49357cacb4a809453b7201
Implements: blueprint brick-add-storpool-driver
Doug Hellmann
Zuul
Patricia Domingues
OpenStack Proposal Bot
iain MacDonnell
Chhavi Agarwal
Eric Young
Lucian Petrut
Luong Anh Tuan
OpenStack Release Bot
Andreas Scheuring
Jack Lu
wang yong
Eric Harney
melissaml
Andreas Jaeger
Rikimaru Honjo
Peter Penchev
wanghongxu