Hi Melanie, actually no need to have a separate "Physical Network", unless i.e. you decide to use VXLAN or some SDN technology for network/tenant isolation for Guest traffic. Reason for that is since isolation method (vlan/vxlan/etc.) is set per Physical network and affects all Traffic types in it - but i.e. VXLAN is only supported with Guest traffic - so you end up having 2 Physical networks, one with Mgmt/Public/Storage traffic, using VLAN for isolation, while the other Physical Network is using VXLAN and you only have Guest traffic on it.
I would assume it makes zero sense to change anything with XenServer now and I support ditching it for KVM (my personal attitude...) After you have prepared all the bridges/OpenVSwitches, just edit each of the 4 Traffic types, to set "KVM Traffic Lable" to have the value as the name of bridge / OpenvSwitch that will carry your traffic. Later add you cluster etc... One question though, why are you aiming to use OVS for KVM? i.e. why not regular/default Linux bridge? Cheers On Thu, 15 Aug 2019 at 10:00, Melanie Desaive <[email protected]> wrote: > Hi Andrija, > > Am Mittwoch, den 14.08.2019, 17:57 +0200 schrieb Andrija Panic: > > > a) I assume you are planning on staying on single "Physical network" > > in ACS? > > Yes. But actually I do have to admit, that I am not aware, how more > than one "Physical Network" could be set up for one zone and what that > would mean. > > > b) are you planning on reconfiguring your XenServer hosts at all (in > > sense > > of networking) or just thinking adding KVM hosts and defining proper > > KMV > > Traffic Label for each traffic type you have? > > Would it be possible to reconfigure the XenServer Host network labels > without taking all XenServer clusters down? > > Anyway. I do not plan to reconfigure those. But I do think, that in > case the KVM hosts do their job nicely, it is very likely, that we will > completely replace the XenServer infrastructure by KVM in the future. > > > Makes sense to have all 4 traffic types targeting different Traffic > > Labels > > (networks/bridges) - since later you can change your underlying > > NICs/cabling infra to stick in more NICs as you suggested. > > I assume zero difference on switch port configuration - VLAN is a > > VLAN, > > whatever bridge/openvSwitch you use on hosts locally. > > Good to hear your opinion. That gives me courage to look into it more > thoroughly and give it a try. ;) > > > This would an interesting exercise anyway... > > If you like, I keep you informed! > > Cheers, > > Melanie > -- > -- > Heinlein Support GmbH > Schwedter Str. 8/9b, 10119 Berlin > > https://www.heinlein-support.de > > Tel: 030 / 40 50 51 - 62 > Fax: 030 / 40 50 51 - 19 > > Amtsgericht Berlin-Charlottenburg - HRB 93818 B > Geschäftsführer: Peer Heinlein - Sitz: Berlin > -- Andrija Panić
