Hi Tomas, Actually the networking nodes, and in a DVR scenario the compute nodes, don't need a public IP assigned to the node itself. All they need is a networking interface connected to the "public" network. Only tenant routers set as a gateway consume one public IP address each as overhead. You cannot get around each tenant gateway router consuming an extra public IP address itself as far as I know. Does that answer your question? Cheers, Tom 2016-01-20 13:48 GMT+01:00 Tomas Vondra <vondra at czech-itc.cz>: > Hi! > I have just deployed an OpenStack Kilo installation with DVR and expected > that it will consume one Public IP per network node as per > http://assafmuller.com/2015/04/15/distributed-virtual-routing-floating-ips/ > , > but it still eats one per virtual Router. > What is the correct behavior? > Otherwise, it works as a DVR should according to documentation. There are > router namespaces at both compute and network nodes, snat namespaces at the > network nodes and fip namespaces at the compute nodes. Every router has a > router_interface_distributed and a router_centralized_snat with private > IPs, > however the router_gateway has a public IP, which I would like to getr id > of > to increase density. > Thanks > > > _______________________________________________ > Mailing list: > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack at lists.openstack.org > Unsubscribe : > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack/attachments/20160120/244f88a5/attachment.html>