UI does not allow to specify floating range from non-default node group

[Aleksandr Didenko]

In 8.0 it's possible to deploy controllers in non-default node group, thus it's possible to specify floating IP from public network of such non-default nodegroup. Nailgun API allows it, but UI shows error (see screenshot).

How to reproduce:
1) Create a new env
2) Create new network node group
3) Specify different CIDRs for all networks in both node groups
4) Go to "Neutron L3" tab and specify floating IP range that matches public CIDR of non-default node group

Expected result:
It's possible to save floating IP range, no errors/warnings.

Actual result:
It's not possible to save floating IP range, 'Invalid IP range start' error is shown (see screenshot)

VERSION:
  feature_groups:
    - mirantis
  production: "docker"
  release: "8.0"
  openstack_version: "2015.1.0-8.0"
  api: "1.0"
  build_number: "243"
  build_id: "243"
  fuel-nailgun_sha: "1b6ae6c7fd4766f4a57d90afc1cd0f2315255a42"
  python-fuelclient_sha: "91474bd8c526f4f536ab13368feb4a5c1b84d185"
  fuel-agent_sha: "660c6514caa8f5fcd482f1cc4008a6028243e009"
  fuel-nailgun-agent_sha: "a33a58d378c117c0f509b0e7badc6f0910364154"
  astute_sha: "b60624ee2c5f1d6d805619b6c27965a973508da1"
  fuel-library_sha: "22ed1ebd7804457a02b51b57c7019d853c528611"
  fuel-ostf_sha: "a98973482f839554d90cc1c071d625a01e018cfe"
  fuel-mirror_sha: "5a1efffd411611b87cbd45af59b9733b7e170cd4"
  fuelmenu_sha: "fcb15df4fd1a790b17dd78cf675c11c279040941"
  shotgun_sha: "25a0cc461a9fa4f7684f04cef0ff4ad9aa99a64d"
  network-checker_sha: "a3534f8885246afb15609c54f91d3b23d599a5b1"
  fuel-upgrade_sha: "1e894e26d4e1423a9b0d66abd6a79505f4175ff6"
  fuelmain_sha: "ff6eec402830ea8aa9898249b5eeb928576962ff"

[Alexandra Morozova (astepanchuk)]

Floating range is validated against network which has meta.floating_range_var field. In the case described above this network is still the default one, so IMO either this field should removed or changed in the backend, or no validation of floating ip range correspondence to cidr can be performence on the UI side.
the first option seems better for me, so re-assigning this bug fuel-python team.

[Aleksandr Didenko (adidenko)]

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.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/255889
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=532eb5f2b9195ae903d0179705d9f1381f169300
Submitter: Jenkins
Branch: master

commit 532eb5f2b9195ae903d0179705d9f1381f169300
Author: Julia Aranovich <email address hidden>
Date: Thu Dec 10 17:05:53 2015 +0300

    Allow to set floating range for public network of any node network group

    Closes-Bug: #1522760

    Change-Id: I7ba67e17d8bd731e46abc6fd3e181eec9f2146f1

[Veronica Krayneva (vkrayneva)]

Verified on #478 iso.