Release notes for Genus 11.0
Introduction
This document lists all user-visible changes to Genus since the previous release.
This release note will be updated prior to the release and may also be updated as long as the release is available, e.g. with information of new patches or known issues. Please take note of the installation and upgrading comments, and the release notes change log.
Installation and upgrading
Prior to upgrading to this release, you must:
- Upgrade to the previous release. See the Release notes for the previous release for more information.
- Review the Expiry date of your Genus License File and install a new one if necessary.
- Review the rest of the release notes for this release.
- Please note that there does not exist any Genus Upgrade Assistant for this upgrade.
See also the following notes.
#23618 Helm config volumesMounts changed to volumeMounts
There was a typing error in the helm value for setting volumeMounts for datamartQueryService and CoreService. The correct spelling is "volumeMounts". If it says "volumesMounts" in any config files, this must be changed to "volumeMounts".
This is relevant for application using client certificates or startup scripts.
End-of-life functionality
End-of-life functionality is functionality that was available in the previous release, but is no longer available in this release.
There are no end-of-life functionality identified in this release.
Deprecated functionality
Deprecated functionality is available in this release, but will (most probably) no longer be available in the next release.
There is no deprecated functionality in this release.
Breaking changes
This section lists important changes introduced in this release. You will need to use this list in order to understand the changes you might need to make to your application to support the new release.
#23634 Mega service is replaced by core-service
After 10.23, the mega-service is no more. It is replaced by the core-service, which runs on Linux as default. Please update your helm-value config files accordingly.
If you wish to run the core-service on Windows, this can be done by setting the helm values like this:
genus-core-service:
runOnWindows: true
#23636 Changes to global.timezone helm value (Genus and Genus Operator)
If the global.timezone helm value is specified in any of your helm value files, you will need to change this value in Genus 11.0, and Genus Operator 7.0.
We are moving from a volumeMount to an environment variable approach to setting the timezone in the containers.
This means that were you before specified the path to the file specifying the timezone, now you must set the time zone code. This means that if it says global.timezone: "/usr/share/zoneinfo/Europe/Oslo" now, you should change it to global.timezone: "Europe/Oslo"..
Europe/Oslo is the default value. If this is your local timezone, you can delete it from your helm value files.
#23637 Genus 11.0.0-alpha.4 and later requires Genus Operator 7.0.0-rc.0 or newer
Due to changes to how we authenticate with the docker repository, any versions after Genus 11.0.0-alpha.4 will require Genus Operator 7.0.0-rc.0 or newer to run in the same namespace in order to be allowed to pull images.
#23642 Stricter data type interpretation
Is some cases, Genus has accepted a property to be modeled as a different type that the actual type in the database.
This is no longer permitted. Genus will stop, and an error message will be generated describing the problematic property/column.
Tip: Try https://
#23643 Genus 11.0.0-alpha.27 and later fails with deploy error: no matches for kind "ServiceMonitor" Genus deploys servicemonitor-resouces which requires Prometheus to be installed in the Kubernetes cluster. If you get the following error on deploy Prometheus is not installed:
Error: UPGRADE FAILED: [resource mapping not found for name: "klp-skade-origin-authentication-service-servicemonitor" namespace: "" from "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1" Solution is either to: #23641 New effect: Split Document The Split Document effect separates pages in a document to new documents. It is the opposite of Combine Documents. #23644 Handling of REST and SOAP requests moved to its own microservice In version 11.0.0-beta.3, REST and SOAP requests are handled by a new microservice, called the rest-soap-service. This means that they are now processed independently of traffic coming from Genus Web, and should improve performance in cases where there is simultaneous traffic coming from both sources. This also means that if you have made adjustsments to the default configuration for the core-service to handle heavy REST or SOAP traffic, these configuration changes should be made to the rest-soap-service instead. #23632 Access to request/response data for REST services in action flow The Action Orchestrator object available in action flows extended to include request data for a published REST service and request/response data for last consumed REST service. The data is structured into two groups: Rest Service - Last Consumed and Rest Service - Published: -- Rest Service - Published ---- Request ------ Method ------ Path ------ Query String ------ Headers -------- Name -------- Value ------ Content -------- Media Type -------- String Data -- Rest Service - Last Consumed ---- Request ------ Method ------ URL ------ Headers -------- Name -------- Value ------ Content -------- Media Type -------- String Data ---- Response ------ Headers -------- Name -------- Value ------ Content -------- Media Type -------- String Data ------ Status ------ Status Text #23635 Model instance recycling is now configurable, and disabled as default Each application model instance will use more and more memory as it processes different requests and requires more parts of the model. In Genus 10.23 we added model instance recyling, which is a way to prevent excessive memory usage by the core service. This works by having each instance of the application model running in a core-service recycle after handling a certain amount of requests. This worked well for limiting the memory usage, but at the expense of performance and caching. In Genus 11.0, we are making some adjustsments to this functionality by turning it off as default, and making it configurable for those who want to use it. If you are noticing that the core-service is using excessive amounts of memory, consider doing the following adjustments to your helm value config: Specify a min and a max value for how many requests each model instance should handle before getting recycled. Both a min and a max value is needed to have a degree of randomization for when the recycling happens, so not all the model instances will recycle at the same time. #23638 Add contact information for bug reports If there is a crash in a Genus runtime, an automatic bug report is sent to Sentry. Often it is helpful for R to know who to contact if there is a need to discuss the bug or ask for more information regarding the case. To provide this contact information, please use the helm value There are no resolved issues in this release. Known issues are errors or lack of functionality. Known issues may be solved in a future release based on customer demand. There are no known issues in this release. Tips and hints are design decisions or answers to support questions that may be of general interest. There are no tips and hints specifically targeting this release.
servicemonitor:
enabled: false
Major new functionality
Minor new functionality
global:
modelInstanceRecycling:
min: NNNN
max: MMMM
global.contact, which can be either an email, name or phone number where R can reach someone responsible for the application.Resolved issues
Known issues
Tips and hints
Change log