Fuel prevents separation of Public and Floating networks
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Invalid
|
High
|
Fuel Library (Deprecated) |
Bug Description
Currently Fuel prevents the separation of the Public and Floating networks, justified by the idea that Neutron cannot do its own external routing.
We have a requirement to separate the networks so that we can put the Public services behind reverse proxies and other protections instead of publishing them directly on public IP ranges. The Floating range, however, needs to be a public network.
We don't see why the two need to be on the same CIDR subnet?
For other deployments we've done, we've separated them. The 'Floating' network is setup as is described in http://
We therefore see the forced co-location of the two networks as a bug.
Changed in fuel: | |
milestone: | none → 5.1 |
assignee: | nobody → Fuel Python Team (fuel-python) |
importance: | Undecided → High |
Changed in fuel: | |
assignee: | Dima Shulyak (dshulyak) → Fuel Library Team (fuel-library) |
FYI - I see that there's already a blueprint for this: https:/ /blueprints. launchpad. net/fuel/ +spec/separate- public- floating