<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic PAN-VM OpenStack interface assignments in VM-Series in the Private Cloud</title>
    <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-private-cloud/pan-vm-openstack-interface-assignments/m-p/616861#M288</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;we have come came across the issue that the PAN-VM appliance relies on the PCI topology to assign network interfaces and not the mac address.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;This is the a problem, OpenStack the PCI topology is not persistent across reboots (when an instance is recreated, the libvirt config is rebuilt).&lt;/P&gt;
&lt;P&gt;It happened to us, that after a reboot the interface assignments were gone.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;In OpenStack the metadata feature [2] or the MAC address usually used to assign the correct interfaces [1].&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Has anyone come across this or have any idea how to fix it? IMO the PAN-VM should not rely on the PCI topology but rather the mac address (or the metadata service).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Jan&lt;/P&gt;
&lt;P&gt;[1] &lt;A href="https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/AUMDRRBSNI3IKA2DDPULP6RDGM74DKCQ/" target="_blank"&gt;https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/AUMDRRBSNI3IKA2DDPULP6RDGM74DKCQ/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;[2] &lt;A href="https://specs.openstack.org/openstack/nova-specs/specs/newton/implemented/virt-device-role-tagging.html#proposed-change" target="_blank"&gt;https://specs.openstack.org/openstack/nova-specs/specs/newton/implemented/virt-device-role-tagging.html#proposed-change&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 11 Nov 2024 21:17:02 GMT</pubDate>
    <dc:creator>pit-jm</dc:creator>
    <dc:date>2024-11-11T21:17:02Z</dc:date>
    <item>
      <title>PAN-VM OpenStack interface assignments</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-private-cloud/pan-vm-openstack-interface-assignments/m-p/616861#M288</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;we have come came across the issue that the PAN-VM appliance relies on the PCI topology to assign network interfaces and not the mac address.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;This is the a problem, OpenStack the PCI topology is not persistent across reboots (when an instance is recreated, the libvirt config is rebuilt).&lt;/P&gt;
&lt;P&gt;It happened to us, that after a reboot the interface assignments were gone.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;In OpenStack the metadata feature [2] or the MAC address usually used to assign the correct interfaces [1].&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Has anyone come across this or have any idea how to fix it? IMO the PAN-VM should not rely on the PCI topology but rather the mac address (or the metadata service).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Jan&lt;/P&gt;
&lt;P&gt;[1] &lt;A href="https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/AUMDRRBSNI3IKA2DDPULP6RDGM74DKCQ/" target="_blank"&gt;https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/AUMDRRBSNI3IKA2DDPULP6RDGM74DKCQ/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;[2] &lt;A href="https://specs.openstack.org/openstack/nova-specs/specs/newton/implemented/virt-device-role-tagging.html#proposed-change" target="_blank"&gt;https://specs.openstack.org/openstack/nova-specs/specs/newton/implemented/virt-device-role-tagging.html#proposed-change&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Nov 2024 21:17:02 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-private-cloud/pan-vm-openstack-interface-assignments/m-p/616861#M288</guid>
      <dc:creator>pit-jm</dc:creator>
      <dc:date>2024-11-11T21:17:02Z</dc:date>
    </item>
  </channel>
</rss>

