Distributed upgrade testing for (semi) real systems in a VM

Registered by Michael Vogt on 2008-05-13

Give (power) users a way to test the system upgrade in a sandbox (VM). The "clone-system-to-vm" script (build on top of ubuntu-vm-builder) could be used for this:
https://code.edge.launchpad.net/~mvo/ubuntu-jeos/clone-system-to-vm

We could provide two options:
a) automatic - create clone of the current system as vm and run update-manager with the non-interactive frontend and copy the results
b) manual - create the clone of the current VM but let the user do the upgrade with his favorite GUI

On failures, provide a "report bug" page that uses apport to sent a failure report.

We need to make clear to the user that this test will only ensure that packages and daemon upgrade correctly, not that e.g. the new kernel works well with their specific hardware (because we only test in the VM).

Blueprint information

Status:
Complete
Approver:
Scott James Remnant (Canonical)
Priority:
Low
Drafter:
Michael Vogt
Direction:
Approved
Assignee:
Michael Vogt
Definition:
Approved
Series goal:
Accepted for intrepid
Implementation:
Implemented
Milestone target:
None
Started by
Michael Vogt on 2008-07-25
Completed by
Michael Vogt on 2008-09-12

Related branches

Sprints

Whiteboard

Code in the sandbox-upgrader package in my ppa and at http://code.launchpad.net/~mvo/sandbox-upgrader/main - feedback from testers trickles in :)

Also available in intrepid now.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.