Feature #17266

Create VM for Gitlab migration work

Added by zen 2019-11-28 18:55:10 . Updated 2019-12-06 20:42:20 .

Status:
Rejected
Priority:
Normal
Assignee:
zen
Category:
Infrastructure
Target version:
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

  • This VM will be used to publish our prototypes to some more people within Tails community.
  • It can be deleted after the project is done (planned May 2020).
  • It is an open question whether Tails will host it’s own Gitlab instance.
  • Requirements:
    • root access to setup a Gitlab (after Gitlab is setup, root access might not be needed).
    • 1 core.
    • 4GB RAM.
    • Rounded up the space of all repos + 10G for the base system.
    • doesn’t need to accessible from the outside any proxy mechanism is fine.

Subtasks

Related issues

Related to Tails - Feature #15878: Switch to GitLab In Progress 2018-08-30
Blocks Tails - Feature #13284: Core work: Sysadmin (Adapt our infrastructure) Confirmed 2017-06-30

History

#1 Updated by intrigeri 2019-11-29 06:26:10

  • blocks Feature #13284: Core work: Sysadmin (Adapt our infrastructure) added

#2 Updated by intrigeri 2019-11-29 06:26:33

#3 Updated by zen 2019-12-06 20:42:20

  • Status changed from Confirmed to Rejected

The VM is not needed, as communicated to sysadmins through the mailing list:

> The outcome from our first sprint, was, that we currently don’t need the VM, as
> Gitlab supports export/import and we can easily push our current state to an
> external Gitlab instance. That’s why I would suggest to not put time into
> creating a VM atm. We may need it in a later process.

I’m closing this for now, feel free to reopen when/if it’s needed.