tree 37b3bef57300634ff15209dafb9e8082d0e37004
parent 6a341ef6166a25a8a18472856df983c6456d6d47
author Matthew Treinish <mtreinish@kortar.org> 1427466345 -0400
committer Matthew Treinish <mtreinish@kortar.org> 1427483424 -0400

Handle fixed_network edge cases gracefully

When we added support for using the fixed_network_name config option to
specify the network to boot with in a multi-network env a couple of
configuration edge cases were not taken into account. First the case
of misconfiguration was not handled at all this would cause an ugly
IndexError exception to be raised because no matches were found for
the name specified in config. The other was since the default config
option was set to 'private' and fixed network name is always used when
configured the default for single network environments broke if the
single network. This commit addresses these by removing the default
value for fixed_network_name (and making the help more clear) and
having fixed_network_name handle the misconfiguration case more
clearly by raising an InvalidConfiguration exception.

Change-Id: I06ac0605a1a7e35d1af9a93a3bfc387a78f8be1c
Closes-Bug: #1437328