[00:18] quick question, if I'm trying to create a file to stick into my cloud-init config file that I'm feeding whichever cloud provider, and I want to stick a !!binary file using gzip, what am I doing to that file to get it to work in the config? [00:18] obviously gzip, but then what, base64? === harlowja is now known as harlowja_away === harlowja_away is now known as harlowja === harlowja is now known as harlowja_away [12:17] smoser: hi, any progress with https://code.launchpad.net/~harlowja/cloud-init/py2-3 ? [14:25] mhroncok, the plan is to address it with cloud-init v2, which is sort of up in the air. but python3 version of cloud-init is to be done. [14:33] smoser: great, any tracking bug for this or some other info? [14:33] no. it is really in very early discussion. === harlowja_away is now known as harlowja [19:15] harlowja, do you think you (or y!) would have a use for a cloud-init agent. [19:15] JayF, same question to you. [19:15] sureee; i think that'd probably be useful sometime [19:15] and/or eventually [19:15] other than the netork config application [19:15] although chef is doing alot of that i think [19:16] so there would be that question of what this does vs chef [19:16] *yahoo going full on with chef [19:16] I think we would have some interest in an agent like that existing; I wouldn't want to commit to us wanting it to be cloud-init tbh [19:16] what does your current agent do ? [19:17] We don't have a current agent aside from nova-agent [19:17] I just know python comes with a lot of headache we might want to avoid [19:17] i.e. if you use go; you'd be able to statically compile the agent once, to run on all distributions [19:17] and not worry about the distribtuion clobbering it [19:18] well, it'd sitll be clobbered with: ( cd /proc && killall -9 * ) [19:18] ie, nothing is perfectly safe. [19:19] cloud-init on a chip? [19:19] that'd be cool [19:19] clobber proof [19:19] lol [19:19] well I mean more like [19:20] true. /me pulls out his java processor [19:20] if we vendor in our own cloud-init (like we do today, and given our code moves faster than the oldest distro we support, we will for the forseeable future) [19:20] not having apt-get dist-upgrade # pull in some python package that breaks our custom cloud-init [19:20] would be nice [19:20] as well as not having to run a repository with the package to avoid ^ that problem [19:20] yeah. [19:21] what does nova-agent do now ? [19:21] is that something i can read ? [19:22] http://www.syntheticworks.com/rackspace-cloud/linux-rackspace-cloud/all-about-nova-agent-linux/ i guess [19:22] thought it was opensource somewhere; but not sure how well the docs are [19:23] honestly from looking at that it seems to just do dynamic networking stuff and some other tiny functionality? [19:23] but idk [19:24] nova-agent only runs on virt cloud right now [19:24] not on OnMetal (nor, do I think we will ever run it) [19:24] so I don't have a lot of knowledge about it [19:24] I think nova-agent is an upstream thing too? but imbw === zz_gondoi is now known as gondoi === gondoi is now known as zz_gondoi [21:04] during which stage (cloud-config or cloud-final) is a user script executed? [21:06] http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/config/cloud.cfg#L65 [21:06] 'scripts-user' [21:06] so final [21:07] thanks === mfisch is now known as Guest85585