paulgorman.org

< ^ txt

Mon Apr 16 09:11:23 EDT 2018 Slept from ten-thirty to seven. Woke briefly around four. High of forty-two today. Rain. Work: - Resolve new Dropbox licensing Done? - Work on automating Asterisk build/deploy Done. https://cdimage.debian.org/cdimage/openstack/ So, there's no way to enable console output for Debian using the qcow2 image during `virt-install`? This is annoying, since output of the graphical install modes pauses for a _long_ time doing something. Also, cloud-init seems to be at least somewhat broken; I can't insert ssh keys using nocloud. At one point nocloud was not enabled: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826954 I guess they never fixed it? Regression? Half-hour walk at lunch. Went to Meijer to buy half-and-half, and noticed a lady making sushi. She comes in once a week. The sushi wasn't bad; I'll buy more if I see her again. https://asciinema.org/a/132009 The `cloud-localds` tool can also be used to make nocloud image files. # apt-get install cloud-image-utils I realized that even after the suspended vnc console output, I could still get updated output by hitting: $ virsh console myvm Cloud-init runs, and is sure looks like it never checks nocloud. It tries 'http://10.0.0.1/latest/meta-data/instance-id' for a long time, gives up, then tries 'http://169.254.169.254/2009-04-04/meta-data/instance-id'. Yeah. The Debian qcow2 image never tries the NoCloud datasource for cloud-init. Annoying. Home: - Delete old Clyde VM from Vultr (if we're all good on the new VM) Done. Lunch: coffee, sushi Dinner:

< ^ txt