Application deployment automation (XebiaLabs)

Deployment Automation
for Software Applications
Deployit. Automating your Deployment Process

Agenda

 Introducing XebiaLabs

 Today’s deployment challenges for IT organizations

 Vision on deployment automation

 Zooming in on the deployment function

 Deployit: world-class deployment automation solution

XebiaLabs

XebiaLabs provides
a deployment automation solution
to automate the application deployments
to middleware environments

XebiaLabs – company overview

2001 ~ 2007 2008 2009 2010 2011 and beyond

XebiaLabs Release of International Expanding
Xebia founded KLM as 1st customer
founded Deployit v.1 expansion customer base

Scandinavia
Netherlands
Germany

France
USA

India

XebiaLabs serves customers around the world

Deployment automation defined

Deployment automation is a
series of configuration tasks
to be processed in the right order
to get an application running correctly
in a middleware environment

Application deployments at 10,000 feet

MyApp

Challenges for deploying Java applications today

 Increasing complexity of target landscapes
 Heterogeneity in middleware environments
 Lack of standardization of deployment procedures
 Clouds & virtualization on the rise



 Increasing complexity of applications
 From monolithic to componentized applications (SOA)




 Acceleration of change
 New technologies release cycles
 Agile methodologies
 Business pushing for frequent functional upgrades




 Acceleration of change
 New technologies release cycles
 Agile methodologies
 Business pushing for frequent functional upgrades
 Organizational
 Difference in mindset between Development and Operations
 Lack of ownership (hand-over between Development and Operations)
 Lack of governance of and security on environments

Pitfalls for a reliable deployment process

 Infrastructure design ignores deployment tasks

 Deployment is overlooked by developers

 Development, test and deployment environments differ substantially

 Deployment manuals are seldom used properly

 Middleware environments are out-of-synch

 Incomplete view of all existing configurations

 Deployment itself is not tested

 Mindset: “Fully automated deployment is simply not possible”

Deployment Automation of IT capacity
Deployments consume lots

Did you know…

... an average software
engineer spends around
200 hours per year on
redeploying his own
applications?

Source: ZeroTurnAround, July 2009

Deployment Automation Level Agreements
Deployments impact Service

Did you know…

... about 28% of all server downtime
is caused by config changes, updates
or deployments?

Source: The Sources of Web Application Downtime, 2009

Deployment Automation
Deployments often are hidden costs for IT organizations

Did you know…

... an average company invests
over $850,000 per year on
creating & maintaining deployment scripts?

Source: The Sources of Web Application Downtime, 2009

Deployment Automation in focus new challenge for IT
Analysts recognize deployment as the

Most IT organizations today are in fact
“throwing people at the problem”.
However, they should be putting in place solutions that will
make it possible to filter the complexity so that it becomes
controllable and manageable.

Organizations need to embrace an automated application
deployment solution to ensure efficient, repeatable,
accurate and reliable application deployments.

XebiaLabs’ vision on deployment automation

… having one streamlined, integrated, end-to-end software
deployment process, tailored by my middleware specialists:



 Streamlined: standardized way of working for developers
and operators based on in-depth deployment knowledge



 Integrated: unleashing full potential of existing investments
in development, release, and change management tools



 End-to-end: from package composition up to actually
releasing software to my target environments



 End-to-end: from package composition up to actually
releasing software to my target environments
 Tailored: fully adaptable to my applications, environments
and my preferred way-of-working

Deployments are end-to-end processes

A deployment is a complicated, context-dependent process:

 Installing applications

 Configuring resources

 Configuring middleware components

 Starting/stopping components

 Configuring the installed application for the
target environment

And all of these in the right order …

Deployit: bridging the deployment gap

Continuous Monitoring
Build
CruiseControl,
Hudson…

IDEs
RAD,
Eclipse…
SCM
ClearCase,
SVN...

Interactive
Release
Management

?
Build Change
Maven, Ant… Management

Configuration
Management


Build
CruiseControl,
Hudson…

IDEs
RAD,
Eclipse…
SCM
ClearCase,
SVN...

Interactive
Release
Management

?
Build Change

Development is automated
Configuration
Management


Build
CruiseControl,
Hudson…

IDEs
RAD,
Eclipse…
SCM
ClearCase,
SVN...

Interactive
Release
Management

?
Build Change

Development is automated Operations is automated
Configuration
Management


Build
CruiseControl,
Hudson…

But: manual transition
IDEs SCM Release
RAD, ClearCase, Management of software packages
Eclipse… SVN...
between Dev & Ops…

Interactive
Build Change

Development is automated Operations is automated
Configuration
Management


Build
CruiseControl,
Hudson…

IDEs SCM Release
RAD, ClearCase, Management
Eclipse… SVN...

Interactive
Build Change

End-to-end automation for all Development Configuration
Management
and Operations’ activities !

Zooming in on the deployment function


End-to-end solution,
integrating with Build and
Release Management
Systems


Self-service deployments to
Development, Test and
Acceptance environments


Compares and synchronizes
target environments


Support for post-
deployment tests


Hooks to system
management and
monitoring tools

Deployit: Capabilities

Deployit: a single deployment platform for Development & IT Operations

 Support for reliable ‘self-service’ deployments
 Automatic discovery of servers, clusters and nodes
 Enables reliable composition of deployment packages
 Synchronizes and compares target environments
 Promotes applications from one environment to another
 Out-of-box support for all major middleware stacks
 Support for clouds and virtualized environments
 Traceable processes with audit trails and reporting
 Both CLI and task-based UI based on Flex
 Secure, role-based solution

Deployit: Architecture

 Agentless, scalable architecture based
on a Unified Deployment Model

 Easy to extend and customize via PluginAPI

 Integrates with CMDBs and build systems

 Integrates with Eclipse and Maven

 Works with all leading middleware:
 IBM, Oracle, JBoss, Tomcat etc

Customer case: KLM/AirFrance

KLM chose Deployit to better manage all Java application deployments in
their Service Oriented-Architecture.

“Deployit provides us with a very powerful
system that helps reduce repetitive work, boost
productivity and improve quality.

Now, we’re able to focus more on developing
advanced online functions for our internal and
external customers.”

Ronald Bosch, Director Web Systems

Situation: KLM WebSystems works on 35 projects simultaneously, leading to around 200 Java
EE deployments per week. Previously, over 70% of all deployments failed.
This has now been drastically reduced, leading to savings of up to 150 manhours per project.

Customer case: CoachClub

CoachClub chose Deployit for reliable deployments in an agile
development environment

Based on my own experience, I knew that a classic
Scrum development Operations
solution, based on scripts could not bring the guarantee
that our application deployments would be done in time
and in a predictable manner.
Stephane Coussement, CIO

The ROI on Deployit was realized within 6 months. We
have chosen the subscription model because it fits our
investment capabilities better.
Benoît Pharisien, CFO

Situation: CoachClub carries out 2 deployments per month. Their SLAs require an uptime of
99.98%. Their technical team wants to avoid unreliable, risky and chaotic deployments, while
the CFO wants to keep costs down to the bare minimum.

What is your reason to evaluate Deployit?

1. We want to carry out our own deployments (e.g. to test systems)

2. We want to avoid error-prone and time consuming scripting

3. We want to migrate our applications from one platform to another

4. We want to spend our time on added-value tasks

5. We face many dependencies between applications, servers or teams

6. We want to support incremental updates to our SOA-based applications

7. We want to support an Agile development approach with frequent releases

8. We want to be ITIL and SOX-compliant

9. We want to eliminate hidden costs in our IT organization

10. We want to reduce time to market of our business critical applications

Let’s get in touch!

Contact us at:
twitter.com/xebialabs
blog.xebialabs.com
youtube.com/xebialabs
www.xebialabs.com

Application deployment automation (XebiaLabs)

Recommended

More Related Content

What's hot (20)

Similar to Application deployment automation (XebiaLabs) (20)

More from XebiaLabs (20)

Recently uploaded (20)

Application deployment automation (XebiaLabs)