The document discusses leveraging DevOps practices to improve mainframe application delivery. It describes how traditional mainframe development and testing causes delays due to shared, restricted resources and inefficient processes. The solution presented uses DevOps tools and practices like continuous integration/delivery, dependency virtualization, and automated quality testing to enable more efficient mainframe application development and testing. This allows development and operations teams to work in parallel, validate code quality earlier, and deploy applications more frequently.
RDz for DevOps Webcast Series: Implementing Continuous Integration with RDzSusan Yoskin
How do you improve code quality and achieve continuous integration in a mainframe environment? Continuous integration testing, by shifting defect detection and resolution earlier in the delivery cycle (shift left approach), speeds up development while increasing quality and time to market. This session focuses on the development and test phase of the DevOps lifecycle. It centers on development using Rational Developer for System z (RDz), including debug, code review and code coverage. It discusses test automation using a customized zUnit testing framework in conjunction with automated mainframe SCM build and deploy. Keith Allen, IBM Software Sales European IOT Team Lead - DevOps for Enterprise z Systems, and Luis Carlos Silva, IBM EM Continuous Integration Lead and Product Line Manager, will take you through this methodology.
Mobile to mainframe - The Challenges and Best Practices of Enterprise DevOps IBM UrbanCode Products
Delivering software is complex. Systems being developed are made up of multiple components, which in turn interact with other systems, services, application servers, data sources and invocations of 3rd party systems. In an Enterprise this complexity is further enhanced by the cross-platform nature of the infrastructure typical enterprises have. While the customers may be interacting with Systems of Engagement using Mobile and Web Apps, the core capabilities of the enterprise that the customers access are in Systems of Record that are running on large datacenters and more than likely Mainframe systems. Keeping these complex systems up and running and constantly updated with the latest capabilities is a task that requires constant coordination between the lines of business, various cross-platform development, QA and operations teams.
DevOps addresses these development and deployment challenges. The goal of DevOps is to align Dev and Ops by introducing a set of principles and practices such as continuous integration and continuous delivery. Cross-platform enterprise Systems take the need for these practices up a level due to their inherent complexity and distributed nature. Such systems need even more care in applying DevOps principles as there are multiple platforms to be targeted, in a coordinated manner, each with its own requirements, quirks, and nuanced needs. This talk takes a look at the DevOps challenges specific to Cross-platform Enterprise Systems and present Best Practices to address them.
DevOps for the IBM Mainframe environmentMicro Focus
Establishing a model that works across enterprise IT –
including mainframe systems
The solutions and methodologies tackling business challenges are constantly evolving. From waterfall to agile and on to continuous integration and DevOps, successful software development is about achieving the improved efficiencies needed to meet ever-growing business requirements.
DevOps - a blend of Development and Operations - is not a straightforward fit for the mainframe environment. But change is required if enterprises are going to match more agile operations in meeting efficiency targets against a background of increasing application complexity.
Mobile to Mainframe - the Challenges of Enterprise DevOps AdoptionSanjeev Sharma
Delivering software is complex. Systems being developed are made up of multiple components, which in turn interact with other systems, services, application servers, data sources and invocations of 3rd party systems. In an Enterprise this complexity is further enhanced by the cross-platform nature of the infrastructure typical enterprises have. While the customers may be interacting with Systems of Engagement using Mobile and Web Apps, the core capabilities of the enterprise that the customers access are in Systems of Record that are running on large datacenters and more than likely Mainframe systems. Keeping these complex systems up and running and constantly updated with the latest capabilities is a task that requires constant coordination between the lines of business, various cross-platform development, QA and operations teams.
DevOps addresses these development and deployment challenges. The goal of DevOps is to align Dev and Ops by introducing a set of principles and practices such as continuous integration and continuous delivery. Cross-platform enterprise Systems take the need for these practices up a level due to their inherent complexity and distributed nature. Such systems need even more care in applying DevOps principles as there are multiple platforms to be targeted, in a coordinated manner, each with its own requirements, quirks, and nuanced needs.
This talk will take a look at the DevOps challenges specific to Cross-platform Enterprise Systems and present Best Practices to address them.
Continuous Application Delivery to WebSphere - Featuring IBM UrbanCodeIBM UrbanCode Products
UrbanCode Deploy provides extensive capabilities for configuring WebSphere Application Server (WAS) through plug-ins: Application Deployment for WebSphere – which enables the auto-discovery of WAS cells; and Middleware Configuration for WebSphere – which allows for management of WAS configurations.
See how, when combined, UrbanCode Deploy and these plug-ins enable a rapid, controlled method for continuous delivery to WebSphere Application Servers.
RDz for DevOps Webcast Series: Implementing Continuous Integration with RDzSusan Yoskin
How do you improve code quality and achieve continuous integration in a mainframe environment? Continuous integration testing, by shifting defect detection and resolution earlier in the delivery cycle (shift left approach), speeds up development while increasing quality and time to market. This session focuses on the development and test phase of the DevOps lifecycle. It centers on development using Rational Developer for System z (RDz), including debug, code review and code coverage. It discusses test automation using a customized zUnit testing framework in conjunction with automated mainframe SCM build and deploy. Keith Allen, IBM Software Sales European IOT Team Lead - DevOps for Enterprise z Systems, and Luis Carlos Silva, IBM EM Continuous Integration Lead and Product Line Manager, will take you through this methodology.
Mobile to mainframe - The Challenges and Best Practices of Enterprise DevOps IBM UrbanCode Products
Delivering software is complex. Systems being developed are made up of multiple components, which in turn interact with other systems, services, application servers, data sources and invocations of 3rd party systems. In an Enterprise this complexity is further enhanced by the cross-platform nature of the infrastructure typical enterprises have. While the customers may be interacting with Systems of Engagement using Mobile and Web Apps, the core capabilities of the enterprise that the customers access are in Systems of Record that are running on large datacenters and more than likely Mainframe systems. Keeping these complex systems up and running and constantly updated with the latest capabilities is a task that requires constant coordination between the lines of business, various cross-platform development, QA and operations teams.
DevOps addresses these development and deployment challenges. The goal of DevOps is to align Dev and Ops by introducing a set of principles and practices such as continuous integration and continuous delivery. Cross-platform enterprise Systems take the need for these practices up a level due to their inherent complexity and distributed nature. Such systems need even more care in applying DevOps principles as there are multiple platforms to be targeted, in a coordinated manner, each with its own requirements, quirks, and nuanced needs. This talk takes a look at the DevOps challenges specific to Cross-platform Enterprise Systems and present Best Practices to address them.
DevOps for the IBM Mainframe environmentMicro Focus
Establishing a model that works across enterprise IT –
including mainframe systems
The solutions and methodologies tackling business challenges are constantly evolving. From waterfall to agile and on to continuous integration and DevOps, successful software development is about achieving the improved efficiencies needed to meet ever-growing business requirements.
DevOps - a blend of Development and Operations - is not a straightforward fit for the mainframe environment. But change is required if enterprises are going to match more agile operations in meeting efficiency targets against a background of increasing application complexity.
Mobile to Mainframe - the Challenges of Enterprise DevOps AdoptionSanjeev Sharma
Delivering software is complex. Systems being developed are made up of multiple components, which in turn interact with other systems, services, application servers, data sources and invocations of 3rd party systems. In an Enterprise this complexity is further enhanced by the cross-platform nature of the infrastructure typical enterprises have. While the customers may be interacting with Systems of Engagement using Mobile and Web Apps, the core capabilities of the enterprise that the customers access are in Systems of Record that are running on large datacenters and more than likely Mainframe systems. Keeping these complex systems up and running and constantly updated with the latest capabilities is a task that requires constant coordination between the lines of business, various cross-platform development, QA and operations teams.
DevOps addresses these development and deployment challenges. The goal of DevOps is to align Dev and Ops by introducing a set of principles and practices such as continuous integration and continuous delivery. Cross-platform enterprise Systems take the need for these practices up a level due to their inherent complexity and distributed nature. Such systems need even more care in applying DevOps principles as there are multiple platforms to be targeted, in a coordinated manner, each with its own requirements, quirks, and nuanced needs.
This talk will take a look at the DevOps challenges specific to Cross-platform Enterprise Systems and present Best Practices to address them.
Continuous Application Delivery to WebSphere - Featuring IBM UrbanCodeIBM UrbanCode Products
UrbanCode Deploy provides extensive capabilities for configuring WebSphere Application Server (WAS) through plug-ins: Application Deployment for WebSphere – which enables the auto-discovery of WAS cells; and Middleware Configuration for WebSphere – which allows for management of WAS configurations.
See how, when combined, UrbanCode Deploy and these plug-ins enable a rapid, controlled method for continuous delivery to WebSphere Application Servers.
Integrations, UI Enhancements and Cloud – See What’s New with IBM UrbanCode D...IBM UrbanCode Products
IBM UrbanCode Deploy delivers several new feature functionalities with the latest software release further extending its commitment to integrations, and cloud, while bringing deployment automation as-a-service to the market. Leading this latest release is a new integration with VMware VRealize Automation; a new Jenkins Pipeline plugin, and new full-featured as-a-service version of Deploy hosted by Softlayer.
IBM UrbanCode is a leader in deploying applications to multiple platforms in complex environments. And Docker is an open platform for developers and system administrators to build, ship, and run distributed applications.
Laurel Dickson-Bull, IBM UrbanCode Product Manager, and Mike Samano, IBM Lead Developer for UrbanCode Integrations, as they discuss how you can leverage UrbanCode to deploy Docker containers.
IBM’s Steve Barbieri and Chad Holliday show how enterprise customers are using blueprints to develop their infrastructure and application layers across different cloud environments - helping them "make the move to cloud" in 2017.
Continuous Delivery seeks to deliver increased Business Agility by releasing smaller releases more frequently. To truly leverage Continuous Delivery, enterprises must consider impacts that span functional silos. Enterprises also struggle to apply continuous delivery principals to applications that touch older, slower moving components. When applications are a composite of numerous services, databases, and other components, managing dependencies can result in slowdown.
Join Eric Minick, DevOps Evangelist & Product Management Lead, at IBM. In this presentation, he will discuss:
- “Standard” continuous delivery
- Challenges larger organizations have with CD
- Techniques for applying continuous delivery to the largest applications
Learn more about Continuous Delivery, and Deployment Automation today!
Helping Organizations Realize the Value of DevOps with Continuous Software De...IBM UrbanCode Products
The IBM UrbanCode solution enables continuous release and application deployment allowing organizations to deliver applications rapidly and improve overall time to market.
How to Adopt Docker Within Your Enterprise Using IBM UrbanCode Deploy (Interc...Michael Elder
In this session, we will discuss how to incorporate Docker into your Continious Delivery pipeline. We will highlight challenges that enterprises can encounter when adopting Docker, including image management, promotion and configuration management. We will discuss how Docker applications or components can compliment existing traditional IT architectures, and will perform a live demonstration of the Docker/IBM UrbanCode capabilities to deploy Docker containers into local Docker Runtimes, or to IBM Container Services on Bluemix.
Automating and Accelerating Application Deployments to IBM WebSphere without ...XebiaLabs
Slides from the Jun 11, 2013 Global WebSphere Community webinar "Deploy. Faster. Automating and Accelerating Application Deployments to IBM WebSphere without Scripting"
Improving Software Delivery with DevOps & Software Defined EnvironmentsMichael Elder
Introducing UrbanCode Deploy with Patterns - based on OpenStack technology, UCD with Patterns enables you to quickly leverage software defined environments based on OpenStack and other off premise clouds to improve your software delivery lifecycle.
Turning up the HEAT with IBM MobileFirst for iOS Apps (Interconnect 2016)Michael Elder
The landmark partnership between Apple and IBM announced in 2014 set the Internet abuzz. This partnership aims to spark true, mobile-led business change across the enterprise. In this talk, we’ll show you how IBM is using OpenStack, Heat, and DevOps to deploy the MobileFirst Platform for iOS enterprise solutions. We willl tell the story of how we used full-stack application patterns based on OpenStack Heat to provision environments with speed and reliability.
DevOps is a culture that promotes collaboration between Development and Operations Team to deploy code to production faster in an automated & repeatable way. The word 'DevOps' is a combination of two words 'development' and 'operations.'
Integrations, UI Enhancements and Cloud – See What’s New with IBM UrbanCode D...IBM UrbanCode Products
IBM UrbanCode Deploy delivers several new feature functionalities with the latest software release further extending its commitment to integrations, and cloud, while bringing deployment automation as-a-service to the market. Leading this latest release is a new integration with VMware VRealize Automation; a new Jenkins Pipeline plugin, and new full-featured as-a-service version of Deploy hosted by Softlayer.
IBM UrbanCode is a leader in deploying applications to multiple platforms in complex environments. And Docker is an open platform for developers and system administrators to build, ship, and run distributed applications.
Laurel Dickson-Bull, IBM UrbanCode Product Manager, and Mike Samano, IBM Lead Developer for UrbanCode Integrations, as they discuss how you can leverage UrbanCode to deploy Docker containers.
IBM’s Steve Barbieri and Chad Holliday show how enterprise customers are using blueprints to develop their infrastructure and application layers across different cloud environments - helping them "make the move to cloud" in 2017.
Continuous Delivery seeks to deliver increased Business Agility by releasing smaller releases more frequently. To truly leverage Continuous Delivery, enterprises must consider impacts that span functional silos. Enterprises also struggle to apply continuous delivery principals to applications that touch older, slower moving components. When applications are a composite of numerous services, databases, and other components, managing dependencies can result in slowdown.
Join Eric Minick, DevOps Evangelist & Product Management Lead, at IBM. In this presentation, he will discuss:
- “Standard” continuous delivery
- Challenges larger organizations have with CD
- Techniques for applying continuous delivery to the largest applications
Learn more about Continuous Delivery, and Deployment Automation today!
Helping Organizations Realize the Value of DevOps with Continuous Software De...IBM UrbanCode Products
The IBM UrbanCode solution enables continuous release and application deployment allowing organizations to deliver applications rapidly and improve overall time to market.
How to Adopt Docker Within Your Enterprise Using IBM UrbanCode Deploy (Interc...Michael Elder
In this session, we will discuss how to incorporate Docker into your Continious Delivery pipeline. We will highlight challenges that enterprises can encounter when adopting Docker, including image management, promotion and configuration management. We will discuss how Docker applications or components can compliment existing traditional IT architectures, and will perform a live demonstration of the Docker/IBM UrbanCode capabilities to deploy Docker containers into local Docker Runtimes, or to IBM Container Services on Bluemix.
Automating and Accelerating Application Deployments to IBM WebSphere without ...XebiaLabs
Slides from the Jun 11, 2013 Global WebSphere Community webinar "Deploy. Faster. Automating and Accelerating Application Deployments to IBM WebSphere without Scripting"
Improving Software Delivery with DevOps & Software Defined EnvironmentsMichael Elder
Introducing UrbanCode Deploy with Patterns - based on OpenStack technology, UCD with Patterns enables you to quickly leverage software defined environments based on OpenStack and other off premise clouds to improve your software delivery lifecycle.
Turning up the HEAT with IBM MobileFirst for iOS Apps (Interconnect 2016)Michael Elder
The landmark partnership between Apple and IBM announced in 2014 set the Internet abuzz. This partnership aims to spark true, mobile-led business change across the enterprise. In this talk, we’ll show you how IBM is using OpenStack, Heat, and DevOps to deploy the MobileFirst Platform for iOS enterprise solutions. We willl tell the story of how we used full-stack application patterns based on OpenStack Heat to provision environments with speed and reliability.
DevOps is a culture that promotes collaboration between Development and Operations Team to deploy code to production faster in an automated & repeatable way. The word 'DevOps' is a combination of two words 'development' and 'operations.'
SHARE Conference DevOps Sessions & "Mobile to Mainframe DevOps for Dummies" ...IBM z Systems
Visit the DevOps ped (IBM booth) at SHARE 2015 to get the new book "Mobile to Mainframe DevOps for Dummies" autographed by the author, Rosalind Radcliffe, IBM Distinguished Engineer.
There are limited hard copies available, so get yours quickly
Topics:
* Understanding the Value of the Mainframe
* Understanding the Typical Mainframe Application Dev. Challenges
* DevOps and the Mainframe: Mission Possible?
* Looking at DevOps Best Practices for z Systems
* Building for the Modern Omni‐Channel World
* Seeing DevOps Success Stories in the Enterprise
System Z Mainframe Security For An EnterpriseJim Porell
System z provides technology that makes it one of the most secure platforms available. It also has the capability to secure other platforms. This presentation provides a number of examples of Enterprise Security. Reduce your cost, your risk, improve your security and resilience with System z.
For Complete Learning: http://www.thelearnet.com/
What is an Operating System?
Mainframe Systems
Desktop Systems
Multiprocessor Systems
Distributed Systems
Clustered System
Real -Time Systems
Handheld Systems
Computing Environments
Introducing MFX for z/OS 2.1 & ZPSaver SuitePrecisely
Syncsort MFX for z/OS 2.1 leverages the latest advancements in mainframe technology, including IBM’s zHPF architecture and deeper exploitation of zIIP engines, to help you overcome the challenges of modern mainframe systems.
Technology is evolving and changing at a very rapid pace, and it is more important than ever to ensure that mission critical back-end mainframe applications can exploit these new and disruptive technologies to transform digitally and deliver real value to the business, and to customers. DevOps on z Systems is a key enabler for the API economy and hybrid cloud. In this session we will discuss how DevOps can transform application delivery on z Systems, mitigate risk, and elevate the ability to respond quickly to customer expectations through continuous improvement"
The results from Syncsort’s annual State of the Mainframe Survey are in! The importance of mainframe data is rising as a critical component of enterprise-wide strategies that leverage modern data architectures for Big Data analytics and security and compliance. Join us for a live webcast and Q&A as we take you through an in-depth look at the survey results and the four trends to watch for in 2017. You’ll also learn how for their organizations your peers view:
• The future of mainframe and mainframe-related budgets
• The importance of Mainframe data for Big Data analytics
• The need for operational intelligence and security intelligence for the mainframe
• How IT priorities are shifting (and where)
For Complete Learning: http://www.thelearnet.com/
Computer System Operation
I/O Structure
Storage Structure
Storage Hierarchy
Hardware Protection
General System Architecture
Christian Bk Hansen - Agile on Huge Banking Mainframe Legacy Systems - EuroST...TEST Huddle
EuroSTAR Software Testing Conference 2011 presentation on Agile on Huge Banking Mainframe Legacy Systems by Christian Bk Hansen. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
XebiaLabs, CloudBees, Puppet Labs Webinar Slides - IT Automation for the Mode...XebiaLabs
Learn how you can enhance and extend your existing infrastructure to create an automated, end-to-end IT platform supporting on-demand middleware and application environments, application release pipelines, Continuous Delivery, Private/ hybrid development platform and PaaS and more.
This slide deck Introduces Chef and its role in DevOps. The agenda of the deck is as follows:
- A Review of DevOps
- BMs Continuous Delivery solution
- Introduction to Chef
- Chef and Continuous Delivery
Read more on DevOps: http://sdarchitect.wordpress.com/understanding-devops/
Watch the recorded version of this Webinar here:
Curious about Continuous Integration? Tune in!
Continuous Integration (CI), which is a big part of continuous delivery, is the concept of continuously building and testing software using an automated process. We have learned that utilizing CI could help us catch bugs earlier, enable better visibility, reduce repetitive processes, enable the development team to produce deployable products at a moment's notice, and reduce risk overall.
These slides will identify the various levels of continuous integration and delivery with regards to a release maturity of the development team or parent organization.
(SEC312) Taking a DevOps Approach to Security | AWS re:Invent 2014Amazon Web Services
More organizations are embracing DevOps to realize compelling business benefits, such as more frequent feature releases, increased application stability, and more productive resource utilization. However, security and compliance monitoring tools have not kept up. In fact, they often represent the largest single remaining barrier to continuous delivery. Learn how to integrate security controls in your DevOps program from experts at Alert Logic and George Miranda, engineer and evangelist at Chef. Sponsored by Alert Logic.
Enabling multicloud in the enterprise with DevSecOpsJosh Boyd
Core federal agencies are using multiple cloud providers to avoid vendor lock-in and optimize their workloads' infrastructure. Taking advantage of each cloud provider's strengths comes with some challenges: multicloud security and compliance, inventory tracking, resource utilization, and software delivery automation.
In this session, you'll see how Red Hat CloudForms and Red Hat OpenShift Container Platform, paired with Booz Allen’s Solutions Delivery Platform, addresses these challenges and brings governance to your DevOps pipeline and multicloud environment.
Unified Deployment: Including the Mainframe in Enterprise DevOpsCompuware
During this collaborative webcast, Compuware Product Manager Mark Schettenhelm and XebiaLabs VP of Products Tim Buntel demo and discuss how the integration between Compuware’s ISPW mainframe DevOps solution and XebiaLabs’ XL Release Continuous Delivery technology helps enterprises engage in cross-platform release orchestration and create business agility. Mark and Tim:
- Overview ISPW’s functionality
- Overview XebiaLabs XL Release’s functionality
- Demo the ISPW and XL Release integration
- Explain the importance of two-platform Continuous Release
We had this presentation running on one of the screens in our booth at the April 4, 2013, Innotech Dallas/SharePoint TechFest. We have been excited by the developments in the latest release of Visual Studio and it's ability to work seamlessly with Microsoft's Azure.
En DevOps är en roll i teamet som överbryggar utveckling och drift och som hjälper till att säkerställa leverenspresision och kvalitet, bland annat genom att se till att bra lösningar för applikationsövervakning, felrapportering, paketering och deployment finns på plats.
Med lösningar för dessa funktioner kan vi exempelvis rejält korta tiden det tar från att ett fel identifierats till att det finns en fix ute i produktion.
Presentation on Mobile DevOps. Presented at MoDevTablet conference on Sept. 14th. Focuses on:
- What is DevOps?
- What are the challenges of DevOps for Mobile?
- Best practices for Mobile DevOps
Blog post: https://sdarchitect.wordpress.com/2012/09/15/slides-for-my-presentation-on-mobile-devops/
DevOps is a methodology capturing the practices adopted from the very start by the web giants who had a unique opportunity as well as a strong requirement to invent new ways of working due to the very nature of their business: the need to evolve their systems at an unprecedented pace as well as extend them and their business sometimes on a daily basis.
While DevOps makes obviously a critical sense for startups, I believe that the big corporations with large and old-fashioned IT departments are actually the ones that can benefit the most from adopting these principles and practices.
Microservice Builder: A Microservice DevOps Pipeline for Rapid Delivery and P...David Currie
Presentation from IBM InterConnect 2017.
Abstract: Acceleratate your microservice delivery and promotion with an out-of-box DevOps pipeline! In this session, you'll learn how to use the Project Liber8 DevOps pipeline. We will explore its anatomy, operation, visualization, customization and ecosystem integration. We will further examine its use in deploying to IBM Cloud and on-premise deployments. A live demo will be used to reinforce concepts.
Devops transformation in the Rational Collaborative Lifecycle OrganizationRobbie Minshall
Set of slides providing a summary of our DevOps Transformation efforts within the Rational Collaborative Lifecycle Management organization. Discusses the use of IBM Urbancode Deploy, IBM Pure Application System and adoption of DevOps methodologies.
Similar to DevOps for Mainframe for IBM Pulse Conference (20)
2. Please note
IBM’s
statements
regarding
its
plans,
direc3ons,
and
intent
are
subject
to
change
or
withdrawal
without
no3ce
at
IBM’s
sole
discre3on.
Informa3on
regarding
poten3al
future
products
is
intended
to
outline
our
general
product
direc3on
and
it
should
not
be
relied
on
in
making
a
purchasing
decision.
The
informa3on
men3oned
regarding
poten3al
future
products
is
not
a
commitment,
promise,
or
legal
obliga3on
to
deliver
any
material,
code
or
func3onality.
Informa3on
about
poten3al
future
products
may
not
be
incorporated
into
any
contract.
The
development,
release,
and
3ming
of
any
future
features
or
func3onality
described
for
our
products
remains
at
our
sole
discre3on.
Performance
is
based
on
measurements
and
projec3ons
using
standard
IBM
benchmarks
in
a
controlled
environment.
The
actual
throughput
or
performance
that
any
user
will
experience
will
vary
depending
upon
many
factors,
including
considera3ons
such
as
the
amount
of
mul3programming
in
the
user’s
job
stream,
the
I/O
configura3on,
the
storage
configura3on,
and
the
workload
processed.
Therefore,
no
assurance
can
be
given
that
an
individual
user
will
achieve
results
similar
to
those
stated
here.
2
3. New era systems integrate existing operational systems
with rapid delivery of new client-facing apps
Social, Local, Mobile
Smart Infrastructure Analytics
CRM
HR
Legacy
ERP
DB
Manage workloads Rapid innovation User experience and
and maintain security in the cloud mobile management
3
3
4. Evolving customer and market expectations
Capabilities and User Experience Today Emerging
Systems of Record Systems of Engagement (+ Record)
Primary Workload Types Transactional Big Data, Analytics, Mobile/Social Channels
Time to Value Planned Opportunistic
Delivery Model Planned Incremental (DevOps)
Development and Operations Team Sizes 100s and Costly 10s with built-in DevOps automation
Release Frequency Months to Years Hours to Days, based on business opportunity
Integration Frequency Weeks Continuous
Service Sourcing Develop Consume and Assemble (Public and Private)
Operational Model Systems Management Built in to application, Recovery Oriented Computing, Continuous Availability
Infrastructure Deployment Days Minutes
4
Risk Profile Big-Bang (High Risk) Incremental
5. DevOps is…
A set of principles and values that facilitate
collaboration across disciplines to…
1. Enable rapid evolution of deployed business services
2. Reduce risk, decrease cost, and improve quality across
the portfolio
People
Process
DevOps Principles
§ Collaborate across disciplines Tools
§ Develop and test against a production-like system
§ Deploy frequently using repeatable and reliable
processes
§ Continuously monitor and validate operational quality
characteristics
§ Amplify feedback loops
5
6. Solution: A Continuous Delivery Pipeline
Development Testing Staging Production
Business
Owners Customers
Ensure applications are production-ready throughout the lifecycle
and can be released at any time while minimizing rollback due to quality issues
• Validate
on
more
produc3on-‐like
• Standardiza3on
on
processes
and
assets
condi3ons
earlier
between
Dev
and
Ops
• Automate
hand-‐offs/promo3ons
to
• Automated
monitoring
and
dashboarding
increase
velocity
through
the
different
of
quality
and
performance
against
service
stages
level
agreements
at
mul3ple
stages
6
7. Mainframe Delivery Pains…
§ Multiple teams working across § Too much bad code going into
restricted dev and test capacity test and production causes crit
lead to conflict, delays, or bad sits and emergency fixes
test results in shared
environments
§ Bottlenecks due to inefficient
§ Complex and manual
communications between
management and configuration disparate platforms and teams
tasks result in errors and delays (Dev/Test - System Programmers;
mobile – distributed-mainframe)
7
8. …solutions from IBM
Play
Defense
§ Provide
cheap,
isolated,
development
§ Enforce
base
quality
standards
and
test
environments
for
project
automa3cally
prior
to
promo3on
teams
– Ra3onal
Development
and
Test
Environment
– Ra3onal
Test
Workbench
– Ra3onal
Test
Virtualiza3on
Server
– Ra3onal
Quality
Manager
– SmartCloud
Provisioning
– SmartCloud
Applica3on
Monitoring
– Cloud
Ready
for
Linux
on
System
z
– Omegamon
§ Automate
consistent
build,
configure,
§ Improve
communica3on
and
and
deploy
processes
across
all
stages
collabora3on
with
cross-‐plaVorm
– Ra3onal
Team
Concert
release
planning
– SmartCloud
Con3nuous
Delivery
– IBM
Collabora3ve
Lifecycle
Management
– SmartCloud
Orchestrator
– Smart
Cloud
Control
Desk
Go
on
Offense
8
9. DevOps for the common mainframe delivery cycle
1
2
2
Dev
Test
Dev
Test
Dev
Test
Staging
Prod
4
3
Development" Test" System
Programmer"
9
10. Typical z/OS Testing Architecture
Organized by project team, vertically scaled, sharing resources, limited automation
z/OS
Problems Encountered
Test LPAR
Project
Team 1. Shared resources combined
[April Maintain] with overlapping schedules can
App elicit conflicts, impede
innovation and slow code
Project delivery
Team
[Prototype SOA]
2. Coordination of environmental
Test
changes and releases cause
App bottlenecks, delays and
Project Data
Team additional overhead
[June New Func]
3. Shared test data is difficult to
…
manage and can lead to over
testing or incorrect test results
Project
Team App
[Dec Sys Upgrade]
10
10 10
11. Rational Development and Test Environment for
System z
The ultimate in modern application development for System z
COBOL,
PL/I,
C++,
Java,
EGL,
Batch,
Assembler,
Debug
Tool
IMS
DB2
CICS
WAS MQ
RDz user
RDz user z/OS
x86
PC
running
Linux
RDz user
ISPF user
RDz user
RDz & ISPF user
§ Liberate
developers
to
rapidly
prototype
new
applica3ons
§ Develop
and
test
System
z
applica3ons
anywhere,
any3me!
§ Free
up
mainframe
development
MIPS
for
produc3on
capacity
§ Eliminate
costly
delays
by
reducing
dependencies
on
opera3ons
staff
Note:
This
Program
is
licensed
only
for
development
and
test
of
applica3ons
that
run
on
IBM
z/OS.
The
Program
may
not
be
used
to
run
produc3on
workloads
of
any
kind,
nor
more
robust
development
workloads
including
without
limita3on
produc3on
module
builds,
pre-‐produc3on
tes3ng,
stress
tes3ng,
or
performance
tes3ng.
11
12. Decouple subsystem teams using Green Hat
Improve
tes+ng
with
Green
Hat
service
simula+on
Simulate subsystem dependencies
– Test impact of latency
– Test application response to unresponsive
services
Application changes
Create a stable test environment being tested
– Simulate “public” services
– Reduce capacity requirements on
infrastructure
– Improve security by reducing access from
external services
Databases Mainframe Third-party
applications Services
virtualized services
Ra3onal
Test
Virtualiza3on
Server
12
13. Testing with dependency virtualization
Controlled large system testing by isolating components under test
• Easier problem determination
• Lower test environment capacity requirements
• Improved component quality
Phase 1 Phase 2 Phase 3
Test
Case
Test
Case
Test
Case
IMS
Data 3rd Party
IMS Data 3rd Party
Access Call IMS Data 3rd Party
App
Access
App
Call
Access Call
App
CICS
CICS
Commarea CICS
Commarea
Call Commarea
Call
Call
Virtual
Virtual
Virtual
Services
Services
Services
13
14. Provision new dev / test systems in minutes
• Fast
VM
provisioning
for
near-‐instant
deployment
of
100s
of
virtual
machines
and
scale
based
on
business
needs
• Rich
set
of
web
interfaces
into
the
cloud
that
can
be
driven
by
a
user
or
scripts
for
complete
automa3on
• Reliable,
non-‐stop
cloud
capable
of
automa3cally
tolera3ng
and
recovering
from
soeware
and
hardware
failures
• Near-‐zero
down=me
due
to
faults,
hypervisor/
management
soeware
upgrades
or
addi3on/
removal
of
hardware
Func3on
Test
Performance
Test
Requested
VMs
will
be
up
and
running
under
a
minute
using
standard
HW
14
15. Fail fast and drive better quality downstream
Reduced delivery time, end-to-end visibility of test activities, safer and faster upgrades (V2V)
Automated, Reusable
continuous testing integration
with isolated Continuous Integration for z tests simplify
development and testing across
test environment layers
Check
In
+
Build
+
Deploy
+
Run
Code
Automated
Tests
Change
Promote
Request
To
QA
Frequent, rapid
feedback earlier Developer Higher quality
to improve
going into QA
quality Rapid
Feedback
§ Fast, dependable, automatic feedback speeds time to market
§ Lower cost of application testing using off-mainframe z/OS test environment
§ Enables confidence by automatically tracking and promoting code health
15
16. Continuous Integration for System z Scenario
System z
Test
ests>
pp+zUnit T Environment
<Deploys A (RD&T or LPAR)
<Drives>
SCM/CI <Starts Tests> Test
Server Execution
(Rational Team Manager
Concert) (Ra3onal
Quality
<Results> Manager)
Test
Automation
(Rational Test
1. Check-in code 5. Kick-off Automated Workbench)
2. Build code and zUnit Test Plan
6. Run automated
tests interface tests against
3. Deploy build results 8. Report test results Test Environment
and test data to Test in dashboard/build 7. Mark execution
Environment results/defect records Pass/Fail in
4. Execute zUnit Tests records in CI server. Test Execution 16
Manager
16
17. Separate tools makes collaboration inefficient or
difficult...
§ Each tool came with its own Tool A
Dev work Items Tool B
• UI - Web and desktop
presentations of views and DB
Release
Planning
UI
tasks
• Logic – Workflow, process, LOGIC
DB
UI
search, query, scale, security Tool E
and collaboration LOGIC
• Storage – Availability,
SCM
traceability DB
UI
• Privacy, backup/archive
LOGIC
§ Resulting in... DB
UI
• Brittle integrations
LOGIC
• Silos everywhere DB
UI Tool C
• High cost to maintain and
Tool D LOGIC Reporting
administer
• Proprietary API's Incident
Management
17
18. Tie development release to operational release
Ra3onal
Team
Concert
Release
Plan
and
work
items
SmartCloud
Control
Desk
18
19. Delivery Organized for Flexibility and Speed
Organized by application team, horizontally sliced, dedicated resources, highly automated
z/OS LPAR
Problems Encountered
Project 1. Shared resources
Team
[April Maintain] LPAR combined with
overlapping schedules
Data
can elicit conflicts,
QA/Integra3on
Test
LPAR
impede innovation and
Project
Team slow code delivery
[Prototype SOA] RD&T 2. Coordination of
Data
Integr.
environmental changes
Test
and releases cause
Project Data
bottlenecks, delays and
Team
[June New Func] RD&T
additional overhead
3. Shared test data is
…
Data
difficult to manage and
can lead to over testing
Project or incorrect test results
Team
[Dec Sys Upgrade] LPAR 4. Provisioning, managing,
and synchronizing project
Data
test environments
including data 19
19 19
20. Deploy application and config changes to test environments in minutes
Opera+ons
team
Development
team
establishes
deployment
makes
applica+on
pa;erns
for
use
by
IBM code
and
development
and
test
SmartCloud
configura+on
Continuous
teams
Delivery
changes
Deliver
Environments 3x
Test against
Faster!!
production-like
environments with
Applications &
middleware
AUTOMATICALLY
installed and properly IBM
configured IBM SmartCloud Workload
20
Provisioning Deployer
22. …solutions from IBM
Play
Defense
§ Provide
cheap,
isolated,
development
§ Enforce
base
quality
standards
and
test
environments
for
project
automa3cally
prior
to
promo3on
teams
– Ra3onal
Test
Workbench
– Ra3onal
Development
and
Test
Environment
– Ra3onal
Quality
Manager
– Ra3onal
Test
Virtualiza3on
Server
– SmartCloud
Applica3on
Monitoring
– SmartCloud
Provisioning
– Omegamon
– Cloud
Ready
for
Linux
on
System
z
§ Automate
consistent
build,
provision,
§ Improve
communica3on
and
configure,
and
deploy
pof
zLinux
across
collabora3on
with
cross-‐plaVorm
Cloud-‐style
deploy
rocesses
all
stages
dev
and
test
paMerns
and
z/OS
release
planning
on
RD&T
or
zHardware
– Ra3onal
Team
Concert
– IBM
Collabora3ve
Lifecycle
Management
– SmartCloud
Con3nuous
Delivery
– Smart
Cloud
Control
Desk
– SmartCloud
Orchestrator*
Go
on
Offense
22
23. Provisioning using Cloud
#!/usr/bin/env ruby
class DevopsDeployer
def initialize(build_url, build_id)
@log = Logger.new(LOG_FILE)
@log.level = LOG_LEVEL
@iaas_gateway = IaasGateway.new(HsltProvider.new(),
LOG_FILE, LOG_LEVEL)
@server_instance = nil
.cbl
.cpy
rtc_build_system_provider = RtcBuildSystemProvider.new(
RTC_REPOSITORY_URL, RTC_USER_ID, RTC_PASSWORD_FILE)
@build = rtc_build_system_provider.resolve_build(
build_url, ENV['buildResultUUID'], build_id)
Infrastructure
as
Code
@build_system_gateway = BuildSystemGateway.new(
.asm
rtc_build_system_provider, LOG_FILE, LOG_LEVEL)
end
def add_build_stamp
template_file = WEB_APP_ROOT +
"/app/templates/pages/page.html"
@log.info "Adding build ID stamp #{@build.id} to
.rexx
#{template_file}" CLIST
# Read in the file's contents as a string, replace
# the build_id, then overwrite the original contents
# of the file
text = File.read(template_file)
new_text = text.gsub(/{{ build_id }}/,
Source
Ar3facts
"<a href="#{@build.uri}">#{@build.id}</a>")
File.open(template_file, "w") { |file|
}
end
Source
Control
file.puts new_text
# ... Management
23
24. Delivery Pipeline Fundamentals
Build,
Package,
&
Unit
Test
Applica+on
.cbl
.cpy
Binaries
&
PlaGorm
Configura+on
Deploy
.asm
.rexx
CLIST
Environment
Deployable
Ar3facts
Running
System
Source
Ar3facts
Source
Control
Library
Management
24
25. Consolidate, standardize, simplify deployment
Enterprise
Applica3ons
have
thousands
of
disparate
parts
• Currently
maintained
in
separate
systems,
if
maintained
at
all
• Limited
linkage
between
systems
for
applica3on
and
configura3on
dependencies
• Missing
assets
and
informa3on
is
rampant
DevOps
force
linkages,
automa3on,
and
standardized
packaging…
Copybooks
HTML
COBOL
JCL
Build,
Package,
WSDL
&
Unit
Test
MQ
Applica+on
Deploy
Java
Queue
Binaries
&
Def
PlaGorm
Configura+on
DB2
IMS
DBD/PSB
DDL
DB2
Plans
Environment
Deployable
Ar3facts
Running
System
Procs
Library
Source
Management
25
26. Create, secure, and deploy test data
Automated Build &
Deploy Test Data
-Compare z/OS
-Subset -Refresh UT
RD&T
2TB 1 GB
Test Data
z/OS
Production or
UT
LPAR
Production Clone
1 GB
Masked Test Data
Automated
Testing
Create “right-size” De-identify sensitive information Automated test data
production-like environments De-identify sensitive information
with realistic but fictional data for deployment for each
for application testing with realistic purposes
testing & development but fictional data for
testing & development purposes build and test
Optim RTC 26
27. Standardize z/OS region configurations to ease
deployment
Configura3on
Applica3on
• Standard topologies exist today
(production LPARs)
• Standardized regions which can be
Data
repeatedly deployed are rare
• Standardized/Automated deployment of
COMPLETE system is spotty
CICS
5.1
IMS
11.1
Standard
Middleware
Palern
To adopt the cloud for testing…
Standardize and automate provisioning of
Z/OS
1.12
DB2
10.1
everything …
27
28. Standardize z/OS region configurations to ease
deployment
RTC/CIz Available
Application
Capabilities
Configura3on
Applica3on
load modules
Data
JCL and REXX
Test Data
CICS
5.1
IMS
11.1
Pattern/Platform
Standard
Middleware
Palern
Z/OS
1.12
DB2
10.1
28
29. Evolving to deploying regions … cloud-style
“Cloud”
CICS+DB2
RD&T
CICS+
IMS
Or
DB
LPAR
Region/Middleware
RD&T
Palerns
Or
Batch
LPAR
RD&T
Or
LPAR
RD&T
Or
LPAR
SmartCloud
Orchestrator
+
<SCD
for
Mainframe
Project>
29