Proposal to Enhance Private Gateway Functionality for Measuring and Billing Usage
- Langage dominant
- Java
- Étoiles
- 3.1k
- Forks
- 1.4k
- Merge moyen
- 6 j 19 h
- PR mergées (30 j)
- 32
Description
##### 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
~~~
~~~
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
L’issue nomme le composant Private Gateway et trois scénarios de peering, mais ne fournit ni fichiers, ni commandes, ni tests, ni critères d’acceptation. Commencez par recenser la manière dont CloudStack enregistre actuellement le trafic de la gateway et la facturation pour le peering au sein d’une même zone, le peering interzone et le peering externe. La tâche serait terminée lorsqu’un périmètre d’amélioration convenu et des données d’utilisation mesurables, adaptées à des tarifications différenciées, seraient disponibles.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- java
- Domaine
- cloud, infrastructure
- Type d'issue
- Fonctionnalité
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 25/100