Alex Huang 572e71e57d Moved most of the VOs and DAOs from server package into engine-schema as well		2013-05-06 16:34:26 -07:00
..
download	CLOUDSTACK-2188 : Parsing error with Download Monitor while checking the health of downloaded templates	2013-05-06 15:11:49 +05:30
listener	CLOUDSTACK-1426: We has strong implication that VO must implement an interface, otherwise EntityManagerImpl can't the vo	2013-03-07 18:25:57 -08:00
monitor	Remove @author tag from non third-party source files in server folder	2012-08-13 15:17:31 +08:00
resource	squash changes into one giant patch	2013-02-21 11:22:48 -08:00
s3	squash changes into one giant patch	2013-02-21 11:22:48 -08:00
secondary	QuickCloud: sanitize logs for normal running of agents outside systemvm	2013-04-09 14:45:27 -07:00
snapshot	Removed files that are no longer used and further separated out the files in the core project	2013-05-06 16:34:21 -07:00
swift	Improve component lifecycle management with system run-level concept	2013-01-30 15:21:02 -08:00
upload	squash changes into one giant patch	2013-02-21 11:22:48 -08:00
LocalStoragePoolListener.java	CLOUDSTACK-1426: We has strong implication that VO must implement an interface, otherwise EntityManagerImpl can't the vo	2013-03-07 18:25:57 -08:00
OCFS2Manager.java	Patch from Chip Childers	2012-07-02 09:51:21 -04:00
OCFS2ManagerImpl.java	Moved agent commands to core and out of api	2013-05-06 16:34:20 -07:00
RegisterVolumePayload.java	squash changes into one giant patch	2013-02-21 11:22:48 -08:00
ResizeVolumePayload.java	Correcting license headers that broke the build	2013-02-21 16:29:05 -05:00
StorageManager.java	CLOUDSTACK-2036 - Adding storage storage.overprovisioning.factor configurable at zone level.	2013-05-01 14:21:09 +05:30
StorageManagerImpl.java	CLOUDSTACK-741 - Making storage disable thresholds configurable at zone level.	2013-05-01 15:44:09 +05:30
StoragePoolAutomation.java	move default primary storage plugin into its own pom	2013-03-20 17:21:40 -07:00
StoragePoolAutomationImpl.java	move default primary storage plugin into its own pom	2013-03-20 17:21:40 -07:00
TemplateProfile.java	fix downloading template	2013-02-21 11:22:48 -08:00
VolumeManager.java	Storage motion for Xenserver changes: 1. Implemented Api findStoragePoolsForMigration. Added a new response objects to list storage pools available for migration. 2. Updated migrateVolume api for allowing migrating volumes of running vms. These changes are integrated into the latest storage refactoring changes. 3. Added the implementation for findHostsForMigration api. It lists the hosts to which an instance can be migrated, including hosts from within and across clusters to which an instance may be migrated with storage motion. The work of migrating a volume of a running vm is also done in copyAsync. 4. Updated the listHosts api for backward compatibility. 5. Added the implementation for migrateVirtualMachineWithVolume api. It migrates an instance with its volumes within a cluster and also across clusters. Also introduced a new XenServerStorageMotionStrategy for migrating volumes of a vm. When a vm is being migrated with its volumes, the vm is put in migrating state and a request is send to the volume manager to migrate the vm and its volumes. Volume manager calls into the volume service which forwards the request to data motion service after moving all the volumes to migrating state. Data motion service enumerates the strategies and the request reaches the XenServerStorageMotionStrategy. It calls in to the resource to complete the operation. 6. Resolved an issue where storage xenmotion of 2nd VM created from the same template to a host was failing with duplicate_vm exception. Made changes to remove the mac_seed key value pair from other_config when vms are created. This is was storage motion to fail. 7. Updated the db upgrade schema script. 8. Added the right permissions in commands.properties 9. Marvin tests for testing storage motion. Following scenarios are tested. 9.1. A virtual machine is migrated to another host. Its volumes are also migrated to another storage pool. 9.2. Just the volumes of a vm are migrated to another storage pool while the vm continues to run on the same host. 10. Unit tests for testing migration of a vm with its volumes.	2013-04-19 11:36:42 +05:30
VolumeManagerImpl.java	Storage motion for Xenserver changes: 1. Implemented Api findStoragePoolsForMigration. Added a new response objects to list storage pools available for migration. 2. Updated migrateVolume api for allowing migrating volumes of running vms. These changes are integrated into the latest storage refactoring changes. 3. Added the implementation for findHostsForMigration api. It lists the hosts to which an instance can be migrated, including hosts from within and across clusters to which an instance may be migrated with storage motion. The work of migrating a volume of a running vm is also done in copyAsync. 4. Updated the listHosts api for backward compatibility. 5. Added the implementation for migrateVirtualMachineWithVolume api. It migrates an instance with its volumes within a cluster and also across clusters. Also introduced a new XenServerStorageMotionStrategy for migrating volumes of a vm. When a vm is being migrated with its volumes, the vm is put in migrating state and a request is send to the volume manager to migrate the vm and its volumes. Volume manager calls into the volume service which forwards the request to data motion service after moving all the volumes to migrating state. Data motion service enumerates the strategies and the request reaches the XenServerStorageMotionStrategy. It calls in to the resource to complete the operation. 6. Resolved an issue where storage xenmotion of 2nd VM created from the same template to a host was failing with duplicate_vm exception. Made changes to remove the mac_seed key value pair from other_config when vms are created. This is was storage motion to fail. 7. Updated the db upgrade schema script. 8. Added the right permissions in commands.properties 9. Marvin tests for testing storage motion. Following scenarios are tested. 9.1. A virtual machine is migrated to another host. Its volumes are also migrated to another storage pool. 9.2. Just the volumes of a vm are migrated to another storage pool while the vm continues to run on the same host. 10. Unit tests for testing migration of a vm with its volumes.	2013-04-19 11:36:42 +05:30