There are two widely used network file systems for virtual machines: iSCSI and NFS. As far as which is better you will find various flame wars throughout the web akin to Ford vs. Chevy. For small environments like ours they server the same purpose. One can make the argument that some network switches are optimized
Posted in Apps, CentOS, Linux, Networking, Tech, Ubuntu, Virtualization
Leave a comment
One of the pitfalls with using Windows as a workstation (which I need to as my wife uses the same machine – we consolidated into one machine) is that you cannot run virt-manager to handle your virtual machines. Additionally, the ESXi VMWare client only runs natively on Windows, so you must have at least one
This is essentially the schema of what we are trying to do. Since we are running this in our house (or a dedicated WAN possibly at an office), I had a need to separate the server production subnet (at least in my nomenclature) vs the end-users (such as my wife and kids). I could have
The primary storage server (don’t want to call what I have as a SAN really as it’s just one server, not a filer with added modules) and has the following specs: Dell R510 Server 1 (Phoenix) Primary Purpose: Storage CPU: Single E5520 Xeon CPU (quad core) RAM: 8GB DDR3 ECC Registered First RAIDset: Two 160GB
As much as I wish I could use Dell R510 servers for everything, sometimes you have to use what you have available. In reality, you can use much weaker hardware when creating a home lab, as it is the learning of how everything works together that is the primary purpose, not how fast everything runs