Open Stack

Dear list,

We are trying to implement tenant bandwidth metering at the neutron router 
level. Since some of the network spaces connected to the external interface of 
the neutron router are supposed to be unmetered, we need to match on the 
remote address.

Conveniently, there exists a --remote-ip-prefix option on meter label create; 
however, since [1], its meaning was changed to the exact opposite: Instead of 
matching on the *remote* prefix (towards the external interface), it matches 
on the *local* prefix (towards the OS tenant network).

In an ideal world, we would want to revert that change and instead introduce a 
--local-ip-prefix option which covers that use-case. I suppose this is not a 
thing we *should* do though, given that this change made it into a few 
releases already.

Instead, we’ll have to create a new option (which whatever name) + associated 
database schema + iptables rule patterns to implement the feature.

The questions associated with this are now:

- Does this make absolutely no sense to anyone?
- What is the process for this? I suppose since this change was made 
intentionally and passed review, our desired change needs to go through a 
feature request process (blueprints maybe?).

kind regards,
Jonas Schäfer

   [1]: https://opendev.org/openstack/neutron/commit/
92db1d4a2c49b1f675b6a9552a8cc5a417973b64


-- 
Jonas Schäfer
DevOps Engineer

Cloud&Heat Technologies GmbH
Königsbrücker Straße 96 | 01099 Dresden
+49 351 479 367 37
jonas.schaefer at cloudandheat.com | www.cloudandheat.com

New Service:
Managed Kubernetes designed for AI & ML
https://managed-kubernetes.cloudandheat.com/

Commercial Register: District Court Dresden
Register Number: HRB 30549
VAT ID No.: DE281093504
Managing Director: Nicolas Röhrs
Authorized signatory: Dr. Marius Feldmann
Authorized signatory: Kristina Rübenkamp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20200707/293bd378/attachment.sig>