CSS Corp Open Source Services

[Eucalyptus Beginner’s Guide – UEC edition] Chapter 2 – Installation & Configuration

with 42 comments

Chapter 1
Introduction to UEC and its components
Chapter 3
Web Interface

The following sections describe how to install and configure a basic UEC setup spanning 3 servers. 2 Servers(Server1 and Server2) will run Lucid 64-bit server version and the third server will run Lucid Desktop 64-bit version(Client1). We have decided on installing the Desktop version on Client1 so that we can use Firefox or other browsers to access the web interface of UEC and also to use RDP/VNC clients during the image creation process.

UEC SETUP

What we have used as a sample setup is a typical minimal Eucalyptus setup. Client1 above need not be a dedicated machine. If you need to setup Eucalyptus on a single server, you can refer to UEC: CC and NC on a single machine . However, such a setup will not support Managed and Managed-NOVLAN modes of networking.

Hardware Server 1 Server 2 Server 3
Minimum Suggested Minimum Suggested Minimum Suggested
CPU 1GHz 2 x 2GHz VT extensions VT, 64Bit, Multicore VT extensions VT, 64Bit, Multicore
Memory 1 GiB 2 GiB 1 GiB 4 GiB 1 GiB 2 GiB
Disk 5400rpm IDE 7200rpm SATA 5400rpm IDE 7200rpm SATA or SCSI 5400rpm IDE 7200rpm SATA or SCSI
Disk Space 40GB 200GB 40GB 100GB 40GB 100GB
Networking 100Mbps 1000Mbps 100Mbps 1000Mbps 100Mbps 1000Mbps

Note:

UEC installation is very similar to the installation of Ubuntu Server, the only difference is the additional configuration screens for the UEC components. The following instructions only cover the UEC specific options as it is assumed that you are familiar with the installation of Ubuntu server.

For ease of understanding, the instructions here in this chapter and the rest of the book assume the following sample setup. Please make necessary modifications to suit your setup.

Server 1 Server 2 Client
Common Username to log-in “uecadmin”
Functionality CLC, CC and
Walrus
NC Bundling and Web Interface Client
No. of NICs eth0 – (Enterprise N/W)
eth1 – (Eucalyptus N/W)
eth0 – (Eucalyptus Network) eth0 – (Enterprise Network)
eth1 – (Eucalyptus Network)
IP Addresses eth0 – 192.168.10.121
(set during install)
eth1 – 192.168.20.1
(set after install)
eth0 – 192.168.20.2
(set during install)
eth0 – ???
eth1 – ???
Hostname server1.example.com server2.example.com client1.example.com
Enterprise Name Servers 192.168.10.2
192.168.10.3
192.168.10.2
192.168.10.3
192.168.10.2
192.168.10.3
Gateway IP 192.168.10.100 192.168.20.1 192.168.10.2
192.168.10.3
  • The gateway for Server2 is set to the IP of the CC – IP 192.168.20.1 . This will enable the Server2 to connect to the enterprise network through Server1 (CC).
  • Server1 is a 64-bit server and Server2 is a 64-bit VT-enabled server.
  • The enterprise network runs on a class ‘C’ private network – 192.168.10.0/255.255.255.0
  • IP addresses allocated for the cloud instances as public IP addresses : 192.168.10.200-192.168.10.220 ( Enterprise range )
  • The UEC components will use a dedicated class ‘C’ private network for their interconnections – 192.168.20.0/255.255.255.0
  • Cluster Name – “myueccluster”

Server1

Installation

  • Boot the server off the Ubuntu Server 10.04 CD. At the graphical boot menu, select “Install Ubuntu Enterprise Cloud” and proceed with the basic installation steps.
  • Installation only lets you set up the IP address details for one interface. Please do that for eth0.
  • You will need to choose certain configuration options for your UEC, during the course of the install:
  • Cloud Controller Address – Leave this blank as server1 is the Cloud Controller in this setup.
  • Cloud Installation Mode – Select ‘Cloud controller’, ‘Walrus storage service’, ‘Cluster controller’ and ‘Storage controller’.
  • Network interface for communication with nodes – eth1
  • Eucalyptus cluster name – myueccluster
  • Eucalyptus IP range – 192.168.10.200-192.168.10.220

Post Install Steps & Configuration

  • Set up static IP for the second network interface eth1 by adding the following to /etc/network/interfaces
auto eth1
iface eth1 inet static
address 192.168.20.1
netmask  255.255.255.0
network 192.168.20.0
broadcast 192.168.20.255
  • After making the above changes, run the following command to restart the networking.
uecadmin@server1:~$sudo /etc/init.d/networking restart
  • Make sure that you have the latest version of EUCALYPTUS.
uecadmin@server1:~$sudo apt-get update
uecadmin@server1:~$sudo apt-get upgrade eucalyptus
  • Install the NTP package, this machine is going to act as an NTP server for the nodes. The time on all components of UEC will have to be in sync. Since CLC is connected to Internet, we can run ntp server on it and have other components sync to it.
uecadmin@server1:~$sudo apt-get install ntp
  • Open the file /etc/ntp.conf and add the following two lines to make sure the server serves time even when its connectivity to the Internet is down. The following settings makes sure that the ntp server uses its own clock as the clock source.
server 127.127.1.0
fudge  127.127.1.0 stratum 10
  • Restart ntp service to make the changes effective.
uecadmin@server1:~$sudo /etc/init.d/ntp restart
  • Save the changes and restart CC.
uecadmin@server1:~$sudo start eucalyptus-cc CLEAN=1

Server2

Installation

  • Boot the server off the Ubuntu Server 10.04 CD. At the graphical boot menu, select “Install Ubuntu Enterprise Cloud” and proceed with the basic installation steps.
  • Installation only lets you set up the IP address for one interface. Please do that for eth0 by setting up the private IP – 192.168.20.2
  • You will need to choose certain configuration options for your UEC, during the course of the install. You can ignore all the settings, except the following:
  • Cloud Controller Address – 192.168.20.1
  • Cloud Installation Mode – Select ‘Node Controller’
  • Gateway – 192.168.20.1 ( IP of the CC )

Post Install Steps & Configuration

  • Add your DNS server details to /etc/resolv.conf
nameserver 192.168.10.2
nameserver 192.168.10.3
  • Make sure that you have the latest version of EUCALYPTUS.
uecadmin@server2:~$sudo apt-get update
uecadmin@server2:~$sudo apt-get upgrade eucalyptus
  • Install the NTP package to synchronize with the NTP server
uecadmin@server2:~$sudo apt-get install ntp
  • Open the file /etc/ntp.conf and append the following line
server 192.168.20.1
  • Restart ntp service to make the changes effective.
uecadmin@server2:~$sudo /etc/init.d/ntp restart
  • Open the file /etc/eucalyptus/eucalyptus.conf and make the following changes
VNET_PUBINTERFACE="br0"
VNET_PRIVINTERFACE="br0"
VNET_BRIDGE="br0"
VNET_DHCPDAEMON="/usr/sbin/dhcpd3"
VNET_DHCPUSER="dhcpd"
VNET_MODE="MANAGED-NOVLAN"
  • After making the above changes, run the following commands
uecadmin@server2:~$sudo restart eucalyptus-nc-publication
uecadmin@server2:~$sudo restart eucalyptus-nc
  • Install CC’s ssh public key to NC
  • On the Node Controller, temporarily set a password for the eucalyptus user:
uecadmin@server2:~$sudo passwd eucalyptus
  • On the Cluster Controller:
uecadmin@server2:~$sudo -u eucalyptus ssh-copy-id -i ~eucalyptus/.ssh/id_rsa.pub eucalyptus@192.168.20.2
  • You can now remove the password of the eucalyptus account on the Node:
uecadmin@server2:~$sudo passwd -d eucalyptus

Client1

The purpose of Client1 machine is to interact with the Cloud setup, for bundling and registering new Eucalyptus Machine Images (EMI)

Installation

  • Boot the Desktop off the Ubuntu Desktop 10.04 CD and install. The Desktop would be on the enterprise network and obtaining an IP address through DHCP.
  • Install KVM to help us install images on KVM platform and bundle them.
uecadmin@client1:~$apt-get install qemu-kvm

Post Install Configuration

  • Install euca2ools to be able to manage the cloud from it.
uecadmin@client1:~$sudo apt-get install euca2ools
  • Login to the web interface of CLC by using the following link https://192.168.10.121:8443. The default username is ‘admin’ and the default password is ‘admin’.
  • Note that the installation of UEC installs a self signed certificate for the web server. The browser will warn you about the certificate not having been signed by a trusted certifying authority. You can authorize the browser to access the server with the self signed certificate. Instruction on how to install a valid certificate signed by a trusted certifying authority is beyond the scope of this guide.
  • When you login for the first time, the web interface prompts you to change the password and provide the email ID of the admin. After completing this mandatory step, download the credentials archive from https://192.168.10.121:8443/#credentials and save it in the ~/.euca directory.
  • Extract the credentials archive.
cd .euca
unzip mycreds.zip
  • Source eucarc script to make sure that the environmental variables used by euca2ools are set properly.
  • To verify that euca2ools are able to communicate with the UEC, try fetching the local cluster availability details:
$ . ~/.euca/eucarc
 euca-describe-availability-zones verbose

You should see something like the following if it works properly:

$ euca-describe-availability-zones verbose
 AVAILABILITYZONE        myueccluster    192.168.10.121
 AVAILABILITYZONE        |- vm types     free / max   cpu   ram  disk
 AVAILABILITYZONE        |- m1.small     0016 / 0016   1    128     2
 AVAILABILITYZONE        |- c1.medium    0014 / 0014   1    256     5
 AVAILABILITYZONE        |- m1.large     0007 / 0007   2    512    10
 AVAILABILITYZONE        |- m1.xlarge    0003 / 0003   2   1024    20
 AVAILABILITYZONE        |- c1.xlarge    0001 / 0001   4   2048    20

If you see the free/max VCPUs as 0 in the above list, it means the node did not get registered automatically. Please use the following on Server1 and approve when prompted to add 192.168.20.2 as the Node Controller.

uecadmin@client1:~$sudo euca_conf --discover-nodes
Chapter 1
Introduction to UEC and its components
Chapter 3
Web Interface
About these ads

42 Responses

Subscribe to comments with RSS.

  1. You set Eucalyptus IP range – 192.168.10.200-192.168.10.220 for Server1. This is part of your Enterprise Network.
    That seems wrong for me… Should’nt this be from the Eucalyptus 192.168.20.xxx range?

    Rainer

    June 14, 2010 at 7:32 pm

    • Hi Rainer,

      The public IP address range should be in the enterprise range, so that the cloud instance is accessible from anywhere within the LAN. In our case, the LAN subnet is 192.168.10.xxx. So the selection of public IP address range as 192.168.10.200-192.168.10.220 is correct.

      In case you have REAL public IP address, you can assign them as the range of IP addresses, so that the cloud instance is accessible over internet.

      Hope that answers your question.

      Kiran

      kiranmurari

      June 15, 2010 at 11:24 am

  2. Hi Kiran,
    yes got it – it’s the range of IPs that the instances on the node get.

    On the node I have br0 which is a bridge on eth0 in eucalyptus network – I plugged eth1 in the enterprise network switch but it is not configured.
    But how are the instances reachable if the node does not have an interface in enterprise range?

    Rainer

    Rainer

    June 15, 2010 at 4:23 pm

    • Cluster Controller takes care of the routing between the instances and outside world. This is done by a combination of:
      * adding iptables rules
      * attaching the public IPs of the instances to the public interface of CC. (On CC, based on your VNET_PUBINTERFACE and VNET_PRIVINTERFACE setting, you would see eth0:pub or eth1:pub in “ip addr show” output)

      kiranmurari

      June 15, 2010 at 4:30 pm

      • Kiran,

        With this said, could you give us a bit more info on exactly what needs to be added to the following?

        * adding iptables rules

        * attaching the public IPs of the instances to the public interface of CC. (On CC, based on your VNET_PUBINTERFACE and VNET_PRIVINTERFACE setting, you would see eth0:pub or eth1:pub in “ip addr show” output)

        I am in the middle of building out the NC, but can’t seem to get it to be able to route to the internet to pull down the packages.

        djchrishart

        June 16, 2010 at 5:09 pm

      • Hi,

        CC automatically takes care of adding the iptables rules and attaching the public IP to the public interface of the instance. No manual configuration is needed in this regard.

        In order to have internet connectivity on NC, please configure NC’s gateway as the private IP address of the CC. (192.168.20.1 in above setup)

        Hope that helps.

        Kiran

        kiranmurari

        June 17, 2010 at 12:11 pm

  3. Hi

    I’m a a bit confused here as to how to set this up.

    I know that three machines are required (one for the CLC, one for NC and one as a client machine), but do I need to have two switches. or am I not reading the diagram at the top of this page correctly.

    James Jackson

    July 17, 2010 at 12:29 am

    • Hi,

      The intention is to stress on the need for having 2 NICs on the CC, so that one NIC is used for communicating with the NC and the other NIC is for communicating with your LAN network. In case, two switches are not available, CC and NC can be connected via a cross cable.

      Hope that helps.

      cheers,
      Kiran

      kiranmurari

      July 20, 2010 at 12:00 pm

      • Thanks for responding to my last enquiry.

        I have managed to get as far as setting up the client.

        I am unsure as to how to “Source eucarc script to make sure that the environmental variables used by euca2ools are set properly”. which commands should I enter for this to work.

        Thanks

        James Jackson

        July 20, 2010 at 9:05 pm

  4. Please disregard last comment – I have managed to source the “eucarc” directory.

    I have encountered another problem though

    after entering the “euca-describe-availability-zones verbose” command I can see the table but the VCPU’s are all set to zero so I entered the command recommended by this guide into server 1 to discover the node:-

    “uecadmin@client1:~$sudo euca_conf –discover-nodes”

    When I do this I receive a message stating:

    “INFO: We expect all nodes to have eucalyptus installed in //var/lib/eucalyptus/keys for key synchronisation.”

    Have you any advice for me on how to rectify this problem

    Thanks,
    James

    James Jackson

    July 22, 2010 at 8:04 pm

  5. Kiran,

    Have a question on the routing mentioned above.

    My setup uses IPs of the Enterprise LAN as Public IPs just like your setup.
    My CC has 10.44.171.22 and 172.19.1.1 ( SINGLE NIC CARD )
    My NC has 10.44.171.23
    My Client has 10.44.171.21
    My public IP range is 10.44.171.24- 10.44.171.25 ( 2 IPs)
    All my 3 machines are connected to the enterprise switch and no private switch is involved.
    Gateway on 21, 22, 23 is specified as 10.44.171.1

    When my instance runs it gets 171.24 from Public IP and 1.2 from the pvt pool.

    Here are my observations:
    1. From 10.44.171.21 ( Client )
    Ping to 22 OK, Ping to 23 OK Ping to 24 FAILS

    2. From 10.44.171.22 (CC)
    Ping to 1.2 OK, Ping to 171.24 OK

    3. From 10.44.171.22 (NC)
    Ping to 1.2 Fails, Ping to 171.24 Fails

    4. From 1.2 ( Instance)
    Ping to 171.1 OK, Ping to 171.22 OK, Ping to 171.23 OK

    Also tried to add a route on Client machine with the CC as the gateway using this command. But it still did not connect.
    – sudo route add -host 10.44.171.24 netmask 0.0.0.0 gw 10.44.171.22 dev eth0

    Am foxed on this network problem and seek your assistance

    Krishna Iyer

    August 7, 2010 at 5:49 pm

  6. I have followed the instructions, everything was OK until I began to configure eth1 in Server 1. When I ran the command ” sudo /etc/init.d/networking restart”, the output was “Don’t seem to be have all the variables for eth1/inet. Failed to bring up eth1.” . Is your “PRIVATE SWITCH” a “switch ” or a “router ” ? thanks

    jafelee

    October 11, 2010 at 4:35 pm

    • Hi,

      We have used a “switch” not a “router”. Please check if there are any typos or if you have missed any parameters in /etc/network/interfaces.

      Kiran

      kiranmurari

      October 15, 2010 at 11:20 am

  7. Hi I am a beginner of UEC.
    Please answer me this question.

    Server2 has private address 192.168.20.2 and connected to Server1 via PRIVATE SWITCH.
    By configuration of this manual,there is no settings about router.

    How Server2 is connected to internet through Server1?

    Sotohiro Terashima

    October 14, 2010 at 12:33 pm

    • Hi,

      The first interface of Server1 is connected to the Enterprise LAN or directly to internet. Second interface is the private network. Since the private IP of Server1 is the gateway of Server2, the traffic to internet will be routed through Server1. After the NC (Server2) is registered with CC (Server1), the routing to NC (Server2) and the instances running on NC is taken care by CC (Server1).

      Hope that helps.

      Kiran

      kiranmurari

      October 15, 2010 at 11:29 am

  8. Thank you Kiran for your reply.

    But for me configuration route using iptables was effective.
    Such as below:

    internal_ip=’192.168.10.0/24′
    iptables -A FORWARD -i eth1 -o eth0 -s $internal_ip -j ACCEPT
    iptables -A FORWARD -m state –state ESTABLISHED,RELATED -j ACCEPT

    Sotohiro Terashima

    October 29, 2010 at 1:43 am

    • Hi I made a misstake.

      internal_ip=’192.168.10.0/24′
      iptables -A FORWARD -i eth1 -o eth0 -s $internal_ip -j ACCEPT
      iptables -A FORWARD -m state –state ESTABLISHED,RELATED -j ACCEPT

      One more line needed.
      iptables -t nat -A POSTROUTING -o eth0 -s $internal_ip -j MASQUERADE

      Sotohiro Terashima

      November 15, 2010 at 5:58 am

  9. Hi, have you ever tried the Ubuntu 10.10 which integrated with eucalyptus 2.0 ? Now my platform installed from 10.04 works perfectly. Thanks for your help! However, when I try the ubuntu 10.10 following the same instructions, it doesn’t work.

    jafelee

    November 10, 2010 at 2:11 pm

    • Yeah I’ve been working on setting up a 10.10 UEC all day today and so far I’m still having errors. There is very little documentation for 10.10 since it only came out last month. Tomorrow I’m going to try 10.04 with the above documentation and see how it turns out.

      NIx

      November 12, 2010 at 4:45 am

      • Hi Nix,

        We are in the process of creating new documentation for UEC on Ubuntu 10.10
        Please stay tuned for updates.

        Kiran

        kiranmurari

        November 24, 2010 at 3:49 pm

    • Hi,

      Good to hear that you got UEC on Ubuntu 10.04 working perfectly following the guide.
      We are in the process of creating new documentation for UEC on Ubuntu 10.10

      Please stay tuned for updates.

      Kiran

      kiranmurari

      November 24, 2010 at 3:48 pm

  10. Hi Kiran,
    I left a message on the wrong page, which I believe (sadly) is answered above. For UEC out of the box one needs 3 machines, one of which with 2 nics, and 2 routers or switches. Do I have that correct? I did not realize a second nic was required. Perhaps the confusing thing is UEC (pre 10.10 and 10.10) comes out of the box with UEC installed as MANAGED_NOVLAN. It is in this mode that the 2 NICS and 2 routers/switches are required…is this correct? For my previous post, and perhaps others as well, if we went into eucalyptus.conf and changed MANAGED_NOVLAN to SYSTEM on cc and nc and restarted the world with -CLEAN would that solve our problems?

    Also, if one needs to, post install, change the range of ip addresses configured during cc install, what file should be updated to avoid having a completely new install? Although, if one changes to SYSTEM from MNV that IP address range is superfluous isn’t it? In system mode there is no ‘known’ ip address as it just picks one up from the router acting as dhcp?

    Thanks,
    Walt

    Walt

    November 28, 2010 at 11:22 pm

  11. hi kiran, i would like to ask…
    i have setup my UEC
    and it goes well when i run everything on my front-end
    so i manage to run instances, ssh to the VM from my front-end
    but when i read your article, we should be acces the VM from a client computer
    i try to follow your step , but it comes some error said like:

    Warning: failed to parse error message from AWS: :1:0: syntax error
    EC2ResponseError: 403 Forbidden
    Failure: 403 Forbidden

    what should i do?

    Indra Suryatama

    December 2, 2010 at 2:03 pm

    • Hi,

      This error occurs if eucalyptus environment variable are not available. Source the eucarc file that you find after uncompressing the mycreds.zip.

      $ source /path/to/eucarc

      Hope that helps.

      Thanks,
      Kiran

      kiranmurari

      December 13, 2010 at 2:31 pm

  12. I’m getting frustrated to access UEC from client side,
    it goes well when everything i did on my front end, but i cant access the VM of UEC from client side
    I’ve download the certificate and extract it on .euca directory
    But when I tried to check
    $euca-describe-availability-zones verbose
    It come some error

    I got the following error
    Warning: failed to parse error message from AWS: :1:0: syntax error
    EC2ResponseError: 403 Forbidden
    Failure: 403 Forbidden

    Is there anyone know how to access UEC from client side (Ubuntu Desktop 10.10 host)?

    Thank you very much

    Indra Suryatama

    December 9, 2010 at 10:01 am

    • You need to set the eucalyptus environment variables. Source the eucarc file.

      $ source /path/to/eucarc

      kiranmurari

      December 13, 2010 at 2:37 pm

  13. Hi,

    I’ve set up server1 and connected eth0 to my public network and eth1 to a private switch with the ip 192.168.20.1. I have server2 connected to this private switch with ip 192.168.20.2. When I use the gateway 192.168.20.1 on server2, the internet doesn’t route through to server2. I can only access server1 from server2. It cannot route out through eth0 of server1 to my public network.

    Any help would be greatly appreciated

    Thanks,
    Ethan

    Ethan

    March 17, 2011 at 8:28 am

  14. Hello sir,

    I am working on cloud computing and faced lots of problems while implementing it…. i have used everything and currently on UEC 10.10 server. Sir, i am having

    1 Desktop
    2 Workstation

    I don’t have any switch and any router but they all are connected in LAN.

    ON CLOUD

    br0: 192.168.1.2
    br1: 192.168.2.2

    ON NC
    br0: 192.168.1.3

    ON Desktop which is acting as a client is
    eth0: 192.168.2.4

    The problem is coming in running the instance because it is going in pending state and nothing i can ping from Node controller. I have done euca-describe-addresses and it is showing me in the range of 192.168.2.0-192.168.2.30…………. even i tried allocate also but it is showing like this

    INSTANCE i-xxxxx emi-xxxxxxx 192.168.2.10 172.19.1.2 pending mykey………..

    Now i can’t ping the the address of 192.168.2.10 so please help me from where i can ping the address and what i can do to make it work…. if any other thing will be required i will be more than happy to produce it in front of you…………

    Rohit

    March 18, 2011 at 3:40 pm

  15. I am a beginner.
    I would like to know what parameters are used while setting up the static IP for eth1.

    your example says:
    address 192.168.20.0
    netmask 255.255.255.0
    network 192.168.20.0
    broadcast 192.168.20.255

    i have used ip address of my computer for address field.(10.10.10.55)
    netmask is the same.(255.255.255.0)
    i also have broadcast value (10.10.10.255)

    but what is to be entered in network field?

    Tushar

    April 27, 2011 at 11:55 am

  16. Hii
    i have added the eth1 static ip address to server1 but when network interface is restarted, it gives error as:
    eth1: ERROR while getting interface flags: No such device
    Failed to bring up eth1

    Nirmal

    May 26, 2011 at 10:59 am

    • Hi,

      Can you please check if the interface eth1 is listed in ‘ifconfig -a’ output?

      Atul

      koolhead17

      May 31, 2011 at 6:17 pm

      • NO
        it is not listed there
        But why does this happen?

        Tushar

        June 9, 2011 at 2:24 pm

  17. Hi kiran,
    Can u please tell me what the function of the client is??
    im a beginner and i couldnt really understand what the client does.
    it seems like all the computing takes place at the client end
    if so what is the NC used for.
    I may be wrong,but please do help.
    Thankyou

    Bibin Rajan

    June 26, 2011 at 8:43 pm

  18. Hi Kiran

    I have config’d everything as described above. However, when I check the local cluster availablity details of the client, the free/max vcpu’s all register as o. when I run;

    sudo euca_conf –discover-nodes

    the cc still doesn’t pickup the nc’s address. Have you any advice on how to fix this.

    Thanks

    501st scout

    August 5, 2011 at 2:37 pm

  19. can’t find the ~/.euca folder. Where is this folder? Should it automatically be created when you install euca2ools?

    Amit Lad

    September 14, 2011 at 2:45 am

  20. Hi is it possible to setup UEC with an unmanaged switch and three PC’s

    Jithin Parakka

    March 2, 2012 at 7:35 am

  21. hi ,i am nitesh b.tech final year student ,i am working in eucalyptus for my major proj,
    i am facing some problem in installation,like when i am installing node controller on a system after installing the cc,clc,sc,and walrus on another system ,it doesn detect Cloud controller ,it says no cloud controller foind but if it is a mistake and there is atually and cloud controller then just enter the ip of the cloud controller ,so i entered the ip ,then it says that clloud controller foind but there is no walrus detected,but when i tried installing walrus saperately on cloud controller system then it says that it is already installed
    please help

    nitesh

    November 16, 2012 at 11:14 am

  22. Hi, I tried to follow the beginners guide for installation but I get the below error at verification step

    cloud@ubuntu:~/.euca$ euca-describe-availability-zones
    Warning: failed to parse error message from AWS: :1:0: syntax error
    EC2ResponseError: 400 Bad Request
    Failure: 400 Bad Request

    Younus

    December 8, 2012 at 1:10 pm

  23. hi everybody,
    i installed uec on my network with two servers and one client. everything was fine when i’m working for the first time. When i shutdown and restart all the three systems and again accessing the server 1’s ip address in browser, it gives me an ‘Internal error(2):’..
    Can anyone help me?
    Thanks in advance

    Dharmaprasath.V

    March 8, 2013 at 2:44 pm

  24. when i got inside after logging with credentials and if i search anything in ‘store’ it throws me an error “Error 6: Couldn’t resolve host ‘imagestore.canonical.com'”

    Dharmaprasath.V

    March 8, 2013 at 2:48 pm


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

Join 171 other followers

%d bloggers like this: