nailgun does not allow to set floating IP range from non default nodegroup

[Aleksandr Didenko]

If you use nodegroups then nailgun wont' allow to set floating IP range from non-default nodegroup. Thus can deploy network/controller nodes only in default nodegroup. If you deploy controllers in non-default nodegroup then public network for your OpenStack VMs will be non-routable.

Steps to reproduce:
1. Create multirack env with 2+ nodegroups
2. Put controllers in non-default nodegroup
3. Download network_1.yaml and try to change floating IP range to the public network of non-default nodegroup
4. Check results.
5. Deploy changes
6. Run OSTF
7. Check results.

Expected results:
4 - floating IP range changed to non-default public cidr
7 - OSTF passed

Actual results:
4 - nailgun rejects network_1.yaml
7 - OSTF failed on tests related to floating IPs

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/235956

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/235956
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=2c0f51b4495b571dc26b8911ea8f7ad8c394bc6d
Submitter: Jenkins
Branch: master

commit 2c0f51b4495b571dc26b8911ea8f7ad8c394bc6d
Author: Nikita Koshikov <email address hidden>
Date: Fri Oct 16 17:30:37 2015 +0300

    Lookup parent network for floating range by CIDR

    Floating range was always considered as subrange within Public network of default node group.
    Now, lookup of parent network for floating range by CIDR is implemented.
    So, floating range may match any Public network of a cluster.

    Co-Authored-By: Aleksei Kasatkin <email address hidden>

    Change-Id: I7d8b0c1db0835aec9e035177e076e40f4e793902
    Closes-Bug: #1502829

[Dmitry Belyaninov (dbelyaninov)]

Verified on ISO 361 by integration/test_orchestrator_serializer.py test

[Denis Meltsaykin (dmeltsaykin)]

Won't fix for 7.0 as it's a feature.