Search: "deployment plan"

Deploy - Releases: We fixed a bug where runtimes that did not change appeared in the deployment plan in the list of flows that will be restarted. (#1379) Deploy - Releases: We have resolved a bug that prevented you from deploying anything on a newly created model.

. * Deploy - Releases: We fixed a bug where runtimes that did not change appeared in the deployment plan in the list of flows that will be restarted. (#1379) * Deploy - Releases: We have resolved a bug that prevented you from deploying anything on a newly created model. * Deploy - Runtime Overview: We fixed a bug such that the runtime overview now shows the correct container version. (#1310) * Manage - Alerting: We have implemented a fix that allows you to activate and test queue triggers per environment when you are migrating your model to the current runtime architecture.

. * The Docker Cloud templates are now also connected to the eMagiz support infrastructure providing cloud instance level alarms === **Improvements** === * Performance Deployment plan When running a Deployment plan on a large environment, the browser would consume a significant amount of CPU.

//__Random stuck in deployment plan execution__// We addressed an issue where the execution of the deployment plan would occasionally become stuck or halted unexpectedly. == **Fancy Forum Answers** == As always, this is a gentle reminder to ask questions via the Q&A forum.

. ** HTTP Statistics - Overview *** Problematic requests *** All requests == **Feedback Items** == //__Failover deployment plan__// The deployment plan steps with type 'Failover' are now deprecated, meaning they can no longer be added to a deployment plan.

With this release, we have changed this behavior so that this only happens when the flow you remove is an API-related flow and not when it is a messaging or event streaming flow. //__Stop deployment plan when a property is missing__// Currently, the execution of your deployment plan continues when eMagiz notices a missing property.

This allows you to fill in the properties, and once filled in, you can continue with the remainder of the deployment plan. //__Cap stack trace of error messages and log entries__// To prevent that enormous stack traces of error messages and log entries need to be processed by various systems, we have now limited what is kept so only the relevant information is shown to the user. == **Fancy Forum Answers** == As always, this is a gentle reminder to ask questions via the Q&A forum.

This also means that your deployment plan changes as well. For example, instead of deploying on a flow-by-flow basis, we will package the whole runtime in one image and deploy that to the machine. Therefore new steps have been added to the deployment plan to deploy changes on your machine. For example, the first time you introduce a Generation 3 runtime on a machine, you must add a Deploy Machine step to the deployment plan and remove all actions referencing the runtime you migrated.

[[image:Main.Images.Migrationpath.WebHome@migration-path-migration-path-emagiz-runtime-generation-3--deployment-plan-example.png]] {{info}} When selecting the option for the "big bang" approach of migrating your model, you can use the "Default plan" option to update your Deployment plan {{/info}} {{info}} When opting for the "step-by-step" approach of migrating your model, depending on which part of your model you are already updating, you must manually add a "Deploy machine" step per machine that is migrated to the next-generation architecture.

If the flow version is as expected, we can check the [[properties>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]] to see whether we see any changes.

Deploy - Architecture: Several improvements for our failover functionality have been done: We have improved the warning message for the balance failover deployment plan step, making it more clear how to solve this issue should it occur during your deployment.

. * Deploy - Architecture: Several improvements for our failover functionality have been done: ** We have improved the warning message for the balance failover deployment plan step, making it more clear how to solve this issue should it occur during your deployment. ** We have added the option to manually initiate the failover balancing process, saving you from having to execute your deployment.

. * To keep your project manageable, it's recommended to include a manual step in your ACCP or PROD deployment plan to clean up unused resources during every release cycle. == 5.

Prerequisites == * Basic knowledge of the eMagiz platform * Understanding Releases and be able to run a Deployment plan effectively == 2. Key concepts == eMagiz uses the concept of flows and runtimes.