CERN feature list

[labkode]

This issue is to track all functionalities that are or will be implemented in the Reva master branch for CERNBox use-cases.
This is issue acts as a master issue, please follow individual issues for more details:

• Project spaces: CERN: Project Spaces #2964
• Universal path-based URLs: CERN: Universal path-based URLs #2965
• Lightweight accounts: CERN: Lightweight accounts support #2966
• Deny of ACLS: CERN: Deny of ACLS #2967
• User-defined notifications: CERN: User defined notifications #2971
• File-based search: CERN: File search #2970
• Single file sharing: CERN: Single file sharing #2969
• Integration with applications: CERN: Integration with applications #2968
• Synchronisation of shares from the desktop client in a different namespace (not inside user homedirectory): CERN: Synchronisation of shares from the desktop sync client #2972

Performance:
OCIS suffers from performance penalties when using a network filsystem (example in #2881). The main reason lies into how the owncloud filesystem implementation is done: it assumes a fast local filesystem access and AND exclusive access to the underlying filesystem (users are not allowed to touch the filesystem directly). These two design decissions are voided in CERNBox because we rely a network filesystem (latency applies) and we allow users to access the filesystem direclty.

To help ownCloud to optimise this aspect we suggest two approaches:

• 1. Analyse the systemcalls regarding IO in the OCIS decomposedFS and reduce them as much as possible. Each IO call will inevitably become a network round trip on networked filesystems: IO patterns in OCIS decomposed FS #2976
• 2. We can provide a containerised enviroment to mimic our CERNBox setup (including EOS, OCIS Web and Reva).

[labkode]

From mail thread:

#2964: Obviously working in edge. Your specific input what is not up to your mark is required.
#2965: Done, we merged https://github.com/owncloud/web/pull/7053
#2966: Not in scope for oC as it is a CERN only feature. Would work automatically after merge if it works in master (I assume).
#2967: Discussed before, not in scope for GA. And even your presentation reveals open questions that we can not consider solved, right? Or are the concerns mentioned in the presentation resolved in master? How is that handled in oCweb?
#2971: Not in scope for oC for GA, as communicated before
#2970: Working in edge
#2969: Working in edge
#2968: Working in edge
#2972: WIP