[PDB-1263] Round robin support for EC2 subnets Created: 2015/02/25 Updated: 2015/06/04 Resolved: 2015/04/23
|Fix Version/s:||PDB 2.3.5|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|Epic Link:||QA/QEng Phase 1|
Using VPCs requires that we pin our instances to a specific subnet which also implies a specific availability zone. Under normal conditions this is fine, but when one availability zone is at capacity, it results in errors like the one below:
If we were not specifying an availability zone, it would have just picked one of the other zones that were under capacity (and we would have not seen the error). Since we need to have the subnet pinned in order to use VPCs Ken Barber has created a subnet in each of the zones. If we were able to specify a list of subnet ids and beaker was able to roll to the next subnet when one failed, it would give us the same ability as not specifying a vpc/subnet.
This change involves changing Beaker to support a list of subnets, the failover code and updating PuppetDB to take advantage of that new subnet list feature.
|Comment by Rob Browning [ 2015/04/15 ]|
Currently waiting for preliminary team review.
|Comment by Rob Browning [ 2015/04/22 ]|
Issued initial upstream pull request: https://github.com/puppetlabs/beaker/pull/791
|Comment by Ken Barber [ 2015/04/23 ]|
I'm guessing this is meant to be "Ready for merge" not "Needs information" since its in review by the beaker team now?
|Comment by Wyatt Alt [ 2015/05/06 ]|
I'm removing 2.3.x as a fix version here. I'll add it back in a bit later.
|Comment by Wyatt Alt [ 2015/05/07 ]|
replacing 2.3.x as the fix version.