Hi
thanks, this is the case what i am looking for.



At 2016-11-13 19:38:57, "Irena Berezovsky" <irenab....@gmail.com> wrote:

Hi,
The case you are describing may be related to the previously discussed RFE [1].
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].


[1]  https://bugs.launchpad.net/neutron/+bug/1566191


BR,
Irena






On Sun, Nov 13, 2016 at 12:35 PM, Gary Kotton <gkot...@vmware.com> wrote:


Hi,

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.

Thanks

Gary

 

From: huangdenghui <hdh_1...@163.com>
Reply-To: OpenStack List <openstack-dev@lists.openstack.org>
Date: Saturday, November 12, 2016 at 10:26 AM
To: OpenStack List <openstack-dev@lists.openstack.org>
Subject: [openstack-dev] [neutron][dvr][fip] router support two external network

 

Hi all
    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.


__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to