OK - thanks, Min!
On Wed, Apr 23, 2014 at 10:24 AM, Min Chen 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 meth
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 refac
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.tutkow...@solidfire.com
o: 303.746.7302
Advancing the
