Re: [openstack-dev] [neutron]Do we need to rfe to implement active-active router?

2016-12-02 Thread huangdenghui
Hi Assaf I already file a RFE bug, please check bug#1645625. Any comment is welcome. 发自网易邮箱手机版 On 2016-11-17 01:32 , Assaf Muller Wrote: On Wed, Nov 16, 2016 at 10:42 AM, huangdenghui wrote: > hi > Currently, neutron support DVR router and legacy router. For high > ava

Re: [openstack-dev] [neutron]Do we need to rfe to implement active-active router?

2016-11-29 Thread huangdenghui
Hi Thomas I have already filed a RFE bug.Please refer to bug #1645625 发自网易邮箱手机版 On 2016-11-18 01:27 , Thomas Morin Wrote: Hi, What would active-active exactly be in DVR mode ? -Thomas Le 16/11/2016 à 16:42, huangdenghui a écrit : hi Currently, neutron support DVR router and

[openstack-dev] [neutron][metadata] Is there HTTP attack issue in metadata proxy functionality offered by reference implementation?

2016-11-16 Thread huangdenghui
hi Currently, nova metadata service is proxy by metadata agent in dhcp agent or l3 router agent, it is depended on whether network attach to router or not. In essential, metadata agent implements a http proxy functionality by computer node host protocal stack. In other words, it exposes host

[openstack-dev] [neutron]Do we need to rfe to implement active-active router?

2016-11-16 Thread huangdenghui
hi Currently, neutron support DVR router and legacy router. For high availability, there is HA router in reference implementation of legacy mode and DVR mode. I am considering whether is active-active router needed in both mode? __

Re: [openstack-dev] [neutron][dvr][fip] router support two external network

2016-11-16 Thread huangdenghui
f 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 Reply-To: OpenStack List Date: Saturday, November 12, 2016 at 10:26 AM To: OpenStack List Subject:

[openstack-dev] [neutron][dvr][fip] router support two external network

2016-11-12 Thread huangdenghui
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

[openstack-dev] [neutron][networking-ovs-dpdk][dvr] how to use dvr with networking-ovs-dpdk

2016-08-23 Thread huangdenghui
hi Is it possible to use dvr with networking-ovs-dpdk now? If not, is it on the roadmap of networking-ovs-dpdk? 发自网易邮箱手机版__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@

Re: [openstack-dev] [neutron][dvr][fip] fg device allocated private ip address

2016-08-16 Thread huangdenghui
:38:52,"Carl Baldwin" 写道: On Tue, Aug 2, 2016 at 6:15 AM, huangdenghui wrote: hi john and brain thanks for your information, if we get patch[1],patch[2] merged,then fg can allocate private ip address. after that, we need consider floating ip dataplane, in current dvr implementat

Re: [openstack-dev] [neutron] Neutron Port MAC Address Uniqueness

2016-08-09 Thread huangdenghui
hi Armando I think this feature causes problem in sriov scenario, since sriov NIC don't support the vf has the same mac,even the port belongs to the different network. 发自网易邮箱手机版 On 2016-08-10 04:55 , Armando M. Wrote: On 9 August 2016 at 13:53, Anil Rao wrote: Is the MAC address

Re: [openstack-dev] 答复: [neutron][dvr][fip] fg device allocated private ip address

2016-08-03 Thread huangdenghui
at 6:15 AM, huangdenghui wrote: hi john and brain thanks for your information, if we get patch[1],patch[2] merged,then fg can allocate private ip address. after that, we need consider floating ip dataplane, in current dvr implementation, fg is used to reachment testing for floating ip, now,w

Re: [openstack-dev] [neutron][dvr][fip] fg device allocated private ip address

2016-08-02 Thread huangdenghui
;On 07/31/2016 06:27 AM, huangdenghui wrote: >> Hi >>Now we have spec named subnet service types, which provides a >>capability of >> allowing different port of a network to allocate ip address from >>different >> subnet. In current implementation of DVR, fip also is dist

[openstack-dev] [neutron][dvr][fip] fg device allocated private ip address

2016-07-31 Thread huangdenghui
Hi Now we have spec named subnet service types, which provides a capability of allowing different port of a network to allocate ip address from different subnet. In current implementation of DVR, fip also is distributed on every compute node, floating ip and fg's ip are both allocated from ex

Re: [openstack-dev] [neutron][L3][DVR][arp]

2015-11-29 Thread huangdenghui
If those 200 subnets are VXLAN networks, i think it is a good idea, since L2population already propagate this configuration to OVS-Agent. One comment for VLAN network, since DVR also support in VLAN network and L2population is not necessary in it, what is your consideration in this case?