apache / apache/cloudstack

Proposal to Enhance Private Gateway Functionality for Measuring and Billing Usage

未關閉
#8,270 5 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
archive component:networking component:usage-server component:vpc type:enhancement
主要語言
Java
星號
3.1k
分支
1.4k
平均合併
6 天 19 小時
30 天內合併 PR
32

描述

##### ISSUE TYPE

* Enhancement Request

##### COMPONENT NAME

~~~
Private Gateway
~~~

##### CLOUDSTACK VERSION

~~~
CloudStack 4.18.0.0
~~~

##### CONFIGURATION

##### OS / ENVIRONMENT

##### SUMMARY

Hello Community,

I'd like to address an observation regarding Private Gateway functionality that presents a challenge in billing and measuring end-user usage. Currently, while it's feasible to connect VPCs or other networks, there exists a notable gap in quantifying and billing the usage for end users.

There are two key scenarios where this limitation is evident:

1. VPC to VPC Peering within the same zone (No Charges)
- Network traffic travels through fiber cables within the zone.

2. VPC to VPC Peering not within the same zone (Charges Apply)
- Network traffic travels via Private Lines managed by the Cloud Operator.
- Multiple VPCs from different tenants utilize these Private Lines.

3. VPC to External Networks Peering (Charges Apply)
- Clients may deploy their devices in the data center.

To address this issue, I believe it's crucial to enhance the system's capability to measure Private Gateway usage accurately. This enhancement would enable the application of different tariffs for billing purposes, allowing for a more transparent and fair billing process for all users involved. I intend to raise this concern on Github and propose enhancements to facilitate these measurements and billing functionalities.

##### STEPS TO REPRODUCE

~~~

~~~

##### EXPECTED RESULTS

~~~

~~~

##### ACTUAL RESULTS

~~~

~~~

貢獻指南

開啟貢獻指南

研究方向

該 issue 提到了 Private Gateway 元件和三種 peering 情境,但沒有提供檔案、指令、測試或驗收標準。首先整理 CloudStack 目前如何記錄相同區域內 peering、跨區域 peering 和外部 peering 的閘道流量及計費。完成的要求是確定一個經過同意的增強範圍,並產出適用於差異化費率的可量測使用量資料。

由索引模型根據 Issue 內容生成。

評估

技術堆疊
java
領域
cloud, infrastructure
Issue 類型
功能
難度
5/5
預估耗時
一週以上
活躍度
停滯
描述清晰度
需要釐清
新手友好度
25/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。