Skip to Content

Changes for page 243 - Migration Magic

Last modified by Erik Bakker on 2025/04/22 14:08
From version 239.1
edited by Erik Bakker
on 2025/04/07 09:25
Change comment: There is no comment for this version
To version 163.1
edited by Carlijn Kokkeler
on 2023/11/23 08:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -242 - Stability Score
1 +209 - Max Verstappen
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,18 +1,29 @@
1 -In the last sprint, we have released several items improving the stability of the platform across the various ILM phases. The biggest change we have is a new [[cloud template>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] allowing models running on our current-generation architecture to better utilize their CPU within the cloud models. On top of that, we release various improvements in the platform regarding clarity and stability.
1 +In the last sprint cycle, we focused on improving the speed of the deployment plan and making the next generation architecture the default. On top of that, we have worked to release new cloud templates for Docker Single Lane and Docker Double Lane, to introduce faster machine boot up and improved auto-healing. Moreover, we processed several feedback items and did some bug fixes.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.242 - Stability Score.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.209 - Max Verstappen.WebHome||target="blank"]].
4 4  
5 -====New Features====
5 +=====New features=====
6 6  
7 -* Cloud - Templates: We have implemented a feature for Cloud models to be able to consume an unlimited amount of CPU burst on their production environment. This is released as part of a new [[cloud template>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]].
7 +* Deploy - Releases: We added the ability 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.
8 +* Deploy - Cloud Templates: New Cloud Templates are available for docker single and double environments to introduce faster machine boot up and improved auto-healing. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
9 +* All - The next generation architecture is the default now. New models will use this generation as default.
8 8  
9 -====Minor Changes====
11 +=====Minor changes=====
10 10  
11 -* Store - Overview: Statistics tab in Store item details shows the number of imports and the models where a store item has been imported to, which is only visible to store admins. (#799)
12 -* eMagiz Connector - Softcrow: Softcrow restoration is added for the eMagiz Connector.
13 +* 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.
14 +* Manage - Monitoring: The queue browser now displays milliseconds in the timestamps.
15 +* Manage - Alerting: Alerts will only be generated for queues that are created and managed by the eMagiz JMS server.
13 13  
14 14  ====Bug fixes====
15 15  
16 -* Create - Transformation: In the Transformation tab of the Create phase. Newly created attribute operations of type aggregator can freely switch positions with a destination filter using the move left or move right buttons. (#1307)
17 -* Create - Flow Designer: Updated help texts and documentation references that pointed to Joda time with the relevant Java DateTimeFormatter options to reflect the current state of libraries supported in the runtime images.
19 +* 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.
20 +* Create - Flow Designer: We added a migration step to set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false.
21 +* 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.
22 +* 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.
18 18  
24 +
25 +
26 +
27 +
28 +
29 +