Updated openstack/openstack
Project: openstack/nova  d73d62c2616a44cc2e7369146befda4faf4e993c
null
Deprecate instance_get_all_by_filters() from conductor

This deprecates the instance_get_all_by_filters() method from
conductor, which is no longer used.

This also removes a test that was mocking the conductor method,
but that really tests nothing at all. Perhaps a new test to ensure
that the period=0 case is handled properly is in order, but this
test definitely wasn't doing that.

Related to blueprint compute-manager-objects-juno

Change-Id: I1e7bc19296d1773bbc2f5f9e77a1faf0e6ac1fe6
Updated openstack/openstack
Project: openstack/nova  16f4c5bf9754f67fc095ae5525dcd357a99509d6
null
Deprecate instance_get_active_by_window_joined() from conductor

This deprecates the instance_get_active_by_window_joined() method
from conductor which is no longer used.

Related to blueprint compute-manager-objects-juno

Change-Id: Ia9ce0cf49180806da64cc034ad12ddf2b3f1c424
Updated openstack/openstack
Project: openstack/neutron  3e7d07d9a5a8f7a7f2458c87c86dfd20e076e77a
null
Add 2-leg configuration to Radware LBaaS Driver

Radware's load balancer currently supports three network interfaces.
Prior to this code addition, the configuration of those three
interfaces was: one interface for management, one for high
availability backup, and one for load balancing servers where the
IP that the outside world sees (VIP) and the IP that the servers
respond to (PIP) are identical.

This change adds a new "2-legged" configuration: one interface for
management, one interface for a VIP network, and one interface for the
PIP and the high availability backup network.

During VIP creation, the LBaaS driver detects if the incoming
configuration is "2-legged" by comparing VIP and PIP networks.  If they
are different it allocates a new port on the PIP network in order to
obtain an IP address for the PIP and names that port after its
associated VIP ID.  vDirect is then directed to create a load balancer
with the PIP network also used as the HA network instead of using the
vDirect container's default HA network configuration.

During VIP deletion, the LBaas driver detects if a port for the PIP
had been previously allocated by searching for and deleting port names
that map to the VIP ID.

Change-Id: Ifb93159c654f16958842f646c119479c465230f9
Closes-Bug: 1268728
Updated openstack/openstack
Project: openstack/cinder  ee434fbad271e02aa92dbe200448c6d723b6d4e7
null
Fix handling multiple WWPNs on preferred FC node

There was a bug in the code that checked to see if the
appropriate WWPN for a preferred node was available on the storage
host in intialize_connection.  It was assumed that there would only
ever be one preferred WWPN.  The code just checked to see if the list of
preferred WWPNs was in the list of available WWPNs.  This would only work
if all of the WWPNs were available on the storage host.  This resulted in
volumes not being able to be mounted when they should have been
available.

This fix changes the check of the preferred WWPNs to check each
item in the list until one is found.  The first one found is used
as the target WWPN.  If no match is found, the old default behavior
of selecting the first available WWPN is used.  I have added a
warning message for this case as it is quite possible that this
won't work in the user's environment as was the case that uncovered
this bug.

Note that this change is only relevant for systems that are not using
multipath as systems that use multipath don't choose one WWPN, they
just send the whole available list back.

Change-Id: I8d3239da24a8f9fbd8309ba5c90b05b29a068754
Close-bug: 1308298
Updated openstack/openstack
Project: openstack/neutron  a017a0be80f5c90e5d52a6156d1a19976b96b849
null
IBM: set secret=True on passwd config field

This should carry secret=True to avoid being logged as clear text.

Change-Id: I7d15b9648b3a037589405b9ca9d26aae4a834f15
Closes-bug: 1311943