On Mon, May 20, 2024 at 10:47 AM Wei ZHOU <ustcweiz...@gmail.com> wrote:
> What type of zone and network do you use ? > I have tried both edge and core/advanced zones with KVM as hypervisor and OVS switching as the underlying network stack. Now testing with core-advanced zone. I have configured several traffic types and have defined the labels for them. For example the public network is defined at the physical network 1 and has label cloudbr0 as below: [image: image.png] But I am not able to add a vNIC at the guest VM which will be connected at the cloudbr0 interface. Whatever I try all the VM NICs will be connected at the guest network which is cloudbr2. > Try network with vlan = "vlan://untagged" > For some reason all guest networks get a VLAN from the guest VLAN range defined at the initial zone creation. There does not seem to be a way to avoid this. > > > > > > On Friday, May 17, 2024, Alex K <rightkickt...@gmail.com> wrote: > > > Hi All, > > > > Is it possible to create untagged guest networks in cloudstack and have > > them assigned to different OVS bridges? > > > > I have created several OVS bridges at the KVM host and then tried to > attach > > the different VM NICs to the different OVS bridges without any VLAN > > tagging, but it seems that whatever I try there is always VLAN tagging at > > the guest VM interfaces at the VLAN ID range given at the initial zone > > creation. > > > > Also any NIC I add at the VM seems to be mapped only at the single guest > > network. Although I have defined different types of networks (guest, > > management, public) during zone creation, defining also the traffic > labels > > according to the OVS bridge names, there does not seems to be a way to > > attach these different networks to the different OVS bridges through the > > cloudstack UI. My intention is to have the VM connected to different > > networks, with or without VLAN tag. > > > > I am testing now with an edge zone with a KVM server. > > > > Thanks for any input. > > Alex > > >
