[00:12] <harlowja> hmmm, i don't know of any reason that would happen swaT30 
[00:13] <harlowja> depends on whats in /etc/sysconfig/network-scripts/ifcfg-eth0
[00:13] <harlowja> and also what came in on the ec2 metdata/configdrive
[00:13] <swaT30> harlowja: let me take a look at the scripts
[00:14] <swaT30> harlowja: eth0 config script is pretty standard dhcp.. and both instances are getting the same metadata/configdrive info
[00:15] <harlowja> hmmm, not sure then :-/
[09:03] <harmw> swaT30: an unrelated question, but do your centos instances get configured with static networking?
[15:02] <smoser> nate`, lxc
[15:03] <smoser> http://ubuntu-smoser.blogspot.com/2013/08/lxc-with-fast-cloning-via-overlayfs-and.html
[15:03] <smoser> or kvm
[15:03] <smoser> http://ubuntu-smoser.blogspot.com/2013/02/using-ubuntu-cloud-images-without-cloud.html
[15:16] <nate`> I'm forced into using RHEL because of contractual obligations.
[15:24] <swaT30> harmw: nope, all DHCP
[15:47] <harmw> oh ok
[15:59] <smoser> hey...
[17:35] <smoser> harmw, ping
[17:35] <smoser> harlowja, 
[17:35] <smoser> https://bugs.launchpad.net/cloud-init/+bug/1241834
[17:35] <smoser> can you verify that bug  and fix ?
[17:35] <smoser> i'll yank that.
[17:35] <smoser> wanting to do 0.7.4
[17:35] <smoser> and that looked reasonable if it "works and fixes" for you.
[17:52] <harmw> sup smoser 
[17:53] <harmw> don't tell me you tabcompleted the wrong person :p
[17:53] <smoser> i did.
[17:53] <smoser> yeah, sorry.
[17:53] <harmw> np :)
=== shardy is now known as shardy_afk
[18:17] <harlowja> hey smoser , just got in, will verify that
[18:18] <smoser> i think the issue is just that 0.6.4 is listed there.
[18:18] <smoser> and there is no tag
[18:18] <smoser> ie, i think this: http://paste.ubuntu.com/6444094/
[18:18] <smoser> i can see the failure without it
=== shardy_afk is now known as shardy
[18:20] <harlowja> ah
[18:21] <harlowja> hmmm
[18:22] <harlowja> let me try that out
[18:53] <smoser> harlowja, i just pushed up a fix. just joined 0.6.4 into 0.7.0 (which is actually "correct")
[18:53] <harlowja> kkk
[18:53] <harlowja> was just about to try it out :)
[18:53] <smoser> and now 'make rpm' fails for me with command not found on 'rpmbuild'
[18:53] <smoser> (which is compltely reasonable)
[18:54] <harlowja> :)
[18:54] <harlowja> i'll double check, getting bugged to review some stuff
[18:58] <harlowja> i've been neglecting some internal reviews, haha
[19:03] <smoser> harlowja, https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1250398
[19:03] <smoser> very tempted to drop boto requirement
[19:03] <harlowja> botooo
[19:03] <harlowja> oooo
[19:04] <harlowja> that code still exists somewhere i think
[19:04] <utlemming> smoser: also, boto is now maintained by AWS
[19:04] <harlowja> intersting it is utlemming 
[19:05] <harlowja> was there a public announcement about that?
[19:07] <utlemming> harlowja: I don't think so. Mitch went to work for AWS a while back. The new EC2 CLI python tool is based on Boto.
[19:07] <harlowja> ah
[19:07] <utlemming> https://aws.amazon.com/sdkforpython/
[19:07] <harlowja> so by inference its supported by amazon then :)
[19:08] <utlemming> well, that last link is about as official as AWS can get on that
[19:08] <harlowja> but that seems like they are replacing boto -> boto3?
[19:08] <harlowja> https://github.com/boto/boto3 
[19:08] <utlemming> that's news to me....
[19:08] <harlowja> "This is not a port of boto, but a ground-up rewrite." 
[19:09] <utlemming> (admittately I don't follow boto closely)
[19:09] <harlowja> *from readme.rst there
[19:09] <harlowja> np
[19:09] <harlowja> good to know anyway (i didn't know it either)
[19:11] <utlemming> at least it is a MIT license....with AWS you never know what you'll get
=== shardy is now known as shardy_afk
[23:11] <harlowja> smoser on a RHEL 6.4 box, http://paste.ubuntu.com/6445336/, all seems ok
[23:11] <harlowja> *on a fresh VM/box
[23:11] <harlowja> seems ok to me