durdin85 opened a new issue, #14712:
URL: https://github.com/apache/cloudstack/issues/14712

   ### The required feature described as a wish
   
   As having KVM hosts with linux bridge, I would like VMs on selected shared 
guest VLANs to be unable to reach each other, while still reaching the gateway 
and the virtual router.
   
   Use case: advanced zone without security groups, plus a shared subnet where 
tenants must not talk to each other. PVLAN is the natural fit, but on KVM it is 
only implemented for OVS (the #13521 might be related).
   On linux bridge there is no supported way to get this.
   
   Today we work around it with a groovy agent hook that adds `<port 
isolated='yes'/>` to the NIC. 
   But that proven to be unreliable:
   
   - the hook only runs on VM start, so NIC hot-plug, replug and live NIC 
updates might
     produce non-isolated ports;
   - a failing hook is skipped and the VM starts without isolation;
   - the hook also isolates the virtual router's NIC.
   
   ### Proposal
   
   Use the kernel's bridge port isolation, which libvirt exposes as
   `<port isolated='yes'/>`:
   
   1. `InterfaceDef` can emit the element, and the domain XML parser reads it 
back,
      so NIC definitions rebuilt from a running domain keep it.
   2. A new agent property, `network.bridge.port.isolation.vlans`, lists the 
guest
      VLANs to isolate. An entry is a VLAN ID, or `label:vlan` to match only the
      physical network with that KVM traffic label, e.g. `cloudbr1:100,200`.
   3. `BridgeVifDriver` plugs user VM guest NICs on those VLANs as isolated 
ports.
      System VM NICs stay non-isolated.
   4. The agent refuses to start if the property is set and libvirt is too old.
   
   Isolation between hosts still relies on the uplink switch (e.g. PVLAN there).
   
   ### Limitations / open questions
   
   - Configuration is per host, not per network. Would maintainers prefer this 
to
     be driven by the network's existing PVLAN setting instead? Part 1 above is
     needed either way.
   - Only isolated/promiscuous semantics; community PVLANs cannot be expressed.
   - Tagged VLAN guest networks only (no untagged, no VXLAN).
   
   I have a working patch proposal (AI generated -- 
https://github.com/durdin85/cloudstack/tree/kvm-bridge-port-isolation ) and can 
open a PR if needed, but it would be good to have some human control over this.
   Thank you.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

  • [I] Feature: KVM: port isolat... durdin85 (via GitHub) via commits

Reply via email to