Comment 4 for bug 1511747

firist thing there - 'floating range' parameter will not be update automatically if you create new network and will assign public role for it into network template. You should manually change this value in cluster settings - ['networking_parameters']['floating_ranges'] for 7.0 version.
But, here we have another issue. When we try to change this floating range to range belongs to 'everything' network we encountered following error there:
"Error uploading configuration: Floating address range 192.168.124.130:192.168.124.254 is not in public address space 192.168.123.0/24."

We get this message due to our validation approach in 'public' network identification:
https://github.com/openstack/fuel-web/blob/master/nailgun/nailgun/network/checker.py#L390-L391

We assumed that public network should have only constant name('public'), but in template's case it may have different name('everything' in our case).

I see two ways to fix an issue:
1. To document that it's not possible to set another name for public network then 'public' and we should have only one network with 'public' name for on nodegroup.
2. To introduce new meta parameter for network what will help us to identify public networks and verify floating range (seem like feature for me)