Difference between revisions of "Tims minnowboard test provisioning"
(Created page with "Tim is (in early 2018), trying to come up with a provisioning system for the Minnowboard turbot in his lab. He put out a request for information on the automated-testing e-m...") |
m |
||
| Line 11: | Line 11: | ||
* If possible to avoid hardware, that would be good. | * If possible to avoid hardware, that would be good. | ||
** I don't mind special hardware | ** I don't mind special hardware | ||
| − | * I want to boot the machine for testing | + | * I want to boot the machine for testing as similar to how it will be used in production as possible |
** This means that automatic boot from sdcard is preferable to network boot, or especially boot with network FS. | ** This means that automatic boot from sdcard is preferable to network boot, or especially boot with network FS. | ||
* fewer package dependencies is better | * fewer package dependencies is better | ||
Revision as of 12:40, 26 January 2018
Tim is (in early 2018), trying to come up with a provisioning system for the Minnowboard turbot in his lab.
He put out a request for information on the automated-testing e-mail list, and got back lots of options. See https://lists.yoctoproject.org/pipermail/automated-testing/2018-January/subject.html#152
Here is an evaluation of those options, along with his own test experiences setting this up for his lab:
principles
- If possible to avoid hardware, that would be good.
- I don't mind special hardware
- I want to boot the machine for testing as similar to how it will be used in production as possible
- This means that automatic boot from sdcard is preferable to network boot, or especially boot with network FS.
- fewer package dependencies is better
- fewer runtime host dependencies is better
suggestions
- use LAVA, with network download of kernel and ramdisk (suggested by Matt Hart)
- No specifics were mentioned
- Collabora is using LAVA on a Minnowboard. An example usage is here:
- use labgrid and SD-USB-Mux (suggested by Robert Schwebel)
- use ci-rt project stuff for this (suggested by Thomas Gleixner)
- supports debian-packaged kernels - good for kbuild?
- presumably this uses r4d for low-level board control, and libvirt and
- r4d requires sqlite3 python-sqlalchemy python-pysimplesoap snimpy snmp-mibs-downloader
- daemon must be running at all times (ugh)
- presumably starts new kernel using kexec
- does it support non-x86_64? What platforms support kexec?
= overview of provisioning/booting options:
- install kernel to SD card, boot from grub (kernel selection at boot)
- install kernel to USB flash, boot from grub (kernel selection at boot?)
- install kernel to host, boot from network
- install kernel to target fs, kexec boot from local file
action items
- get an SD-USB-Mux for testing from Robert Schwebel
- can a wireless SD card be used for this?
- find out if r4d relies on kexec support
- find out if configuring grub for serial port control requires rebuilding grub
