Changes between Version 18 and Version 19 of Network driver development HOWTO

Show
Ignore:
Timestamp:
05/21/10 11:52:32 (9 years ago)
Author:
ibaldin (IP: 152.54.9.131)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Network driver development HOWTO

    v18 v19  
    7676 
    7777=== Tasks === 
    78 Once the interface is implemented, the next step is to implement a set of tasks (a class per task) corresponding to driver actions. A common way to implement them is to define a device-specific base task that is a child of !NetworkBaseTask and subclass further tasks from it (see the orca.handlers.network.tasks.Cisco6509 or orca.handlers.network.tasks.EX3200 [[Image(EX3200Driver.png)]] as an example).  
     78Once the interface is implemented, the next step is to implement a set of tasks (a class per task) corresponding to driver actions. A common way to implement them is to define a device-specific base task that is a child of !NetworkBaseTask and subclass further tasks from it (see the orca.handlers.network.tasks.Cisco6509 or orca.handlers.network.tasks.EX3200  as an example).  
     79 
     80[[Image(EX3200Driver.png)]] 
    7981 
    8082=== Meta-information === 
     83 
     84Once the tasks are implemented, you must create a mapping between Java properties used by Ant handlers and tasks and declare the driver as available. Targets must be created in the test handler to facilitate testing. This is done by editing files: 
     85 
     86$ORCA_SRC/handlers/network/src/main/resources/orca/handlers/network/network.properties - driver declaration 
     87 
     88$ORCA_SRC/handlers/network/src/main/resources/orca/handlers/network/network.tasks - Java properties to task classname mapping 
     89 
     90$ORCA_SRC/handlers/network/test.xml - test handler where targets need to be added for each declared task and properties can be passed in as parameters to tasks 
    8191 
    8292=== Unit tests ===