Add route whose nexthop not in router's attaching subnets

Registered by Zhiyuan Cai

Currently when we add a route to a router, Neutron will check if the nexthop ip is in one of the routers's attaching subnets. If not, Neutron will raise a BadRequest error. We would like to remove this restriction. An external network may have more than one subnets, but a router can only be associated with one gateway ip. In some scenarios, we would like a vm can communicate with subnets in the external network, which are not associated with the gateway ip. Thus we need to add a route to the router whose nexthop is in these none-gateway-ip-associated subnets. This operation can not be fulfilled currently because these subnets are not attached to the router.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
Zhiyuan Cai
Direction:
Needs approval
Assignee:
Zhiyuan Cai
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Armando Migliaccio

Related branches

Sprints

Whiteboard

Nov-09-2015(armax): If someone is interested in pursuing it, this must be re-submitted according to guidelines defined in [1]

[1] http://docs.openstack.org/developer/neutron/policies/blueprints.html

-----------------

Gerrit topic: https://review.openstack.org/#q,topic:bp/route-nexthop-not-in-router-subnet,n,z

Addressed by: https://review.openstack.org/152768
    Add route whose nexthop not in router's attaching subnets

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.