Comment 9 for bug 1817881

Hi Liu,

I was thinking about this proposal once again. And I'm still not convinced if we should do it in L3 agent.
As we all know, we have metering agent and service plugin already - this service plugin provides API - https://docs.openstack.org/api-ref/network/v2/?#metering-labels-and-rules-metering-labels-metering-label-rules - now You are proposing to add new API and new implementation for same thing basically. I'm affraid that from user perspective it may not be the best solution to provide 2 different APIs to the same thing basically.
Maybe You could simply propose another driver (based on tc counters) for metering agent: https://github.com/openstack/neutron/tree/master/neutron/services/metering/drivers ? That way change would be smaller IMO and there would be no new API for the same thing.