Current CI pass / failure rates:
Jenkins results – can get history of builds from here:
http://104.130.29.226:8080
Ci watch can show you the Jenkins passes and scroll across to the XenProject CI, you can then easily see tests which the XenProject CI failed where Jenkins passed.
http://ci-watch.tintri.com/project?project=nova&time=7+days
Bob
From: Wg-openstack [mailto:wg-openstack-bounces@xxxxxxxxxxxxxxxxxxxx]
On Behalf Of Lars Kurth
Sent: 05 April 2016 13:37
To: wg-openstack@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [Wg-openstack] Call for Agenda items for this week's meeting
I talked to a few people and propose the following agenda
== 1 year review of WG / CI loop running ==
It's been a year since the CI loop went live: I want to report back to the AB on
* Where do we need more engagement from outside the existing stake-holders (Citrix, Suse, Rackspace, Oracle)
== Stuck Reviews/Known bugs ==
We seem to have a few stuck reviews, e.g.
How important are these. Should they be canned, etc.
== Xen Project CI/Xen Project Openstack Leadership ==
I think we are missing end-to-end ownership/leadership rather than “work item” level activities like fixing bugs or maintaining infrastructure. Stefano was sort
of doing some of it at the beginning, but never quite fully. I have been trying to fill the gap, but am not closely enough engaged in engineering for me to be able to do this well in the long run. With Stefano gone now, we should probably look at this topic.
Perhaps we – the project - need a sort of “Openstack maintainer” or “Openstack coordinator” in a similar manner to how we have a release coordinator/maintainer
for point releases to make sure all the individual things (like bug fixes and CI loop breakages) come together to make a release successful.
* If so, what would be involved in such a community role (activities, time requirement)? It sort of sounds similar to what Jan does for maintenance releases of
Xen.
* Who would be willing (vendor or individual) to step up or be suitable?
* What can we use Credativ for (they could work under the supervision of the “Openstack maintainer/coordinator”) and what cannot be done via Credativ?
I think this is related to, but distinct from, the WG leadership. If we found someone who is willing to step up, I would be willing to hand over WG leadership to
that person also. Am also willing to mentor.
= Stuck reviews/known bugs =
We seem to have a few stuck reviews, e.g.
and Bob is concerned that if known bugs aren’t progressed in a timely manner, or the CI isn’t monitored and degrades, then there is no point in continuing to run
it. Over time it’s likely to become more frustrating to those with the power to disable the CI and unless they see “progress” we can’t really argue that it should remain enabled.
I don't know whether there are any other bugs that may be present in the integration. That are the only outstanding issues I could find
please let me know of any agenda items that you want to discuss. If we don't have anything, let's keep the meeting short.
The following actions are closed
* ACTION: Lars to wait for response from Christian Berendt and then fix extra capitalization
* ACTION: Lars to wait for 2 x 2+
* ACTION: Anthony to see whether the setup is correct
The following actions are ongoing
* ACTION: Lars get Credativ to take ownership and address montoring and backup
** Credativ have been trying to get access to the machines and are working through their TODO list
** Seems Bob's instructions were maybe missing changes to the DNS and thus jenkins.openstack.xenproject.org now points to a non-existant VM
