Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Nova-Volume can create volume on Essex

Hi there!

I've a little question today. I've setup an OpenStack using Three servers (Dell M610):

One of them is for Cloud Control purpose (Keystone+MySQL+Glance).

The second one is for Cloud Compute purpose (Nova-all except for nova-volume).

And finally, the third one is for Cloud Volume purpose.

Everything is running fine on API/RPC communication layer, however, I'm facing a really strange behavior when I'm trying to create volume.

Indeed, when I'm on the dashboard, or on the CLI and that I start to create a volume, everything is fine BUT my volume still remain in the Creating State for ever.

I've double check my nova.conf and api.conf, everything is fine, all communication are running and my frontend is correctly sending request to my backend nodes.

If I launch a volume-create on the frontend, I correctly see the volume-list on the distant volume node.

I've check date and time parameters and the offset is not exceeding 2ms.

Here is my nova.conf and api-paste.ini files on the Compute Node:

Nova.Conf-Compute & Api-paste.Ini-Compute

Here is my nova.conf file on the Volume Node:

Nova.Conf-Volume& Api-paste.Ini-Volume

As you can see it, I'm using tgtadm as the iSCSI tool and I've check that tgtd service is started.

I also have installed open-iscsi (initiator) and iscsitarget+iscsitarget-dkms (target and module) packages.

all of them have not been edited except for the /etc/default/iscsitarget file that have been set to: TRUE to properly launch the service.

All services are up and running, and all my Openstack stuff are in DEBUG VERBOSE mode but none of them are reporting any kind of error.

There is no trace of any logical volume created on the nova-volumes VG Volume.

I'm suspecting a iscsi issue, but I can't get it so far, then, if you've got some hint/clue/other it'll be really appreciate ;-)

Nova-Volume can create volume on Essex

Hi there!

I've a little question today. I've setup an OpenStack using Three servers (Dell M610):

One of them is for Cloud Control purpose (Keystone+MySQL+Glance).

The second one is for Cloud Compute purpose (Nova-all except for nova-volume).

And finally, the third one is for Cloud Volume purpose.

Everything is running fine on API/RPC communication layer, however, I'm facing a really strange behavior when I'm trying to create volume.

Indeed, when I'm on the dashboard, or on the CLI and that I start to create a volume, everything is fine BUT my volume still remain in the Creating State for ever.

I've double check my nova.conf and api.conf, everything is fine, all communication are running and my frontend is correctly sending request to my backend nodes.

If I launch a volume-create on the frontend, I correctly see the volume-list on the distant volume node.

I've check date and time parameters and the offset is not exceeding 2ms.

Here is my nova.conf and api-paste.ini files on the Compute Node:

Nova.Conf-Compute & Api-paste.Ini-Compute

Here is my nova.conf file on the Volume Node:

Nova.Conf-Volume& Api-paste.Ini-Volume

As you can see it, I'm using tgtadm as the iSCSI tool and I've check that tgtd service is started.

I also have installed open-iscsi (initiator) and iscsitarget+iscsitarget-dkms (target and module) packages.

all of them have not been edited except for the /etc/default/iscsitarget file that have been set to: TRUE to properly launch the service.

All services are up and running, and all my Openstack stuff are in DEBUG VERBOSE mode but none of them are reporting any kind of error.

There is no trace of any logical volume created on the nova-volumes VG Volume.

I'm suspecting a iscsi issue, but I can't get it so far, then, if you've got some hint/clue/other it'll be really appreciate ;-)

PS: Sorry for the links, I don't seems to have suffisent karma right now :-/.