[14:07] <jclift> Script failure was caused by /usr/bin/bash not existing.  /me sighs
[14:07] <jclift> Well, that's fixed at least ;)
[14:30] <cds> does anyone know how i can force cloud-init to only run once?
[14:30] <cds> i pass nocloud data as a cdrom during first boot, everything works fine
[14:30] <cds> reboot without it and it falls back to the no data source and resets all my changes
[15:58] <smoser> cds, 2 options:
[15:58] <smoser> a.) don't detach the cdrom
[15:59] <smoser> b.) set manual_cache_clean: True
[15:59] <smoser> http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/examples/cloud-config.txt
[16:03] <cds> cool, thanks
[16:03] <cds> is setting the kernel param ds=nocloud acceptable?
[16:03] <cds> i am just using this vm on a local machine
[16:04] <smoser> well, how did you get the kernel and intiramfs? 
[16:05] <cds> let me back up, i just want to boot ubuntu cloud once, have cloud-init configure it via nocloud-data
[16:05] <cds> then not worry about passing it anything cloud-init related
[16:06] <cds> changing ds=nocloud in /etc/grub/default after the initial configuration worked ok
[16:47] <smoser> ah. ok. that doesn't sound terrible. 
[16:48] <smoser> probably other ways to do it, but i'd have to think. yours doesn't sound terrible.
[16:54] <cds> cool, thanks :)
[19:27] <jclift> smoser: Btw, for the RHEL/Fedora/CentOS thought on "how to tell if a reboot is needed", it might not be that hard to tell for kernel changes
[19:29] <jclift> eg just retrieve + store the version info strings prior to running yum, retrieve them again afterwards, if they compare differently, voila, new kernel installed.  No need to even understand the version number breakdown inside, just "if it's different, reboot".