[00:46] <smoser> kiall, it doesn't do that in default installations
[00:47] <smoser> i believe that you can have it be the dns server, but that is not default install, and without it, it cannot answer dns requests
[00:47] <kiall> no problem .. one other question - should instances be able to communicate with each other via their public IPs then?
[00:47] <kiall> (I'm seeing some strange NAT "stuff" happening at the mo ;))
[00:48] <kiall> meaning there is no way for 2 instances to talk without knowing their private IPs (not exactly ideal...)
[00:51] <smoser> both public and private should work for instance-to-instance traffic
[00:53] <kiall> thats what I thought .. but until 30 seconds ago, that simply didnt work .. and now is looking a bit wrong (aka "ping public-ip" .. "reaply from private ip", and an instance cant ping its own public IP).. The change that got me that far was removing the bridge on the CC priv net, and switching to a normal eth interface(
[06:52] <Makere> I'm having trouble running instances
[06:52] <Makere> they get stuck on pending
[09:24] <Makere> can't get the bundled images to run at all
[09:45] <Makere> let's put this otherway, has ANYONE managed to ANY images downloaded from the website and HOW?
[09:53] <Makere> I'm losing all hope
[10:51] <kiall> Makere, i scrapped the "store" images .. they simply didnt work!
[10:52] <kiall> Downloaded the 10.10 uec image from uec-images.ubuntu.com and used the uec-publish-tarball command to push it up..
[10:52] <kiall> worked like a charm
[10:52] <kiall> (oh and - I had to increase the m1.small settings to get it to work with 64 bit images.. they dont work out of the box ... go figure  )
[12:28] <Makere> kiall: well the uec-images on didn't work for me
[12:29] <Makere> got stuck on pending :(
[14:18] <Makere> no errors on any log, nc, nc
[14:19] <Makere> cc
[14:19] <Makere> kiall, you runnin lucid or maverick?
[14:19] <kiall> maverick
[14:20] <Makere> controllers on seperate pc's?
[14:21] <Makere> one or more clusters?
[14:21] <Makere> just [Brunning thevm's without ramdisk?
[14:21] <kiall> a combined CLC/CC/SC/Walrus and a few nodes... (so 1 cluster)
[14:22] <kiall> and no ramdisk for the 10.10 uec-images EMI
[14:23] <Makere> I'm trying 2 clusters with 1 cloud controller and walrus and 2 cluster controllers/sotrage controllers
[14:24] <kiall> Havent done a split setup yet .. but I hope your starting simple and going with 1 cluster and 1 NC first ;)
[14:24] <Makere> so I guess the problem has to do something with splitting them :p
[14:24] <kiall> ...and going with 1 clc, 1 cc, 1 nc*
[14:27] <kiall> anyway .. I thing I found was, once I had tried a load of different things .. stop. wipe. reinstall with your new knowledge ;)
[14:27] <kiall> 1 thing i found*
[14:27] <kiall> Also .. I found the package install "buggy" and ended up using the CD install (hell - it even asked more UEC specific setup questions .. go figure)
[14:44] <Makere> yea
[14:44] <Makere> I did CD install
[14:45] <Makere> problem is that we've done it multiple times now
[14:45] <Makere> and this is not the first time we get the problem
[14:45] <Makere> kiall: have you updated the packages?
[14:45] <Makere> on the nodes or the "Controller"
[15:02] <kiall> Makere, yea - apt-get update && apt-get dist-upgrade && reboot after the CD install .. then setup bridges etc, edit config, clean restart the euca services, and reboot .. - thats about all i needed to get a VM booted (there was more .. but VMs booted)
[15:10] <Makere> setup bridges?
[15:10] <Makere> :O
[15:11] <Makere> no mention of that in the installation guide
[15:11] <kiall> lol ... im sure it mentions it loads of times ;)
[15:11] <Makere> https://help.ubuntu.com/community/UEC/CDInstall atleast this one doesn't
[15:12] <kiall> http://www.google.com/url?sa=t&source=web&cd=1&ved=0CBcQFjAA&url=http%3A%2F%2Fcssoss.wordpress.com%2F2010%2F05%2F10%2Feucalyptus-beginner%25E2%2580%2599s-guide-%25E2%2580%2593-uec-edition-chapter-7-%25E2%2580%2593-network%25C2%25A0management%2F&rct=j&q=eucalyptus%20beginner%27s%20guide%20networking&ei=Np_iTKb0MIHtsgbz3snkCw&usg=AFQjCNGOWI5oW4sBUfT8-AcILsaCl8_hSQ&sig2=vbyB86w94lQLeUdxEo-9tw&cad=rja <-- was a good howto on the network setup that
[15:12] <kiall> doesnt leave anything out
[15:12] <kiall> wow... that URL wasnt exactly the one I was going for ;)
[15:12] <kiall> but it should work ;P
[15:13] <kiall> LOL .. it actually doesnt mention bridges ..≥
[15:13] <Makere> yea
[15:13] <Makere> :)
[15:13] <kiall> yea .. just go to chapter one of that link (and do it the CD install way instead from my exp) .. ;)
[15:14] <Makere> so annoying >_>
[15:15] <Makere> that guide looks like million times better
[15:15] <Makere> thanks
[15:16] <Makere> I wonder if I should start from the beginning
[15:16] <Makere> zzz takes 2 hours to setup with 2 clusters
[15:16] <Makere> I guess usb installation would be faster
[15:17] <Makere> oh wow
[15:17] <Makere> that ubuntu community guide is so shit compared to this
[16:05] <kiall> can anyone with a UEC instance running check if they can ping that instances public IP from itself?
[16:05] <kiall> (the euca community cloud cant, neither can my setup .. but I believe it should be able to)
[16:11] <smoser> kiall, i'll check
[16:12] <kiall> cool :) Lets see If i should quit my job or not ;)
[16:20] <Makere> lol
[16:20] <smoser> well, ping of 'public-ipv4' fails
[16:23] <kiall> right so .. at best thats an inconsistency with EC2, and worst a bug :)
[16:23] <kiall> I'll dig into iptables rules and see whats missing/wrong and file a bug
[16:32] <smoser> i tested in 10.04 host, not 10.10 it could have changed.
[16:32] <smoser> but it is a bug if its an inconsistency with ec2
[16:33] <kiall> I've tested with 10.10, but I can't guarantee my setup is correct
[16:34]  * kiall can *never* remember what hairpin NAT iptables rules should look like  .. google time
[16:37] <kiall> funny - it looks like the iptables rules are in place for hairpin NAT ...
[16:38] <smoser> kiall, i did you a favor, can you do one for me ?
[16:38] <kiall> sure
[16:38] <smoser> ec2metadata --local-ipv4
[16:38] <smoser> in an instance
[16:38] <kiall> oo unavailable
[16:38] <smoser> yeah.
[16:39] <smoser> eucalyptus metadata service doesn't like a trailing slash
[16:39] <smoser> http://169.254.169.254/2008-02-01/meta-data/local-ipv4/
[16:39] <smoser> is what ec2metadata asks for
[16:39] <kiall> Yea - without the / it works spot on
[16:41] <smoser> https://bugs.launchpad.net/ubuntu/+source/cloud-utils/+bug/676144
[16:51] <jmgalloway> anyone here good with ssh?
[16:51] <jmgalloway> I am getting an error when trying to connect to my walrus and cluster controller machines..
[17:22] <kiall> smoser, got the missing rule (evenually) ;)
[17:22] <smoser> oh. great. open bug and put it in there.
[17:22] <kiall> "-t nat -A POSTROUTING -s $VNET_PRIV_NET/16 -d $INSTANCE_PRIV_IP -j MASQUERADE" seems to do the trick
[17:23] <kiall> infact .. I wonder if one of the existing rules can be changed (now that I look at it and it works...)
[17:26] <kiall> Yup - one of the existing MASQ rules has a ! $PRIV_NET which is the real issue it seems...
[17:37] <kiall> smoser, worlds worst worded bug report ;)
[17:37] <kiall> https://bugs.launchpad.net/eucalyptus/+bug/676167
[17:48] <smoser> kiall, fyi, if you wanted to a.) be nice and b.) push your fix in
[17:49] <kiall> trying to figure out this hole bzr thing ;)
[17:49] <kiall> whole*
[17:49] <smoser> you could branch
[17:49] <smoser> bzr branch lp:ubuntu/eucalyptus/natty
[17:49] <smoser> wait
[17:49] <smoser> bzr branch lp:ubuntu/natty/eucalyptus
[17:50] <smoser> cd eucalyptus
[17:50] <smoser> quilt new kiall-fix-hairpin
[17:50] <smoser> quilt edit path/to/new/file
[17:50] <smoser> quilt refresh
[17:50] <smoser> dch -i
[17:50] <smoser> # edit the new message
[17:50] <smoser> bzr commit
[17:50] <kiall> aha .. git is way easier ;)
[17:51] <smoser> well, thats not really git versus bzr
[17:51] <smoser> more bzr packaging (using quilt)
[17:51] <smoser> but i will argue no further against git (as i tend to lean that way also)
[17:51] <kiall> lol
[17:53] <kiall> OMG @ dch -i .. what a timesaver
[17:55] <kiall> comitted rev 174 .. I presume I should find a patch file here somewhere/
[17:55] <kiall> ?
[17:58] <smoser> kiall, oh. i guess i shoudl have said you'd have
[17:58] <smoser> to bzr add debian/patches
[17:58] <smoser> i hope
[17:58] <smoser> you probalby didn't get hte patch added
[17:58] <kiall> Nope :)
[17:58] <kiall> add and commit again?
[17:59] <kiall> or some form of bzr history rewrite ;)
[18:02] <smoser> you can bzr uncommit
[18:02] <smoser> that is probably what i would do
[18:02] <smoser> uncommit
[18:02] <smoser> then, add
[18:02] <smoser> then 'debcommit'
[18:02] <smoser> oh, and make sure your debian/changelog has '(LP: #BUGNUM)'
[18:02] <smoser> that will tag the branch that you fixed that bug
[18:03] <smoser> and hten when you push the branch to somewhere (like 'bzr push lp:~yournamehere/ubuntu/maverick/eucalyptus/fix-public-addr-ping'
[18:03] <smoser> )
[18:03] <smoser> that will get automatically linked to the bug
[18:03] <smoser> then, you bother Daviey and tell him to not be lazy
[18:04] <Daviey> o/
[18:04] <kiall> Right so .. that should be pushed to lp:~kiall/ubuntu/natty/eucalyptus/fix-hairpin-nat ;)
[18:04] <Daviey> kiall: What is the bug #?
[18:05] <kiall> 676167
[18:05] <Daviey> bug #676167
[18:05] <kiall> BTW .. It reads like it was translated via google translate a few times .. I apologize ;)
[18:05] <Daviey> kiall: interesting... is that a regression?
[18:06] <kiall> smoser, tested 10.04, i tested 10.10 .. so I dont think so
[18:06] <Daviey> kiall: ok, thanks!
[18:07] <Daviey> kiall: looks good....
[18:07] <Daviey> 2 comments...
[18:08] <kiall> dooh
[18:08] <kiall> 1 see one of them
[18:08] <kiall> I see*
[18:08] <Daviey> for maverick, as it is post release, the pocket needs to be "maverick-proposed" not "maverick" (top line of debian/changelog)
[18:08] <Daviey> secondly, it would be awesome if the patch had DEP-3 "patch tagging"
[18:09] <Daviey> "http://dep.debian.net/deps/dep3/"
[18:09] <kiall> Right so .. First time doing anything other than a quick PPA ;)
[18:09] <Daviey> You can get an idea of what patch tagging looks like by looking at the other patches
[18:09] <Daviey> kiall: You've done great (and the hard part)!  I don't mind fixing them up before merging..
[18:10] <Daviey> otherwise, awesome if you do it :)
[18:10] <kiall> dont forget to remove the extra "network, slashnet, " I left in .. when re-doing after a clean clone ;)
[18:10] <kiall> (thats the 1 I spotted)
[18:10] <Daviey> kiall: the other thing, the version number for maverick-proposed should be "2.0+bzr1241-0ubuntu4.1"
[18:11] <kiall> aha I'll blame that one on "dch -i" making me thing it knew better ;)
[18:11] <Daviey> lol
[18:12] <Daviey> kiall: seriously awesome work tho...  i'm over the moon you've contributed this
[18:13] <kiall> lol .. 1 line patch .. cmon ;) (I work on some open source projects .. 1 lines aren't that hard to come by!)
[18:13] <Daviey> kiall: we've traditionally not had great success getting contributions outside the usual suspects..
[18:13] <Daviey> that is the main reason i'm pleased
[18:14] <Daviey> OK... i need to go and do some family time..
[18:14] <kiall> sure .. cya
[18:14]  * kiall gets back to my real work after 2 days on/off wondering what I had configured wrong ;)
[18:14] <Daviey> kiall: one more comment... can you add an impact statement to the bug....  why this is importiant it's fixed in stable versions?
[18:15] <Daviey> kiall: needs to be fixed in natty first, then either you - or me should backport it to maverick and lucid
[18:15] <kiall> sure ..
[18:15] <Daviey> \o/
[18:16] <Daviey> kiall: ok.. speak soon o/
[18:24] <kiall> Impact statement added (At least I think I wrote an impact statement ;) .. maybe! ) .. right. home, then sleep. cya!
[18:39] <kiall> oh god. reboot a server before I leave .. and ...
[18:39] <kiall> # shutdown -r now
[18:39] <kiall> -bash: /sbin/shutdown: Input/output error