UI doesn't reflect state of waiting for floating IP to be assigned/unassigned
Problem/Opportunity Statement
- After user initiates a floating IP assign/unassign action, there is a delay in a floating IP actually getting assigned/unassigned to/from a server. In the meantime, the UI looks like nothing happened when the assign/unassign button was pressed.
- This is a specific case of a more general problem where the OpenStack API sometimes takes a while to reflect the result of a user-requested asynchronous action. How should we model the circumstance where an action has been requested and is in progress? How should the UI reflect this circumstance?
What would success / a fix look like?
When user clicks the assign/unassign button, it is apparent in the UI that an action has been initiated and is in progress. When the assignment/unassignment is complete, the UI reflects this within a reasonable period of time (<1 minute).
We have had to solve this already (see server exoProps "deletionAttempted" and "targetOpenstackStatus"). Is there a better general solution that would apply both there and here?