Our last release of 2024, Inmanta Service Orchestrator 7.3, is now available. This minor release improves performance and provides a general clean-up in preparation for our next major release. The most notable improvement is state transfer optimization in our lifecycle management.
State Transfer Optimization
Each service has a number of lifecycle states, for example ordered, up, failed, ... A state transfer is triggered by an external event like an API call or a deploy. This transfer requires at least one model evaluation to be performed. Often even more, for example when the intent is updated through the API, the model is evaluated twice:
- First, a validation to confirm the intent is valid
- Second, an evaluation that generates the intent for each of the resources the service is decomposed in
However, these evaluations are not always required. This release introduces the ability to explicitly specify that two states have an identical low-level intent within your infrastructure. The lifecycle manager can then relax some of the validations it performs, which potentially results in significant speed improvements depending on the use case.
The model developer is responsible for indicating in the lifecycle of the service which states have the same intent. The lifecycle manager will optimize by skipping unnecessary model evaluations. This means that it is important that this information is correct, so any required evaluations aren't skipped by accident.
We also added support for automated testing by stepping automatically through the lifecycle and verifying if the low-level intent is the same. Depending on the number of lifecycle states of the service this can take some time. Below is a visual output of the test while it is running:
Want to see everything that's new? Head over to docs.inmanta.com for a comprehensive overview of everything this latest release has to offer.