Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 155.1
edited by Carlijn Kokkeler
on 2023/10/10 13:56
on 2023/10/10 13:56
Change comment:
There is no comment for this version
To version 277.1
edited by Carlijn Kokkeler
on 2023/12/04 14:43
on 2023/12/04 14:43
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -20 6-SituationalDeployment1 +209 - Deployment Delights - Content
-
... ... @@ -1,60 +1,43 @@ 1 1 {{container}} 2 -{{container layoutStyle="columns"}}((( 2 +{{container layoutStyle="columns"}} 3 +((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** In thelast few weeks, wehavedone 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 +**Hi there, eMagiz developers!** We have... 6 6 7 -== ** DeploymentPlan** ==8 +== **Release Maintenance** == 8 8 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 -//__Editing release properties__// 13 -With this release, it will be possible to change the description of a property by editing the property. 14 14 15 -//__JMS memory setting check__// 16 -A change in memory settings triggers redeployment of the container now. 17 17 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 - 25 25 26 26 == **Feedback Items** == 27 27 28 -//__ Alertingmanualpause__//29 - Afewreleasesago we changedthebehaviorofalertinginthe deploymentplan. Noweach timewhena deploymentplanisexecutedthealertingwill be automatically re-enabledwhenthedeployer closesthedeploymentplan or closes the web browser. Themajorityof theusers arehappywiththenew behavior, buttherearesome use cases that youdonotwantstartthe alertingimmediately.With thisrelease, if alerting has beenpausedmanually, thiswill not beactivated automatically after a release deployment.16 +//__Container version overview__// 17 +In Deploy > Releases, it is now possible to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section. 30 30 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). 19 +[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]] 33 33 34 -//__U TC times inGrafanapanels__//35 - All Grafanapanels nowshowUTC times,whicharenormally usedineMagiz, insteadoflocal(browser)timezones.This way, it iseasierto matchgraphs withloggingeventsoralerts.21 +//__Unchanged containers__// 22 +When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted. 36 36 37 -//__ Updateflowdesigner version__//38 - The framework usedin the flowdesignerhasbeenupdatedto thelatestversion.24 +//__Rebuilding of images__// 25 +Changing the list of flows that should run on a container will now trigger the rebuilding of images. 39 39 40 40 41 - 42 42 == **Bug Fixes** == 43 43 44 -//__ Gainhe ability again to configurecertificatesin Deploy Architecture again__//45 - In restricting the configurationoptions onthecertificatelevelinoneofourlatterreleases, it became impossiblefornormal userstoadd and editcertificates within Deploy Architecture.To resolve thisproblem we havenow releaseda fixto resolve this issue, givingpeople the ability again to add and editcertificatesunder Deploy Architecture.30 +//__Runtime metrics processing__// 31 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing. 46 46 47 -//__ Ensurethat differing container configurations deploythecorrectconfiguration__//48 -W henyou run in a multi-runtimeconfiguration andchangethe actualflows that need to runon containerA vs. containerB,it happenedbeforethat all flows werestill beingdeployed onall runtimes.With this release,we will feedthis informationcorrectlyto our infrastructureoensurethe correct and configured flows are deployed on the propercontainers.33 +//__Deployment plan__// 34 +We solved a bug where a deployment step in the deployment plan could randomly get stuck. 49 49 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. 52 - 53 53 == **Fancy Forum Answers** == 54 54 55 55 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: 56 56 57 -* [[ Gettingfilesfromsubfolders(FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]40 +* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]] 58 58 59 59 == **Key takeaways** == 60 60 ... ... @@ -76,5 +76,11 @@ 76 76 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 77 77 78 78 ~*~* Indicates a next-generation-architecture only feature. 79 -{{/info}})))((({{toc/}}))){{/container}} 62 +{{/info}} 63 +))) 64 + 65 +((( 66 +{{toc/}} 67 +))) 80 80 {{/container}} 69 +{{/container}}