vania-janet/multiturn-rag-retrieval-data huggingface dataset:
After reviewing the [overview](https://cloud.ibm.com/docs/openshift?topic=openshift-satellite-responsibilitiesoverview-by-resource-sat), see what tasks you and IBM share responsibility for each area and resource when you use Red Hat OpenShift on IBM Cloud.



 Incident and operations management 

You and IBM share responsibilities for the set up and maintenance of your Red Hat OpenShift on IBM Cloud cluster environment for your application workloads. You are responsible for incident and operations management of your application data.



Table 2. Responsibilities for incident and operations management

 Resource IBM responsibilities Your responsibilities 

 Worker nodes <br><br> * Deploy a fully managed, highly available dedicated master in a secured, IBM-owned infrastructure account for each cluster.<br> * Ensure that worker nodes successfully provision when the user account and permissions are correctly set up, and sufficient quota exists.<br> * Fulfill requests for more infrastructure, such as adding, reloading, updating, and removing worker nodes.<br> * Provide tools, such as the [cluster autoscaler](https://cloud.ibm.com/docs/containers?topic=containers-cluster-scaling-classic-vpc), to extend your cluster infrastructure.<br> * Integrate ordered infrastructure resources to work automatically with your cluster architecture and become available to your deployed apps and workloads.<br> * Fulfill automation requests to help recover worker nodes.<br><br><br> <br><br> * Use the provided API, CLI, or console tools to adjust [compute](https://cloud.ibm.com/docs/containers?topic=containers-add_workers) and [storage](https://cloud.ibm.com/docs/containers?topic=containers-storage-plan) capacity to meet the needs of your workload.<br> * Use the provided API, CLI, or console tools to request that worker nodes are rebooted, reloaded, or replaced, and troubleshoot issues such as when the worker nodes are in an [unhealthy state](https://cloud.ibm.com/docs/containers?topic=containers-debug_worker_nodes).<br><br><br>
"access_key_id": "1111111a1111111a11aa1a111111111a11aa1a111a11a1a1",
"secret_access_key": "222222b222222b22bb2b22222222b22bb2b222b22b2b2"
}



4. In the CLI, create a secret with the service credentials you created and saved.



1. [Log in to your account. If applicable, target the appropriate resource group. Set the context for your cluster.](https://cloud.ibm.com/docs/containers?topic=containers-access_cluster)
2. Create the secret.

oc create secret generic image-registry-private-configuration-user --from-literal=REGISTRY_STORAGE_S3_ACCESSKEY=<access_key_id> --from-literal=REGISTRY_STORAGE_S3_SECRETKEY=<secret_access_key> --namespace openshift-image-registry



5. Change the management state of the Red Hat OpenShift Register operator.

oc patch configs.imageregistry.operator.openshift.io cluster --type merge --patch '{"spec":{"managementState":"Managed"}}'
6. Edit the configuration storage attributes to store images in your Object Storage bucket.



1. Find and save your Satellite location's regional link endpoint. In the output, the endpoint is listed under the Address column.

ibmcloud sat endpoint ls --location <location_name> | grep satellite-cosRegional

Example output.

ID Name Destination Type Address
cavvku1p1h1gcfgk1kn1_uwokw satellite-cosRegional-cavvku1p1h1gcfgk1kn1 cloud TLS i11aa11a1a1a11a11-1a11a1aaa1a1a1a1a-c000.us-east.satellite.appdomian.cloud:11111
2.
If the schema namespace field is specified, the composite-recordName takes the value of "<namespace>.<recordName>", otherwise it takes the value of "<recordName>".



The following code shows an example of sending a message that conforms to a schema that is specified under the schema field by using curl:

curl -v -X POST 
-H "Authorization: Bearer $token" -H "Content-Type: application/json" -H "Accept: application/json" 
-d '{
"value": {
"type": "avro",
"schema": "{"namespace": "com.eventstreams.samples","type": "record","name": "recordValueName","fields": [{"name": "valueName", "type": "string"}]}",
"schema_name_strategy": "record",
"data": "{"valueName": "sampleValueName"}"
}
}' 
"$kafka_http_url/v2/topics/$topic_name/records?serializer=confluent"





 Migrating from existing endpoint to the v2 endpoint of the REST producer API 

Several improvements were made to the v2 endpoint for better usage and alignment with the API standards. To make the most of these improvements, make changes to your existing applications.

The following considerations can help you plan the migration:



1. Accessing the REST producer API:

You can access the v2 endpoint in the same way as the existing URL, which is by obtaining the value of kafka_http_url property for the service instance. The path to use is /v2/topics/<topic_name>/records.

Example URL: https://service-instance-adsf1234asdf1234asdf1234-0000.us-south.containers.appdomain.cloud/v2/topics/topic_name/records
2. Authentication:

The supported authentication mechanism is a bearer token.
"spark.hadoop.fs.cos.<cos-name>.endpoint":"https://s3.us-south.cloud-object-storage.appdomain.cloud",
"spark.hadoop.fs.cos.<cos-name>.access.key":"<access_key>",
"spark.hadoop.fs.cos.<cos-name>.secret.key":"<secret_key>",
"ae.spark.librarysets":"my_library_set"
}
}
}

Currently, only one library set can be referenced during Spark application submission under the "ae.spark.librarysets" attribute.

If the application is accepted, you will receive a response like the following:

{
"id": "87e63712-a823-4aa1-9f6e-7291d4e5a113",
"state": "accepted"
}
3. Track the status of the application by invoking the application status REST API. See [Get the status of an application](https://cloud.ibm.com/docs/AnalyticsEngine?topic=AnalyticsEngine-spark-app-rest-apispark-app-status).
If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.--output: Specify output format, only JSON is supported.<-- </section "id="section-command-options-logpush-job-update" "> --><-- <section "id="section-command-example-logpush-job-update" "> --> Examples Update range_events log push job for domain 31984fea73a15b45779fa0df4ef62f9b. ibmcloud cis logpush-job-update 31984fea73a15b45779fa0df4ef62f9b --destination cos://cis-test-bucket/logs?region=us&instance-id=f75e6d90-4212-4026-851c-d572071146cd --enable true --fields all --timestamps rfc3339 --dataset range_events --frequency high -i cis-demo --output JSON
<-- </section "id="section-command-example-logpush-job-update" "> --><-- </section "id="section-logpush-job-update" "> --><-- <section "id="section-logpush-jobs" "> --> ibmcloud cis logpush-jobs Get all log push jobs for a given domain (Enterprise plan only). ibmcloud cis logpush-jobs DNS_DOMAIN_ID -i, --instance INSTANCE] --output FORMAT] ! ! ! ! ! !
<-- <section "id="section-command-options-logpush-jobs" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.-i , --instance value: Instance name or ID.
resource "ibm_cos_bucket" "smart-us-south" {
bucket_name = "atest-bucket"
resource_instance_id = "cos-instance-id"
region_location = "us-south"
storage_class = "smart"
key_protect = ibm_kms_key.test.id
}
* Can you enable the TRACE to help DEBUG Schematics API while running workspace list command?

No, currently Schematics do not support this feature while running IBMCLOUD_TRACE=true ibmcloud schematics workspace list command.
* How do I resolve errors listing workspaces

When listing or retrieving workspaces the following error may be received. Error while retrieving Schematics Instance for the given account.

Error:
Bad status code [400] returned when getting workspace from Schematics: {"requestid":"fe5f0d6d-1d43-4643-a689-35d090463ce8","timestamp":"2022-01-25T20:23:54.727208017Z","messageid":"M1070","message":"Error while retrieving Schematics Instance for the given account.","statuscode":400}

You might have insufficient access for the workspaces in specified location to fetch the instance. Do check the permission that is provided for your account and the locations where your instance need to be created. For more information, see [Where is my information stored?](https://cloud.ibm.com/docs/schematics?topic=schematics-secure-datapi-location)
* How can I use (IBM) GitLab repositories?

Yes, You can access the private (IBM) GitLab repository by using Schematics with the privileges.



* If the private (IBM) GitLab repository git.cloud.ibm.com access token is not needed as the IAM token is used.
--authorizations='{"trusted_profile": {"id": "exampleString", "target_iam_id": "exampleString"}, "method": "exampleString", "api_key": "exampleString"}' --compliance-profile='{"id": "exampleString", "instance_id": "exampleString", "instance_location": "exampleString", "attachment_id": "exampleString", "profile_name": "exampleString"}' --input='{"name": "account_id", "value": "$configs].name\"account-stage\"].input.account_id"}]' --setting='{"name": "IBMCLOUD_TOOLCHAIN_ENDPOINT", "value": "https://api.us-south.devops.dev.cloud.ibm.com"}] ! ! '
Show more
<-- </section "id="section-project-config-create-examples" "> --><-- <section "id="section-project-config-create-cli-output" "> --> Example output Sample response for a project configuration draft. {
"id" : "293c3c36-a094-4115-a12b-de0a9ca39be5",
"definition" : {
"name" : "env-stage",
"description" : "Stage environment configuration, which includes services common to all the environment regions. There must be a blueprint configuring all the services common to the stage regions. It is a terraform_template type of configuration that points to a GitHub repo hosting the Terraform modules that can be deployed by a Schematics workspace.",
"labels" : "env:stage", "governance:test", "build:0" ],
* Northern Virginia
* Montreal, Canada



Europe:



* Frankfurt, Germany



Asia Pacific:



* Sydney







 Operations Support Locations 

IBM's MAS-SaaS support personnel are located across the globe in the following countries:



* United States
* Canada
* Brazil
* United Kingdom
* Ireland
* China
* India
* Australia







 Roles & Responsibilities Matrix (RACI) 

The RACI defines IBM and customer responsibilities in the delivery and management of the Maximo Application Suite as a Service (SaaS) environment.

MAS-SaaS RACI Spreadsheet (excel download):

[MAS-MS RACI Spreadsheet](https://www.ibm.com/support/pages/system/files/inline-files/MAS-MS-RACI-V2.xlsx)





 IBM SRE Task Lead Times 

The following table lists the expected lead time for the IBM SRE team (CDS) to complete certain types of tasks based on the initial case or service request response date. Lead times are in business days and are approximate.



Table 1. MAS-MS IBM SRE Lead Times

 IBM SRE Task Duration 

 VPN Setup 15 Days 
 SSO/LDAP setup 2 Days 
 Backflow (refresh) Database 3 Days 
 On Demand Backup and Restore 3 days 
 Cloud Object Storage (COS) Setup 2 days 
 Environment Migration (Database and Doclinks) 3 Days 
 Access to Logs 1 Day 
 Maximo Manage configdb request 2 Days 
 Application Server Restarts 1 Day 







 Incident Management and RCA Process 

The IBM SRE team has monitoring in place for all sites and infrastructure under our control. These are designed to allow the SRE team to pro-actively respond to service impacting or service threatening events or conditions. When a site is unavailable, or there are infrastructure issues leading to monitor alerts, an incident record is automatically generated within our Incident Management System.

At the same time, for production environments, a SRE Incident Response Team (IRT) provides 24/7 critical outage support.
* The solution architecture does not preclude any of the vCenter Server options such as Caveonix, Entrust, and VMware Aria Operations.
* Sandboxes can be provisioned by using VMware NSX-T™ overlay segments to provide network-isolated zones to mount cyber-recovery backups for inspection by your cyber toolsets.
* Cyber toolsets are customer-supplied tools that run as virtual machines (VMs) in the isolated recovery environment.
* Cyber admins are customer personnel who are authorized to access the isolated recovery environment.
* The air gap enables network connectivity between the production environment and the isolated recovery environment only when required.
* The solution architecture:



* Is independent of the location of the production environment. However, it is required network connectivity between the production environment and the cyber-recovery site.
* Is independent of the production backup solution.
* Requires that the production environment is vSphere based.
* Requires that cyber-recovery backup proxies that are registered with the cyber-recovery environment be installed on the ESXi hosts in the production environment.
* Requires that the cyber-recovery backup infrastructure has access with sufficient privileges to the production vCenter and ESXi hosts.



* This solution is suitable for clients who want to copy critical data away from the production environment. Also, that cyber-recovery backup systems and personnel are separate from production and disaster recovery processes.



[The definitive guide to ransomware: Readiness, response, and remediation](https://www.ibm.com/downloads/cas/EV6NAQR4) provides an overview of ransomware history, its current prevalence, and resources to help fortify organizations and technical-level guidance on techniques to protect networks before an attack can happen. Also, a recovery guidance if an attacker makes it through defenses.



 Terms and definitions 

This documentation uses the following terms and definitions:



Table 1. Terms and definitions

 Term Definition 

 vCenter Server instance A VMware vSphere environment that is hosted on a minimum of three IBM Cloud bare metal servers and includes VMware NSX to provide a virtual network overlay. An instance includes a vCenter appliance and Microsoft® Windows® AD/DNS.
Schema Registry It is recommended good practice that a customer stores their schema in the same repository as their application source code. This way the schema can be restored into a new cluster if a disaster occurs. 







 App orchestration 



Table 5. Responsibilities for app orchestration

 Task IBM Responsibilities Your Responsibilities 

 Integrate with select third-party partnership technologies Event Streams provides integrations with select third-party partnership technologies, such as IBM Cloud Activity Tracker with LogDNA. 
 Provide service binding to other IBM services Event Streams provides the capability for service binding to other IBM services. 
 Manage, integrate, and monitor Customer is responsible for using the provided tools and features to manage the lifecycle of customer-owned applications, for integrating with other services, and monitoring the health of the application (for example, Availability Monitoring). 







 Mirroring 



Table 6. Responsibilities for mirroring

 Task IBM Responsibilities Your Responsibilities 

 Clusters Checking clusters are viable mirroring pairs Provisioning both clusters. 
 Setup Setting up mirroring Setting up service to service binding. 
 Enablement and monitoring Monitoring health and SLA of mirroring link . Requesting enablement by support ticket. 
 Metrics and applications Providing metrics to enable customer to understand the current recovery point objective (RPO). Enabling applications to switch clusters. 
 IAM Setting up required access policies. 
 Failover Deciding when to fail over and failover applications. 
 Failback Reconfiguring mirroring Developing and executing failback plan. Coordinating with IBM to reconfigure mirroring. 







 Support of client-side libraries 

IBM does not own Kafka client-side libraries and cannot commit to provide fixes in case issues are found in them. Client-side libraries include the official Apache Kafka clients (Consumer, Producer, Connect, and Streams), as well as third-party clients, libraries, tools, and connectors.

As an active member of the Kafka community, IBM works, on a best effort basis, with communities that own clients-side libraries to help develop and release fixes for critical issues.
Consolidated and workload cluster 

Cyber Recovery instances are deployed with a consolidated cluster for VMware vSphere® 7, in which all the VMware® management components and user workloads run.

You can also order an extra workload cluster.



 Cluster name 



* For the consolidated cluster, the cluster name is preset to instance name-consolidated.
* For the workload cluster, the cluster name is preset to instance name-workload.



You can also specify a new cluster name that meets the following requirements:



* Only lowercase alphabetic, numeric, and dash (-) characters are allowed.
* The cluster name must start with a lowercase alphabetic character.
* The cluster name must end with a lowercase alphabetic or numeric character.
* The maximum length of the cluster name is 30 characters.
* The cluster name must be unique within the vCenter Server instance.







 Data center location 

Select the IBM Cloud® data center settings. For more information, see [Region and data center locations for resource deployment](https://cloud.ibm.com/docs/overview?topic=overview-locations).



 Geography 

Select the region where your cluster or instance is hosted.





 Data center 

Select the IBM Cloud data center where the cluster is hosted.





 Pod 

Select the IBM Cloud data center pod where you want to deploy your resources. Keep the default pod selection unless you have specific reasons to choose a different pod.







 CPU model 

Select either Cascade Lake or SAP-certified Cascade Lake.



 Cascade Lake 

For Cascade Lake servers, you can choose the following CPU models and a supported RAM size, which depends on the NSX networking solution.

NSX-T instances



Table 1. Options for Cascade Lake bare metal servers - NSX-T instances

 CPU model Cores GHz RAM 

 Dual Intel Xeon Silver 4210 processor 20 2.2 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB 
 Dual Intel Xeon Gold 5218 processor 32 2.3 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB
If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.--output: Specify output format, only JSON is supported.<-- </section "id="section-show-waf-group-options" "> --><-- <section "id="section-show-waf-group-examples" "> --> Examples Get details of WAF group de677e5818985db1285d0e80225f06e5 in WAF package a25a9a7e9c00afc1fb2e0245519d725b. ibmcloud cis waf-group 31984fea73a15b45779fa0df4ef62f9b a25a9a7e9c00afc1fb2e0245519d725b de677e5818985db1285d0e80225f06e5 -i "cis-demo"
<-- </section "id="section-show-waf-group-examples" "> --><-- </section "id="section-show-waf-group" "> --><-- <section "id="section-update-waf-group" "> --> ibmcloud cis waf-group-mode-set Set mode of a WAF group. ibmcloud cis waf-group-mode-set DNS_DOMAIN_ID WAF_PACKAGE_ID WAF_GROUP_ID WAF_GROUP_MODE -i, --instance INSTANCE] --output FORMAT] ! ! ! ! ! !
<-- <section "id="section-update-waf-group-options" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.WAF_PACKAGE_ID: The ID of WAF package. Required.WAF_GROUP_ID: The ID of WAF group. Required.WAF_GROUP_MODE: The mode of WAF group. Valid values are: on, off.
config rule 

See [configuration rule](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx3084914).





 configuration rule (config rule) 

A JSON document that defines the configuration of resources and validates the compliance based on security requirements when a resource is created or modified.





 confusion matrix 

A table that provides a detailed numeric breakdown of annotated document sets. The table is used to compare the annotations that were added by a machine learning model to the annotations in the ground truth. The table reports the number of false positives, false negatives, true positives, and true negatives.





 connection 

In data communication, an association established between entities for conveying information.





 consensus 

The process of participants in a blockchain agreeing to a transaction and validating it through the peer network. Consensus ensures that shared ledgers are exact copies, and lowers the risk of fraudulent transactions since tampering would have to occur across many places at the exact same time.





 consumer 

A member in a blockchain network that uses the network to invoke transactions against the distributed ledger.





 container 

A system construct that allows users to simultaneously run separate logical operating system instances. Containers use layers of file systems to minimize image sizes and promote reuse. See also [image](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx2024928), [registry](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx2064940), [layer](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx2028320).





 context 

Environmental or conditional information that can be used to define when rules that restrict access to resources should be applied. A context can be a set of properties or attributes like client IP addresses, office hours, time of day, or multi-factor authentication.





 context-based restriction 

An access management method that defines and enforces access for resources based on the network location of the access request.





 control
See also [disaster recovery](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx2113280).





 red-black deployment 

A deployment technique that drives continuous delivery by enabling synchronized test, development, and deployment. Initially, development is done on an inactive environment (black) while the active environment continues to take traffic (red). Once deployment starts, both environments go live (red-red) until routing is disabled on the formerly active, previous version environment, then subsequently removed (black) while the new environment serves as the only active environment. See also [blue-green deployment](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx7807335).





 reference architecture 

An opinionated pattern of technologies that work together that includes a summary, an architecture diagram, and a list of modules.





 region 

A defined geographic territory. A region could be a specific postal code area, a town, a city, a state, a group of states, or even a group of countries. Each region can itself be a set of other regions or a set of postal codes that form the region.





 registry 

A storage and distribution service that contains public or private images that are used to create containers. See also [image](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx2024928), [container](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx2010901).





 relation 

Typically a verb that reflects how entities are related to one another. For example, "lives in" is a relation between a person and a town. A relation links two different entities in the same sentence.





 relation type 

A binary, unidirectional relationship between two entities. For example, Mary employedBy IBM is a valid relationship; IBM employedBy Mary is not.





 Representational State Transfer (REST) 

A software architectural style that guides the design and development of the architecture for the web. REST defines a set of constraints for the architecture of Internet-scale distributed hypermedia systems, such as the web.





 resource
See [Real-time analytics on IoT data](https://www.ibm.com/blogs/journey-to-ai/2022/09/real-time-analytics-on-iot-data/).







 Migration assistance 

If your organization needs help migrating from IBM Watson IoT Platform to IBM Maximo Application Suite, there are for-pay migration assistance options from IBM teams that are available to you. IBM Sustainability Expert Labs provide deep technical expertise and a proven approach to migrating solutions to IBM hybrid cloud technologies. For your Watson IoT Platform journey, we offer both Advisory Services to assess, recommend, and plan your Watson IoT Platform migration approach and Migration Services to assist with application remediation and migration. Contact your local IBM account manager for more information and contacts to get started.





 Customer support 

If you have questions, or need help, contact [IBM Cloud Customer Support](https://www.ibm.com/cloud/support) for additional information and assistance.