Ask Your Question
0

Launching instance and volume

asked 2013-04-29 22:00:22 -0500

neumerance gravatar image

I have installed Openstack using Devstack i a VMware running in Ubuntu 12.04 that has 3gb RAM 100GB HDD and 4cores.

I can only launch an instance with a Flavor of tiny and when i try the other flavors it gives me an error status.

It also the same with my volumes. I am not able to create a volume that more than 2GB.

Do you have an idea where am i doing wrong here?

Any help would be much appreciated, thanks

edit retag flag offensive close merge delete

Comments

You're not by chance running on a 32 bit machine are you? I would go for dtroyer's answer however it doesn't explain the issue you're having with instance creation, 32 bit however may very well explain both.

jgriffith gravatar imagejgriffith ( 2013-05-01 17:34:04 -0500 )edit

4 answers

Sort by ยป oldest newest most voted
1

answered 2013-04-30 17:58:20 -0500

smaffulli gravatar image

It is possible that your environment doesn't have enough free resources to create bigger instances. Check this question as this may be a duplicate:

https://ask.openstack.org/question/526/why-can-i-create-no-instance-bigger-than-tiny/

edit flag offensive delete link more
0

answered 2013-05-01 14:08:58 -0500

dtroyer gravatar image

About the volumes, originally the limit on the size of volumes in DevStack was 2Gb due to the default size of the backing file created to hold the logical volumes. The default changed to 5Gb a while ago.

You can set the size of the LV backing file in locarc with VOLUMEBACKINGFILE_SIZE. To get a 10Gb max size add this to localrc:

VOLUME_BACKING_FILE_SIZE=10260M

You can verify the file size by looking at /opt/stack/data/stack-volumes-backing-file. Also the usual LVM command suspects will be helpful here (pvs, vgs, lvs, etc).

Note that if you already have a backing file, rerunning stack.sh with a new VOLUME_BACKING_FILE_SIZE WILL NOT change the existing file. You must remove it for the new size to take effect.

You can also just create a volume group named 'stack-volumes' yourself and DevStack will find it and use it instead of the backing file.

edit flag offensive delete link more
0

answered 2013-04-30 03:24:51 -0500

Please check quotas for tenant:

nova quota-show

If you are using mysql database, you can also check there:

use nova;
# To show usage
select * from quota_usages;
# To show quotas
select * from quotas;
edit flag offensive delete link more
0

answered 2013-05-24 20:54:00 -0500

fred gravatar image

I want to append a question: when I shutdown a instance ,its resource(RAM,vcpu) is also in nova resource pool rather than to use for other new instance creating . So how can I recover these resource to use again for others?

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

Stats

Asked: 2013-04-29 22:00:22 -0500

Seen: 1,519 times

Last updated: May 24 '13