Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: pass (athena.apache.org: domain of mike.tutkowski@solidfire.com
 designates 209.85.219.43 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAHkbCDjwaCc0HrhH8o5JZKNhr+oVRVzJ8DuCPTLxz9Lw1kCV6Q@mail.gmail.com>
References: 
 <CAHkbCDgJKzYhhmGOUYu2-104YhFeUP9SHM38f74O1e-p3Qxkfg@mail.gmail.com>
	<CACOnxCgxPy3pzQZXcxmeidFXnTBW075=5nyxm5mJoQD3LAdz8w@mail.gmail.com>
	<CAHkbCDjwaCc0HrhH8o5JZKNhr+oVRVzJ8DuCPTLxz9Lw1kCV6Q@mail.gmail.com>
Date: Thu, 8 Aug 2013 00:27:51 -0600
Message-ID: 
 <CACOnxChA3yAZq-6r8D+FdCTMA9cj2OmneWar=TffaaSVf1X3Uw@mail.gmail.com>
Subject: Re: [DISCUSS] CloudStack Storage Plugin for CloudByte's ElastiStor
From: Mike Tutkowski <mike.tutkowski@solidfire.com>
To: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>
Content-Type: multipart/alternative; boundary=089e01228aeee91dce04e369c11b

--089e01228aeee91dce04e369c11b
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi,

You are definitely free to map one of your SAN volumes to many CloudStack
volumes. I'm not sure how this would look code wise, but it should be
doable with some changes to CloudStack.

We encourage our customers to keep to smaller clusters (like four compute
nodes per cluster) as a way of improving the scalability of this one-to-one
approach.

Depending on the hypervisor, you could even have a cluster of one compute
node and have CloudStack handle HA across clusters.

Talk to you later


On Thu, Aug 8, 2013 at 12:22 AM, Amit Das <amit.das@cloudbyte.com> wrote:

> Hi Mike,
>
> I have gone through the mentioned jira as well the following article in
> dZone.
> http://architects.dzone.com/articles/cloudstack-storage
>
> It describes the problem & solution pretty well.
>
> However, do we have any alternatives w.r.t one-to-one mapping between a C=
S
> Volume & a SAN Volume ? Is this approach scalable ?
>
> Regards,
> Amit
> *CloudByte Inc.* <http://www.cloudbyte.com/>
>
>
> On Thu, Aug 8, 2013 at 11:36 AM, Mike Tutkowski <
> mike.tutkowski@solidfire.com> wrote:
>
> > Hi Amit,
> >
> > As I mentioned on a different thread, I would recommend looking at the
> > SolidFire plug-in.
> >
> > Also, John Burwell and I can work with you on changes in 4.3 in the
> storage
> > framework that might impact your development.
> >
> > The SolidFire plug-in was designed to provide Min and Max IOPS guarante=
es
> > to CloudStack data volumes. In this model, the CloudStack volume maps o=
n
> to
> > a single SAN volume (as opposed to the traditional technique in
> CloudStack
> > where a volume (say, on a SAN) would house many CloudStack volumes).
> >
> > Also, feel free to a look at the JIRA ticket I wrote up for 4.2:
> >
> > https://issues.apache.org/jira/browse/CLOUDSTACK-2778
> >
> > Thanks
> >
> >
> > On Wed, Aug 7, 2013 at 11:47 PM, Amit Das <amit.das@cloudbyte.com>
> wrote:
> >
> > > I would like to implement a new storage plugin based on the recently
> > > refactored CloudStack(CS) storage code.
> > >
> > > This plugin will allow a CS Admin to interact with ElastiStor's APIs =
to
> > > provision and manage QoS-aware storage volumes for VMs.
> > >
> > > CloudByte's ElastiStor is a full-featured software-defined storage Qo=
S
> > > solution.
> > >
> > > Any suggestions ?
> > >
> > > Regards,
> > > Amit
> > > *CloudByte Inc.* <http://www.cloudbyte.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=3Dplay>
> > *=99*
> >
>


--=20
*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=3Dplay>
*=99*

--089e01228aeee91dce04e369c11b--