Search: "deployment plan"

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.

. * 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.

Once you have created your new release, you can use the deployment plan steps to activate the changes on both flow and property levels.

When you are finished with all runtimes navigate back to the Releases overview in Deploy and press the Deploy icon to activate your deployment plan. This is a great way to ensure that you did not accidentally miss one or more flows and will automatically ensure that the eMagiz alerting is activated again (assuming you make use of the best practices of eMagiz). == 4. Key takeaways == * Make your life easier by keeping up to date with regards to the build numbers that eMagiz releases * Determine the impact of the build number upgrade based on the release notes and the comparison functionality * Communicate before executing the upgrade * Ensure that data traffic is limited (or even better halted) during the upgrade * Verify your work by running the deployment plan == 5. Suggested Additional Readings == If you are interested in this topic and want more information on it please read the help text provided by eMagiz. )))((({{toc/}}))){{/container}}{{/container}}

. (#572) When a cloud slot change is pending, you will be notified. (#606) Deploy - Deployment plan: Details of a deployment step are now visible for users with view rights. (#590) Deploy - Properties: We add more information in history to show containers or connectors where you changed the properties.

. (#606) * Deploy - Deployment plan: Details of a deployment step are now visible for users with view rights. (#590) * Deploy - Properties: We add more information in history to show containers or connectors where you changed the properties.

The impact of this can be read [[here>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]{{/info}} //__Improved efficiency in deploying a release__// This release improves the efficiency of the "prepare release" step needed when deploying on the next-generation architecture.

Deploy - Releases: We fixed an issue where after removing containers from a machine, during the execution of the deployment plan, the removed containers are not recognized as change, causing the 'Deploy machine' step to be skipped. (#514) Manage/Event streaming statistics.

. * Deploy - Releases: We fixed an issue where after removing containers from a machine, during the execution of the deployment plan, the removed containers are not recognized as change, causing the 'Deploy machine' step to be skipped. (#514) * Manage/Event streaming statistics.

//__Failover__// 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.

//__List of runtimes__// We fixed a bug where runtimes that did not change appeared in the deployment plan in the list of runtimes that will be restarted.