Proposal to Enhance Private Gateway Functionality for Measuring and Billing Usage

##### 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 コンポーネントと 3 つの peering シナリオが挙げられていますが、ファイル、コマンド、テスト、受け入れ条件は示されていません。まず、CloudStack が現在、同一ゾーン内の peering、ゾーン間の peering、外部 peering について、ゲートウェイのトラフィックと課金をどのように記録しているかを整理してください。完了とするには、合意された機能拡張の範囲と、差別化された料金設定に適した測定可能な使用量の出力が必要です。

索引モデルが issue の本文から書いたものです。