Improve logic for nvp plugin nat rules ordering
Bug #1176947 reported by
Salvatore Orlando
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
Fix Released
|
Low
|
Salvatore Orlando | ||
Bug Description
NAT rule ordering for the nicira plugin is currently trivial. A higher order is assigned to floating IP rules whereas a lower order is assigned to default SNAT rules.
A better logic would leverage the cidr prefix, establishing the rule order as MAX_ORDER - PREFIX_LEN.
In this way, floating IP rules (/32) will still have highest priority.
This will also avoid problems with deployments upgraded from 2.x to 3.x where NAT rules order are rearranged according to this logic.
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to quantum (master) | #1 |
| Changed in quantum: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to quantum (master) | #2 |
| Changed in quantum: | |
| status: | In Progress → Fix Committed |
| Changed in quantum: | |
| status: | Fix Committed → Fix Released |
| Changed in neutron: | |
| milestone: | havana-1 → 2013.2 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/