[01:50] <blackboxsw> hmm looks like I can't run dhclient from /run/cloud-init/tmp/something/dhclient
[01:50] <blackboxsw> http://pastebin.ubuntu.com/25544142/
[01:50] <smoser> tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=378640k,mode=755 0 0
[01:50] <smoser> noexec
[01:50] <smoser> :-(
[01:50] <smoser> its fallout of https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1707222
[01:50] <blackboxsw> yeap
[01:51] <blackboxsw> sooo where to store our tmp files
[01:52] <smoser> wouldn't it be neat if there was a directory named "/tmp" or something
[01:52] <blackboxsw> temp_utils dumps them under /run/cloud-init which breaks our dhcp ec2local
[01:52] <blackboxsw> heh
[01:52] <blackboxsw> :)
[01:52] <blackboxsw> yeah I'm testing passing dir='/tmp' right now
[01:52] <blackboxsw> to temp_utils.tempdir
[01:52] <smoser> well, that'll work, but possibly have your directory deleted
[01:53] <blackboxsw> right might have a race still on the cleanup
[01:53] <blackboxsw> could drop it in /etc :)
[01:53] <blackboxsw> nasty nasty
[01:54] <smoser> i think /var/tmp might be an option.
[01:54] <blackboxsw> not a bad idea
[01:54] <smoser> not sure. have to look at systemd-tmpfiles-clean
[01:55] <blackboxsw> : SUCCESS: found local data from DataSourceEc2Local
[01:55] <blackboxsw> ok so using dir=/tmp works, I'll try a reboot w/ /var/tmp
[01:59] <blackboxsw> smoser: per unit tests in systemd "        # files in /var/tmp/ older than 30d should get cleaned up
[01:59] <blackboxsw> "
[01:59] <blackboxsw> checking the code now
[02:00] <blackboxsw> looks to be commented out in /usr/lib/tmpfiles.d/tmp.conf in artful #q /var/tmp 1777 root root 30d
[02:03] <blackboxsw> ok dhclient runs Ec2Local work from /var/tmp
[02:09] <blackboxsw> smoser: for monday https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/330875
[02:09] <blackboxsw> gotta run
[02:09] <smoser> k. i'll ask xnox for review too
[02:09] <smoser> need to file a bug
[02:09] <smoser> i will
[02:09] <smoser> you go
[02:09] <smoser> later
[02:16] <smoser> bug https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1717627
[02:23] <blackboxsw> thanks smoser, so maybe my patch should really just be http://paste.ubuntu.com/25544275/
[02:23] <blackboxsw> shouldn't we change where our temp_utils default tmp dir is?
[02:23] <smoser> i dont know.
[02:23] <smoser> its obnoxious
[02:24] <blackboxsw> yeah it is.
[02:24] <smoser> i can reproduce the GCE one
[02:24] <smoser> its failure of some of my changes for GCE metadata servvice
[02:24] <blackboxsw> thanks, what'd I break?
[02:24] <smoser> the 'add a main'
[02:24] <blackboxsw> ahh
[02:46] <blackboxsw> Added https://trello.com/c/qDqAXygV/387-bug-gce-datasource-doesnt-run-bootcmd-config
[02:46] <blackboxsw> Ok outta here
[02:46] <blackboxsw> Have a good one
[02:53] <smoser> blackboxsw, https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1717598 has a branch for you at your leisure
[07:49] <dknight87> hi guys, how can I usee masterless puppet and cloudinit to provision aws servers?
[22:04] <blackboxsw> dknight87.  Puppet-apply is how most folks run puppet locally. Any config keys and. Values provided under the puppet: conf: key get written into /etc/puppet/puppet.conf so you could specify where your local manifests etc live and have a cron job run that runs puppet-apply for you.  I thought this tutorial was fair
[22:04] <blackboxsw> https://www.digitalocean.com/community/tutorials/how-to-set-up-a-masterless-puppet-environment-on-ubuntu-14-04
[22:05] <blackboxsw> The puppet: conf: keys I mentioned would be in your #cloud-config user-data file you provide at instance launch time. http://cloudinit.readthedocs.io/en/latest/topics/modules.html#puppet