In a production environment, you would want to separate the hypervisor and storage network to different networks/switches (just for easier management), but in our setup we will use one switch with multiple VLANs to isolate the traffic. This is more a function of cash flow for me as managed switches are usually several hundred dollars
In a production environment, you would want to separate the hypervisor and storage network to different networks/switches (just for easier management), but in our setup we will use one switch with multiple VLANs to isolate the traffic. This is more a function of cash flow for me as managed switches are usually several hundred dollars
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
Posted in Apps, CentOS, Linux, Networking, Tech, Ubuntu, Virtualization
Leave a comment
Wolverine is configured almost identically to Cyclops, the only difference is that it uses bonds (groups of NICs) to communicate instead of individual NICs. This is useful for both load balancing and redundancy. It has the following specs: Dell R510 Server 2 (Wolverine) Primary Purpose: Hypervisor CPU: Dual L5520 Xeon CPUs (quad core) RAM: 32GB DDR3