[Openstack-operators] Packet flow in Neutron

Jonathan Proulx jon at jonproulx.com
Tue Jan 28 15:14:17 UTC 2014

On Tue, Jan 28, 2014 at 7:49 AM, gustavo panizzo <gfa> <gfa at zumbi.com.ar>wrote:

> b
> you can confirm checking arp tables on both vm1 and vm2

yes B.

Packets only need to transit through the networking node if it is doing
routing with or without NAT for them. I believe this includes SNAT for
floating IPs, but I don't use floating IPs so not 100% sure.

I have (most of) my neutron subnets configured to use an existing external
router so none of the traffic is bottlenecked by the networking host nor is
i ta single point of failure for running instances.  Though if it goes away
so does the control plane so I can't start anything new or make any
changes, so what I have is not a true HA config.


> 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333
> sent from mobile
> Miguel A Diaz Corchero <miguelangel.diaz at externos.ciemat.es> wrote:
>> Hi
>> Regarding this schema of Neutron [1], could you confirm which packet flow
>> is the correct?
>> We are considering that a virtual machine (VM1) sends packets to VM2, but
>> both VMs are located in different compute nodes (PM1 and PM2). Both VMs are
>> in the same virtual network.
>> Which is the flow, a or b?
>> a) VM1 -> PM1 -> Networking node -> PM2 -> VM2
>> b) VM1 -> PM1 -> PM2 -> VM2
>> Thanks
>> Miguel.
>> [1]
>> http://docs.openstack.org/havana/install-guide/install/apt/content/section_networking-provider-router_with-provate-networks.html
>> --
>> *Miguel Angel Díaz Corchero*
>> *System Administrator / Researcher*
>> *c/ Sola nº 1; 10200 TRUJILLO, SPAIN*
>> *Tel: +34 927 65 93 17 Fax: +34 927 32 32 37 <%2B34%20927%2032%2032%2037>*
>> [image: CETA-Ciemat logo] <http://www.ceta-ciemat.es/>
>>  ---------------------------- Confidencialidad: Este mensaje y sus
>> ficheros adjuntos se dirige exclusivamente a su destinatario y puede
>> contener información privilegiada o confidencial. Si no es vd. el
>> destinatario indicado, queda notificado de que la utilización, divulgación
>> y/o copia sin autorización está prohibida en virtud de la legislación
>> vigente. Si ha recibido este mensaje por error, le rogamos que nos lo
>> comunique inmediatamente respondiendo al mensaje y proceda a su
>> destrucción. Disclaimer: This message and its attached files is intended
>> exclusively for its recipients and may contain confidential information. If
>> you received this e-mail in error you are hereby notified that any
>> dissemination, copy or disclosure of this communication is strictly
>> prohibited and may be unlawful. In this case, please notify us by a reply
>> and delete this email and its contents immediately.
>> ----------------------------
>> ------------------------------
>> OpenStack-operators mailing list
>> OpenStack-operators at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
> _______________________________________________
> 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/20140128/4372b5d8/attachment.html>

More information about the OpenStack-operators mailing list