Custom Query (87 matches)

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

• A project group will be created in iRODS for every project in the GENI Portal.
• This will allow us to manage access to iRODS data by project membership rather than having the data accessible only by a single experimenter.
• Add the project lead to the group when the project is created.

• 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)