Hi,

Oh! They are same. I just masked the values before pasting the configuration files. Although, now that I think of it, its pretty harmless. Here are the originals.

controller node - http://paste.openstack.org/show/17513/
compute node - http://paste.openstack.org/show/17514/
volume node - http://paste.openstack.org/show/17515/

As per my understanding, I just need to figure out how the volume node is identified. Thank you for replying.

Regards,
Shashank Sahni

On 05/14/2012 09:43 PM, George Mihaiescu wrote:

Is it possible that you have two similar entries in your hosts file?

 

I see that your nova.conf on the the compute node mentions “volume-node” but your successful “"iscsiadm -m discovery -t st -p volume_node” used a different host (volume-node vs. volume_node).
 
Try using IP addresses in the config and while testing iscsi discovery.
 
 

 

 


From: openstack-bounces+george.mihaiescu=q9....@lists.launchpad.net [mailto:openstack-bounces+george.mihaiescu=q9....@lists.launchpad.net] On Behalf Of Shashank Sahni
Sent: Monday, May 14, 2012 10:28 AM
To: raja.me...@wipro.com
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] Problem with attaching disks to an instance

 

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, raja.me...@wipro.com 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: openstack-bounces+raja.meena=wipro....@lists.launchpad.net [mailto:openstack-bounces+raja.meena=wipro....@lists.launchpad.net] On Behalf Of Shashank Sahni
Sent: Monday, May 14, 2012 6:23 PM
To: Razique Mahroua
Cc: openstack@lists.launchpad.net
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



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 : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp

 

--
Nuage & Co - Razique Mahroua
razique.mahr...@gmail.com

 

 

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     : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Reply via email to