Return-Path: 
 <dev-return-36435-apmail-cloudstack-dev-archive=cloudstack.apache.org@cloudstack.apache.org>
X-Original-To: apmail-cloudstack-dev-archive@www.apache.org
Delivered-To: apmail-cloudstack-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 7A0EC1043F
	for <apmail-cloudstack-dev-archive@www.apache.org>;
 Tue, 25 Jun 2013 23:07:04 +0000 (UTC)
Received: (qmail 4786 invoked by uid 500); 25 Jun 2013 23:07:03 -0000
Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org
Received: (qmail 4700 invoked by uid 500); 25 Jun 2013 23:07:03 -0000
Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@cloudstack.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@cloudstack.apache.org>
List-Post: <mailto:dev@cloudstack.apache.org>
List-Id: <dev.cloudstack.apache.org>
Reply-To: dev@cloudstack.apache.org
Delivered-To: mailing list dev@cloudstack.apache.org
Received: (qmail 4691 invoked by uid 99); 25 Jun 2013 23:07:03 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Jun 2013 23:07:03 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of Edison.su@citrix.com
 designates 66.165.176.63 as permitted sender)
Received: from [66.165.176.63] (HELO SMTP02.CITRIX.COM) (66.165.176.63)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Jun 2013 23:07:00 +0000
X-IronPort-AV: E=Sophos;i="4.87,940,1363132800";
   d="scan'208";a="31825508"
Received: from sjcpex01cl03.citrite.net ([10.216.14.145])
  by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA;
 25 Jun 2013 23:06:38 +0000
Received: from SJCPEX01CL01.citrite.net ([169.254.1.104]) by
 SJCPEX01CL03.citrite.net ([10.216.14.145]) with mapi id 14.02.0342.004; Tue,
 25 Jun 2013 16:06:37 -0700
From: Edison Su <Edison.su@citrix.com>
To: 'Prasanna Santhanam' <tsp@apache.org>, "dev@cloudstack.apache.org"
	<dev@cloudstack.apache.org>
CC: John Burwell <jburwell@basho.com>
Subject: RE: How does the plugin model work for storage providers?
Thread-Topic: How does the plugin model work for storage providers?
Thread-Index: AQHOcaiCq5l2+178yEmoK3f8Klsj1JlG8BYAgAACioCAABh1wA==
Date: Tue, 25 Jun 2013 23:06:36 +0000
Message-ID: <77B337AF224FD84CBF8401947098DD870542E9@SJCPEX01CL01.citrite.net>
References: <20130625133243.GA13801@cloud-2.local>
 <CACOnxChUL17-EN16aBcBoPSZzRJS9KYxs4uyfNjWjisjr=c=Vw@mail.gmail.com>
 <20130625142845.GB17817@cloud-2.local>
In-Reply-To: <20130625142845.GB17817@cloud-2.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.216.48.12]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Virus-Checked: Checked by ClamAV on apache.org

I would say, the adapter thing is the legacy stuff, all the storage plugins=
 will be managed by DataStoreProviderManager. But as you said, we can group=
 plugins into one place by using spring's syntax, such as:
<bean id=3D"storageProviders"
      class=3D"org.apach.***.datastoreproviderManagerImpl">
    <property name=3D"providerList">
        <list>
            <ref local=3D"providerOne"/>
            <ref local=3D"providerTwo"/>
        </list>
    </property>
</bean>
         =20


> -----Original Message-----
> From: Prasanna Santhanam [mailto:tsp@apache.org]
> Sent: Tuesday, June 25, 2013 7:29 AM
> To: dev@cloudstack.apache.org
> Cc: Edison Su; John Burwell
> Subject: Re: How does the plugin model work for storage providers?
>=20
> Understood, I've done that. But I was wondering if there was a generic wa=
y
> to group all components (driver, lifecycle, provider) of a vendor-
> implementation into a logical spring context like say:
>=20
> In componentContext.xml.in
>=20
> <!-- Networking adapters -->
>   <bean id=3D"ipDeployers" class=3D"com.cloud.utils.component.AdapterList=
">
>     <property name=3D"Adapters">
>       <list>
>           <ref bean=3D"elasticLoadBalancerElement"/>
>           <ref bean=3D"VirtualRouter"/>
>           <ref bean=3D"VpcVirtualRouter"/>
>           <ref bean=3D"NiciraNvp"/>
>           <ref bean=3D"InternalLbVm"/>
>       </list>
>     </property>
>   </bean>
>=20
> On Tue, Jun 25, 2013 at 08:19:40AM -0600, Mike Tutkowski wrote:
> > Hi,
> >
> > Yeah, John Burwell is finishing up the review process for the
> > SolidFire plug-in, so - at present - the code is not in master.
> >
> > To try to answer your question, I had to modify the
> > applicationContext.xml.in file.
> >
> > Here is the line I added:
> >
> > <bean id=3D"solidFireDataStoreProvider"
> >
> class=3D"org.apache.cloudstack.storage.datastore.provider.SolidfirePrimar=
yDat
> aStoreProvider"
> > />
> >
> > Talk to you later!
> >
> >
> > On Tue, Jun 25, 2013 at 7:32 AM, Prasanna Santhanam <tsp@apache.org>
> wrote:
> >
> > > Hi
> > >
> > > I noticed that all the storage providers are plugged in via
> > > applicationContext by default. How does one plugin a custom provider
> > > - say for example CompanyXStorageProvider?
> > >
> > > On looking at the SolidFire implementation I found the plugin
> > > doesn't actually come into play when running in either OSS or nonOSS
> mode.
> > > IOW, the plugin isn't injected in either of -
> > > componentContext.xml.in / nonossComponentContext.xml.in. Is the
> merge still in progress?
> > >
> > > Since these are not 'Adapters' so I don't know how to plugin my own
> > > storage provider into the contexts - oss/non-oss. Unlike network
> > > elements the DataStoreProvider, DataStoreLifeCycle seem independant
> > > and don't follow the plugin model. How does this work?
> > >
> > > Thanks,
> > >
> > > --
> > > Prasanna.,
> > >
> > > ------------------------
> > > Powered by BigRock.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>
> > *?*
>=20
> --
> Prasanna.,
>=20
> ------------------------
> Powered by BigRock.com