Thank you Vish. That did the trick :)
Regards,
Shashank Sahni
you have to set
iscsi_ip_address on the volume node. The volume node is the one that
creates this db entry.
Vish
Hi Vish,
Yeah you are right. I checked the settings in the volume database
and for all volumes the entry is similar to following.
controller_node:3260,3 iqn.2010-10.org.openstack:volume-00000004
But it seems these entries are being generated automatically, i.e.
as soon as I issue volume creation command. How do I fix this? I am
already using properly configured iscsi_ip_address option in the
controller's nova.conf file.
Regards,
Shashank Sahni
It should be getting the
connection properties via the call to the volume node. Is it possible
your volume in the database has incorrect properties stored in
provider_location?
It is set from the cofig
iscsi_ip_address, so if you have not set that configuration option to a
routable ip from compute -> volume then it will not work. Also,
changing the config option will not change the existing values in the
db, so you might have to change those manually.
Vish
Hi,
Thanks for the reply.
Yes, I've gone through the document. Volume creation and deletion
are working perfectly fine. When I run "iscsiadm -m discovery -t st
-p volume_node" on the compute node, I can see the volumes. But
somehow the compute node is being misinformed about the volume node
after giving the attach command.
I'm not using iscsitarget as per that document. Installation of
nova-volume on ubuntu precise automatically took care of it using
tgt.
Kind Regards,
Shashank Sahni
On 05/14/2012 07:34 PM,
[email protected]
