Skip to Content

Changes for page 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 245.1
edited by Carlijn Kokkeler
on 2023/11/21 11:31
Change comment: There is no comment for this version
To version 155.1
edited by Carlijn Kokkeler
on 2023/10/10 13:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -209 - Max Verstappen
1 +206 - Situational Deployment
Content
... ... @@ -2,71 +2,60 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** We have done .....
5 +**Hi there, eMagiz developers!** In the last few weeks, we have done much work for the Deploy phase. On top of that, we have worked on several store functionalities. Next to this, we have several smaller feedback items from our hackathon efforts that are now released to you.
6 6  
7 -{{warning}}Please be aware that for this release, because of the duration of the deployment, we advise you to check your TEST and ACCP cloud slots status, since you might need to start them manually in case your model is using the automatic wake up functionality. For following releases we will set the automatic wake up time to 6:00 AM UTC instead of 5:00 AM UTC. {{/warning}}
7 +== **Deployment Plan** ==
8 8  
9 -== **Next Generation Architecture Default** ==
10 -With this release, the next generation architecture will become the default. New models will use this generation as default.
9 +//__Improved deployment plan to make the process better and more predictable__//
10 +The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum. Next to this, the start/stop/restart machine deployment steps are now also executed correctly for aws and on-premises machines.
11 11  
12 -[[image:Main.Images.Release Blog.WebHome@release-blog-next-gen-default.png]]
12 +//__Editing release properties__//
13 +With this release, it will be possible to change the description of a property by editing the property.
13 13  
14 -== **Cloud Template R11 - Single Lane** ==
15 -This release introduces a new cloud template for all our customers running in a single-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found here
15 +//__JMS memory setting check__//
16 +A change in memory settings triggers redeployment of the container now.
16 16  
17 -== **Cloud Template R13 - Double Lane** ==
18 +//__Properties tab__//
19 +We have removed the deprecated tab Properties in the Deploy phase.
20 +
21 +//__Cleanup old images__//
22 +
23 +== **Store Improvements** ==
24 +
18 18  
19 -
20 20  == **Feedback Items** ==
21 21  
22 -//__Unused properties overview__//
23 -In Deploy > Releases, it is now possible to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties. Unused properties are properties that are:
24 -* Not used by any runtime that is in the Create phase release.
25 -* Not required by a flow that is in the Create phase release.
26 -* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
28 +//__Alerting manual pause__//
29 +A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser. The majority of the users are happy with the new behavior, but there are some use cases that you do not want start the alerting immediately. With this release, if alerting has been paused manually, this will not be activated automatically after a release deployment.
27 27  
28 -//__Send build requests asynchronously__//
29 -The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
31 +//__Ordering of graphs in Manage__//
32 +The graphs in Manage are now ordered according to importance. This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first).
30 30  
31 -//__Queue explorer milliseconds__//
32 -The queue browser now displays milliseconds in the timestamps.
34 +//__UTC times in Grafana panels__//
35 +All Grafana panels now show UTC times, which are normally used in eMagiz, instead of local (browser) time zones. This way, it is easier to match graphs with logging events or alerts.
33 33  
34 -//__Cancel and next buttons order__//
35 -The order of the cancel and next buttons when creating a new trigger has been changed to increase alignment across the platform. Now, all cancel buttons are placed on the right of a 'next' or 'save' button.
37 +//__Update flow designer version__//
38 +The framework used in the flow designer has been updated to the latest version.
36 36  
37 -//__Unused images__//
38 -When a release is removed, the related unused images in the on-premises machines will be removed as well.
39 39  
40 -//__Carwash logging__//
41 -A new logging feature enabling us to make better choices in encryption standards will be released.
42 -
43 -//__Static alerts queue consumers__//
44 -Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
45 -
41 +
46 46  == **Bug Fixes** ==
47 47  
48 -//__Images rebuild__//
49 -We fixed an issue which caused the release preparation step to take longer time than necessary and caused the machine deployment steps to execute when they could be skipped.
44 +//__Gain the ability again to configure certificates in Deploy Architecture again__//
45 +In restricting the configuration options on the certificate level in one of our latter releases, it became impossible for normal users to add and edit certificates within Deploy Architecture. To resolve this problem we have now released a fix to resolve this issue, giving people the ability again to add and edit certificates under Deploy Architecture.
50 50  
51 -//__Flow Designer connection line__//
52 -In the Flow Designer an issue has been fixed where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas.
47 +//__Ensure that differing container configurations deploy the correct configuration__//
48 +When you run in a multi-runtime configuration and change the actual flows that need to run on container A vs. container B, it happened before that all flows were still being deployed on all runtimes. With this release, we will feed this information correctly to our infrastructure to ensure the correct and configured flows are deployed on the proper containers.
53 53  
54 -//__Portal for migrated models__//
55 -We fixed a rare case where a runtime could not start, or logging, errors and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
50 +//__Remove queurying options in Manage__//
51 +To avoid errors and loading problems when analyzing your statistics in Manage, we have removed the option to select a default time range spanning more than seven days. This is to guarantee the stability of the solution and to avoid users getting unnecessary errors.
56 56  
57 -//__Error channel inbounds__//
58 -We added a migration step, where we set the error channel to “errorChannel” of all inbounds in a flow if the custom error handling is set to false. Before, the error channel would be set to “errorChannel” only for the first inbound in an entry flow.
59 -
60 60  == **Fancy Forum Answers** ==
61 61  
62 62  As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers:
63 63  
64 -* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]
65 -* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
66 -* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]
67 -* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]
57 +* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
68 68  
69 -
70 70  == **Key takeaways** ==
71 71  
72 72  Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you: