Installation Prerequisites
- The Component Cluster is deployed and configured.
- Usage Collector is installed.
- Rating Engine is installed.
- Order Management is installed.
Kubernetes Resource Requirements
The minimum Kubernetes resources required for the microservice deployment, including on-premise Kubernetes cluster deployment, are:
| Container | CPU cores | RAM in GiB |
|---|---|---|
| rating-orchestrator | 1.0 | 1.25 |
How to Deploy Rating Orchestrator
To deploy Rating Orchestrator:
- Ensure the prerequisites above.
- Follow the common CloudBlue Commerce component deployment procedure using the Rating Orchestrator deployment parameters below in the config.yaml.
How to Upgrade Rating Orchestrator
To update Rating Orchestrator, follow the common CloudBlue Commerce component update procedure using the Rating Orchestrator deployment parameters below in the config.yaml.
Rating Orchestrator Deployment Parameters
When installing or updating Rating Orchestrator, use the parameters below in the config.yaml.
Component Name
rating-orchestrator
Common Parameters
| Parameter | Default value |
|---|---|
| javaopts | -XX:MinRAMPercentage=30.0 -XX:MaxRAMPercentage=70.0 -XX:MetaspaceSize=96m -XX:MaxMetaspaceSize=256m |
| resources.requests.cpu | 500m |
| resources.requests.memory | 780Mi |
| resources.limits.cpu | 1 |
| resources.limits.memory | 1280Mi |
Specific Parameters
| Parameter | Default value | Description |
|---|---|---|
| max_order_details_in_batch | 1000 | The maximum number of subscriptions per billing order creation request |
| rating_data_partition_size | 100 | The maximum number of usage records sent to Rating Engine for processing at one time |
| alerts_enabled | false |
This setting enables or disables Prometheus alerts:
|
Sample config.yaml
Default config.yaml:
---
components:
rating-orchestrator: {}
Full config.yaml:
---
components:
rating-orchestrator:
javaopts: "-XX:MinRAMPercentage=30.0 -XX:MaxRAMPercentage=70.0 -XX:MetaspaceSize=96m -XX:MaxMetaspaceSize=256m"
resources:
requests:
cpu: 500m
memory: 780Mi
limits:
cpu: "1"
memory: 1280Mi
alerts_enabled: false
max_order_details_in_batch: 1000
rating_data_partition_size: 100
How to Obtain the Current config.yaml from CloudBlue Commerce
When updating CloudBlue Commerce components, you may need to obtain the current config.yaml.
To obtain the current config.yaml from CloudBlue Commerce, on a machine with kubectl, execute the following request:
kubectl -n NAMESPACE get secret config-yaml-backup -o "jsonpath={.data['config\.yaml']}" | base64 -d
Note: NAMESPACE is the namespace of your CloudBlue Commerce installation.
To find it, execute the following command:
kubectl describe svc oss-proxy | grep namespace
How to View the Deployment Parameters with Default Values for the Component Version You Want to Install (values.yaml)
To view the deployment parameters with default values (values.yaml) for the component version you want to install, run the following command from the machine with kubectl:
helm show values <component_name_for_config.yaml> --version <component_version> --username <username_for_deployment_repository> --password <username_for_deployment_repository> --repo <a_link_to_repository_with_CloudBlue Commerce_components>
For username and password to the deployment repository, please contact your Technical Account Manager.