Fix log rotation to use dateext
Bug #1848407 reported by
Haw Loeung
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Content Cache Charm |
Fix Released
|
Undecided
|
Haw Loeung | ||
Bug Description
Hi,
Logs are currently using the default .1, .2, .3, etc. This makes it harder to archive for long term (e.g. to swift). Let's fix it to use dateext.
Also, let's make the retention time configurable and exposed as a charm option.
Related branches
~hloeung/content-cache-charm:master
- Joel Sing (community): Approve (+1)
- Haw Loeung: Needs Resubmitting (ptal)
- Canonical IS Reviewers: Pending requested
-
Diff: 254 lines (+144/-4)9 files modifiedconfig.yaml (+5/-0)
lib/utils.py (+24/-0)
reactive/content_cache.py (+22/-4)
tests/unit/files/haproxy-dateext-logrotate.conf (+12/-0)
tests/unit/files/haproxy-logrotate.conf (+11/-0)
tests/unit/files/nginx-dateext-logrotate.conf (+19/-0)
tests/unit/files/nginx-logrotate.conf (+18/-0)
tests/unit/test_content_cache.py (+17/-0)
tests/unit/test_utils.py (+16/-0)
| Changed in content-cache-charm: | |
| assignee: | nobody → Haw Loeung (hloeung) |
| status: | New → In Progress |
| Changed in content-cache-charm: | |
| status: | In Progress → Fix Committed |
| Changed in content-cache-charm: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
