Repository navigation
Assigning resource pools in different VPC offerings. #8219
Description
Activity
@IgaoWolf , the config key
site2site.vpn.vpngateway.connection.limitis now only global. It would have to be overridable in one of the details tables and the usage of it (in the code) would have to take that into account.
This sounds like an improvement request.@DaanHoogland I also find this interesting; I think it's a good implementation for the community. It will provide more freedom to create different types of offerings or "plans" and also the ability to serve different types of users/clients. It opens up a significant advantage for those who can build an architecture around different VPC plans, separating them into tiers and adding a differential value.
Reacted by Jithin Raju@IgaoWolf @DaanHoogland PR #6918 adds the support for network-scope settings. After it gets merged, we could also consider adding VPC-scope settings to allow overriding settings such as
site2site.vpn.vpngateway.connection.limit,site2site.vpn.service.provider.excludeandsite2site.vpn.customergateway.subnets.limit.Reacted by dahn and Igor Augusto Wolf@IgaoWolf @DaanHoogland PR #6918 adds the support for network-scope settings. After it gets merged, we could also consider adding VPC-scope settings to allow overriding settings such as
site2site.vpn.vpngateway.connection.limit,site2site.vpn.service.provider.excludeandsite2site.vpn.customergateway.subnets.limit.@winterhazel I would agree, but #6918 is not getting much attention at the moment.
@IgaoWolf @DaanHoogland PR #6918 adds the support for network-scope settings. After it gets merged, we could also consider adding VPC-scope settings to allow overriding settings such as
site2site.vpn.vpngateway.connection.limit,site2site.vpn.service.provider.excludeandsite2site.vpn.customergateway.subnets.limit.As I remember, the leaseweb fork has vpc-scope settings, right? @soreana
Is this resolved, can we close the ticket?
16 remaining items
We have decided in the past to not use this feature, so we can't dedicate time to develop it.
Perhaps someone can adopt it and port to the current codebase.
- changed the title
[-]Doubt - Assigning resource pools in different VPC offerings.[/-][+]Assigning resource pools in different VPC offerings.[/+]on Aug 13, 2026
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