Gitlab migration plan


#1

Bonjour,

Here are the steps to follow after gitlab-host is up to migrate the current lab.securedrop.club.

Before provisionning gitlab-host

  • ssh -p 2222 ubuntu@lab.securedrop.club :thumbsup:

  • sudo docker stop gitlab :thumbsup:

  • sudo docker stop gitlab-postgresql :thumbsup:

  • copy all credentials from ~/bootstrap into host_vars/gitlab-host.yml :thumbsup:

  • molecule create -s preprod # add gitlab-host

  • update lab.securedrop.club to be a CNAME of gitlab-host in molecule/bind/bind-playbook.yml :thumbsup:

  • ssh -A debian@IP of the new gitlab :thumbsup:

  • sudo docker stop gitlab :thumbsup:

  • sudo mv /opt/gitlab /opt/gitlabl.old :thumbsup:

  • RSYNC_RSH=‘ssh -p 2222’ rsync --progress -avS root@lab.securedrop.club:/opt/gitlab/ /opt/gitlab/ :thumbsup:

  • sudo docker stop gitlab-postgresql :thumbsup:

  • sudo mv /opt/postgresql /opt/postgresql.old :thumbsup:

  • RSYNC_RSH=‘ssh -p 2222’ rsync --progress -avS root@lab.securedrop.club:/opt/postgresql/ /opt/postgresql/ :thumbsup:

  • sudo chown -R 101 /opt/postgresql :thumbsup:

Run the ansible playbook again at ansible.securedrop.club

  • ansible-playbook --private-key infrastructure_key … molecule/gitlab/gitlab-playbook.yml :thumbsup:
  • verify it works as expected :thumbsup:

Weblate maintenance
#2

switched weblate in read-only mode so it does not use gitlab anymore


#3

migration is over, weblate back to read/write