Opened 10 years ago

Last modified 10 years ago

#109 new enhancement

defApplication Template/API for packaged OML apps

Reported by: dbhat@bbn.com Owned by: Thierry.Rakotoarivelo@nicta.com.au
Priority: major Milestone: GEC21
Component: OMF Version: Backlog
Keywords: Cc:
Dependencies:

Description

For using packaged OML Applications, currently the OEDL script contains:

defApplication('ping') do |app|
  app.description = 'Simple Definition for the ping-oml2 application'
  app.binary_path = '/usr/bin/ping-oml2'
  app.defProperty('target', 'Address to ping', '', {:type => :string})
  app.defProperty('count', 'Number of times to ping', '-c', {:type => :integer})
  app.defMeasurement('ping') do |m|
    m.defMetric('dest_addr',:string)
    m.defMetric('ttl',:uint32)
    m.defMetric('rtt',:double)
    m.defMetric('rtt_unit',:string)
  end
end

Could this be replaced with a library or API call such as:

loadOEDL('system:///omf_ec/ping.oedl') # or require 'oml_app_wrapper' 

defGroup('Source1', property.source1) do |node|
  node.addApplication("ping") do |app|
    app.setProperty('target', property.sinkaddr12)
    app.setProperty('count', 30)
    #app.setProperty('interval', 1)
    app.measure('ping', :samples => 1)
  end
end

Will it be easier to integrate loadOEDL for this instead?

Change History (1)

comment:1 Changed 10 years ago by johren@bbn.com

Milestone: GEC21
Note: See TracTickets for help on using tickets.