Test classes for autopkgtests for covering real hardware and different scenarios
proposed-migration currently runs package tests exactly once in a generic virtualized environment (cloud instance, QEMU, or LXC container) whenever that package or one of its dependencies changes. But for packages which are closely tied to specific hardware or system configurations, such as Linux, X.org/Mir, graphics drivers, IPMI etc. this does not suffice and we actually want to run these tests on several different pieces of real hardware, and/or several kernel versions.
See the linked spec for details.
Set up MaaS autopkgtest worker for kernel team MaaS stack: TODO
autopkgtest: Add --class option and run only those tests when given: TODO
worker: Implement class/instance/
worker: Put class/instance/
britney: Move data structures and presentation from "architecture" to "platform-id", falling back to architecture if not given: TODO
britney: Create initial classes.conf for bare-metal and kernel-specific: TODO
britney: Parse test-classes from Sources index, translate to instances/scenarios using classes.conf: TODO
britney: Send test requests with class/instance/
[apw] Add "Classes: bare-metal" to all linux* source flavors: TODO
Add "Classes: kernel-specific" to lxc and systemd: TODO
* Blueprints in grey have been implemented.