Logs are difficult to understand after a 3-4 redeployments on the big env
Bug #1397384 reported by
Sergey Galkin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Confirmed
|
Medium
|
Fuel Sustaining | ||
Mitaka |
Won't Fix
|
Medium
|
Fuel Python (Deprecated) | ||
Newton |
Confirmed
|
Medium
|
Fuel Sustaining |
Bug Description
After 3-4 deployment on the cluster with 100 nodes we have logs that difficult to understand
On example we have node with 1 day uptime and 4 deployment
[root@fuel ~]# uptime
16:46:05 up 1 day, 5:07
[root@fuel ~]# ls -l /var/log/remote/ | grep node-81
lrwxrwxrwx 1 root root 18 Nov 27 13:55 10.20.1.130 -> node-81.domain.tld
lrwxrwxrwx 1 root root 18 Nov 28 10:52 10.20.1.82 -> node-81.domain.tld
drwxr-xr-x 4 root root 4096 Nov 28 12:01 node-81.domain.tld
drwxr-xr-x 4 root root 4096 Nov 28 07:35 node-81.
[root@fuel ~]# du -sh /var/log/
11G /var/log/
We should have the way to separate logs (and snapshots) between deployments
summary: |
- Difficult to understand logs after a 3-4 redeploument on the big env + Logs are difficult to understand after a 3-4 redeployments on the big + env |
Changed in fuel: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
assignee: | nobody → Fuel Python Team (fuel-python) |
milestone: | none → 6.1 |
tags: | added: module-shotgun |
Changed in fuel: | |
milestone: | 6.1 → 7.0 |
tags: | added: qa-agree-7.0 |
tags: | added: feature |
tags: | removed: feature |
Changed in fuel: | |
milestone: | 7.0 → 8.0 |
status: | Won't Fix → Confirmed |
no longer affects: | fuel/8.0.x |
tags: | added: area-python |
Changed in fuel: | |
milestone: | 8.0 → 9.0 |
To post a comment you must log in.
There is a BP for this purpose: https:/ /blueprints. launchpad. net/fuel/ +spec/enable- per-environment -snapshots.