[01:26] flaccid, i would think you must have an old version of the module.. .possibly you upgraded? [01:27] and you're using a cached version of the object and new code... but i'm not sure. [01:27] i have not seen it. [01:27] smoser: well this is actually natty package which must not be ready as the attribute is not in the module [01:28] i do nearly have the maverick package working on squeeze though [01:29] well, it is there. look in /usr/share/pyshared/cloudinit/DataSource.py [01:29] the attributes are not in the module [01:29] the module is there yes [01:29] i'd really like for you to chase the trunk working... i can help, but not really right now [01:29] well, you should in that file see : [01:30] DEP_FILESYSTEM = "FILESYSTEM" [01:30] DEP_NETWORK = "NETWORK" [01:30] must not be in the natty pkg yet. is there an easy way to build the trunk src into packages ? [01:44] flaccid, yes, actually, but the natty pkg should have it... anyway [01:45] (otherwise this would be completely busted, but alpha-2 did work) [01:45] flaccid, run ./tools/bddeb is a short cut "build me a deb" of the trunk [01:46] danke. most likely cloud-init is going in these debian images. there isn't too many things left to do before release [02:54] smoser: not sure why, i added both your gpg keys, but am still getting gpg: skipped "Scott Moser ": secret key not available [02:59] oh its secure, i'd need your secret key. i see. guess i have to change that [03:27] ok cool i learnt about that [03:28] so cloud-init uses initctl thoroughly however does not have a dep, upstart. this is making it difficult for debian [05:25] join #lopsa === daker_ is now known as daker === dendro-afk is now known as dendrobates [14:03] flaccid, it does use initctl, you're right, but i don tthink there is many dependencies on it any more [14:03] yeah, it doesn't really use it, externally something coudl take the 'cloud-config' event, but internally the upstart jobs don't use it anymore === daker_ is now known as daker === zul_ is now known as zul [20:12] my ubuntu ec2 instance just seems to refuse incoming connections. like a firewall is configured, but the security group has all proper rules. and no errors appear in the console output. what do i do? [20:13] i have httpd and sshd running, both refuse connections. no issues for a week until today. === zul_ is now known as zul === mrjazzcat is now known as mrjazzcat-lunch === dendrobates is now known as dendro-afk === dendro-afk is now known as dendrobates === dendrobates is now known as dendro-afk === dendro-afk is now known as dendrobates === Kiall is now known as Kiall|AFK