Bug 1689816

Summary:	[RFE] Nova metadata api per cell
Product:	Red Hat OpenStack	Reporter:	Martin Schuppert <mschuppe>
Component:	openstack-tripleo-heat-templates	Assignee:	Martin Schuppert <mschuppe>
Status:	CLOSED ERRATA	QA Contact:	Piotr Kopec <pkopec>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	15.0 (Stein)	CC:	amodi, ccopello, egallen, gregraka, jamsmith, lyarwood, mbooth, mburns, mwitt, sclewis
Target Milestone:	Upstream M3	Keywords:	FutureFeature, Patch, Triaged, ZStream
Target Release:	16.0 (Train on RHEL 8.1)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-11.3.1-0.20191022072831.698e7db.el8ost puppet-nova-15.4.1-0.20191014175323.e6628d6.el8ost puppet-tripleo-11.3.1-0.20191022051220.c97dbd1.el8ost	Doc Type:	Enhancement
Doc Text:	In Red Hat OpenStack Platform 16.0, a new Orchestration service (heat) deployment parameter is available that enables administrators to turn on the nova metadata service on cell controllers: parameter_defaults: NovaLocalMetadataPerCell: True This new parameter automatically directs traffic from the OVN metadata agent on the cell computes to the nova metadata API service hosted on the cell controllers. Depending on the RHOSP topology, the ability to run the metadata service on cell controllers can reduce the traffic on the central control plane.	Story Points:	---
Clone Of:
Clones:	1767418 (view as bug list)		Environment:
Last Closed:	2020-02-06 14:39:53 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:
Embargoed:
Bug Depends On:
Bug Blocks:	1767418

Description Martin Schuppert 2019-03-18 08:31:08 UTC

Description of problem:

From [1]

Nova Metadata API service
Starting from the Stein release, the Nova Metadata API service can be run either globally or per cell using the api.local_metadata_per_cell configuration option.

Global

If you have networks that span cells, you might need to run Nova metadata API globally. When running globally, it should be configured as an API-level service with access to the api_database.connection information. The nova metadata API service must not be run as a standalone service in this case (e.g. must not be run via the nova-api-metadata script).

Local per cell

Running Nova metadata API per cell can have better performance and data isolation in a muli-cell deployment. If your networks are segmented along cell boundaries, then you can run Nova metadata API service per cell. If you choose to run it per cell, you should also configure each Neutron metadata-agent to point to the corresponding nova-metadata-api. The nova metadata API service must be run as a standalone service in this case (e.g. must be run via the nova-api-metadata script).

[1] https://docs.openstack.org/nova/latest/user/cellsv2-layout.html#nova-metadata-api-service



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 11 Martin Schuppert 2019-12-10 13:21:17 UTC

*** Bug 1767418 has been marked as a duplicate of this bug. ***

Comment 16 errata-xmlrpc 2020-02-06 14:39:53 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, 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-2020:0283