Ubuntu Server Eucalyptus Testers Needed

[px43]

A few comments on some troubles I have had during my test deployment..
following https://help.ubuntu.com/community/UEC/CDInstall
Using the 10.04 beta install disk, installing all components on a single piece of hardware

First of all, when trying to run either emi-DF89105E or emi-DF89105E, which are the only 32 and 64 bit ubuntu server images currently available in the store, ec2-init hangs for about an hour before the instance starts up sshd, which is damn annoying, and I haven't figured out how to get past that on first run (the first thing I normally to when I can log in is apt-get remove ec2-init).

Once ssh is running, I have found that the user I need to use is actually "root", not "ubuntu" as described in the documentation. Even then, pubkey authentication occasionally will fail on some instances.

One thing I have also had trouble with is my instances not surviving reboots. The files for the instances usually seem to be there after a reboot, and euca-describe-instances says they are pending for a while, and then terminates them and wipes all the files (including the console log). I figured out that I could set MANUAL_INSTANCES_CLEANUP to 1 in the eucalyptus.conf, which saves the images from being wiped (sometimes), but even then, I have no idea how to launch the instance again. I even used ps aux to grab the kvm command and all the proper arguments, but running the command manually still failed.

How am I supposed to install kernel updates etc if all my instances die when I reboot the host? Is there some sort of euca-save-instance euca-restore-instance command that I am just not seeing or something? I am not really even sure what logs I should be looking at. The only ones I have really been looking into was the cc.log, nc.log, and the console.log in the instance directory. Any tip or advice on something I may have overlooked would be greatly appreciated, thanks.

[kjordan2001]

Nevermind what I wrote here if anyone saw my previous stuff, apparently I can do "sudo service eucalyptus stop" and that stops all services and then I can do "sudo service eucalyptus-cc start" which starts that and the eucalyptus-sc service to get just a CC and SC running on a server without having the cloud controller there. I figure since I might have multiple clusters later on, that's the best way to set it up to have the cluster controller and storage controller for that cluster on one box and another box for tying them all together.

@px43, I'm not sure why you'd want to get that same instance running again unless you had some piece of data that you just needed from it. Otherwise, just start up another instance and mount a volume for persistent information. It also sounds like something is somewhat messed up when you start an instance since the root user shouldn't be the user that gets your login key. I've had mine take a while to startup before too as it copied and prepared the image. After that though, it should cache the image. Hopefully at some point using the web UI eucalyptus will let you move an instance to another server so that you can do maintenance on that server, but at the moment if you reboot a server or it crashes, you lose all instances. The manual cleanup was mostly meant for debugging an instance and not starting it back up through it.

[dbrooke]

I can't seem to spark any conversation about Cloud Computing And/Or Eucalyptus on the "Server Platforms" discussion. What's the deal here, is this too new of a service that people don't know anything about it? Am in the wrong place? Is it too complicated? Do I smell? ... maybe all 4.

Donovan

[Rusty au Lait]

Hello everyone. I started studying UEC late last summer. After a month or so I gave up thinking I needed to know more about linux before I could go on. I got clobbered with the network issues.
Long story short, I picked it up again in May. Downloaded the Lucid version and started again. It did not install the first time but it only took me a day or two to set it up. Started up an instance, ssh'd in, downloaded Apache just as quick as you please. Lesson?
Two steps:
(1) start and end with a clean install.
(2) if anything fails go to step 1.
So. I'll let you know how things are going. Ciao

[bmullan]

I can't seem to spark any conversation about Cloud Computing And/Or Eucalyptus on the "Server Platforms" discussion. What's the deal here, is this too new of a service that people don't know anything about it? Am in the wrong place? Is it too complicated? Do I smell? ... maybe all 4.

Donovan

I've sent an email to the forum admins asking if there could be a separate forum section for UEC ... since it doesn't really fit specifically with the "server" section.

I've not heard or seen any addition tho'

[Rusty au Lait]

OK. I made it. I'm in the clouds. Tiny clouds in my basement. Two instances up w/ apache on both. I can reach each from the CLC but not from another host. This host has Ubuntu Desktop. I can start instances from this host using the command line but not elasticFox. I can not reach the instances that are running from this host (web, nor ssh, nor ping). Private keys or something like that. So, now to save instances that have changed and i'm ready to build my own. Any ideas?
later

[ddemarco]

I am having some issues with 10.4 and the cloud. Is there a sub forum for this sort of stuff? I've posted to the dev-list, made a post here, and on the Euca open site.

What I'm looking for is a community dedicated/subsection for Cloud on Ubuntu. I've got 15-20 nodes and activly testing.

[Rusty au Lait]

If you have 15 nodes up then you are way ahead of me. I have 1 node. I'm not even to a managed-novlan. I have not found any other thread but this one. Can now ping the instance from a host on the network but no web (I installed lamp). I can however, get to the instance's web page from CLC using w3m. Good luck.
Did you mean 10.04 Lucid Lynx?

[santhony]

Is this thread still active??

I've been working on my cloud installation the past month.

2 Computers, 1 for Node and 1 for CC,SC,Walrus.

CC,SC,Walrus (aka server1 192.168.1.10):
AMD 3 Core
4 GB DDR2 @ 1066
500 MB SATA HD
eth0-static 192.168.1.10
bios virtualization disabled


NODE Controller (aka server2 192.168.1.11):
AMD 4 Core
4 GB DDR2 @ 1066
500 GB HD
eth0-manual
br0-static 192.168.1.11
bios virtualization enabled

I have no issues getting VNET_MODE="MANAGED_NOVLAN" working.

I cannot get VNET_MODE="SYSTEM" mode working....

I have been using the install instructions of:
https://help.ubuntu.com/community/UEC

What I need to confirm is the eucalytpus.conf and eucalytpus.local.conf
of both the Server1 and Server2.

Here are my eucalytpus.conf Files:

server1:
eucalytpus.conf:

EUCALYPTUS="/"
EUCA_USER="eucalyptus"

# Affects: CLC, Walrus, SC
DISABLE_DNS="Y"
DISABLE_ISCSI="Y"
JVM_MEM="512m"

# Affects: CC, NC
# See: **NOTE** below
ENABLE_WS_SECURITY="Y"
LOGLEVEL="DEBUG"
VNET_PUBINTERFACE="eth0"
VNET_PRIVINTERFACE="eth0"
VNET_MODE="SYSTEM"

# Affects: CC
# See: **NOTE** below
CC_PORT="8774"
SCHEDPOLICY="ROUNDROBIN"
POWER_IDLETHRESH="300"
POWER_WAKETHRESH="300"
NC_SERVICE="axis2/services/EucalyptusNC"
#VNET_DHCPDAEMON="/usr/sbin/dhcpd3"
#VNET_DHCPUSER="dhcpd"
NODES=""
#VNET_ADDRSPERNET="32"
#VNET_SUBNET=""
#VNET_NETMASK=""
#VNET_DNS=""
#VNET_PUBLICIPS=""

# Affects: NC
NC_PORT="8775"
HYPERVISOR="kvm"
MANUAL_INSTANCES_CLEANUP=0
VNET_BRIDGE="br0"
INSTANCE_PATH="/var/lib/eucalyptus/instances/"

server1 eucalytpus.local.conf
# /etc/eucalyptus/eucalyptus.local.conf

# This file is read and written by euca_conf(8)
# WARNING: You should *never* edit this file directly.

# To modify Eucalyptus parameters, either use euca_conf(8), or
# edit /etc/eucalyptus/eucalyptus.conf according to eucalyptus.conf(5).


# network configuration from the input configuration file
VNET_MODE="SYSTEM"
#VNET_SUBNET="172.19.0.0"
#VNET_NETMASK="255.255.0.0"
#VNET_DNS="192.168.1.2"
#VNET_ADDRSPERNET="32"
#VNET_PUBLICIPS="192.168.1.30-192.168.1.139"


server2 eucalyptus.conf

# /etc/eucalyptus/eucalyptus.conf
#
# These are the Ubuntu Enterprise Cloud's default Eucalyptus parameters.

# Affects: All
# See: **NOTE** below
EUCALYPTUS="/"
EUCA_USER="eucalyptus"

# Affects: CLC, Walrus, SC
DISABLE_DNS="Y"
DISABLE_ISCSI="Y"
JVM_MEM="512m"

# Affects: CC, NC
# See: **NOTE** below
ENABLE_WS_SECURITY="Y"
LOGLEVEL="DEBUG"
VNET_PUBINTERFACE="eth0"
VNET_PRIVINTERFACE="eth0"
VNET_MODE="SYSTEM"

# Affects: CC
# See: **NOTE** below
CC_PORT="8774"
SCHEDPOLICY="ROUNDROBIN"
POWER_IDLETHRESH="300"
POWER_WAKETHRESH="300"
NC_SERVICE="axis2/services/EucalyptusNC"
#VNET_DHCPDAEMON="/usr/sbin/dhcpd3"
#VNET_DHCPUSER="dhcpd"
NODES=""
VNET_ADDRSPERNET="32"
#VNET_SUBNET=""
#VNET_NETMASK=""
#VNET_DNS=""
#VNET_PUBLICIPS=""

# Affects: NC
NC_PORT="8775"
HYPERVISOR="kvm"
MANUAL_INSTANCES_CLEANUP=0
VNET_BRIDGE="br0"
INSTANCE_PATH="/var/lib/eucalyptus/instances/"

server2 eucalytpus.local.conf (it is Empty)

# /etc/eucalyptus/eucalyptus.local.conf

# This file is read and written by euca_conf(8)
# WARNING: You should *never* edit this file directly.

# To modify Eucalyptus parameters, either use euca_conf(8), or
# edit /etc/eucalyptus/eucalyptus.conf according to eucalyptus.conf(5).

[Rusty au Lait]

I am not experienced yet. Mine works in system mode. Did you disable bios virtualization on the node?