Ask Your Question

karel-striegel's profile - activity

2015-06-30 03:44:44 -0500 received badge  Famous Question (source)
2014-09-22 12:41:05 -0500 received badge  Notable Question (source)
2014-09-07 20:51:13 -0500 received badge  Popular Question (source)
2013-03-07 08:56:12 -0500 answered a question Cinder create volume hangs/stuck (no error msg in logs)

09:25] <dcz> I've noticed something strange yesterday when I was reinstalling cinder. My database connection string was ignored when I added the line at the end of the cinder.conf [09:25] <dcz> below the section :[keystone_authtoken] [09:26] <dcz> could it be that if I place qpid_hostname below the section [keystone_authtoken] in my cinder.conf that it is ignored ? [09:26] <dcz> ow fuck [09:26] <dcz> that was the problem [09:27] <dcz> it is working now :D [09:27] <winston-d> DCZ: :) you were mixing api-paste.ini content into cinder.conf

2013-03-07 07:24:22 -0500 answered a question Cinder create volume hangs/stuck (no error msg in logs)

My config files can be found here : https://bugs.launchpad.net/bugs/1146550

2013-03-07 07:23:40 -0500 answered a question Cinder create volume hangs/stuck (no error msg in logs)

PV VG Fmt Attr PSize PFree /dev/sda5 VolGroup00 lvm2 a-- 687,78g 651,78g /dev/sdb cinder-volumes lvm2 a-- 931,51g 931,51g /dev/sdc cinder-volumes lvm2 a-- 931,51g 931,51g /dev/sdd cinder-volumes lvm2 a-- 698,63g 698,63g /dev/sde cinder-volumes lvm2 a-- 931,51g 931,51g /dev/sdf cinder-volumes lvm2 a-- 931,51g 931,51g

vgs VG #PV #LV #SN Attr VSize VFree VolGroup00 1 5 0 wz--n- 687,78g 651,78g cinder-volumes 5 0 0 wz--n- 4,32t 4,32t

When running the create command no logical volume is created. (I am, manually, able to create a 5G lv in the vg cinder-volumes)

root@OpenStackNode2 /var/log/cinder$ cinder list +--------------------------------------+----------+--------------+------+-------------+-------------+ | ID | Status | Display Name | Size | Volume Type | Attached to | +--------------------------------------+----------+--------------+------+-------------+-------------+ | 43500252-845d-41c8-bf65-ab65650863f6 | creating | test-volume | 5 | None | | +--------------------------------------+----------+--------------+------+-------------+-------------+

Output of the create command with the debug turn on :

root@OpenStackNode2 /var/log/cinder$ cinder --debug create 1 connect: (172.16.41.166, 35357) *** send: 'POST /v2.0/tokens HTTP/1.1\r\nHost: 172.16.41.166:35357\r\nContent-Length: 101\r\ncontent-type: application/json\r\naccept-encoding: gzip, deflate\r\naccept: application/json\r\nuser-agent: python-cinderclient\r\n\r\n' send: '{"auth": {"tenantName": "demo", "passwordCredentials": {"username": "admin", "password": ""}}}' reply: 'HTTP/1.1 200 OK\r\n' header: Vary: X-Auth-Token header: Content-Type: application/json header: Content-Length: 2749 header: Date: Tue, 05 Mar 2013 10:34:44 GMT connect: (172.16.41.168, 8776) ***** send: u'POST /v1/26568729f86f4bb18359fc800ef207c3/volumes HTTP/1.1\r\nHost: 172.16.41.168:8776\r\nContent-Length: 265\r\nx-auth-project-id: demo\r\naccept-encoding: gzip, deflate\r\naccept: application/json\r\nx-auth-token: 46bf3196b5b946879022d147e31d9f5a\r\nuser-agent: python-cinderclient\r\ncontent-type: application/json\r\n\r\n' send: '{"volume": {"status": "creating", "availability_zone": null, "display_description": null, "snapshot_id": null, "user_id": null, "size": 1, "display_name": null, "imageRef": null, "attach_status": "detached", "volume_type": null, "project_id": null, "metadata": {}}}'

Some extra information, my scheduler.log remains untouched. Only when I restart the cinder-scheduler service is sees some activity

fyi : the behavior remains the same when I use the python-novaclient instead of the python-cinderclient : "nova volume-create --display_name vol0 10"

2013-03-07 07:11:14 -0500 answered a question Need help setting up to do cinder development

Hi Joe,

If you are referring to nova-volume then yes Cinder is compatible. You will just have to "migrate" the volumes, which is mainly moving the database info from the nova database to the cinder database.

A bit more info : Compatibility and Migration: There has been a significant amount of concern raised regarding "compatibility"; unfortunately this seems to mean different things to different people. For those that haven't looked at the Cinder code or tried a demo in devstack, here are some question/answers:

Do the same nova client commands I use for volumes today still work the same? YES Do the same euca2ools that I use for volumes today still work the same? YES Does block storage still work the same as it does today in terms of LVM, iSCSI and the drivers that are curently in place? YES Are the associated database tables the same as they are in the current nova volume code? For the most part YES, all volume related tables and columns are migrated, non-volume related tables however are not present Does it use the same nova database as we use today? No, it does require a new independent database Are you going to implement cinder with complete disregard for my current install and completely change everything out from under me? ABSOLUTELY NOT Are you going to test migrating from nova-vol to Cinder? YES Are those migration tests going to be done just using fakes/unit tests? NO, we would require running setups, most likely devstack Are you planning to provide migration scripts/tools to move from nova to cinder? YES

src: https://wiki.openstack.org/wiki/Cinder#Compatibility_and_Migration (https://wiki.openstack.org/wiki/Cinde...) :

guide to install cinder: http://docs.openstack.org/trunk/openstack-compute/install/apt/content/osfolubuntu-cinder.html (http://docs.openstack.org/trunk/opens...) guide to migrate existing volumes to cinder : https://wiki.openstack.org/wiki/MigrateToCinder (https://wiki.openstack.org/wiki/Migra...) or http://docs.openstack.org/trunk/openstack-compute/install/yum/content/n-volume_to_cinder.html (http://docs.openstack.org/trunk/opens...)

Kr Karel.

2013-03-06 09:23:37 -0500 answered a question Cinder create volume hangs/stuck (no error msg in logs)

The version of cinder that I'm using :

Installed Packages Name : openstack-cinder Arch : noarch Version : 2012.2.1 Release : 1.el6 Size : 67 k Repo : installed From repo : epel Summary : OpenStack Volume service

2013-03-06 09:19:12 -0500 answered a question Need help setting up to do cinder development

Can a development config run all on one system?

I believe it can.

fyi in Folsom the default block storage is nova-volume, not cinder. So you will have to make some configuration changes.

2013-03-06 09:16:30 -0500 answered a question Question on having Cinder at a separate node

Hi I have a question regarding your configuration, you mention you have :

paste.filter_factory = keystone.middleware.auth_token:filter_factory service_protocol = http service_host = "Cinder's IP" service_port = 5000

But the service_host doesn't it reflex the keystone service instead of the cinder service ? Keystones default port is 5000 , while cinder is running on a different port.

2013-03-05 10:25:52 -0500 asked a question Cinder create volume hangs/stuck (no error msg in logs)

My problem: When launching on the cinder node the command : cinder create 1 the command "hangs" and keeps hanging without providing a single error msg on the screen or in any log file. When I open another terminal and run cinder list is see the new volume, with state 'creating'. The only way to recover is by existing the command and run a 'cinder delete <id>' after.

My setup : Running latest version of folsom 1 controller node running keystone,nova compute, glance, network 1 compute node running nova compute 1 compute node running nova compute and cinder

Config files of cinder are provided. The cinder logs files have been cleaned before running the command. So they only contain valid entries.