Infrastructure code for
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Quentin e2bb0e1b4e Fix tab again 4 days ago
app Fix sogo conf to match RAM usage 4 days ago
op_guide Fix tab again 4 days ago
os Add LX key3 1 week ago
.gitignore Rework jitsi-xmpp to support cert gen 8 months ago
.gitmodules Refactor 2 2 months ago
LICENSE Initial commit 1 year ago Add plume 2 months ago

Many things are still missing here, including a proper documentation. Please stay nice, it is a volunter project. Feel free to open pull/merge requests to improve it. Thanks.

Our abstraction stack

We try to build a generic abstraction stack between our different resources (CPU, RAM, disk, etc.) and our services (Chat, Storage, etc.):

  • ansible (physical node conf)
  • nomad (schedule containers)
  • consul (distributed key value store / lock / service discovery)
  • garage/glusterfs (file storage)
  • stolon + postgresql (distributed relational database)
  • docker (container tool)
  • bottin (LDAP server, auth)

Some services we provide:

  • Chat (Matrix/Riot)
  • Email (Postfix/Dovecot/Sogo)
  • Storage (Seafile)

As a generic abstraction is provided, deploying new services should be easy.

I am lost, how this repo works?

To ease the development, we make the choice of a fully integrated environment

  1. os the base os for the cluster
    1. build: where you will build our OS image based on Debian that you will install on your server
    2. config: our Ansible recipes to configure and update your freshly installed server
  2. apps apps we deploy on the cluster
    1. build: our Docker files to build immutable images of our applications
    2. integration: Our Docker compose files to test locally how our built images interact together
    3. config: Files containing application configurations to be deployed on Consul Key Value Store
    4. deployment: Files containing application definitions to be deployed on Nomad Scheduler
  3. op_guide: Guides to explain you operations you can do cluster wide (like configuring postgres)

Start hacking

Clone the repository

git clone
git submodule init
git submodule update

Deploying/Updating new services is done from your machine

The following instructions are provided for ops that already have access to the servers.

Deploy Nomad on your machine:

export NOMAD_VER=0.9.1
unzip nomad_${NOMAD_VER}
sudo mv nomad /usr/local/bin
rm nomad_${NOMAD_VER}

Deploy Consul on your machine:

export CONSUL_VER=1.5.1
unzip consul_${CONSUL_VER}
sudo mv consul /usr/local/bin
rm consul_${CONSUL_VER}

Create an alias (and put it in your .bashrc) to bind APIs on your machine:

alias bind_df="ssh \
  -p110 \
  -N \
  -L 4646: \
  -L 8500: \
  -L \
  -L \
  <a server from the cluster>"

and run: