File System Configuration for Deployment Manager in Openshift Environment

General
, , ,
1

We’re using the On-Prem Cloud (VM Based Deployments) with OpenShift Containerization Platform. Imported the Deployment Manager in Development Environment itself.

In-order to create a file system as repository, Facing the issue.

  1. Configured a test folder path in Repository configuration from Record - Sysadmin - Repository

  2. Found that, Test folder is from the PV attached to container.

Question: How do we make sure that a shared file system is configured in OpenShift Containerization for Deployment Manager to connect with Development, QA and Production Environment?

2

@Kishore Sanagapalli

Applied Solution in our environment:

  1. Mount an NFS Share to a cluster and make sure root level access provisioned.

  2. A new storage class defined on the same NFS Share and enabled to access by the required Openshift Cluster.

  3. Defined a new PV and PVC in shared mode and attached to the required Project in Openshift.

  4. Added / mapped user: pegauser to the NFS share to access / modify the content in the PVC.

  5. Configure /opt/pega/ as a resource path in Deployment Manager and check the Test Connectivity.

  6. From POD terminals, you may check the pegauser permissions of NFS share mounted on cluster using linux commands: ls -lrt & df -h.

Note:

  1. NFS share provided with shared mode for PVC, does not require any POD creation to map as it’s mapped the NFS Share being mounted on Cluster Directly.

  2. Please do not include the New Storage class defined on an NFS Share in-specific for Deployment Manager needs in the values file storage class section.