[OpenStack-Infra] Hosting your CI logs at dropbox is not acceptable
Anita Kuno
anteaya at anteaya.info
Mon Jun 23 14:50:34 UTC 2014
On 06/23/2014 10:35 AM, Avishay Balderman wrote:
> Hi
> Thanks for your detailed answer.
> Is the following link "valid" for logs hosting?
> (download is not needed, works fine under Chrome and FF)
>
> https://www.dropbox.com/sh/wl2i5kbofvpbgm9/AADj8qye3nU05Y2ZKNwRQNIWa
>
> Thanks
>
> Avishay
Well it isn't open source for starters, and so far while it isn't a
requirment, use of non open source options is discouraged.
Secondly, go to the link yourself and click. See long you you have to
wait until the log file is served, then do the same for the second file.
Now imagine 30 files, some of which you have to go back and look at a
second time. Now imagine a patch where the developer has 5 or more
systems reporting on a given patch (some patches have more but lets go
with 5). All the log hosting systems meet the letter of the requirements
but all are in a different format. The developer has to spend at least
an hour going through 6 different sets of logs (including the OpenStack
set) for one patchset to see where there is a problem. They are going to
get frustrated because this takes too much of their time to figure out
what the problem is. The system that takes so long to render logs is
going to get a complaint, I field the complaint and act on the behalf of
the developer. Then I have to make up a new rule so that third party ci
systems more closely match our system (which the devlopers are used to)
but without saying "do what we do".
So in short, I prefer open source solutions and I would get frustrated
waiting for the log files to render.
Thanks Avishay,
Anita.
>
> -----Original Message-----
> From: Anita Kuno [mailto:anteaya at anteaya.info]
> Sent: Monday, June 23, 2014 5:16 PM
> To: Avishay Balderman
> Cc: Samuel Bercovici; Izik Penso; openstack-infra at lists.openstack.org
> Subject: Re: Hosting your CI logs at dropbox is not acceptable
>
> On 06/22/2014 07:10 AM, Avishay Balderman wrote:
>> Hi Anita
>> Can you please point us to the specification explaining how the 3rd party test results should be hosted?
>>
>> What is the main feature for the hosting?
>> As far as we understand the files should be visible via browser (Chrome,FF).
>>
>> Anything else?
>>
>> Thanks
>>
>> Avishay
>>
> Hi Avishay:
>
> In opensource we have less of an emphasis on specifications and more of an emphasis on discussion. Yes I can point you to at least one discussion so far on log hosting and invite you and members of your group to more discussions on the topic.
> http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2014-06-19.log
> timestamp 2014-06-19T13:49:43
>
> Currently we have this documentation around third party testing
> requirements: http://ci.openstack.org/third_party.html
> Also in light of recent discussions there are two patches in review for changes to that document: https://review.openstack.org/#/c/101013/ and https://review.openstack.org/#/c/101227/
>
> We also have a weekly third party meeting that takes place on Mondays at
> 1800 utc in the #openstack-meeting channel on the freenode network where we discuss current practices, any questions, identify issues and work to address them as well as share information among openstack programs and third party ci systems: https://wiki.openstack.org/wiki/Meetings/ThirdParty
>
> Opensource is a living entity and the more you participate in the discussions that result in documentation, the more you have a say in what happens and the better informed you are.
>
> The main feature for the hosting is that it most closely matches the workflow that the developers already use with gerrit. The more familiar you are with gerrit, the easier it is to get hosting right. Now we will create and amend documents as we need to to refine communication around hosting of logs (as well as all other aspects of third party ci) but the docs will only ever be looking to address behaviour that we never imagined anyone would do (or omit) in the first place. I strongly encourage you to participate in the third party meetings as well as in the irc channel for the project you are testing to talk with the developers who are getting the comments from your system on their patches and hear from them what you system needs to do to make them happy.
>
> Also if I email you in future and cc the openstack-infra mailing list, please cc the openstack-infra mailing list in your reply. I have done so in my reply.
>
> Thanks Avishay, I hope to see you or another representative of your third party ci account in the third party meeting in a few hours, Anita.
>
>>
>> -----Original Message-----
>> From: Anita Kuno [mailto:anteaya at anteaya.info]
>> Sent: Thursday, June 19, 2014 6:39 PM
>> To: OpenStack3RDPartyTesting; openstack-infra at lists.openstack.org
>> Subject: Re: Hosting your CI logs at dropbox is not acceptable
>>
>> On 06/19/2014 10:08 AM, Anita Kuno wrote:
>>> Hello:
>>>
>>> Your system, Radware 3rd Party Testing, has logs hosted at a dropbox
>>> account. This is not acceptable.
>>>
>>> Further, your logs are a tarball which must be downloaded. This also
>>> is unacceptable.
>>>
>>> https://review.openstack.org/#/c/98899/
>>>
>>> Your logs must be hosted on a secure server that allows the logs to
>>> be accessible via a browser. Firefox and chrome must be supported, at
>>> the very least.
>>>
>>> Please respond to this email as soon as you receive it to acknowledge
>>> its receipt. Please disable your system until you can make the
>>> required changes.
>>>
>>> It is preferred if someone is available on irc to field questions
>>> about your account. Please have that person make contact with me on
>>> irc, my nickname is anteaya.
>>>
>>> Thank you,
>>> Anita.
>>>
>> This email generated a fast response in irc:
>> http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack
>> -infra.2014-06-19.log
>> timestamp 2014-06-19T14:23:54
>>
>> by IzikPenso
>>
>> Izik decided to disable the system to fix the log situation.
>>
>> Thank you for the quick response, Izik, Anita.
>>
>
More information about the OpenStack-Infra
mailing list