Custom Query (87 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (4 - 6 of 87)

1 2 3 4 5 6 7 8 9 10 11 12
Ticket Resolution Summary Owner Reporter
#48 fixed Add/remove experimenter to/from project group when added/removed to/from the project tmitchel@bbn.com johren@bbn.com
Description
  • The experimenter's iRODS user must be added to the iRODS project group when the experimenter is added to a project.
  • The experimenter's iRODS user must be removed from the iRODS project group when the experimenter is removed from a project.
  • The experimenter's iRODS user must be added to all projects of which he/she is a member when his/her account is first created via the GENI Portal.
  • Use new resource in iRODS REST interface (see http://groups.geni.net/gimi/ticket/46)
#55 fixed Pass project and slice information to Labwiki in OpenID data tmitchel@bbn.com johren@bbn.com
Description

Labwiki needs to know the slices and projects for the authenticated user in order to set the context. This information needs to come from the GENI Portal via OpenID data.

#105 fixed List of Properties in OEDL Thierry.Rakotoarivelo@nicta.com.au dbhat@bbn.com
Description

Currently we have experiments where we run the same application per group with a variation of just one Property, for e.g,

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

In the above example, it is only the target address which changes for each application. Could we have a construct similar to:

a) setProperty as a list and have the parser iterate through the list to run the application

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

b) Allow defProperty to take list of properties as an as an input and have the addApplication iterate through the list. For e.g.,

defProperty('sinkaddrs', '192.168.1.7', '192.168.1.8','192.168.1.13', '192.168.1.14', '192.168.1.15', "Ping destination address")

defGroup('Source1', property.source1) do |node|
  node.addApplication("ping") do |app|
     app.setProperty('count', 30)
     app.addProperty('target', property.sinkaddrs) do |prop|
        app.setProperty(prop)    
     end
     app.measure('ping', :samples => 1)
  end
end
1 2 3 4 5 6 7 8 9 10 11 12
Note: See TracQuery for help on using queries.