Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #5634 (closed)

Opened 13 years ago

Closed 11 years ago

FS-based Silo implementation

Reported by: jamoore Owned by: jamoore
Priority: minor Milestone: Unscheduled
Component: General Version: n.a.
Keywords: n.a. Cc: hic@…, cblackburn
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: 0.0d
Sprint: n.a.

Description

One possible implementation to follow-on #5633 could be referred to as a "silo as repository" implementation.

  • In order to keep all files from being accessed directly via RawFileStore (or similar), the files could be physically separated from all other OMERO binary resources by being within an OmeroFs repository, optionally started as a different user (i.e. not the "omero" user).
  • The repository would take the role of the "OMERO.silo" OriginalFile from #5633, storing configuration and similar details in whatever manner the implementation chose most appropriate.
  • The repository could provide views of the filesystem to users based on their privileges. Administrators could see the actual, original data files, as well the raw HDF5 files and interact with, possibly adding new ones to kick of import. Non-admin users may or may not be able to see the data and/or HDF5 files. But any access of those views, would be audited as if via the silo API.

Change History (10)

comment:1 Changed 13 years ago by jmoore

  • Cc hic@… added; szwells jrswedlow removed
  • Milestone changed from Unscheduled to OMERO-Beta4.3.2
  • Remaining Time set to 2
  • Sprint set to 2011-08-04 (2)

In order to start work on the new sub-silo functionality (#6320), it may make sense to move the client-side python SiloApi object (#5633) server-side. This would use the existing FS API and servants where possible, but keep an eye on the #909 FS re-work for possible commonalities (if necessary the silo branch (team/silo) can be rebased on top of the #909 branch (team/features/909-Proposal2).

Moving into 4.3.2 in order to evaluate the server-side work.

comment:2 Changed 13 years ago by ajpatterson

  • Owner set to jmoore

comment:3 Changed 13 years ago by cxallan

  • Sprint changed from 2011-08-04 (2) to 2011-08-18 (3)

Moved from sprint 2011-08-04 (2)

comment:4 Changed 13 years ago by jburel

  • Sprint changed from 2011-08-18 (3) to 2011-09-01 (4)

Moved from sprint 2011-08-18 (3)

comment:5 Changed 13 years ago by jburel

  • Sprint changed from 2011-09-01 (4) to 2011-09-15 (5)

Moved from sprint 2011-09-01 (4)

comment:6 Changed 13 years ago by jburel

  • Sprint changed from 2011-09-15 (5) to 2011-09-29 (6)

Moved from sprint 2011-09-15 (5)

comment:7 Changed 13 years ago by jburel

  • Milestone changed from OMERO-Beta4.3.2 to OME-5.0
  • Sprint 2011-09-29 (6) deleted

comment:8 Changed 12 years ago by jmoore

Referencing ticket #4652 has changed sprint.

comment:9 Changed 12 years ago by jmoore

  • Milestone changed from OMERO-Beta4.4 to Unscheduled

Moving to "Unscheduled" as 4.4.0 release approaches.

comment:10 Changed 11 years ago by jamoore

  • Remaining Time changed from 2 to 0
  • Resolution set to invalid
  • Status changed from new to closed

Closing all specific HIC tasks.

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.67987 sec.)

We're Hiring!