On 08/05/13 07:26 PM, Gawlas, Julius wrote:
Lucas,
It will be 4:40 my time so I will skip this time;
I'm considering marking the Weekly hangout on alternate times every
week, so it's easier for folks on other time zones, such as PST. Stay
tuned :)
Few generic comments:
1) Reservations: we are planning to add time based components so they will
optionally kick in/release at appointed time, let me know what other pieces
would be useful and are missing
I was talking to Cleber and I'll write user stories of how I envision
the reservation functionality could work.
2) > Our next challenge will be to tackle how to make the autotest server more
resilient against failures, such as:...
This is great; In addition to what you state, we have something concrete in
that area: our team is facing immediate problem - when default cobbler profile
is messed up system cannot be repaired and it will be in 'Repair failed' state
forever - likely pull request coming your way
Excellent!
3) We would like to have ability to define proper autotest add-on that will
have some db, some django code and front end, just like TCM; To do that
properly there are few changes to basic framework that would make it easier. If
we do that ground work we have some add ons that we can can push upstream.
We had long ago a project called autotest planner, that was another gwt
app with the rpc server (django) backend, started by the folks @google.
It wasn't finished and they dropped their plans of completing it.
Later on, we had no option other than removing the app from the code
base. It's still in revision control history, though.
_______________________________________________
Virt-test-devel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/virt-test-devel
