Setting up Initial SWIFT Dashboard Admission

After creating a SWIFT example, connect to the example and execute the below control to set a password for the 'admin' user.

# sudo swiftcli user alter admin --password < password_of_your_choice >

Login to the SWIFT dashboard

To access the SWIFT dashboard, use the URL:
https://<swift-host-ip>/swift/dashboard

Username: admin

Password: <password_set_in_prerequisite_step>

If you have logged in successfully, then congratulations! You lot are now ready to drift the Kubernetes/OpenShift applications to the Azure Kubernetes Service and/or enable DR/backup.

Downloading Operations Guide/Get Additional Help

If you need more help, download operations guide from login page,

Or if you lot are already logged in and so, Click on Assistance > Help.

Upload TRAI Image to your Azure Container Registry

TRAI stands for Transient RackWare Amanuensis Image. TRAI is an sectional container image deployed with the SWIFT. It is used by the SWIFT server to deploy under your SWIFT managed Kubernetes or OpenShift cluster for the transient sync time. To know more about TRAI epitome, delight check the "SWIFTOperationsGuide.pdf"

The TRAI image needs to exist uploaded to the container registry for the SWIFT managed Kubernetes or OpenShift cluster. It is an one-time configuration stride. The beneath section highlights steps for uploading TRAI paradigm to Azure Container Registry (ACR). If you are managing any not-Azure clusters under SWIFT (like you lot source cloud or on-prem cluster for migration, for example), so you lot can use the SWIFT Operations Guide for specific steps. The steps overall remain the aforementioned for uploading TRAI epitome to any registry blazon.

Note: It's not mandatory to use ACR registry and you lot can use a container registry of your choice. Just make the TRAI image bachelor to the source and target namespace by setting up the image pull secret with similar steps as below.

Upload TRAI Image to ACR

  1. Connect to ACR with username and token

# docker login < registry-name >.azurecr.io

Here you will need to enter your container registry'southward name. This volition prompt yous to enter the username and password values which are as follows:

Username: < service main'southward application (client ID) >
Password : < service principal's countersign (client hole-and-corner) >

  1. The TRAI image for the corresponding SWIFT version is deployed along with the SWIFT. You tin can find it at /opt/swift/traipod/rackware-trai-docker.tar.gz on your SWIFT server. Copy the TRAI image tar file (mentioned in a higher place) from the SWIFT server to a host where you have the 'docker' customer installed and configured.Alter the directory to which the TRAI paradigm is copied.
  2. Execute the below command to load the prototype. With 'docker images' command, verify that image is loaded.

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

REPOSITORY TAG IMAGE ID CREATED SIZE
rackware-trai Release-1.1.0.340 148d70c65ab7 18 hours ago 837 MB
  1. You volition come across the tagged image loaded in the output to a higher place. Utilize the TAG field displayed in the stride 3 output and run below command to tag the image for your ACR registry.

# docker tag < image-id >< registryname >.azurecr.io/< namespace >/< epitome >

Annotation: Namespace tin can be empty if yous choose to load your paradigm in root namespace.

Example:

# docker tag 148d70c65ab7 myregistry.azurecr.io/mynamespace:release-i.i.0.340

  1. Push button the image to ACR.

# docker push < registry-proper name >.azurecr.io/< namespace >/< image >

Instance:

# docker push myregistry.azurecr.io/mynamespace:release-1.i.0.340

  1. Once the TRAI image is uploaded to your private registry. You need to brand information technology bachelor to the source and target cluster namespaces that you are going to migrate or set upward DR on. To exercise this, configure the paradigm-pull secret in the namespace.

    Note that there are multiple ways to make a container image available to the Kubernetes cluster and recommended way for SWIFT is to gear up upwardly anImagePullSecrete in each namespace. The below steps highlight setting upward such a underground.

  1. Connect to the K8S/OpenShift source cluster. Create an image pull hole-and-corner in the in the namespace which you are going to migrate

# kubectl --namespace < app_namespace_to_migrate > create secret docker-registry < secret_name > --docker-server=< registry-name >.azurecr.io --docker-username=< client-id > --docker-countersign=< customer-secret > --docker-email=< user-email >

Example:

# kubectl --namespace app1 create clandestine docker-registry acrsecret --docker-server=myregistry.azurecr.io --docker-username= 'b8cef2ab-f259-4bc2-ad33-fe84e3e40522' --docker-password= '4yT7Q~cK2fgkG38MEro8hTm5Y_WSy-lvSS38K' --docker-email='swift@rackwareinc.com'

  1. Follow the same process for all namespaces that yous want to replicate or set up DR on.
  2. Annotation down the uploaded TRAI image name and version from the registry and the image-pull secret created on both sides of clusters. Y'all will employ those two inputs for sync configuration later. You can also optionally configure these two inputs equally defaults nether SWIFT managed cluster (from SWIFT cluster assistants card and Config pick of the SWIFT dashboard), and so you don't have to input these for each sync or replication run.

For the above case,values to note will be following:

TRAI Image name: myregistry.azurecr.io/mynamespace:release-1.i.0.340

Prototype pull secret: acrsecret