Changes between Version 2 and Version 3 of Internal/NewNodeAgent


Ignore:
Timestamp:
Sep 5, 2014, 10:45:20 PM (10 years ago)
Author:
ssugrim
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • Internal/NewNodeAgent

    v2 v3  
    4343Observations:
    4444 * active? is defined at "Ready to be configured". If a device is set to active, it is read to accept config commands.
    45  *
     45 * Activation should check if the module is loaded before loading it.
     46 * All devices will not know their device name during creation (default is nil). All dev_driver classes will be instantiated at startup, however none of them will be activated (with the exception of eth1). When a device need to be used. It will have to be activated. Once activated (that is once the module is loaded) the agent will give names to the respective objects now that they have been created. This is essentially how the logical names are bound to the dev names (a logic managed by the agent, not the dev).