Open Stack

On Wed, Jul 25, 2018 at 11:56 AM, Samuel Monderer
<smonderer at vasonanetworks.com> wrote:
> Hi,
>
> I'm trying to upgrade from OSP11(Ocata) to OSP13 (Queens)
> In my network-isolation I refer to files that do not exist anymore on the
> director such as
>
>   OS::TripleO::Compute::Ports::ExternalPort:
> /usr/share/openstack-tripleo-heat-templates/network/ports/external.yaml
>   OS::TripleO::Compute::Ports::InternalApiPort:
> /usr/share/openstack-tripleo-heat-templates/network/ports/internal_api.yaml
>   OS::TripleO::Compute::Ports::StoragePort:
> /usr/share/openstack-tripleo-heat-templates/network/ports/noop.yaml
>   OS::TripleO::Compute::Ports::StorageMgmtPort:
> /usr/share/openstack-tripleo-heat-templates/network/ports/noop.yaml
>   OS::TripleO::Compute::Ports::TenantPort:
> /usr/share/openstack-tripleo-heat-templates/network/ports/tenant.yaml
>   OS::TripleO::Compute::Ports::ManagementPort:
> /usr/share/openstack-tripleo-heat-templates/network/ports/management_from_pool.yaml
>
> Where have they gone?

These files are now generated from network/ports/port.network.j2.yaml
during the jinja2 template rendering process. They will be created
automatically during the overcloud deployment based on the enabled
networks from network_data.yaml.

You still need to refer to the rendered path (as shown in your
example) in the various resource_registry entries.

This work was done to enable full customization of the created
networks used for the deployment. See:
https://docs.openstack.org/tripleo-docs/latest/install/advanced_deployment/custom_networks.html


-- 
-- James Slagle
--