[clug] Bridging for KVM HOST servers - diagram

[George at Clug]

Hi,

In my previous email, my imagined environment was simplified, the idea would be to have more than one KVM HOST servers for fail-over, redundancy, migration, etc.

I hope the below diagram gives a better idea. If it is not readable, I apologise, it is the best I could think of.  

Notes:
KVMn means to what ever number of KVM hosts are in the environment.
{SWITCH} means various switch ports for connecting to multiple physical devices.

Concept borrowed from https://www.cyberciti.biz/faq/rhel-linux-kvm-virtualization-bridged-networking-with-libvirt/
===Bare Metal KVM HOST Servers KVM1 to KVMn =================================================================

Internet  --> |SWITCH | --> | eth1 |  <=KVM1=> | br1 |       -> KVM VMs connected to Directly the Internet
                   |SWITCH | --> | eth1 |  <=KVM2=> | br1 |       -> KVM VMs connected to Directly the Internet
                   |SWITCH | --> | eth1 |  <=KVMn=> | br1 |       -> KVM VMs connected to Directly the Internet 
                   |{SWITCH}|-->| ports |  <=====> |       |       -> physical servers (some applications require bare metal servers for performance reasons)
                              59.51.2.0/28

DMZ  --> |SWITCH | --> | eth2 |  <=KVM1=> | br2 |       -> KVM VMs connected to DMZ for isolated Internet facing servers (for web and email servers)
              |SWITCH | --> | eth2 |  <=KVM2=> | br2 |       -> KVM VMs connected to DMZ for isolated Internet facing servers (for web and email servers)
              |SWITCH | --> | eth2 |  <=KVMn=> | br2 |       -> KVM VMs connected to DMZ for isolated Internet facing servers (for web and email servers)
              |{SWITCH}|-->| ports |  <=====> |       |       -> physical servers (some applications require bare metal servers for performance reasons)
                               123.1.2.0/24

LAN  -->  |SWITCH | --> | eth3 |  <=KVM1=> | br3 |      ->  KVM VMs connected to the companies internal LAN  (DHCP server, file servers, virtual workstations, etc)
              |SWITCH | --> | eth3 |  <=KVM2=> | br3 |       -> KVM VMs connected to the companies internal LAN  (DHCP server, file servers, virtual workstations, etc)
              |SWITCH | --> | eth3 |  <=KVMn=> | br3 |       -> KVM VMs connected to the companies internal LAN  (DHCP server, file servers, virtual workstations, etc)
              |{SWITCH}|-->| ports |  <=====> |       |       -> physical servers (some applications require bare metal servers for performance reasons)
              |{SWITCH}|-->| ports |  <=====> | PCs |       -> physical workstations connected to the companies internal LAN 
                               123.2.2.0/24

LAN  -->  |SWITCH | --> | eth0 |  <=KVM1=> | br0 |      ->  KVM VMs connected to LAN for SAN/NFS/BACKUP and management network
              |SWITCH | --> | eth0 |  <=KVM2=> | br0 |       -> KVM VMs connected to LAN for SAN/NFS/BACKUP and management network
              |SWITCH | --> | eth0 |  <=KVMn=> | br0 |       -> KVM VMs connected to LAN for SAN/NFS/BACKUP and management network
              |{SWITCH}|-->| NICs |  <=====>  |       |      ->  physical LAN for SAN/NFS/BACKUP and management network
                               10.10.x.y/24
====================================================================

George.