I have responded to the comment in Launchpad.

Allain Legacy, Software Developer, Wind River
direct 613.270.2279  fax 613.492.7870 skype allain.legacy

350 Terry Fox Drive, Suite 200, Ottawa, Ontario, K2K 2W5

From: Xu, Chenjie [mailto:chenjie.xu@intel.com]
Sent: Monday, December 17, 2018 12:51 AM
To: Peters, Matt; Legacy, Allain
Cc: starlingx-discuss@lists.starlingx.io
Subject: [Starlingx-discuss] RFE Discussion for patch 9f926a5 for StartlingX upstreaming

Hi Matt/Allain,

For RFE “Add l2pop support for floating IP resources”, Miguel left a comment as below:

Maybe I am misunderstanding, but I am having difficulty understanding the need for this RFE:

1) In both use cases described above, you state that "When VM-1 pings FloatingIP-2 for the first time, it needs to know the MAC address for FloatingIP-2. Thus ARP request is sent out". Since FloatingIP-2 is

not in the same subnet as Port1, wouldn't just VM send the the ICMP echo request directly to its default gateway and let L3 level protocols route the request to the correct destination?

2) The summary of your proposal is "The idea is that advertising the FDBs for floating IP when the FIP status changes to "ACTIVE" and withdraw the FDBs for floating IP whenever the status is set to "DOWN"

or the resource is deleted or disassociated." Aren't we mixing L2 and L3 concepts here unnecessarily. The FDB entries in L2pop are meant to optimize the communication at L2. Floating IPs should be handled

by L3. Am I missing something?

Could you please help review and comment? The link for the RFE is below:

https://bugs.launchpad.net/neutron/+bug/1803494

Best Regards,

Xu, Chenjie