add nbd module to init script
Bug #1531171 reported by
Ben Howard
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| launchpad-buildd |
Fix Released
|
High
|
Colin Watson | ||
Bug Description
The Cloud Team is moving builds from KVM-based builders to buildds in Launchpad. Some of the targets that we build are derivatives of the upstream cloud image and are variants of disk formats (i.e. VMDK, VHD, VDI, etc). One of the targets. Further, the MAAS image generation code uses qemu-nbd. In order to facilitate all Cloud image deliverables being generated in buildds we would like the nbd module to be loaded in the buildd host.
i.e.
modprobe nbd || true
Related branches
lp:~cjwatson/launchpad-buildd/modprobe-nbd
- William Grant: Approve (code)
-
Diff: 26 lines (+6/-0)2 files modifieddebian/changelog (+2/-0)
debian/launchpad-buildd.init (+4/-0)
Revision history for this message
| Scott Moser (smoser) wrote | #1 |
| description: | updated |
| Changed in launchpad-buildd: | |
| status: | New → In Progress |
| importance: | Undecided → High |
| assignee: | nobody → Colin Watson (cjwatson) |
| Changed in launchpad-buildd: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Colin Watson (cjwatson) wrote | #2 |
| Changed in launchpad-buildd: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
for justification, the maas build process basically does this:
qemu-img create -f qcow2 -b pristine-
qemu-nbd --connect /dev/nbd0 trash.img
mount /dev/nbd0 /mnt
chroot /mnt apt-get install ....
cp /mnt/boot/vmlinuz .
umount /mnt
rm -f trash.img
we dont *need* it, but using qemu-nbd there is faster at least initially then copying 'pristine-
note, selection of a /dev/nbd0 is done by mount-image-