Bug 1577611 - The global amount of Octavia loadbalancers is constrained by the size of lb-mgmt-subnet
Summary: The global amount of Octavia loadbalancers is constrained by the size of lb-m...
Status: CLOSED DUPLICATE of bug 1577612
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-common
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Ryan Brady
QA Contact: Alexander Chuzhoy
Depends On:
TreeView+ depends on / blocked
Reported: 2018-05-13 13:24 UTC by Nir Magnezi
Modified: 2018-05-16 13:48 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-05-16 13:48:07 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Nir Magnezi 2018-05-13 13:24:44 UTC
Description of problem:
Octavia creates Amphorae (service VMs) under an operator configured project (tenant). In TripleO, we currently use 'service' project by default.
Each Amphora instance has its own tap device in a shared management subnet named lb-mgmt-subnet. That subnet is concealed under the 'service' project and cannot be accessed by non-privileged users.

TripleO creates that subnet during the Octavia deployment process. Currently, it is created as a class B subnet with allocation_pools that essentially limit the number of address in that subnet to 150.
Which means, globally for a given OpenStack deployment:
- 150 Amphorae ==> 150 Loadbalancers if the Amphora topology is SINGLE
- 150 Amphorae ==> 75 Loadbalancers if the Amphora topology is ACTIVE_STANDBY

Here's how it currently looks (snipped):

| Field             | Value                                |
| allocation_pools  |       |
| cidr              |                     |
| created_at        | 2018-05-07T09:14:36Z                 |
| enable_dhcp       | True                                 |
| gateway_ip        |                        |
| ip_version        | 4                                    |
| name              | lb-mgmt-subnet                       |

Version-Release number of selected component (if applicable):
OSP13 2018-05-10.3 openstack-tripleo-common-8.6.1-9 

How reproducible:

Steps to Reproduce:
1. Deploy OpenStack with Octavia via TripleO

Actual results:
As mentioned above.

Expected results:
We should have a much larger subnet such as class B, so the global amount of Octavia loadbalancers won't constrained to a very low number.

Comment 1 Bernard Cafarelli 2018-05-16 13:48:07 UTC

*** This bug has been marked as a duplicate of bug 1577612 ***

Note You need to log in before you can comment on or make changes to this bug.