Task #5017 (closed)
Opened 8 years ago
Closed 7 years ago
RapidService: Staging and unstaging data
| Reported by: | dzmacdonald | Owned by: | dzmacdonald |
|---|---|---|---|
| Priority: | minor | Milestone: | Unscheduled |
| Component: | General | Version: | n.a. |
| Keywords: | n.a. | Cc: | jamoore, jos@…, jburel, jrswedlow |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | 0.0d |
| Sprint: | n.a. |
Description (last modified by dzmacdonald)
The RapidService? needs to be able to convert the data before it is staged and after it is unstaged, depending on the knowledge the script and cluster has about OMERO.
Each of these will rely on a different strategy for transforming the data.
- Cluster and script are both OMERO agnostic.
- Convert the data on OMERO and copy it to the cluster, could be done via OMERO.scripts, or inside Service.
- The Cluster is OMERO aware, the script is OMERO agnostic.
- The script deploys pre and post staging scripts to the cluster as well as the omero agnostic executable. OMERO.fs, or OMERO.fuse are copied to the server and the script sees a user mounted file system, it is unaware of OMERO, the data it requires is transformed on the fly.
- The Cluster and script are OMERO aware.
- The simplest method, the script itself gets the data from OMERO.
Change History (5)
comment:1 Changed 8 years ago by dzmacdonald
- Description modified (diff)
comment:2 Changed 8 years ago by dzmacdonald
- Description modified (diff)
comment:3 Changed 8 years ago by jburel
- Sprint changed from 2011-04-21 (10) to 2011-05-05 (11)
comment:4 Changed 8 years ago by dzmacdonald
- Milestone changed from OMERO-Beta4.3 to Unscheduled
- Sprint 2011-05-05 (11) deleted
comment:5 Changed 7 years ago by jburel
- Remaining Time changed from 2 to 0
- Resolution set to invalid
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Moved from sprint 2011-04-21 (10)