Download Red Hat Enterprise Virtualization 3.3 Technical Reference Guide
Transcript
Chapt er 2 . Red Hat Ent erprise Virt ualiz at ion Archit ect ure A logical network that carries virtual machine network traffic is implemented at the host level as a software bridge device. By default, one logical network is defined during the installation of the Red Hat Enterprise Virtualization Manager: the rhevm Management network. Other logical networks that can be added by an administrator are: a dedicated storage logical network, and a dedicated display logical network. Logical networks that do not carry virtual machine traffic do not have an associated bridge device on hosts. They are associated with host network interfaces directly. Red Hat Enterprise Virtualization 3.3 segregates management-related network traffic from migration-related network traffic. This makes it possible to use a dedicated network (without routing) for live migration, and ensures that the management network (rhevm) does not lose its connection to hypervisors during migrations. Exp lan at io n o f lo g ical n et wo rks o n d if f eren t layers Logical networks have different implications for each layer of the virtualization environment. D at a C en t er Layer Logical networks are defined at the data center level. Each data center has the rhevm management network by default. Further logical networks are optional but recommended. D esignation as a VM Netwo rk and a custom MTU can be set at the data center level. A logical network that is defined for a data center must also be added to the clusters that use the logical network. C lu st er Layer Logical networks are made available from a data center, and must be added to the clusters that will use them. Each cluster is connected to the management network by default. You can optionally add to a cluster logical networks that have been defined for the cluster's parent data center. When a required logical network has been added to a cluster, it must be implemented for each host in the cluster. Optional logical networks can be added to hosts as needed. H o st Layer Virtual machine logical networks are implemented for each host in a cluster as a software bridge device associated with a given network interface. Non-virtual machine logical networks do not have associated bridges, and are associated with host network interfaces directly. Each host has the management network implemented as a bridge using one of its network devices as a result of being included in a Red Hat Enterprise Virtualization environment. Further required logical networks that have been added to a cluster must be associated with network interfaces on each host to become operational for the cluster. Virt u al Mach in e Layer Logical networks can be made available to virtual machines in the same way that a network can be made available to a physical machine. A virtual machine can have its virtual NIC connected to any virtual machine logical network that has been implemented on the host that runs it. The virtual machine then gains connectivity to any other devices or destinations that are available on the logical network it is connected to. Examp le 2.1. Man ag emen t N et wo rk The management logical network, named rhevm, is created automatically when the Red 17