USING VM FOR DSS
Originally
ADR-0070-USING-VM-FOR-DSS (v5) · Source on Confluence ↗Deploying Test DSS as a VM
| Comment | ||
|---|---|---|
| Status | accepted |
Decision
Rather than use paved path Kubernetes techniques, UTM will deploy the Test DSS using VM (Google Compute Engine) infrastructure.
Context
DSS - Discovery and Synchronization Service is a component of the
InterUSS Project. Drone operators will use this system to coordinate flights and avoid crashing into each other.
The open source project linked above is a ready-built DSS system that UTM would like to use for building our integration in preparation for simulations and live flight tests with the FAA and other operators.
The repo offers a test configuration using five Docker images running in a single container. We were able to get a test DSS up and running on a developer machine in a couple of hours. However, when considering the deployment of this test system in using DroneUp’s paved paths the task become daunting. Our interpretation would be that we’d need to create 5 repos (one per Docker image), split apart the existing build files across the 5 repos, get all 5 images wired up, etc… Square peg, round hole.
Deploying to a VM running Docker requires a fraction of the effort, a fraction of the code, and no extra repos.
Consequences
- It requires OPA Policy change to unlock GCE features
- PR cannot offer standard monitoring and support
Alternatives Considered
- Clean Coders offered to host a DSS to circumnavigate the complexities for DroneUp’s PE environment. This is undesirable as it leaves DroneUp without the resources or know-how of deploying DSS systems.