The document discusses a continuous deployment tool developed by Infobip, highlighting the software development process including test-driven development, continuous integration, and various components like SCM and CI servers. It details the drawbacks of manual deployments and introduces an internal deployment manager designed to improve service availability and automate deployment processes across multiple data centers. Future steps for enhancing the tool include deploying to Amazon Web Services, implementing smoke tests, and providing live log streaming.

1. Continuous deployment tool
www.infobip.com
Aleksandar Dostic
Emir Dzaferovic

2. Introduction
• Software development
• Test Driven Development
–Unit Testing and Integration Testing
• Built goes through compiling and testing phases
• Continuous Integration
• Data Centers and virtualization

3. CI Environment
• Source Code Management (SCM)
GIT, TFS, Subversion …
• CI Build Server
Apache Continuum, Hudson/Jenkins ...
• Maven Repository Manager
Archiva, Nexus, Artifactory ...

4. CI Environment
SCM (Git)
CI server (Jenkins)
Maven Repository Manager
(Atrifactory)
...
...
DC Artifactory:
Servers:
...
DC Artifactory:
...
DC Artifactory:
Servers:
......
Servers:
...
Data Center 1 Data Center 2 Data Center N

5. Manual Deployment Drawbacks
• Can be performed only by specialized people, usually engineers
• The incorrect versions of software can be shipped
• Quick rollback to old versions can be challenging
• Complex maintenance of security across servers
• Difficult or impossible to track who deployed what, when and where• Difficult or impossible to track who deployed what, when and where

6. Deployment Manager
• Internal tool for maintaining high level of service availability
• Manage of load balancing in private cloud
• Automated deploys on cross-platform environment
• Inter service connectivity configurator
• Properties file management

7. DEPLOYMENT PROCESS
LVS

8. DEPLOYMENT PROCESS (STEP 1)
LVS

9. DEPLOYMENT PROCESS (STEP 2)
LVS

10. DEPLOYMENT PROCESS (STEP 3)
LVS

11. DEPLOYMENT PROCESS (STEP 4)
LVS

12. DC Environment
ssh
ssh
Artifactory
ssh
powershell
gateway
session
session

13. Demo
www.infobip.com
Demo

14. Main Features
•¸Load Balancing:
−HAProxy (High Availability Proxy)
−Apache Httpd Load Balancer (Apache Module)
−MML Load Balancer (internal service)
• Operating Systems:
−CentOS−CentOS
−Windows Server
−Windows Failover Cluster

15. Main Features
• Service types:
−WAR
−NodeJS
−Java standalone
−Python
−DotNet−DotNet
−Infobip application bundles(internal package format)

16. Main Features
• Actions:
−Enable/Disable balancer route
−Start
−Stop
−Deploy
−Deploy configuration−Deploy configuration
−Revert
−Edit configuration
−View application log files

17. Infobip numbers
• 8 Data Centers
• 100+ Physical Servers
• 250+ Virtual Servers
• 98 Applications
• 284 Application Instances
FrankfurtWashington
Zagreb
Moscow
Lagos
Kinshasa
• 44 Balancers
• 569 Balancer Routes
• 100+ Developers
• 60+ Deployers

18. Evaluation
• 12785 enable/disable routes (every 2.47 minutes)
• 1770 Deployments (every 17.89 minutes)
• 18 days of deployment (manual 74 days) out of 66 in Q3
284300
848900
37 39
71
150 156
July August September
0
50
100
150
200
250
300
Total savings in July/August/September 2013: ~ 440
hours
hoursspent
DM
Manual
445 447
July August September
0
100
200
300
400
500
600
700
800
An evident increase in the number of deployments
in September 2013
# deployments

19. Future steps
• Deployment into Amazon Web Services
• Smoke test support
• JBoss deployment
• Live log streaming
• Access to server terminal

20. Thank you for your attention.
www.infobip.com