Hide Forgot
Currently, we can only use the networks that are defined in the TripleO templates (i.e. control plane, external, internal API, tenant, storage, storage management and generic management). A user might require additional networks or might want to label a network to reflect its role. To achieve this, director should allow the user to compose networks for using in the Overcloud.
Some related upstream work: https://review.openstack.org/#/c/409921/
Steve, are there any other patches required to complete the composable networks work after OpenStack Gerrit patch 409921 was merged?
*** Bug 1381704 has been marked as a duplicate of this bug. ***
Verified: Environment: openstack-tripleo-heat-templates-7.0.3-0.20171024200825.el7ost.noarch Successfully deployed OC with: composable networks for all roles. IPv6 composable networks. predictable IP on ipv4 and ipv6 networks.
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-2017:3462
*** Bug 1361714 has been marked as a duplicate of this bug. ***