Instances will not be able to reach internet and will not be reachable from public/private networks IF floating range configured as a part of `public` network of rack with no controllers. So in this case correct to configure float range as part of public net of rack2.
Given multirack environment:
Rack01 (default):
* slave01 = compute
* slave02 = cinder
Rack02 (custom):
* slave03..05 = controllers
Instances will not be able to reach internet and will not be reachable from public/private networks IF floating range configured as a part of `public` network of rack with no controllers. So in this case correct to configure float range as part of public net of rack2.
There few issues with this: /docs.mirantis. com/openstack/ fuel/fuel- master/ operations. html#configurin g-multiple- cluster- networks
1. Issue are not described in our documentation: https:/
2. Fuel are not validate this case BEFORE deployment (both on UI or backend)