Client should send the vm type in the registration message
Bug #795752 reported by
Kevin McDermott
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Landscape Client |
Fix Released
|
Medium
|
Kevin McDermott | ||
Bug Description
The client should detect whether or not it's running in a virtualisation environment and send this in the registration message.
Related branches
lp:~bigkevmcd/landscape-client/vm-info-in-registration
- Thomas Herve (community): Approve
- Free Ekanayaka (community): Approve
-
Diff: 577 lines (+208/-214)7 files modifiedlandscape/broker/registration.py (+3/-1)
landscape/broker/tests/test_registration.py (+39/-5)
landscape/lib/tests/test_vm_info.py (+121/-0)
landscape/lib/vm_info.py (+39/-0)
landscape/message_schemas.py (+5/-5)
landscape/monitor/computerinfo.py (+0/-37)
landscape/monitor/tests/test_computerinfo.py (+1/-166)
| Changed in landscape-client: | |
| assignee: | nobody → Kevin McDermott (bigkevmcd) |
| milestone: | none → 11.06.2 |
| importance: | Undecided → Medium |
| status: | New → In Progress |
Revision history for this message
| Kevin McDermott (bigkevmcd) wrote | #1 |
| Changed in landscape-client: | |
| status: | In Progress → Fix Committed |
| tags: | added: verified |
Revision history for this message
| Clint Byrum (clint-fewbar) wrote Please test proposed package | #2 |
| tags: | added: verification-needed |
Revision history for this message
| Andreas Hasenack (ahasenack) wrote | #3 |
| tags: |
added: verification-done removed: verification-needed |
Revision history for this message
| Martin Pitt (pitti) wrote | #4 |
| tags: | removed: verification-done |
| tags: | added: verification-needed |
Revision history for this message
| Martin Pitt (pitti) wrote | #5 |
Revision history for this message
| Andreas Hasenack (ahasenack) wrote | #6 |
| Changed in landscape-client: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
So, this branch removes the vm-info from the computer info, and we'll store it upon registration, this does have a downside, in that you can't switch VMs to the new VM licensing scheme, as we'll never update that value?
The bzr history is ok tho', as I implemented that as a feature after the main work, so I can revert :-)