Comment 10 for bug 1716913

Reviewed: https://review.openstack.org/561668
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=a01780203b259dc4218e31261333123b60833a03
Submitter: Zuul
Branch: stable/ocata

commit a01780203b259dc4218e31261333123b60833a03
Author: leegy <email address hidden>
Date: Sun Oct 29 05:35:55 2017 +0000

    Fix meter-label-rule creation

    The existing method is to meter outgoing traffic from the entire VM
    to a specific "remote_ip_addr"(in case of outbound),
    but the method I suggested can meter outgoing traffic
    from a particular subnet to external network.

    From a metering point of view,
    it does not matter which address/CIDR is the destination for outbound.
    But, it is important to know where(subnet or VM) the packet leaves from.
    That way you can see how much VMs are using the external network.
    For outbound metering, dst is 0.0.0.0/0 and src is network of VMs
    and for inbound metering, src is 0.0.0.0/0 and dst is network of VMs.

    When creating a meter-label-rule, it is correct
    to specify src address for "remote_ip_prefix" option for outbound
    and specify dst address for inbound.
    If you are confused by the term "remote_ip_prefix",
    you need to clarify this option.

    Change-Id: Ia3f3e26410a73d7b44abae637703fda41c4bc09a
    Closes-Bug: #1716913
    (cherry picked from commit 92db1d4a2c49b1f675b6a9552a8cc5a417973b64)