[cells v2 multicell] nova metadata api per cell

[Martin Schuppert]

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

This is to track nova metadata api per cell in tripleo

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.opendev.org/675070

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/675103

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/675070
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=520dd2a4cbca1579c2fd7cfd36b96f82d7bbc5e8
Submitter: Zuul
Branch: master

commit 520dd2a4cbca1579c2fd7cfd36b96f82d7bbc5e8
Author: Martin Schuppert <email address hidden>
Date: Wed Aug 7 11:33:31 2019 +0200

    Use nova_metadata related hiera and make cell aware

    Since nova metadata runs via wsgi and can be run on its own
    use nova_metadata_ related hiera keys to configure the
    proxy in haproxy.
    It is now also possible to configure nova_metadata local
    to a nova cellv2.

    Change-Id: I364436ed6ca451dfaa079dc891c2cb6516eb3907
    Related-Bug: #1823760

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/675103
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=2cd9e44e66dbf83ce763cbe2d7bca1593b1bd891
Submitter: Zuul
Branch: master

commit 2cd9e44e66dbf83ce763cbe2d7bca1593b1bd891
Author: Martin Schuppert <email address hidden>
Date: Thu Aug 1 10:17:03 2019 +0200

    Add NovaLocalMetadataPerCell cell support

    Indicates that the nova-metadata API service has been deployed
    per-cell, so that we can have better performance and data isolation
    in a multi-cell deployment. Users should consider the use of this
    configuration depending on how neutron is setup. If networks span
    cells, you might need to run nova-metadata API service globally.
    If your networks are segmented along cell boundaries, then you can
    run nova-metadata API service per cell.

    Introduces a new endpoint_map entry NovaMetadataInternal.

    If NovaLocalMetadataPerCell is true, NovaMetadataCellInternal points
    to the local cell endpoint.

    If NovaLocalMetadataPerCell is false, NovaMetadataCellInternal points
    to the central control plane nova metadata endpoint.

    The NovaMetadataCellInternal endpoint is then used to configure the
    nova-metadata api endpoint the ovn metadata agent points to.

    Also removes setting the deprecated [DEFAULT]/nova_metadata_ip
    hiera key and only uses [DEFAULT]/nova_metadata_host for the ovn
    metadata agent.

    Depends-On: https://review.opendev.org/675070
    Depends-On: https://review.opendev.org/650943
    Change-Id: I78f6d30676ee166f84d8aca1609b376bb73e5f2c
    Closes-Bug: #1823760

    Change-Id: I1e05230e4105a3706f0662b0c203137d05ebf3d8

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-heat-templates 11.2.0 release.