<div dir="ltr">Hi,<div>The case you are describing may be related to the previously discussed RFE [1].</div><div>Having additional networks with FIP range attached via router interface should be allowed from the API point of view, but may need some adaptations to make it work properly. Please see the details in the discussion log [1].</div><div><br></div><div>[1] <a href="https://bugs.launchpad.net/neutron/+bug/1566191">https://bugs.launchpad.net/neutron/+bug/1566191</a></div><div><br></div><div>BR,</div><div>Irena</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Nov 13, 2016 at 12:35 PM, Gary Kotton <span dir="ltr"><<a href="mailto:gkotton@vmware.com" target="_blank">gkotton@vmware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="m_-8665095668012927466WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Hi,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Today the mapping is 1:1. So if you want additional mappinsg to internal networks then you can define more than one interface on your instance. Then map each interface to the relevant network.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Thanks<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Gary<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><u></u> <u></u></span></p>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:Calibri;color:black">From: </span>
</b><span style="font-family:Calibri;color:black">huangdenghui <<a href="mailto:hdh_1983@163.com" target="_blank">hdh_1983@163.com</a>><br>
<b>Reply-To: </b>OpenStack List <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.<wbr>openstack.org</a>><br>
<b>Date: </b>Saturday, November 12, 2016 at 10:26 AM<br>
<b>To: </b>OpenStack List <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.<wbr>openstack.org</a>><br>
<b>Subject: </b>[openstack-dev] [neutron][dvr][fip] router support two external network<u></u><u></u></span></p>
</div><span class="">
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:Arial;color:black">Hi all<br>
Currently, neutron model supports one router with one external network, which is used to connect router to outside world. FIP can be allocated from external network which is gateway of a router. One private fixed ip of one port(usually it is a vm port )
can only associate one floating ip. In some deployment scenario, all ports served by one router, all ports need ip address which can be accessed by intranet, and some ports need ip address which can be accessed by internet. I was wondering how neutron to
resolve this kind of use cases? One idea is one router support two external network(one for intranet, the other one for internet, but only have gateway), the other idea is one router still have only one external network, but this external have two different
type of subnet (one for internet, the other one for intranet). any comment is welcome. thanks.
<u></u><u></u></span></p>
</div>
</div>
</span></div>
</div>
<br>______________________________<wbr>______________________________<wbr>______________<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.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br></blockquote></div><br></div>