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" <[email protected]> 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: [email protected] >o: 303.746.7302 >Advancing the way the world uses the >cloud<http://solidfire.com/solution/overview/?video=play> >*(tm)*
