Thanks for the ideas - we actually are trying to put the DSpace
installations on AWS, and the files on the university network. As far as I
understand the only way to mount the assetstore in this situation is with
something like sshfs. It didn't seem to take very well - what I did was
mount /dspace/assetstore to the sshfs connection, and the site wasn't
working properly (e.g., site not coming up). I may try it again, though, to
see if I had configured something wrong or if it's more related to just
slow connection/overhead.
--Charlene
On Mon, Dec 9, 2013 at 8:58 AM, helix84 <[email protected]> wrote:
> On Wed, Dec 4, 2013 at 11:54 PM, Charlene Chinda Barina <[email protected]>
> wrote:
> > Hi, per what I understand about bitstream storage, the two options are a
> > local directory and via SRB (or iRODS, if I want to go an unsupported
> > route). Is that a correct understanding?
>
> Hi Charlene,
>
> that is correct, those are the two ways DSpace recognizes and
> supports. However, by local storage we mean *anything* that can be
> represented as a local filesystem path (i.e. mounts in unix-like
> systems and whatever the Windows equivalent is - drive mapping, hard
> links, DFS?). So if you already have a NAS or a server at your
> institution that exports directories, you can simply mount them at
> OS-level and point DSpace assetstore to the mounted directory. DSpace
> will work happily with it and won't care where it resides. Same goes
> for mostly anything else you can think of, like SMB/CIFS shares - they
> can be mounted locally and completely transparently to DSpace. The one
> thing I'd recommend against is sshfs as Peter suggested - while this
> is simply another protocol that can be used to mount remote
> directories, I'm pretty sure don't want the overhead of encryption to
> transfer files within your institution. If you had a SAN with iSCSI
> targets that you want to use, you'd connect to it from your DSpace
> system as a local block device, create a filesystem on it and mount it
> within your regular directory structure. From there it's the same
> local FS story again.
>
>
> Regards,
> ~~helix84
>
> Compulsory reading: DSpace Mailing List Etiquette
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>
--
Charlene Barina, MPH
Research Analyst 2, U.S. IMPACT Study
The Information School
303-359-6347 | Skype: cbarina
facebook.com/ImpactSurvey | twitter.com/impactsurvey
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
