github-actions[bot] commented on issue #11983: URL: https://github.com/apache/cloudstack/issues/11983#issuecomment-4856144982
## ๐ฏ Triage report The reporter wants to use VXLAN for the management and secondary storage traffic types, but CloudStack currently does not expose a way to assign a VXLAN broadcast domain to these traffic types via the zone setup wizard or the "Edit traffic type" UI. Maintainer feedback in comments confirms VXLAN on the management network is not officially supported today; the feature only works for guest networks. Several community members clarified that the typical workaround is to configure the VXLAN interface at the host OS level and point CloudStack to a standard bridge (`cloudbr1`) without teaching CloudStack about the underlying VNI. ### ๐ Assessment | Dimension | Value | Reasoning | |---|---|---| | **Type** | type:new-feature | VXLAN support for management/storage traffic types is not currently implemented | | **Component** | component:networking, component:vxlan | Network traffic type configuration; VXLAN isolation method | | **Severity** | n/a | Not a code defect; unsupported feature | | **Labels** | type:new-feature, component:networking, component:vxlan | As above | | **Coding agent** | Not suitable | Requires design decisions on supported topology, traffic type isolation model, and zone setup wizard changes | <details><summary>๐ก Notes and suggestions</summary> - Current workaround (confirmed by community): configure the VXLAN VNI/bridge (`vxlan.XXX` โ `cloudbr1`) at the host OS level; CloudStack only sees `cloudbr1` and uses `(untagged/redacted) for management. This is a supported operational pattern even if not visible in the UI. - Management IPs in the Pod are only used by System VMs (on KVM/XenServer); Virtual Routers use them as Control IP on VMware only. - Related discussion: https://github.com/apache/cloudstack/discussions/10694 โ `@rohityadavcloud` noted VXLAN is guest-only in the current implementation. - Implementation would require changes to zone wizard, traffic type DAO, and agent network configuration logic for KVM. </details> > Generated by [Daily Issue Triage](https://github.com/apache/cloudstack/actions/runs/28523943189) ยท [โท](https://github.com/search?q=repo%3Aapache%2Fcloudstack+%22gh-aw-workflow-call-id%3A+apache%2Fcloudstack%2Fdaily-issue-triage%22&type=issues) > <details> <summary>Add this agentic workflows to your repo</summary> To install this agentic workflow, run ``` gh aw add githubnext/agentics/workflows/daily-issue-triage.md@d7c1dc4b72b00607a67caaffdcc216cb64379cf9 ``` </details> <!-- gh-aw-agentic-workflow: Daily Issue Triage, engine: copilot, version: 1.0.52, model: claude-sonnet-4.6, id: 28523943189, workflow_id: daily-issue-triage, run: https://github.com/apache/cloudstack/actions/runs/28523943189 --> <!-- gh-aw-workflow-call-id: apache/cloudstack/daily-issue-triage --> -- 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]
