Mike, - Original VolumeManager and Impl has been broken up into two sets of files. - The code that handles the incoming api commands is in VolumeApiServiceImpl.java and remains in the server package. It will handle all self-service related type of changes. - The code that handles the orchestration for volume provisioning is in VolumeOrchestrationService and VolumeOrchestrator. They are in the cloud-engine-orchestration package. They handle how to interact with the storage plugins and the lifecycle of volume.
I intend to make changes on the VolumeOrchestrationService so that it unifies the creation of volume. But I wanted to separate them without making coding changes first so I don't make the same mistakes as in vmsync where the changes became too large to review. Appreciate any thoughts you have on this. --Alex > -----Original Message----- > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] > Sent: Monday, August 12, 2013 10:01 PM > To: dev@cloudstack.apache.org > Subject: Question: Has VolumeManager and VolumeManagerImpl been > refactored/removed in master > > Hi, > > I was curious to learn more about VolumeManager and VolumeManagerImpl > in master. > > They appear to be gone and I was interested in learning how this code has > been refactored. > > Thanks! > > -- > *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> > *(tm)*
