Comment 18 for bug 1800811

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to tripleo-heat-templates (stable/rocky)

Reviewed: https://review.openstack.org/629307
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=836b1b3327e89a1136f30ea752d916c96eb6a082
Submitter: Zuul
Branch: stable/rocky

commit 836b1b3327e89a1136f30ea752d916c96eb6a082
Author: Harald Jensås <email address hidden>
Date: Tue Jan 8 12:23:52 2019 +0100

    Reno only - Check for available networks for a role

    Since change: I07822ec0cba7eed352c0010eb893b5e5a522e95c
    resources are no longer created for networks that are not
    defined in roles data. While this is an improvement we
    need to communicate this change.

    There is tribal knowledge and documentation that failed
    reflect the requirement to add networks to roles data
    since the introduction of composable networks in Pike.

    Prior to Pike adding a network to a role was achived by
    overriding the resource_registry entry to not use the
    noop.yaml fake port (fall back to ctlplane) template.
    i.e to add External network to compute role the
    following was commonly added to network-environment.yaml

      OS::TripleO::Compute::Ports::ExternalPort:
        ../network/ports/external.yaml

    NOTE: Current OVN-DVR and ODL doc's downstream uses the
          resource_registry override, whitout also adding
          the network to roles data.

    Related-Bug: #1800811
    Change-Id: I6c03c7a2bd6f369bf35a9e479a97302c9a455197
    (cherry picked from commit 991e0fc0c0c9fc24b53b3760b396de75d9fb52ad)