Open Stack

You can't get rid of the "External" address as it's used to direct return
traffic to the right router node.  DVR as implemented is really just a
local NAT gateway per physical compute node.  The outside of your NAT needs
to be publicly unique, so it needs it's own address.  Some SDN solutions
can provide a truly distributed router model, because they globally know
the inside state of the NAT environment, and can forward packets back to
the internal source properly, regardless of which distributed forwarder
receives the incoming "external" packets.

If the number of external addresses consumed is an issue, you may consider
the dual gateway HA model instead of DVR.  This uses classic multi-router
models where one router takes on the task of forwading packets, and the
other device just acts as a backup.  You do still have a software
bottleneck at your router, unless you then also use one of the plugins that
supports hardware L3 (last I checked, Juniper, Arista, Cisco, etc. all
provide an L3 plugin that is HA capable), but you only burn 3 External
addresses for the router (and 3 internal network addresses per tenant side
interface if that matters).

Hope that clarifies a bit,
Robert

On Tue, Jan 26, 2016 at 4:14 AM, Carl Baldwin <carl at ecbaldwin.net> wrote:

> On Thu, Jan 14, 2016 at 2:45 AM, Tomas Vondra <vondra at czech-itc.cz> wrote:
> > 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?
>
> Regardless of DVR, a Neutron router burns one IP per virtual router
> which it uses to SNAT traffic from instances that do not have floating
> IPs.
>
> When you use DVR, an additional IP is consumed for each compute host
> running an L3 agent in DVR mode.  There has been some discussion about
> how this can be eliminated but no action has been taken to do this.
>
> > 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.
>
> I'm not sure if it is possible to avoid burning these IPs at this
> time.  Maybe someone else can chime in with more detail.
>
> Carl
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160127/0f432924/attachment.html>