Changes for page 220 - Patch Parade
Last modified by Carlijn Kokkeler on 2024/05/22 13:30
From version 89.1
edited by Erik Bakker
on 2023/06/09 10:12
on 2023/06/09 10:12
Change comment:
There is no comment for this version
To version 158.1
edited by Carlijn Kokkeler
on 2023/11/21 12:42
on 2023/11/21 12:42
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 199-HomeImprovements1 +209 - Max Verstappen - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,19 +1,31 @@ 1 -In the last sprint cycle, we focused on improving variousaspectsof the portalfunctionality. Among others,wefocusedon the next-generation architecture,thestore,security,and certificate management.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. 199-HomeImprovements.WebHome||target=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===== 6 + 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. 10 + 11 + 12 + 5 5 =====Minor changes===== 6 6 7 -* Design - Message mapping: It is now possbile to create a message mapping to an imported system message from the store. 8 -* Deploy - Architecture: In the details view of a machine, you can now see the Static IP that was assigned to this machine by the eMagiz cloud. This way, you no longer have to contact your partner manager to retrieve this information. To use this functionality, please ensure you upgrade (automatically) to the latest cloud template. (#899) 9 -* Deploy - User management: Added a new overview pop-up to manage your event streaming users with expiring access certificates. You will also receive a notification email approximately three months before event streaming users' access certificates expire. 10 -* Deploy - Release: Unused runtime images will be automatically removed after successful machine deployments. This can be disabled by changing the machine step in your deployment plan. 11 -* Manage - Monitoring: HTTP statistics page now displays all the resources. (#960) 12 -* Manage - Alerting: congestion control will be enabled by default with ten alerts per ten minutes, and the user cannot see or change it. 13 -* General - Infra: Changed the library for storing metadata in the eMagiz Control Tower. 15 +* Deploy - Releases: We sped up the process of preparing runtime images in the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably. 16 +* Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well. 17 +* Manage - Monitoring: The queue browser now displays milliseconds in the timestamps. 14 14 19 + 20 + 15 15 ====Bug fixes==== 16 16 17 -* Create - Store: Spring Reserved words containing * are not incorrectly replaced with the flow prefix. (#864) 18 -* Manage - Monitoring: Not all log messages were visible in the manage phase when an application failed to start. Note that this functionality requires a newly deployed release. (#937) 23 +====Infra and image changes==== 19 19 25 +* Infra: New logging feature enabling us to make better choices in encryption standards. 26 + 27 + 28 + 29 + 30 + 31 +