NFS mounting on VM

##### ISSUE TYPE

* Other

##### COMPONENT NAME

UI

##### CLOUDSTACK VERSION

14.19.1

##### CONFIGURATION

Advance networking

##### OS / ENVIRONMENT

Ubuntu 22.04 and using KVM hypervisor

##### SUMMARY

I am trying to get NFS storage on the ACS VM. But VM virtual routers don't have a route or interface to that.
I am running the environment as below:
ACS Portal: 10.10.40.252
NFS server: 10.10.40.250
KVM host: 172.16.0.100 (Have to NIC 1 for local and 1 for public configured as cloudbr0 for private and cloudbr1 as public.)

ACS Management Range: 172.16.0.10–172.16.0.50 (cloudbr0)
ACS Public Range: 232.28.15.16 - 232.28.15.23 (cloudbr1)

I had trunked KVM Privet NIC to talk to the ACS and NFS subnets. So through 172.16.0.0, I can communicate with the 10.10.40.0 network.

I bring up a VM with isolated network 10.1.1.5 and it creates VR with 10.1.1.1 and 232.28.15.19. I am getting internet, and the rest is fine.
I need to mount NFS server with this VM. While checking the VR route, I can see the default route to the public NIC. Through that NIC, I won't get the 10.10.40.250 system as it passed out from KVM through cloudbr1.

It is not advised to trunk KVM host cloudbr1 NIC and allow 10.10.40.250 traffic to route through the public network. What will be the best solution for this in this case?

##### EXPECTED RESULTS

Most of the production environment ACS will be running on a DC, which will have a NAS or SAN for NFS storage and which will be on some other LAN vlan. I can see an option like configuring VPC and adding site-site VPN. But in most cases, all devices have the same DC, which will affect NFS performance when traffic moves out and in through a VPN. So CloudStack should have some option to add this storage to VMs and Kubernetes clusters.

Commencez par la configuration CloudStack 14.19.1 signalée, notamment la VM isolée, les routes du routeur virtuel, les bridges KVM et le réseau du serveur NFS. Examinez la manière dont le routeur virtuel gère l’accès au réseau 10.10.40.0 et déterminez la configuration prise en charge nécessaire pour l’accès NFS depuis la VM et Kubernetes. Le travail sera considéré comme terminé lorsqu’une solution clairement définie et prise en charge aura été établie, en évitant de faire transiter le trafic NFS par le réseau public.

Rédigé par le modèle d'indexation à partir du texte de l'issue.