1. NFS setup in vLab Yunji Zhong

2. Without NFS Each VM is binding to each host machine

3. Without NFS Limitation – Cloud resource can’t be fully used. If the running instances on one host take up all of its CPU or RAM, the rest instances on that host cannot be started. – If one host machine is broken down, all of the VMs on it are unavailable to access.

4. Using NFS All VMs are stored in NFS when they are NOT running.

5. Using NFS When a VM is started, it is copied to a suitable host machine for running. VM will be copied back to NFS when stopped

6. Using NFS Limitation – A wasting of host machine’s hard disk resource – If the NFS is damaged, all the VMs are lost

7. NFS on every host A part of host’s hard disk serves as NFS

8. Limitation of NFS The VM data are frequently transferring between host machines and NFS, so it needs a high network speed to maintain an acceptable performance of vLab. NFS is one of the most vulnerable parts of vLab. If it is attacked, the consequence could be very serious.

9. NFS ISO library The VM could be created based on a operating system’s iso image(Windows, Ubuntu, Fedora, etc). Instead of storing all these images on each single host machine, NFS is a good place to hold them together.