[17:29] <Chocobo> Hello.  What comes after generating the SSH key pair?  I created a snapshot of an image and when I try to boot it seems to hang after initializing SSH.  Is there a way to disable cloud-init with a kernel/grub parameter?
[17:40] <Chocobo> hrmmm.  I even tried setting "init=/bin/bash" and "single"  to no avail.   Interestingly on the first boot the log shows a root prompt but the vnc console just shows a black screen with a blinking cursor.
[18:02] <Chocobo> I am not sure what is causing this.
[18:25] <bjweaver> Still trying to get cloud-init to run the user-data script on an ISO..  The script is on the ISO as openstack/latest/user_data
[18:26] <bjweaver> I turned up logging as harlowja suggested , added  output: {all: '|tee -a /var/log/cloud-init-output.log} to cloud.cfg
[18:27] <bjweaver> Only thing in the log is a warning about 2012-08-10 not available and attempting to use 'latest'
[18:36] <bjweaver> might be magically working now
[18:59] <smoser> Chocobo, i can't answer you if you're not here.
[18:59] <smoser> bjweaver, working ?
[19:36] <harlowja_> harmw yt
[19:37] <harlowja_> smoser also, u might be interested in
[19:37] <harlowja_> http://paste.openstack.org/show/61294/ (config rc.d script for cloud-init)
[19:37] <harlowja_> *an inital attempt, feedback wanted (from sean)
[19:38] <harlowja_> http://paste.openstack.org/show/61295/ (cloud-final)
[19:38] <harlowja_> http://paste.openstack.org/show/61296/ (cloud-init)
[19:39] <harlowja_> http://paste.openstack.org/show/61297/ (cloud-init-local)
[19:39] <harlowja_> any feedback welcome
[19:39] <harlowja_> ^^ for freebsd
[19:39] <smoser> well i think that functions with a '-' in their name are not posix shell
[19:39] <harlowja_> k
[19:40] <smoser> $ dash -c 'foo-bar() {echo hi}'
[19:40] <smoser> dash: 1: Syntax error: Bad function name
[19:40] <harlowja_> ya
[19:40] <harlowja_> comment fwded ;)
[19:40] <smoser> actually, they dont even work for bash :)
[19:41] <smoser> $ bash -c 'foo-bar() {echo hi;}'
[19:41] <smoser> bash: -c: line 0: syntax error near unexpected token `{echo'
[19:41] <smoser> bash: -c: line 0: `foo-bar() {echo hi;}'
[19:42] <harmw> oh my, he's used - and _ as well :p
[19:43] <harlowja_> :-p
[19:43] <harlowja_> i told him, haha
[19:52] <harmw> harlowja_: i'm looking at 61296, I think lines 17 and 28 won't work this way
[19:52] <harmw> and command=bla differs between the different files :)
[19:55] <harlowja_> kk, let me bug him as this
[20:54] <bjweaver> smoser - I believe so.. I had to move the scripts-* up to the cloud_init_modules section. I haven't found docs on how init vs config vs final stages work. Seems our init scripts only run the init section. 
[20:55] <smoser> bjweaver, ubuntu?
[20:55] <smoser> you dont want those in the modules section
[20:55] <smoser> as running in modules section does not guarantee network
[20:55] <bjweaver> This is the opensuse package port of cloud-init
[20:56] <smoser> i wonder are you getting networking from the config-drive ?
[20:56] <bjweaver> networking is coming from a DHCP server. 
[20:57] <bjweaver> This is a project we are doing under VMware. 
[22:14] <grepory> does documentation exist for logging configuration? cloud-init isn't generating new ssh host keys when it's being run, and i can't figure out why... the debug logs do not have anything useful in them.
[22:17] <grepory> As far as I can tell, logging is configured at level debug, but ... i would expect to see something about modules running at the very least, but that is not the case.
[22:18] <grepory> Ah because it is supposed to bail if it doesn't find a datasource. I was expecting it to use "None" as I configured it to in /etc/cloud/cloud.cfg, but to no avail.
[22:19] <grepory> datasource_list: ["NoCloud", "ConfigDrive", "OVF", "MAAS", "Ec2", "CloudStack", "None"]
[22:19] <grepory> is this insufficient?
[22:19] <grepory> or incorrect?
[22:26] <grepory> ugh n/m. figured out how config resolution works.
[22:28] <grepory> and that the None datasource isn't actually something you can use.
[23:43] <harlowja_> smoser harmw so scripts are fixed, sean i think will also package this sucker into the freebsd ports repository once it works
[23:43] <harlowja_> so +1