Skip to content
SENSE LogoSENSE Operations Manual
Release Notes

Release 26.08

- 3 min read

Technical Release Details: https://github.com/esnet/StackV/releases/tag/26.08

Release 26.08 is a minor release focused primarily on our long-overdue migration to MySQL 9.7, including improved system stability, health visibility, a healthy mix of UX and UI improvements.

⚠️ Breaking Changes

Section titled “⚠️ Breaking Changes”
  • Due to incompatibilities and complications with our schemas, a fresh installation is required for this release. There is no supported in-place database upgrade from existing deployments.
    • Use the new System Backup and Restore feature and the legacy archive exporter to transfer some of your existing data to the fresh installation.
      • Archives include selected system settings, drivers, and service profiles.
      • Archives exclude service instances, tasks, alerts, model/runtime state, metadata, logging, and audit history.
  • The SENSE-O Docker Compose templates and Helm charts now use MySQL 9.7, and Flyway has replaced Sqitch for our DB migration sidecar.

✨ New Features

Section titled “✨ New Features”
  • A new System Backup and Restore feature has been added, allowing operators to transfer data between SENSE-O deployments or to save a snapshot of their current configuration. For more details see the dedicated page at System Backup and Restore.
  • System Health telemetry for Version Groups, Version Items, and model rows has been added. This allows managers to inspect and monitor key model statistics, as well as inspect the new model-cache state.

System Health Monitoring Modal

  • The new Profile Table page has replaced the previous pop-up modal, and further support for navigation, saving and tagging features, and general usability improvements have been made.

Profile Table Page

  • As mentioned above, the SENSE-O application stack now operates on the latest LTS of MySQL. This naturally brings improved database performance, but a large amount of work was done to optimize and refactor many parts of our persistence code that were lacking or problematic. The result is a more consistent and reliable orchestrator, and a large chunk of years-old tech debt finally overcome.

Minor Additions

Section titled “Minor Additions”
  • A pilot Garbage Collection system has been added, allowing for scheduled cleanup of eligible orphaned and stale model/version artifacts. Currently, this system is automatically operated in the background, but API endpoints allow admins to manually execute cleanups as needed. In the future this system will be integrated into a more robust background tasks system, allowing operators to configure and monitor the runs of various system operations.
  • The SENSE-O RBAC has been updated to support more restrictive and explicit user permissions, based around user classes. This is the first step in a larger user management rework we are undergoing, with more significant improvements to come later this year.
  • Standalone SENSE-P developments can now select a remote orchestrator to connect to, even across Keycloak boundaries.

🚧 Known Issues

Section titled “🚧 Known Issues”
  • The orchestrator may still run into VersionItem or VersionGroup stalls in rare circumstances. This release adds more measures to allow for remedies without restarting the orchestrator (such as the new system health and garbage collection), as well as better transactional stability. Still, an operator may run into cases where service instances are unable to be provisioned (often accompanied by orchestration errors like VG_VI_ERROR). In such a case, if the unplugging and re-plugging of underlying drivers does not resolve the issue, a restart of the orchestrator may be required.
Tags: