WORKING WITH GFRT AUTOMATION

(KAKADU)
DEVELOPERS & APPROVERS GUIDE

ABOUT KAKADU
Kakadu is a complete Automation Solution providing end-to-end automation for L1 activities, Deployments, Job Monitoring and
Operations Calendar Maintenance.
This would provide the predictive timeline for Delay/advance system availability and provide Operations and Users with capability to
view and predict uptime for EGL, OBIEE and associated systems

LOGIN
Login to Kakadu is integrated with BNS LAM and hence one can use his own Scotia Id to login.

DEVELOPERS

DEPOYMENTS
The Application provides a framework to integrate existing Devops pipelines to more robust and customized approval process which
would be driven completely through email.

Menus for Deployments

The above three menus are for deployments for different Applications. The menus would be available based on the role grated to each
User.

Create Deployment

This menu is used to create a deployment request for a code version.

User would have a list of Applications assigned to the user as below.

Each Application would have list of Instance type for deployment (I,e; DEV/IST, QAT, PROD)
A change can follow one of the below two paths :
1. DEV > IST > QAT > PROD (Normal Changes)
2. QAT > PROD (Emergency changes)

Once the mouse is hovered against any Application the Deployment type would be dropped down as shown in screenshot below.
DEV/IST
QAT
PROD

Prod Deployments could be done only for those versions which are already deployed in QAT.
Once select IST/DEV or QAT. The below form needs to be filled up to start the deployment workflow.

Code Version: This is the Artifact version and could be obtained wither from ACCP if using Plato Acclerated Pipeline build as show
below :

OR
From Jenkins build as shown below :
External Change #: This is for reference is any external Change management system is used or ticket number for emergency changes
Project Name: The name of the project for which the change is done.
Package Description: The description of the package for approver. This would help approver to understand what changes are being
done and keep track for audit.
Scotia password: This is required to connect to Artifactory to download the code. This is not stored anywhere but just used to connect
to BNS antifactory to download the code.
Target Instance: This would give a dropdown for different DEV/IST/QAT instances available for deployment where the code needs
to be deployed.
Click on “SAVE” button to start the workflow for the deployment. This should trigger an email as shown below which would reach
the approver for that instance (e,g; IST owner would approve the changes for IST)
For PROD and QAT it would reach the Application owner.

The Approver would receive an email as below:

The Approver can Reject or Approve a change and based on that the workflow would continue to the Operations who would deploy
the code from email.
Once the deploy button on email is clicked the code gets deployed using the Jenkins deploy.sh file on the Server.
The detailed deployment report is sent to the developer as below.

APPROVERS
APPROVE DEPLOYMENTS

Approve Deployments is for Instance approvers to approve the deployment of changes in an environment. This would be done through
email. In case email is not working it could be done from the Application as well.
Select the Environment to Approve the deployment from the Applications displayed on the left-hand side.
Once selected it would display the list of changes pending approval as shown below.

Click on the to approve the deployment or to reject the deployment.

Once Approved it would go to the Operations team for actual deployment of code.
If Rejected the request needs to be raised again by developers to get the approval.

OPERATIONS
DEPLOY CODE

Deploy Code is used to deploy approved codes to Environments. This would be done through email. In case email is not working it
could be done from the Application as well.
Select the Environment to Deploy pre-Approved codes from the Applications displayed on the left-hand side.

Once selected it would display the list of changes pending approval as shown below.
Click on the to deploy the code or to reject the deployment to that instance.
If Rejected the request needs to be raised again by developers to get the approval.
The deployment could be done again if there is a failure.

DOWNLOAD & UPLOAD FILES

This Functionality is used to download and upload files from Server. Every file downloaded and uploaded is audited at the backend
and report is sent to respective supervisor for Audit control.

The menu to do the same is as below:

Click on the menu and the list of all Instances available to that user would be listed on the left hand menu as shown below:

Select the instance from where you want to list the files or upload files to and list of available directories would be shown as below:
Use the icon to upload files and to list files on that directory.

Download Files:

Once the list files icon is clicked. It would display all files available at that location as shown below:

Use the button to download that file.

Click on it and it would create the Audit request Id and the link to the file as below:

Right click on the icon and click “Save Link as.”

This would download the file to your system.
Upload Files:
To upload files, click on the icon on the directory page and this would give you the prompt to upload files as below:

Click on Choose File and select the file to be uploaded which would upload the files to the respective directory on the Server and
create an Audit request for the same.

DOWNLOAD & VALIDATE DATABASE OBJECTS

This functionality would be used by Developers to download/validate database objects post migration to check if all objects have been
migrated successfully.
Use the below menu to download/validate objects.

It would display the list of instances available for the user as below:

Click on the Instance to check the objects and click on the sign to start the validation:

Enter Object name and object type on the below screen:

And click on download and it should show the below page.

The status of the package ad body is valid as shown above. Right Click on the to download the objects.