cloud-specific configuration of floating IP address behavior
Problem/Opportunity Statement
With !441 (merged), Exosphere attempts to automatically determine whether a floating IP address needs to be created and assigned to a new instance. A cloud operator may wish to override this behavior for Exosphere users of their organization's cloud: to always or never create a floating IP by default.
What would success / a fix look like?
clouds
JSON configuration object could give deployer the option to specify how to deal with public IP addresses for new instances: whether a floating IP is required, optional, or even supported at all. This could determine how Exosphere exposes floating IP address-related actions throughout the app.
Or, this may be a bad idea / proliferate unnecessary configuration options, and we should just build the automatic detection to do the right thing in most/all cases.