[01:26] <smoser> flaccid, i would think you must have an old version of the module.. .possibly you upgraded?
[01:27] <smoser> and you're using a cached version of the object and new code... but i'm not sure.
[01:27] <smoser> i have not seen it.
[01:27] <flaccid> smoser: well this is actually natty package which must not be ready as the attribute is not in the module
[01:28] <flaccid> i do nearly have the maverick package working on squeeze though
[01:29] <smoser> well, it is there.  look in /usr/share/pyshared/cloudinit/DataSource.py
[01:29] <flaccid> the attributes are not in the module
[01:29] <flaccid> the module is there yes
[01:29] <smoser> i'd really like for you to chase the trunk working... i can help, but not really right now
[01:29] <smoser> well, you should in that file see :
[01:30] <smoser> DEP_FILESYSTEM = "FILESYSTEM"
[01:30] <smoser> DEP_NETWORK = "NETWORK"
[01:30] <flaccid> must not be in the natty pkg yet. is there an easy way to build the trunk src into packages ?
[01:44] <smoser> flaccid, yes, actually, but the natty pkg should have it... anyway
[01:45] <smoser> (otherwise this would be completely busted, but alpha-2 did work)
[01:45] <smoser> flaccid, run ./tools/bddeb is a short cut "build me a deb" of the trunk
[01:46] <flaccid> danke. most likely cloud-init is going in these debian images. there isn't too many things left to do before release
[02:54] <flaccid> smoser: not sure why, i added both your gpg keys, but am still getting gpg: skipped "Scott Moser <smoser@ubuntu.com>": secret key not available
[02:59] <flaccid> oh its secure, i'd need your secret key. i see. guess i have to change that
[03:27] <flaccid> ok cool i learnt about that
[03:28] <flaccid> so cloud-init uses initctl thoroughly however does not have a dep, upstart. this is making it difficult for debian
[05:25] <koolhead11> join #lopsa
[14:03] <smoser> flaccid, it does use initctl, you're right, but i don tthink there is many dependencies on it any more
[14:03] <smoser> 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
[20:12] <lazyshot> 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] <lazyshot> i have httpd and sshd running, both refuse connections. no issues for a week until today.