github-actions[bot] commented on issue #14372:
URL: https://github.com/apache/cloudstack/issues/14372#issuecomment-6084170720
## ๐ฏ Triage report
This is a feature request to make the per-VPC tier (network) limit
configurable at the domain/account level instead of only as the global setting
`vpc.max.networks`, and to improve the generic/uninformative API error returned
when the limit is hit.
### ๐ Assessment
| Dimension | Value | Reasoning |
|---|---|---|
| **Type** | type:new-feature | Requests new configurability
(per-domain/account limit) plus an improved error message, not a fix to
existing broken behavior. |
| **Component** | component:vpc, component:networking | Directly relates to
VPC tier/network creation limits (`VpcManagerImpl`, `vpc.max.networks`). |
| **Severity** | n/a | Not a bug, so severity does not apply. |
| **Labels** | type:new-feature, component:vpc, component:networking | See
above. |
| **Coding agent** | Needs more info | The error-message improvement
(propagate `CloudRuntimeException` message instead of generic "Internal error
executing command") is fairly self-contained and could be tackled by an agent.
However, making the VPC tier limit per-domain/account configurable is a larger
design change (new setting scope, API params, UI, docs) requiring
maintainer/architecture input before implementation. |
### ๐ Similar issues
No similar open issues were found in a search for related terms
(`vpc.max.networks`, VPC tier limit).
<details><summary>๐ก Notes and suggestions</summary>
- Two distinct asks are bundled here; maintainers may want to split them:
1. **Configurability**: Promote `vpc.max.networks` from a global-only
setting to one overridable per domain/account, similar to how VPC count limits
already work (`max.account.vpcs` style per-domain/account overrides).
2. **Error UX**: The API currently surfaces a generic `Request failed
(530): Internal error executing command` to the caller while the real cause
(`CloudRuntimeException: Number of networks per VPC cannot surpass [3]`) is
only visible in management server logs. This should be a quick win โ propagate
the specific exception message to the API response, similar to other
resource-limit checks in `VpcManagerImpl`.
- Relevant code: `VpcManagerImpl` (network/tier creation path) and the
`vpc.max.networks` global config definition.
- Suggest confirming with the reporter whether they need both items or
primarily the error-message fix, which is lower risk and could be a good first
contribution.
</details>
> Generated by [Daily Issue
Triage](https://github.com/apache/cloudstack/actions/runs/37938129624) ยท
sonnet50 71.3K ยท
[โท](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-5, id: 37938129624, workflow_id:
daily-issue-triage, run:
https://github.com/apache/cloudstack/actions/runs/37938129624 -->
<!-- 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]
