Aaron, I thought the l3-agent already did this if doing a "full sync"?
_sync_routers_task()->_process_routers()->spawn_n(self.process_router, ri) So each router gets processed in a greenthread. It seems like the other calls - sudo/rootwrap, /sbin/ip, etc are now the limiting factor, at least on network nodes with large numbers of namespaces. -Brian On 03/13/2014 10:48 AM, Aaron Rosen wrote: > The easiest/quickest thing to do for ice house would probably be to run the > initial sync in parallel like the dhcp-agent does for this exact reason. See: > https://review.openstack.org/#/c/28914/ which did this for thr dhcp-agent. > > Best, > > Aaron > > On Thu, Mar 13, 2014 at 12:18 PM, Miguel Angel Ajo <majop...@redhat.com > <mailto:majop...@redhat.com>> wrote: > > Yuri, could you elaborate your idea in detail? , I'm lost at some > points with your unix domain / token authentication. > > Where does the token come from?, > > Who starts rootwrap the first time? > > If you could write a full interaction sequence, on the etherpad, from > rootwrap daemon start ,to a simple call to system happening, I think > that'd > help my understanding. > > > Here it is: https://etherpad.openstack.org/p/rootwrap-agent > Please take a look. > > -- > > Kind regards, Yuriy. > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org <mailto:OpenStack-dev@lists.openstack.org> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
