can give us an idea what you are planning to modify.
>
> --Alex
>
> > -Original Message-
> > From: Amit Das [mailto:amit@cloudbyte.com]
> > Sent: Wednesday, September 11, 2013 5:53 AM
> > To: dev@cloudstack.apache.org
> > Subject: Re: [DESIGN] Ac
, which is what you listed here.
Maybe you can give us an idea what you are planning to modify.
--Alex
> -Original Message-
> From: Amit Das [mailto:amit@cloudbyte.com]
> Sent: Wednesday, September 11, 2013 5:53 AM
> To: dev@cloudstack.apache.org
> Subject: Re: [DE
Thanks Mike.
I referred to SolidFire's plugin implementation & found some differences
with the recommendations in this email thread.
Alex's email talks about using entity interface e.g. Volume than a VO class
e.g. VolumeVO.
However, both of our plugins require a mutable object (w.r.t volume,
stor
Hey Amit,
We might have already chatted a bit about this, but feel free to examine
the SolidFire plug-in as it likely handles what you're referring to here.
Talk to you later
On Wed, Sep 11, 2013 at 6:52 AM, Amit Das wrote:
> Hi All,
>
> I am in process of implementing a storage plugin and wo
Hi All,
I am in process of implementing a storage plugin and would require more
clarity on this front.
I need to update the 'Volume' as well as the 'StoragePool' in a new
implementing class of PrimaryDataStoreDriver (createAsync method to be
exact).
Should following method invocations be used to
Sorry clicked something that send that last email...
To finish
if ( obj instance VMInstanceVO )
return (VMInstanceVO)obj
else
return findByIdIncludingRemoved(obj.getId())
Just a thought
Darren
On Thu, Aug 22, 2013 at 1:38 PM, Darren Shepherd <
darren.s.sheph...@gmail.com> wrote:
> Thes
These are great points Alex is making here and I was just noticing the
same thing.
One if the things I've noticed is that most managers inject a lot of
DAOs. When you look at the code usually about half those DAOs are
needed only for findById. So if you are consuming an object use the
interface
