Ensure unit tests don't assume an IP address allocation strategy
These unit tests initially asserted sequential allocation of IP
addresses, even though they have no need to specifically assert
that a specific IP was allocated. This made it difficult to
change out the IP allocation algorithm in the future and made
these tests fragile and poorly isolated.
This change breaks the dependency these unit tests have on a
specific IP allocation strategy and isolates them from any
changes that may be made to the order in which IP addresses
are allocated on a subnet.
Reviewed: https:/ /review. openstack. org/303603 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=cbc15d2e1db 22fbefaac0a9736 3589aebf834b24
Committed: https:/
Submitter: Jenkins
Branch: master
commit cbc15d2e1db22fb efaac0a97363589 aebf834b24
Author: Ryan Tidwell <email address hidden>
Date: Fri Apr 8 14:12:01 2016 -0700
Ensure unit tests don't assume an IP address allocation strategy
These unit tests initially asserted sequential allocation of IP
addresses, even though they have no need to specifically assert
that a specific IP was allocated. This made it difficult to
change out the IP allocation algorithm in the future and made
these tests fragile and poorly isolated.
This change breaks the dependency these unit tests have on a
specific IP allocation strategy and isolates them from any
changes that may be made to the order in which IP addresses
are allocated on a subnet.
Change-Id: Idc879b7f1e6496 aa96b4f7ae6c3ea ca6079bdcac
Partial-Bug: #1543094