lp://staging/~therve/landscape-client/juju-env-info-2

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp://staging/~landscape/landscape-client/trunk at revision 609

Alberto Donato: Approve on 2013-01-17

Chris Glass (community): Approve on 2013-01-17

Diff: 112 lines (+64/-2)

3 files modified

landscape/message_schemas.py (+5/-2)
landscape/monitor/computerinfo.py (+19/-0)
landscape/monitor/tests/test_computerinfo.py (+40/-0)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #1100179: Update registration to send extra information about Juju environment

Medium

Fix Released

Link a bug report

Related blueprints

609. By Thomas Herve on 2013-01-17

Add data to the computer-info message

608. By Thomas Herve on 2013-01-17

Revert juju-env-info merge [trivial]

607. By Andreas Hasenack on 2013-01-16

Load the Cephusage plugin by default. [trivial] [r=radix] [f=1100452]

606. By Thomas Herve on 2013-01-16

Merge juju-env-info [r=cglass,bjornt] [f=1100179]

Add a mechanism in registration to upload extra data.

605. By Chris Glass on 2013-01-15

Add a Ceph storage monitor plugin that reports Ceph disk usage to the server [f=1098495] [r=ack,jseutter]

604. By Chris Glass on 2013-01-11

Add a monitor plugin that reports the client's CPU usage (by looking at /proc/stat). [f=1097617] [r=jseutter,therve]

603. By Thomas Herve on 2013-01-09

Add comment in may_complement_changes about upgrades [trivial]

602. By Phillip Susi on 2013-01-08

landscape-sysinfo was reporting memory usage values that
were entirely incorrect. This was because it was calculating free
memory to be all memory not on the active list. Changed to use
free + cached + buffers, just like the free command does. [f=1075619] [r=jseutter,tealeg]

601. By Geoff Teale on 2013-01-04

This branch is the client side half of the fix for bug #1087458.

I have added code to inspect the file /etc/update-manager/release-upgrades and extract the vale of the Prompt variable in the [DEFAULT] section. This variable controls when the user is prompted by the update-manager to do a release upgrade. Valid values are 'never', 'normal' and 'lts'. It is possible that this file doesn't exist, in which case we pretend it is set to 'normal'. If for some reason another value is set it also returns 'normal' but log a warning.

This code is now embedded into a monitor plugin that runs every hour - if the value has changed then it will attempt to inform the server of the new value. [f=1087458] [r=free.ekanayaka,tribaal]

600. By Chris Glass on 2013-01-03

Make the checking for new package state based on "last modified timestamp" instead of the apt facade. [f=1091131] [r=bjornt,jseutter]