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="solidFireDataStoreProvider" class="org.apache.cloudstack.storage.datastore.provider.SolidfirePrimaryDataStoreProvider" /> Talk to you later! On Tue, Jun 25, 2013 at 7:32 AM, Prasanna Santhanam <t...@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.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play> *™*