[16:39] <smoser> harlowja_at_home, ping
[16:40] <smoser> you want to be on a cloud-init talk submission for ods-vancouver
[16:40] <smoser>  http://paste.ubuntu.com/10144643/ <-- abstract
[17:11] <harlowja_at_home> yo yo, will check when i get into work, bb
[17:35] <larsks> smoser: are new commits still going to lp:cloud-init, or has all work (even maintenance) moved to github?
[17:36] <smoser> larsks, my plan is to keep cloud-init 0.7.x on launchpad/bzr for near term.
[17:36] <larsks> smoser: Thanks.
[17:55] <robjo> Hi, how do I prevent host key regeneration?
[17:56] <robjo> The situation is that I am trying to switch running instances from initialization framework $HOMEBREW to cloud-init
[17:56] <robjo> after reboot the host key is regenerated, but there was a hostkey already, and I need to prevent this from heppening?
[18:04] <harlowja> smoser whats up dawg
[18:06] <larsks> robjo: it looks like you should be able set 'ssh_deletekeys' to 'false' to prevent cloud-init from deleteing and re-generating keys.
[18:06] <robjo> larsks: thanks will test this
[18:07] <smoser> you want to be on a cloud-init talk submission for ods-vancouver
[18:07] <smoser> harlowja, ^
[18:08] <harlowja> smoser ohhh, sureeee
[18:08] <harlowja> smoser like a talk or like a presentation?
[18:08] <harlowja> *not a session right?
[18:09] <smoser> presentation, yeah.
[18:09] <smoser> as in https://www.openstack.org/summit/vancouver-2015/call-for-speakers/TalkDetails/
[18:09] <smoser> i need a catchy title.
[18:10] <harlowja> Click and Clack talk Cloud-init
[18:10] <harlowja> haha
[18:10] <harlowja> *u can be click
[18:10] <harlowja> i'll be clack
[18:11] <smoser> deal
[18:12] <smoser> i didn't realize californians listened to npr
[18:13]  * harlowja not in a while, ha
[18:13] <harlowja> sometimes :-P
[18:13] <harlowja> i thought car-talk over though
[18:35] <robjo> larsks: Thanks, worked :)
[18:36] <larsks> robjo: \o/
[19:12] <jseun> hi! I am facing a strange behaviour with cloud-init: it seems that I cannot change the default username 'ubuntu' in the /etc/cloud/cloud.cfg file to something else.  I get a bunch of error like Failed to set passwords, etc... as if the user creation failed earlier in the boot process.
[19:13] <jseun> but naming it 'ubuntu' again works flawlessly
[19:22] <larsks> jseun: what version of cloud-init is in use?
[19:27] <jseun> larsks: 0.7.5-0ubuntu1.3
[19:31] <larsks> jseun: Interesting.  If I boot a Trusty image on my openstack environment, using this user-data file: http://chunk.io/f/c170788bd870459185833da5fbcfd3b8
[19:31] <larsks> ...it just works.  That is, the 'example' user is created instead of 'ubuntu',  and I can log into the 'example' account using my ssh key.
[19:33] <jseun> larsks: interesting indeed.  I'll disable clearing the console so I can see what's going on
[19:33] <jseun> thanks for having a look
[19:34] <jseun> hmm.. I did not use that syntax, larsks (looking at your user-data)
[19:35] <jseun> system_info:
[19:35] <jseun>   default_user:
[19:35] <jseun>     name: docker
[19:35] <jseun> that's how I specified the default user
[19:35] <jseun> I'll try your way
[19:35] <larsks> Hope it works! :)
[19:57] <smoser> jseun, that should work also
[19:57] <smoser> and actually is the "new" er way to do that.
[20:01] <jseun> smoser: neither worked for me. cc_ssh_authkey_fingerprints.py and friends fail if I change the default username, which is strange.  I am trying to get more debug informations from the console buffer since I am locked out.
[20:04] <smoser> jseun, http://paste.ubuntu.com/10147330/
[20:04] <smoser> that just "worked for me" on a trusty instance
[20:05] <smoser> jseun, http://paste.ubuntu.com/10147350/ and that one for vivid
[20:10] <jseun> smoser: allright, so it does work.  I'll have to see what happens on my side.  I am using cloud-init to configure a custom live CD image based on Ubuntu Core 14.04 (see http://github.com/jseun/ucldh)
[20:10] <harmw> harlowja: any experience with glusterfs?
[20:11] <harmw> (or anyone else, for that matter)
[20:11] <harlowja> negative
[20:13] <larsks> harmw: a *litttte* experience with glusterfs.
[20:13] <larsks> s/tte/ttle/
[20:13] <harmw> ok, fair enough
[20:14] <harmw> and how was that experience :)
[20:14] <larsks> harmw: well...it seemed super easy to setup, and I was happy with my little experiement.  I wasn't doing anything performance (I was using it to provide shared storage in a test kubernetes cluster).
[20:15] <harmw> hm hm hm
[20:15] <larsks> harmw: there is a #gluster channel, too :)
[20:15] <harmw> sure, but I'm not after biased answers :P
[20:16] <harmw> I had a tiny ceph deploymnt that worked, kinda
[20:16] <harmw> interested in gluster, if it's any good to replace ceph
[20:17] <smoser> jseun, ah. nice. maybe you're not finding a datasource?
[20:17] <smoser> jseun, one thing i might do for debuggin is use 'backdoor-image' 
[20:17] <smoser> https://code.launchpad.net/~smoser/+junk/backdoor-image
[20:17] <smoser> basically will just inject another user (backdoor user) into a system
[20:18] <smoser> into an image or into a target root directory
[20:18] <jseun> oh yes! that's just what i need right now
[20:18] <smoser> see the usage http://bazaar.launchpad.net/~smoser/+junk/backdoor-image/view/head:/backdoor-image
[20:18]  * harmw cloud insert some random NSA-based joke here
[20:18]  * harmw allows harlowja to do just that
[20:19]  * harlowja runs away
[20:19] <smoser> well, that tool by default inserts the user 'backdoor', so it tries to be up front about everything
[20:19] <smoser> HEY! i'm putting a backdoor into your system !
[20:19] <smoser> then later, you say:
[20:19] <smoser>  hm... why is there a user 'backdoor' here... i wonder if thats a good thing.
[20:19] <harmw> consipiray and clever mindtricks
[20:21] <jseun> lol
[20:54] <jseun> smoser: i could not add the docker user because the docker group already exists : http://paste.ubuntu.com/10147940/
[20:55] <jseun> having docker group in primary-group directive should fix it i think
[21:20] <jseun> http://paste.ubuntu.com/10148316/ <-- how would you guys tell cloud-init to create this default user with a primary-group already created?