/srv/irclogs.ubuntu.com/2014/04/01/#cloud-init.txt

=== harlowja is now known as harlowja_away
=== harlowja_away is now known as harlowja
=== harlowja is now known as harlowja_away
jcliftScript failure was caused by /usr/bin/bash not existing.  /me sighs14:07
jcliftWell, that's fixed at least ;)14:07
=== shardy is now known as shardy_afk
cdsdoes anyone know how i can force cloud-init to only run once?14:30
cdsi pass nocloud data as a cdrom during first boot, everything works fine14:30
cdsreboot without it and it falls back to the no data source and resets all my changes14:30
smosercds, 2 options:15:58
smosera.) don't detach the cdrom15:58
smoserb.) set manual_cache_clean: True15:59
smoserhttp://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/examples/cloud-config.txt15:59
cdscool, thanks16:03
cdsis setting the kernel param ds=nocloud acceptable?16:03
cdsi am just using this vm on a local machine16:03
smoserwell, how did you get the kernel and intiramfs? 16:04
cdslet me back up, i just want to boot ubuntu cloud once, have cloud-init configure it via nocloud-data16:05
cdsthen not worry about passing it anything cloud-init related16:05
cdschanging ds=nocloud in /etc/grub/default after the initial configuration worked ok16:06
smoserah. ok. that doesn't sound terrible. 16:47
smoserprobably other ways to do it, but i'd have to think. yours doesn't sound terrible.16:48
cdscool, thanks :)16:54
=== harlowja_away is now known as harlowja
jcliftsmoser: 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 changes19:27
jclifteg 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".19:29

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!