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