Proposal to Enhance Private Gateway Functionality for Measuring and Billing Usage
- Lenguaje dominante
- Java
- Estrellas
- 3.1k
- Forks
- 1.4k
- Merge medio
- 6 d 19 h
- PR fusionados (30 d)
- 32
Descripción
##### 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
~~~
~~~
Guía de contribución
Línea de trabajo
El issue menciona el componente Private Gateway y tres escenarios de peering, pero no proporciona archivos, comandos, pruebas ni criterios de aceptación. Empieza por documentar cómo registra actualmente CloudStack el tráfico del gateway y la facturación para el peering dentro de la misma zona, el peering entre zonas y el peering externo. La tarea estaría terminada cuando exista un alcance de mejora acordado y datos de uso medibles adecuados para tarifas diferenciadas.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- java
- Área
- cloud, infrastructure
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 25/100