Service project default quota allows only 10 HA Octavia LoadBalancers

[Srinivas Atmakuri]

Service project default quota allows only 10 HA Octavia LoadBalancers

Description
=======
default service project quota allows 10 server_groups and 10 server_group_members. Every HA Octavia LoadBalancers consumes one of these. Creating more than 10 load balancers fails.

Octavia creates Amphorae (service VMs) under an operator configured project (tenant). In TripleO, we currently use the 'service' project by default.

Since booting Amphorae consume the project quota, this essentially results in a very low (around 10) global upper constraint for load balancers amount.

Steps to reproduce
============
1. Launch 10 HA Octavia LoadBalancers successful
2. Error while launching 10+x HA Octavia LoadBalancers

Expected Result
==========
Able to launch 10+x HA Octavia LoadBalancers

Actual Result
========
Quota exceeded too many server groups.

Possible Fix
=======
We need to address the 'service' project as a system project. Thus, we cannot be limited by project quotas for Octavia VMs.
We need to set '-1' for the following quotas (in the 'service project only):
1. server-group-members
2. server-groups

Logs
===
ERROR oslo_messaging.rpc.server novaclient.exceptions.Forbidden: Quota exceeded, too many server groups. (HTTP 403) (Request-ID: req-d48de5eb-de5f-4918-a92f-42092a21e1b3)

Additional Info:
Relevant bugs: #1769896

[Brent Eagles (beagles)]

Patches merged back to train https://review.opendev.org/q/I0048fec8c1e19bd20b1edcd23f2490456fe1cd12

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-ansible 2.2.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-ansible 0.7.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-ansible 1.5.3 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-ansible 3.1.0 release.