Creating workflows for live optimizations
A workflow for a live optimization study automates all the actions required to interface the configuration management. Notice that metrics collection is an implicit action that does not need to be coded as part of the workflow.
![](https://docs.akamas.io/~gitbook/image?url=https%3A%2F%2F1061986906-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FPWZ2pgV3c1fFpYm28w7h%252Fuploads%252Fgit-blob-2c8644e13b1d7b232cbb684758685c846fa89b9a%252FScreenshot%25202023-01-17%2520at%252015.29.53.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=d45ff636&sv=1)
More in detail, a typical workflow includes the following types of tasks:
Applying the configuration, by preparing and then applying the parameter configuration that has been recommended and/or approved to the target environment - this may require interfacing configuration management tools or pushing configuration to a repository
Depending on the complexity of the system, the workflow might be composed by multiple actions of the same type, each operating on separate components of the target system.
As expected, with respect to workflows for offline optimization studies, there are no actions to apply synthetic workloads as part of a load-testing scenario.
Last updated