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