oVirt infra progress scoreboard

[Eyal Edri]

I agree, we are in the progress of making the ovirt jira usable using email
tickets like eng-ops / it are doing.
I believe this will create volume of tickets as we'll defer any request to
that email.

we can start adding EPICs of major items we're working on to the JIRA for
starts and later create nice graphs and reports on status from it.

example of EPICs:
 - migration of production environment to PHX dc  (sub task -
jenkins,foreman,mailman,etc..) (sub-task - complete puppetizing production
infra)
 - adding monitoring to services
 - moving & adding missing docs to sphinx/rtd
 - optimize jenkins throughput and ability to handle more load (by removing
un-needed jobs, moving to faster storage,etc..)
 - automate and improve jenkins slaves creation
 - backup & drp plan for ovirt services

and i'm sure there is more i forgot about.
any volunteers to start creating those in JIRA?

e.


On Mon, Nov 23, 2015 at 12:17 PM, David Caro <dcaro at redhat.com> wrote:

> On 11/23 10:58, Sandro Bonazzola wrote:
> > On Mon, Nov 23, 2015 at 9:11 AM, Barak Korren <bkorren at redhat.com>
> wrote:
> >
> > > Hi all,
> > >
> > > I think it is no secret that the oVirt infra is a work-in-progress.
> > > We seem to have multiple major goals that require multiple
> > > relatively-independent efforts to achive. Example of such goals are
> > > "Puppetizing the infra" which requires writing Puppet manifests for
> > > each and every service and "Migrating to CI standards" which requires
> > > effor from each individual oVirt project.
> > >
> > > I was wondering if it would be useful for us to have a set of tables
> > > posted somewhere tracking the progress towards the major goals.
> > >
> > > I think it can be very useful as a place to point new team members to
> > > and also to provide high-level but detailed view of where we stand.
> > >
> > > WDYT?
> > >
> >
> > Isn't https://ovirt-jira.atlassian.net enough?
>
> For me yes, maybe add a 'nicer graphs' and really start using it to track
> progress, but imo that's one of the best solutions for that problem (given
> that
> we are already going to use it)
>
> >
> >
> >
> > >
> > > --
> > > Barak Korren
> > > bkorren at redhat.com
> > > RHEV-CI Team
> > > _______________________________________________
> > > Infra mailing list
> > > Infra at ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/infra
> > >
> >
> >
> >
> > --
> > Sandro Bonazzola
> > Better technology. Faster innovation. Powered by community collaboration.
> > See how it works at redhat.com
>
> > _______________________________________________
> > Infra mailing list
> > Infra at ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
>
>
> --
> David Caro
>
> Red Hat S.L.
> Continuous Integration Engineer - EMEA ENG Virtualization R&D
>
> Tel.: +420 532 294 605
> Email: dcaro at redhat.com
> IRC: dcaro|dcaroest@{freenode|oftc|redhat}
> Web: www.redhat.com
> RHT Global #: 82-62605
>
> _______________________________________________
> Infra mailing list
> Infra at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>


-- 
Eyal Edri
Supervisor, RHEV CI
EMEA ENG Virtualization R&D
Red Hat Israel

phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/infra/attachments/20151125/03017537/attachment.html>