On 11/18/2013 08:19 PM, Salvatore Orlando wrote:
Basically I think we can assume test machines have access to the
Internet
IMO, we should assume test machines doesn't. It's a too dangerous
assumption to make.
I assume you want
to check servers such as www.google.com http://www.google.com are
than three addresses -- Why?
- Original Message -
From: Jeremy Stanley fu...@yuggoth.org
To: openstack-dev@lists.openstack.org
Sent: Thursday, November 21, 2013 12:17:52 AM
Subject: Re: [openstack-dev] [Openstack][qa][Tempest][Network] Test for
external connectivity
On 2013-11-20 14:07:49
On 2013-11-28 06:46:27 -0500 (-0500), Yair Fried wrote:
[...]
4. Jeremy Stanley - test check for no fewer than three addresses
-- Why?
If your tests try to communicate with addresses which are truly
outside your own network, and thus outside your sphere of control,
you don't want them failing
On 2013-11-21 13:59:16 +0100 (+0100), Salvatore Orlando wrote:
[...]
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 (172.24.4.224/28 by default). If
the OS instance is trying to reach
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
, November 19, 2013 7:31 PM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Rami Vaknin
Subject: Re: [openstack-dev] [Openstack][qa][Tempest][Network] Test for
external connectivity
Hi Salvatore, et al,
On Mon, Nov 18, 2013 at 9:19 PM, Salvatore Orlando
sorla
On 11/18/2013 02:41 AM, Yair Fried wrote:
I'm editing tempest/scenario/test_network_basic_ops.py for external
connectivity as the TODO listed in its docstring.
the test cases are for pinging against external ip and url to test
connectivity and dns respectivly.
since default deployement
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 8.8.8.8)
+1 for #2. In the gate we'll need to think about what that
Hi Salvatore, et al,
On Mon, Nov 18, 2013 at 9:19 PM, Salvatore Orlando sorla...@nicira.comwrote:
Hi Yair,
I had in mind of doing something similar. I also registered a tempest
blueprint for it.
Basically I think we can assume test machines have access to the Internet,
but the devstack
On 11/18/2013 11:41 AM, Yair Fried wrote:
I'm editing tempest/scenario/test_network_basic_ops.py for external
connectivity as the TODO listed in its docstring.
the test cases are for pinging against external ip and url to test
connectivity and dns respectivly.
since default deployement
Hi Yair,
I had in mind of doing something similar. I also registered a tempest
blueprint for it.
Basically I think we can assume test machines have access to the Internet,
but the devstack deployment might not be able to route packets from VMs to
the Internet.
Being able to ping the external
11 matches
Mail list logo
