Changes for page 206 - Situational Deployment

Summary

• Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-205 - World Explorers
	1	+206 - Situational Deployment

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ebakker
	1	+XWiki.CarlijnKokkeler

Content

...	...	@@ -2,45 +2,91 @@
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 processed additional feedback on the Manage phase to ensure you can more easily create overviews of your statistics, displaying all information correctly and improving the migration process to the next-generation architecture in the Create phase slightly. On top of that, we have improved the scalability of our new generation monitoring stack and the alerting structure. We will also release a new cloud template for our next-generation infrastructure to comply with technical requirements from our cloud provider.
	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		-== **Mandatory Cloud Template Upgrade - Next-generation models ** ==
	7	+== **Deployment Plan** ==
8	8
9		-As can be seen on our [[status page>>https://status.emagiz.com/incidents/dbh6g9w3ks7q||target="blank"]], we will release a new cloud template for our next-generation models (both single and double lane) that will change a configuration in these templates to comply with technical and operational requirements from our cloud provider. The announcement of the status page itself holds more detail for those to whom it pertains.
	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.
10	10
	12	+//__Editing release properties__//
	13	+With this release, it will be possible to change the description of a property by editing the property.
	14	+
	15	+//__JMS memory setting check__//
	16	+A change in memory settings triggers redeployment of the container now.
	17	+
	18	+//__Properties tab__//
	19	+We have removed the deprecated tab Properties in the Deploy phase.
	20	+
	21	+//__Cleanup old images__//
	22	+When a release is removed, the related unused images in the on-premises machines will be removed as well.
	23	+
	24	+//__Performance improvements for loading releases__//
	25	+Performance improvements have been implemented for loading releases in Deploy. Releases should now load faster than before. All functionality should remain exactly the same as before.
	26	+
	27	+== **Store Improvements** ==
	28	+
	29	+//__Message definition elements order__//
	30	+We fixed an issue that the order of message definition elements was changed after being imported.
	31	+
	32	+//__Improting a store item with synchronous message definitions__//
	33	+We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should correspond with the exported message definitions.
	34	+
	35	+//__Importing store items containing static copies__//
	36	+We fixed an issue that store items were missing static copies. Now, store items with static copies are imported correctly.
	37	+
11	11	== **Feedback Items** ==
12	12
13		-//__Improved Validation when migrating to the next-generation architecture__//
14		-To improve the migration process to the next-generation architecture, we now show a list of all reported problems, allowing the user to resolve them before migrating to the next-generation architecture.
	40	+//__Alerting manual pause__//
	41	+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.
15	15
16		-{{info}}Note that when no problem is found, the migration process of that runtime will start automatically.{{/info}}
	43	+//__Ordering of graphs in Manage__//
	44	+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).
17	17
18		-//__Improved HTTP Statistics__//
19		-To improve the filtering and refresh functionality we offer on this overview, we have made several changes in this release that will improve the behavior of this overview.
	46	+//__UTC times in Grafana panels__//
	47	+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.
20	20
21		-//__Show values on the runtime level in Deploy Architecture__//
22		-We have improved the values shown on the runtime (i.e., container) level in Deploy Architecture so you can better assess whether the memory configuration is still suitable for your deployed solution.
	49	+//__Update flow designer version__//
	50	+The framework used in the flow designer has been updated to the latest version.
23	23
24		-{{info}}To get to the values we use different calculation methods per type of runtime, as certain runtime types have various reasons for existence.
25		-* JMS - The number of queues in the active release.
26		-* Messaging Container - The number of messaging integrations in the active release.
27		-* Messaging Connector - The number of messaging integrations related to this system in the active release.
28		-* API Gateway Container - The number of operations in the active release.
29		-* Event Streaming Container - The number of event processors in the active release.
	52	+//__Carwash track TLS versions in logging__//
	53	+A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
30	30
31		-There might be multi-tenant and multi-runtime situations that do not always get to the exact number; however, this is a great improvement compared to showing no values.{{/info}}
	55	+//__Moving channels in the flow designer__//
	56	+Moving already attached channels in the flow designer has been made sligthly easier.
32	32
	58	+//__Topic sizes description change__//
	59	+In the change description (and History) when altering the topic size of a topic the new and old value were switched around creating confusion, this has been resolved.
	60	+
	61	+//__Password change notification__//
	62	+When an account password change request is made, even when this fails, a mail is sent to the account owner to inform the owner about the action.
	63	+
	64	+//__Password comparison__//
	65	+When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password corresponds with a password in the database.
	66	+
	67	+//__Inactive user alerting__//
	68	+Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
	69	+
	70	+//__Alphabetical sorting on user level in HTTP statistics__//
	71	+Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
	72	+
	73	+//__SOAP Web services path__//
	74	+Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings.
	75	+
33	33	== **Bug Fixes** ==
34	34
35		-//__Gain the ability again to configure certificates in Deploy Architecture again__//
36		-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.
	78	+//__Flow designer styling__//
	79	+The styling of the flow designer's left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
37	37
38		-//__Ensure that differing container configurations deploy the correct configuration__//
39		-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.
	81	+//__Partial search for messages__//
	82	+It is now possible to search on messages partially in Manage Monitoring. For example, search for Uptime can be done by searching for "up" "time" "ptim".
40	40
41		-//__Remove queurying options in Manage__//
42		-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.
	84	+//__Disk usage after cloud template update__//
	85	+In the last cloud template update there was an issue with disk performance. This has been resolved in this release. You can manually upgrade your cloud template, or rely on automatic updates.
43	43
	87	+//__Error handling migration__//
	88	+If there is no custom error handling, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow. This has been fixed by adding a migration step, where we set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false.
	89	+
44	44	== **Fancy Forum Answers** ==
45	45
46	46	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: