-
Notifications
You must be signed in to change notification settings - Fork 1
/
OCPtrng_SDI3onOCP4.6.md.bak
1274 lines (918 loc) · 46.4 KB
/
OCPtrng_SDI3onOCP4.6.md.bak
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
Install SAP Data Intelligence Lab
==================================
## Intro
This workshop demonstrates the installation of SAP Data Intelligence 3.1 on Red Hat OpenShift 4.6
## High-level architecture and components
The high-level architecture consists of 3 different RHEL 8.x servers:
- **bastion**: this is meant to be used as the jump host for SSH access to the environment and where to run SAP GUI from if required.
- **hana**: this is meant to be used as the RHEL server where you can deploy SAP HANA.
- **s4hana**: this is meant to be used as the RHEL server where you can deploy SAP S/4HANA.
And an OpenShift 4.x cluster with the following components deployed:
- **OpenShift Container Storage**: used for multi-purpose container storage backend.
[](https://redhat-sap.github.io/sap-workshops//sap-integration/img/infra_layout.png)
## prerequisites
To install SAP Data Intelligence (SDI) the following is needed
- A running Openshift Cluster with at least
- 3 master nodes
- 3 worker nodes for SDI with minimum requirements and for OCS storage
- Your SAP S-User data for downloading the software
- login credentials to the bastion host to access the Openshift Cluster
> **Note**
>
> In the test environment we install on 3 worker nodes including the storage, in a
> production environment it is recommended to have the SDI worker nodes and the
> storage worker nodes on separate nodes. For more detailed sizing guidelines look at
> https://access.redhat.com/articles/5100521#ftnt-ocs-requirements
Requirements and the minimum number of instances for each node type.
This is sufficient of a PoC (Proof of Concept) environments.
<table>
<caption>Openshift Requirements for SAP Data Intelligence Test Systems</caption>
<colgroup>
<col style="width: 14%" />
<col style="width: 14%" />
<col style="width: 14%" />
<col style="width: 14%" />
<col style="width: 14%" />
<col style="width: 14%" />
<col style="width: 14%" />
</colgroup>
<thead>
<tr class="header">
<th>Type</th>
<th>Count</th>
<th>Operating System</th>
<th>vCPU</th>
<th>RAM (GB)</th>
<th>Storage (GB)</th>
<th>AWS Instance Type</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td><p>Bootstrap</p></td>
<td><p>1</p></td>
<td><p>RHCOS</p></td>
<td><p>2</p></td>
<td><p>16</p></td>
<td><p>120</p></td>
<td><p>i3.large</p></td>
</tr>
<tr class="even">
<td><p>Master</p></td>
<td><p>3+</p></td>
<td><p>RHCOS</p></td>
<td><p>4</p></td>
<td><p>16</p></td>
<td><p>120</p></td>
<td><p>m4.xlarge</p></td>
</tr>
<tr class="odd">
<td><p>Compute</p></td>
<td><p>3+</p></td>
<td><p>RHEL 7.6 or RHCOS</p></td>
<td><p>4</p></td>
<td><p>32</p></td>
<td><p>120</p></td>
<td><p>m4.2xlarge</p></td>
</tr>
<tr class="even">
<td><p>Storage</p></td>
<td><p>3+</p></td>
<td><p>RHCOS</p></td>
<td><p>10</p></td>
<td><p>24</p></td>
<td><p>120</p></td>
<td><p>m5.4xlarge</p></td>
</tr>
</tbody>
</table>
## Verify the management workstation
1. Login to the managament host (you will find your login credentials in the Lab information)
ssh <admin-user>@<management host>
2. Ensure the following software is installed
- jq
# sudo dnf -y install jq
- openshift client
# OCP_VERSION=4.7.2
# wget https://mirror.openshift.com/pub/openshift-v4/clients/ocp/${OCP_VERSION}/openshift-client-linux-${OCP_VERSION}.tar.gz
# sudo tar zxvf openshift-client-linux-${OCP_VERSION}.tar.gz -C /usr/bin
# sudo rm -f openshift-client-linux-${OCP_VERSION}.tar.gz /usr/bin/README.md
# sudo chmod +x /usr/bin/oc /usr/bin/kubectl
3. setup bash completion (optional)
oc completion bash | sudo tee /etc/bash_completion.d/openshift > /dev/null
## Verify Openshift Cluster
1. make sure you have Openshift Cluster admin rights
[root@provisioner ~]# oc whoami
system:admin
2. Delete existing projects
# oc delete project serverless
# oc delete project side-by-sidecar
3. check, that min requirements are met:
# oc get nodes
ip-10-0-133-218.ec2.internal Ready master 47m v1.20.0+5fbfd19
ip-10-0-141-94.ec2.internal Ready worker 37m v1.20.0+5fbfd19
ip-10-0-154-232.ec2.internal Ready master 47m v1.20.0+5fbfd19
ip-10-0-159-127.ec2.internal Ready worker 40m v1.20.0+5fbfd19
ip-10-0-167-89.ec2.internal Ready master 48m v1.20.0+5fbfd19
ip-10-0-175-27.ec2.internal Ready worker 43m v1.20.0+5fbfd19
You should see 3 worker nodes and 3 master nodes
NOTE: If you see something like this after your systems shut down:
# oc get nodes
NAME STATUS ROLES AGE VERSION
ip-10-0-137-27.ec2.internal NotReady worker 2d23h v1.20.0+5fbfd19
ip-10-0-141-89.ec2.internal NotReady master 3d v1.20.0+5fbfd19
ip-10-0-154-182.ec2.internal NotReady master 3d v1.20.0+5fbfd19
ip-10-0-159-71.ec2.internal NotReady worker 2d23h v1.20.0+5fbfd19
ip-10-0-165-90.ec2.internal NotReady worker 2d23h v1.20.0+5fbfd19
ip-10-0-168-27.ec2.internal NotReady master 3d v1.20.0+5fbfd19
This can happen if the systems are shutdown for more then 24hrs and the certificates
are set invalid. The following command will manually approve the new certificates:
# oc adm certificate approve $(oc get csr | grep Pending | awk {'print $1'})
4. Store the worker names in a variable for later use:
# WORKER=$(oc get nodes | awk ' ( $3 ~ "worker" ) {print $1 }')
5. Check the hardware resources of the cluster Nodes
# oc describe node $WORKER | grep -A 6 Capacity
Capacity:
attachable-volumes-aws-ebs: 25
cpu: 16
ephemeral-storage: 125293548Ki
hugepages-1Gi: 0
hugepages-2Mi: 0
memory: 64792280Ki
--
Capacity:
attachable-volumes-aws-ebs: 25
cpu: 16
ephemeral-storage: 125293548Ki
hugepages-1Gi: 0
hugepages-2Mi: 0
memory: 64792280Ki
--
Capacity:
attachable-volumes-aws-ebs: 25
cpu: 16
ephemeral-storage: 125293548Ki
hugepages-1Gi: 0
hugepages-2Mi: 0
memory: 64792280Ki
So the minmum requirements 64 GiB memory and 120 GiB Storage are met
prepare OCP cluster for SDI
===========================
1. Label SDI compute Nodes
for n in $WORKER; do
oc label node/$n node-role.kubernetes.io/sdi=""
done
> **Note**
>
> If you want to remove the label again use
> `oc label node/$n node-role.kubernetes.io/sdi-`
2. Enable net-raw capability for containers on schedulable nodes
Check existing with:
oc get machineconfigs -o yaml 97-crio-net-raw
if this doesn’t exist run:
# oc create -f - <<EOF
apiVersion: machineconfiguration.openshift.io/v1
kind: MachineConfig
metadata:
labels:
machineconfiguration.openshift.io/role: sdi
name: 97-crio-net-raw
spec:
config:
ignition:
version: 2.2.0
storage:
files:
- contents:
source: data:text/plain;charset=utf-8;base64,W2NyaW8ucnVudGltZV0KZGVmYXVsdF9jYXBhYmlsaXRpZXMgPSBbCiAgICAgICAgIkNIT1dOIiwKICAgICAgICAiREFDX09WRVJSSURFIiwKICAgICAgICAiRlNFVElEIiwKICAgICAgICAiRk9XTkVSIiwKICAgICAgICAiU0VUR0lEIiwKICAgICAgICAiU0VUVUlEIiwKICAgICAgICAiU0VUUENBUCIsCiAgICAgICAgIk5FVF9CSU5EX1NFUlZJQ0UiLAogICAgICAgICJLSUxMIiwKICAgICAgICAiTkVUX1JBVyIsCl0K
verification: {}
filesystem: root
mode: 420
path: /etc/crio/crio.conf.d/90-default-capabilities
EOF
> **Note**
>
> If you get the message:
> `Error from server (AlreadyExists): error when creating "STDIN": machineconfigs.machineconfiguration.openshift.io "97-crio-net-raw" already exists`
> rerun with `oc replace -f`
3. Pre-load needed kernel modules
Check existing with:
oc get machineconfigs -o yaml 75-worker-sap-data-intelligence
The follwoing command prints the config file, if it exists on the
host
for worker in `oc get nodes | awk '/worker/{print $1}'`; do
oc debug node/$worker -- chroot /host cat /etc/modules-load.d/sdi-dependencies.conf
oc debug node/$worker -- chroot /host systemctl status sdi-modules-load.service
done
If the modules file does not exist run the following to create it:
# oc create -f - <<EOF
apiVersion: machineconfiguration.openshift.io/v1
kind: MachineConfig
metadata:
labels:
machineconfiguration.openshift.io/role: sdi
name: 75-worker-sap-data-intelligence
spec:
config:
ignition:
version: 2.2.0
storage:
files:
- contents:
source: "data:text/plain;charset=utf-8;base64,$content"
verification: {}
filesystem: root
mode: 420
path: /etc/modules-load.d/sdi-dependencies.conf
systemd:
units:
- contents: |
[Unit]
Description=Pre-load kernel modules for SAP Data Intelligence
After=network.target
[Service]
Type=oneshot
ExecStart=/usr/sbin/modprobe iptable_nat
ExecStart=/usr/sbin/modprobe iptable_filter
RemainAfterExit=yes
[Install]
WantedBy=multi-user.target
enabled: true
name: sdi-modules-load.service
EOF
4. PID limits
Check if PID Limits are already set:
# for worker in `oc get nodes | awk '/sdi-worker/{print $1}'`; do
oc debug node/$worker chroot /host -- cat /etc/crio/crio.conf.d/ /etc/crio/crio.conf.d/01-ctrcfg-pidsLimit
done | grep -i pids_limit
> **Note**
>
> the file path may change using a different OCP version
check if the config is already created:
oc get ContainerRuntimeConfigs -o yaml sdi-pids-limit
Create the runtime config
# oc create -f - <<EOF
apiVersion: machineconfiguration.openshift.io/v1
kind: ContainerRuntimeConfig
metadata:
name: sdi-pids-limit
spec:
machineConfigPoolSelector:
matchLabels:
workload: sapdataintelligence
containerRuntimeConfig:
pidsLimit: 16384
EOF
5. Associate MachineConfigs to the Nodes
The machine configs match to a machine config pool is labeled
`workload: sapdataintelligence`. the follwing command creates a
machine config pool out of nodes which have the role `SDI` labeled
`workload: sapdataintelligence`. Hence the new config is created on
these nodes by the machine operator.
# oc create -f - <<EOF
apiVersion: machineconfiguration.openshift.io/v1
kind: MachineConfigPool
metadata:
labels:
workload: sapdataintelligence
name: sdi
spec:
machineConfigSelector:
matchExpressions:
- key: machineconfiguration.openshift.io/role
operator: In
values:
- sdi
- worker
nodeSelector:
matchLabels:
node-role.kubernetes.io/sdi: ''
EOF
It may take a while until all nodes are updated. The following
command can be used to wait until the change gets applied to all the
worker nodes:
oc wait mcp/sdi --all --for=condition=updated
The following command lists steh status of the nodes:
oc get mcp
> **Note**
>
> If the update is not working, check the machineconfig operator
6. Double check that settings are made
you can use the following script to double check that all required
changes are made on the Openshift Worker nodes
#!/usr/bin/bash
# CHECK OCP (Note Files may change after update)
for worker in `oc get nodes|awk '/worker/{print $1}'`; do
echo "Checking node $worker ------------------------------------------------------------------------------"
# Check for additional kernelmodules
oc debug node/$worker -- chroot /host cat /etc/crio/crio.conf.d/90-default-capabilities 2> /dev/null
# Check for additional kernelmodules
oc debug node/$worker -- chroot /host cat /etc/modules-load.d/sdi-dependencies.conf 2> /dev/null
# check for module load service
oc debug node/$worker -- chroot /host systemctl status sdi-modules-load.service 2> /dev/null
# check for pidsLimit:
oc debug node/$worker -- chroot /host cat /etc/crio/crio.conf.d/01-ctrcfg-pidsLimit
echo "--------------------------------------------------------------------------------------------------------"
done
Configure Storage
=================
1. Check that OCS is properly installed
**TODO** → Please give hints how to do this
2. Create Project to keep SDI Storage
# oc new-project sdi-infra
3. Create S3 buckets for checkpoint store (required) and data lake
(optional)
# for claimName in sdi-checkpoint-store sdi-data-lake; do
oc create -f - <<EOF
apiVersion: objectbucket.io/v1alpha1
kind: ObjectBucketClaim
metadata:
name: ${claimName}
spec:
generateBucketName: ${claimName}
storageClassName: openshift-storage.noobaa.io
EOF
done
Expect the following output
objectbucketclaim.objectbucket.io/sdi-checkpoint-store created
objectbucketclaim.objectbucket.io/sdi-data-lake created
Check if buckets are created:
# oc get obc -w
NAME STORAGE-CLASS PHASE AGE
sdi-checkpoint-store openshift-storage.noobaa.io Bound 58s
sdi-data-lake openshift-storage.noobaa.io Bound 58s
4. Get the credentials required by the SDI installer
# for claimName in sdi-checkpoint-store sdi-data-lake; do
printf 'Bucket/claim %s:\n Bucket name:\t%s\n' "$claimName" "$(oc get obc -o jsonpath='{.spec.bucketName}' "$claimName")"
for key in AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY; do
printf ' %s:\t%s\n' "$key" "$(oc get secret "$claimName" -o jsonpath="{.data.$key}" | base64 -d)"
done
done | column -t -s $'\t' | tee storage-credentials.txt
Bucket/claim sdi-checkpoint-store:
Bucket name: sdi-checkpoint-store-22d885f0-da59-4d24-bffa-5e908bf78d1d
AWS_ACCESS_KEY_ID: < keep this >
AWS_SECRET_ACCESS_KEY: < keep this >
Bucket/claim sdi-data-lake:
Bucket name: sdi-data-lake-c132663c-b96b-4e6a-ba3b-01db3e999f82
AWS_ACCESS_KEY_ID: < keep this >
AWS_SECRET_ACCESS_KEY: < keep this >
Deploy SDI OBSERVER
===================
SDI Observer is a redhat monitoring software that controls the behaviour
and the proper installation of SDI
1. Create Namespaces for SDI Observer:
# NAMESPACE=sdi-observer SDI_NAMESPACE=sdi SLCB_NAMESPACE=sap-slcbridge
# for nm in $SDI_NAMESPACE $SLCB_NAMESPACE $NAMESPACE; do oc new-project $nm; done
2. Create a service account for `registry.redhat.io` at
<https://access.redhat.com/terms-based-registry/>, download and save
it to `rht-registry-secret.yaml`
3. Create the Pull Secret for redhat registry within sdi-observer
namespace:
# oc create -n "${NAMESPACE:-sdi-observer}" -f rht-registry-secret.yaml
4. set the variables for SDI Observer & install
You can influence the behaviour of SDI observer by setting certain
environment variables. See
<https://access.redhat.com/articles/5100521> section 4.1 for the
variable lists
NAMESPACE=sdi-observer
SDI_NAMESPACE=sdi
SLCB_NAMESPACE=sap-slcbridge
OCP_MINOR_RELEASE=4.7
#NODE_LOG_FORMAT=text
DEPLOY_SDI_REGISTRY=true
INJECT_CABUNDLE=true
#BUNDLE_SECRET_NAME=openshift-ingress-operator/router-ca
MANAGE_VSYSTEM_ROUTE=true
REDHAT_REGISTRY_SECRET_NAME=$(oc get secret | awk '/pull-secret/ { print $1 }')
SDI_NODE_SELECTOR=node-role.kubernetes.io/sdi=
oc process -f https://raw.githubusercontent.com/redhat-sap/sap-data-intelligence/master/observer/ocp-template.json \
NAMESPACE="${NAMESPACE:-sdi-observer}" \
SDI_NAMESPACE="${SDI_NAMESPACE:-sdi}" \
SLCB_NAMESPACE="${SLCB_NAMESPACE:-sap-slcbridge}" \
OCP_MINOR_RELEASE="${OCP_MINOR_RELEASE:-4.7}" \
DEPLOY_SDI_REGISTRY="${DEPLOY_SDI_REGISTRY:-true}" \
INJECT_CABUNDLE="${INJECT_CABUNDLE:-true}" \
MANAGE_VSYSTEM_ROUTE="${MANAGE_VSYSTEM_ROUTE:-true}" \
SDI_NODE_SELECTOR="${SDI_NODE_SELECTOR}" \
REDHAT_REGISTRY_SECRET_NAME="$REDHAT_REGISTRY_SECRET_NAME" | oc create -f -
> **Note**
>
> You can change or at variables at a later time with the following
> command:
> `oc set env -n sdi-observer dc/sdi-observer <variable name>=<value>`
> **Note**
>
> you can list the variables with
> `oc set env -n sdi-observer --list dc/sdi-observer`
5. wait until sdi-observer and registry pods are running:
$ oc get pods
NAME READY STATUS RESTARTS AGE
container-image-registry-1-build 0/1 Completed 0 3m20s
container-image-registry-1-deploy 0/1 Completed 0 82s
container-image-registry-1-jkrx8 1/1 Running 0 79s
deploy-registry-4gccn 0/1 Completed 0 3m26s
sdi-observer-1-build 0/1 Completed 0 5m48s
sdi-observer-1-deploy 0/1 Completed 0 3m53s
sdi-observer-1-xphzw 1/1 Running 0 3m49s
You can follow the deployment processes with e.g.
oc logs sdi-observer-1-build -f
oc logs container-image-registry-1-build -f
6. Check Registry, get the credentials and and configure OCP to trust
do appropriate settings:
The follwoing script tests the registry, prints the access
credentials and makes some required additional settings in the
cluster to trust the deployed DEPLOY\_SDI\_REGISTRY:
#!/bin/bash
## Change Namespace to sdi-observer
NAMESPACE="${NAMESPACE:-sdi-observer}"
oc project sdi-observer
## Obtain registry credentials
reg_credentials=$(oc get -n "${NAMESPACE:-sdi-observer}" secret/container-image-registry-htpasswd -o jsonpath='{.data.\.htpasswd\.raw }' | base64 -d )
reg_user=$(echo $reg_credentials| cut -d: -f1)
reg_pw=$(echo $reg_credentials| cut -d: -f2)
## Obtain registry hostname
reg_hostname="$(oc get route -n "${NAMESPACE:-sdi-observer}" container-image-registry -o jsonpath='{.spec.host}')"
echo "================================================="
echo "Using registry: $reg_hostname"
echo "USER: $reg_user"
echo "PW : $reg_pw"
echo "================================================="
if [ -z "$reg_user" -o -z "$reg_pw" ]; then
echo "Something went wrong. Check if the pods are running"
exit 1
fi
### Obtain Ingress Router's default self-signed CA certificate
mkdir -p "/etc/containers/certs.d/${reg_hostname}"
router_ca_crt="/etc/containers/certs.d/${reg_hostname}/router-ca.crt"
oc get secret -n openshift-ingress-operator -o json router-ca | \
jq -r '.data as $d | $d | keys[] | select(test("\\.crt$")) | $d[.] ' | base64 -d > ${router_ca_crt}
### test via curl
curl -k -I --user ${reg_credentials} --cacert ${router_ca_crt} "https://${reg_hostname}/v2/"
### test via podman
echo $reg_pw | podman login -u $reg_user --password-stdin ${reg_hostname}
reg_login_ok=$?
if [ $reg_login_ok ]; then
# Configure Openshift to trust container registry (8.2)
echo "Configure Openshift to trust container registry"
echo "CTRL-C to stop, ENTER to continue"
read zz
caBundle="$(oc get -n openshift-ingress-operator -o json secret/router-ca | \
jq -r '.data as $d | $d | keys[] | select(test("\\.(?:crt|pem)$")) | $d[.]' | base64 -d)"
# determine the name of the CA configmap if it exists already
cmName="$(oc get images.config.openshift.io/cluster -o json | \
jq -r '.spec.additionalTrustedCA.name // "trusted-registry-cabundles"')"
if oc get -n openshift-config "cm/$cmName" 2>/dev/null; then
# configmap already exists -> just update it
oc get -o json -n openshift-config "cm/$cmName" | \
jq '.data["'"${reg_hostname//:/..}"'"] |= "'"$caBundle"'"' | \
oc replace -f - --force
else
# creating the configmap for the first time
oc create configmap -n openshift-config "$cmName" \
--from-literal="${reg_hostname//:/..}=$caBundle"
oc patch images.config.openshift.io cluster --type=merge \
-p '{"spec":{"additionalTrustedCA":{"name":"'"$cmName"'"}}}'
fi
# Check that the certifcate is deployed
sleep 10 # give some time for configuration
oc rsh -n openshift-image-registry "$(oc get pods -n openshift-image-registry -l docker-registry=default | \
awk '/Running/ {print $1; exit}')" ls -1 /etc/pki/ca-trust/source/anchors
else
echo "Registry setup failed, please repair before you continue"
fi
## Ensure that the project service accounts have correct priviledges
# oc project sdi
# oc adm policy add-scc-to-group anyuid "system:serviceaccounts:$(oc project -q)"
# oc adm policy add-scc-to-user privileged -z "$(oc project -q)-elasticsearch"
# oc adm policy add-scc-to-user privileged -z "$(oc project -q)-fluentd"
# oc adm policy add-scc-to-user privileged -z default
# oc adm policy add-scc-to-user privileged -z mlf-deployment-api
# oc adm policy add-scc-to-user privileged -z vora-vflow-server
# oc adm policy add-scc-to-user privileged -z "vora-vsystem-$(oc project -q)"
# oc adm policy add-scc-to-user privileged -z "vora-vsystem-$(oc project -q)-vrep"
Install SDI Install Bridge
--------------------------
Now that the SDI observer is running, we can install the SDI Install
Bridge container that is used to install SDI on the cluster. The
following steps should run as the user `admin`.
# oc login -u admin
# oc whoami
admin
> **Note**
>
> This document assumes your cluster has direct internet access. If you
> require proxy settings follow the steps in
> <https://access.redhat.com/articles/5100521> section 5.1
1. Download the SAP install bridge from SAP (you need your S-User now)
Go to the maintenance planner (MP) at https://apps.support.sap.com/sap/support/mp and create a new system:
** Bilder **
Download the corresponding SLCB* file
Alternatively you can download SLCB01\_<Version>.EXE for Linux directly from
<https://support.sap.com/>, rename it to `slcb` and make it
executable (click `Software Downloads` and enter `Software Lifecycle Container Bridge` in the search field)
# mv SLCB01_*.EXE /usr/bin/slcb
# chmod +x /usr/bin/slcb
2. Install SDI Install Bridge
> **Note**
>
> This tutorial is tested with version 1.1.58. You can always
> install this version with
> `` `slcb init --bridgebaseVersion 1.1.58 ``, but any later version
> should do, too.
When answering the installer, the following selections are important:
- Installation Type: Expert Mode
- Service Type
1. on AWS choose Loadbalancer.
You do not need to give annotations
2. on all other choose NodePort
- Have a look at <https://access.redhat.com/articles/5100521>, if
you need to configure proxies - This lab has direct
connection to the internet
- You need to provide the following information:
- Address of the Container Image Repository
- Image registry user name
- Image registry password
- Your S-USer + password
- admin user password
Now you need the different credentials and information you noted
earlier. Execute `slcb init`. Here is an example log:
$ slcb init
'slcb' executable information
Executable: slcb
Build date: 2021-03-26 03:45:45 UTC
Git branch: fa/rel-1.1
Git revision: 4f99471a2f764f65da2d72ef74c5259e8639697e
Platform: linux
Architecture: amd64
Version: 1.1.62
SL Core version: 1.0.0
SLUI version: 2.6.67
Arguments: init
Working dir: /home/generic_emea_mkoch
Schemata: 0.0.62, 1.13.62
Explanation of supported shortcuts:
<F1>: Display help for input value.
<ENTER> or <Ctrl-N>: Confirm and continue to next input value.
<F12> or <Ctrl-B>: Go back to previous input value.
<r>: Retry current step.
<e>: Edit a multi-line input value.
<Ctrl-C>: Abort current processing and return to the Welcome dialog of the SLC Bridge Base.
Ctrl-C is not explicitly shown as an option in the command line prompt but you can always use it.
<Tab>: Completion of input values.
In dialogs that accept only a restricted set of values (like files, directories etc)
use the <Tab> key to cycle through the values or for completion of incomplete input.
Execute step Download Bridge Images
***********************************
* Product Bridge Image Repository *
***********************************
Enter the address of your private container image repository used to store the bridge images.
You require read and write permissions for this repository.
Choose action <F12> for Back/<F1> for help
Address of the Container Image Repository: container-image-registry-sdi-observer.apps.cluster-bf86.bf86.example.opentlc.com
************************
* Image Registry User *
************************
The user name used to logon to "container-image-registry-sdi-observer.apps.cluster-bf86.bf86.example.opentlc.com".
Choose action <F12> for Back/<F1> for help
Image registry user name: user-q5j0lq
Choose action <F12> for Back/<F1> for help
Image registry password:
***************************
* Enter Logon Information *
***************************
You require S-User credentials to log on to the SAP Registry ("rhapi.repositories.cloud.sap") for product version "SL TOOLSET 1.0" (01200615320900005323)
Choose action <F12> for Back/<F1> for help
S-User Name: S0001234567
Choose action <F12> for Back/<F1> for help
Password:
Copying image slcb://01200615320900005323.dockersrv.repositories.sapcdn.io/com.sap.sl.cbpod/slcbridgebase:1.1.62 to "container-image-registry-sdi-observer.apps.cluster-bf86.bf86.example.opentlc.com"
Copying image slcb://01200615320900005323.dockersrv.repositories.sapcdn.io/com.sap.sl.cbpod/nginx-sidecar:1.1.62 to "container-image-registry-sdi-observer.apps.cluster-bf86.bf86.example.opentlc.com"
Checking prerequisite
Execute step Check Prerequisites
I0331 13:01:04.372152 6354 request.go:621] Throttling request took 1.153431509s, request: GET:https://api.cluster-bf86.bf86.example.opentlc.com:6443/apis/flows.knative.dev/v1beta1?timeout=32s
Checking prerequisite Kubernetes Server Version
************************
* Prerequiste Check *
************************
Checking the prerequisites for "SL Container Bridge" succeeded.
Kubernetes Cluster Context:
Cluster name: api-cluster-bf86-bf86-example-opentlc-com:6443
API server URL: https://api.cluster-bf86.bf86.example.opentlc.com:6443
Editable Prerequisites
Enter the path to the "kubectl" configuration file. The configuration information contained in this file will specify the cluster on which you are about to
perform the deployment.
Choose action <Tab> for completion/<F1> for help
Path to the "kubeconfig" file: ESC[1G Path to the "kubeconfig" file: /home/generic_emea_mkoch/.kube/configESC[0KESC[71G
Prerequisite Check Result
Name Current Value Result Error Message
KUBECONFIG /home/generic_emea_mkoch/.kube/config + (passed)
Kubernetes Server Version 1.20.0 + (passed)
Choose "Retry (r)" to retry the Prerequisite Check.
Choose "Next (n)" to continue.
Choose action Retry(r)/Next(n)/<F1> for help: n
Execute step Collect Input
***************************************************************************
* Choose whether you want to run the deployment in typical or expert mode *
***************************************************************************
You can run the deployment either in typical or expert mode:
- Typical Mode
If you choose "Typical Mode", the option is performed with default settings. As a result, you only have to respond to a small selection of prompts.
- Expert Mode
If you choose "Expert Mode", you are prompted for all parameters.
> 1. Typical Mode
2. Expert Mode
Choose action <F12> for Back/<F1> for help
possible values [1,2]: 2
************************
* SLC Bridge Namespace *
************************
Enter the Kubernetes namespace for the SLC Bridge.
Choose action <F12> for Back/<Tab> for completion/<F1> for help
Namespace: sap-slcbridge
************************
* Administrator User *
************************
Specify the name of the administrator user for the SLC Bridge Base.
Choose action <F12> for Back/<F1> for help
User Name: admin
*******************************
* Administrator User Password *
*******************************
Define the password of the administrator user admin
Choose action <F12> for Back/<F1> for help
Password of User admin:
Confirm:
***********************************************
* Service Type of the SLC Bridge Base Service *
***********************************************
In order to access the SLC Bridge Base, the UI Port needs to be exposed. This is accomplished by defining a Kubernetes service.
Kubernetes offers multiple service types. SAP currently supports the following service types. You have to select one of them.
- Service Type "LoadBalancer" is suitable if your Kubernetes cluster comes with a controller for this service type. For example, this is the case for all
hyperscaler platforms.
- Service Type "NodePort" is suitable if your Kubernetes cluster runs on premise and the cluster nodes can be reached from your network
> 1. Service Type LoadBalancer
2. Service Type NodePort
Choose action <F12> for Back/<F1> for help
possible values [1,2]: 2
************************
* Proxy Settings *
************************
Do you want to configure Proxy Settings for the Pods running in the cluster?
This is necessary if the Pods in the cluster are running behind a proxy.
Configure Proxy Settings: n
Choose action <F12> for Back/<F1> for help
possible values [yes(y)/no(n)]: n
Execute step Show Summary
************************
* Parameter Summary *
************************
Choose "Next" to start the deployment with the displayed parameter values or choose "Back" to revise the parameters.
SLC Bridge Namespace
Namespace: sap-slcbridge
Image Registry User
Image registry user name: user-q5j0lq
SLP_BRIDGE_REPOSITORY_PASSWORD
Enter Logon Information
S-User Name: S0000000000
IMAGES_SAP_SUSER_PASSWORD
KUBECONFIG
Path to the "kubeconfig" file: /home/generic_emea_mkoch/.kube/config
Choose whether you want to run the deployment in typical or expert mode
1. Typical Mode
> 2. Expert Mode
Administrator User
User Name: admin
Administrator User Password
Service Type of the SLC Bridge Base Service
1. Service Type LoadBalancer
> 2. Service Type NodePort
Proxy Settings
Configure Proxy Settings: n
Choose "Next" to start the deployment with the displayed parameter values or choose "Back" to revise the parameters.
Choose action <F12> for Back/Next(n)/<F1> for help: ESC[1G Choose action <F12> for Back/Next(n)/<F1> for help: n
Apply Secret Template (secret-slcbridge.yml)...
Execute step Master secret
Apply Secret Template (secret-nginx.yml)...
Execute step Nginx secret
Execute step Wait for Kubernetes Object SLCBridgeNamespace
Execute step Wait for Kubernetes Object SLCBridgeServiceAccount
Execute step Wait for Kubernetes Object DefaultsMap
Execute step Execute Service
Execute step Wait for Kubernetes Object ProductHistory
Execute step Wait for Kubernetes Object MasterSecret
Execute step Wait for Kubernetes Object NginxSecret
Execute step Wait for Kubernetes Object SLCBridgePod
Execute step SL Container Bridge
************************
* Message *
************************
Deployment "slcbridgebase" has 1 available replicas in namespace "sap-slcbridge"
Service slcbridgebase-service is listening on any of the kubernetes nodes on "https://node:30713/docs/index.html"
Choose action Next(n)/<F1> for help: n
Execute step Get User Feedback
******************************
* Provide feedback to SAP SE *
******************************
Dear user, please help us improve our software by providing your feedback (press <F1> for more information).
> 1. Fill out questionnaire
2. Send analytics data only
3. No feedback
Choose action <F12> for Back/<F1> for help
possible values [1,2,3]: 3
Execute step Service Completed
> **Note**
>
> this is an interactive script, which currently cannot run
> unattended
3. Check Bridge is running:
If everything went well you can see the resources like this:
$ oc -n sap-slcbridge get all
NAME READY STATUS RESTARTS AGE
pod/slcbridgebase-6cd8b94579-4l72q 2/2 Running 0 24m
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/slcbridgebase-service NodePort 172.30.122.31 <none> 9000:30578/TCP 24m
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/slcbridgebase 1/1 1 1 24m
NAME DESIRED CURRENT READY AGE
replicaset.apps/slcbridgebase-6cd8b94579 1 1 1 24m
4. connect to the bridge
Get the exposed node port and pick an IP address of one of the nodes
and point your browser to:
[https://<IP>:<NodePort>/docs/index.html](https://<IP>:<NodePort>/docs/index.html)
- Get IP:
oc get node -o wide sdi-worker-1
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
sdi-worker-1 Ready sdi,worker 14d v1.19.0+9c69bdc 10.19.20.160 <none> Red Hat Enterprise Linux CoreOS 46.82.202101131942-0 (Ootpa) 4.18.0-193.40.1.el8_2.x86_64 cri-o://1.19.1-2.rhaos4.6.git2af9ecf.el8
- Get Port
oc get svc -n "${SLCB_NAMESPACE:-sap-slcbridge}" slcbridgebase-service -o jsonpath=$'{.spec.ports[0].nodePort}\n'
30578
In this example point your browser to
<https://10.19.20.160:30578/docs/index.html>
> **Note**
>
> Username/Password: Use the one that you provided during