=== harlowja is now known as harlowja_away
=== harlowja_away is now known as harlowja
=== harlowja is now known as harlowja_away
[12:34] <kwadronaut> hmmm first time i noticed Module ssh-import-id is verified on ['ubuntu'] distros but not on debian distro. It may or may not work correctly.
[12:34] <kwadronaut> but i never noticed any problems with that.
[12:34] <kwadronaut> (as in: happy user)
[15:14] <smoser> kwadronaut, right. i suspect its fine.
[15:15] <smoser> that one is fairly well known to work, as failures are quite obvious: I CANT SSH IN!
[15:27] <kwadronaut> (-:
=== harlowja_away is now known as harlowja
[18:17] <harlowja> smoser yt
[18:18] <harlowja> so far this is what i got
[18:18] <harlowja> http://bazaar.launchpad.net/~harlowja/cloud-init/ds-openstack/view/head:/cloudinit/sources/DataSourceOpenStack.py
[18:18] <harlowja> input appreciated, need to do a little more shared/common refactoring
[18:18] <smoser> here now.
[18:19] <smoser> wooth. i'll take a look.
[18:19] <smoser> thanks harlowja 
[18:19] <harlowja> np
[18:19] <smoser> harlowja, is there vendor data support ?
[18:19] <harlowja> ya
[18:19] <smoser> sweet
[18:21] <harlowja> smoser does the config-drive have vendor data, was analyzing the nova code, didn't see it
[18:22] <smoser> it should have vendor data.
[18:23] <harlowja> k
[18:38] <harlowja> i'll work on refactoring some more of the common stuff today/tommorow, but let me know if i missed anything major
[18:39] <smoser> harlowja, vendordata should be there.
[18:39] <smoser>  etc/nova/nova.conf.sample
[18:39] <harlowja> k
[18:39] <smoser>  nova/api/metadata/base.py
[18:39] <smoser> should get into the config drive or the metadata service > HAVANA
[18:39] <smoser>  >= HAVANA
[18:41] <harlowja> kk
[18:41] <harlowja> will make sure its read in the configdrive code
[18:41] <harlowja> gotta share more of that code
[18:41] <harlowja> they are basically reading the same stuff :-P
[18:44] <smoser> harlowja, thanks.
[18:45] <harlowja> np
[19:17] <iliyas> I want to add a DNS A record for an instance at boot. Our DNS is managed at UltraDNS. Any pointers how to go about with it ?
[19:17] <harlowja> iliyas u should just be able to add a script to do that
[19:18] <harlowja> http://cloudinit.readthedocs.org/en/latest/topics/examples.html#run-commands-on-first-boot 
[19:18] <harlowja> thats one example
[19:18] <harlowja> or http://cloudinit.readthedocs.org/en/latest/topics/format.html#user-data-script
[19:20] <iliyas> harlowja: Thanks. If I want to use the 2nd approach (user-data-script) where should be the script place ?
[19:20] <iliyas> placed*
[19:20] <harlowja> depends on the cloud u are running in :)
[19:20] <harlowja> openstack, ec2?
[19:20] <harlowja> other
[19:20] <iliyas> CloudStack
[19:20] <harlowja> hmmm, k, i'm not so sure about that one then
[19:21] <harlowja> but typically there is some way to pass in a user-data file
[19:21] <harlowja> so u'd pass it in via that mechanism
[19:21] <harlowja> cloudstack documentation should tell u how i would think
[19:22] <iliyas> I used the 1st approach (run-commands-on-first-boot) to setup the hostname by querying the metadata URL wherein I placed the script on the VM filesystem (/scripts/update_hostname.sh)
[19:23] <smoser> iliyas, so pretty much anything you can do by modifying the image prior to boot, you can do via user-data in cloud-init.
[19:24] <harlowja> *as long as its a relatively recent version of cloud-init
[19:26] <smoser> well, pretty much anything supported boothooks
[19:26] <smoser> so you can drop a file down inside.
[19:27] <smoser> but CloudStack support came more recently i think. 
[19:27] <iliyas> Yes smoser. CloudStack support has been added recently.
[20:43] <dgarstang1> Anyone awake? :) 
[20:44] <dgarstang1> I have such bad luck with cloud-init. Is there any reason stuff in /etc/cloud/cloud.cfg.d would be totaly ignored?
[20:44] <harlowja> dgarstang1 depends, could be many reasons, do u have log files that u can share?
[20:46] <dgarstang1> harlowja: Here ya go... http://pastebin.com/aAfJY1az
[20:47] <dgarstang1> not much to it
[20:47] <harlowja> hmmm, how about /var/log/cloud-init.log
[20:47] <dgarstang1> I'm expecting to see the final message. The first two lines of the pastebin are from /var/log/cloud-init.log
[20:47] <harlowja> do u have the rest of /var/log/cloud-init.log?
[20:48] <dgarstang1> harlowja: Sure. Is anything before the last reboot relevant?
[20:48] <harlowja> could be
[20:48] <dgarstang1> kk, here http://pastebin.com/YReDs9Ps
[20:48] <harlowja> dgarstang1 how cloud-init works is that not all modules will be ran repeatly (Every boot)
[20:49] <dgarstang1> harlowja: not even final_message ?
[20:49] <dgarstang1> Also, I'm on Google Compute 
[20:49] <harlowja> k, on google compute might not be so helpful, never used that myself
[20:50] <harlowja> *especially if they modified cloud-init
[20:50] <harlowja> so the final-message should always come out
[20:50] <dgarstang1> I know cloud-init doesn't have a data source for GCE, but it wasn't clear before I grabbed the one referred to by http://comments.gmane.org/gmane.linux.debian.cloud/965 that if it was failing to run anything was because it was on GCE, or for some other reason
[20:50] <harlowja> ya, logs not showing to much
[20:50] <dgarstang1> harlowja: They seldom do
[20:50] <harlowja> if u turn on debug logging then they will show lots more :-P
[20:50] <dgarstang1> the ec2 errors certainly went away
[20:51] <dgarstang1> how?
[20:51] <harlowja> oh, nm
[20:51] <harlowja> u already on debug level, lol
[20:51] <dgarstang1> I changed the Data Source to NoData, but as I said, it still wasn't doing anything. is that because GCE breaks it, or for some other reason? 
[20:52] <harlowja> unsure, it almost looks like they aren't running all the cloud-init stages
[20:52] <dgarstang1> i don't need the GCE functionality really. So, if setting the datasource to NoData would at least let scripts run, that's fine
[20:52] <harlowja> all i see is 'start' and 'start-local' running
[20:52] <dgarstang1> harlowja: and this is with debug log. See my frustration?
[20:52] <harlowja> ya, how cloud-init is installed in the GCE images though cloud-init wouldn't be aware of
[20:52] <harlowja> what images are those?
[20:53] <dgarstang1> harlowja: custom made with packer
[20:53] <harlowja> oh, then i have no idea :-P
[20:53] <harlowja> it appears like the install of cloud-init isn't right
[20:53] <dgarstang1> harlowja: what makes you say that?
[20:54] <harlowja> logs aren't showing more than start and start-local running
[20:54] <harlowja> typically these are the stages 
[20:54] <harlowja> http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/files/head:/sysvinit/redhat/
[20:54] <dgarstang1> harlowja: just a package... 0.6.3-0ubuntu1.9
[20:55] <dgarstang1> Argh
[20:55] <harlowja> ya, ubuntu uses upstart, so it could be not configured/using the right ocnfig files
[20:55] <harlowja> *config
[20:56] <harlowja> http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/files/head:/upstart/
[20:56] <harlowja> smoser might be able to help with those
[20:56] <dgarstang1> harlowja: it's starting on boot obviously cuz it's logging stuff
[20:56] <harlowja> ya, 1 stage is running
[20:56] <harlowja> but not the 'config' stage or the 'final' stage
[20:57] <harlowja> so something seems off
[20:58] <dgarstang1> is good? http://pastebin.com/2cJ0hiVJ
[20:59] <harlowja> ya, but thats not connected to the upstart system
[20:59] <harlowja> different config
[20:59] <dgarstang1> http://i.imgur.com/A9tp2w7.jpg
[20:59] <dgarstang1> hm
[21:00] <harlowja> ha
[21:00] <dgarstang1> i suppose I could post a link to a y u no meme, but meh
[21:00] <harlowja> but then u could have that meme for all software ;)
[21:01] <dgarstang1> cloud-init is especially frustrating
[21:01] <dgarstang1> not so good logging, not so good docs
[21:01]  * harlowja improvements welcome :)
[21:02] <smoser> dgarstang1, its ubuntu, right?
[21:03] <dgarstang1> smoser: yep
[21:03]  * dgarstang1 takes a deep breath
[21:03] <smoser> that pastebin is odd.
[21:03] <smoser> cloud-init was being run over and over again
[21:04] <dgarstang1> smoser: maybe cuz it was exiting !0 ?
[21:04] <dgarstang1> This is on GCE... Would using GCE with NoDataSource work or just outright barf?
[21:05] <harlowja> GCE, use openstack ;)
[21:05] <smoser> it should work.
[21:05] <harlowja> *j/k
[21:05] <dgarstang1> harlowja: que?
[21:05] <harlowja> nm
[21:05] <dgarstang1> *squinty eye*
[21:05] <dgarstang1> we have ... contractual obligations. :)
[21:06] <smoser> you installed an ubuntu package ?
[21:06] <dgarstang1> smoser: for cloud-init? Yah... for precise. 0.6.3-0ubuntu1.9
[21:07] <dgarstang1> smoser: Tried to get the one from debian experimental as it apparetly has gce support, but it didn't want to install on precise
[21:09] <smoser> dgarstang1, is rsyslog installed?
[21:11] <dgarstang1> Yep
[21:12] <dgarstang1> I just restarted a new instance of the same image. I'm not sure if a better approach is to use no data source, or to use the patched GCE one
[21:13] <smoser> ok. looking at this paste http://pastebin.com/YReDs9Ps
[21:13] <smoser> you know that for it to find the nocloud datasource, you have to populate /var/lib/cloud, right?
[21:15] <smoser> i think that the behavior you're seeing is what you got on 0.6.3 when there was no datasoruce found.
[21:15] <smoser> there was no 'none' datasource, so the subsequent portions wouldn't end up running.
[21:15] <dgarstang1> one sec
[21:15] <smoser> http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/files/934/doc/examples/seed
[21:15] <smoser> read that. 
[21:16] <smoser> or you may be able to use 'ci-tool' 
[21:16] <smoser> http://bazaar.launchpad.net/~smoser/cloud-init/ci-tool/view/head:/ci-tool
[21:16] <smoser> which basically can write a /var/lib/cloud/data/seed dir for you.
[21:16] <dgarstang1> i have to populate /var/lib/cloud ?
[21:16] <smoser> "NoCloud" is a datasource, but it has to have data (metadata and userdata).  the "no cloud" part is just that its prvided by you.
[21:17] <dgarstang1> smoser: maybe I should try the GCE patch then?
[21:17] <smoser> well, newer cloud-init will probably have dependency issues on 12.04.
[21:17] <dgarstang1> This is it... http://pastebin.com/GjDWFGMj
[21:18] <dgarstang1> no, just drop that file in...
[21:18] <smoser> thats not terribly likely to work/
[21:18] <dgarstang1> Oh
[21:18] <smoser> if it was written for newer cloud-init
[21:18] <dgarstang1> ok, back to no data source then
[21:18] <smoser> then it wont "just work" on 12.04's version
[21:19] <smoser> probably would'nt be too hard to port it to 0.6.3.
[21:19] <dgarstang1> populate /var/lib/cloud... looking for docs...
[21:19] <smoser> but i pointed at the docs above.
[21:19] <dgarstang1> one sec
[21:24] <dgarstang1> is http://bazaar.launchpad.net/~smoser/cloud-init/ci-tool/view/head:/ci-tool the only way to populate /var/lib/cloud? 
[21:24] <smoser> no. you can do it by hand. its very easy. 
[21:25] <dgarstang1> doc? :)
[21:25] <dgarstang1> http://cloudinit.readthedocs.org/en/latest/topics/dir_layout.html ?
[21:25] <smoser> http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/files/934/doc/examples/seed
[21:25] <dgarstang1> oic
[21:26] <dgarstang1> do I need user-data ?
[21:27] <dgarstang1> Actually I have a /var/lib/cloud with stuff in it already http://pastebin.com/BChLFcjt
[21:27] <smoser> sudo sh -c 'd=/var/lib/cloud/seed/nocloud-net/; mkdir -p $d; echo "instance-id: i-abcdefg" > $d/meta-data; printf "%s\n%s\n" "#!/bin/sh" "echo hi mom" > $d/user-data'"#!/bin/sh"; 
[21:27] <smoser> bah. the '!
[21:27] <smoser> sudo sh -c 'd=/var/lib/cloud/seed/nocloud-net/; mkdir -p $d; echo "instance-id: i-abcdefg" > $d/meta-data; printf "%s\n%s\n" "#!/bin/sh" "echo hi mom" > $d/user-data"#!/bin/sh"; 
[21:27] <dgarstang1> so, if I have stuff in /var/lib/cloud already, I'd say thats' not the issue?
[21:28] <smoser> no. you aren't finding a datasource.
[21:28] <smoser> because there *is not a datasource*
[21:28] <smoser> and i'm showing you how to make one.
[21:30] <dgarstang1> not following context.... this isnt amazon. There is no user-data or instance-id
[21:30] <dgarstang1> modifying...
[21:31] <smoser> you're giving it one.
[21:32] <dgarstang1> smoser: they don't contextually exist in gce.
[21:33] <smoser> i really don't understand what you're wanting.
[21:33] <smoser> http://pastebin.com/GjDWFGMj
[21:33] <smoser> clearly *does* have a instance-id
[21:33] <smoser> (at least the metadata service has something labeled 'instance-id')
[21:33] <smoser> but thats not even improtant here.
[21:33] <smoser> if you're wanting to run cloud-init, then you need to have it find a datasource
[21:34] <smoser> and you can create a directory in /var/lib/cloud/... that it will see as a datasource
[21:34] <dgarstang1> smoser: Can I just create an empty /var/lib/cloud/nocloud-net?
[21:34] <smoser> there was something there before you put it there?
[21:34] <smoser> you can rm -Rf /var/lib/cloud if you want
[21:35] <dgarstang1> smoser: yes. http://pastebin.com/BChLFcjt
[21:35] <smoser> it will all be put back on boot
[21:35] <smoser> that all was created by cloud-init
[21:35] <smoser> the *seed* is not crated by cloud-init
[21:35] <smoser> it is created by you
[21:35] <dgarstang1> k
[21:36] <dgarstang1> I created /var/lib/cloud/seed/nocloud-net, changed the data source to datasource_list: [ NoCloud ] ...
[21:38] <dgarstang1> added a final_message... rebooted... it's not running it
[21:38] <dgarstang1> Did not find data source. searched classes: ['DataSourceNoCloudNet']
[21:38] <dgarstang1> I don't know why it even mentions DataSourceNoCloudNet. I certainly didn't specify it
[21:40] <dgarstang1> yay. running
[21:56] <smoser> ok. for what its worth, i just pushed a couple small changes to ci-tool.
[21:56] <smoser> and now:
[21:56] <smoser>  sudo ./ci-tool reset --full
[21:58] <smoser>  sudo ./ci-tool seed
[21:58] <smoser> will populate the datasource and remove other state that might have been present.
[22:08] <dgarstang1> smoser: seems I can get away with the directory and some dummy data. I need to keep it simple as packer is running this and I don't want to have to store, and push out an entire script
=== harlowja is now known as harlowja_away
=== harlowja_away is now known as harlowja