Cloud Native ECE Should Have Unified Interface for Configuration Changes
(Doc ID 2768465.1)
Last updated on APRIL 16, 2021
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
On : 184.108.40.206.0 version, Script, config and sample data
In current version of Elastic Charging Engine (ECE) 12.0 PatchSet 3 InterimPatch 4, during initial cluster deployment, configuration is set through a combination of Helm (override-)values.yaml and configMaps yaml’s.
Once ECE cluster is up and running, further configuration changes are possible only through JMX.
It means that in a DevOps environment, where configuration is stored in a Configuration Repository, DevOps toolset must support (at least) two interfaces:
• CloudNative Helm API (specifically for install & upgrade operations)
• JMX via a custom “JMX connector”
It is requested that ECE configuration changes (including these on a running cluster) are unified and possible through helm upgrade operation.
Helm upgrade should support configuration changes of any parameter present in management/charging-settings.xml, regardless if the parameter is reflected or not in Helm values.yaml
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document