cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Tutkowski <mike.tutkow...@solidfire.com>
Subject Re: Storage Subsystem 2.0 plugin docs
Date Wed, 20 Mar 2013 16:29:40 GMT
Hi,

Yeah, CHAP is not supported in the CloudStack API when creating/editing
Primary Storage (in other words, you can't create an iSCSI-based Primary
Storage using CHAP).  To make it work for XenServer, for example, you need
to set up your Storage Repository in XenServer first, then go to CloudStack
and create a PreSetup-type Primary Storage.

The reason I want to create a storage plug-in for CS is because of my
particular use case.  The SAN my company builds supports guaranteed IOPS to
iSCSI targets.  What this means is we'd like to have a single VM or data
disk use a single one of our iSCSI targets so we can say that VM or data
disk is guaranteed a set number of IOPS.

The way CS works today is generally to have multiple VMs and data disks
share a single iSCSI target.  In that model, we can't guarantee IOPS to any
VM or data disk specifically (only to the volume as a whole).

Edison's storage framework for CS 4.2 should fix this issue.  When a VM is
spawned or a data disk created, the storage framework should make use of
the plug-in to dynamically create an iSCSI target and use it for the VM or
data disk in question only.

Talk to you later!
Mike


On Wed, Mar 20, 2013 at 10:16 AM, Vladimir Popovski <
vladimir@zadarastorage.com> wrote:

> Thank you, Mike!
>
>
>
> I was really surprised when I found that there are no plugins from other
> companies and standard storage volume implementation does not support CHAP.
>
> I will wait for Edison and the community to answer. Btw, have you
> succeeded to activate your plugin? Is there any normal way of doing it or
> have you replaced DefaultPrimaryDatastoreProviderImpl
>
>
>
> Thanks,
>
> -Vladimir
>
>
>
>
>
> *From:* Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
> *Sent:* Wednesday, March 20, 2013 9:10 AM
> *To:* Vladimir Popovski
> *Subject:* Re: Storage Subsystem 2.0 plugin docs
>
>
>
> Hi Vladimir,
>
>
>
> This is Mike from SolidFire.
>
>
>
> I am still working on the SolidFire plug-in.  I have some questions
> outstanding with Edison and hope to have this all wrapped up before I
> present on it at a CloudStack Meetup in California on April 30th.
>
>
>
> I am only aware of the documentation you listed in your e-mail.  It is a
> good start, but not sufficient to implement a plug-in with.
>
>
>
> I'm guessing Edison will get back to us soon.
>
>
>
> Thanks!
>
> Mike
>
>
>
> On Wed, Mar 20, 2013 at 10:05 AM, Vladimir Popovski <
> vladimir@zadarastorage.com> wrote:
>
> Hi All,
>
>
>
> Thank you for a great work on CloudStack! We are interested in integrating
> CS with our storage system and started to look at your documentation and
> storage-related code. I see that Mike from SolidFire started working on
> something similar some time ago and Edison even created an empty plugin for
> it (in Nov’12?).
>
>
>
> We have couple of questions related to that:
>
> -          Is there any documentation about plugins (except of
> https://cwiki.apache.org/CLOUDSTACK/storage-subsystem-20.html)
>
> -          Are there any exemplary plugins for primary & secondary
> datastores? Was the SolidFire plugin ever finished?
>
> -          How to activate a new plugin and use it (at least through
> CLIs/APIs)
>
> -          How to integrate it with the UI
>
>
>
> Thanks,
>
> -Vladimir
>
>
>
>
>
> -------
>
> Vladimir Popovski
>
> VP, Cloud Operations
>
> Zadara Storage
> (949) 677-2095
>
> Vladimir@zadarastorage.com
>
> www.zadarastorage.com
>
>
>
>
>
>
>
>
>
> --
> *Mike Tutkowski*
>
> *Senior CloudStack Developer, SolidFire Inc.*
>
> e: mike.tutkowski@solidfire.com
>
> o: 303.746.7302
>
> Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play>
> *™*
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*™*

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message