=== harlowja is now known as harlowja_away [11:04] harlowja_away: :) === harlowja_away is now known as harlowja [17:48] let me see how much farther i can get today harmw , nearly there i think [17:56] I'm trying to find the code for the puppet module in cloud-init. part of it is just what variables are available for interpolation into the puppet.conf file.. can someone point me to it? [17:57] I've looked in the bzr repo, and don't see anything, but it clearly works... [17:57] mbarr http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/cloudinit/config/cc_puppet.py [17:57] and there's nothing about modules in the current docs site. [17:57] mainly line 51 and on [17:57] Hmm... i wouldn't have expected it inside config. [17:57] :) [17:57] that's why i didn't find it :) [17:57] back in the day i tried to name that differently [17:58] *name the folder differently [17:58] i failed, haha [17:58] ahh, there is only the %f & %i. got it. [17:59] What's interesting is that I'm trying to change the hostname of the system early enough to be picked up by puppet, and it gets cranky.. [17:59] Thus, the code is helpful. [18:00] hmmm [18:01] i suspect it's starting the puppet instance before the runcmd actually changes the hostname. [18:02] are u using the sethostname module? [18:02] http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/cloudinit/config/cc_set_hostname.py [18:02] That was what i was *just* looking at. [18:02] It's not documented at present in the main docs. [18:02] so thus.. the code. it is helpful :) [18:02] ah [18:02] http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/config/cloud.cfg#L40 [18:03] runcmd happens after pupper [18:03] I could switch it to bootcmd, and it'd be OK, it looks like. [18:03] ya, i suspect so [18:03] I was figuring i would just read code, and figure it out :) [18:04] although set_hostname module runs after bootcmd [18:04] or i could just use the set_hostname and it'd be fine too. [18:04] so it might get overwritten [18:05] preserve_hostname would prevent that, or i could just do the puppet command by hand. [18:05] however, it's annoying to have to edit the defaults file. [18:05] So i was looking to see how you dealt with it. [18:08] hmmm, i haven't use the puppet stuff personally :) [18:08] That's oK. [18:08] it's just using the autostart(). [18:09] I could not bother w/ the init script and just run it, and mostly, it'd be fine. [18:09] :) [18:09] i just really wanted to see how this thing worked, and seeing the order was actually key :) [18:10] def [18:17] I'm attempting to give more info to things like logs, so i need my hostnames to have some info as to role, but also still be unique, and auto scaleable... [18:17] oh what fun autoscaling is [18:21] I end up w/ hostnames like webserver-prod-us-east-1c-i-2828384.ec2....... [18:21] thank you, I'm glad to see that the project was included in RHEL 6.4. That'll make this a fairly standard option now. [18:23] def [18:24] Thanks again! wonderful job :) [18:24] np [18:24] ha [20:31] harlowja: any luck? [20:31] ah, haven't had time yet [20:36] ok [20:44] harlowja: you work at yahoo, right? [20:44] correct [20:45] you're behind the ads.yahoo.com malware? :p [20:46] lol [20:46] nope [20:46] :) what is it you do, software developer? [20:47] yuppers, openstack software developer guy [20:47] cool [20:47] developer or also responsible for the yahoo cloud running smooth and gentle? [20:48] a little of all the things :-P [20:48] more developer, less smooth running person [20:48] i try to not get involved there [20:48] haha [20:49] and yahoo pays you to 'just work on openstack'? [20:51] pretty much [20:51] thats pretty cool [20:51] just you or a team of several? [20:51] openstack to big for 1 person ;) [20:51] so more than 1 [20:51] less than 50 [20:51] :-P [20:52] thats quite a few :) [20:52] and something similar to keep the yahoo cloud running? [20:52] and please forgive me for beeing curious :) [20:53] np [20:53] well its almost the same team, we have to be pretty well connected with the people running it [20:53] obviously [20:53] how large is your deployment anyway? [20:53] ah [20:54] now u getting into the intereting questions :-P [20:54] :> [20:54] ya, that one i can't easily say [20:54] but in the thousands [20:54] thats the estimate i can say [20:54] instances? [20:54] (vm's) [20:55] lets say both to that [20:55] lol [20:55] ok [20:55] compute nodes? [20:56] and what kind of storage do you use? [20:56] something iscsi-ish? or a ceph cluster? [20:57] hmmmm [20:57] lol [20:57] ya, not sure if i can answer that one :-P [20:57] *not yet at least* [20:57] lol [20:57] because you don't know or because it's a secret :p [21:00] well lets say its a WIP [21:00] lol [21:00] on something, lol [21:00] lol, do tell :> [21:00] ha [21:00] someday when i can :-P [21:01] haha, though by then it's probably on yahoo.com/cloud/solution/bla [21:02] link not work :-P [21:02] :> [21:02] btw, is the yahoo cloud private or public? [21:02] since there's no easy reference on yahoo.com [21:03] private [21:03] http://www.openstack.org/summit/openstack-summit-hong-kong-2013/session-videos/presentation/yahoo-case-study :-P [21:03] with me [21:03] lol [21:04] lol nice [21:04] you're the bald guy from the still? :p [21:06] lol [21:06] 2 bald guys are in that video [21:06] but yes [21:06] oh haha [21:10] :) [21:12] bb food [21:12] :) nice talk [21:13] ha [21:13] thx [23:25] alright, harmw finally getting back to freebsd