Post-Encryption Migration Phase
In the post-encryption migration phase, SCM updates the Flux-managed Siebel CRM manifests to the target image level, triggers Flux reconciliation, scales the SES workloads back to the desired capacity, and confirms that the environment returns to a healthy Running or Ready state. This phase includes the following tasks:
Running the Post-Encryption Migration Script
You must run the post_openssl_encryption.sh script to perform the
post-encryption migration tasks.
To run the post_openssl_encryption.sh script:
- Go to the
cmappdirectory:cd /home/opc/siebel-cloud-manager/scripts/cmapp - Execute the post-encryption migration shell
script:
bash post_openssl_encryption.sh - Enter the ID of the environment that you want to encrypt.
The post-encryption migration script performs tasks such as the following:
- Roll out new target Siebel version pods for Siebel Server (for example,
edge). - Scale the Siebel server (for example,
edge) StatefulSet to the desired replicas.
- Roll out new target Siebel version pods for Siebel Server (for example,
Verifying Post-Encryption Migration Updates
You can verify that the post-encryption migration script ran successfully as follows:
- Verify the status of the post-encryption migration job, as follows:
- Load the Kubernetes profile for your
environment:
source ~/siebel/<ENV_ID>/k8sprofile - Check that the SES pods are
running:
kubectl -n <env_namespace> get pods
- Load the Kubernetes profile for your
environment:
- Verify the logs. Look for a message such as "Post-steps completed successfully", which confirms that the post-steps completed successfully.