palashbiswas-git opened a new issue, #8270:
URL: https://github.com/apache/cloudstack/issues/8270
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Enhancement Request
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
Private Gateway
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
CloudStack 4.18.0.0
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
##### SUMMARY
<!-- Explain the problem/feature briefly -->
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
<!--
For bugs, show exactly how to reproduce the problem, using a minimal
test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
<!-- Paste example playbooks or commands between quotes below -->
~~~
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
~~~
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
