Previously, the Data Service allowed only 1 IP to be specified
for the 'data_node_access_ip' config option, which prevented
Host-assisted Share Migration to be successful on a combination
of backends that include IPv6 and IPv4 export locations.
To fix this, we are adding a new config option and deprecating
the old one. The new one is named 'data_node_access_ips' and
accepts a list of IPs. All IPs included in this list should
correspond to interfaces on the node running the Data Service
and will be allowed access during Host-assisted Share Migration.
Additionally, we are improving the responsiveness of the
Host-assisted Share Migration by using exponential waiters
instead of polynomial. Those waiters are used when managing
resources created by Share Migration.
Reviewed: https:/ /review. openstack. org/541478 /git.openstack. org/cgit/ openstack/ manila/ commit/ ?id=53ec28a1caa 2555917974c8e0e b0efffdf58dfdb
Committed: https:/
Submitter: Zuul
Branch: master
commit 53ec28a1caa2555 917974c8e0eb0ef ffdf58dfdb
Author: Rodrigo Barbieri <email address hidden>
Date: Thu Feb 1 17:08:41 2018 -0200
Fix Host-assisted Share Migration with IPv4+IPv6
Previously, the Data Service allowed only 1 IP to be specified access_ ip' config option, which prevented
for the 'data_node_
Host-assisted Share Migration to be successful on a combination
of backends that include IPv6 and IPv4 export locations.
To fix this, we are adding a new config option and deprecating access_ ips' and
the old one. The new one is named 'data_node_
accepts a list of IPs. All IPs included in this list should
correspond to interfaces on the node running the Data Service
and will be allowed access during Host-assisted Share Migration.
Additionally, we are improving the responsiveness of the
Host-assisted Share Migration by using exponential waiters
instead of polynomial. Those waiters are used when managing
resources created by Share Migration.
Closes-bug: #1745436
Partial-bug: #1708491
Change-Id: I1c0b7621ae8192 f75f691987b185a 4fc6a7228ce