Presents the current state and proposed state for Application lifecycle of Liferay Applications. Introduces DevOps concepts and explains how they can be applied to Liferay application. Also includes Ansible scripts for deployment Automation.

1. DevOps Pipe Line for Liferay ApplicationsDevOps Pipe Line for Liferay Applications
02-Jan-2017
Maruti Gollapudi
@gmaruti

2. AgendaAgenda
DevOps
Current Process
Liferay Application – Challenges
Recommended Process

3. DevOps - WhyDevOps - Why
 DevOps reduces the
cycle time from
development to
deployment
 With end to end
automation, failure rate
is reduced
 Frees up some time for
team which can be
used for innovations!
https://puppet.com/resources/white-paper/2016-state-of-devops-report

4. DevOps - WhatDevOps - What
 Driving principles
◦ Maximize left to right flow ofWork from
Development to IT Operations to Customer.
In order to maximize the flow we need small
intervals of work, never passing defects to
downstream.
◦ Constant flow of feedback from right to left at
all stages of the value stream
◦ Create a culture that forests continuous
experimentation (which helps continuous
innovation) and understanding that repetition
and practice is pre requisite to mastery.This
https://en.wikipedia.org/wiki/The_Phoenix_Project_(novel)

5. DevOps - WhatDevOps - What
A Culture and mind set for collaborating between developers and operations
http://www.slideshare.net/thekua/devops-from-the-ground-up
Plan Code Build Test Release Deploy Operate
DevOps
Continuous Delivery
Continuous Integration
Agile Development
• Automate Provisioning - Infrastructure as Code
• Automate Builds – Continuous Integration
• Automate Deployments – Defined Deployment
Pipeline and Continuous Deployments with
appropriate configurations for the environments
• Automate Testing – Continuous Testing,
Automated tests after each deployment
• Automate Monitoring – Proper monitors in place
sending alerts
• Automate Metrics – Performance Metrics, Logs
Jira
Rally
SVN
GIT
Jenkins
Hudson
Junit
Selenium
QTP
Chef
Puppet
Ansible
Data Center
Public Cloud
Monitoring
DevOps helps automating end to end flow from development to
deployment and monitoring.

6. Liferay Application LifecycleLiferay Application Lifecycle
Traditional FlowTraditional Flow
Develop Integrate, Test
Code
Bug
Report
Pull Code
Build
Run Test
Version Control
Package
Release, Deploy
Monitor
Operate
Dev
QA
Prod
Deploy
• Provision
• Install &
Configure Liferay,
java, MySQL DB,
Monitoring s/w
• Deploy
• Alert
• Add / Remove
node to Linux
Cluster
Check In
Test fail Test Pass
Developer
Manual
Trigger of
Build and
Test
Tester /
Build Rep
manually
logs in
Errors
Manual
Trigger of
Build and
Package
Process
Ops team
sets up
environment
manually
and triggers
deploy
script
Post
Deployment,
Themes and
Layouts are
manually
configured Ops team
checks the Log
files and raises
report in Jira

7. Liferay Application LifecycleLiferay Application Lifecycle
Traditional Flow - ChallengesTraditional Flow - Challenges
There are few tasks that need to be initiated or
require physical resource.This could potentially cause
delays due to non-availability of concerned resource.
The tasks that are done manually are error prone and
don’t guarantee to be consistent. In case of manual set
up of environment it is possible to install wrong
version of S/W.
One of the critical component of the Liferay
application is Themes and Layouts. In general these are
configured manually by development team even in
Production, post application deployment.

8. Liferay Application LifecycleLiferay Application Lifecycle
Recommended Process - DevOpsRecommended Process - DevOps
Develop Integrate, Test
Code
Bug
Report
Pull Code
Build
Run Test
Version Control
Package
Release, Deploy
Monitor
Operate
Dev
QA
Prod
Deploy
• Provision
• Install &
Configure Liferay,
java, MySQL DB,
Monitoring s/w
• Deploy
• Alert
• Add / Remove
node to Liferay
Cluster
Check In
On Check In
Test fail Test Pass

9. Liferay Application LifecycleLiferay Application Lifecycle
Recommended Process – Dev, Build &TestRecommended Process – Dev, Build &Test

10. Liferay Application LifecycleLiferay Application Lifecycle
Recommended Process – Deploy & MonitorRecommended Process – Deploy & Monitor

11. DevOps –Tools used in the SolutionDevOps –Tools used in the Solution
Tool Purpose
Eclispe IDE for development
Junit Unit testing framework
Java Development Language
GIT, SVN Code repository
Jenkins Continuous integration tool
Selenium Automated testing tool
Jira Bug report tracking tool
Puppet, Ansible Configuration and Infrastructure management tools
Zabbix System monitoring tool
Logstash Monitor and parse log files

12. Automated Activities & CodeAutomated Activities & Code
Using CI/CD tool jenkins along with Ansible playbooks, we
achieved automating the end to end flow.
The new process enables -
◦ Build and generate "build once, deploy everywhere" Liferay
application packages
◦ Quick and easy setup of environments (Dev,Test, QA and Prod)
and automated deployment and installation of the software on
new servers including automatically configuring Layouts and
Themes
◦ Automated deployment of upgrades on existing servers
◦ Execute multiple build, release, and deployment jobs
◦ Provision and configure nodes
◦ Monitor and Report
◦ Backup and Restore

13. CodeCode
 List of Ansible roles and their brief descriptiion
◦ mysql-db-liferay-user: Installs mysql and creates mysql user
◦ liferay-portal: Installs Java and Liferay portal
◦ portal-sdk: Deploys the application into liferay
◦ backup: Creates Portal backup snapshot
◦ restore: Restores Portal snapshot
 List of utility shell script to trigger different Ansible roles
◦ portal_deploy.sh: Run to install mysql, liferay and deploy the portal
and application
◦ portal_update.sh: Run to update the application on portal.
◦ portal_backup.sh: Run to create a snapshot of the portal application
◦ portal_restore.sh: Run to restore the portal snapshot
 Above code is available at https://github.com/gunduv/portal-
deployment