Hi, just a quick reminder: unless you got strong network authentication and absolute control over the LAN it's a bad advice to trust some random IP address. In today's networking world I would advice to not trust any LAN resource without strong authentication mechanisms. Am 11.03.2014 18:23, schrieb Prakash Surya: > Is > the best option to just limit access to these NFS exports to the IP > addresses of the hypervisor nodes (and maybe the engine)? -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

On Tue, 11 Mar 2014 10:23:19 -0700 Prakash Surya <surya1(a)llnl.gov&gt; wrote: > Hi, > > All the documentation I've seen states that the oVirt NFS storage should > use the "all_squash,anonuid=36,anongid=36" options. Obviously this isn't > secure, so I'm curious how others have locked down their NFS storage? Is > the best option to just limit access to these NFS exports to the IP > addresses of the hypervisor nodes (and maybe the engine)? Is there a > better way to go about this? Run vlans and have some active monitoring for physical ports up|down states etc... If you cannot control your environment then ask yourself if you trust your infrastructure provider at all. You can run kerberized NFS etc... but what about kerberos security? The beginning is trust towards your infrastructure.

j.