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!
cancel
Showing results for 
Search instead for 
Did you mean: 
architectSAP
Active Contributor
In my previous blog, I leveraged the SAP Data Hub, developer edition as my SAP Data Hub Distributed Runtime:



This worked well to some extent, but is of course not a supported architecture. Therefore, I will explain how to install the SAP Data Hub Distributed Runtime on the SUSE CaaS Platform which is supported as per SAP Note 2464722 - Prerequisites for installing SAP Data Hub:



To start with, I install three SUSE CaaSP nodes as per the respective Deployment Guide.

Administration Node



  • 2 cores

  • 12 GB RAM

  • 40 GB disk


Please ensure to select Install Tiller during the Initial CaaS Platform Configuration as this will be needed for the SAP Data Hub Distributed Runtime:


Master Node



  • 2 cores

  • 8 GB RAM

  • 40 GB disk


Worker Node



  • 4 cores

  • 20 GB RAM

  • 80 + 16 GB disks


This is the node onto which I will install the SAP Data Hub Distributed Runtime later. To make this work, I need to mount an additional volume as /var/local:


Cluster


As a result, I got my cluster ready and can monitor its Cluster Status from Velum:



As well as my respective Cluster Nodes from my Kubernetes dashboard:



With this I configure my Docker Registry to Use self-signed certificates and verify its availability:
424e441f1fef4c629d512f5fa33889f0:~ # curl -iv https://registry.dynalias.com:5000/v2
* Hostname was NOT found in DNS cache
* Trying 86.164.155.84...
* Connected to registry.dynalias.com (86.164.155.84) port 5000 (#0)
* successfully set certificate verify locations:
* CAfile: none
CApath: /etc/ssl/certs/
* SSLv3, TLS Unknown, Unknown (22):
* SSLv3, TLS handshake, Client hello (1):
* SSLv2, Unknown (22):
* SSLv3, TLS handshake, Server hello (2):
* SSLv2, Unknown (22):
* SSLv3, TLS handshake, CERT (11):
* SSLv2, Unknown (22):
* SSLv3, TLS handshake, Server key exchange (12):
* SSLv2, Unknown (22):
* SSLv3, TLS handshake, Server finished (14):
* SSLv2, Unknown (22):
* SSLv3, TLS handshake, Client key exchange (16):
* SSLv2, Unknown (20):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv2, Unknown (22):
* SSLv3, TLS handshake, Finished (20):
* SSLv2, Unknown (20):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv2, Unknown (22):
* SSLv3, TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* Server certificate:
* subject: C=UK; ST=Warwickshire; O=BOA; CN=registry.dynalias.com
* start date: 2018-01-14 12:17:16 GMT
* expire date: 2019-01-14 12:17:16 GMT
* common name: registry.dynalias.com (matched)
* issuer: C=UK; ST=Warwickshire; O=BOA; CN=registry.dynalias.com
* SSL certificate verify ok.
* SSLv2, Unknown (23):
> GET /v2 HTTP/1.1
> User-Agent: curl/7.37.0
> Host: registry.dynalias.com:5000
> Accept: */*
>
* SSLv2, Unknown (23):
< HTTP/1.1 301 Moved Permanently
HTTP/1.1 301 Moved Permanently
< Docker-Distribution-Api-Version: registry/2.0
Docker-Distribution-Api-Version: registry/2.0
< Location: /v2/
Location: /v2/
< Date: Wed, 17 Jan 2018 16:58:52 GMT
Date: Wed, 17 Jan 2018 16:58:52 GMT
< Content-Length: 39
Content-Length: 39
< Content-Type: text/html; charset=utf-8
Content-Type: text/html; charset=utf-8

<
<a href="https://blogs.sap.com/v2/">Moved Permanently</a>.

* Connection #0 to host registry.dynalias.com left intact

Next, I provide the Kubernetes Persistent Volumes required by the SAP Data Hub Distributed Runtime. Please ensure that their Capacity and Access modes are exactly as shown below, otherwise the Kubernetes Persistent Volume Claims could not be satisfied:



Finally, I install Helm to match Tiller:
424e441f1fef4c629d512f5fa33889f0:~ # curl -LO https://storage.googleapis.com/kubernetes-helm/helm-v2.6.2-linux-amd64.tar.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 15.5M 100 15.5M 0 0 6296k 0 0:00:02 0:00:02 --:--:-- 6299k
424e441f1fef4c629d512f5fa33889f0:~ # gunzip helm-v2.6.2-linux-amd64.tar.gz gzip: helm-v2.6.2-linux-amd64.tar already exists; do you wish to overwrite (y or n)? ^C
424e441f1fef4c629d512f5fa33889f0:~ # rm helm-v2.6.2-linux-amd64.tar
424e441f1fef4c629d512f5fa33889f0:~ # curl -LO https://storage.googleapis.com/kubernetes-helm/helm-v2.6.2-linux-amd64.tar.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 15.5M 100 15.5M 0 0 6478k 0 0:00:02 0:00:02 --:--:-- 6476k
424e441f1fef4c629d512f5fa33889f0:~ # gunzip helm-v2.6.2-linux-amd64.tar.gz 424e441f1fef4c629d512f5fa33889f0:~ # tar -xvf helm-v2.6.2-linux-amd64.tar linux-amd64/
linux-amd64/helm
linux-amd64/LICENSE
linux-amd64/README.md
424e441f1fef4c629d512f5fa33889f0:~ # cp linux-amd64/helm bin/

With this the installations runs smoothly and I am rewarded with a fully operational and supported SAP Data Hub Distributed Runtime:



If you needed more compute capacity, you could of course add more nodes.
11 Comments
Labels in this area