If you can create the SR in XenServer then I would recommend just doing that, make a note of the name-label (don't use spaces in the name), and reference that name as a preSetup SR for CloudStack to reference. In our case, all of our SR's are preSetup because of some customizations we have to make with XS that CloudStack can't do (certain things specific to our SAN). I've found it to be the most reliable and easiest way to configure an iSCSI LUN with CS.
-----Original Message----- From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] Sent: Monday, January 28, 2013 2:42 PM To: cloudstack-dev@incubator.apache.org Subject: Re: DevCloud Question I can see if our test group has a XenCenter instance running...they likely do (since those guys test our SAN against all sorts of configs). I didn't actually kick a VM off, but I went through the process of doing so and was able to select my iSCSI SR. On Mon, Jan 28, 2013 at 3:26 PM, Clayton Weise <cwe...@iswest.net> wrote: > Oh, and the 'xe' stuff aside you can just do basic iSCSI operations just > as if it were a regular Cent/RHEL box with the open-iscsi tools. > > -----Original Message----- > From: Clayton Weise [mailto:cwe...@iswest.net] > Sent: Monday, January 28, 2013 2:25 PM > To: cloudstack-dev@incubator.apache.org > Subject: RE: DevCloud Question > > OpenXenManager is spotty at best. If you have the option available of a > windows workstation then run XenCenter otherwise the xe commands are your > best bet. > > -----Original Message----- > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] > Sent: Monday, January 28, 2013 2:13 PM > To: cloudstack-dev@incubator.apache.org > Subject: Re: DevCloud Question > > Hi guys, > > Yeah, I'm trying to use OpenXenManager, but am seeing mixed results. > Sometimes it just crashes. > > It did seem to attach my iSCSI storage, though, but does not show it from > the GUI (I can see it in Xen directly). > > Weird > > > On Mon, Jan 28, 2013 at 3:11 PM, Clayton Weise <cwe...@iswest.net> wrote: > > > Sebastien, he's trying to attach to an iSCSI LUN which is different. If > > available, XenCenter is the easiest way to do it otherwise it _can_ be > done > > through the xe commands but it's a bit more involved. > > > > -----Original Message----- > > From: Sebastien Goasguen [mailto:run...@gmail.com] > > Sent: Monday, January 28, 2013 12:42 PM > > To: cloudstack-dev@incubator.apache.org > > Subject: Re: DevCloud Question > > > > Mike, I am out of my comfort zone here, but I believe you need to define > a > > storage repository on your xen host: > > > > In devcloud Rohit did it like this: > > > > xe sr-create host-uuid=$hostuuid name-label=local-storage shared=false > > type=file device-config:location=/opt/storage/primary > > > > > > -sebastien > > > > On Jan 28, 2013, at 7:16 PM, Mike Tutkowski < > mike.tutkow...@solidfire.com> > > wrote: > > > > > Cool...so, as far as you know, David, if I have an iSCSI target that > > seems > > > to be working (I can access it from the iSCSI initiator on my Mac OS X > > > box), I should be able to add a Primary Storage type in CS (for a > cluster > > > using Xen + XAPI) that leverages that iSCSI target? > > > > > > That is what I'm currently having trouble with as CS throws an > exception. > > > > > > I plan to try to hook up the iSCSI target directly to Xen next and then > > use > > > the PreSetup option in CS to see if that works. > > > > > > > > > On Mon, Jan 28, 2013 at 10:05 AM, David Nalley <da...@gnsa.us> wrote: > > > > > >> On Mon, Jan 28, 2013 at 12:00 PM, Mike Tutkowski > > >> <mike.tutkow...@solidfire.com> wrote: > > >>> Thanks David > > >>> > > >>> So, is XAPI the way CloudStack communicates to Xen? I'm just coming > up > > >> to > > >>> speed on Xen, by the way. > > >>> > > >>> Also, when you say, "is essentially XenServer in the eyes of > > CloudStack," > > >>> what does that mean? The two (Xen + XAPI or XenServer) are looked at > > as > > >> if > > >>> they are the same? > > >> > > >> XenServer, other features notwithstanding - is essentially Xen + XAPI > > >> atop a Linux distribution. While there are other important pieces, the > > >> piece that CloudStack interacts with is XAPI, so it assumes if it is > > >> interacting with XAPI that it is interacting with XenServer. (as it > > >> does with XCP, and in this case with Xen + XAPI on Ubuntu) > > >> > > >> --David > > >> > > > > > > > > > > > > -- > > > *Mike Tutkowski* > > > *Senior CloudStack Developer, SolidFire Inc.* > > > e: mike.tutkow...@solidfire.com > > > o: 303.746.7302 > > > Advancing the way the world uses the > > > cloud<http://solidfire.com/solution/overview/?video=play> > > > *(tm)* > > > > > > > -- > *Mike Tutkowski* > *Senior CloudStack Developer, SolidFire Inc.* > e: mike.tutkow...@solidfire.com > o: 303.746.7302 > Advancing the way the world uses the > cloud<http://solidfire.com/solution/overview/?video=play> > *(tm)* > -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play> *(tm)*
