A few months back, I was tasked with integrating the functionality of Ettus’s RF-NoC (RF Network on Chip) with the capability of REDHAWK. Luckily, there was already a pattern for this provided by the developers of REDHAWK: the Persona Device Pattern. At the time of this writing, the documentation for this pattern can be found […]
A common misconception about REDHAWK and GNURadio is that they’re at odds with one another, perhaps enemies. The truth is each can support the other with a little bit of integration effort. In this post, we’ll be digging more into the details and usage of GNURadio-REDHAWK, which we discussed and released during the GNURadio Convention in 2017.
To build upon the rapid deployment capabilities we introduced with Docker REDHAWK, we now bring you a distributed computing solution in the form of Docker Redhawk Swarm! Docker Swarm is the perfect companion to enable the greatest power of Redhawk: its capability to divide a complex signal processing task into components that can be distributed across a diverse set of devices. In this post, we walk you through the steps of setting up your Swarm, deploying Redhawk, and even integrating SDR and GPS platforms!
In the previous posts, we’ve covered how to set up trusted SSL for internal services, then how to enable HTTPS and Container Repository features on a GitLab server, and finally how to add Runners to your server. In this case, we’ll focus on a Docker runner.
In the previous two posts, we covered first setting up SSL registration and automated maintenance using a Docker container from LinuxServer.io for Let’s Encrypt’s services, and then followed it up with enabling encrypted HTTPS and Container Repository on a GitLab server. So what’s next on the list for fully-functional Continuous Integration (CI)? Runners.