<font size=2 face="sans-serif">I think that it would also be a good idea
to have the option to let the CI maintainers add some useful information
on the current status.</font><br><font size=2 face="sans-serif">It is very helpful to know that the
CI system is under maintenance which is the reason why it hasn't been reporting
for the last week or so... </font><br><br><font size=2 face="sans-serif">Isaac Beckman</font><br><font size=2 face="sans-serif"><br>Office: +972-3-6897874</font><br><font size=2 face="sans-serif">Fax: +972-3-6897755</font><br><font size=2 face="sans-serif">Mobile: +972-50-2680180<br>Email: isaacb@il.ibm.com</font><br><font size=2 face="sans-serif"><br>IBM XIV, Cloud Storage Solutions (previously HSG)</font><br><a href=www.ibm.com/storage/disk/xiv><font size=2 color=blue face="sans-serif">www.ibm.com/storage/disk/xiv</font></a><font size=2 face="sans-serif"><br></font><img src=cid:_1_7B454E087B454A0800273F0AC22580AB width=152 height=68 style="border:0px solid;"><font size=2 face="sans-serif"> </font><br><br><br><br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"Jay S. Bryant"
<jsbryant@electronicjungle.net></font><br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">"OpenStack Development
Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org></font><br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">16/01/2017 21:56</font><br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [openstack-dev]
[all] Improving Vendor Driver Discoverability</font><br><hr noshade><br><br><br><tt><font size=2><br><br>On 01/16/2017 12:19 PM, Jonathan Bryce wrote:<br>>> On Jan 16, 2017, at 11:58 AM, Jay S. Bryant <jsbryant@electronicjungle.net>
wrote:<br>>><br>>> On 01/13/2017 10:29 PM, Mike Perez wrote:<br>>>> The way validation works is completely up to the project team.
In my research<br>>>> as shown in the Summit etherpad [5] there's a clear trend
in projects doing<br>>>> continuous integration for validation. If we wanted to we
could also have the<br>>>> marketplace give the current CI results, which was also requested
in the<br>>>> feedback from driver maintainers.<br>>> Having the CI results reported would be an interesting experiment.
I wonder if having the results even more publicly reported would result
in more stable CI's. It is a dual edged sword however. Given the
instability of many CI's it could make OpenStack look bad to customers
who don't understand what they are looking at. Just my thoughts on
that idea.<br>> That’s very useful feedback. Having that kind of background upfront
is really helpful. As we make updates on the display side, we can take
into account if certain attributes are potentially unreliable or at a higher
risk of showing instability and have the interface better support that
without it looking like everything is failing and a river of red X’s.
Are there other things that might be similar?<br>><br>> Jonathan<br>><br>Jonathan,<br><br>Glad to be of assistance.<br><br>I think reporting some percentage of success might be the most accurate
<br>way to report the CI results. Not necessarily flagging it good or
bed <br>but leave it for the consumers to see and compare. Also combine that
<br>with Anita's idea of when the CI last successfully reported and I think
<br>it could give a good barometer for consumers. Our systems all have their
<br>rough times so we need to avoid a 'snapshot in time' view and provide <br>more of a 'activity over time' view. Third party CI is a good barometer
<br>of community activity and attention, but not always 100% accurate.<br><br>Obviously there will need to be some information included with the <br>results explaining what they are and helping guide interpretations.<br><br>Jay<br><br>><br>> __________________________________________________________________________<br>> OpenStack Development Mailing List (not for usage questions)<br>> Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>> </font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><tt><font size=2>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></tt></a><tt><font size=2><br><br><br>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br></font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><tt><font size=2>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></tt></a><tt><font size=2><br></font></tt><br><br><BR>