>>Sorry, too much information for me. Please can you explain why we need 
>>a floating IP?

floating ip are simply public ip which are used to do nat 1:1. 
(internet->public ip -->nat 1:1-> private ip)
(they call them floating, because you can reassign them to another private ip 
on the fly ..but it's just nat).


>>I thought we can use a special static IP on each 
>>virtual bridge, something like: 
>>
>>https://networkop.co.uk/blog/2016/10/13/os-dvr/ 
>>
>>Requires to block some ARP traffic on the vxlan. 

This depend which model you want to implement:

1 central gateway (with failover if possible): works with simple layer2 
network, vlan network, ovn. 

1 distributed gateway:(same ip/mac on same vmbr on all host, works with ovn 
dvr, vxlan-ebgp out of the box, and maybe vxlan without bgp but I'm not sure 
how routing is done from external network)

(personnaly, distributed gateway is more sexy, no spof, no failover)




----- Mail original -----
De: "dietmar" <diet...@proxmox.com>
À: "Alexandre Derumier" <aderum...@odiso.com>, "pve-devel" 
<pve-devel@pve.proxmox.com>
Envoyé: Vendredi 26 Janvier 2018 06:48:27
Objet: Re: [pve-devel] proxmox 2018 : add support for "virtual" network and 
network plugins ?

> I have look at ovn documentation and gateway 

Sorry, too much information for me. Please can you explain why we need 
a floating IP? I thought we can use a special static IP on each 
virtual bridge, something like: 

https://networkop.co.uk/blog/2016/10/13/os-dvr/ 

Requires to block some ARP traffic on the vxlan. 

_______________________________________________
pve-devel mailing list
pve-devel@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Reply via email to