Bug 1720404

Summary:	[RFE] Count quota usage from placement
Product:	Red Hat OpenStack	Reporter:	melanie witt <mwitt>
Component:	openstack-nova	Assignee:	melanie witt <mwitt>
Status:	CLOSED ERRATA	QA Contact:	OSP DFG:Compute <osp-dfg-compute>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	16.0 (Train)	CC:	alifshit, dasmith, egallen, eglynn, igallagh, jgrosso, jhakimra, jparker, kchamart, lyarwood, mariel, sbauza, sgordon, spower, stephenfin, vromanso
Target Milestone:	ga	Keywords:	FutureFeature, TestOnly, Triaged
Target Release:	17.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-nova-21.1.0-0.20200425164546.347d656.el8ost	Doc Type:	Enhancement
Doc Text:	With this update, you can configure your RHOSP deployment to count the quota usage of cores and RAM by querying placement for resource usage and instances from instance mappings in the API database, instead of counting resources from separate cell databases. This makes quota usage counting resilient to temporary cell outages or poor cell performance in a multi-cell environment. + Set the following configuration option to count quota usage from placement: + ``` parameter_defaults: ControllerExtraConfig: nova::config::nova_config: quota/count_usage_from_placement: value: 'True' ```	Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-08-16 01:09:21 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:	Ussuri
Embargoed:
Bug Depends On:
Bug Blocks:	2033222

Description melanie witt 2019-06-13 22:45:35 UTC

In Pike, we re-architected the quota system to count actual resource usage instead of using reservations and tracking quota usages in a separate database table. We're counting resources like instances, CPU, and RAM by querying each cell database and aggregating the results per project and per user. This approach has a downside: it is susceptible to undesirable behavior if a cell becomes unavailable. If a cell becomes unavailable, resources in its database cannot be counted and will not be included in resource usage until the cell returns. Cells could become unavailable if an operator is performing maintenance on a cell or if a cell database is experiencing problems and we cannot connect to it.

We can make resource usage counting for quotas resilient to temporary cell outages by querying placement for resource usage instead of reading separate cell databases.

This adds the ability to count quota usage from placement on an opt-in basis via configuration option.

Comment 6 Artom Lifshitz 2022-08-23 16:47:27 UTC

This will need an enhancement doc text once this graduates out of tech preview (https://bugzilla.redhat.com/show_bug.cgi?id=2120756)

Comment 23 errata-xmlrpc 2023-08-16 01:09:21 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Release of components for Red Hat OpenStack Platform 17.1 (Wallaby)), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2023:4577