Nova on Compute Node cannot connect to Cinder #93

Closed
davidsackett opened this Issue Mar 21, 2013 · 6 comments

Projects

None yet

3 participants

@davidsackett

Hi,

Thanks for the great guide! After following https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst I couldn't attach Cinder volumes to instances. I tracked it down to Nova on the Compute Node using the publicURL (192.168.100.51) for Cinder by default. The Compute Node can't access that IP. My solution was to add cinder_catalog_info=volume:cinder:internalURL to /etc/nova/nova.conf on the Compute Node. This makes Nova use the internalURL (100.10.10.51).

Is this the correct solution? Or have I made some other error?

@mseknibilel
Owner

Yes that's correct. The advantage is that you secure VM's access to the
volumes since it is on the private network but it is gona overcharge the
management network in case there is some heavy traffic between VMs and
their volumes !

regards,
Bilel

2013/3/22 David Sackett notifications@github.com

Hi,

Thanks for the great guide! After following
https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rstI couldn't attach Cinder volumes to instances. I tracked it down to Nova on
the Compute Node using the publicURL (192.168.100.51) for Cinder by
default. The Compute Node can't access that IP. My solution was to add
cinder_catalog_info=volume:cinder:internalURL to /etc/nova/nova.conf on
the Compute Node. This makes Nova use the internalURL (100.10.10.51).

Is this the correct solution? Or have I made some other error?


Reply to this email directly or view it on GitHubhttps://github.com/mseknibilel/OpenStack-Folsom-Install-guide/issues/93
.

Best regards,

Bilel Msekni | Research & Development Engineer
Institut Mines-Telecom | TELECOM & Management SudParis
9 rue Charles Fourier, 91011 EVRY Cedex, France
Mobile: +33 6 49 52 42 17

@davidsackett

Thanks for the response! So in regard to this guide, should it be updated to include this configuration? I assume this is the only way to achieve a working Openstack deployment given that the Compute nodes have no connectivity to the 192.168 network.

Cheers,
David

@f905201
f905201 commented Apr 2, 2013

Hello,

I got same problem, but after modifying nova.conf in compute node, I still can't attach volume to vm. The status remains 'Attaching'. And it seems no error in log. Do you have any idea to fix it?

Thanks

@mseknibilel
Owner

Hello,

When you connect to any compute node, try this commande: vgdisplay, if you
can't see the cinder-volumes, it means that you can't attach the volume !
Try mounting the cinder volume group on the compute nodes, that should fix
the problem.

regards,
Bilel

2013/4/2 f905201 notifications@github.com

Hello,

I got same problem, but after modifying nova.conf in compute node, I still
can't attach volume to vm. The status remains 'Attaching'. And it seems no
error in log. Do you have any idea to fix it?

Thanks


Reply to this email directly or view it on GitHubhttps://github.com/mseknibilel/OpenStack-Folsom-Install-guide/issues/93#issuecomment-15776096
.

Best regards,

Bilel Msekni | Research & Development Engineer
Institut Mines-Telecom | TELECOM & Management SudParis
9 rue Charles Fourier, 91011 EVRY Cedex, France
Mobile: +33 6 49 52 42 17

@f905201
f905201 commented Apr 3, 2013

Hello,

I have tried to create /dev/loop2 and created volume group "cinder-volumes"on compute node. At first, it solved the problem. I could attach volume to vm. But after rebooting both node, it stuck to attaching again, volume group now are set well on controller node and compute node. It seems everything is ok except attaching volume to VMs. Any suggestion?

Thanks.

@mseknibilel
Owner

Hi,

I guess this is an OpenStack Bug ! might better to report it :)

regards,
Bilel

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment