Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
Showing results for 
Search instead for 
Did you mean: 
Active Contributor
0 Kudos
Red Hat Ansible is an enterprise solution for building and operating automation at scale. In this blog I will demonstrate how to leverage it for validating your SAP Data Intelligence installation on the SUSE CaaS Platform.

As per the SAP Data Intelligence Installation Prerequisites, all Kubernetes nodes need access to a container registry that mirrors the SAP Data Intelligence container images and deploys images created by the Pipeline Engine. To ensure that this is the case I install Red Hat Ansible on my SUSE CaaSP Management Workstation. The advantage is that from there I already got SSH access to all machines in the cluster.

Ansible is part of the SUSE Package Hub package and depends on the Development Tools package that itself is dependent on the Desktop Applications package. Therefore, I install those packages in reverse order:
SUSEConnect --product sle-module-desktop-applications/15.1/x86_64
SUSEConnect --product sle-module-development-tools/15.1/x86_64
SUSEConnect --product PackageHub/15.1/x86_64
zypper in ansible

For this simple automation, I only need a minimum Ansible configuration file:
inventory = $HOME/hosts

And a respective hosts file containing a tiny subset of my Kubernetes nodes:

The Ansible playbook to test the container registry connection is very simple and straight forward:
hosts: kubernetes
name: Docker Registry

So, let’s run it:
ansible-playbook registry.yml

PLAY [all] *********************************************************************

TASK [Gathering Facts] *********************************************************
ok: []
ok: []

TASK [Docker Registry] *********************************************************
ok: []
ok: []

PLAY RECAP ********************************************************************* : ok=2 changed=0 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0 : ok=2 changed=0 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0

As a result, I will no longer have failed graphs because of images that could not be deployed to the container registry on a rogue node by the SAP Data Intelligence Pipeline Engine.
Labels in this area