[openstack-dev] [Openstack][qa][Tempest][Network] Test for external connectivity

Salvatore Orlando sorlando at nicira.com
Thu Nov 21 12:59:16 UTC 2013

Forgive my ignorance, but I would like to make sure that packets generated
from Openstack instances on neutron private networks will actually be able
to reach public addresses.

In its default configuration the traffic from the OS instance is SNATed and
the SRC IP will be rewritten to an address in the neutron's public network
range ( by default). If the OS instance is trying to reach a
public server like www.google.com, then, assuming ip_forward is enabled on
the devstack-gate VM,  the traffic should be forwarded via the default
route with a src IP of

If the above is correct, will it be possible for the IP traffic to be
correctly routed back to the Openstack instance?


On 20 November 2013 23:17, Jeremy Stanley <fungi at yuggoth.org> wrote:

> On 2013-11-20 14:07:49 -0800 (-0800), Sean Dague wrote:
> > On 11/18/2013 02:41 AM, Yair Fried wrote:
> > [...]
> > > 2. add fields in tempest.conf for
> > >      * external connectivity = False/True
> > >      * external ip to test against (ie
> >
> > +1 for #2. In the gate we'll need to think about what that address
> > can / should be. It may be different between different AZs. At this
> > point I'd leave the rest of the options off the table until #2 is
> > working reliably.
> [...]
> Having gone down this path in the past, I suggest the test check for
> no fewer than three addresses, sending several probes to each, and
> be considered successful if at least one gets a response.
> --
> Jeremy Stanley
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131121/54996884/attachment.html>

More information about the OpenStack-dev mailing list