Project

General

Profile

Feature #524

Create a concrete _proposal_ on how to use/migrate to git/sparkleshare

Added by Bjoern Michaelsen over 3 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Category:
-
Target version:
-
Start date:
Due date:
% Done:

100%

Estimated time:
Tags:
URL:

Description

A concrete proposal on how to introduce the internal document storage to git with migration milestones and implications, so the board has an concrete idea what we are talking about, and can decide if and when certain milestones should be implemented:

WebDAV and git/sparkleshare (milestone 0 - status quo)

features and misfeatures of milestone 0

  • + accessable to all external users (StB) read-only
  • - for a daily cronjob, 2GB/day/per person of traffic syncing the data alone
  • - no git write access, writing is only possible via WebDAV
  • - no canonical history or revisioning
  • - no data on who changed what
  • - wrong granularity of commits (days)

WebDAV and central git/sparkleshare (milestone 1)

decisions to make

  • where to host the (currently 1.1 GB without the checkout) git repo? options:
    • gerrit:
      • + existing infra
      • + already has ACL support needed to keep the repo readonly
      • + already has ACL support to prevent forging commits
      • - mixing TDF and LibreOffice stuff and hosting private data there. Then again we already have the MC decision there already
    • new repo:
      • + not mixing existing services
      • - needs new host/backup setup etc.
      • - needs new readonly hook etc.

features and misfeatures of milestone 1

  • + still accessable to all external users (StB) read-only
  • + no more 2GB/day/per person syncing traffic
  • + canonical history or revisioning
  • o better granularity of commits (cronjob could run every 10 minutes without horrible traffic)
  • - no git write access, writing is only possible via WebDAV
  • - no data on who changed what

WebDAV and read/write git/sparkleshare (milestone 2)

decisions to make

  • this should be trivial on gerrit with ACLs
  • selfhosting would be more work, because of ACLs
  • needs all writers to the repos to use git or sparkleshare

features and misfeatures of milestone 2

  • + still accessable to all external users (StB) read-only
  • + no more 2GB/day/per person syncing traffic
  • + canonical history or revisioning
  • + correct granularity of commits (no cronjobs)
  • + correct data on who changed what
  • + git write access
  • - WebDAV is read-only

read/write git/sparkleshare only (milestone 3)

  • all access via sparkleshare/git only

decisions to make

  • would this even work for the StB? No partial checkouts with git/sparkleshare

features and misfeatures of milestone 3

  • + no more 2GB/day/per person syncing traffic
  • + canonical history or revisioning
  • + correct granularity of commits (no cronjobs)
  • + correct data on who changed what
  • + git write access
  • + one service less to worry/document about: WebDAV
  • - external users (StB) would need to be trained on sparkleshare, and would get access to the whole repo

Related issues

Has duplicate Infrastructure - Task #624: migrate from WebDAV to SparkleShareIn Progress

History

#1 Updated by Bjoern Michaelsen over 3 years ago

  • Description updated (diff)

Attached a concrete migration proposal with multiple milestones, each step can be decided on individually. Note that e.g. milestone 3 has some current unresolved issues (partial checkout for the StB) that would need to to have a solution before going forward with it, but the previous milestones are widely independant of that

#2 Updated by Bjoern Michaelsen over 3 years ago

  • Description updated (diff)

typos

#3 Updated by Bjoern Michaelsen over 3 years ago

  • Description updated (diff)

formatting

#4 Updated by Bjoern Michaelsen over 3 years ago

  • Description updated (diff)

formatting

#5 Updated by Bjoern Michaelsen over 3 years ago

  • Description updated (diff)
  • Private changed from Yes to No

#6 Updated by Bjoern Michaelsen over 3 years ago

  • Has duplicate Task #624: migrate from WebDAV to SparkleShare added

#7 Updated by Bjoern Michaelsen over 3 years ago

  • % Done changed from 0 to 50

FWIW, I hope this proposal is concrete enough for evaluation.

Florian Effenberger: Feel free to make a separate (follow up) issue for implementing this in production, if you dont want to reuse this one.

#8 Updated by Florian Effenberger over 3 years ago

My bad, didn't spot the other one

#9 Updated by Bjoern Michaelsen about 3 years ago

  • Status changed from New to Resolved
  • % Done changed from 50 to 100

Marking this one as resolved as the proposal is done. Evaluation and implementation at https://redmine.documentfoundation.org/issues/624 then.

#10 Updated by Bjoern Michaelsen about 3 years ago

  • Status changed from Resolved to Closed

eh, resolved is not closed, so now doing the latter.

Also available in: Atom PDF