apache / apache/cloudstack

Assigning resource pools in different VPC offerings.

未关闭
#8,219 12 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
component:advanced-networking component:api component:networking component:orchestration component:vpc good-first-issue status:stale type:question
主要语言
Java
星标
3.1k
派生
1.4k
平均合并
6 天 19 小时
30 天内合并 PR
32

描述

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.

Screenshot 2023-11-10 at 11 51 25

So, I would like to check if it is possible to not use the global settings for this format.

![Screenshot_2023-09-08_at_09 11 06](https://github.com/apache/cloudstack/assets/81160709/a1349071-1b78-4a6e-b878-a3059060af9a)

Site2site.vpn.vpngateway.connection.limit

贡献指南

打开贡献指南

调研方向

首先追踪全局设置 `site2site.vpn.vpngateway.connection.limit` 和 VPC offering 配置。将当前的全局行为与所请求的按 offering 设置的 VPN 限制进行比较,并检查现有评论中是否有已达成一致的方案。完成的标准是明确确定是否支持按 offering 设置限制;如果不支持,则定义实现范围。

由索引模型根据 Issue 内容生成。

评估

领域
cloud, infrastructure, networking
Issue 类型
功能
难度
5/5
预计耗时
一周以上
活跃度
冷清
描述清晰度
需要澄清
新手友好度
25/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。