Skip to Content

Changes for page 225 - Pop-up Party

Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 84.1
edited by Erik Bakker
on 2023/05/26 08:40
Change comment: There is no comment for this version
To version 168.1
edited by Carlijn Kokkeler
on 2023/12/04 15:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -198 - Great Migration
1 +210 - Deployment Delights
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,23 +1,24 @@
1 -Another couple of weeks have passed, so it is time for a new release. We have focused in this period on improving the migration process towards the next-generation architecture as well as how the user experience and interaction with the next-generation architecture works.
1 +In the last sprint cycle, we focused on improving several aspects related to the deployments. It is now possible to see an overview of container versions, and containers will not be deployed and restarted when no changes have been made. Moreover, several bug fixes have been done relating to the Flow Designer, the Deploy phase, and alerting.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.198 - Great Migration.WebHome||target= "blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.210 - Deployment Delights||target="blank"]].
4 4  
5 +=====New features=====
6 +
7 +* Deploy - Releases: We added the possibility to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section.
8 +
5 5  =====Minor changes=====
6 6  
7 -* Create - 3rd generation runtime migration: You will be notified by a pop-up when the migration is complete.
8 -* Create - 3rd generation migration: Migrating a JMS server to the 3rd generation runtime will migrate backup JMS servers too.
9 -* Create - Flow designer: Added a validation for HTTP outbound gateways and HTTP outbound channel adapters that will create an alert if both Encoding mode and a REST template is set for the component.
10 -* Deploy - Releases: We improved the performance of preparing and deploying releases, by optimizing the algorithm that decides if runtime images needs to be rebuild or not.
11 -* Deploy - Releases: We improved resource validation when preparing releases. You will get notified when a flow resource was updated in one flow, but not in another flow in your release. Only applies to third generation runtimes.
12 -* Deploy - Architecture: When pressing "Apply to Environment" in Deploy -> Architecture there is no hard dependencies anymore on the (active) release when running in the next generation architecture. This makes it more clear and tangible what function is necessary for what goal.
13 -* Manage - Alerting: Updated the eMagiz control tower with an improved way to determine whether metrics for a runtime are missing.
14 -* General: Updated the monitoring stack so alerts can be paused, reducing the alerts that are received during eMagiz infra deployments.
11 +* Deploy - Releases: When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
12 +* Deploy - Containers: Changing the list of flows that should run on a container will now trigger the rebuilding of images.
15 15  
16 16  ====Bug fixes====
17 17  
18 -* General: Increased the performance of the eMagiz Control Tower, which should significantly reduce the occurence of the 'failed to send to elastic' log message in your models.
19 -* Deploy - Architecture: The docker commands now correctly propagate to the java process, making sure containers stop, start and restart as intended when running runtimes in a hybrid situation. Please check out the runtime [[release notes>>Main.Release Information.Runtime Images.WebHome||target="blank"]] for additional information.
16 +* Create - Flow Designer: An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
17 +* Create - Flow Designer: We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior.
18 +* Deploy - Containers: The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
19 +* Deploy - Deployment plan: We solved a bug where a deployment step in the deployment plan could randomly get stuck.
20 +* Deploy - Runtimes: We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
21 +* Manage - Alerting: The alert ‘topic approaching maximum size’ alert has been temporarily disabled due to a high number of false positives.
22 +* Manage - Alerting: We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
20 20  
21 -====Remarks====
22 22  
23 -* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.