Comment 3 for bug 1522760

I'm afraid, that there's no way for backend to guess which exactly public network user wants to use for floating IPs. So it's impossible to prepare proper meta.floating_range_var parameter. Right now backend sets this parameter to 'floating_ranges' for ALL public networks.

So I see two options here:
1) Validate floating IP range in UI against ALL networks that have meta.floating_range_var=='floating_ranges'
2) Remove floating IP range validation from UI and let backend handle it (in case of wrong range, backend will respond with error message)

Forwarding this back to UI team.