LAN/File Configuration in AC4

Prerequisites

Before configuring NFS storage in Adeptia Connect, ensure you have the following:

• NFS file share

Steps to Configure NFS Storage

1. Install NFS Feature on Server

   • Open Server Manager.

   • Click on the Manage option from the toolbar.

   • Select Add Roles and Features.

   • Click Next until you reach the Select Features page.

   • Select the Server for NFS option.

   • Click Add Feature.

   • Click Next and then Install.

   • Once the installation is complete, close the Server Manager.

2. Create and Share NFS Folder

   • Create a folder and go to its properties.

   • Select the NFS Sharing option.

   • Click on Manage NFS Sharing.

   • Click on the Permissions button.

   • Select the Read and Write option and click OK.

   • Apply and save the changes.

3. Mount NFS Folder on Cluster Node

   • To test folder access, go to the cluster node shell and run the following command:

     shell

     Copy code

     mount -t nfs -o vers=3 10.0.1.4:/NFSShare_Test /mnt/adeptia

   • Here, NFSShare_Test is the NFS folder, and /mnt/adeptia is the cluster folder where it is being mounted to sync.

   • Note: To unmount, use the command:

     shell

     Copy code

     umount -lf /mnt/adeptia

4. Backup Deployment

   • Before making changes, take a backup of the deployment mentioned in point number 6 below.

Configuration Files

• PVC YAML Reference: PVC YAML

• PV YAML Reference: PV YAML

Steps to Configure NFS Share in Adeptia Connect

1. Create PV YAML

   • Create a pv.yaml file with the following configuration, updating it as per your requirements:

     • PV name

     • Namespace

     • Storage

     • Path

     • Server IP

2. Create PVC YAML

   • Create a pvc.yaml file with the following configuration, updating it as per your requirements:

     • PVC name

     • Namespace

     • Storage

3. Deploy PV and PVC

   • Deploy the PV/PVC YAML using kubectl:

     shell

     Copy code

     kubectl apply -f pv.yaml -n <namespace> kubectl apply -f pvc.yaml -n <namespace>

   • Check the status of PV and PVC:

     • Persistent Volumes (nfs-pv) should be listed.

     • Persistent Volume Claims (pvc-claim-adeptia-lan) should be listed.

NFS Mounting on Deployment

1. Take Backups

   • Backup the following pods (deployments):

     • Adeptia-connect-ac-event

     • Adeptia-connect-ac-runtime

     • Adeptia-connect-ac-runtime-deployment-manager

     • Adeptia-connect-ac-webrunner

     • Adeptia-connect-ac-portal

     • Adeptia-archival-and-cleanup

     • Adeptia-connect-ac-listener

2. Update Deployment Configurations

   • Open the deployment of event and look for the property volumes.

   • Add the following lines after claimName:

     yaml

     Copy code

     name: pvc-claim-karmak-sandbox-lan persistentVolumeClaim: claimName: pvc-claim-karmak-sandbox-lan

   • Maintain the same structure and spacing.

   • Scroll up and look for the properties volumeMounts and add the following syntax under Container - Env:

     yaml

     Copy code

     mountPath: /mnt/adeptia name: pvc-claim-adeptia-lan

3. Save Changes

   • Save the changes and wait for the pod to be up with the new changes.

   • Verify the files inside the /mnt/adeptia folder by running:

     shell

     Copy code

     cd /mnt/adeptia

4. Repeat for Other Deployments

   • Repeat the same steps for the other deployments mentioned in point 6.

   • For adeptia-connect-ac-runtime-deployment-manager, in addition to the above changes, set LAN_VOLUME_ENABLED to true.

Final Verification

1. Verify Folder Access

   • Once all pods are up and running, log in to the Connect application and create FileSource/LAN source.

   • Verify folder access.