pcp
[Top] [All Lists]

Re: Service advertising versus QA

To: Nathan Scott <nathans@xxxxxxxxxx>
Subject: Re: Service advertising versus QA
From: Dave Brolley <brolley@xxxxxxxxxx>
Date: Thu, 29 May 2014 10:08:11 -0400
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <1726157269.16845669.1401321783766.JavaMail.zimbra@xxxxxxxxxx>
References: <410753304.16136418.1401248705845.JavaMail.zimbra@xxxxxxxxxx> <5386075A.70505@xxxxxxxxxx> <1726157269.16845669.1401321783766.JavaMail.zimbra@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
On 05/28/2014 08:03 PM, Nathan Scott wrote:
I think that the tests should be able to
tolerate randomly discovered services on other machines. I ran into the
same problem when working up a test for the new active probing. The
solution ended up being more aggressive filtering. I'll have a look at
these tests from the same point of view.
OK, sounds good.  In my case here, with the Avahi tests there's remote
IP addresses in the output, so the qa/common.filter _host_to_ipaddr()
function might prove handy - I guess we could pick out the local host
IP that way, and discard all others?  ( aaand that function looks like
it needs some IPv6 love :] ).

Since:

- there could be an indeterminate number of remote services discovered
- the host machine could have more than one active network interface
- pmproxy and/or pmwebd services may or may not be running on the local machine at the time of the test

I went the route of filtering out the urls completely and relying on the headers (e.g. "Discovered pmcd servers") and the exit code from pmfind for indication that results were found.

Dave

<Prev in Thread] Current Thread [Next in Thread>