On Mon, 15.07.13 17:21, Stephen John Smoogen (smooge@xxxxxxxxx) wrote: > On 15 July 2013 16:39, Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> wrote: > > > I'm putting this in a separate thread so it doesn't get buried in the > > enthusiasm over the other one. :) > > > > Here's our dilemma (Or trilemma?) in the Fedora Cloud SIG. > > > > 1) Double-logging is a significant waste of scarce resources > > > > > Well I can see IO resources as being scarse but how scarse are we really > talking? [There comes a point where cutting down the size of an image isn't > going to help a bit because it takes up the same number of sectors on a > disk whether its X Mb or Y Mb. Well, the duplicate log files will be accounted for every instance of a container/VM. The more containers you run, the more often you pay for it. This is different than just having one package installed too much in the image, which can be shared among instances. Written log files cannot. > > 3) If we leave out rsyslog, we lose text /var/log/messages ... > > ... which is less of a big deal from the server-room emergency-analysis > > angle that might apply in the general case ... > > ... but it's a pretty big change from the rest of Fedora, and we'd > > prefer not to do that just for the cloud image. > > > > > So if I am going to spin up a lot of boxes.. I am going to want those logs > not on one box but transmitted to a central location. Does journald have > remote logging capabilities (will it?) Well, it currently doesn't have full featured solution. However, it has some bits and pieces around to make it work nicely for some usecases: if you share /var/log/journal between multiple hosts or containers, then you can use "journalctl -m" to view them all at the same time and nicely interleaved. Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
