------_=_NextPart_001_01CF0D11.E17769E3 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, I am evaluating oVirt as a replacement/alternative to VMware deployments = we typically do. I have installed and all-in-one setup on a test box = (which itself used to be an ESXi server), but it only has one NIC. I = trying to duplicate our typical configuration we do in VMware, which is = this: 1.) we create several "port groups" on the vSwitch, each assigned a = VLAN ID, such as: - VLAN001 (VLAN ID: 1) - VLAN002 (VLAN ID: 2) - VLAN009 (VLAN ID: 9) - VLAN010 (VLAN ID: 10) - VLAN200 (VLAN ID: 200) - TRUNK (VLAN ID: 4095 - in VMware-world, VLAN ID "4095" is "all = VLANS" and basically just passes the VLANs through to whatever is = attached to the port group for the VM to handle) 2.) We assign VMs to port groups appropriate for the VLAN they are = part of. 3.) The only VM that has a NIC assigned to the "TRUNK" port group is = the firewall (which is Linux), and we create VLAN interfaces on it = (i.e., "eth1.1", "eth1.2", "eth1.10", "eth1.200"). The firewall VM acts = as the router between the various VLANs. To replicate the above in oVirt, I created logical networks for each = VLAN, and assigned the appropriate VLAN ID. It seems oVirt/KVM does not = have an equivalent for VMware's VLAN ID of "4095", so after some = searching around, so for the "TRUNK" network, I left it with no VLAN = assigned. Because i cannot add VLAN and non-VLAN networks to the same = physical NIC, after some searching around, it looks like I may have to = utilise two NICS: one for the VLAN networks and one for the "TRUNK" = network. Because, at this point, I am not yet concerned with making the test VMs = I will be setting up be accessible from outside the virtual lab = environment (i.e., everything will communicate within my oVirt = server/network for now), I am trying to make use of "dummy" interfaces, = but I am not sure the best way to make use of this. I am able to create = the dummy* interfaces and have them show up in oVirt, but I am not sure = of how they should be setup. Here is what I am *thinking* should be = done, but want to make sure it is correct before getting too deep: - I will use the physical NIC for management, therefore the = "ovirtmgmt" bridge with eth0 assigned to it will remain as-is - Create two dummy interfaces: "dummy0" and "dummy1" - Create a new bridge, "ovirtvm" and assign "dummy0" and "dummy1" to = it - Attach the VLAN-enabled networks to "dummy0" - Attach the "TRUNK" network to "dummy1" Would the above be the way to go about this? The one thing I am not = sure of is whether or not having no VLAN assigned (on the "TRUNK" = network) accomplishes the same this as the "VLAN ID 4095" in VMware: = will oVirt/KVM just pass the traffic through for the VM attached to it = to deal with? Thanks for reading this far, and I appreciate any help you might be able = to lend in the above. -Alan ------_=_NextPart_001_01CF0D11.E17769E3 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Diso-8859-1"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 6.5.7654.12"> <TITLE>Networking questions (LONG)</TITLE> </HEAD> <BODY> <!-- Converted from text/plain format --> <P><FONT SIZE=3D2>Hello,<BR> <BR> I am evaluating oVirt as a replacement/alternative to VMware deployments = we typically do. I have installed and all-in-one setup on a test = box (which itself used to be an ESXi server), but it only has one = NIC. I trying to duplicate our typical configuration we do in = VMware, which is this:<BR> <BR> 1.) we create several "port groups" on the vSwitch, = each assigned a VLAN ID, such as:<BR> <BR> - VLAN001 (VLAN ID: 1)<BR> - VLAN002 (VLAN ID: 2)<BR> - VLAN009 (VLAN ID: 9)<BR> - VLAN010 (VLAN ID: 10)<BR> - VLAN200 (VLAN ID: 200)<BR> - TRUNK (VLAN ID: 4095 - in VMware-world, = VLAN ID "4095" is "all VLANS" and basically just = passes the VLANs through to whatever is attached to the port group for = the VM to handle)<BR> <BR> 2.) We assign VMs to port groups appropriate for the VLAN they = are part of.<BR> 3.) The only VM that has a NIC assigned to the "TRUNK" = port group is the firewall (which is Linux), and we create VLAN = interfaces on it (i.e., "eth1.1", "eth1.2", = "eth1.10", "eth1.200"). The firewall VM acts = as the router between the various VLANs.<BR> <BR> To replicate the above in oVirt, I created logical networks for each = VLAN, and assigned the appropriate VLAN ID. It seems oVirt/KVM = does not have an equivalent for VMware's VLAN ID of "4095", so = after some searching around, so for the "TRUNK" network, I = left it with no VLAN assigned. Because i cannot add VLAN and = non-VLAN networks to the same physical NIC, after some searching around, = it looks like I may have to utilise two NICS: one for the VLAN networks = and one for the "TRUNK" network.<BR> <BR> Because, at this point, I am not yet concerned with making the test VMs = I will be setting up be accessible from outside the virtual lab = environment (i.e., everything will communicate within my oVirt = server/network for now), I am trying to make use of "dummy" = interfaces, but I am not sure the best way to make use of this. I = am able to create the dummy* interfaces and have them show up in oVirt, = but I am not sure of how they should be setup. Here is what I am = *thinking* should be done, but want to make sure it is correct before = getting too deep:<BR> <BR> - I will use the physical NIC for management, therefore the = "ovirtmgmt" bridge with eth0 assigned to it will remain = as-is<BR> - Create two dummy interfaces: "dummy0" and = "dummy1"<BR> - Create a new bridge, "ovirtvm" and assign = "dummy0" and "dummy1" to it<BR> - Attach the VLAN-enabled networks to "dummy0"<BR> - Attach the "TRUNK" network to "dummy1"<BR> <BR> Would the above be the way to go about this? The one thing I am = not sure of is whether or not having no VLAN assigned (on the = "TRUNK" network) accomplishes the same this as the "VLAN = ID 4095" in VMware: will oVirt/KVM just pass the traffic through = for the VM attached to it to deal with?<BR> <BR> Thanks for reading this far, and I appreciate any help you might be able = to lend in the above.<BR> <BR> -Alan<BR> </FONT> </P> </BODY> </HTML> ------_=_NextPart_001_01CF0D11.E17769E3--