This document discusses an automated deployment strategy for artifacts and configuration files across clusters. It allows deployment to environments like ENV1, ENV2, and ENV* with turnaround times of just a few minutes regardless of cluster size. The process involves generating SSH keys for passwordless communication between nodes, using tools like rsync and Jenkins to deploy wars, configuration files, take backups, and restart services, while allowing for rollbacks. A trigger of a generic "P*" job drives the end-to-end process flow to prep, deploy, backup, and restart services on target nodes.

1. Naveen.S.R

2. Smarter. Faster. Closer.
Objective
Automated
deployment
of Artifacts
Automated
deployment
of CONF files
Cluster
deployment
• ENV1 ,
• ENV2
• ENV*
Turn around
time of few
minutes
irrespective of
cluster size.

3. Smarter. Faster. Closer.
Insights
3
Automated Deployment
SSH
Keygen
rsync
Jenkins
Password less
communication

4. Smarter. Faster. Closer.
Capability
Stop Service
Take backup
of essentials
Deploy wars
and conf files
Start Service
Rollback

5. Smarter. Faster. Closer.
Deployment Strategy
P1 Cluster
5
S1
S2
S3
S*
HostName
Release version
Generic Job Type
Pre-built
packages
S1 S2
S*
S3
P2 Cluster
S1 S2
S*
S3
Generic Jobs
Master Node Slave Node

6. Smarter. Faster. Closer.
SSH Keygen
Build server
login
Create Authentication
SSH-Keygen Keys on
Slave node
Create .ssh Directory on target
Upload Generated Public Keys to target
Set Permissions on target and for passwordless
communication
6

7. Smarter. Faster. Closer.
Process Flow on trigger of P* Job
Prepping prod package
Trigger P1 Job
Invokes generic Job
Executes on slave node
Slave node communicates to known
target node
Take backup
Stop service
Deploy artifacts
Start service
Roll back
7

8. Smarter. Faster. Closer.
Questions?
 newnaveen15@yahoo.co.in
8