Upgrade Notes for Otter 2.1

KB#1162: Last Updated February 12, 2019

Otter 2.1 is minor release with the following changes:

  • Pipeline Raft Support

Breaking Changes

There are no breaking changes in this release.

While there are no expected breaking changes, the context behavior of Orchestration Jobs has been specified as of v2.1 where previously it was undefined, and it is possible that executing plans with via orchestration job could result in unexpected behavior.

See the Orchestration Job Context documentation for the behavior specification.

New Features & Non-Functional Changes

Pipeline and Pipeline-Only Rafts

A new type of virtualized raft is now available to facilitate a promotion-based approach to infrastructure automation – A configuration plan and all of its resources can be kept in Git or the Otter database for a Dev/Testing environment, then promoted to higher environments (such as Production) using read-only zip file rafts.

Risk Mitigation

The only significant changes are additive. If you do not use the new pipeline rafts, then risk is minimal.

Upgrade Process

Otter may be upgraded by simply running the latest installer. The agents do not need to be updated.


There are no database schema changes, so a rollback will only require uninstalling Otter, and then reinstalling the old version.