Open Stack

Hi, 
I wanted to retrieve the gate's DNS server (or google's 8.8.8.8) in order to check external connectivity, but I've been told that I'm running the risk of getting the Jenkins gate blacklisted by either DNS server. 
It was also brought to my attention, that testing actual external connectivity is not really helpful because my current test actually tests the external server's resolution ability and not the actual Openstack instance. 

So Here's my question: 
Infra - suppose that I can get devstack to configure it's own DNS server into tempest.conf (from resolve.conf), could I get the gate blacklisted for abusing the DNS (either local or google's) 
Neutron/Tempest/Maru - What is there to gain from pinging an external address/url? Could pinging the public network's default GW be enough? Please take into account the fact that we now have CrossTenant test checking L3 routing 

Yair 

----- Original Message -----

From: "Yair Fried" <yfried at redhat.com> 
To: openstack-infra at lists.openstack.org 
Sent: Monday, December 23, 2013 5:57:44 PM 
Subject: [OpenStack-Infra] Fwd: [openstack-dev] [Openstack][qa][Tempest][Network] [Infra]Test for external connectivity 



----- Forwarded Message ----- 
From: "Yair Fried" <yfried at redhat.com> 
To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org> 
Sent: Sunday, December 22, 2013 10:00:52 PM 
Subject: Re: [openstack-dev] [Openstack][qa][Tempest][Network] [Infra]Test for external connectivity 

Hi Guys, 
So, I'm done with my patch: 
https://review.openstack.org/#/c/55146 
1. ping an external IP 
2. ping a url to test the dns 
3. check VM's resolve.conf 
4. change the dns server and recheck resolve.conf 

My issue now (same as before) is that this test cannot be executed (and therefore pass) on the gate unless the gate is configured for external connectivity. 

A. How do I get the neutron gate to allow it's VM external connectivity (i.e. ping 8.8.8.8)? 

Considering Jeremy's comment, I agree that depending on external ip/url introduces an unnecessary point of failure. However IMO, using multiple addresses is not the best way to proceed , I'd rather test against a local node. Therefore: 

B. Can I get the neutron gate to enter it's own (local) DNS server? A local url? 
C. I this a change I can push to some project by myself, or do I need someone to change this for me (infra?)? 

I would really like your input in this matter, as I am in the final stretch of this patch and cannot move any farther by myself 

Regards 
Yair Fried 

----- Original Message -----

From: "Jeremy Stanley" <fungi at yuggoth.org> 
To: openstack-dev at 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 -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 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 

_______________________________________________ 
OpenStack-dev mailing list 
OpenStack-dev at lists.openstack.org 
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev 

_______________________________________________ 
OpenStack-Infra mailing list 
OpenStack-Infra at lists.openstack.org 
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-infra/attachments/20131225/2f24734c/attachment.html>