Skip to content

Support multiple storage providers for secondary storage in a zone #9521

Description

@kiranchavala

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

  1. Navigate to Infrastructure > Secondary storage >

  2. Add secondary storage for storage provider s3

Screenshot 2024-08-13 at 1 35 07 PM

Screenshot 2024-08-13 at 2 51 15 PM

Logs

root@ref-trl-7087-k-Mu24-kiran-chavala-mgmt1:~# cat  /var/log/cloudstack/management/management-server.log |grep -i "logid:ab39b82d"
2024-08-02 07:17:32,204 DEBUG [c.c.a.ApiServlet] (qtp364604394-20:ctx-36924578) (logid:ab39b82d) ===START===  10.0.3.251 -- GET  name=minio&details[2].key=bucket&details[2].value=kiran-bucket2&details[3].key=usehttps&details[3].value=false&details[4].key=endpoint&details[4].value=http:%2F%2F10.0.32.251:9000&provider=S3&command=addImageStore&response=json
2024-08-02 07:17:32,204 DEBUG [c.c.a.ApiServlet] (qtp364604394-20:ctx-36924578) (logid:ab39b82d) Two factor authentication is already verified for the user 2, so skipping
2024-08-02 07:17:32,210 DEBUG [c.c.a.ApiServer] (qtp364604394-20:ctx-36924578 ctx-4856a5f7) (logid:ab39b82d) CIDRs from which account 'Account [{"accountName":"admin","id":2,"uuid":"97bbbe87-4fc8-11ef-82b1-1e00590001cf"}]' is allowed to perform API calls: 0.0.0.0/0,::/0
2024-08-02 07:17:32,213 DEBUG [o.a.c.a.StaticRoleBasedAPIAccessChecker] (qtp364604394-20:ctx-36924578 ctx-4856a5f7) (logid:ab39b82d) RoleService is enabled. We will use it instead of StaticRoleBasedAPIAccessChecker.
2024-08-02 07:17:32,214 DEBUG [o.a.c.r.ApiRateLimitServiceImpl] (qtp364604394-20:ctx-36924578 ctx-4856a5f7) (logid:ab39b82d) API rate limiting is disabled. We will not use ApiRateLimitService.
2024-08-02 07:17:32,216 INFO  [c.c.a.ApiServer] (qtp364604394-20:ctx-36924578 ctx-4856a5f7) (logid:ab39b82d) You can only add new image stores from the same provider NFS already added
2024-08-02 07:17:32,216 DEBUG [c.c.a.ApiServlet] (qtp364604394-20:ctx-36924578 ctx-4856a5f7) (logid:ab39b82d) ===END===  10.0.3.251 -- GET  name=minio&details[2].key=bucket&details[2].value=kiran-bucket2&details[3].key=usehttps&details[3].value=false&details[4].key=endpoint&details[4].value=http:%2F%2F10.0.32.251:9000&provider=S3&command=addImageStore&response=json

Expected behaviour

It would be a useful feature if end user wants to migrate the secondary storage other storage providers

Activity

  1. added this to the 4.21.0.0 milestone on Aug 13, 2024
  2. andrijapanicsb commented on Aug 14, 2024

    @andrijapanicsb
    Contributor

    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.

  3. rajujith commented on Aug 16, 2024

    @rajujith
    Contributor

    @kiranchavala @andrijapanicsb Adding S3 secondary storage got fixed: #8956
    The seeding template remains to be fixed: #9002
    IMO this feature request will be a valid use once we have S3 secondary storage fully working.

  4. modified the milestones: 4.21.0, 4.22.0 on Jul 11, 2025
  5. 2 remaining items

  6. added this to the 4.22.1 milestone on Nov 12, 2025
  7. kiranchavala commented on Feb 10, 2026

    @kiranchavala
    MemberAuthor

    can we revist this @DaanHoogland @rajujith @sureshanaparti @abh1sar

    Currently s3 secondary storage will work fine with this pr

    #12426

  8. modified the milestones: 4.22.1, 4.20.3, 4.23.0 on Feb 10, 2026
  9. DaanHoogland commented on Feb 10, 2026

    @DaanHoogland
    Contributor

    @kiranchavala so #12426 fixes the s3 issue, but still a region even only works with one type of secondary storage, right?

  10. modified the milestones: 4.23.0, 4.24.0 on Jun 29, 2026
  11. nvazquez commented on Oct 29, 2026

    @nvazquez
    Contributor

    PR in progress: #12426

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions