inconsistent logging between different providers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| pyjuju |
Low
|
Unassigned |
Bug Description
lxc instances have no /var/lib/
ec2 instances still have the charm.log separate from the unit-agent log.
description: | updated |
Clint Byrum (clint-fewbar) wrote : | #1 |
Changed in juju: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Kapil Thangavelu (hazmat) wrote : Re: [Bug 893379] Re: inconsistent logging between different providers | #2 |
Excerpts from Clint Byrum's message of Tue Nov 22 00:39:47 UTC 2011:
> I was quite confused by this as well at first. Seems like a by-product
> of the 1 machine -> multiple units paradigm that only exists in the
> local provider right now. Maybe if LXC is used everywhere (sans
> networking?) then the logging will end up consistent?
>
> ** Changed in: juju
> Status: New => Confirmed
>
> ** Changed in: juju
> Importance: Undecided => Medium
>
I'm fine with either, consistency is important, afaics per fhs we should do the
/var/log/
Changed in juju: | |
milestone: | none → florence |
Changed in juju: | |
milestone: | florence → galapagos |
Changed in juju: | |
milestone: | galapagos → honolulu |
Changed in juju: | |
milestone: | 0.6 → none |
Changed in juju: | |
status: | Confirmed → Triaged |
Changed in juju: | |
importance: | Medium → Low |
I was quite confused by this as well at first. Seems like a by-product of the 1 machine -> multiple units paradigm that only exists in the local provider right now. Maybe if LXC is used everywhere (sans networking?) then the logging will end up consistent?