oVirt.org Access Needed

[Brian Proffitt]

Perhaps I am a bit confused... what is needed here is a cron job that pulls static information from a git repo into a folder on the web server on a daily basis.. and then an alias that points to the browser.html file in that cloned repo via a URL like ovirt.org/stats. This is static content, no packages are being installed on the ovirt.org web server, just data.

This is a long-running project to set up a dashboard that the community needs to see so I can get proper feedback about it. 

If there is a formal ticket process that I have missed, forgive me. I was informed that making this request on this list was the proper way to go.

Thanks,
Brian

----- Original Message -----
From: "R P Herrold" <herrold at owlriver.com>
To: "Dave Neary" <dneary at redhat.com>
Cc: "oVirt infrastructure ML" <infra at ovirt.org>
Sent: Thursday, January 30, 2014 7:05:03 PM
Subject: Re: oVirt.org Access Needed

On Wed, 29 Jan 2014, Dave Neary wrote:

> > and so to some questions for clarification: Is 'bitergia' and 
> > its sub-parts packaged into a form that has landed in Fedora, 
> > or ... where ? 

so, not packaged -- looking at:
	http://metricsgrimoire.github.io/, it in turns points 
to
	https://github.com/metricsgrimoire

with nine component sub-parts (one the web presence and so 
it may be ignored here), so ... to work packaging ...

Setting to teasing the packaging task apart in a CentOS 6 
environment, the first [Bicho] pulls in Requires for:
	python-storm		(epel * )
	python-beautifulsoup	(in Fedora)
		--seemingly also called: python-BeautifulSoup
	python-feedparser	(epel)
	python-dateutil		base OS

* I get consistent local 'make test' failures when the 
mocker checks DB connectivity, on each of the 19 available 
python-storm candidates when trying a rebuild from SRPM.  I 
will be filing a bug

I do not see any open bug on this package, but then neither I 
do see that the package went through the expected accessioning 
review in the Fedora process either [1]

After about 1.5 hr work, I have a rough initial packaging done 
of 'Bicho' -- there is none of the setup doco there yet, and 
the spec file is ... rough --- I also pushed the generating 
script (a 'README') to:
	ftp://ftp.owlriver.com/pub/local/ORC/Bicho/

But obviously doing the remaining ones is in order (this the 
release exteriorly of the 'README' to re-point at the other 
seven (let me know, anyone, if such work is done, and where I 
might pull a revised 'README', and it will save me doing it)

> It's all open source, but the specific configuration files used for
> oVirt are not published at this point.

If there is confidential information to abstract out [I see 
that DB credentials are mentioned in the setup documentation] 
into placefolders that puppet completes, I certainly 
understand, but the rest should be boiler plate.  Seeing a 
worked example or puppet recipes will speed matters
 
> > Is that linked instance pulling real time stats from live 
> > servers or from cached details?

> [the latter]

Wonder why it was sluggish.  There is a caution in Bicho that 
it is quite aggressive in pulling content out of bug trackers, 
and that one has to take steps to slow it down so it does not 
get banned

-- Russ herrold

[1] http://red.ht/1aKw8k5
_______________________________________________
Infra mailing list
Infra at ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra