Ask Your Question
3

Nova did not use cinder volume

asked 2014-04-17 01:36:22 -0500

senyapsudah gravatar image

i have one issue where i can see that everytime i create an instance, nova will use my OS storage instead of my cinder volume.

image description

as you can see my hypervisor is using 103GB for OS disk and actually has 3.5TB storage. but i'm not sure why it detect my OS disk instead of cinder-volume storage. FYI, currently i'm running cinder-volume inside the same host for nova.

auth_strategy=keystone
dhcpbridge_flagfile=/etc/nova/nova.conf
dhcpbridge=/usr/bin/nova-dhcpbridge
logdir=/var/log/nova
state_path=/var/lib/nova
lock_path=/var/lock/nova
force_dhcp_release=True
libvirt_use_virtio_for_bridges=True
connection_type=libvirt
root_helper=sudo nova-rootwrap /etc/nova/rootwrap.conf
verbose=True
ec2_private_dns_show_ip=True
api_paste_config=/etc/nova/api-paste.ini
volumes_path=/var/lib/nova/volumes
enabled_apis=ec2,osapi_compute,metadata

#Compute configurations
compute_stats_class = nova.compute.stats.Stats
enable_instance_password = True
resume_guests_state_on_host_boot = True

#Volume Configurations
volume_api_class=nova.volume.cinder.API
volume_driver=nova.volume.driver.ISCSIDriver
volume_group=cinder-volumes
volume_name_template=volume-%s
iscsi_helper=tgtadm
libvirt_volume_drivers=iscsi=nova.virt.libvirt.volume.LibvirtISCSIVolumeDriver
cinder_catalog_info=volume:cinder:adminURL

above is part of the config inside my nova.conf. is there anything else missing. btw, any command that i can use to check utilization on my storage? please advise.

edit retag flag offensive close merge delete

Comments

Could you run:- $ cinder list

dbaxps ( 2014-04-17 02:01:13 -0500 )edit

yes, i could run cinder list. but currently nothing listed as i believe i haven't created any volume yet.. but i believe when i create an instance, it will use cinder volume to create the instance disk rite? correct me if i'm wrong.. getting confuse a bit.. :)

senyapsudah ( 2014-04-17 02:16:50 -0500 )edit

Please , source tenants env and run nova list

dbaxps ( 2014-04-17 02:45:54 -0500 )edit

So means that, it will not use cinder volume to create image rite. the usage will only be when we manually attached the volume to it or we create a bootable volume and boot from it. am i right?

senyapsudah ( 2014-04-17 03:54:02 -0500 )edit

In meantime on Havana command like :-
$ nova boot --flavor 2 --key_name oskey25 --block-device source=image,id=d0e90250-5814-4685-9b8d-65ec9daa7117,dest=volume,size=5,shutdown=preserve,bootindex=0 VF20RS012
which creates cinder volume via glance image at boot fails ( Target milestone for fix IceHouse RC1).
Quote :-
we create a bootable volume and boot from it. am i right?
This statement is correct.

dbaxps ( 2014-04-17 04:28:17 -0500 )edit

2 answers

Sort by ยป oldest newest most voted
0

answered 2014-04-23 04:33:23 -0500

danifr gravatar image

I had this problem too but I was able to solve it.

OpenStack's configuration only sees what it is under your / (root) partition. If you execute df -H, I bet you will see that your / is ~103Gb.

So the answer is easy, in order to have more disk available for your instances you should resize your / partition.

Here you can find a nice document explaining how to do it: http://information-technology.web.cern.ch/book/cern-cloud-infrastructure-user-guide/administering-vms/resizing-disks (http://information-technology.web.cer...)

Hope this helps.

edit flag offensive delete link more

Comments

Quote


So the answer is easy, in order to have more disk available for your instances you should resize your / partition.


On my Controller - df -h has entries
/dev/mapper/fedora00-data1 77G 11G 63G 14% /data1
192.168.1.127:/cinder-volumes05 77G 11G 63G 14% /var/lib/cinder/volumes/acdeb4a4d53d1bdae1a2eddc405ba43d

    All cinder bootable volumes supporting VMs  are located on /data1 ( xfs formated fs) and <br>
    $ gluster volume info cinder-volumes05
    Volume Name: cinder-volumes05
    Type: Replicate
    Volume ID: 029b210d-1fd6-4276-b6d1-86b75078113b
    Status: Started
    Number of Bricks: 1 x 2 = 2
    Transport-type: tcp
    Bricks:
    Brick1: dfw02.localdomain:/data1/cinder5
    Brick2: dfw01.localdomain:/data1/cinder5
    Options Reconfigured:
    auth.allow: 192.168.1.*
    storage.owner-uid: 165
    storage.owner-gid: 165
Having gluster backend for cinder, only size of /data1 XFS partition limits space allocated for bootable cinder volumes attached to VMs.
My "/" partition has no any connection to allocating space for newly launched VMs based on bootable cinder ...
(more)
dbaxps ( 2014-04-23 12:25:59 -0500 )edit

Having gluster backend for cinder, only size of /data1 XFS partition limits space allocated for bootable cinder volumes attached to VMs.
My "/" partition has no any connection to allocating space for newly launched VMs based on bootable cinder volumes, been created via corresponding glance images.

dbaxps ( 2014-04-23 12:37:07 -0500 )edit

Hi dbaxps, I think your problem is different than the one senyapsudah described. My answer only applies to that problem. Cheers.

danifr ( 2014-04-24 07:42:04 -0500 )edit

hi guys, after test for a few times, i found out that we can force the instance to automatically use cinder-volumes at boot time.. what you need to add under nova.conf is.

[libvirt]
images_type = lvm
images_volume_group =cinder-volumes

but when you try to delete the instance it super slow.

senyapsudah ( 2014-04-25 07:19:11 -0500 )edit
0

answered 2014-04-17 02:34:11 -0500

dbaxps gravatar image

updated 2014-04-18 09:55:53 -0500

smaffulli gravatar image

nova boot via image with volume creation doesn't work on Havana. It's known bug. Downhere, first volume is created, then instance gets loaded via volume

$ cinder create --image-id ad91d437-53a8-4486-a825-3443086a4a46 --display_name UbuntuTVL0417 5 
$ cinder list 
| 3c858fac-c085-4de2-a6c3-e715abf8739f | availabe | UbuntuTVL0417 |  5   |  glusterfs  |  true    |         | 
$ nova boot --flavor 2 --key_name oskey25 --block_device_mapping vda=3c858fac-c085-4de2-a6c3-e715abf8739f:::0 UbuntuTRS0417

In meantime on Havana command like :

 $ nova boot --flavor 2 --key_name oskey25 --block-device source=image,id=d0e90250-5814-4685-9b8d65ec9daa7117,dest=volume,size=5,shutdown=preserve,bootindex=0 VF20RS012

which creates cinder volume via glance image at boot fails ( Target milestone for fix IceHouse RC1).

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

[hide preview]

Get to know Ask OpenStack

Resources for moderators

Question Tools

Follow
3 followers

Stats

Asked: 2014-04-17 01:36:22 -0500

Seen: 512 times

Last updated: Apr 23 '14