Open Stack

Hi Jeremy, 

We need this change in tempest test for our testing system to execute the test successfully.
https://review.openstack.org/#/c/68190/

We tested the change with HAPROXY and with our lbaas solution and it works for both. 
Should we wait for this change to be merged, until we enable the system ?
Or can we enable the system, modify the test locally and run it ? 

The other problems that were before, start message and URL to logs, are resolved now.   

Thanks, 
Izik Penso.
Radware.

-----Original Message-----
From: Izik Penso 
Sent: Thursday, January 16, 2014 9:43 PM
To: Jeremy Stanley; OpenStack3RDPartyTesting
Cc: openstack-infra at lists.openstack.org
Subject: RE: [OpenStack-Infra] Radware's service account request for third party testing

True, I'll let you know when it all fixed.

Izik Penso.
Radware.

-----Original Message-----
From: Jeremy Stanley [mailto:fungi at yuggoth.org] 
Sent: Thursday, January 16, 2014 8:54 PM
To: Izik Penso; OpenStack3RDPartyTesting
Cc: openstack-infra at lists.openstack.org
Subject: Re: [OpenStack-Infra] Radware's service account request for third party testing

On 2014-01-16 16:45:46 +0000 (+0000), Izik Penso wrote:
> Working, All good.

Actually, not quite so good. Mark McClain (Neutron PTL) and others have asked me to temporarily remove all access for that service account since it's leaving messages on changes when it starts testing (as opposed to only when it finishes) and is leaving URLs to unreachable systems or no useful information at all. This was the example brought to my attention just now...

    https://review.openstack.org/66970

Let us know when these issues have been corrected so we can try reenabling it. Thanks!
--
Jeremy Stanley