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 摘要。