NetworkInfrastructure¶

What	Where	Access type	Who	comments
Redmine instance	OSUOSL	Redmine administrator	Several Replicant contributors including: * Paul Kocialkowski * GNUtoo * Joonas Kylmälä * Add your name here if you have access and want to be mentioned
Mailing list	OSLOSL	Mailing list administrator	Several Replicant contributors including: * Paul Kocialkowski * GNUtoo * Add your name here if you have access and want to be mentioned
Wordpress instance	OSUOSL	Wordpress administator	Several Replicant contributors including: * Paul Kocialkowski * GNUtoo * 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	OSUOSL	SSH?/SFTP	Several Replicant contributors: * Paul Kocialkowski * GNUtoo * Add your name here if you have access and want to be mentioned	We should not use too much space
Source code	FSF	SSH in a vm in a server that is at the FSF office	Several Replicant contributors: * Paul Kocialkowski * Joonas Kylmälä * GNUtoo * Several FSF system administrators * Add your name here if you have access and want to be mentioned	Resources kindly offered by the FSF
Private contact address	This is handled by Paul Kocialkowski's mail servers: * armstrong.paulk.fr * gagarine.paulk.fr	SSH, physical access	Paul Kocialkowski only (it's his machines)	The contact address is redirected to several Replicant contributors including: * Paul Kocialkowski * GNUtoo * Add your name here if you receive mail from this address and want to be mentioned
IRC channel	Freenode	Channel operator(s)	Several Replicant contributors including: * GNUtoo * Paul Kocialkowski * Kurtis Hanna * Add your name here if you have access and want to be mentioned	MODE #Replicant +qe $~a *!*@gateway/web/* and MODE #Replicant +qe $~a *!*@gateway/shell/matrix.org/* have been applied. Unless one connects via a web based irc client or via the Matrix.org IRC bridge one will need to register one's nick with Freenode in order to speak
The replicant.us (mostly-static) front website	OSUOSL (hook) + FSF for the source code	* See the source code hosting line above. * Probably none for the hook	See the source code hosting line above.	* Source code * Patches are to be sent to the Replicant mailing list * There is a jenkins hook with a token to pull and deploy the website source code
The replicant.us domain name	gandi.net	* Web inteface through gandi website * The DNS entries are configured to use gandi's DNS server	Several Replicant contributors including: * Paul Kocialkowski * Add your name here if you have access and want to be mentioned
The replicant.us TLS certificate	Let's Encrypt	Access probably by controlling the respective domain name	* https://www.replicant.us: OSUOSL * https://blog.replicant.us: OSUOSL * https://redmine.replicant.us: OSUOSL * https://git.replicant.us: ?	History: CA-cert -> GlobalSign -> LetsEncrypt

OSUOSL¶

The OSUOSL is the Oregon State University Open Source Lab.

Contact:

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

Virtual machine in FSF's office¶

• The virtual machine is hosted in a server that is in their office.
• Several FSF network administrator also have access to the virtual machine

Virtual machine specifications
The virtual machine has:

• About 3G of RAM
• 1 virtual core
• a 10G rootfs partition
• a 100G storage partition for Replicant git repositories

Virtual machine backup policies

• The virtual machine is backed up about once per day. The backup procedure excludes the following path at the time of writing:
  

  /dev
  /proc
  /tmp
  /sys
  /run
  /mnt
  /mnt0
  /mnt1
  /mnt2
  /mnt3
  /mnt4
  /mnt5
  /mnt6
  /mnt7
  /mnt8
  /mnt9
  /floppy/
  /cdrom/
  /media/
  /net/
  /var/spool/squid/
  /var/spool/squid3/
  /var/spool/squid3_bak/
  /var/spool/squid-tbd/
  /var/spool/squid*/
  /var/spool/django/
  /var/spool/exim/
  /var/cache/
  /srv/chroot/
  /t
  /srv/to-tape
  /var/lib/ceph/osd/
  /var/lib/apt/lists/
  /var/cache/apt/
  

Gandi¶

• See https://en.wikipedia.org/wiki/Gandi for more details

Freenode¶

TODO:¶

• 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