Proposal to Enhance Private Gateway Functionality for Measuring and Billing Usage
- Linguagem predominante
- Java
- Estrelas
- 3.1k
- Forks
- 1.4k
- Merge médio
- 6d 19h
- PRs com merge (30d)
- 32
Descrição
##### 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
~~~
~~~
Guia de contribuição
Direção de pesquisa
A issue nomeia o componente Private Gateway e três cenários de peering, mas não fornece arquivos, comandos, testes nem critérios de aceitação. Comece mapeando como o CloudStack atualmente registra o tráfego do gateway e o faturamento para peering na mesma zona, peering entre zonas e peering externo. O trabalho estará concluído quando houver um escopo de aprimoramento acordado e dados de uso mensuráveis adequados para tarifas diferenciadas.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- java
- Domínio
- cloud, infrastructure
- Tipo de issue
- Funcionalidade
- Dificuldade
- 5/5
- Tempo estimado
- Mais de uma semana
- Status de atividade
- Estagnada
- Clareza
- Precisa de esclarecimento
- Facilidade para iniciantes
- 25/100