First-class support for non-floating public IP addresses in server details view
Problem/Opportunity Statement
!441 (merged) introduces support for creating and managing instances that don't have a floating IP address. These instances may still have a publicly routable/accessible fixed IPv4 address, but the server details view doesn't currently recognize this IP as publicly accessible.
What would success / a fix look like?
- if an instance has a fixed IP address in publicly routable (outside RFC 1918) space, then attempt to use/expose interactions (e.g. Guacamole-based interactions and native SSH) at this fixed IP address
- server details view should display an instance's public (non-RFC 1918) IP address most prominently, regardless of whether that IP address is fixed or floating