For 4.0, the new image upload feature is going to be added, and as some of
you already know we've created a new project (
https://gerrit.ovirt.org/#/admin/projects/ovirt-imageio) containing 2 small
applications and a common library.
- one of the applications (called "ovirt-imageio-daemon") is supposed to
run in a VDSM host.
- Other application (called "ovirt-imageio-proxy") is supposed to run as a
proxy, could be on a standalone host or in the engine's host.
My question for you is, what else do we need except for a Makefile that
builds rpms, for the project to be ready to be released to public repos?
David Caro Estevez created OVIRT-507:
Summary: Can't move jira bugs from blocked status
Project: oVirt - virtualization made easy
Issue Type: Bug
Reporter: David Caro Estevez
Since a few days ago, if an issue is is blocked status, you can't (at least I can't) move it to any other status, not even closing it so they remain there, for example:
This message was sent by Atlassian JIRA
Following the successful runs on the old patch jenkins job on a few
projects (mostly engine + vdsm) we are enabling the script to run on ALL
projects hosted on gerrit.ovirt.org.
As a starting point, as we did for ovirt-engine & vdsm, the limits were
raised back to : 
WARN: 90 Days
ABANDON: 360 Days.
If you have old patches that were untouched for the above dates, you should
expect an email asking you to abandon or update the patch.
Since there might be a lot of projects alerting, we've also added the
project name to the email subject to make it easier to differ between
The script will be activated next week on Sunday.
I would like to thank Vishnu to wrote this script and added the new
functionally in a very short time!
 And will continue to be lowered periodically towards a reasonable limit
of a 30-60 days.
Content-Type: text/plain; charset="UTF-8"
Le mercredi 27 avril 2016 =C3=A0 17:26 +0530, Kaushal M a =C3=A9crit :
> On Wed, Apr 27, 2016 at 5:21 PM, Michael Scherer <mscherer(a)redhat.com> wr=
> > Le mercredi 27 avril 2016 =C3=A0 14:39 +0300, Eyal Edri a =C3=A9crit :
> >> Excellent post-mortem!
> >> Do you think its worth adding mirrors to gluster repos like oVirt is d=
> >> 
> >>  http://ovirt-infra-docs.readthedocs.org/en/latest/General/Mirror.h=
> > That could be a solution.
> > But we have the ressources to host a mirror ourself in the DC, it just
> > need a ip address, and a migration of servers (which is taking a awful
> > lot of time to happen :/ ).
> > One issue we would have with a mirror is on the download stats.
> > This and the need to have a mirrorlist, not sure how that's done on
> > dnf/yum side theses days.
> Someone recently offered to mirror download.gluster.org (I need to dig
> archives to find out who exactly). Didn't we take up their offer?
Do not seems so.
But my question regarding the download stats is still unaswered. Given
how critical they seems to be, I would like to be sure we have a plan.
A mirror is the first step, but then:
- how do we signal to people to use the mirror and the main server
- are we ok with the decrease of download by a unspecified amount of
data on the download stats side
- who will edit the website for the change
Sysadmin, Community Infrastructure and Platform, OSAS
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
-----END PGP SIGNATURE-----