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> *™*
