Dealing with the current Floating IP Behavior #582

The current Floating Ip behavior has two downsides:

1. When adding a floating IP to a VM there is no check, whether the floating IP is already associated to another VM, this makes it possible to "steal" the floating IP from another VM
2. When removing a floating IP from a VM there is no check, whether the correct IP was specified, because the the given server name or id is not checked.

There are many ways to deal with this behavior:

1. Talk to upstream about the whole situation, that in both cases, the association is not checked
2. Talk to upstream about the CLI command, that may need to be adjusted to better reflect the workflow (especially for the removing part)
3. Talk to upstream about the documentation of floating ip usage
4. Maybe have a guide / information about this behavior in the scs docs