Open kiranchavala opened 1 month ago
I don't think that S3 even works, so adding support for mixing different providers, while the other provider (S3) is broken, doesn't make much sense (I recall @rajujith testing S3 as the Sec.Stor.) - unless this has been fixed - then I take it back.
What is the use case for this? I see code getting more complicated and I'm unaware of a single user request for such (IMO) unusual feature? Happy to be said I'm wrong/have missed something.
@kiranchavala @andrijapanicsb Adding S3 secondary storage got fixed: https://github.com/apache/cloudstack/issues/8956 The seeding template remains to be fixed: https://github.com/apache/cloudstack/issues/9002 IMO this feature request will be a valid use once we have S3 secondary storage fully working.
ISSUE TYPE
Enhancement/Improvement request
COMPONENT NAME
Component: UI
CLOUDSTACK VERSION
Cloudstack version 4.19
SUMMARY
Support multiple storage providers for secondary storage
Steps to reproduce the issue
Have an existing nfs secondary storage present
Navigate to Infrastructure > Secondary storage >
Add secondary storage for storage provider s3
Logs
Expected behaviour
It would be a useful feature if end user wants to migrate the secondary storage other storage providers