[11:59] <jgrimm> smoser, thoughts on -> https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1600766
[12:02] <jgrimm> hmm.. maybe we've fixed already but we just haven't done a release with it? https://bugs.launchpad.net/cloud-init/+bug/1246485
[12:03] <smoser> jgrimm, this is fixable by lxc templates. i've discussed it with stgraber.
[12:03] <smoser> it is now fixable in cloud-init with some thought ... the most recent changes would allow for it when previously there wasn't really a  point in boot where you could do that.
[12:04] <smoser> but a rose by any other name would still smell as sweet
[12:04] <smoser> ie, why does it matter?
[12:04] <jgrimm> ubuntu-core folks have use case
[12:04] <smoser> probably not good ones.
[12:05] <smoser> the host platform (lxd in this case) declares that the hostname of the system is XXXX
[12:05] <smoser> why do you care what the system calls itself ?
[12:05] <smoser> the system says "I want to be named bob"
[12:05] <smoser> lxd says "his name is robert"
[12:05] <smoser> who cares what the system says. if you ask the platform (dns) his name is robert.
[12:06] <smoser> but, as i said, 2 ways to fix it.
[12:06] <smoser> does that make sense ?
[12:06] <smoser> why do you care what the container calls itself.
[12:06] <jgrimm> This is a problem when using the dnsmasq for local dns resolving for *.lxd, which is the standard way of doing host dns for containers, as new containers are not dns addressable with a restart or renew.
[12:07] <smoser> lxd should fix that.
[12:07] <smoser> if lxd wants to insist that you can ask dnsmasq for dns resolution
[12:07] <smoser> then it can't rely on the system behaving correctly
[12:15] <smoser> jgrimm, stgraber i commented in bug
[12:15] <jgrimm> smoser, sorry.. laptop locked up.   looking now
[16:09] <smoser> rharper, harlowja larsks
[16:09] <rharper> here
[16:09] <smoser> i'm going to delete lp:cloud-init
[16:09] <smoser> which means http://paste.ubuntu.com/21155351/
[16:09] <larsks> howdy
[16:10] <larsks> I've only got one in that list and I can resubmit...
[16:10] <rharper> ditto
[16:10] <smoser> your repos wont be deleted, but yeah. they  have to be re-done
[16:10] <smoser> k
[16:12] <smoser> larsks, and harlowja since i know you're such high bzr and launchpad users, you might sometime need the solution i came up with at
[16:12] <smoser>  https://bugs.launchpad.net/bzr-fastimport/+bug/1606973
[16:12] <smoser> powersj, rharper might actually use that at some point (curtin and other things)
[16:13] <rharper> smoser: nice
[16:13] <rharper> that'll be needed for curtin move to git as well
[16:13] <smoser> i wasted a lot of time trying to use another solution that just didnt work with cloud-init's bzr export
[16:14] <powersj> this is cool
[16:14] <smoser> this way was much easier.
[16:15] <rharper> y
[17:57] <smoser> larsks, rharper https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init harlowja
[17:57] <smoser> that is up now.
[17:57] <smoser> ready for merge proposals
[17:57] <rharper> thx
[17:57]  * larsks looks...
[18:06] <larsks> re-propsed: https://code.launchpad.net/~larsks/cloud-init/+git/cloud-init/+merge/301310
[18:08] <smoser> larsks, what does git push -u do for me ?
[18:08] <larsks> smoser: sets the upstream tracking branch so that in the future you can just "git push" instead of "git push myremote mybranch"
[18:09] <larsks> Otherwise you get: http://chunk.io/f/6378b82ea0c647cd888de1af0d912bb8
[18:10] <larsks> (-u is short for --set-upstream)
[18:11] <smoser> larsks, do you want to stick with with cheetah in that tempatle ?
[18:12] <larsks> You mean the spec file?  Not really!  I just didn't want to make too many changes at once that weren't directly related to the task at hand...
[18:12] <smoser> ok
[18:12] <smoser> thats fine,  want to ditch cheetah
[18:12] <smoser> but that is good to not do that here.
[18:12] <larsks> I will make that a subsequent merge proposal.
[18:12] <larsks> (converting the redhat and suse spec files to jinja templates)
[18:12] <smoser> although you did do arbitrary white space (line 534)
[18:12] <smoser> :)
[18:13] <larsks> That hurt my brain.
[18:14] <smoser> i think keep the 'find_root' around line 635
[18:14] <smoser> same reason as before... would like to set those
[18:14] <smoser> rather than relying on git
[18:14] <smoser> alghouth i guess less improtant there
[18:14] <smoser> as that is explicitly a git operation
[18:14] <larsks> Even make-tarball? That seems like we really want that to come from version control.
[18:14] <larsks> Yeah.
[18:15] <smoser> line 681 in that diff
[18:15] <smoser> isthat set -o pipefailed ?
[18:15] <smoser> i dont think so.
[18:15] <smoser> so the gzip is unlikely to fail and thus unlikely to error
[18:16] <smoser> (if the left sizde of that | (git archive) fails, then the command will succeed)
[18:16] <smoser> read-depednecies... there is some reason we cant' use egrep
[18:16] <smoser> let me log
[18:17] <smoser> commit e26ac6b63072f3217de2fc9214584e61682cd211
[18:17] <larsks> I'll update the script to set pipefail.
[18:17]  * larsks looks at that commit.
[18:17] <smoser> pipefail is bash
[18:18] <smoser> silly non-linux unixes
[18:18] <larsks> Ah, right, and we can't assume bash.
[18:18] <smoser> and their silly 1986 shells
[18:18] <larsks> That basically means "freebsd" at this point?
[18:18] <smoser> yeah.
[18:18] <smoser> those changes came in with freebsd
[18:18] <smoser> it makes sense to use python though
[18:18] <smoser> as we're pretty dependent on python working
[18:18] <smoser> :)
[18:19] <larsks> I guess.  It seemed like a ridiculous amount of logic, but that's okay, I'll revert.
[18:26] <smoser> larsks, my mom reminds me that i didnt' say thank you. this is good, thank you.
[18:27] <larsks> smoser: thanks! just pushed a restored (mostly) read-dependencies; fixing up make-tarball now...
[18:34] <larsks> ...and there's a fixed up make-tarball