Hi:

What I would look at would either using separate NFS endpoints for primary and secondary, or just different mountpoints being tied to different (performance-wise) disk pools.  Otherwise, you would be stuck using custom ports for primary and default port for secondary (I don't know if there is a way to specify a custom port on secondary NFS).

Personally, I would look into different mount points pointing to different disk pools.  Example: server1:/primary0 and server1:/secondary0 - something like that.  Bonus: you can also tie in the loadbalancer arrangement to get the benefits of high-availability.

$.02

Ron Gage


On 5/26/2025 6:40 PM, amosgiture (via GitHub) wrote:
GitHub user amosgiture created a discussion: Secondary Storage NFS custom port

I'm using a Ceph cluster for both primary and secondary storage. Using a 
floating ceph cluster IP and port 2050 to make NFS highly available. Port 2049 
is already in use by the NFS server daemons in Ceph.
Primary storage works great since I can specify port=2050 in the mount options 
in the cloudstack UI. Secondary storage does not provide a way to customize the 
NFS port. I'm stuck.
I'm using KVM hosts on Ubuntu 22.04.
Any help would be appreciated to overcome this. If not, I'll try configuring S3 
in Ceph instead of NFS for secondary storage.

GitHub link: https://github.com/apache/cloudstack/discussions/10920

----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org

Reply via email to