rhtyd opened a new pull request #3037: kvm: when untagged vxlan is used, use the default guest/public bridge URL: https://github.com/apache/cloudstack/pull/3037 When vxlan://untagged is used for public (or guest) network, use the default public/guest bridge device same as how vlan://untagged works.  Note: currently its possible to use vlan://untagged in the public IP address range for a zone with `vxlan` isolation, which will trick cloudstack-agent (bridge driver) to think the vif/nic to plug is of vlan type and allows `untagged` plugging into the default public/guest bridge device (by default cloudbr0/br1). ## Types of changes <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] New feature (non-breaking change which adds functionality) - [x] Bug fix (non-breaking change which fixes an issue) - [ ] Enhancement (improves an existing feature and functionality) - [ ] Cleanup (Code refactoring and cleanup, that may add test cases) ## How Has This Been Tested? Deploy a KVM advance zone with VXLAN isolation for guest+management+public physical nics/network and pass vxlan://untagged for the public address/range. Agent logs will have exceptions on incorrect `untagged` vnet ID passed error.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
