- Validata SAS

advertisement
Validata Release Coordinator
Accelerated application delivery through automated end-to-end release management
Agenda
1
Business Challenges
2
Validata Release Coordinator
3
Validata Release Coordinator Features
4
Validata Release Coordinator Best Practises
5
Reporting Capabilities
6
Benefits
Business Challenges
The cloud is pushing the needs of Dev-Ops for quicker and more efficient application
delivery and automated Release Management. The challenge with current, often
manual scripted processes is costly. They need to overcome deployment bottlenecks,
speed the update/patch process and avoid error driven disruptions.
Release management process is often performed manually raising the likelihood of
error-driven disruptions , deployment bottlenecks and leaving a gap between
Development and IT Operation teams.
Server environments vary between Development, QA, Staging, and Production, and
these differences often cause problems when applications are promoted between them.
Validata Release Coordinator
Validata SAS Release Coordinator enables IT organizations to automate the process of
application updates, resulting in shortened release cycles, application configuration alignment,
and automated updates across groups.
Users can ensure that server and application configurations are consistent across environments
by tracking application compliance in each environment against a distributed application policy
model.
All deployment actions can be authorized based on user roles, ensuring appropriate levels of user
access. If necessary, deployments can be rolled back easily. Deployment of applications
themselves can also be automated, even for deployments that consist of complex, multi-tier
changes, such as sequenced updates of web, application, and database servers.
The net result of these capabilities is shortened release cycles, enabling organizations to achieve
faster time-to-market.
Product Features
Planning
Capability to easily specify the tasks that are going to be implemented
in a new release system and the dates for new release deployments.
Execution
Automatic execution of package deployment across multiple
environments
Tracking
Easy and fast tracking of application compliance in each
environment against a distributed release application policy model.
Audit
Central
Repository
Full history and audit trail of new release deployments
Full management of all release deployments s enabled
through a central repository
Product Capabilities
Promotion rules for package
deployment across environments
and teams
Access control for administrators based
on role, environment, package or their
properties
Defining properties and
interdependencies for complex
applications and environments
Integrated Alerting mechanism with
automated email notifications upon
predefined system event
Packaging and Automation updates
integrated to environments
Schedule the Release Planning and
reporting for all Tasks statuses
supporting multiple teams and locations
Configuration control across preproduction and production environments
Impact analysis reporting of the
unfinished and uncovered software
development requirements
Environment-specific Transaction Safe Deployments: Pre-screening for any potential
errors in any environment prior to committing changes, and rollback of changes upon
failure or at user request
Baseline impact
analysis report has
been created and
verified
Deploy the Baseline to
QA environment for
testing
Deploy the Baseline to
Pre-Production
environment for Testing
Run the automated
environments
comparison reports to
identify any differences
Cut the Baseline
Update all the related
change requests with
status closed
Notify the related
stakeholders
Deliverables
Baseline has been
planned and
content has been
confirmed
Activities
Entry Criteria
Release Coordinator Methodology
Change request
coverage status
Deployment
reporting and
environments
comparison
Release Coordinator Workflows
Creation of workflows : Process, Roles, Dependencies
Release Coordinator Workflows
Creation of workflows : Process, Roles, Dependencies
Multi Company Deployment & Multi Country Roll Out
In our days the main Base code development gets implemented at the main development
site or it is out sourced to the vendor. When ready and tested, gets shared and delivered at
the business sites where now it has to be combined with the local developments, get tested
and communicate with several interfaces.
Remote Release Management
Capabilities







Fully automated Deployment
(records, data, objects, versions)
Role Based
Integrity of the Build
Pre-screening for any potential
errors in any environment
Rollback of changes upon failure
or at user request
Multiple Catalogues support
(Multiple
Versions )
Base Code
&
Local
Independent staging area
Code
Project
Contains Core + Local
Development for UK Site
Benefits
Base
 Reduce Deployment errors
 Reduce defects and improve
Code
consistency in packages across
environments
 Accuracy during package development,
promotion, and deployment across
environments.
 Reduced deployment costs through
increased effectiveness and accuracy
 Reduce downtime by ensuring
consistency in configurationsPoland
across
multiple environments
.
Base Code
&
Local
 Lower downtime costs through the
ability to back Code
out changes on demand
or upon failures in any environment.
Project
Contains Core + Local
Development for Poland Site
Release Coordinator Best Practises
Deploy for unit
testing on
development
environment
BCON Deploy to QA
environment for
System Integration
Testing (SIT)/ User
Acceptance Testing
(UAT)
Another pass of
testing - Repeat
#7 and #8 if
needed.
Rollback in
case of issue
Comparison between
development and
SIT/UAT environments
is highly recommended
to confirm that
content of BCON
packages is deployed
correctly.
Deploy on
preproduction
through Build
Control
Repeat the
process until
issue solved
Create a
BUILD.CONTROL
(BCON) deployment
package for all the
developments
Log the issues no rollback
here on QA!
Refresh QA
environments
and deploy
the fixed packs!
Compare SIT/UAT
and preproduction
environments to
confirm that
content is deployed
correctly.
Deploy to live and
Compare with
preproduction
environment to
confirm that
deployment is
complete and correct
Reporting Capabilities
Deployment History Report
Release
Status
ReportReport
Release
Planning
Releases Streams Overview
How is it different?
Support of Release Streams and Release
Iterations
Build integrity protection
Automatic import of existing T24
programming artifacts and turn them into
controlled source and record objects
Integration between version control
and deployment on T24
Automatic build of BCON
packages
Versioning of data record objects
through Temenos T24 specific data
editing feature
The Critical Differencies
Faster
Deployments
Shorten release cycles to better support the business
Greater Business
Faster respond to changing market conditions and competitive threats
Agility
Improved User
Experience
Enable instant delivery of feature requests and enhancements
Aligned Release
Teams
Ensure worry-free deployments by leveraging process visibility,
measurement, and management to improve communication between
Development, QA, and Operations
Reduced Application
Downtime
Prevent configuration errors and accelerate troubleshooting
Lowered costs
Eliminate labor-intensive manual and script-based deployment processes
Auditing and
Governance
Detect and remediate changes and demonstrate effective policy
enforcement
Do You Have
Any Questions?
We would be happy to help.
Download
Related flashcards

Project management

14 cards

Mind-mapping software

26 cards

Create Flashcards