Custom Query (87 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (79 - 81 of 87)

Ticket Resolution Summary Owner Reporter
#86 fixed New requirements for iRODS and git repositories jack.hong@nicta.com.au johren@bbn.com
Description

Currently, the Labwiki scripts are being stored and accessed in git repositories on emmy9. This was done for at least two reasons:

  1. The ODBC issues in iRODS (now resolved)
  2. Performance of listing scripts stored in iRODS

One of the problems with using the git repositories on emmy9 is that users do not have access to their scripts other than through Labwiki. If they want to save them off, they have to cut and paste them from Labwiki.

One of the advantages of using git is that the scripts can be versioned. However, this is not a real benefit current because the users do not have direct access to the git repository.

A few options were discussed at the 4/15 meeting. This ticket will be used to track the discussions of these requirements to solve these problems.

Option 1: possibly rsync git repository on emmy9 to iRODS

  • this will not really give versioning benefit

Option 2: dump script and config parameters to iRODS at the same time as dumping the data

  • this keeps the scripts archived with the data
  • still does not provide versioning

Jack agreed to take a look at effort required for Option #2.

#90 fixed 404 error if GENI Portal user is not activated johren@bbn.com johren@bbn.com
Description

I tried logging into Labwiki with a brand new test account that had not yet been activated. When I do this, I get the following error:

Not Found

The requested URL /secure/openid/kmactivate.php was not found on this server.

It is not immediately obvious that the problem is that the user hasn't activated their accounte yet. Is there a way that we can handle this condition and pop up a page that directs the user to log into the portal to activate their account?

#91 fixed fields in Execute pane are ignored jack.hong@nicta.com.au johren@bbn.com
Description

When I try to run the step1_threenode.rb experiment, it has properties for the three sources that default to nodeX-sample10.

defProperty('source1', "nodea-sample10", "ID of a resource") defProperty('source2', "nodeb-sample10", "ID of a resource") defProperty('source3', "nodec-sample10", "ID of a resource")

When I drag this script over to the Execute pane and change source1, source2, and source3 to nodea-joLabwiki70, nodeb-joLabwiki70, and nodec-joLabwiki70. However, when I start the experiment, I see that it is still using "sample10" rather than "joLabwiki70".

This is happening on gimi1.casa.umass.edu.

I tried it on emmy9 and this does not happen there.

Note: See TracQuery for help on using queries.