CSS Corp Open Source Services

Eucalyptus: Not enough resources: vm instances

with one comment

Issue:

FinishedVerify: Not enough resources: vm instances.

Reasoning:

This issue arises if the node controller is not registered with the cluster controller or if there are no free VMs available to launch the instance.

Solution:

In case, the node controller is not registered, the output of “euca-describe-availability-zones verbose” will show zero free and max VMs as below.

$ euca-describe-availability-zones verbose
 AVAILABILITYZONE        mycloud       A.B.C.D
 AVAILABILITYZONE        |- vm types     free / max   cpu   ram  disk
 AVAILABILITYZONE        |- m1.small     0000 / 0000   1    128     2
 AVAILABILITYZONE        |- c1.medium    0000 / 0000   1    256     5
 AVAILABILITYZONE        |- m1.large     0000 / 0000   2    512    10
 AVAILABILITYZONE        |- m1.xlarge    0000 / 0000   2   1024    20
 AVAILABILITYZONE        |- c1.xlarge    0000 / 0000   4   2048    20

Register the node controller with the following command and add the discovered nodes.

$ sudo euca_conf --no-rsync --discover-nodes

Once the node is successfully registered “euca-describe-availability-zones verbose” shows the following output

$ euca-describe-availability-zones verbose
 AVAILABILITYZONE        oss-cloud       A.B.C.D
 AVAILABILITYZONE        |- vm types     free / max   cpu   ram  disk
 AVAILABILITYZONE        |- m1.small     0002 / 0002 1    128     2
 AVAILABILITYZONE        |- c1.medium    0002 / 0002 1    256     5
 AVAILABILITYZONE        |- m1.large     0001 / 0001 2    512    10
 AVAILABILITYZONE        |- m1.xlarge    0001 / 0001 2   1024    20
 AVAILABILITYZONE        |- c1.xlarge    0000 / 0000 4   2048    20

Now an instance can be successfully started (provided other network related configuration has been taken care).

But after starting a couple of instances, again if the same error is encountered, then its time to look at the MAX_CORES macro in /etc/eucalyptus.conf

For example:

Before starting any instances,

$ euca-describe-availability-zones verbose
 AVAILABILITYZONE        oss-cloud       A.B.C.D
 AVAILABILITYZONE        |- vm types     free / max   cpu   ram  disk
 AVAILABILITYZONE        |- m1.small     0002 / 0002 1    128     2
 AVAILABILITYZONE        |- c1.medium    0002 / 0002 1    256     5
 AVAILABILITYZONE        |- m1.large     0001 / 0001 2    512    10
 AVAILABILITYZONE        |- m1.xlarge    0001 / 0001 2   1024    20
 AVAILABILITYZONE        |- c1.xlarge    0000 / 0000 4   2048    20

After running two instances of type c1.medium,

$ euca-describe-availability-zones verbose
 AVAILABILITYZONE        oss-cloud       A.B.C.D
 AVAILABILITYZONE        |- vm types     free / max   cpu   ram  disk
 AVAILABILITYZONE        |- m1.small     0000 / 0002 1    128     2
 AVAILABILITYZONE        |- c1.medium    0000 / 0002 1    256     5
 AVAILABILITYZONE        |- m1.large     0000 / 0001 2    512    10
 AVAILABILITYZONE        |- m1.xlarge    0000 / 0001 2   1024    20
 AVAILABILITYZONE        |- c1.xlarge    0000 / 0000 4   2048    20

This deprives from launching further instances of any image.

MORE CORES….. MORE VMS……

In /etc/eucalyptus.conf, there sits this MAX_CORES macro which defaults to available CPU cores.

Before changing MAX_CORES and not running any instances:

$ euca-describe-availability-zones verbose
 AVAILABILITYZONE        oss-cloud       A.B.C.D
 AVAILABILITYZONE        |- vm types     free / max   cpu   ram  disk
 AVAILABILITYZONE        |- m1.small     0002 / 0002 1    128     2
 AVAILABILITYZONE        |- c1.medium    0002 / 0002 1    256     5
 AVAILABILITYZONE        |- m1.large     0001 / 0001 2    512    10
 AVAILABILITYZONE        |- m1.xlarge    0001 / 0001 2   1024    20
 AVAILABILITYZONE        |- c1.xlarge    0000 / 0000 4   2048    20

After changing MAX_CORES to 8 and not running any instances:

$ euca-describe-availability-zones verbose
 AVAILABILITYZONE        oss-cloud       A.B.C.D
 AVAILABILITYZONE        |- vm types     free / max   cpu   ram  disk
 AVAILABILITYZONE        |- m1.small     0008 / 0008 1    128     2
 AVAILABILITYZONE        |- c1.medium    0008 / 0008 1    256     5
 AVAILABILITYZONE        |- m1.large     0004 / 0004 2    512    10
 AVAILABILITYZONE        |- m1.xlarge    0003 / 0003 2   1024    20
 AVAILABILITYZONE        |- c1.xlarge    0001 / 0001 4   2048    20

Earlier, an instance of type c1.xlarge was not possible, but now one instance of c1.xlarge is possible.

So MORE CORES….. MORE VMs…..

Advertisements

Written by kiranmurari

March 22, 2010 at 11:36 am

One Response

Subscribe to comments with RSS.

  1. hii i tried to register node controller using command
    sudo euca_conf –no-rsync –discover-nodes…but it shows error related to –discover-node
    ibut i registered node controller with /usr/sbin/euca_conf –register-nodes Node1_IP; & it works..but again i typed euca-describe-availability-zones verbose still it is showing same result i.e 0000/0000…plz help me it’s urgent..u cam mail me at sankalp.sawant59@gmail.com

    sankalp sawant

    April 7, 2013 at 12:18 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

%d bloggers like this: