You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Mike Tutkowski <mi...@solidfire.com> on 2014/04/23 18:10:42 UTC
[VMware] VmwareStorageProcessor vs. VmwareStorageManager
Hi,
Can someone tell me what's a good rule of thumb to use when deciding if
storage-related code should go into VmwareStorageProcessor or
VmwareStorageManager?
Thanks!
--
*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>
*(tm)*
Re: [VMware] VmwareStorageProcessor vs. VmwareStorageManager
Posted by Mike Tutkowski <mi...@solidfire.com>.
OK - thanks, Min!
On Wed, Apr 23, 2014 at 10:24 AM, Min Chen <mi...@citrix.com> wrote:
> VmwareStorageProcessor was introduced in 4.2 storage refactor, which
> contains methods to execute all those StorageSubSystemCommand we
> introduced, like CopyCommand, CreateObjectCommand, etc.
> VmwareStorageManager has methods to execute all other resource commands
> which were there before storage refactor.
>
> Thanks
> -min
>
> On 4/23/14 9:10 AM, "Mike Tutkowski" <mi...@solidfire.com> wrote:
>
> >Hi,
> >
> >Can someone tell me what's a good rule of thumb to use when deciding if
> >storage-related code should go into VmwareStorageProcessor or
> >VmwareStorageManager?
> >
> >Thanks!
> >
> >--
> >*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>
> >*(tm)*
>
>
--
*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>
*(tm)*
Re: [VMware] VmwareStorageProcessor vs. VmwareStorageManager
Posted by Min Chen <mi...@citrix.com>.
VmwareStorageProcessor was introduced in 4.2 storage refactor, which
contains methods to execute all those StorageSubSystemCommand we
introduced, like CopyCommand, CreateObjectCommand, etc.
VmwareStorageManager has methods to execute all other resource commands
which were there before storage refactor.
Thanks
-min
On 4/23/14 9:10 AM, "Mike Tutkowski" <mi...@solidfire.com> wrote:
>Hi,
>
>Can someone tell me what's a good rule of thumb to use when deciding if
>storage-related code should go into VmwareStorageProcessor or
>VmwareStorageManager?
>
>Thanks!
>
>--
>*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>
>*(tm)*