User1: kiall, it doesn't do that in default installations
User1: 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
User2: no problem .. one other question - should instances be able to communicate with each other via their public IPs then?
User2: (I'm seeing some strange NAT "stuff" happening at the mo ;))
User2: meaning there is no way for 2 instances to talk without knowing their private IPs (not exactly ideal...)
User1: both public and private should work for instance-to-instance traffic
User2: 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(
User3: I'm having trouble running instances
User3: they get stuck on pending
User3: can't get the bundled images to run at all
User3: let's put this otherway, has ANYONE managed to ANY images downloaded from the website and HOW?
User3: I'm losing all hope
User2: Makere, i scrapped the "store" images .. they simply didnt work!
User2: Downloaded the 10.10 uec image from uec-images.ubuntu.com and used the uec-publish-tarball command to push it up..
User2: worked like a charm
User2: (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  )
User3: User2 well the uec-images on didn't work for me
User3: got stuck on pending :(
User3: no errors on any log, nc, nc
User3: cc
User3: kiall, you runnin lucid or maverick?
User2: maverick
User3: controllers on seperate pc's?
User3: one or more clusters?
User3: just [Brunning thevm's without ramdisk?
User2: a combined CLC/CC/SC/Walrus and a few nodes... (so 1 cluster)
User2: and no ramdisk for the 10.10 uec-images EMI
User3: I'm trying 2 clusters with 1 cloud controller and walrus and 2 cluster controllers/sotrage controllers
User2: Havent done a split setup yet .. but I hope your starting simple and going with 1 cluster and 1 NC first ;)
User3: so I guess the problem has to do something with splitting them :p
User2: ...and going with 1 clc, 1 cc, 1 nc*
User2: anyway .. I thing I found was, once I had tried a load of different things .. stop. wipe. reinstall with your new knowledge ;)
User2: 1 thing i found*
User2: 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)
User3: yea
User3: I did CD install
User3: problem is that we've done it multiple times now
User3: and this is not the first time we get the problem
User3: User2 have you updated the packages?
User3: on the nodes or the "Controller"
User2: 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)
User3: setup bridges?
User3: :O
User3: no mention of that in the installation guide
User2: lol ... im sure it mentions it loads of times ;)
User3: https://help.ubuntu.com/community/UEC/CDInstall atleast this one doesn't
User2: 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
User2: doesnt leave anything out
User2: wow... that URL wasnt exactly the one I was going for ;)
User2: but it should work ;P
User2: LOL .. it actually doesnt mention bridges ..â¥
User3: yea
User3: :)
User2: yea .. just go to chapter one of that link (and do it the CD install way instead from my exp) .. ;)
User3: so annoying >_>
User3: that guide looks like million times better
User3: thanks
User3: I wonder if I should start from the beginning
User3: zzz takes 2 hours to setup with 2 clusters
User3: I guess usb installation would be faster
User3: oh wow
User3: that ubuntu community guide is so shit compared to this
User2: can anyone with a UEC instance running check if they can ping that instances public IP from itself?
User2: (the euca community cloud cant, neither can my setup .. but I believe it should be able to)
User1: kiall, i'll check
User2: cool :) Lets see If i should quit my job or not ;)
User3: lol
User1: well, ping of 'public-ipv4' fails
User2: right so .. at best thats an inconsistency with EC2, and worst a bug :)
User2: I'll dig into iptables rules and see whats missing/wrong and file a bug
* You're now known as ubuntulog
User1: i tested in 10.04 host, not 10.10 it could have changed.
User1: but it is a bug if its an inconsistency with ec2
User2: I've tested with 10.10, but I can't guarantee my setup is correct
 * kiall can *never* remember what hairpin NAT iptables rules should look like  .. google time
User2: funny - it looks like the iptables rules are in place for hairpin NAT ...
User1: kiall, i did you a favor, can you do one for me ?
User2: sure
User1: ec2metadata --local-ipv4
User1: in an instance
User2: oo unavailable
User1: yeah.
User1: eucalyptus metadata service doesn't like a trailing slash
User1: http://91.69.162.6/2008-02-01/meta-data/local-ipv4/
User1: is what ec2metadata asks for
User2: Yea - without the / it works spot on
User1: https://bugs.launchpad.net/ubuntu/+source/cloud-utils/+bug/676144
User4: Launchpad bug 676144 in cloud-utils "ec2metadata should not add trailing / to requests" [Undecided,New]
* You're now known as ubuntulog_
* You're now known as ubuntulog
User5: anyone here good with ssh?
User5: I am getting an error when trying to connect to my walrus and cluster controller machines..
User2: smoser, got the missing rule (evenually) ;)
User1: oh. great. open bug and put it in there.
User2: "-t nat -A POSTROUTING -s $VNET_PRIV_NET/16 -d $INSTANCE_PRIV_IP -j MASQUERADE" seems to do the trick
User2: infact .. I wonder if one of the existing rules can be changed (now that I look at it and it works...)
User2: Yup - one of the existing MASQ rules has a ! $PRIV_NET which is the real issue it seems...
User2: smoser, worlds worst worded bug report ;)
User2: https://bugs.launchpad.net/eucalyptus/+bug/676167
User4: Launchpad bug 676167 in eucalyptus "Hairpin NAT on CC disabled - EC2 inconsistency" [Undecided,New]
User1: kiall, fyi, if you wanted to a.) be nice and b.) push your fix in
User2: trying to figure out this hole bzr thing ;)
User2: whole*
User1: you could branch
User1: bzr branch lp:ubuntu/eucalyptus/natty
User1: wait
User1: bzr branch lp:ubuntu/natty/eucalyptus
User1: cd eucalyptus
User1: quilt new kiall-fix-hairpin
User1: quilt edit path/to/new/file
User1: quilt refresh
User1: dch -i
User1: # edit the new message
User1: bzr commit
User2: aha .. git is way easier ;)
User1: well, thats not really git versus bzr
User1: more bzr packaging (using quilt)
User1: but i will argue no further against git (as i tend to lean that way also)
User2: lol
User2: OMG @ dch -i .. what a timesaver
User2: comitted rev 174 .. I presume I should find a patch file here somewhere/
User2: ?
User1: kiall, oh. i guess i shoudl have said you'd have
User1: to bzr add debian/patches
User1: i hope
User1: you probalby didn't get hte patch added
User2: Nope :)
User2: add and commit again?
User2: or some form of bzr history rewrite ;)
User1: you can bzr uncommit
User1: that is probably what i would do
User1: uncommit
User1: then, add
User1: then 'debcommit'
User1: oh, and make sure your debian/changelog has '(LP: #BUGNUM)'
User1: that will tag the branch that you fixed that bug
User1: and hten when you push the branch to somewhere (like 'bzr push lp:~yournamehere/ubuntu/maverick/eucalyptus/fix-public-addr-ping'
User1: )
User1: that will get automatically linked to the bug
User1: then, you bother Daviey and tell him to not be lazy
User6: o/
User2: Right so .. that should be pushed to lp:~kiall/ubuntu/natty/eucalyptus/fix-hairpin-nat ;)
User6: User2 What is the bug #?
User2: 676167
User6: bug #676167
User4: Launchpad bug 676167 in eucalyptus "Hairpin NAT on CC disabled - EC2 inconsistency" [Undecided,New] https://launchpad.net/bugs/676167
User2: BTW .. It reads like it was translated via google translate a few times .. I apologize ;)
User6: User2 interesting... is that a regression?
User2: smoser, tested 10.04, i tested 10.10 .. so I dont think so
User6: User2 ok, thanks!
User6: User2 looks good....
User6: 2 comments...
User2: dooh
User2: 1 see one of them
User2: I see*
User6: for maverick, as it is post release, the pocket needs to be "maverick-proposed" not "maverick" (top line of debian/changelog)
User6: secondly, it would be awesome if the patch had DEP-3 "patch tagging"
User6: "http://dep.debian.net/deps/dep3/"
User2: Right so .. First time doing anything other than a quick PPA ;)
User6: You can get an idea of what patch tagging looks like by looking at the other patches
User6: User2 You've done great (and the hard part)!  I don't mind fixing them up before merging..
User6: otherwise, awesome if you do it :)
User2: dont forget to remove the extra "network, slashnet, " I left in .. when re-doing after a clean clone ;)
User2: (thats the 1 I spotted)
User6: User2 the other thing, the version number for maverick-proposed should be "2.0+bzr1241-0ubuntu4.1"
User2: aha I'll blame that one on "dch -i" making me thing it knew better ;)
User6: lol
User6: User2 seriously awesome work tho...  i'm over the moon you've contributed this
User2: lol .. 1 line patch .. cmon ;) (I work on some open source projects .. 1 lines aren't that hard to come by!)
User6: User2 we've traditionally not had great success getting contributions outside the usual suspects..
User6: that is the main reason i'm pleased
User6: OK... i need to go and do some family time..
User2: sure .. cya
 * kiall gets back to my real work after 2 days on/off wondering what I had configured wrong ;)
User6: User2 one more comment... can you add an impact statement to the bug....  why this is importiant it's fixed in stable versions?
User6: User2 needs to be fixed in natty first, then either you - or me should backport it to maverick and lucid
User2: sure ..
User6: \o/
User6: User2 ok.. speak soon o/
User2: Impact statement added (At least I think I wrote an impact statement ;) .. maybe! ) .. right. home, then sleep. cya!
User2: oh god. reboot a server before I leave .. and ...
User2: # shutdown -r now
User2: -bash: /sbin/shutdown: Input/output error
ubuntu-cloud
Ubuntu IRC