Search: "deployment plan"

Setting up a deployment plan

crashcourse-platform-deploy-setup-deployment-plan--default-deployment-plan.png

crashcourse-platform-deploy-setup-deployment-plan-pic1.png

crashcourse-platform-deploy-setup-deployment-plan-gen3

The release is active in that all changes made to it compared to the running environment are applied effectively before executing the deployment. The Deployment plan is defined in the Deployment Plan section under Deploy.

[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-deploy-setup-deployment-plan-pic1.png]] == 3. Defining the Deployment plan == Below is a screenshot of a basic Deployment plan.

[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-deploy-setup-deployment-plan--default-deployment-plan-gen3.png]] Running a deployment plan means machines are stopped, and new images are deployed. eMagiz does this by comparing your currently running release and the recent release you have activated.

Setting up a deployment plan

crashcourse-platform-deploy-setup-deployment-plan--default-deployment-plan.png

crashcourse-platform-deploy-setup-deployment-plan-pic1.png

crashcourse-platform-deploy-setup-deployment-plan

{{container}}{{container layoutStyle="columns"}}((( In this microlearning, we will focus on setting up a deployment plan and learn about the considerations when setting up such a deployment plan.

Active in that all changes made to the release compared to the running environment are applied effectively before executing the deployment. The Deployment plan is defined in the Deployment Plan section under Deploy.

[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-deploy-setup-deployment-plan-pic1.png]] == 3. Defining the Deployment plan == Below is a screenshot of a very basic Deployment plan.

Define deployment plan & create release

crashcourse-platform-exercise-define-deployment-plan-and-create-release

This exercise will explain how you can define a deployment plan for your environment and create a release based on what we have just finished in the Create phase of eMagiz.

Exercise == In this exercise, please execute the following steps in Deploy to prepare your environment for deployment. * Actualize Deploy Architecture by pressing "Apply to environment" in "Start Editing" mode * Create a default deployment plan * Create a release based on what we have just finished in the Create phase of eMagiz. == 3.

{{video attachment="crashcourse-platform-exercise-define-deployment-plan-and-create-release.mp4" reference="Main.Videos.Microlearning.WebHome"/}} )))((({{toc/}}))){{/container}} {{/container}}

Define deployment plan & create release

crashcourse-platform-exercise-define-deployment-plan-and-create-release

This exercise will explain how you can define a deployment plan for your environment and create a release based on what we have just finished in the Create phase of eMagiz.

Exercise == In this exercise, please execute the following steps in Deploy to prepare your environment for deployment. * Actualize Deploy Architecture by pressing "Apply to environment" in "Start Editing" mode * Create a default deployment plan * Create a release based on what we have just finished in the Create phase of eMagiz. == 3.

{{video attachment="crashcourse-platform-exercise-define-deployment-plan-and-create-release-update.mp4" reference="Main.Videos.Microlearning.WebHome"/}} )))((({{toc/}}))){{/container}} {{/container}}

New features Deploy - Runtime overview: We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines. Deploy - Deployment plan: Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.

Bug fixes Deploy - Deployment plan: We fixed an issue where an error was given when trying to display an error message regarding deployment plan execution errors. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history.

It is now possible to see an overview of all runtimes on running machines, see runtimes and flow versions in the missing properties overview, and see which runtimes will be restarted or redeployed in a pop-up displayed when starting the deployment plan. Moreover, crash handling has been improved, as well as runtime logging and the display of the deployment execution error message.

====New features==== * Deploy - Runtime overview: We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines. * Deploy - Deployment plan: Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.

====Bug fixes==== * Deploy - Deployment plan: We fixed an issue where an error was given when trying to display an error message regarding deployment plan execution errors.

The automated upgrade feature replaces it alongside the "Upgrade" functionality in Deploy - Architecture. Deploy - Deployment plan: We updated the right pane of the deployment plan to make it more compatible with the new runtime generation.

You can use the filter logs icons at the top of the list to show more information. Deploy - Deployment plan: We updated the logic within our deployment plan functionality. The deployment step that disables all enabled triggers from the Manage phase disables triggers till you exit the deployment plan overview. That means that those triggers will be re-enabled after you move away from the deployment process or close the browser.

The automated upgrade feature replaces it alongside the "Upgrade" functionality in Deploy - Architecture. * Deploy - Deployment plan: We updated the right pane of the deployment plan to make it more compatible with the new runtime generation.

You can use the filter logs icons at the top of the list to show more information. * Deploy - Deployment plan: We updated the logic within our deployment plan functionality. The deployment step that disables all enabled triggers from the Manage phase disables triggers till you exit the deployment plan overview. That means that those triggers will be re-enabled after you move away from the deployment process or close the browser.

In the last sprint cycle, we focused on improving the speed of the deployment plan and making the next generation architecture the default.

Minor changes Deploy - Releases: We sped up the process of preparing runtime images in executing the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.

Bug fixes Create - Flow Designer: An issue has been fixed, where, previously, the connection line for drawing channels did not work well after the user scrolls or zooms in/out on the canvas. Deploy - Deployment plan: We fixed an issue of the release preparation step taking longer than necessary which is caused by the machine deployment steps to be executed when they could have been skipped.

In the last sprint cycle, we focused on improving the speed of the deployment plan and making the next generation architecture the default.

====Minor changes==== * Deploy - Releases: We sped up the process of preparing runtime images in executing the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably. * Manage - Monitoring: The queue browser now displays milliseconds in the timestamps. * Manage - Alerting: Alerts will only be generated for queues that are created and managed by the eMagiz JMS server. ====Bug fixes==== * Create - Flow Designer: An issue has been fixed, where, previously, the connection line for drawing channels did not work well after the user scrolls or zooms in/out on the canvas. * Deploy - Deployment plan: We fixed an issue of the release preparation step taking longer than necessary which is caused by the machine deployment steps to be executed when they could have been skipped. * Manage - Monitoring - We fixed a rare case where a runtime either (1) could not start, or (2) logging, errors, and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.

Deploy - Check properties: Informative error messages when saving or creating a property. (#576) Deploy - Deployment plan: We improved the deployment plan to avoid it causing problems when executing a deployment plan containing loads of steps.

Deploy - User management: Fixed an issue where 'Apply to environment' would take very long to finish. Deploy - Deployment plan: While generating a default plan, flow type steps will not be created for OSGi runtimes that run on a Docker machine. (#798) Deploy - Architecture: Cloud slots now wake up without potential need to apply to environment.

. (#576) * Deploy - Deployment plan: We improved the deployment plan to avoid it causing problems when executing a deployment plan containing loads of steps. * Deploy - Architecture: Added reset feature for 3rd generation runtimes. ====Bug fixes==== * Create - Settings: We fixed an issue where changing the connection type did not update all relevant flows. * Create - Flow designer: Newly generated flows were configured with incorrect resource locations under specific circumstances. * Deploy - User management: Fixed an issue where 'Apply to environment' would take very long to finish. * Deploy - Deployment plan: While generating a default plan, flow type steps will not be created for OSGi runtimes that run on a Docker machine. (#798) * Deploy - Architecture: Cloud slots now wake up without potential need to apply to environment. * Deploy - Architecture: 3rd generation runtimes are included in runtime checks while upgrading your cloud environment.

We also made some small changes to various XPath-related parts of the portal and updated our deployment plan. Please find all our changes and bug fixes below.

Minor changes Deploy - Deployment plan: We updated the deployment step that temporarily disables the triggers in your model.

On top of that, we reintroduced the automatic "enable trigger" step, which can be added as the last step of your deployment plan to automatically re-enable triggers. Be aware that you still need to enable triggers manually if you have manually disabled them before deploying.

We also made some small changes to various XPath-related parts of the portal and updated our deployment plan. Please find all our changes and bug fixes below.

====Minor changes==== * Deploy - Deployment plan: We updated the deployment step that temporarily disables the triggers in your model.

On top of that, we reintroduced the automatic "enable trigger" step, which can be added as the last step of your deployment plan to automatically re-enable triggers. Be aware that you **still** need to enable triggers manually if you have manually disabled them before deploying.

. (#1423) Deploy - Architecture: The helptext of volume mappings has been improved. (#1405) Deploy - Deployment Plan: The deployment plan steps with type 'Failover' are now deprecated, meaning they can no longer be added to a deployment plan.

. (#1405) * Deploy - Deployment Plan: The deployment plan steps with type 'Failover' are now deprecated, meaning they can no longer be added to a deployment plan. * Deploy - History: We added logging for when properties are deleted from the unused properties screen. (#1428) * Deploy - Missing Properties Overview: Setting the value of a missing property will now automatically remove it from the missing properties overview.