[Fuel UI] Multiple floating ranges are not supported when using Neutron

[Sam Stoelinga]

Steps to reproduce:
1. Create an environment using Neutron
2. In the Network settings define multiple floating ranges for floating ips
3. Deploy the environment

Current result:
Deployment succeeds but only a single allocation_pool gets allocated to the floating subnet

Expected result:
For all releases of Neutron that do not support fragmented floating ip ranges in a single subnet, disable this functionality from the UI. Or fix multiple floating allocation_pools in a single subnet

There are 2 fixes, for having fragmented floating IPs in a single subnet:
1. Divide them into different subnets, where every subnet has 1 allocation_pool
2. Bypass API and directly manipulate mysql db, seems risky! For more info see: http://samos-it.com/posts/neutron-multiple-allocation-pools-single-subnet.html

See related discussion:
https://<email address hidden>/msg09001.html

[Irina Povolotskaya (ipovolotskaya)]

Should this be included into Release Notes?
Can 2 abovementioned fixed be described as a possible workaround?

[Aleksey Kasatkin (alekseyk-ru)]

Seems to be on Nailgun side:
https://github.com/stackforge/fuel-web/blob/master/nailgun/nailgun/network/neutron.py#L59-60

[Aleksey Kasatkin (alekseyk-ru)]

But I'm not sure whether manifests support something different.

[Sam Stoelinga (sammiestoel)]

I can take a look at this as soon as we confirm how to fix, my suggestion goes to only allow a single range when Neutron is choosen for now and add documentation for user how to solve this problem manually after deployment. It's too risky to include the fixes in Fuel untill there is an official fix in upstream.

[Sam Stoelinga (sammiestoel)]

I noticed that Neutron API also supports multiple allocation_pools per subnet but it requires using the python api instead of the CLI, please see the following script I created to update a subnet with multiple allocation_pools: http://paste.openstack.org/show/115423/

So instead of disabling it in UI i suggest using the python api to create the subnets which support multiple allocation_pools per subnet.

[Aleksey Kasatkin (alekseyk-ru)]

Sergey V. suggestion is to disable this in UI as a quick solution. Seems it is not supported in library now.

[Sam Stoelinga (sammiestoel)]

So I did the initial code, but still need to get a development environment up to run the code.

Patch: https://review.openstack.org/#/c/126635/

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/126635
Committed: https://git.openstack.org/cgit/stackforge/fuel-web/commit/?id=e9d02599aebaf45fc0397b8ca1cae27d1a2e967c
Submitter: Jenkins
Branch: master

commit e9d02599aebaf45fc0397b8ca1cae27d1a2e967c
Author: Sam Stoelinga <email address hidden>
Date: Wed Oct 8 12:42:32 2014 -0700

    Disable multi floating ranges when using Neutron

    Currently fuel-library doesn't seem to support multiple
    floating ranges when using Neutron. Neutron it self does
    support multiple floating ranges when using the Python api
    although the CLI has no support for this.

    This patch will first disable it in the UI as a first step
    and the actual support for multiple floating ip ranges with Neutron
    in fuel will be added later. We should re-enable the functionality
    in UI as soon as we have support in Fuel.

    Hacky way - needs change after advanced networking implementation

    Related-bug: #1371363

    Change-Id: I7917f5b8419b4f36e80a9d1a59291d67c832a4bd

[Matthew Mosesohn (raytrac3r)]

Sam, can we close this bug?

[Sam Stoelinga (sammiestoel)]

I would prefer to have support for multiple floating ranges as Openstack
supports this. So we can keep this bug open to track that we are missing
this support in Fuel.
The current fix is a temporary workaround to just bluntly disable multiple
floating ips in the UI.

If somebody decides that we dont want to support multiple floating ranges
at all when using neutron in Fuel, you can just close it.

[Dmitry Pyzhov (dpyzhov)]

Is it supported by puppet now?

[Vladimir Sharshov (vsharshov)]

As i can see, we have workaround which used from 6.0 version. We kept it because we want to support for multiple floating ranges as Openstack supports in future. That is why we moved it to 8.0

[Alexander Kislitsky (akislitsky)]

We passed SCF in 8.0. Moving the bug to 9.0.

[Dmitry Pyzhov (dpyzhov)]

It's a feature and we passed SCF for 9.0. Moving to 10.0.

[Aleksey Kasatkin (alekseyk-ru)]

First, let's ensure that multiple floating is supported in fuel-library.

[Michael Polenchuk (mpolenchuk)]

multiple floating is supported in fuel-lib since Nov 4, 2015
https://review.openstack.org/235879

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.openstack.org/310033

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/310033
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=41bbcb9db34efcfc0c5d87aac67d60ae3ae0aadb
Submitter: Jenkins
Branch: master

commit 41bbcb9db34efcfc0c5d87aac67d60ae3ae0aadb
Author: Michael Polenchuk <email address hidden>
Date: Mon Apr 25 20:49:48 2016 +0300

    Smooth down format_allocation_pools func

    * check cidr by way of ipaddr build-in method
    * take ranges as an array or string
    * go faster if cidr ain't provided
    * rewrite tests in 'expected' fashion

    Change-Id: Idbbeeeeaf952fa4f7bd9b520d819105537ba45c6
    Related-Bug: #1371363

[Aleksey Kasatkin (alekseyk-ru)]

So, just API and UI are affected.