In the Swift agentless solution, deploy the TRAI when starting the sync and delete the TRAI once the sync is finished.     


TRAI’ is an exclusive container image pod that is temporarily deployed by SWIFT on both the source and target clusters during the sync process.


- if u want to more about sync, check this KB <kb link>

            Index : How to configure

           

How it works?


1. This is a pod. It will be installed on both the server and the target cluster.

2. Once Traipod is deployed, a secure and encrypted communication channel is established. Data is transferred from the source Traipod to SWIFT, and then from SWIFT to the target Traipod. This ensures secure end-to-end data transfer between the source and target.

3. TRAIPOD uses a range of ports for communication. This port range can be customized using SWIFT. If the user wants to use specific ports, they can configure this in the 'TRAI Ports' section within SWIFT. You can either select the 'Auto Select Ports' option or choose 'Specify Port Range'. If you choose to specify the port range, you must manually enter the service’s default ports within the range of 30000–32767. Please refer to the screenshot below for guidance.

4. The following screenshot appears when you initiate a sync. The options shown below will be available under the 'TRAIPOD Options' section. 



5. Also, note that whenever you specify the port manually, the control and data ports should be the same on both the source and target sides. Please refer to the screenshot below for better understanding.


                         

6. SWIFT deploys transient pods and services on both the source and target sides. Users have full control over the resources used by the TRAIPOD, including CPU, memory, and network bandwidth. To configure these, go to 'Advanced Options' > select 'TRAI Config' > then set CPU/Memory Configuration and Bandwidth Throttling as needed.





                                

 Import TRAI image to private docker registry. 

  • The ‘TRAI image’ is deployed with SWIFT. The location is /opt/swift/traipod/rackware-trai-docker.tar.gz in SWIFT server.

  • There are few steps to import the TRAI image as below.

    1. Copy the ‘TRAI image’ tar file from the SWIFT server to the host where you have the docker client installed.

    2. Go to that directory where you have copied the above image.

    3. Run, 

      docker load <rackware-trai-docker.tar.gz>


    4. The image will be imported with default tag.

    5. Also, you can tag the image and assign it to registry where you want to push it.

    6. Run, docker image tag rackware-trai:<version>private-registry:latest (<version>  will be default version, you can find this with ‘docker image ls’ command)

    7. Now push the image to your private registry.

    8. Run, docker push private-registry:latest

    9. Also note that you will have to perform the above steps after a new SWIFT installation. If SWIFT is upgraded, a new ‘TRAI image’ will appear.




            Making the private registry available for namespace

      •         Once you push the ‘TRAI image’ to private registry then it should be visible to the namespace also.

      •         There is a step below to configure image-pull credentials within a namespace from one container platform to another.

                            a. Step1: Connect to the server where kubectl is working.

                           b.         Step2: Create a secret to get docker registry credentials.:  kubectl create secret docker-registry regcred --docker-server=<your-registry-server> --docker-username=<your-name> --docker-password=<your-password> --docker-email=<your-email>




        Configure TRAI details for Cluster in SWIFT.


        • After creating private registry and secret for cluster, then now you must provide those details in ‘TRAIPOD Config’ in SWIFT.

        • TRAI image will be used for creating staging POD while sync. You must enter the details of image name; version tag and image pull secret in SWIFT during sync configuration. Please find below snippet.



        • Alternatively, you can use the image registry in the ‘TRAIPOD config’ section. However, you need to discover an image registry first in the ‘container registry’ section. We support multiple container registries, e.g., Docker Hub, AWS, OCI, GCP, etc. Please find below a snippet for the reference of Image Registry under the ‘TRAIPOD Config’ section. Here, we have already created a ‘Docker registry’.

        •  just must select the dropdown option in both sides.



        • Now you can start the sync. The ‘TRAIPOD’ will be installed at both the source and destination for staging purposes. And data will be transferred from the source to the destination in a secure manner.