...
Following will be the changes in their behavior post introduction of Object Store plugin framework:
...
image store commands
- addSecondaryStorageCmd addImageStoreCmd - This command will be used to handle adding secondary storage image store from different providers, including NFS, S3, Swift, etc, also support zone-wide or global secondary storage options.
- listImageStoreCmd
- deleteImageStoreCmd
- enableImageStoreCmd
- listImageProviderCmd - List all enabled image store providers
Here are previous APIs to be deprecated
- addSecondaryStorageCmd
- addS3Cmd
- addSwiftCmd
- listS3Cmd
- listSwiftCmdaddS3Cmd and addSwiftCmd - These two commands will be removed.
snapshot commands
...
- No changes: attachVolume, detachVolume, deleteVolume, listVolumes
- To be changed:
extractVolume - Do we put it into S3 now internally ?
uploadVolume - similar to register template. User needs to put in just the S3 url here.
createVolume - when creating volume from snapshot, zone id needs to be mentioned.
migrateVolume - should work as is using scratch storage instead of nfs sec. storage.
Besides these existing API changes, we will provide two new admin APIs to configure backup object store provider:
- listBackupProviders – List CS managed backup providers and their capabilities.
- configureBackupProvider – choose a provider (like S3 or Swift) as backup provider.
Tasks:
- Backup storage framework
- refactoring snapshot service
- refactoring template service
- refactoring data motion strategy plugin
- Autoscaling cache storage framework
- cache storage plugin interface
- autoscaling strategy plugin
- NFS based cache storage implementation
- NFS transport VM based cache storage implementation
- NFS cache storage vs NFS transport VM based cache storage
- image store plugins at the mgt server side
- classical NFS plugin
- S3 plugin
- swift plugin
- image store plugins at the hypervisor side
- vmware
- kvm
- xenserver
- API changes
- end user APIs
- admin APIS