-
Notifications
You must be signed in to change notification settings - Fork 12
Ephemeral IP checkbox on instance create form #1097
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
So if you can't specify a pool, this essentially has to be a checkbox meaning "give me an ephemeral IP"? |
That would be the simplest way to implement this at the moment, I think. That wouldn't work for a Floating IP, since you'd need to name the object, but that's down the line. I was hoping to give the fullest picture, so y'all could decide what makes sense in the short- and longer-term. |
Checkbox would go under Advanced > Networking and default to checked. This bit would be populated or empty based on the checkbox value. console/app/forms/instance-create.tsx Line 213 in 0469280
|
Based on the discussions we had, here is the Figma file with relevant designs: |
Beginning with oxidecomputer/omicron#1458, the control plane now has the concept of an external IP address for guests. This is a publicly-visible address that allows inbound connections, such as SSH, from outside the rack into the guest. (That's distinct from the IP addresses that provide outbound connectivity, which don't appear in the API.)
These addresses are associated with the primary network interface, and are shown in the console as part of #1070. We also need a way to request such an address in the web console. The parameters for describing this address are currently defined here. We currently support ephemeral addresses, optionally specifying the name of an IP Pool from which to draw the address. (Ephemeral addresses only live as long as the instance, and can't move around between different objects.) It's not clear yet how to specify the pool, since that's currently a top-level / operator / global resource (discussed in RFD 288), so it might be better to leave that off for now.
Though they're not yet implemented, Floating IP addresses will also be supported here. (Implementation tracked in oxidecomputer/omicron#1334.) Those are separate, named API resources scoped to a VPC, which can be created independently from instances. In that case, the name of the Floating IP will be specified in the API request (it'll be looked up relative to the VPC of the primary network interface, most likely).
The text was updated successfully, but these errors were encountered: