Administering PDC Cloud Native Services

17 Administering PDC Cloud Native Services

Learn how to perform common system administration tasks on your Oracle Communications Pricing Design Center (PDC) cloud native services.

Topics in this document:

Creating PDC Users (Release 15.0.1 or later)

PDC is a role-based application that authenticates and authorizes users based on the group to which they belong. The role-based functionality of PDC is supported by the following WebLogic Server groups, which are created when you deploy oc-cn-op-job-helm-chart.

PricingDesignAdmin: This group's users have administrative privileges on PDC. They can perform operations on all PDC UI screens, pricing components, and setup components.
PricingAnalyst: This group's users have administrative privileges for pricing components and view-only privileges for setup components.
PricingReviewer: This group's users have view-only privileges for all pricing and setup components.

When you create PDC users, add them to one of these groups based on the role of the user in the organization.

To create PDC users in the PDC domain:

In your override-values.yaml file for oc-cn-op-job-helm-chart, set the following keys:
```
ocpdc:
   wop:
      users:
         name: UserName
         description: Description
         password: EncodedPassword
         groups: Group
```
where:
- UserName is the name of the user.
- Description is a brief description of the user.
- EncodedPassword is the Base64-encoded password for the user.
- Group is the name of the group that the user belongs to. The available PDC groups are PricingAnalyst, PricingDesignAdmin, and PricingReviewer.
Deploy or redeploy PDC by running the helm install command for oc-cn-op-job-helm-chart:
```
helm install OpJobReleaseName oc-cn-op-job-helm-chart --values OverrideValuesFile --namespace BrmNameSpace
```
where:
- OpJobReleaseName is the release name assigned to your existing oc-cn-op-job-helm-chart installation.
- OverrideValuesFile is the file name and path of your override-values.yaml file.
- BrmNameSpace is the namespace for your existing BRM deployment.

Using Resource Limits in PDC Domain Pods

You can optimize the PDC system's CPU and memory usage for requests and limits during runtime. To do so:

In your override-values.yaml file for both oc-cn-helm-chart and oc-cn-op-job-helm-chart, set the ocpdc.wop.isVPAEnabled key to true.

In your oc-cn-helm-chart/pdc/vpa_values.yaml file, set the keys listed in Table 17-1.

Table 17-1 Keys for the BRM Helm Chart vpa_values.yaml File

Pods	Keys
PDC Domain	To set the request and limit values for the PDC domain pod: pdcDomainPOD.requests.cpu: Set this to the default CPU request value. pdcDomainPOD.requests.memory: Set this to the default memory requests value. pdcDomainPOD.limits.cpu: Set this to the maximum number of CPU cores the pod can utilize. pdcDomainPOD.limits.memory: Set this to the maximum amount of memory a pod can utilize. The default is 26i.
Real-Time Rating, Batch Rating, and the SyncPDC utility	To set the request and limit values for the PDC domain pod: pdcDomainPOD.requests.cpu: Set this to the default CPU request value. pdcDomainPOD.requests.memory: Set this to the default memory requests value. pdcDomainPOD.limits.cpu: Set this to the maximum number of CPU cores the pod can utilize. pdcDomainPOD.limits.memory: Set this to the maximum amount of memory a pod can utilize.
The ImportExportPricing utility	To set the request and limit values for the ImportExportPricing pod: pdcDomainPOD.requests.cpu: Set this to the default CPU request value. pdcDomainPOD.requests.memory: Set this to the default memory requests value.. pdcDomainPOD.limits.cpu: Set this to the maximum number of CPU cores the pod can utilize. pdcDomainPOD.limits.memory: Set this to the maximum amount of memory a pod can utilize.

Pods

Keys

PDC Domain

To set the request and limit values for the PDC domain pod:

pdcDomainPOD.requests.cpu: Set this to the default CPU request value.
pdcDomainPOD.requests.memory: Set this to the default memory requests value.
pdcDomainPOD.limits.cpu: Set this to the maximum number of CPU cores the pod can utilize.
pdcDomainPOD.limits.memory: Set this to the maximum amount of memory a pod can utilize. The default is 26i.

Real-Time Rating, Batch Rating, and the SyncPDC utility

To set the request and limit values for the PDC domain pod:

pdcDomainPOD.requests.cpu: Set this to the default CPU request value.
pdcDomainPOD.requests.memory: Set this to the default memory requests value.
pdcDomainPOD.limits.cpu: Set this to the maximum number of CPU cores the pod can utilize.
pdcDomainPOD.limits.memory: Set this to the maximum amount of memory a pod can utilize.

The ImportExportPricing utility

To set the request and limit values for the ImportExportPricing pod:

pdcDomainPOD.requests.cpu: Set this to the default CPU request value.
pdcDomainPOD.requests.memory: Set this to the default memory requests value..
pdcDomainPOD.limits.cpu: Set this to the maximum number of CPU cores the pod can utilize.
pdcDomainPOD.limits.memory: Set this to the maximum amount of memory a pod can utilize.

In your oc-cn-op-job-helm-chart/pdc/vpa_values.yaml file, set the request and limit values for the PDC domain job:
- pdcDomainJOB.requests.cpu: Set this to the default CPU request value.
- pdcDomainJOB.requests.memory: Set this to the default memory requests value.
- pdcDomainJOB.limits.cpu: Set this to the maximum number of CPU cores the pod can utilize.
- pdcDomainJOB.limits.memory: Set this to the maximum amount of memory a pod can utilize.
Run the helm upgrade command to update the release:
```
helm upgrade BrmReleaseName oc-cn-helm-chart --values OverrideValuesFile --namespace BrmNameSpace
```
where:
- BrmReleaseName is the release name assigned to your existing oc-cn-helm-chart installation.
- OverrideValuesFile is the file name and path of your override-values.yaml file.
- BrmNameSpace is the namespace for your existing BRM deployment.