you have to set iscsi_ip_address on the volume node. The volume node is the one that creates this db entry.
Vish On May 14, 2012, at 1:54 PM, Shashank Sahni wrote: > 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 > > On 05/15/2012 02:15 AM, Vishvananda Ishaya wrote: >> >> 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 >> >> On May 14, 2012, at 7:28 AM, Shashank Sahni wrote: >> >>> 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] wrote: >>>> >>>> Hi Shashank , >>>> >>>> I preassume that the steps outlined in the link below has been followed. >>>> >>>> http://docs.openstack.org/trunk/openstack-compute/admin/content/managing-volumes.html >>>> >>>> >>>> Thanks >>>> Meena Raja >>>> >>>> >>>> >>>> >>>> From: [email protected] >>>> [mailto:[email protected]] On >>>> Behalf Of Shashank Sahni >>>> Sent: Monday, May 14, 2012 6:23 PM >>>> To: Razique Mahroua >>>> Cc: [email protected] >>>> Subject: Re: [Openstack] Problem with attaching disks to an instance >>>> >>>> Hi, >>>> >>>> I set this option in the configuration files of both compute and >>>> controller. Restarted the service, but unfortunately same result. >>>> >>>> Regards, >>>> Shashank Sahni >>>> >>>> On 05/14/2012 05:58 PM, Razique Mahroua wrote: >>>> Hi, >>>> do you have the flag iscsi_ip_prefix configured in your nova.conf ? >>>> Razique >>>> >>>> >>>> <postbox-contact.jpg> >>>> Shashank Sahni >>>> 14 mai 2012 14:22 >>>> Hi everyone, >>>> >>>> I'm trying to configure a multi-node installation. Here is a brief >>>> overview. >>>> >>>> 1) controller - api+network+scheduler+novnc+glance+keystone (nova.conf - >>>> http://paste.openstack.org/show/17470/) >>>> 2) compute node (nova.conf - http://paste.openstack.org/show/17469) >>>> 3) volume node(single) >>>> >>>> Compute and vnc are working fine. I'm able to create and delete volumes. >>>> Iscsi discovery from the compute nodes is working too. But when I try to >>>> attach a volume, the compute node tries to connect to the controller node >>>> instead of volume and hence crashes with the following error. >>>> >>>> 2012-05-14 17:32:13 TRACE nova.rpc.amqp ProcessExecutionError: Unexpected >>>> error while running command. >>>> 2012-05-14 17:32:13 TRACE nova.rpc.amqp Command: sudo nova-rootwrap >>>> iscsiadm -m node -T iqn.2010-10.org.openstack:volume-00000003 -p >>>> controller:3260 --rescan >>>> 2012-05-14 17:32:13 TRACE nova.rpc.amqp Exit code: 255 >>>> 2012-05-14 17:32:13 TRACE nova.rpc.amqp Stdout: '' >>>> 2012-05-14 17:32:13 TRACE nova.rpc.amqp Stderr: 'iscsiadm: No portal >>>> found.\n' >>>> >>>> Any suggestions? >>>> >>>> Kind Regards, >>>> Shashank Sahni >>>> _______________________________________________ >>>> Mailing list: https://launchpad.net/~openstack >>>> Post to : [email protected] >>>> Unsubscribe : https://launchpad.net/~openstack >>>> More help : https://help.launchpad.net/ListHelp >>>> >>>> -- >>>> Nuage & Co - Razique Mahroua >>>> [email protected] >>>> >>>> <image.jpg> >>>> >>>> >>>> >>>> Please do not print this email unless it is absolutely necessary. >>>> >>>> The information contained in this electronic message and any attachments >>>> to this message are intended for the exclusive use of the addressee(s) and >>>> may contain proprietary, confidential or privileged information. If you >>>> are not the intended recipient, you should not disseminate, distribute or >>>> copy this e-mail. Please notify the sender immediately and destroy all >>>> copies of this message and any attachments. >>>> >>>> WARNING: Computer viruses can be transmitted via email. The recipient >>>> should check this email and any attachments for the presence of viruses. >>>> The company accepts no liability for any damage caused by any virus >>>> transmitted by this email. >>>> >>>> www.wipro.com >>>> >>> >>> _______________________________________________ >>> Mailing list: https://launchpad.net/~openstack >>> Post to : [email protected] >>> Unsubscribe : https://launchpad.net/~openstack >>> More help : https://help.launchpad.net/ListHelp >> >
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
