Assigning resource pools in different VPC offerings.
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 1.4k
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 32
Description
Hello community, how are you?
I have a project that I would like to implement, but I am having trouble designing it within CloudStack. I imagine there are ways to work around this situation, so let's get straight to the point:
I created 3 different offerings for VPC, in which I would like to limit the site-to-site VPNs to a significant quantity among them. For example, VPC 1 - enabled for 2 site-to-site VPNs, and the others would have different limited quantities.
So, I would like to check if it is possible to not use the global settings for this format.
Site2site.vpn.vpngateway.connection.limit
Contributor guide
Research direction
Start by tracing the global setting `site2site.vpn.vpngateway.connection.limit` and the VPC offering configuration. Compare the current global behavior with the requested per-offering VPN limits and review the existing comments for any agreed approach. Done would require a clear determination of whether per-offering limits are supported and, if not, a defined implementation scope.
Written by the indexing model from the issue text.
Assessment
- Domain
- cloud, infrastructure, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100