Re: [Openstack] Problem with attaching disks to an instance

2012-05-15 Thread Vishvananda Ishaya 
Yes that code is unused and the removal is under review here:

https://review.openstack.org/#/c/7450/

Vish

On May 15, 2012, at 8:18 PM, Lorin Hochstein wrote:

> On May 15, 2012, at 1:27 PM, Vishvananda Ishaya wrote:
> 
>> FYI iscsi_ip_prefix doesn't exist in essex.  
> 
> That flag is referenced in the XenAPI code in essex: 
> https://github.com/openstack/nova/blob/stable/essex/nova/virt/xenapi/volume_utils.py#L408
> 
> However, it doesn't appear anywhere else in essex. Is this a bug?
> 
> Take care,
> 
> Lorin
> --
> Lorin Hochstein
> Lead Architect - Cloud Services
> Nimbis Services, Inc.
> www.nimbisservices.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

Re: [Openstack] Problem with attaching disks to an instance

2012-05-15 Thread Lorin Hochstein 
On May 15, 2012, at 1:27 PM, Vishvananda Ishaya wrote:

> FYI iscsi_ip_prefix doesn't exist in essex.  

That flag is referenced in the XenAPI code in essex: 
https://github.com/openstack/nova/blob/stable/essex/nova/virt/xenapi/volume_utils.py#L408

However, it doesn't appear anywhere else in essex. Is this a bug?

Take care,

Lorin
--
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.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

Re: [Openstack] Problem with attaching disks to an instance

2012-05-15 Thread Shashank Sahni 
Thanks for the info. This way is indeed more convenient.

-- Shashank Sahni

On Tue, May 15, 2012 at 10:57 PM, Vishvananda Ishaya
wrote:

> FYI iscsi_ip_prefix doesn't exist in essex.  The ip is passed back to the
> compute node based on what it has stored in the database, so the compute
> node no longer finds it through discovery and matching to the prefix.  You
> should only need iscsi_ip_address on the volume node to make sure that the
> db entry is created properly.
>
> Vish
>
> On May 15, 2012, at 12:25 AM, Razique Mahroua wrote:
>
> In fact, it looks like the service is not able to retrieve the
> nova-volume' IP; as if there were some issue parsing the flag or something
> like that.
> Could you try by commenting that entry on all your servers :
>
> --iscsi_ip_address
>
>  and only keep the prefix ?
> Razique
>
>
>  Shashank Sahni 
>  14 mai 2012 18:22
> 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
>
>
> ___
> 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
>
>  
>
>
>  ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>
<>___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Problem with attaching disks to an instance

2012-05-15 Thread Vishvananda Ishaya 
FYI iscsi_ip_prefix doesn't exist in essex.  The ip is passed back to the compute node based on what it has stored in the database, so the compute node no longer finds it through discovery and matching to the prefix.  You should only need iscsi_ip_address on the volume node to make sure that the db entry is created properly.VishOn May 15, 2012, at 12:25 AM, Razique Mahroua wrote:

In fact, it looks like the service is not able to retrieve the 
nova-volume' IP; as if there were some issue parsing the flag or 
something like that.Could you try by commenting that entry on all 
your servers : --iscsi_ip_address and
 only keep the prefix ?Razique 	   
   	Shashank Sahni  
  14 mai 2012 18:22
  

  
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


  ___Mailing list: 
https://launchpad.net/~openstackPost to : 
openstack@lists.launchpad.netUnsubscribe : 
https://launchpad.net/~openstackMore help   : 
https://help.launchpad.net/ListHelp-- Nuage & Co - Razique Mahroua 
razique.mahr...@gmail.com








 






___Mailing list: https://launchpad.net/~openstackPost to : openstack@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstackMore help   : https://help.launchpad.net/ListHelp___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Problem with attaching disks to an instance

2012-05-15 Thread Razique Mahroua 
Oh sorry, haven't read Vish answer, my bad :-) 	   
   	Shashank Sahni  
  14 mai 2012 23:30
  

  
Thank you Vish. That did the trick :)

Regards,
Shashank Sahni


  ___Mailing list: 
https://launchpad.net/~openstackPost to : 
openstack@lists.launchpad.netUnsubscribe : 
https://launchpad.net/~openstackMore help   : 
https://help.launchpad.net/ListHelp 	   
   	Vishvananda Ishaya  
  14 mai 2012 23:13you have to set 
iscsi_ip_address on the volume node.  The volume node is the one that 
creates this db entry.Vish___Mailing
 list: https://launchpad.net/~openstackPost to : 
openstack@lists.launchpad.netUnsubscribe : 
https://launchpad.net/~openstackMore help   : 
https://help.launchpad.net/ListHelp 	   
   	Shashank Sahni  
  14 mai 2012 22:54
  

  
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-0004 

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


  ___Mailing list: 
https://launchpad.net/~openstackPost to : 
openstack@lists.launchpad.netUnsubscribe : 
https://launchpad.net/~openstackMore help   : 
https://help.launchpad.net/ListHelp 	   
   	Vishvananda Ishaya  
  14 mai 2012 22:45It 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___Mailing
 list: https://launchpad.net/~openstackPost to : 
openstack@lists.launchpad.netUnsubscribe : 
https://launchpad.net/~openstackMore help   : 
https://help.launchpad.net/ListHelp 	   
   	Shashank Sahni  
  14 mai 2012 16:28
  

  
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

  -- Nuage & Co - Razique Mahroua 
razique.mahr...@gmail.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

Re: [Openstack] Problem with attaching disks to an instance

2012-05-15 Thread Razique Mahroua 
In fact, it looks like the service is not able to retrieve the 
nova-volume' IP; as if there were some issue parsing the flag or 
something like that.Could you try by commenting that entry on all 
your servers : --iscsi_ip_address and
 only keep the prefix ?Razique 	   
   	Shashank Sahni  
  14 mai 2012 18:22
  

  
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


  ___Mailing list: 
https://launchpad.net/~openstackPost to : 
openstack@lists.launchpad.netUnsubscribe : 
https://launchpad.net/~openstackMore help   : 
https://help.launchpad.net/ListHelp-- Nuage & Co - Razique Mahroua 
razique.mahr...@gmail.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

Re: [Openstack] Problem with attaching disks to an instance

2012-05-14 Thread Shashank Sahni 

Thank you Vish. That did the trick :)

Regards,
Shashank Sahni

On 05/15/2012 02:43 AM, Vishvananda Ishaya wrote:
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-0004

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, 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




*Shashank Sahni* <mailto:shredde...@linuxers.org>

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-0003 -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 
<https://launchpad.net/%7Eopenstack>
Post to : openstack@lists.launchpad.net 
<mailto:openstack@lists.launchpad.net>
Unsubscribe : https://launchpad.net/~openstack 
<https://launchpad.net/%7Eopenstack>

More help : https://help.launchpad.net/ListHelp

--
Nuage & Co - Razique Mahroua
*razique.mahr...@gmail.com <mailto: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 attac

Re: [Openstack] Problem with attaching disks to an instance

2012-05-14 Thread Vishvananda Ishaya 
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-0004 
> 
> 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, 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
>>>> 
>>>> 
>>>> 
>>>> 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-0003 -p 
>>>> controller:3260 --rescan
>>>> 2012-05-14 17:32:13 TRACE nova.rpc.amqp Exit code: 255

Re: [Openstack] Problem with attaching disks to an instance

2012-05-14 Thread Shashank Sahni 

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-0004

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, 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




*Shashank Sahni* <mailto:shredde...@linuxers.org>

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-0003 -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 
<https://launchpad.net/%7Eopenstack>
Post to : openstack@lists.launchpad.net 
<mailto:openstack@lists.launchpad.net>
Unsubscribe : https://launchpad.net/~openstack 
<https://launchpad.net/%7Eopenstack>

More help : https://help.launchpad.net/ListHelp

--
Nuage & Co - Razique Mahroua
*razique.mahr...@gmail.com <mailto: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 
<https://launchpad.net/%7Eopenstack&g

Re: [Openstack] Problem with attaching disks to an instance

2012-05-14 Thread Vishvananda Ishaya 
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, 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
>> 
>> 
>> 
>> 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-0003 -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

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Problem with attaching disks to an instance

2012-05-14 Thread Shashank Sahni 

  
  
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



  
  
  

  

  
  
  
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 th

Re: [Openstack] Problem with attaching disks to an instance

2012-05-14 Thread Shashank Sahni 

  
  
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
  
  
  
  

  

  
  
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-0003 -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

Re: [Openstack] Problem with attaching disks to an instance

2012-05-14 Thread Shashank Sahni 

  
  
Hi,

Thanks for your suggestion. I had earlier configured them to be the
controller node. I tried setting them to the volume node but no
result. I get the following error on running "nova volume-list"

ERROR: n/a (HTTP 400)

As I previously mentioned, volume creation and deletion is working
fine, its the volume node assignment that's flawed.

Regards,
Shashank Sahni

On 05/14/2012 07:00 PM, Yong Sheng Gong wrote:
Hi,
consider to change 
catalog.RegionOne.volume.publicURL = http://volumenode:8776/v1/$(tenant_id)s
catalog.RegionOne.volume.adminURL = http://volumenode:8776/v1/$(tenant_id)s
catalog.RegionOne.volume.internalURL = http://v:8776/v1/$(tenant_id)s
catalog.RegionOne.volume.name = Volume Service
  
It seems your openstack is looking for the volume on
wrong volume server.

-openstack-bounces+gongysh=cn.ibm@lists.launchpad.net
  wrote: -

  To: Razique Mahroua 
From: Shashank Sahni 
  Sent by: openstack-bounces+gongysh=cn.ibm@lists.launchpad.net
  Date: 05/14/2012 09:20PM
  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
  
  

  


  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-0003 -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

 
  

  

  
  
  ___

Re: [Openstack] Problem with attaching disks to an instance

2012-05-14 Thread raja.meena 
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


[cid:image001.jpg@01CD3208.A546CC20]
Shashank Sahni<mailto:shredde...@linuxers.org>
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-0003 -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<https://launchpad.net/%7Eopenstack>
Post to : openstack@lists.launchpad.net<mailto:openstack@lists.launchpad.net>
Unsubscribe : 
https://launchpad.net/~openstack<https://launchpad.net/%7Eopenstack>
More help : https://help.launchpad.net/ListHelp

--
Nuage & Co - Razique Mahroua
razique.mahr...@gmail.com<mailto:razique.mahr...@gmail.com>
[cid:image002.jpg@01CD3208.A546CC20]



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

Re: [Openstack] Problem with attaching disks to an instance

2012-05-14 Thread Yong Sheng Gong 
Hi,consider to change catalog.RegionOne.volume.publicURL = http://volumenode:8776/v1/$(tenant_id)scatalog.RegionOne.volume.adminURL = http://volumenode:8776/v1/$(tenant_id)scatalog.RegionOne.volume.internalURL = http://v:8776/v1/$(tenant_id)scatalog.RegionOne.volume.name = Volume ServiceIt seems your openstack is looking for the volume on wrong volume server.-openstack-bounces+gongysh=cn.ibm@lists.launchpad.net wrote: -To: Razique Mahroua From: Shashank Sahni Sent by: openstack-bounces+gongysh=cn.ibm@lists.launchpad.netDate: 05/14/2012 09:20PMCc: openstack@lists.launchpad.netSubject: 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


  

  
  
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-0003 -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
  
  

   
  
  

  


  ___Mailing list: https://launchpad.net/~openstackPost to     : openstack@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstackMore help   : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Problem with attaching disks to an instance

2012-05-14 Thread Shashank Sahni 

  
  
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


  

  
  
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-0003 -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
  
  

   
  
  

  


  

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Problem with attaching disks to an instance

2012-05-14 Thread Razique Mahroua 
Hi,do you have the flag iscsi_ip_prefix configured in your 
nova.conf ?Razique 	   
   	Shashank Sahni  
  14 mai 2012 14:22Hi 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-0003 -p controller:3260 --rescan


2012-05-14 17:32:13 TRACE nova.rpc.amqp Exit code: 2552012-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/~openstackPost to : 
openstack@lists.launchpad.netUnsubscribe : 
https://launchpad.net/~openstackMore help   : 
https://help.launchpad.net/ListHelp-- Nuage & Co - Razique Mahroua 
razique.mahr...@gmail.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

[Openstack] Problem with attaching disks to an instance

2012-05-14 Thread Shashank Sahni 
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-0003 -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