Where should 'sdata' in my home directory on pfeifer be pointing to?

[firasm]

currently it points to:

sdata -> /export/data/sdata/
hdata -> /export/data/hdata/
bdata -> /export/data/brukerdata/

Is this correct? I don't think so because those folders aren't ownCloud synced...

p.s. I also cannot access /mnt/disk/ownCloud from my user without sudo.

Fortunately this is a one-time fix that we shouldn't have to touch again

[DrSAR]

I am still experimenting with the setup but here is my proposed solution:

• Our software (sarpy) should expect sdata to live below ~/sdata. To achieve this there needs to be a symlink pointing to the location on the machine where the data really resides.
• From pfeifer, there are two options to get the data:
  • via owncloud. If that is so, then sdata will be residing inside your owncloud directory and your ~/sdata link should be pointing into the ~/owncloud/SARlab directory (amend for your situation). This also puts the onus on you to figure out which parts of sdata to sync and which parts to unsync. We might have to amend this if future use shows that people get unexpected amounts of data dumped on their discs. This is the preferred method for intermittently connected system (e.g. my laptop, but this requires forethough before you disappear behind the far side of the moon.)
  • via NFS. This should all work if you NFS-import pfeifer:/mnt/disk/owncloud-data/stefan/files/SARlab/sdata and for brukerdata: pfeifer:/mnt/disk/owncloud-data/stefan/files/SARlab/bdata. This is the preferred method if you have connection method that's reliable enough over the time of your python session (no need to mirror data locally, everything ever acquire/saved is accessible - as it says on the NFS tin)

There is a slight update issue in that NFS-written data might take some time to become visible for owncloud users. Please monitor to see if this becomes a problem. The solution above does not address what to do for a user local to pfeifer. I do not want a single user to use an owncloud client since that leads to data duplication.

Currently the owncloud data is being owned by user www-data. The remote push from the scanner should also send paravision scan data as user www-data

(This is how I spend a fun Fri afternoon)

[firasm]

That's all very comprehensive and nice... except my situation precisely falls in the corner case excluded from your beautiful description:

The solution above does not address what to do for a user local to pfeifer. I do not want a single user to use an owncloud client since that leads to data duplication.

[firasm]

Since the ipython notebooks are all stored and run on pfeifer, my user will need direct access to sdata/adata/hdata

[firasm]

things are working fine so i'll close this issue...