After the BRAKERS project ended, I shortly moved into the edX team for 1-2 weeks where I was tasked to work on documenting the installation procedures of the platform. As simple as the task may seem, it was very time consuming in nature as the platform required to be installed 3 times for the installation to actually work. It turns out that everyone else in the team had similar issues when they had to install the platform... My guess would be that the problem was network related, and that somewhere in the installation, the connection drops when trying to download dependencies.

Aside from that, I was also tasked to fix the SSL problem at Seneca's online development edx platform. The problem looked like this:

SSL Error on online-dev edx @ Seneca

This problem only occurred in Firefox, and worked as intended (showing content instead of an SSL warning) in Chrome. By checking the SSL certificate at SSLShopper, I was able to pinpoint the problem: Firefox did not trust the issuer of the certificate, but Chrome did. To fix this, I appended the issuer's certificate to the original certificate and it now works as intended. The issuer's issuer in this case, was trusted by both browsers, thus preventing that warning page from showing.

After that, I was put into my current project: developing a Fault Injection Framework. The purpose of fault injection is to try to find possible failures of a system before those failures can become a problem (i.e., by fixing them before they become a problem). In other words, it is used for finding weaknesses and fixing those weaknesses that are found.

If you've heard of Netflix's Simian Army, we are trying to do something similar; but instead of randomly injecting faults, we are trying to permutate through all possible failure cases to ensure that we have explored (almost) all weaknesses possible in the system we are testing on.

For more information, continue reading the next post.