[13:12] <smoser> harlowja_away, yeah.  a lot of it amounts to "i'll just build everything on my own, and then it will be done right." which is perfectly fine with me, if you want to do that. it turns out, though, its kind of expensive in the long run.
[16:22] <tennis> hi.  I'm getting this on one of my aws instances, and I'm not sure where to begin to debug it.  Any ideas anyone? https://gist.github.com/anonymous/eb9fd02646e6a760ed34
[16:23] <tennis> For some reason, the url_helper.py cannot find '169.254.169.254' for metadata.
[16:49] <xerxas> hello everyone ! I'm using the chef module to install ... chef. I would like to use omnibus packages and specify the versions I want to install but can't find a way to do it. Any idea ? 
[17:05] <harlowja> smoser agreed
[19:16] <kwaping> when using an #include url, are there any variables available that can be used to identify the host that's phoning home?
[19:16] <kwaping> (hi harlowja)
[19:16] <harlowja> kwaping i assume u are oliver :-P
[19:16] <harlowja> or something else, ha
[19:16] <harlowja> not alien?
[19:16] <kwaping> oh, duh, yes
[19:16] <harlowja> hi oliver!
[19:16] <harlowja> i see u
[19:16] <harlowja> lol
[19:17] <kwaping> sorry, this is my obscure public name, long story
[19:17] <harlowja> smoser just want to introduce u to another y! (oliver aka kwaping ) he's been doing some stuff with cloud-init on baremetal (simialr to maas i guess) annnnnd will be helping out :)
[19:17] <harlowja> sooo hiiii kwaping 
[19:17] <harlowja> :-P
[19:17] <harlowja> kwaping loves the baremetal
[19:17] <harlowja> lol
[19:18] <kwaping> I work with harlowja, don't hold that against me :P
[19:18] <harlowja> lol
[19:19] <kwaping> anyway, my ideal end goal is to include cloud-init in a ramdisk used for installing the final OS, and I want that ramdisk version to phone home and grab a dynamic config for disk setup (especially hardware RAID config), based on the individual host that's making the request
[19:22] <harlowja> smoser that sounds similar to maas and maybe other stuff i think right :-P
[19:23] <harlowja> i guess the smartos folks are doing similar things, idk
[19:24] <harlowja> sooo kwaping  http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/cloudinit/user_data.py#L204 is the code that does all the include stuffs
[19:24] <harlowja> i didn't think the url has any params that get filed in
[19:24] <harlowja> at least it doesn't right now
[19:24] <kwaping> ok thanks, checking
[19:24] <harlowja> basically the userdata gets read, and then out put as X mime segements
[19:25] <harlowja> these mime (mail) segements are then later analyzed to do things
[19:25] <harlowja> http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/cloudinit/user_data.py#L89 is where the fun begins
[19:25] <harlowja> blob there being the starting 'user data blob'
[19:26] <kwaping> fascinating that #include-once really means "fetch and cache"
[19:26] <harlowja> gotta do the 'once' part somehow :-P
[19:26] <harlowja> since #include stuff is recurisvely expanadble
[19:26] <harlowja> #includes urls having content with #includes ....
[19:27] <kwaping> does it also get run only once, or is it "fetch once, run every time"? (still reading code)
[19:27] <harlowja> so this is just the code that does that extraction; its typically called once
[19:27] <harlowja> but depends on what u mean by 'run everytime'
[19:27] <harlowja> all this does is download the userdata and such into a multipart mime message
[19:27] <harlowja> which then gets processed later
[19:28] <kwaping> ah ok, so include-once can load files that are run once or run lots
[19:28] <harlowja> how it gets processed later is dependent on what the processing is
[19:28] <kwaping> content and fetch method are decoupled
[19:28] <harlowja> ya
[19:28] <harlowja> this is just the fetch
[19:28] <kwaping> cool thanks
[19:28] <kwaping> that helps
[19:28] <harlowja> np
[19:31] <harlowja> http://cloudinit.readthedocs.org/en/latest/topics/dir_layout.html is also useful to look at/understand kwaping 
[19:31] <harlowja> user-data.txt.i (is the multipart pieces)...
[19:31] <harlowja> 'user-data.txt' is the unprocessed/initial stuff
[19:32] <kwaping> yeah I've been all over that site lately, but still digesting contents
[19:32] <harlowja> k
[19:32] <harlowja> smoser wanted to eventually i think destroy the usage of mime multipart stuff; maybe in the next version of cloud-init
[19:32] <harlowja> its somewhat confusing to use mime messages for this, ha
[19:32] <harlowja> but thats how it goes :-P
[19:33] <kwaping> yeah I was going to say something about that, but figured there was a good use case that I was missing
[19:33] <kwaping> config by email
[19:33] <harlowja> smoser can explain, i forget the reason back in the day
[19:33] <harlowja> probably something along the line of 'python has real good mime support and such, lets use it'...
[19:33] <harlowja> ^ predates me, ha
[19:33] <kwaping> funny how major decisions get made for reasons like that :)
[19:34] <harlowja> :)
[19:34] <kwaping> ok I'm going to head out since smoser is afk
[19:34] <kwaping> we can continue the witty banter elsewhere
[19:34] <harlowja> ha
[19:34] <harlowja> all we do here is witty banter :-P
[19:34] <harlowja> thats a major part of my day, lol
[19:37] <harlowja> hmmm, will have to get him to idle in here vs leave, will work on that, lol