On Wed, Nov 21, 2007 at 10:25:26PM +0000, Alan Maguire wrote: > Renee Danson wrote: > > > >> It depends on how do we want to define the states for these instances. > >> If we define online like: > >> online: the object (datalink or interface) was initialized and is > >> being managed by the active policy engine. > >> > > > > I agree with this definition. > > > > > one complication though for this approach is that the > policy engine then cannot assume the existence of the > underlying object, e.g. network/physical:default can't > then assume that the interfaces associated with the > IP interface instances are yet plumbed. in fact the > start methods for the IP interface instances won't > run until the policy engine has completed or > daemonized, so getting this to work will involve > some changes to network/physical:default i think.
My assumption had been that all of the per-interface loops in network/physical:default's current start script would move out into the start method for the ip instances. But that start script does do some things that assume that all the interfaces are plumbed: it initializes link properties, check /etc/defaultrouter and set default routes as needed, and a few other odds-and- ends. This is a problem no matter how we organize the dependencies, I think; how do we know that "all" the interfaces are up? -renee
