You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by "shaerul (via GitHub)" <gi...@apache.org> on 2024/05/10 20:26:14 UTC
[D] How CloudStack handles multiple NFS type Primary Storage [cloudstack]
GitHub user shaerul created a discussion: How CloudStack handles multiple NFS type Primary Storage
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete the comments.
-->
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
<!-- Pick one below and delete the rest -->
* Feature Idea
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
Multiple NFS based primary storages
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main branch.
-->
~~~
4.18.1.0
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network, advanced networking, etc. N/A otherwise
-->
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
Ubuntu 20.04 LTS
##### SUMMARY
<!-- Explain the problem/feature briefly -->
Wondering how the writing is managed by ACS
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
* Infrastructure
* Primary Storage
* Add Primary Storage
* Configuring NFS Storage
* After Adding NFS successfully creating Instances/VMs volume
<!-- Paste example playbooks or commands between quotes below -->
~~~
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
* 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
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
Unknown
~~~
GitHub link: https://github.com/apache/cloudstack/discussions/9073
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] How CloudStack handles multiple NFS type Primary Storage [cloudstack]
Posted by "shaerul (via GitHub)" <gi...@apache.org>.
GitHub user shaerul added a comment to the discussion: How CloudStack handles multiple NFS type Primary Storage
Got it thanks. Can you please delete this from here?
GitHub link: https://github.com/apache/cloudstack/discussions/9073#discussioncomment-9389331
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] How CloudStack handles multiple NFS type Primary Storage [cloudstack]
Posted by "rohityadavcloud (via GitHub)" <gi...@apache.org>.
GitHub user rohityadavcloud added a comment to the discussion: How CloudStack handles multiple NFS type Primary Storage
Since this is connected to users@ ML, I don’t see why users can’t ask here. Anybody replying on users@ wouldn’t be reflected here though, but they can follow the link to advise further.
GitHub link: https://github.com/apache/cloudstack/discussions/9073#discussioncomment-9400132
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] How CloudStack handles multiple NFS type Primary Storage [cloudstack]
Posted by "andrijapanicsb (via GitHub)" <gi...@apache.org>.
GitHub user andrijapanicsb added a comment to the discussion: How CloudStack handles multiple NFS type Primary Storage
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
GitHub link: https://github.com/apache/cloudstack/discussions/9073#discussioncomment-9389330
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] How CloudStack handles multiple NFS type Primary Storage [cloudstack]
Posted by "shaerul (via GitHub)" <gi...@apache.org>.
GitHub user shaerul closed a discussion: How CloudStack handles multiple NFS type Primary Storage
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete the comments.
-->
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
<!-- Pick one below and delete the rest -->
* Feature Idea
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
Multiple NFS based primary storages
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main branch.
-->
~~~
4.18.1.0
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network, advanced networking, etc. N/A otherwise
-->
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
Ubuntu 20.04 LTS
##### SUMMARY
<!-- Explain the problem/feature briefly -->
Wondering how the writing is managed by ACS
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
* Infrastructure
* Primary Storage
* Add Primary Storage
* Configuring NFS Storage
* After Adding NFS successfully creating Instances/VMs volume
<!-- Paste example playbooks or commands between quotes below -->
~~~
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
* 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
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
Unknown
~~~
GitHub link: https://github.com/apache/cloudstack/discussions/9073
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] How CloudStack handles multiple NFS type Primary Storage [cloudstack]
Posted by "rohityadavcloud (via GitHub)" <gi...@apache.org>.
GitHub user rohityadavcloud added a comment to the discussion: How CloudStack handles multiple NFS type Primary Storage
@shaerul for all NFS primary storages, CloudStack copies the template/iso (image) on the primary storage from the secondary storage which is called preparing template on primary storage. Such a prepared or cached template is then used to deploy VMs on primary storage where for most hypervisors the VM’s boot/root disk is a copy or link to the cached image.
GitHub link: https://github.com/apache/cloudstack/discussions/9073#discussioncomment-9400139
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] How CloudStack handles multiple NFS type Primary Storage [cloudstack]
Posted by "shaerul (via GitHub)" <gi...@apache.org>.
GitHub user shaerul added a comment to the discussion: How CloudStack handles multiple NFS type Primary Storage
@rohityadavcloud
Thank you very much for all the documentation you've provided on CloudStack installation and troubleshooting. It's been incredibly helpful and has made our lives much easier.
I wanted to ask: If you have multiple NFS primary storages, how does CloudStack manage the distribution of VM volume creation across them? Does it follow round-robin or something like condensed method?
Thanks.
GitHub link: https://github.com/apache/cloudstack/discussions/9073#discussioncomment-9410571
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
Re: [D] How CloudStack handles multiple NFS type Primary Storage [cloudstack]
Posted by "rohityadavcloud (via GitHub)" <gi...@apache.org>.
GitHub user rohityadavcloud added a comment to the discussion: How CloudStack handles multiple NFS type Primary Storage
@shaerul It follows a lazy deployment strategy, i.e. it copies the templates (images) to a primary storage only when it needs to create a VM's root disk on a pool. There's also a [prepareTemplate API](https://cloudstack.apache.org/api/apidocs-4.19/apis/prepareTemplate.html) that can load a template across pools to do this ahead of time.
In terms of using storage pool upon VM deployment or volume creation, it depends what deployment planning algorithm is used, pl search for these global settings (for tuning and configuration): image.store.allocation.algorithm [1], vm.allocation.algorithm [2].
[1] Image store allocation algorithm (image.store.allocation.algorithm)
firstfitleastconsumed','random' : Order in which hosts within a cluster will be considered for VM/volume allocation
[2] Vm allocation algorithm (vm.allocation.algorithm)
'random', 'firstfit', 'userdispersing', 'userconcentratedpod_random', 'userconcentratedpod_firstfit', 'firstfitleastconsumed' : Order in which hosts within a cluster will be considered for VM/volume allocation.
GitHub link: https://github.com/apache/cloudstack/discussions/9073#discussioncomment-9426611
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org