Change default from IP pools silos list (or send user to silo IP pools list)

[askfongjojo]

I should have noticed earlier that the UI doesn't give you the option to set the pool as default. I am also unable to set it after linking the silo. The feature is only available in the API/CLI at this time.

The main issue here is that operator may think that their IP pool setup is done via the UI but user would hit the error "no default IP pool" at instance provisioning time.

[david-crespo]

Change default is available on the silo IP pools tab. It's definitely confusing that it's not available on the silos for IP pool list. I think we could make it work, but it will take a little design. The reason I didn't include it on that page (even though there is a "is default for silo" column) is that on that page, you don't see the other pools for that silo, so you don't necessarily know which one you're removing default on. But I think that could be fixed by putting it in the confirm modal, like "Are you sure you want to make pool A default for silo X? Pool B is currently the default and it would stop being the default".

[askfongjojo]

Ah sorry, now I am remembering....

So perhaps the easiest thing to do here is add a note about the need to set a default pool and, optionally, provide a link to land on the silo UI directly. The note will perhaps need a different color (or other means) to distinguish it from the documentation text that is already there.

[askfongjojo]

A customer hit the "missing default IP pool" error while creating the first instance in the silo. He subsequently found the place to link ip pool to the silo with our guidance. His suggestion is to automatically make the first IP pool created linked to the silo to be the default pool to avoid the one step that's easy to miss.