vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Red Hat OpenShift on IBM Cloud clusters come with all the same configurable project and build components as OCP clusters. You can also choose to integrate your cluster with IBM Cloud services like [Continuous Delivery](https://cloud.ibm.com/docs/openshift?topic=openshift-cicd). 
 Cluster health You can also set up logging, monitoring, and metering tools by installing and configuring various operators. These solutions are cluster-specific and not highly available unless you back them up. Your clusters feature one-click integrations with IBM Log Analysis and IBM Cloud Monitoring for enterprise-grade, persistent monitoring and logging solutions across clusters. You can also install the logging and monitoring operators as with standard OCP, but you might have to adjust the configuration settings. For more information, see [Logging and monitoring cluster health](https://cloud.ibm.com/docs/openshift?topic=openshift-health). 
 Migrating clusters You can use the cluster migrator operator to migrate clusters from one major version to another. Migration requires separate clusters; you can't update a cluster from one major version to another. Various open source tools might be used, but are not officially supported. As with standard OpenShift Container Platform, you can't update a cluster from one major version to another. If you use a third-party open source tool such as the [cluster migrator operator](https://github.com/migtools/mig-operator), the tool is not supported by IBM and might have limitations such as the migration UI being unavailable. 
 Container-native virtualization You can set up [container-native virtualization add-on](https://docs.openshift.com/container-platform/4.11/virt/about-virt.html) on bare metal machines, but not on virtual machines. Container-native virtualization is not supported by IBM. If you experience issues, you are responsible for resolving the issues and any impact to your workloads.
rhn_password The [Red Hat Network password](https://access.redhat.com/solutions/253273)![External link icon](https://cloud.ibm.com/docs-content/v1/content/4cd6263f39a034d265ddb4b0a5e6d50c55d13ee8/ibm-cloud-provider-for-terraform/icons/launch-glyph.svg) to access the OpenShift project. You can enter this information here or provide it as part of your OpenShift deployment in [Lesson 2](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-redhatprovision_infrastructure). n/a 
 rhn_username The [Red Hat Network user name with OpenShift subscription](https://access.redhat.com/solutions/253273)![External link icon](https://cloud.ibm.com/docs-content/v1/content/4cd6263f39a034d265ddb4b0a5e6d50c55d13ee8/ibm-cloud-provider-for-terraform/icons/launch-glyph.svg) to access the OpenShift project. You can enter this information here or provide it as part of your OpenShift deployment in [Lesson 2](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-redhatprovision_infrastructure). n/a 
 private_vlanid Enter the VLAN ID of your existing private VLAN that you want to use. To find existing VLAN IDs, run ibmcloud sl vlan list and review the ID column. n/a 
 public_vlanid Enter the VLAN ID of your existing public VLAN that you want to use. To find existing VLAN IDs, run ibmcloud sl vlan list and review the ID column. n/a
* SAP BW/4HANA, which uses SAP HANA scale-up (world record, as of writing - 2020-07-01)
* SAP BW/4HANA, which uses SAP HANA scale-out









 SAP's Platform-as-a-Service (PaaS) offerings 

IBM Cloud also enables the use of cloud-native SAP technologies. IBM-SAP work on multiple open source projects together and both companies use similar technology underpinnings. You can reduce your SAP implementation project timelines and long-term maintenance by adopting the "Side-by-Side Extensibility" model that SAP recommends for custom development with their SAP Business Applications.

The portfolio includes a variation of SAP's Platform-as-a-Service, which is designed for increased security of cloud-native SAP extensions. This SAP PaaS variation can be combined with IBM Cloud's various PaaS options, functions, and services.

Affiliate offerings for SAP's PaaS by request only:



* SAP Cloud Platform Private Edition, using Red Hat OpenShift Virtualization



However, the core cloud-native SAP technologies are able to be used directly with Red Hat OpenShift on IBM Cloud or other IBM Cloud capabilities (such as Cloud Foundry) in the same way as deploying to SAP Cloud Platform. This is because many of the cloud-native SAP technologies are built upon widely supported cloud-native technologies. However to deploy outside of the SAP Cloud Platform ecosystem requires general knowledge of cloud-native technologies, and will require more manual effort (not described in this documentation series) because the SAP multitarget application (MTA) archive format is not supported outside SAP Cloud Platform.

Cloud-native SAP technologies which are portable, directly to Red Hat OpenShift on IBM Cloud or Cloud Foundry from IBM Cloud, examples include:



* [SAP Fundamental Library Styles component library](https://sap.github.io/fundamental-styles) for UI Frameworks (Angular, React, Vue, and other frameworks)
* [SAPUI5 Framework](https://sapui5.hana.ondemand.com) (and upstream project [OpenUI5](https://openui5.org))







 SAP's Software-as-a-Service (SaaS) offerings
Review the state of a Red Hat OpenShift cluster to get information about the availability and capacity of the cluster, and potential problems that might occur.

To view information about a specific cluster, such as its zones, service endpoint URLs, Ingress subdomain, version, and owner, use the ibmcloud oc cluster get --cluster <cluster_name_or_ID>[command](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_get). Include the --show-resources option to view more cluster resources such as add-ons for storage pods or subnet VLANs for public and private IPs.

You can review information about the overall cluster, the IBM-managed master, and your worker nodes. To troubleshoot your cluster and worker nodes, see [Troubleshooting clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-debug_clusters).

For more information about cluster and worker states, see:



* [Cluster states](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-states-reference).
* [Worker node states](https://cloud.ibm.com/docs/openshift?topic=openshift-worker-node-state-reference).





 Master states 

Your Red Hat OpenShift on IBM Cloud cluster includes an IBM-managed master with highly available replicas, automatic security patch updates applied for you, and automation in place to recover in case of an incident. You can check the health, status, and state of the cluster master by running ibmcloud oc cluster get --cluster <cluster_name_or_ID>.

The Master Health reflects the state of master components and notifies you if something needs your attention. The health might be one of the following states.



* error: The master is not operational. IBM is automatically notified and takes action to resolve this issue. You can continue monitoring the health until the master is normal.
Verify that the logging instance is created by completing the following tasks.



1. Switch to the Workloads → Pods page.
2. Select the openshift-logging project. A list of several pods displays. The list of pods looks similar to the following list and includes pods for cluster logging, Elasticsearch, Fluentd, and Kibana:



* cluster-logging-operator-cb795f8dc-xkckc
* elasticsearch-cdm-b3nqzchd-1-5c6797-67kfz
* elasticsearch-cdm-b3nqzchd-2-6657f4-wtprv
* elasticsearch-cdm-b3nqzchd-3-588c65-clg7g
* fluentd-2c7dg
* fluentd-9z7kk
* fluentd-br7r2
* fluentd-fn2sb
* fluentd-pb2f8
* fluentd-zqgqx
* kibana-7fb4fd4cc9-bvt4p







 Starting Kibana 

You can start Kibana from the menu bar of the Red Hat OpenShift on IBM Cloud console.



1. Click the 3x3 matrix icon in the menu bar.
2. Select Observability → Logging.
3. The first time that you access Kibana you must use your IBM Cloud credentials to log in.









 Step 6: Set up virtual server instance logging with Fluentd 

The EFK stack that is deployed in Red Hat OpenShift on IBM Cloud can also be used to aggregate application and infrastructure logs from virtual server instances. The following instructions describe how to install and configure Fluentd on a virtual server instance so that it can forward its logs to an Elasticsearch cluster.



 Preparing the Elasticsearch cluster to receive logs 

Fluentd should use a Red Hat OpenShift on IBM Cloud private endpoint when sending log data to the Elasticsearch cluster.
Planning your SAP Data Intelligence deployment 

Currently, SAP Data Intelligence 3.2 is available for Red Hat OpenShift Container Platform 4.8 in IBM Cloud. IBM Cloud manages the platform for you; you select the size and number of worker nodes and the geographic locations of one or more data centers.

When planning your deployment, you set the flavor of your worker nodes within your Red Hat OpenShift on IBM Cloud on the IBM Cloud cluster. Flavor describes the compute resources, such as number of CPUs or vCPUs, amount of memory, and disk capacity that you order when provisioning your worker nodes. The total number of worker nodes in a cluster determines the compute capacity that is available to your apps in the cluster. For more information, see [Planning your worker node setup](https://cloud.ibm.com/docs/openshift?topic=openshift-planning_worker_nodes).



 Red Hat OpenShift Cluster Network Connectivity 

SAP Data Intelligence allows you to connect a wide range of systems and components, as long as the required network connectivity is in place.

To be sure the connections between systems and components meet the requirements, we strongly recommend to combine planning of the SAP Data Intelligence network layout with planning the systems you want to connect. Planning both aspects jointly, will ensure that network communication is possible for the required protocols (i.e. required firewall rules, DMZ setups, and so on).

For an enhanced security, we recommend using:



* Properly encrypted communication for all channels, in particular leveraging transport layer security (TLS).
* A common certificate authority (CA) that can be imported as a trusted source in the various components.



For more information, see the [Administration Guide for SAP Data Intelligence](https://help.sap.com/viewer/b13b5722c8ff4bf9bb097251310031d0/latest/en-US/884ffcd587784ed2a311b2c19feb8410.html).

For productive setups, we recommend preparing the required SSL certificates using the preferred tools. For non-productive setups, note that the SAP Data Intelligence installer can generate self-signed certificates.





 Red Hat OpenShift Cluster Storage
Edit your service and change the service type to NodePort.

oc edit svc/nginx
7. Access your nginx app from the internet.



1. Get the public route that was assigned to your nginx app. You can find the route in the HOST/PORT column of your command line output.

oc get routes

Example output:

NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD
nginx-example nginx-example-new.apps.158.123.12.123.xip.io nginx-example all None
2. In your preferred web browser, open your app by using the public route.

http://nginx-example-new.apps.158.176.91.200.xip.io





What's next?
Great! You successfully installed Red Hat OpenShift Container Platform on IBM Cloud classic infrastructure and deployed your first app to your OpenShift cluster. Now you can try out one of the following features:



* [Explore other features in Red Hat OpenShift Container Platform ![External link icon](https://cloud.ibm.com/docs-content/v1/content/4cd6263f39a034d265ddb4b0a5e6d50c55d13ee8/icons/launch-glyph.svg)](https://docs.openshift.com/container-platform/3.11/welcome/index.html).
* Remove your OpenShift cluster by running the make destroy command.
With the oc new-app command you can create applications from source code in a local or remote Git repository.



1. Create an application using the docker build strategy to build a container image from a Dockerfile in the repo. You are setting the application name to the project name for simplicity.

oc new-app https://github.com/IBM-Cloud/openshift-node-app --name=$MYPROJECT --strategy=docker --as-deployment-config

If a Jenkins file exists in the root or specified context directory of the source repository when creating a new application, Red Hat OpenShift on IBM Cloud generates a pipeline build strategy. Otherwise, it generates a source build strategy.You can always override the build strategy by setting the --strategy flag.
2. To check the builder container image creation and pushing to the Internal Red Hat OpenShift on IBM Cloud Container Registry (OCR), run the below command

oc logs -f buildconfig/$MYPROJECT

Your cluster is set up with the internal Red Hat OpenShift on IBM Cloud Container Registry so that Red Hat OpenShift on IBM Cloud can automatically build, deploy, and manage your application lifecycle from within the cluster.
3. Wait till the build is successful and the image is pushed. You can check the status of deployment and service using

oc status







 Access the app through IBM provided domain 

To access the app, you need to create a route. A route announces your service to the world.



1. Create a route by running the below command in a terminal

oc expose service/$MYPROJECT
2. You can access the app through IBM provided domain. Run the below command for the URL

oc get route/$MYPROJECT
3. Copy the HOST/PORT value and paste the URL in a browser to see your app in action at http://<HOST/PORT>. Also, set an environment variable pointing to the hostname

export HOST=<HOST>







 Secure the default IBM provided domain route 



1.
Evaluate the compliance of your Red Hat OpenShift on IBM Cloud clusters 

By using the OpenShift Compliance Operator (OSCO) through Security and Compliance Center, you can run scans to validate your level of compliance to a grouping of controls, also known as a profile. In this scenario, you configure your cluster to be able to run the OSCO scan.



 Before you begin 

Before you get started with this tutorial, be sure you have the prerequistes:



* An IBM Cloud account
* A Red Hat OpenShift on IBM Cloud cluster
* The required permissions:



Table 1. Required user permissions

 Service Required role Reason 

 Security and Compliance Center Compliance Management Needed to enable a service-to-service authorization <br>To view this role, you must be assigned the Administrator role for the service 
 Red Hat OpenShift on IBM Cloud Manager Required to install OSCO 









 Step 1: Enable an authorization 

To ensure that the services can talk with each other, create a service-to-service authorization between Security and Compliance Center and Kubernetes Service. To create this policy, you must have the Administrator platform role for the Security and Compliance Center service.



1. In the IBM Cloud console, go to Manage > Access (IAM) and select Authorizations.
2. Click Create.
3. If you're working in an enterprise account, select the account which has the cluster with OSCO deployed in it as the Source account.
4. Select Security and Compliance Center in the Source drop-down and choose All resources as the scope.
5. Select Kubernetes Service in the Target drop-down. Optionally, you can narrow the focus by selecting specific resources that you want to target.
6. Select Platform access as Compliance Management and click Authorize.



If you are scanning Satellite resources, you must also [enable an authorization for Satellite](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-assign-rolesassign-access-sat).





 Step 2: Install the OSCO 

Before you can start evaluating your resources, the OSCO must be installed to your cluster.
: With the [open source Portieris project](https://github.com/IBM/portieris), you can set up a Kubernetes admission controller to enforce image security policies by namespace or cluster. Use [Portieris](https://cloud.ibm.com/docs/Registry?topic=Registry-security_enforce_portieris) instead of the deprecated Container Image Security Enforcement Helm chart.





 19 November 2020 

Ingress ALB change log
: Updated the [nginx-ingress build to 653 and the ingress-auth build to 425](https://cloud.ibm.com/docs/containers?topic=containers-cluster-add-ons-changelogkube_ingress_changelog) for the Red Hat OpenShift on IBM Cloud Ingress image.





 18 November 2020 

CLI change log
: Updated the Red Hat OpenShift on IBM Cloud CLI plug-in change log page for the [release of version 1.0.197](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_cli_changelog10).

New! Block Storage for VPC change log
: Added a [change log](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc_bs_changelog) for the Block Storage for VPC add-on.





 16 November 2020 

New! GPU support in Red Hat OpenShift 4
: Now, you can create GPU bare metal worker nodes in your Red Hat OpenShift on IBM Cloud version 4 clusters in select zones. GPU machines are suited for high-performance computing, machine learning, or 3D applications that you might have, such as [IBM Maximo Visual Inspection](https://www.ibm.com/products/maximo/remote-monitoring).
: To get started with GPU-accelerated workloads.
For example, your cluster administrator might have [set up the image stream to import an image from an external private registry](https://cloud.ibm.com/docs/openshift?topic=openshift-registryimagestream_registry), such as IBM Cloud Container Registry.



 Using an image stream with the CLI 



1. [Access your Red Hat OpenShift cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster).
2. List the available image streams in a project. If you know the project, name, and tag of the image stream, you can use local image streams in other projects without setting up image pull stream credentials.

oc get is -n <project>
3. Create your app from the image stream.

oc new-app --image-stream="<project>/<imagestream>:<tag>"







 Using an image stream from the Red Hat OpenShift web console 



1. From the [Red Hat OpenShift web console](https://cloud.ibm.com/docs/openshift?topic=openshift-deploy_appdeploy_apps_ui), switch to the Developer perspective and click +Add.
2. In the Add pane menu bar, select a Project that is not default to create your app in, and click Container Image.
3. In the Image section, select Image name from internal registry.
4. Select defaultProject, <image>ImageStreams, and <tag>Tag of the image stream that you previously created.
5. Review the rest of the application details, and click Create.









 Deploying containers from an IBM Cloud Container Registry image to the default Red Hat OpenShift project 

You can deploy containers to your cluster from an IBM-provided public image or a private image that is stored in your IBM Cloud Container Registry namespace.
[Setting up a Red Hat OpenShift for HPC cluster](https://cloud.ibm.com/docs/hpc-openshift?topic=hpc-openshift-setting-up-red-hat-openshift-hpc-cluster)Setting up a Red Hat OpenShift for HPC cluster

While IBM values the use of inclusive language, terms that are outside of IBM's direct influence are sometimes required for the sake of maintaining user understanding. As other industry leaders join IBM in embracing the use of inclusive language, IBM will continue to update the documentation to reflect those changes.

Virtual Private Cloud (VPC) IBM Cloud Load Balancer

+3

Monitoring,Log Analysis,Red Hat OpenShift for HPC



* 60 minutes
* 2022-04-14



[Integrating OpenLDAP with IBM Spectrum Symphony](https://cloud.ibm.com/docs/hpc-spectrum-symphony?topic=hpc-spectrum-symphony-integrate-openldap-spectrum-symphony)Integrating OpenLDAP with IBM Spectrum Symphony

In the following tutorial, you learn how to integrate OpenLDAP with IBM Spectrum Symphony, which is a high-performance distributed computing platform. OpenLDAP is an open source implementation of the Lightweight Directory Access Protocol (LDAP) that can be used to store and manage information about users, groups, and other objects in a network.

IBM Spectrum Symphony



* 2023-05-31



[Adding Spectrum multicluster (SMC) to Spectrum Symphony ](https://cloud.ibm.com/docs/hpc-spectrum-symphony?topic=hpc-spectrum-symphony-smc-adding-to-symphony)Adding Spectrum multicluster (SMC) to Spectrum Symphony

The Spectrum multicluster feature in IBM Spectrum Symphony Advanced Edition is used to connect multiple IBM Spectrum Symphony clusters into a federation cluster. Using this feature, you can:

Virtual Private Cloud (VPC) IBM Spectrum Symphony



* 1 hour
* 2023-05-02
Consult your provider documentation for more information about how to boot your host and include a file path to the ignition script.
3. As you run the scripts on each machine, check that your hosts are shown in the Hosts tab of your location dashboard. This process might take a few minutes to complete. All hosts show a Health status of Ready when a heartbeat for the machine can be detected, and a Status of Unassigned as the hosts are not yet assigned to your Satellite control plane or a Red Hat OpenShift cluster.
4. Assign your hosts to the [Satellite control plane](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-control-plane) or a [Red Hat OpenShift on IBM Cloud cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-satellite-clusters).



If your host is not attaching to your location, you can log in to the host to debug it. For more information, see [Logging in to a RHCOS host machine to debug](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-hosts-login-rhcos).

After you attach a host to your location, Satellite disables the ability to log in to the host as root with SSH for security purposes. You might see error messages if you try to SSH as root into a host that is attached successfully to a location. To restore the ability to SSH into the machine, you can [remove the host](https://cloud.ibm.com/docs/satellite?topic=satellite-host-remove) and reload the operating system.
Since there is only one pod, viewing the application logs will be straight forward.



1. Ensure that you're in the Topology view of the Developer perspective.
2. Navigate to your Pod by selecting your app.
3. Click on View Logs next to the name of the Pod under Pods to see streaming logs from your running application. If you're still generating traffic, you should see log messages for every request being made.

Zoom

![Pod Logs](https://cloud.ibm.com/docs-content/v1/content/f84e2238288b7f0355715a4c355609ce7ac48fb0/solution-tutorials/images/solution55-openshift-microservices/ocp45-pod-logs.png)

Pod Logs







 Red Hat OpenShift on IBM Cloud Terminal 

One of the great things about Kubernetes is the ability to quickly debug your application pods with SSH terminals. This is great for development, but generally is not recommended in production environments. Red Hat OpenShift makes it even easier by allowing you to launch a terminal directly in the dashboard.



1. Switch from the Logs tab to the Terminal tab.
2. Run the following Shell commands:





Examples of Shell commands to run

 Command Description 

 ls List the project files. 
 ps aux List the running processes. 
 cat /etc/redhat-release Show the underlying OS. 
 curl localhost:8080/info output from the node app.js process 







 Red Hat OpenShift on IBM Cloud Monitoring 

When deploying new apps, making configuration changes, or simply inspecting the state of your cluster, the project-scope dashboard gives a Developer clear insights.



1. Access the dashboard in the Developer perspective by clicking Observe on the left side menu.
2. You can also dive in a bit deeper by clicking the Events tab. Events are useful for identifying the timeline of events and finding potential error messages. When tracking the state of a new rollout, managing existing assets, or even something simple like exposing a route, the Events view is critical in identifying the timeline of activity.