WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-api

Re: [Xen-API]Introducing VDI in ISCSISR fail

To: Julian Chesterfield <julian.chesterfield@xxxxxxxxxxxxx>
Subject: Re: [Xen-API]Introducing VDI in ISCSISR fail
From: Anthony Xu <anthony@xxxxxxxxx>
Date: Wed, 3 Feb 2010 10:23:53 -0800
Cc: "xen-api@xxxxxxxxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 03 Feb 2010 10:23:48 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B694A41.60908@xxxxxxxxxxxxx>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
Organization: VMOps
References: <1265154348.2932.12.camel@mobl-ant> <4B694A41.60908@xxxxxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
That makes sense, 
when executing sr-scan, do all servers execute iscsi re-scan operation
to get new shared luns?

- Anthony


On Wed, 2010-02-03 at 02:04 -0800, Julian Chesterfield wrote:
> That's correct. SR scan always executes on the SR master only, so for 
> shared SRs the SR master is the pool master. Are you trying to introduce 
> a LUN to all nodes in the same pool, or is this just mapped to a single 
> host? If the latter, then the SR should not be shared.
> 
> - Julian
> 
> Anthony Xu wrote:
> > I'm playing with ISCSISR in a pool environment, seems like sr-scan is
> > only executed in one specified server even if I execute it in another
> > server. Then I want to introduce a iscsi LUN into this SR, from
> > following traceback, looks like sm-config:LUNid="5"
> > sm-config:SCSIid="3600144f0a5af4e0000004b67aa0c004c" is not passed to
> > ISCSISR sm. 
> >
> > Could you enlighten me how to do it?
> >
> >
> > Thanks
> > - Anthony
> >
> >
> >
> >
> > xe vdi-introduce sr-uuid=2b462a52-4af2-88d8-ad80-e0fd17ec4ac0  type=user
> > name-babel="cenos-root" uuid=7beeee98-7168-137d-d7e8-7ef947af00c3
> > location=7beeee98-7168-137d-d7e8-7ef947af00c3 managed=true
> > sm-config:LUNid="5" sm-config:SCSIid="3600144f0a5af4e0000004b67aa0c004c"
> > There was an SR backend failure.
> > status: non-zero exit
> > stdout: 
> > stderr: Traceback (most recent call last):
> >   File "/opt/xensource/sm/ISCSISR", line 639, in ?
> >     SRCommand.run(ISCSISR, DRIVER_INFO)
> >   File "/opt/xensource/sm/SRCommand.py", line 150, in run
> >     ret = cmd.run(sr)
> >   File "/opt/xensource/sm/SRCommand.py", line 65, in run
> >     return target.introduce(self.params['sr_uuid'],
> > self.params['new_uuid'])
> >   File "/opt/xensource/sm/LUNperVDI.py", line 49, in introduce
> >     vdi_path = self.sr._getLUNbySMconfig(self.sm_config)
> >   File "/opt/xensource/sm/ISCSISR", line 527, in _getLUNbySMconfig
> >     if not self.sm_config.has_key('LUNid'):
> > AttributeError: 'ISCSISR' object has no attribute 'sm_config'
> >
> >
> >
> >
> > _______________________________________________
> > xen-api mailing list
> > xen-api@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/mailman/listinfo/xen-api
> >   
> 


_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api

<Prev in Thread] Current Thread [Next in Thread>