| === kim0 is now known as kim0_3G | ||
| === whaley_ is now known as whaley | ||
| === rgreening_ is now known as rgreening | ||
| === mathiaz_ is now known as mathiaz | ||
| progre55 | hi guys. while installing "Ubuntu Enterprise Cloud" from the disc, I didnt mentions the correct IP ranges. Is there a way to edit it now? | 17:54 |
|---|---|---|
| ttx | progre55: yes, in /etc/eucalyptus/eucalyptus.conf | 17:57 |
| smoser | i'm guessing, but maybe dpkg-reconfigure eucalyptus-cc , then sudo restart eucalyptus CLEAN=1 | 17:57 |
| smoser | but ttx is probably right :) | 17:57 |
| * ttx checks | 17:58 | |
| progre55 | thanks, let me try ttx's way first =) | 17:58 |
| ttx | VNET_PUBLICIPS= | 17:58 |
| ttx | progre55: yes, that should work. | 17:58 |
| ttx | see http://manpages.ubuntu.com/manpages/maverick/en/man5/eucalyptus.conf.5.html for details | 17:59 |
| progre55 | ttx: thanks, appreciate | 17:59 |
| progre55 | smoser: thanks | 17:59 |
| ttx | also sudo restart eucalyptus CLEAN=1 afterwards | 18:00 |
| progre55 | okay | 18:00 |
| ttx | this is needed to take the new network config into account | 18:00 |
| === dendro-afk is now known as dendrobates | ||
| === dendro-afk is now known as dendrobates | ||
| SpamapS | hmm.. seems like karmic 32-bit instances take a long time to spawn.. or maybe I just got unlucky | 21:05 |
| patrickw | Hi. What happens when I upgrade the kernel on a running UEC node? Isn't the kernel chosen by the euca, not the node itself? | 21:39 |
| === kim0_3G is now known as kim0_vacation | ||
| smoser | patrickw, you are correct | 22:15 |
| smoser | nothing will happen | 22:15 |
| smoser | ubuntu kernel images don't get removed by an apt-get upgrade | 22:15 |
| smoser | so you'll still hvae the needed ramdisk and modules | 22:15 |
| smoser | your reboot will just take the old kernel | 22:15 |
| smoser | that said | 22:15 |
| smoser | that changes in maverick on EC2 | 22:16 |
| smoser | and UEC hosts running maverick guests can also service their own kernel. | 22:16 |
| smoser | the trick is that we supply a "kernel" that is a grub loader (and on amazon, you they provide a pv-grub "kernel" that we register our images with) | 22:16 |
| smoser | i' got to reboot. bbiab | 22:17 |
| patrickw | smoser: so if I *do* upgrade an image and rebundle, should I also add new kernel and ramdisk and register those and use them with the new image? I suppose if I'm just doing an apt-get upgrade that no packages will require new kernels? | 22:24 |
| smoser | you could use the old kernels / ramdisks | 22:34 |
| smoser | but if your upgrading/rebundling, probably better to get a new kernel/ramdisk. | 22:34 |
| SpamapS | hrm.. takes about 1 hour to build mysql 5.1 on a karmic m1.small.. :-p | 22:50 |
| erichammond | SpamapS: t1.small is designed for intermittent short high speed CPU bursts. It will get throttled if you try to run long CPU jobs on it. | 23:00 |
| erichammond | er, scratch that. I was talking about t1.micro and you're talking about m1.small. | 23:00 |
| erichammond | SpamapS: m1.small is a horrible slow machine :) Use c1.medium for 5X the CPU at 2X the price. | 23:00 |
| SpamapS | was thinking I should build on top of tmpfs too | 23:02 |
| SpamapS | not really making good use of the 1.5G of RAM | 23:02 |
| SpamapS | and really, it only takes like 20 min to compile.. its the regression tests that take 40 | 23:03 |
| === mathiaz_ is now known as mathiaz | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!