I reckon it is a sort of "convenience" route which allows us to connect directly to private instances running in the network namespace from the devstack host without having to use floating ips.
It is something which probably makes sense for dev scenarios only as FIXED_RANGE is generally not publicly routable, so I doubt it will have any use in production environments. Finally, it would be technically possible for neutron to add such route for every subnet on the host where the l3 agent is running but I don't see this as something pertaining to neutron. I would simply create a local script that wrap neutron subnet-create: neutron subnet-create $network_id $cidr sudo route add -net $cidr gw $router_gw_ip Salvatore On 30 September 2014 07:54, Xu Han Peng <pengxu...@gmail.com> wrote: > Hi, > > Can anyone help elaborate why the following line of code in devstack which > is trying to add a route for VM private network via router gateway IP on > network node is *NOT* taken care by neutron but devstack? The reason to > ask is that every time a router external gateway IP changed or a new router > is added, we have to manually change this route or add a new one on network > node. > > sudo route add -net $FIXED_RANGE gw $ROUTER_GW_IP > > > https://github.com/openstack-dev/devstack/blob/stable/icehouse/lib/neutron#L428 > > Thanks! > Xu Han > > _______________________________________________ > OpenStack-dev mailing list > OpenStackfirstname.lastname@example.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
_______________________________________________ OpenStack-dev mailing list OpenStackemail@example.com http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev