COSMOS 7.5 Release: Data Processing Improvements to Keep COSMOS Responsive Under Heavy Load
COSMOS 7.5 is live with tons of new enhancements and bug fixes as we continue to improve aerospace’s preferred command and control system! This release improves and measures how data moves through COSMOS and tells you when processing can’t keep up. It also reduces memory use to stay responsive while accommodating large targets. The 7.5 release includes updates to the COSMOS documentation, too. Also be sure to check out the OpenC3 Store for a variety of new plugins and functionality.
Here’s what to look forward to when upgrading to COSMOS 7.5:
Data Processing and Performance Improvements
This release focuses on data and memory usage. COSMOS 7.5 introduces threaded socket reads, preventing data from backing up behind processing. Redis writes are now batched every 0.1 seconds to greatly reduce Redis load at high packet rates. 7.5 also adds bounded Redis streams to cap target streams’ maximum age.
COSMOS 7.5 also lowers memory usage by shrinking the CmdTlm memory footprint and now, instead of falling further and further behind, streaming skips ahead when in the event of lag.
Enhancements to COSMOS
A few key enhancements include the new Astro clock driven by a telemetry item, typo-tolerant fuzzy search in Packet Viewer, streamed volume downloads in Bucket Explorer which now account for files over 2GB work, and the ability for non-admin users to write to user-defined buckets.
Security Updates
In 7.5, COSMOS improves security by gating table config overlays, forcing plugin upgrades to protect modified files and report diff failures, and ensuring that any values given are dropped when an item is obfuscated.
Documentation Updates
COSMOS documentation now includes new guides for AWS EC2, AWS EKS, and Network Configuration.
Notice: Migration Notes and Breaking Changes from 6.x
With the addition of the compose.override.yaml and .env.local (first in 7.3.0), it’s necessary to move all compose.yaml and .env updates into these new files. Here is the recommended process:
- Rename existing compose.yaml and .env files to override.yaml and .env.local.
- Get the newly released compose.yaml and .env files from the release.
- Diff with these files to identify any project-specific modifications and remove any defaults or other settings that are not explicitly being overridden.
This process will make upgrading much easier going forward by removing the requirement of syncing with OpenC3’s defaults.
S3 Backend Migration: Migrated from MINIO to versitygw. View the Migration Guide for more information.
COSMOS 7.5 Release Notes
Stay connected with OpenC3 and make sure you always get the latest COSMOS updates by subscribing to our newsletter!
