DevOps Automation

 View Only

Devops Deploy - Deploying to multiple Target Datasets on zOS

By Bharath Kumar posted Wed November 06, 2024 02:37 AM

  

IBM Devops Deploy is a powerful deployment tool in the DevOps world. It can deploy to newer tech like containers to age old platforms like mainframe. This write-up will focus on a feature intended for mainframe deployments. The Devops-Deploy tool comes with a rich set of zOS features to version software packages and deploy them. One such feature is the Deploy-Dataset plugin step.

This plugin step is used to deploy/copy datasets and directories in version to target datasets and directories in respective zOS LPAR. A DEPLOY version may contain several datasets packaged in it. For the plugin to deploy each dataset to the right target datasets, it relies on a user input namely ‘Dataset Mapping’.

The Dataset Mapping looks like below:

It is quite evident from the mapping that one can deploy artifacts from one source dataset in the version to one target dataset in the environment.

Feature: DEPLOY TO MULTIPLE TARGETS

The new feature enhances Deploy Data Set by allowing a user to deploy one source dataset to multiple dataset using the below mapping
As you can notice, every single source dataset is mapped to 2 target datasets in the example. However, theoretically there is no restriction on how  many target datasets a single source dataset can be mapped to. Also, it is not mandatory that all source datasets be mapped to same number of targets.  For example, below is still a valid mapping, where only LOAD type artifacts are mapped to multiple target datasets.
Note that plugin steps can resolve references to properties that can be defined at various levels in Devops Deploy. We encourage our users to store the mapping in a property and refer to them.

The effects on Multi-Generate Artifact / Generate-Artifact plugin steps

This plugin step helps a user to filter their version contents based on artifact types, deployment targets, build sources, custom properties etc and generate a template for those artifacts that can further be used in postprocessing step. More at zOS-multi-generate-artifact-plugin-usage
When using multiple targets during deployment, this plugin step can now generate information for each target dataset. The simpler way of doing it will be to add filter artifacts at source container filter and leave the target container filter as blank.
Given a mapping like below:
Filter artifacts using container below filter :
The results for in-built variable ${dataset} for the above properties after the plugin execution will be:
Of course it is still possible to use filters for Target containers, but that would mean that user needs to create a new property for every target dataset. This is helpful for cases where the post-processing templates vary for different target datasets.

Important:

  • RUNTIME Delta-Deploys are not supported in this feature.
  • Source containers are ignored for deploy process even if one target mapping is found to be DUMMY
Plugin Documentation: Devops Deploy Plugins
Download zOS Utility Plugin at: Devops Deploy zOS Utility downloads
#DevOps#DevOpsSolutions#IBMz/OS
0 comments
11 views

Permalink