NetworkInfrastructure » History » Revision 146

« Previous | Revision 146/158 (diff) | Next »
dl lud, 08/04/2020 09:59 AM
Some ops were temporary on the #replicant freedone channel.

Network Infrastructure

What Where Access type Who Comments
Redmine instance OSUOSL Redmine manager * Paul Kocialkowski
* Wolfgang Wiedmeyer
* GNUtoo
* Joonas Kylmälä
* Fil Bergamo
* Kurtis Hanna
* dl lud
* Grim Kriegor
* OSUOSL system administrators
Since we only have one project, OSUOSL put in a redirect from the main page of our Redmine instance to /project/replicant
OSUOSL keeps 2 weeks worth of backups for restoration purposes.
Mailing list Mailing list administrator * Paul Kocialkowski
* Wolfgang Wiedmeyer
* GNUtoo
* Kurtis Hanna
* dl lud
* OSUOSL system administrators
OSUOSL keeps 2 weeks worth of backups for restoration purposes.
Wordpress instance Wordpress administator * Paul Kocialkowski
* Wolfgang Wiedmeyer
* GNUtoo
* Joonas Kylmälä
* Fil Bergamo
* Kurtis Hanna
* dl lud
* OSUOSL system administrators
* Add your name here if you have access and want to be mentioned
This instance is auto-updated automatically with the help of a plugin.
Releases SSH * Paul Kocialkowski
* Wolfgang Wiedmeyer
* GNUtoo
* Joonas Kylmälä
* OSUOSL system administrators
We should not use too much space.
The (mostly-static) front website None: there is an automatic hook managed by OSUOSL. * Source code
* Patches should be sent to the Replicant mailing list.
* There is a jenkins hook with a token to pull and deploy the website source code.
Replicant Source code Virtual machine at FSF SSH root access * Paul Kocialkowski
* GNUtoo
* Joonas Kylmälä
* Several FSF system administrators
* FSF backup server
* FSF Ansible deployment server
Resources kindly offered by the FSF.
The git configuration has some documentation.
Before handling SSH (root) access to this machine:
* Make sure that the person really needs it.
* Make sure that the person already contributed to Replicant.
* Ask one other person that has SSH access and/or the SteeringCommittee to also agree on it.
Private contact address IMAP access * GNUtoo
* Joonas Kylmälä
* Fil Bergamo
* Kurtis Hanna
* dl lud
* Grim Kriegor
You can write to the contact address (all the members of SteeringCommittee receive it) if for some reasons you need to receive it as well.
#replicant IRC channel Freenode Channel operator * Paul Kocialkowski
* GNUtoo
Temporary, op must be given through ChanServ:
* Joonas Kylmälä
* Kurtis Hanna
* dl lud
Quiet mode for unregistered users is disabled for the time being. If SPAM comes back use: /mode #replicant +qe $~a *!*@gateway/web/* and /mode #replicant +qe $~a *!*@gateway/shell/* to re-apply it. These commands whitelist users coming through web based IRC clients and via the IRC bridge.
OFTC Channel operator * Kurtis Hanna
* Jeremy Rand
Bridged with the Freenode channel through the NCBridge bot operated by Jeremy Rand
The domain name * Web inteface through gandi website
* The DNS entries are configured to use gandi's DNS server
* Bradley Kuhn (administrative contact): Can do everything (including designating the technical contact or transferring the domain)
* GNUtoo (technical contact): can do DNS zone changes
* Other people? Paul Kocialkowski?
The TLS certificate Let's Encrypt Access probably by controlling the respective domain name * OSUOSL
* ?
History: CA-cert -> GlobalSign -> LetsEncrypt


The OSUOSL is the Oregon State University Open Source Lab.

  • They can be contacted on #osuosl on the Freenode IRC network
  • They also have a 'support' mail address at

Virtual machine in FSF's infrastructure

  • The virtual machine is hosted in a server that is in their office or in a datacenter.
  • Several FSF network administrator also have access to the virtual machine
  • The 'sysadmin' mail address at
  • The FSF system administrators can also be contacted on #fsfsys on the Freenode IRC network for more urgent matters

Virtual machine specifications

The virtual machine runs on top of Xen and has:
  • About 3G of RAM
  • 1 virtual core
  • a 10G rootfs partition
  • a 100G storage partition for Replicant git repositories
  • One IPv4 and one IPv6
  • Trisquel 8.0
  • The virtual machine may be using FAI and cfengine but it would need more investigation on that.
  • The distribution seem to have the latest security updates applies. How it does it needs to be investigated by looking at cron jobs (it might use FAI for that).

Virtual machine backup policies

The virtual machine is backed up daily. The backup procedure excludes the following path at the time of writing:


git hosting infrastructure on this machine

The source code is in /srv/git/git-data/repositories and is divided in several groups:
  • Replicant source code
  • LineageOS mirror
  • AOSP mirror
  • Various developers repositories
function software documentation comments
authorization gitolite UpstrreamSourceCodeMirrors
read access * git:// -> git daemon
* ssh:// -> ssh daemon
* https:// -> ? (TODO: document the software/configuration)
web cgit Cgit




  • For GDPR related inquiries, you can write to the PrivateContact mail address.


  • Ask the OSUOSL about backup policies.
  • Document public spaces like Freenode IRC channel.
  • Do our own backup policies and do some backups ourselves.
  • Contact the people that have some control of the resources above and ask for permission to mention them here
  • Fill the gaps (mentioned with '?') in this page
  • Look what happens when an account is deleted
  • Fix the related issues in the tracker
  • Move the entries of this TODO list to the tracker when it makes sense

Funding and legal entity

See the SteeringCommittee for more details.

Legal advise

Contact John Sullivan at the FSF.

Note that John Sullivan is not a lawyer but the FSF has lawyers.


The replicant-infrastructure redmine project has a wiki with more documentation in it.

Updated by dl lud almost 4 years ago · 146 revisions

Also available in: PDF HTML TXT