Feature: KVM: port isolation for guest VLANs on linux bridge (PVLAN-like isolation without OVS)

未关闭
#14,712 0 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
java, linux

调研方向

Start by tracing InterfaceDef and the domain XML parser, then inspect BridgeVifDriver and the agent configuration that controls KVM networking. The issue describes the desired behavior and limitations, but leaves open whether isolation should be configured per host or through the network’s PVLAN setting. Done means user VM NICs on configured tagged VLANs are isolated, system VM NICs remain non-isolated, and the agent handles unsupported libvirt versions.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
Java
星标
3.1k
派生
1.4k
平均合并
7 天 4 小时
30 天内合并 PR
13

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

apache/cloudstack 的其他 Issue

查看 apache/cloudstack 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。