OMF

We need to re-design the driver support in EC/RC to allow more flexibility in the control of devices on the resource.

Main idea is around the addition of a defDriver and addDriver constructs to OEDL.

defDriver( uri , name ) do |d|

  d.category 'net'     # or could be 'usb',etc.. 
  d.prefix 'w'         # prefix for the logical name in OEDL, ie. w0, or 'u',etc...

  d.class = 'XZY'      # this is the class implementing the driver, to be 'required' on the RC side,
                       # we could make this optional, and derive a default class to load based on 
                       # defined driver name above, e.g. 'MadwifiDriver'

  d.require = 'PATH'   # this is where the class defined above is located, again this is could be made 
                       # optional, and a default path can be derived, eg. 'omf_driver/madwifiDriver.rb'

  d.addOption( 'version', some_default, {:required => false, etc...} )
  d.addOption( 'map', {:dev1 => 'ath0', :dev2 => 'ath1'}, {:required => false, etc...} )
  etc...  

  d.addAction( 'ip' , {:type => String, :other_options => ABC} )
  d.addAction( 'other_action' , {:type => Integer, :other_options => ABC} )
  etc...

  # all valid action for this driver need to be listed here, along with their options
  # the EC will use this information to check the validity of a configuration action before
  # sending the corresponding command to the RC.
end

# Then later in the OEDL script we use:

defGroup("actor", "omf.nicta.node1") do |node|

  node.addDriver( 'MadwifiDriver', {:version => XYZ, :other_option => ABC} )

end

Attached are the notes taken during the design meeting with Max on 07/05/10