Open Stack

Hi All,

Is the extra route extension always tied to the router extension or 
can it live in a separate route-table container. If extra-route routes 
are available in separate container then sharing of such
containers across networks is possible.

Another reason to remove the dependency would be to have
next hops that are not CIDRs. Next-hops should be allowed as
interface or a VM instance such as NAT instance. This would
make the extra route extension more generic. 

This way an extra-route container can be attached/bound to
either a router extension or to a network as well. Many plugins
do not need a separate router entity for most of the inter-network
routing.

Thanks,
Rudra