Collect the traffic metrics out/in public/external network
Billing based on data transferred "in" to and "out" is very important for any cloud service provider[1]. Currently, Ceilometer can only collect the in/out data on a VM network interface. However, it's not very useful from the billing perspective. This bp is aim to collect the metric of in/out public network in Ceilometer for the billing purpose.
P.S. Meanwhile, another blueprint maybe created(if necessary) in Neutron to track the work in that part.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Feilong Wang
- Direction:
- Needs approval
- Assignee:
- Feilong Wang
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- gordon chung
Related branches
Related bugs
Sprints
Whiteboard
Fei, can you please elaborate on why is not very useful to collect in/out data from a VM network interface from a billing perspective?
inactive -- gordc (10.07.15)
gordc, Collecting IN/OUT data from the VM network interface will capture all the traffic generated by the VM, including between VMs inside the same subnet. A cloud provider bills its users by the north-south traffic generated by the VM, not east-west
The new neutron L3 bandwith meters try to address this issue. However, if ceilometer could natively collect that data without any configuration required it would be much more convenient.
diogogmt (12.07.15)
