CAcert System Admins discussion list

[Jan Dittberner <jandd AT cacert.org>]

Dear CAcert board,

after long and careful preparation I finished the setup of a new board
voting system a few minutes ago.

The new system is available at https://motion.cacert.org/ data from the old
system has been carried over to the new system. I setup redirects from the
old system (https://community.cacert.org/board/) to the new one to make sure
that the links to motions from the wiki and potential other places keep
working.

Details
-------

The new motion system has been implemented from scratch in Go and is much
faster than the old PHP based system. The source code for the application is
available in Git [1].

The new motion system [2] is setup via Puppet and has no unmanaged
configuration, which is my goal for all future/upgraded systems for the
future. I setup an incoming proxy system [3] that forwards TLS traffic to
motion but could be used for other systems in the future. The idea is to be
able to share a public IP address for services on several backend systems
without losing the ability to use client certificate authentication. The
Puppet code for the new motion system as well as the proxy system are
available in the cacert-puppet git repository [4].

Wytze setup DNS entries for the new system yesterday morning and with the
URL redirects in place the system is usable now.


[1] https://git.cacert.org/gitweb/?p=cacert-boardvoting.git;a=summary
[2] https://infradocs.cacert.org/systems/motion.html
[3] https://infradocs.cacert.org/systems/proxyin.html
[4] https://git.cacert.org/gitweb/?p=cacert-puppet.git;a=summary


Kind regards
Jan

-- 
Jan Dittberner - CAcert Infrastructure Team Lead
Software Architect, Debian Developer
GPG-key: 4096R/0xA73E0055558FB8DD 2009-05-10
         B2FF 1D95 CE8F 7A22 DF4C  F09B A73E 0055 558F B8DD
https://jan.dittberner.info/

Attachment: smime.p7s
Description: S/MIME cryptographic signature