Yes, my guess is that you will need the iscsi initiator utilities installed. There should be standard packages for any distro. Then you'd call an agent storage adaptor to do the initiator login. See the info I sent previously about LibvirtStorageAdaptor.java and libvirt iscsi storage type to see if that fits your need. On Sep 13, 2013 4:55 PM, "Mike Tutkowski" <mike.tutkow...@solidfire.com> wrote:
> Hi, > > As you may remember, during the 4.2 release I developed a SolidFire > (storage) plug-in for CloudStack. > > This plug-in was invoked by the storage framework at the necessary times > so that I could dynamically create and delete volumes on the SolidFire SAN > (among other activities). > > This is necessary so I can establish a 1:1 mapping between a CloudStack > volume and a SolidFire volume for QoS. > > In the past, CloudStack always expected the admin to create large volumes > ahead of time and those volumes would likely house many root and data disks > (which is not QoS friendly). > > To make this 1:1 mapping scheme work, I needed to modify logic in the > XenServer and VMware plug-ins so they could create/delete storage > repositories/datastores as needed. > > For 4.3 I want to make this happen with KVM. > > I'm coming up to speed with how this might work on KVM, but I'm still > pretty new to KVM. > > Does anyone familiar with KVM know how I will need to interact with the > iSCSI target? For example, will I have to expect Open iSCSI will be > installed on the KVM host and use it for this to work? > > Thanks for any suggestions, > Mike > > -- > *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> > *™* >
