Testing CODE-RADE

In this post, we discuss how we can ensure that products in our application repository are ready to use. In order to know whether the applications that we build in our Jenkins are properly built, we include a test phase between build and deployment. Similarly, the only way to know whether our execution environment will work in the wild is to test it too. CODE-RADE is designed to deliver products to arbitrary endpoints in a non-invasive way. The removal of this restriction on where the applications will actually run may seem like an invitation to uncertainty, but in practice these...…

read more...

Delivering Execution Environments

We’ve shipped a lot of applications in the CODE-RADE CVMFS repository, and the project is getting some nice attention from kindred spirits intent on solving the application delivery problem. It’s time to put a bit more focus on the user experience CODE-RADE runs everywhere One of the main selling points of CODE-RADE is that the applications in it are built for arbitrary environments. This is a big claim ! Design decisions have been made to make this achievable, in particular building large matrices of project configurations, for various sites, processor architectures, operating systems, versions and dependencies. However this is all...…

read more...

Monitoring with prometheus

Modernising regional monitoring. Monitoring and alerting is a key part of keeping a distributed platform operational. This has typically been done by generating a topology for a region using the GOCDB and using Nagios to monitor services at sites. These monitors are linked to operating level agreements that define thresholds; if these thresholds of service state, availability, etc are exceeded, an alert is issued, and site administrators are urged to take action. This is all well and good, but it’s time to experiment with a different monitoring service, Prometheus. This to scratch the following itches : have a closer view...…

read more...

You can test (CODE-RADE) if you want to...

TL;DR - You can test if you want to, you can leave your bugs behind So, you’re working on an application that wants to get included in the CODE-RADE repository, but for some reason, it’s failing in CI. Let’s take the R language for example. This project has a slew of dependencies, some of them optional, such as java, lapack, openblas, pcre2, readline and xz It is going to be needed soon for the CODATA/RDA DataScience School, but the project is currently So, you say “shucks, I can fix that !” and set about preparing your pull request to the...…

read more...