Day Three

These wont continue to be daily posts,

Noticed that the first pi in the http/s line is failing checks once in a while and going down, not a big┬áproblem as the other two are there to pick up the slack, I actually expected this as I have a few services running on the “primary” that are not on the other two.


The primary SQL is the one running on the flash stick, the backups are the spinning HDDs over USB, and they are not fast in any means but they were a means to an end in this project and will eventually be upgraded.


Day Two

athis is the second day with this cluster running, I have downed the other webservers I had running, added a few more web apps, oh and most importantly I have made the entire cluster https enabled.

While I read you can terminate (originate? I digress) the ssl connections on the haproxy box its self I couldn’t get this to work so I used the ssl-passthrough method, i configured letsencrypt on the “primary” webserver and have it distribute the keys to the others.

I have also semi-stress tested it with jmeter, it handles fifty connections just fine and jmeter errors when I try five hundred.

Thats it for now!

Hello from the Pis

As you will see in the about this site, it runs on seven Raspberry Pis:

One Raspberry Pi 2 B acts as a proxy load balancer for both incoming http connections and mysql connections.

Three Raspberry Pi 3B+ equipped with 32GB class 10 Micro SD cards, 32 GB stick as swap (Overkill but on sale) and 128GB stick setup with glusterfs between the three of them mounter at /var/www

Three Raspberry Pi 3 as a Clustered MariaDB server, one runs the same setup as the Pi 3B+’s above, the other two have slower SD cards, smaller swap sticks and Mechanical HDDs. The HDDs and 128GB house the databases. The slower Pis in this lot are setup as backups.