Agenda

Devops Overview
Definition
How to Implement
Devops Automation
Infrastructure
Deployment
Testing
 Devops Overview
What is DevOps What is required for DevOps implementation
Devops is a software development method that makes For Devops implementation companies need to adopt
companies to adopt new principles, practices and Devops Culture and Automation tools/technologies with
technologies which help developers, QA and operations focus on communication, collaboration, integration and
team to work together and deliver better Quality cooperation between IT and Operations team that should
software in lesser time and risk create continues Deployment/Delivery environment

Adopt Culture (C)

Implement Automation (A)

Measure Implementation
(M)

Share Everything (S)

 Devops Implementation
Sharing
Adopt Devops Culture
 Improve transparency by creating culture where team
 Implement Agile methodology. Kill long shares ideas, Project Goals and objectives, problems,
duration deliveries with break down of Responsibilities, Knowledge and most important success and
requirements in small continues and failure
meaningful deliveries

 Bridge IT and Operations by collaboration

and highly communicative working Adopt Devops Automation
Environment
 Automate Infrastructure
 Create cross functional team - - Create Scalable, always available servers
which utilizes 100% hardware resources and
(analyst, developer, testers ,operations…..)
reduces provisioning time for creation of
with skilled, flexible and problem solving
software development environments
resources. - - VMware, Citrix, Oracle, Linux Vserver,
Delphix………

Measure  Automate Code, Configuration and deployment

- - Always create deployment packages
Which deploy full functionality as executable
• Measuring what is implemented is extremely important
And reduces human error risk
to for any organization. Right matrices are vital for
- - Chef, Puppet Labs, Jenkins…......
Devops implementation Success
• Implementation should be measure on speed of  Automate Testing
deliveries, customer response, frequency of failure , - - Fully automate to reduce execution time
failure fix time Etc. and human error
- - HP QTP, Selenium, Jenkins, Oracle ATS………….
• Measure criteria should help to find out how Devops
implementation can be improved, modified or extended.
 Next Topic

Devops Overview
Definition
How to Implement
Devops Automation
Infrastructure
Deployment
Testing
 Automate Infrastructure
Why Automate Infrastructure
Agile development model requires multiple teams to work parallel on continues incremental deliveries which requires instant
provisioning of multiple copies of development and QA environments. Automation of infrastructure provisioning helps
individual teams to instantly create their own instances without any help from server administrators, it also helps team to
work on near production environment which improves quality and reduces risk of failure
How to Automat infrastructure
Cloud Computing :- Buy IaaS (Infrastructure as a services) IaaS providers can easily provision development and QA
instances on need bases
Virtualization :- implement virtualization software for in premise servers, virtualization software can create
Multiple instances and helps 100% usage of purchased hardware resources
Problems with ERP Infrastructure
 Cloud computing will not work because of big size of ERP
database and also current investment for in premise servers.
 Virtualization works fine to provision four computing
resources CPU, RAM, Storage and Network and retains prior
investments but it does not understand ERP applications and
databases running on these resources
 Virtualization faces challenges to provision development and
QA environment instantly on need bases as copy and refresh of
What is virtualization ERP suites takes several days and it has dependency on server
• Today’s x86 servers designed to run on only administrators
single operating system at a time, which requires to
deploy many servers running just 30% of its capacity  ERP applications has big size of production database and
• Virtualization software enable several operating replicating it to multiple instances required big storage which is
system and application to run on one physical 10 time bigger than actual production server storage size
server by creating virtual machines which uses as  Because of all above issues Software development team
much of host’s computing resources as required. works in outdated environment and faces more issues in
production
 Delphix VDB (Virtual Database)
What is VDB – Virtual Database What is Delphix
VDB is multiple cloned copy of source Delphix is Daas (Data as a Service) platform that brings virtualization
database which shares storage with source benefit to in premises ERP applications like SAP, J D Edwards,
and other VDB. Each VDB maintains its own Peoplesoft, Oracle E-business suite. It provides self service database
provisioning service for internal developers to create databases on-
read/writable changed version without demand
impacting source or other VDB. VDB is
Delphix captures and stores compressed copy of production database
created with almost no storage and it including ongoing changes . From this data footprint it can provision
accumulates only changed blocks during virtual database for different development and QA instances. This
usage virtual database will use storage spaces only for changed data

Traditional Environment Virtual DB Environment

VDB Dev : 1 GB
Dev :1TB

QA :1TB
VDB QA : 1 GB

Production-1TB Production-1TB

Reporting: 1TB VDB Reporting : 1 GB

Compressed full Prod Copy : 1/3 TB

 Delphix VDB Creation
Detailed VDB (Virtual Database) Creation Process

1) Crete initial full copy of production application Install Delphix engine on separate
machine and provide source application
and destination storage
Delphix will create initial full copy of
production application at destination
No impact on production operation as
it makes one time full copy as additional
application accessing database
Full snapshot in 1/2 time of traditional
refresh and also one time only

2) Compress and store collected data as initial footprint Delphix will copy original data
compress it up to 30% and stores in
destination storage
 Delphix VDB Creation Continued…
Detailed VDB (Virtual Database Creation) Process

3) Delphix stays in sync with production by collecting only It maintains synchronization with source
changed data databases based on configurable policy (E.g.. 1
day, 1 hour)
It maintains TimeFlow of source data changes
– a rolling record of file and log changes retained
by policy (E.g. 2 weeks, 1 Month)

TimeFlow

Week1 Week2 Week 3 Week 4

Delphix Engine
D 4
a W Delphix Storage
i
B F G A
H e
l l F B e
y o C k
S c H F
y D
k R
n G E
s e
c t
e
Redo Logs n
t
i
o
n
 Delphix VDB Creation Continued…
Detailed VDB (Virtual Database Creation) Process

4) Create any number of virtual database that can run VDB can be provisioned from delphix
independently with their own version. server within the Retention Window.
VDB can be created in minutes
Created with almost no storage as
TimeFlow initially it will use data from compressed
and shared storage
Week1 Week2 Week 3 Week 4 Multiple VDB can be created from any
Delphix Engine point in time from the TimeFlow
Each VDB acts as read/write copy of
B F G A
H database. It Maintains its own change
l F C
data blocks and shares unchanged data
o D blocks from shared storage
c H F G E
k
s

Redo Logs

VDB : Dev VDB : QA VDB : Reports

 Delphix Features
It creates compressed copy of production database and
runs multiple copies on single server saves storage and
utilizes 100% computing resources of the server

VDB (Virtual
Database)

It reduces development and

Provides API support to Support to
Fast QA instance provisioning
configuration management Configuration
Provisioning time by 80% and supports
tools like Chef and Puppet Tools
full and incremental refresh
labs
Delphix
Features

Provides automated data

Provides inbuilt support to ERP Data masking masking for development
oracle E-business suite and Virtualization
and QA instances refreshed
SAP with GUI tools and
from production
command line packages
Database
Branching

Create new VDB by branching existing VDB instance

that will copy all changes done on source VDB from
that point of time
 How it can help us
Fast Provisioning :-
• Delphix can refresh the instance in few hours so team can work on near production environment. It has
also feature of fast incremental refresh which can help support team to work on any production issue
directly in support instance

Near Prod Environment for Each Project :-

• One team do not need to wait on another team to finish testing for refresh . Virtualization can easily
create new instances with minimum use of computing resources and also can release resources when one
team finishes testing.

Save Storage :-
• It creates compressed DB copy of production database and uses this copy to create virtual database(VDB).
VDB will stores only changed data so no need to size QA and development instance same as Prod.
Auto Masking
• The inbuilt masking feature of Delphix can help to update production email addresses and other
important data in non prod environment during provisioning
Need to Verify
• How Applying patch will work with VDB
• How DB code can be version and migrated to multiple VDB
• How OA Framework will work
 Next Topic

Devops Overview
Definition
How to Implement
Devops Automation
Infrastructure
Deployment
Testing
 Automate Deployment
Though deployment activity makes everyone panic in organization Devops insist continues deployment and delivery
which require organization to build deployment framework which is automated, fast, painless and human error free.
Manual or semi automated deployment framework is highly unreliable and can become biggest bottleneck in achieving
DevOps goals

Benefits of deployment Automation

Roadblocks on deployment automation It will help in creation of continues deployment
Developers think automated deployment is environment and helps to adopt/implement Devops for
unaccounted additional effort which will steal time from organization
their development activities
Deployment becomes much less human error-prone
Organization thinks developers should more and much more repeatable
concentrate on development rather creating deployment
scripts which are not visible to higher management Anyone can deploy the code so it eliminates person
dependency
Everyone has mindset that our deployment has many
moving parts and dependencies which can not be fully Any new functionality can be moved to any instance
automated very fast and painless so more time for regression
testing and bug fixing

Consideration
• Fast :- If company automate infrastructure provisioning and its available in minutes, deployment should
be completed less than 50% of instance provisioning time.
•Repeatable and consistent :- Create single deployment process which is repeatable and consistent
•Package Driven :- Create deployment package for each delivery by consolidating and organizing depended
deployment activities in single package which should be independently executable in any instance and
Can be roll backed at any point of time.
•High Visibility and Centralized Control :- Clear visibility for what is deployed, where it is deployed and
deployed by whom, it should be centrally controllable and should give clear picture of deployment
state (success and Failure)
 R12 Deployment Process
Oracle E-Business Suite deployment is consists of four deployable objects. Code (PLSQL,DDL,WS,Java), AOL (DFF, Value
Set, Concurrent Request), Standard Setups and Patches. There are available tools like Kintana, Migration LogiK, Dell
Stat that helps to version, package and deploy DB and AOL objects but there is no tool that help automation of
Standard E-business suite Setup.

E-Business Suite deployable objects Current Implementation Process

 Code and new AOL objects are migrated through Kintana
Code AOL E-Buss
Patches that also line by line
Objects Objects Setups
 Changed AOL objects and E-buss setups are maintained
in AP 322 and migrated Manually
 Patches are maintained in Excel sheet during migration
Code Version Control
across the instances
 RRP has Multiple manual steps and required
coordination with multiple teams
 Always required to review and verify changes after
execution of RRP to find and correct human errors
Package-1 Package-2
Kintana Code Repository AP 322 AD Utl Devops Requirement for Deployment Automation
•Deployment process should not include any manual or
Release semi manual activities
Rollout •All deployment resources should be packaged together
Plan
and should be executable by resolving dependencies by
itself
• It required to package technical and functional objects like
oracle patch which can be apply with single command
execution
Dev SIT Prod
 R12 Deployment Automation Options
Currently we have only below options to achieve deployment Automation Requirements for Devops

Use application change management pack for code, AOL, E-Bussiness setups and Patch.
Application Change Management Pack

E-Buss
AOL Code Patches
Setups

Application Change Management Pack

Change Management Tools
 Customization Manager
 Patch Manager
 Setup Manager

 Packages custom code and configuration into custom packages that can be migrated across instances using
patch Manager or AD Utility
 Can be linked with any code version tool
 Deploy standard oracle patches across the instances from GUI tool Patch Manager
 Extends i-support capability to migrate functional setups across instances
 Licensing is the problem