Project

General

Profile

Enhancement #456

Reorganize data spaces

Added by Marc Dequènes almost 4 years ago. Updated about 1 year ago.

Status:
Rejected
Priority:
Low
Assignee:
-
Category:
System :: Base
Start date:
2015-07-07
Due date:
% Done:

0%

Patch Available:
Confirmed:
No
Branch:
Entity:
DuckCorp
Security:
Help Needed:

Description

In the past, data spaces were split to separate services and avoid spreading security problems or configuration mistakes from one service to another. This doesn't necessary lead to real security as sometimes we had to bind-mount spaces inside other spaces in order to allow a legitimate use of multiple protocol to access data. This also lead to available space fragmentation, and we don't have TB of disks.

So we need to rationalize our storage. My first guess would be to split by privacy level:
  • user strictly private data, mostly /home, accessible only with very high security protocols (SSH without passwd)
  • user sharable private data, like data stored in OC
  • user public data, like data on the public FTP
    We should then be able to raise data quota as spaces are less fragmented. Each level would have its own separate quota.

We should also rationalize the access protocols to remove obsolete or unused methods if possible, or perhaps add a brand new wonderful service.

History

#1 Updated by Marc Dequènes almost 4 years ago

  • Category changed from 89 to System :: Base

#2 Updated by Marc Dequènes about 2 years ago

I wonder if could not remove support for FTP.

#3 Updated by Marc Dequènes about 1 year ago

  • Status changed from New to Rejected

Well, I'm not sure about this anymore. We've done some regorg along the way and working on obsolete services led to simplifications and less protocols already.

Also available in: Atom PDF