[Ovirt-devel] Limiting node writes...

Jeff Schroeder jeffschroed at gmail.com
Wed Jun 25 12:49:43 UTC 2008


On Wed, Jun 25, 2008 at 5:40 AM, Darryl L. Pierce <dpierce at redhat.com> wrote:
> Objective:
> Reduce the amount of writing done to the managed node's filesystem. Since
> the managed node is run on an in-memory file system, excessive writes to
> such things as log files will eventually cause an out-of-memory condition.
> Our goal is to limit the amount of writes.
>
> Discussion:
> Initially, rotating logs every hour and deleting all old logs is the likely
> first pass.
>
> A usable feature would be for the WUI to push down (during the identify
> phase, maybe?) a threshold for when logs should be aggressively deleted.
> Then the admin can decide to hold onto logs until disk space hits some
> threshold and then start throwing away old logs. That way some history can
> be viewed if needed.
>
> In future, a more preferable solution would be to have the oVirt server
> collect logging information for all managed nodes centrally. However, this
> would need to use an encrypted pipe to send the data.

Why not use a standard mechanism such as syslog(3)? Fedora already ships
rsyslog since F8 and it supports encrypted connections via tls or ssl.

Would adding rsyslog be too much bloat?

-- 
Jeff Schroeder

Don't drink and derive, alcohol and analysis don't mix.
http://www.digitalprognosis.com




More information about the ovirt-devel mailing list