Making diagnostic snapshot for a particular environment is a good idea. But
the issue is still there.
We often have the situation when user actually doesn't care of old logs at
all. He downloads ISO, installs it and tries various installation options
(Ubuntu, Centos, HA, Ceph, etc.). Sooner or
When nailgun remove a node it can gzip all the logs of this node to a
special file, like: /var/log/remote/archive/node-3-timestamp.tgz And
logrotate can keep these files for month, then delete them.
Master node health monitor is another big discussion.
On Thu, Jun 26, 2014 at 1:25 PM, Vladimir
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
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
Yeah, I thought about diagnostic snapshot too. Maybe it would be better to
implement per-environment diagnostic snapshots? I.e. add diagnostic
snapshot generate/download buttons/links in the environment actions tab.
Such snapshot would contain info/logs about Fuel master node and nodes
assigned to
Hi guys,
What about our diagnostic snapshot?
I mean we're going to make snapshot of entire /var/log and obviously
this old logs will be included in snapshot. Should we skip theem or
such situation is ok?
- Igor
On Tue, Jun 24, 2014 at 5:57 PM, Aleksandr Didenko adide...@mirantis.com
wrote:
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
Hello,
@Aleks, it's a good idea to make snapshot per environment, but I think
we can keep functionality to make snapshot for all nodes at once too.
- Igor
On Tue, Jun 24, 2014 at 6:38 PM, Aleksandr Didenko adide...@mirantis.com
wrote:
Yeah, I thought about diagnostic snapshot too. Maybe it
Yes, of course, snapshot for all nodes at once (like currently) should also
be available.
On Tue, Jun 24, 2014 at 7:27 PM, Igor Kalnitsky ikalnit...@mirantis.com
wrote:
Hello,
@Aleks, it's a good idea to make snapshot per environment, but I think
we can keep functionality to make snapshot