Pre-Con Ed: Become a Power User of CA Release Automation to Get the Most out of Your Implementation

World®
’16
Become a Power User of CA Release
Automation to Get the Most out of
Your Implementation
David Fisher - Principal Consultant - CA Technologies
@DaveAtCA @CAWorld #CAWorld
DO5X18E
DEVOPS

2 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
© 2016 CA. All rights reserved. All trademarks referenced herein belong to their respective companies.
The content provided in this CA World 2016 presentation is intended for informational purposes only and does not form any type of
warranty. The information provided by a CA partner and/or CA customer has not been reviewed for accuracy by CA.
For Informational Purposes Only
Terms of this Presentation

Abstract
Become a Power User of CA Release Automation to Get the Most out of Your Implementation.
This session provides an overview and demonstration of four key features in Release
Automation: Artifact-driven Deployments, Shared Components, Environments, and Environment
Tokens.
These features enable you to mature and optimize your Continuous Delivery practices.
For each feature we provide a definition, the benefits, how it is used and best practices.
David Fisher
CA Technologies
Principal Consultant

Agenda
INTRODUCTION
CA’S CONTINUOUS DELIVERY PORTFOLIO
EMPLOYING ENVIRONMENT TOKENS
ENABLING ARTIFACT-DRIVEN DEPLOYMENTS
LEVERAGING SHARED COMPONENTS
DEFINING AND UTILIZING ENVIRONMENTS
1
2
3
4
5
6
WRAP-UP & QUESTIONS6

Total Visibility
Across Entire
App Lifecycle
Fully
Integrated
Tool Chain
Exceptional
Customer
Experience
Automated
Testing & 100%
Test Coverage
Full Access to
Simulated
Environments
Accelerated
Development
Synthetic Data
Creation & Data
on Demand
Leverage your current investments and tools of choice,
while moving forward in your Continuous Delivery journey
Open & Fully Integrated
CD Solution Stack
Requirements
& Defects
Concurrent
Testing
Dev &
Build
Pre-
production
Production
& Monitoring
CA Release
Automation +
Continuous
Delivery
Edition
CA Agile Requirements
Designer
CA Blaze
Meter
CA Application
Test
CA Test Data
Management
CA Service
Virtualization

release alert
& details
SCALEACCELERATE
QA/TestDEV PRODUCTIONPRE-PROD
Customer
Experience
PROVISIONREP MGR SCM CI TESTCONTAINER CONFIG CLOUD
Document
requirements
Plan
Release
Design
Spec
Code
commit SCM CI/Build Functional
testing UAT Integration
testing
Performance
testing
Deploy to
pre-prod
Deploy to
production
CONTROL
End-to-end
Automation
APM
performance
snapshots
STREAMLINE AND ACCELERATE THE ENTIRE RELEASE
PROCESS, REDUCE MANUAL EFFORT AND ERRORS

High-level Value/Benefits of CA Release Automation
Provides a single
control point
and single pane
of glass across
all environments
Links all of the
critical elements
needed to build
a continuous
delivery pipeline
Consistently and
predictably
orchestrates the
release end-to-
end in a matter of
hours or minutes,
not weeks or
months
With shared
visibility and role
based access
control, get shared
responsibility,
collaboration and
alignment between
the Dev and Ops
teams

Bottom Line Value of CA Release Automation
§ Increases quality and visibility
§ Lowers delivery costs and risk
§ Accelerates agility and time to production
§ Allows you to get innovative applications into the hands of
end-users quickly and with high quality

CA Release Automation Key Capabilities
Model your
applications while
offering a layer of
abstraction from
the underlying
environment and
artifacts
No coding or
scripting is involved
anywhere, even for
complex
deployments and
integrations
Contains over 1800
Out-of-the-Box
vendor-and-
technology-neutral
actions
Provides full
visibility for
deployments,
including numerous
charts, graphs,
reports and metrics
Offers a Rapid
Development Kit
which enables you
to create new,
reusable actions
If an error occurs,
the deployment
pauses and allows
for real-time
remediation
System is
implemented using
a highly-scalable
three-tier
architecture
Define cross
application
releases, view a
calendar, and track
features and fixes
across the pipeline

CA Release Automation Advanced Topics

Enabling Artifact-driven (Dynamic) Deployments
§ RA provides you with the ability to dynamically populate the
list of deployment processes based on the types of artifacts to
be deployed
§ After examining the incoming package, the proper processes
are added to the list, along with any required dependencies
What are Dynamic Deployments?

§ Provides high degree of adaptability when deploying your
code
§ Similar to a CI tool in flexibility; no need to deploy everything
– just the artifacts that changed
§ No need to write and maintain scripts to handle the different
combinations/permutations of incoming artifacts
Benefits of Dynamic Deployments

§ Use the example workflow (will be made available)
§ When creating your Deployment Template, do not add any
processes to the main phase (Deployment Steps) tab
§ Confirm that processes are auto-added during initialization of
the Deployment Plan
How to Enable Dynamic Deployments

§ Associating server types with artifact definitions
Dynamic Deployment Best Practices

Demonstration of
Artifact-driven (Dynamic) Deployments

Leveraging Shared Components
§ RA offers Shared Components, application components that
can be used across applications
§ The components are versioned and can only be changed by an
authorized user
§ Different applications can be using different versions of a
Shared Component
What are Shared Components?

§ Provides high degree of reusability when designing your flows
and processes
§ Enables you to define and enforce standards and best
practices across the organization
§ Version control for greater tracking and control over changes
the components
§ Enables greater flexibility since different applications can be
assigned different versions of a Shared Component
Benefits of Shared Components

§ Define a Shared Component
§ Add necessary actions and create workflows
§ Check in changes
§ Assign Shared Component to an application
How to Leverage Shared Components

§ Branching and committing
§ Sharing of parameters
– Application
– Component
Shared Component Best Practices

Demonstration of Shared Components

Defining and Utilizing Environments
§ In RA an environment is a logical entity that maps to a real-
world environment
§ An architecture with certain server types is assigned to it
§ Actual agents are assigned to the server types
What Are Environments?

§ Provide high degree of adaptability and flexibility when
deploying your code since they're decoupled from the logic
and artifacts
§ All environment-related parameters and tokens are applied at
runtime
§ Agents can be dynamically associated with a particular
environment and server type
Benefits of Environments

§ Add an environment
§ Assign processes
§ Create and assign any environment-specific parameters and
tokens
§ Map agents to the agent types via drag-n-drop
How to Define and Use Environments

§ Canary deployments
§ Use of different architectures
§ Assigning parameters from external sources (e.g. password
vault)
§ Dynamic assignment of agents
Environment Best Practices

Demonstration of Environments

Employing Environment Tokens
§ Special types of parameters that replace environment-specific
values in configuration files
§ The proper environment-specific values are populated at
runtime
§ Tokens can be different data types, and you can apply a RegEx
mask that enforces validation of token values
§ They can be defined via the Web GUI or an manifest XML file
What Are Environment Tokens?

§ Saves time, as it prevents the need to create flows to update
the configuration files with environment-specific changes
§ Provides a single, easy-to-use interface to manage tokens
Benefits of Environment Tokens

§ Create tokens and assign them to environments
– Manually
– Via manifest
§ Provide token values
– Manually
– Via manifest
– Via REST API
§ Associate token with artifact definition
How to Use Environment Tokens

§ Number of Tokens to Use
§ Token Manifest Files
§ Artifacts Affected by Tokens
§ Naming convention
§ Token mask tips
Environment Token Best Practices

Demonstration of Environment Tokens

Experiences
Lorem ipsum dolor sit amet,
consectetur adipisicing elit, sed
do eiusmod tempor incididunt
ut labore et dolore magna.
Key Topics
Findings
Summary
A Few Words to Review

Recommended Sessions
SESSION # TITLE DATE/TIME
DO5X04L
Pre-Con Lab: Design Custom Action Packs and Plug-ins to
Support CA Release Automation Deployment Operations
11/14/2016 at 4:00 pm
DO5X20E
Pre-Con Ed: Make Zero-touch Application Releases a
Reality with the Integrated, Open CA Continuous
Delivery Framework
11/15/2016 at 9:00 am
DO5X25L
Pre-Con Lab: Getting Started (and Hands on) with CA
Release Automation Continuous Delivery Edition
11/15/2016 at 11:00 am
DO5X03L
Pre-Con Lab: Build Plug-ins for CA Release Automation
Continuous Delivery Edition—Easy as 1, 2, 3
11/15/2016 1:00 pm

Must See Demos
Modernize
App Delivery
Integrated CD
Theater 5 - DOV501P
Deliver Test
Data Faster
Test Data Manager
Theater 5 - DOV511P
Deliver
Better Apps
Service Virtualization
Theater 5 - DOV507P
Orchestrate
Your Release
Release Automation
Theater 5 - DOV513P

Questions?

Thank you.
Stay connected at communities.ca.com

Pre-Con Ed: Become a Power User of CA Release Automation to Get the Most out of Your Implementation

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (20)

Similar to Pre-Con Ed: Become a Power User of CA Release Automation to Get the Most out of Your Implementation

Similar to Pre-Con Ed: Become a Power User of CA Release Automation to Get the Most out of Your Implementation (20)

More from CA Technologies

More from CA Technologies (20)

Recently uploaded

Recently uploaded (20)

Pre-Con Ed: Become a Power User of CA Release Automation to Get the Most out of Your Implementation

Editor's Notes