Perhaps not an obvious area for immediate improvement in Spacewalk, but what are
the limiting factors for the File Preservation lists used during kickstart? Is
the 1Mb maximum an arbitrary hard coded limit? Would it be feasible to allow
configuration of this limit?
I ask because I'm running a Satellite system managing a grid processing
environment. We regularly make use of the re-provisioning function of
Satellite/Spacewalk, but would love the ability to preserve some of the
performance log files (RRD's) and job history logs between rebuilds.
It would be great if I could point the file preservation storage area at a
specific directory - which I would then be responsible for. If I blow the
capacity for this area of disk while re-provisioning a few hundred grid servers
. . . this would be my own lookout.
Any thoughts before I start poking around in the code? Am I barking up the
wrong tree entirely?
Cheers
Duncan
_______________________________________________
Spacewalk-devel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-devel
