<div dir="ltr">Hi James,<div><br></div><div>I understand the network-environment.yaml will also be generated.</div><div>What do you mean by rendered path? Will it be "usr/share/openstack-tripleo-heat-templates/network/ports/"?</div><div>By the way I didn't find any other place in my templates where I refer to these files?</div><div>What about custom nic configs is there also a jinja2 process to create them?</div><div><br></div><div>Samuel<br><br><div class="gmail_quote"><div dir="ltr">On Thu, Jul 26, 2018 at 12:02 AM James Slagle <<a href="mailto:james.slagle@gmail.com">james.slagle@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Wed, Jul 25, 2018 at 11:56 AM, Samuel Monderer<br>
<<a href="mailto:smonderer@vasonanetworks.com" target="_blank">smonderer@vasonanetworks.com</a>> wrote:<br>
> Hi,<br>
><br>
> I'm trying to upgrade from OSP11(Ocata) to OSP13 (Queens)<br>
> In my network-isolation I refer to files that do not exist anymore on the<br>
> director such as<br>
><br>
>   OS::TripleO::Compute::Ports::ExternalPort:<br>
> /usr/share/openstack-tripleo-heat-templates/network/ports/external.yaml<br>
>   OS::TripleO::Compute::Ports::InternalApiPort:<br>
> /usr/share/openstack-tripleo-heat-templates/network/ports/internal_api.yaml<br>
>   OS::TripleO::Compute::Ports::StoragePort:<br>
> /usr/share/openstack-tripleo-heat-templates/network/ports/noop.yaml<br>
>   OS::TripleO::Compute::Ports::StorageMgmtPort:<br>
> /usr/share/openstack-tripleo-heat-templates/network/ports/noop.yaml<br>
>   OS::TripleO::Compute::Ports::TenantPort:<br>
> /usr/share/openstack-tripleo-heat-templates/network/ports/tenant.yaml<br>
>   OS::TripleO::Compute::Ports::ManagementPort:<br>
> /usr/share/openstack-tripleo-heat-templates/network/ports/management_from_pool.yaml<br>
><br>
> Where have they gone?<br>
<br>
These files are now generated from network/ports/port.network.j2.yaml<br>
during the jinja2 template rendering process. They will be created<br>
automatically during the overcloud deployment based on the enabled<br>
networks from network_data.yaml.<br>
<br>
You still need to refer to the rendered path (as shown in your<br>
example) in the various resource_registry entries.<br>
<br>
This work was done to enable full customization of the created<br>
networks used for the deployment. See:<br>
<a href="https://docs.openstack.org/tripleo-docs/latest/install/advanced_deployment/custom_networks.html" rel="noreferrer" target="_blank">https://docs.openstack.org/tripleo-docs/latest/install/advanced_deployment/custom_networks.html</a><br>
<br>
<br>
-- <br>
-- James Slagle<br>
--<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div></div></div>