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.
We’ve posted about the powerful capabilities of Docker before, including topics on standing up a containerized version of REDHAWK SDR and testing a REST-Python server with Docker Compose. In this post, we will walk you through using Docker to build and run Analog Devices’ IIO Oscilloscope.
Some Quick History The last time we demoed bringing the B205mini into REDHAWK, it was again using Docker to containerize an environment conducive for a more recent version of UHD. Back then, we were working in different constraints: REDHAWK 2.0.2 CentOS 6.7 64-bit One constraint required the other, and the other required an older version […]