[RFE][L3] add ability to control router SNAT more granularly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
In Progress
|
Wishlist
|
LIU Yulong |
Bug Description
Neutron router now supports SNAT when the attribute ``enable_snat`` of the gateway is set to True.
This will enable all the VMs which has no binding floating IP to access the public world.
But, generally the DataCenter bandwidths for cloud providers are not free. And some users may want to buy a higher
SNAT bandwidth for one of their VMs, a CIDR, or a subnet.
So for Neutron, it should support these scenarios:
1. enable/disable SNAT once for all (supported, controlled by ``enable_snat``)
2. enable/disable SNAT for one internal IP (of VM)
3. enable/disable SNAT for a range CIDR of IPs
4. enable/disable SNAT for a subnet
For 2., 3. and 4. scenario should have QoS support.
So I would like to add a new mechanism for Neutron to support these:
1. An new API extension to add specific SNAT type
2. An new L3 agent extension to install SNAT iptables rules.
Ideas?
tags: | added: l3-dvr-backlog rfe |
Changed in neutron: | |
importance: | Undecided → Wishlist |
tags: |
added: rfe-approved removed: rfe-triaged |
Changed in neutron: | |
status: | New → In Progress |
Spec work: /review. opendev. org/c/openstack /neutron- specs/+ /770540
https:/