Open Stack

Hi,

doesn't matter how /var partition is big, diagnostic snapshot still 
could occupy all its space if there are lots of logs on slave nodes. 
Although, we can try to control disk space usage by snapshot in shotgun, 
but IMHO it's much safer to keep all related to logs staff away from 
critical system files, so I'm voting for 2nd (b) option. By the way it 
will allow us to use hard links for fast copying of files before 
creating tarball, because one partition for storing logs and snapshot 
will be used.

Thanks!

On 12.01.16 12:47, Maciej Kwiek wrote:
> Hi!
>
> I need some advice on how to tackle this issue. There is a bug [1] 
> describing the problem with creating a diagnostic snapshot. The issue 
> is that /var/log has 100GB available, while /var (where diagnostic 
> snapshot is being generated - /var/www/nailgun/dump/fuel-snapshot 
> according to [2]) has 10GB available, so dumping the logs can be an 
> issue when logs size exceed free space in /var.
>
> There are several things we could do, but I am unsure on which course 
> to take. Should we
> a) Allocate more disk space for /var/www (or for whole /var)?
> b) Make the snapshot location share the diskspace of /var/log?
> c) Something else? What?
>
> Please share your thoughts on this.
>
> Cheers,
> Maciej Kwiek
>
> [1] https://bugs.launchpad.net/fuel/+bug/1529182
> [2] 
> https://github.com/openstack/fuel-web/blob/2855a9ba925c146b4802ab3cd2185f1dce2d8a6a/nailgun/nailgun/settings.yaml#L717
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-- 
Artem Panchenko
QA Engineer

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160112/b06a89da/attachment.html>