There has been some discussion on HN of using a logbook or notebook. I’ve used a work notebook on paper for about 20 years. Here are the ones from the last 8 years (minus the one I’m currently using):
Years ago Red Hat even had their own branded notebooks. I nicked one from the office supply cabinet and they seem to have stopped making them:
The older books had blank pages. These notes from 2010 record a list of bugs (tick marks for done/fixed items) and the initial design of guestfs-browser:
Unfortunately unlined pages don’t work well for me because I have pretty terrible handwriting. I’ve moved to using lined notebooks now as you can see by comparing these two pages from 2011 and 2014 respectively:
My ideal notebook is the Oxford Black n’ Red A5 Matt Casebound Hardback Notebook, Ruled 192 Pages, and my ideal pen is the UM-153S Signo Impact Gel Pen:
Most of the pages are scribbled notes from meetings. If you saw me furiously scribbling at the KVM Forum last month, then this is what I was writing.
I find it really helpful to remember the contents of meetings and what to do. Asterisks mean ideas for future research or work. Ticks are items which have been done.
The number of doodles is not necessarily related to the boredom in the meeting!
Really nice doing
make -j46 kernel builds on Qualcomm’s insanely fast ARM-based Amberwing server.
As usual I’ve placed the proposed RHEL 7.5 libguestfs packages in a public repository so you can try them out.
Thanks to Pino Toscano for doing the packaging work.
Eric Blake has been doing some great stuff for nbdkit, the flexible plugin-based NBD server.
- Full parallel request handling.
You’ve always been able to tell nbdkit that your plugin can handle multiple requests in parallel from a single client, but until now that didn’t actually do anything (only parallel requests from multiple clients worked).
- An NBD forwarding plugin, so if you have another NBD server which doesn’t support a feature like encryption or new-style protocol, then you can front that server with nbdkit which does.
As well as that he’s fixed lots of small bugs with NBD compliance so hopefully we’re now much closer to the protocol spec (we always check that we interoperate with qemu’s nbd client, but it’s nice to know that we’re also complying with the spec). He also fixed a potential DoS where nbdkit would try to handle very large writes which would delay a thread in the server indefinitely.
Also this week, I wrote an nbdkit plugin for handling the weird Xen XVA file format. The whole thread is worth reading because 3 people came up with 3 unique solutions to this problem.
Fedora 27 has just been released, and I’ve just uploaded virt-builder images so you can try it right away:
$ virt-builder -l | grep fedora-27
fedora-27 aarch64 Fedora® 27 Server (aarch64)
fedora-27 armv7l Fedora® 27 Server (armv7l)
fedora-27 i686 Fedora® 27 Server (i686)
fedora-27 ppc64 Fedora® 27 Server (ppc64)
fedora-27 ppc64le Fedora® 27 Server (ppc64le)
fedora-27 x86_64 Fedora® 27 Server
$ virt-builder fedora-27 \
--root-password password:123456 \
--install emacs \
$ qemu-system-x86_64 \
-machine accel=kvm:tcg \
-cpu host -m 2048 \
-drive file=fedora-27.img,format=raw,if=virtio &
nbdkit is a liberally licensed NBD server which a stable plugin API for serving disks from unconventional sources.
Finally I got around to adding TLS (encryption and authentication) support. The support is complete and appears to interoperate with QEMU. It also supports a certificate authority, client certificate verification, certificate revocation, server verification (by the client), and configurable algorithms.
Actually using TLS with NBD is no easy matter. It takes a few pages of instructions just to explain how to set up the public-key infrastructure. On the client (QEMU) side, the command line parameter for connecting to a TLS-enabled NBD server is lengthy.
Then there’s the question of how you ensure TLS is being used. In nbdkit as in other NBD servers you can either turn on TLS in which case it’s used when the client requests it, or you can require TLS. In the latter case nbdkit will reject non-TLS connections (thus ensuring TLS is really being used), but most clients won’t be able to connect to such a server.
As usual, where SSH got it right, SSL/TLS/HTTPS got it all horribly wrong.
20:30 < koike> Hi. Is it possible to configure the dmi codes for libguestfs? I mean, I am running cloud-init inside a libguestfs session (through python-guestfs) in GCE, the problem is that cloud-init reads
/sys/class/dmi/id/product_name to determine if the machine is a GCE machine, but the value it read is
Standard PC (i440FX + PIIX, 1996) instead of the expected
Google Compute Engine so cloud-init fails.
The answer is yes, using the guestfs_config API that lets you set arbitrary qemu parameters:
'type=1,product=Google Compute Engine')