Infrastructure as Code (Yes, it applies to z/OS as well)
summary
Argues that z/OS supports real Infrastructure as Code using existing open tools: Git, Azure DevOps pipelines, Ansible, Jenkins, Groovy, Artifactory/Nexus, zD&T/zVM provisioning, z/OSMF APIs and the Zoe CLI. Shows customers who automate full system and middleware validation from 27 hours → 11 → 4 hours of elapsed work, and one who moves from a quoted 6 months → under 2 minutes to build a bootable z/OS image, with sample repos on GitHub for reuse.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:20Claim to fame
- 2:00Making mainframe DevOps able
- 2:39Infrastructure as Code
- 3:45System Image
- 7:55Why Provision
- 9:40Pipeline
- 11:15Load modules
- 13:34Open source
- 15:34Customer example
- 18:33System verification
- 20:06Example
- 23:27Zoe
- 27:39DevOps on zOS
related talks
42mInfrastructure as Code - Lessons learned from Dev to Ops
29mHow z/OS is Changing to Support Your DevOps Transformation
46mImplementing Infrastructure as Code
28mInfrastructure as Code in the Real World
54mInfrastructure as code (anti) Patterns
01h 02mTools and Techniques for Infrastructure as Code
19mInfrastructure as Code: A Must Know Skill for Today's Developers
15mInfrastructure as a Code: Best Practices and Myths