github-actions[bot] commented on issue #14712: URL: https://github.com/apache/cloudstack/issues/14712#issuecomment-6980113032
> [!WARNING] > threat detection engine error > The threat detection engine encountered an error and could not complete analysis. This is a tooling failure, not a security finding. > > <!-- gh-aw-threat-engine-error --> > > <details> > <summary>What happened</summary> > > The threat detection engine failed to produce results. > > Review the [workflow run logs](https://github.com/apache/cloudstack/actions/runs/44314035050) for details. > > </details> ## ๐ฏ Triage report A request for bridge-level port isolation (`<port isolated='yes'/>`) on guest VLANs for KVM hosts that use linux bridge, as a PVLAN-like alternative to OVS. The proposal covers domain XML round-tripping, a per-host agent property listing isolated VLANs, and refusing to start when libvirt is too old. The author says the current workaround (a groovy agent hook) is unreliable. ### ๐ Assessment | Dimension | Value | Reasoning | | --- | --- | --- | | **Type** | type:new-feature | New isolation capability on linux bridge; no defect reported | | **Component** | component:kvm, component:networking | Changes in the KVM agent's domain XML and `BridgeVifDriver`; guest VLAN networking | | **Severity** | n/a | Not a bug report | | **Labels** | type:new-feature, component:kvm, component:networking | Based only on the issue text | | **Coding agent** | Not suitable | Open design questions: per-host vs per-network configuration, and whether the existing PVLAN setting should drive it | ### ๐ Similar issues - #13521 (related) โ mentioned by the author as possibly related to KVM PVLAN support; not checked by this triage - #14518 (related) โ KVM SystemVM networking on a shared VLAN with security groups - #13759 (related) โ packet capture on KVM instance NICs; same NIC/domain-XML area <details> <summary>๐ก Notes and suggestions</summary> - The author has an AI-generated patch on a fork and offers to open a PR. Maintainers should review the design before code is accepted. - Decide whether isolation should be per host (agent property) or per network (driven by the network's PVLAN setting). The author says the XML parsing change is needed either way. - The proposal says isolation between hosts still depends on the uplink switch, so the documentation should state this limit. </details> > Triage by Copilot (automated) > Generated by [Daily Issue Triage](https://github.com/apache/cloudstack/actions/runs/44314035050) ยท copilot ยท haiku55 ยท \~4 AIC ยท โ 3.8K ยท [โท](https://github.com/search?q=repo%3Aapache%2Fcloudstack+%22gh-aw-workflow-call-id%3A+apache%2Fcloudstack%2Fdaily-issue-triage%22&type=issues) <details> <summary><sub>Add this agentic workflow to your repo</sub></summary> To install this agentic workflow, run ``` gh aw add githubnext/agentics/workflows/daily-issue-triage.md@139fa09ef17cde4135e696ff8e7af09bc5ddfa6e ``` </details> <!-- gh-aw-workflow-call-id: apache/cloudstack/daily-issue-triage --> <!-- gh-aw-agentic-workflow: Daily Issue Triage, engine: copilot, model: claude-haiku-5.5, id: 44314035050, workflow_id: daily-issue-triage, run: https://github.com/apache/cloudstack/actions/runs/44314035050 --> <!-- gh-aw-execution: {"version":1,"repo_id":"9759448","repository":"apache/cloudstack","aw_workflow_id":"daily-issue-triage","run_id":"44314035050","run_attempt":"1","run_url":"https://github.com/apache/cloudstack/actions/runs/44314035050","publishing_job":{"key":"safe_outputs","check_run_id":"134838345283"}} --> -- 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]
