How will I identify an organizer at lca2013?
I think it will be pretty hard to spot us given how cunning our camouflage is.
Tags for this post: conference lca2013 pictures 20130116-lca2013 photo
Comment
First day of setup for lca2013
Some of the linux.conf.au 2013 team took the chance to rock on over to ANU today and do some final AV testing. While I was there I took some pictures of the various theaters, as I figure it will help answer some of the questions our speakers have.
Tags for this post: conference lca2013 pictures 20130117-lca2013 photo
Comment
Its either a third child, or Cat is pregnant with a unicorn
So... Catherine is 8 weeks pregnant. We had an ultrasound this morning, and everything seems to be going well. We wouldn't normally tell people this early (its traditional to wait until 12 weeks), but it turns out that we're terrible at keeping secrets. This child is code named "Ducky" until released to the public.
More playing with the new toy
I promise to stop taking pics now...
Tags for this post: blog pictures 20130109-2 photo
Comment
OpenStack at linux.conf.au 2013
As some of you might know, I'm the Director for linux.conf.au 2013. I've tried really hard to not use my powers for evil and make the entire conference about OpenStack -- in fact I haven't pulled rank and demanded that specific content be included at all. However, the level of interest in OpenStack has grown so much since LCA 2012 that there is now a significant amount of OpenStack content in the conference without me having to do any of that.
I thought I'd take a second to highlight some of the OpenStack content that I think is particularly interesting -- these are the talks I'll be going to if I have the time (which remains to be seen):
Monday
Image handlers (in essex)
George asks in the comments on my previous post about loop and nbd devices an interesting question about the behavior of this code on essex. I figured the question was worth bringing out into its own post so that its more visible. I've edited George's question lightly so that this blog post flows reasonably.
Can you please explain the order (and conditions) in which the three methods are used? In my Essex installation, the "img_handlers" is not defined in nova.conf, so it takes the default value "loop,nbd,guestfs". However, nova is using nbd as the chose method.The handlers will be used in the order specified -- with the caveat that loop doesn't support Copy On Write (COW) images and will therefore be skipped if the libvirt driver is trying to create a COW image. Whether COW images are used is configured with the use_cow_images flag, which defaults to True. So, loop is being skipped because you're probably using COW images.
My ssh keys are obtained by cloud-init, and still whenever I start a new instance I see in the nova-compute.logs this sequence of events:This is a bit harder than the first bit of the question. What I think is happening is that there are files being injected, and that's causing the mount. Just because the admin password isn't being inject doesn't mean that other things aren't being injected still. You'd be able to tell what's happening by grepping your logs for "Injecting .* into image" and seeing what shows up.qemu-nbd -c /dev/nbd15 /var/lib/nova/instances/instance-0000076d/disk kpartx -a /dev/nbd15 mount /dev/mapper/nbd15p1 /tmp/tmpxGBdT0 umount /dev/mapper/nbd15p1 kpartx -d /dev/nbd15 qemu-nbd -d /dev/nbd15I don't understand why the mount of the first partition is necessary and what it happens when the partition is mounted.
The Forever War (again)
 ISBN: 9780312536633 LibraryThing |
Still excellent.
Tags for this post: book joe_haldeman reread |
Some quick operational notes for users of loop and nbd devices
A quick note for OpenStack operators -- if you are using loop or nbd devices to mount disk images in nova-compute, then you would be well served to have plenty of device files hanging around to reduce contention. For loop devices, that seems as simple as making more of them with MAKEDEV. With nbd, you'll also need to increase the value of the max_nbd_devices flag to nova-compute. The latter is improved in grizzly, where we will autodetect nbd devices.
Tags for this post: openstack loop nbd operations
Comment
Starquake
 ISBN: 0345312333 Del Rey (1986), Edition: First Thus, Mass Market Paperback LibraryThing |
The sequel to the very excellent Dragon's Egg, this book covers the continued interaction between the humans and the super cute Cheela. Unfortunately for the Cheela they suffer a major natural disaster which destroys society. I love an author who is willing to kill of characters when it progresses the story, and there is lots of that happening in this book. Really enjoyable.
Tags for this post: book robert_l_forward hard alien aliens cheela Related posts: Dragon's Egg; Isaac Asimov's Robot City: Robots and Aliens: Humanity; Isaac Asimov's Robot City: Robots and Aliens: Maverick; Isaac Asimov's Robot City: Robots and Aliens: Changeling; Speaker For The Dead; Jupiter; Isaac Asimov's Robot City: Robots and Aliens: Alliance; The Robot City, Robots and Aliens Series; The Coming; Isaac Asimov's Robot City: Robots and Aliens: Intruder; Isaac Asimov's Robot City: Robots and Aliens: Renegade |
New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.
Keep up with the latest Advogato features by reading the Advogato status blog.
If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!
