Custom Query (87 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1 - 3 of 87)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#112 fixed irods path not correct in production JS for new projects johren@bbn.com johren@bbn.com
Description

I did some testing with a new project today and noticed that the irods path used when I dumped data to iRODS is incorrect. It does not include the project in the path.

Divya helped me dig into a little more and we saw that the irods_path is not correct in Job Service. It should be geni-joTestNew/new01

johren-joTest081101-2014-08-11T21-22-13:
uuid: d71444c5-a763-41f3-8123-62dc41d8d33b
href: http://gimi4.casa.umass.edu:8002/jobs/d71444c5-a763-41f3-8123-62dc41d8d33b
name: johren-joTest081101-2014-08-11T21-22-13
type: job
status: finished
oml_db: postgres://oml2:omlisgoodforyou@128.119.44.12/johren-joTest081101-2014-08-11T21-22-13
irods_path: new01
username: johren
log_file: http://gimi4.casa.umass.edu:8002/logs/d71444c5-a763-41f3-8123-62dc41d8d33b.log

GES seems to have the correct path:

{
type: "project",
uuid: "812aeaf1-8676-4c2c-8226-5dedc8cee997",
href: "/projects/812aeaf1-8676-4c2c-8226-5dedc8cee997",
name: "joTestNew",
path: "geni-joTestNew/",
irods_user: "geni-johren1",
users: [ ],
experiments: [
{
uuid: "2c67ef56-773b-4bff-8222-fc30d4e19c99",
href: "/experiments/2c67ef56-773b-4bff-8222-fc30d4e19c99",
name: "new01",
type: "experiment",
path: "geni-joTestNew/new01/"
},
{
uuid: "4dd03846-7f85-4751-9d86-8e57e715e2ce",
href: "/experiments/4dd03846-7f85-4751-9d86-8e57e715e2ce",
name: "newABC",
type: "experiment",
path: "geni-joTestNew/newABC/"
}
]
}

#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
#102 fixed Automatically append Slice Name to Host name - Move to Production divyashri.bhat@gmail.com dbhat@bbn.com
Description

This ticket relates to:

http://groups.geni.net/gimi/ticket/98

Some initial testing has been done on Dev instance for this fix.
This change will be moved to production.

1 2 3 4 5 6 7 8 9 10 11
Note: See TracQuery for help on using queries.