Skip to content

How CloudStack handles multiple NFS type Primary Storage  #9067

Closed

Description

@shaerul

I have added a second primary storage to my CloudStack which has augmented the storage space in Dashboard. I have gone through the CloudsStack documents and browsed through the Internet but didn't get a precise clue how ACS is managing multiple NFS storages to distribute VM image creation. I didn't find any global parameters either to control this distribution behavior.

Can someone please enlighten me?

ISSUE TYPE
  • Feature Idea
COMPONENT NAME
Multiple NFS based primary storages
CLOUDSTACK VERSION
4.18.1.0
CONFIGURATION
OS / ENVIRONMENT

Ubuntu 20.04 LTS

SUMMARY

Wondering how the writing is managed by ACS

STEPS TO REPRODUCE
  • Infrastructure
  • Primary Storage
  • Add Primary Storage
  • Configuring NFS Storage
  • After Adding NFS successfully creating Instances/VMs volume

EXPECTED RESULTS
* Either round robin Instance Volume creation among two or multiple NFS primary storages OR
* The first one will fill up the threshold space and then ACS will start creating on the second primary storage and so on.
ACTUAL RESULTS
Unknown

Activity

  1. andrijapanicsb commented on May 10, 2024

    @andrijapanicsb
    Contributor

    Please post your questions on the mailing list, GitHub is not the right place for it (it creates clutter) and you will get a much quicker reply on the mailing list (users@).
    Thx

  2. shaerul commented on May 10, 2024

    @shaerul
    Author

    Got it thanks. Can you please delete this from here?

  3. locked and limited conversation to collaborators on May 10, 2024
  4. converted this issue into a discussion #9073 on May 10, 2024
  5. added this to the unplanned milestone on Sep 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions