What about to gzip old logs by Astute and place them to a special directory, which will be managed under logrotate.d, and logrotate will remove untouched logs after 1 month.
On Tue, Jun 24, 2014 at 6:57 PM, Aleksandr Didenko <adide...@mirantis.com> wrote: > Hi, > > If user runs some experiments with creating/deleting clusters, then taking > care of old logs is under user's responsibility, I suppose. Fuel configures > log rotation with compression for remote logs, so old logs will be gzipped > and will not take much space. > > In case of additional boolean parameter, the default value should be > "0-don't touch old logs". > > -- > Regards, > Alex > > > On Tue, Jun 24, 2014 at 4:07 PM, Vladimir Kozhukalov < > vkozhuka...@mirantis.com> wrote: > >> Guys, >> >> What do you think of removing node logs on master node right after >> removing node from cluster? >> >> The issue is when user do experiments he creates and deletes clusters and >> old unused directories remain and take disk space. On the other hand, it is >> not so hard to imaging the situation when user would like to be able to >> take a look in old logs. >> >> My suggestion here is to add a boolean parameter into settings which will >> manage this piece of logic (1-remove old logs, 0-don't touch old logs). >> >> Thanks for your opinions. >> >> Vladimir Kozhukalov >> >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStackfirstname.lastname@example.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > _______________________________________________ > OpenStack-dev mailing list > OpenStackemail@example.com > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Andrey Danin ada...@mirantis.com skype: gcon.monolake
_______________________________________________ OpenStack-dev mailing list OpenStackfirstname.lastname@example.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev