Wiki source code of R6 Docker - Double lane
Last modified by Erik Bakker on 2023/03/03 11:30
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | Non service affecting final template to use the R6 double lane release. | ||
| 2 | Process: To use the new R6 release of our cloud template we upgrade in one steps, the update is non service affecting. | ||
| 3 | |||
| 4 | **Overview** | ||
| 5 | This update changes the Cloud port check, coordination faled and clean store functionality on our 3rd generation runtimes. | ||
| 6 | |||
| 7 | **Updates** | ||
| 8 | * Cloud Port check: When the software does not expose the right ports, it will be restarted | ||
| 9 | * Coordnation failed: When the runtimes failes to startup due to a corrupted startup order, the runtime will restart freshly to remove the corrupted state. | ||
| 10 | * Clean store: The functionality to clean a store is added for generation 3 runtimes. See [[this link>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.eMagiz Cloud Management.expert-emagiz-cloud-management-clean-store||target="blank"]] | ||
| 11 | |||
| 12 | **Update Steps** | ||
| 13 | * Use the final R6 template (non service affecting) (duration: 4 minutes) | ||
| 14 | * User actions after applying the final template: | ||
| 15 | ** Check if all runtimes are reachable by the runtime dashboard. | ||
| 16 | ** Check if all flows have been installed according to the active release. | ||
| 17 | ** Check if messages pass through the bus by verifying a critical message flow in external systems. |