vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Understanding high availability and disaster recovery for Code Engine 

All IBM Cloud general availability (GA) offerings have a Service Level Agreement of 99.99% availability. IBM Cloud® Code Engine is a GA service that is offered in several locations. Each location has three different data centers for redundancy.

For more information about high availability and disaster recovery standards in IBM Cloud, see [How do I ensure zero downtime?](https://cloud.ibm.com/docs/overview?topic=overview-zero-downtimezero-downtime). You can also find information about [Service Level Agreements](https://cloud.ibm.com/docs/overview?topic=overview-slas).



 Code Engine regions 

The following table lists the high-availability (HA) status for the regions (locations) where the Code Engine service is available.



Table 1. Highly available Code Engine regions

 Geography Region High availability 

 Asia Pacific Australia (au-syd) MZR 
 Asia Pacific Osaka (jp-osa) MZR 
 Asia Pacific Tokyo (jp-tok) MZR 
 Europe Frankfurt (eu-de) MZR 
 Europe London (eu-gb) MZR 
 North America Dallas (us-south) MZR 
 North America Toronto (ca-tor) MZR 
 North America Washington (us-east) MZR 
 South America Brazil Sao Paulo (br-sao) MZR 



A geography is a geographic area or larger political body that contains one or more regions. A region contains [multiple availability zones](https://www.ibm.com/cloud/data-centers/) to meet local access, low latency, and security requirements for the region. Each [multizone region (MZR)](https://cloud.ibm.com/docs/overview?topic=overview-locationstable-mzr) is composed of 3 or more zones that are independent from each other to ensure that single failure events affect only a single zone.





 Availability of Code Engine instances 

When you provision a Code Engine project, you select the location (MZR) where the instance is created.
Your responsibilities with using Continuous Delivery 

Learn about the management responsibilities and terms and conditions that you have when you use IBM Cloud® Continuous Delivery. For a high-level view of the service types in IBM Cloud® and the breakdown of responsibilities between the customer and IBM for each type, see [Shared responsibilities for IBM Cloud offerings](https://cloud.ibm.com/docs/overview?topic=overview-shared-responsibilities).

You can integrate third-party tools (such as Public GitHub), or tools that you manage (such as a private Tekton worker that is running on your infrastructure), into Continuous Delivery toolchains. However, IBM’s management responsibilities do not extend to any tools that are managed by you or by third-parties.

Review the following sections for the specific responsibilities for you and for IBM when you use Continuous Delivery. For the overall terms of use, see [IBM Cloud Terms and Notices](https://cloud.ibm.com/docs/overview/terms-of-use?topic=overview-terms).



 Incident and operations management 

Incident and operations management includes tasks such as monitoring, event management, high availability, problem determination, recovery, and full state backup and recovery.



Table 1. Responsibilities for incident and operations

 Task IBM responsibilities Your responsibilities 

 Maintain high availability and respond to incidents. Operate the Continuous Delivery service in accordance with the IBM Cloud Public [Service Level Agreements (SLAs)](https://cloud.ibm.com/docs/overview/terms-of-use?topic=overview-slas). Plan the deployment of your apps and data to meet your availability objectives. For more information about managing availability, see [How do I ensure zero downtime?](https://cloud.ibm.com/docs/overview/terms-of-use?topic=overview-zero-downtime) 







 Change management 

Change management includes tasks such as deployment, configuration, upgrades, patching, configuration changes, and deletion.



Table 2. Responsibilities for change management

 Task IBM responsibilities Your responsibilities 

 Update Delivery Pipeline images. Provide updated Delivery Pipeline job container images.
IBM Cloud console 99.999% [High availability for the platform](https://cloud.ibm.com/docs/overview?topic=overview-zero-downtimeplatform-ha) 
 IBM Cloud CLI 99.999% [Understanding high availability and disaster recovery for the IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-ha-dr) 
 IBM Cloud network 99.9999% [High availability for the network](https://cloud.ibm.com/docs/overview?topic=overview-zero-downtimeha-network) 
 IBM Cloud catalogs 99.999% [High availability for the platform](https://cloud.ibm.com/docs/overview?topic=overview-zero-downtimeplatform-ha) 
 Identity and Access Management (IAM) 99.999% [High availability for the platform](https://cloud.ibm.com/docs/overview?topic=overview-zero-downtimeplatform-ha) 







 Compute services 

The following table describes the service level objectives (SLOs) for the vital IBM Cloud compute services in a high availability configuration.



Table 2. Service level objectives (SLOs) for the IBM Cloud compute services

 Compute service Availability target Performance target High availability guidance 

 IBM Cloud VPC 99.999% Network Performance > 90% in 99.9% of the time <br>NVMe Performance > 90% in 99.9% of the time [Understanding high availability and disaster recovery](https://cloud.ibm.com/docs/vpc?topic=vpc-ha-dr-vpc) 
 Power Systems Virtual Server 99.999% Network Performance > 90% in 99.9% of the time [Understanding high availability and disaster recovery](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-ha-dr) 







 Networking services 

The following table describes the service level objectives (SLOs) for the vital IBM Cloud networking services in a high availability configuration.



Table 3. Service level objectives (SLOs) for the IBM Cloud networking services

 Networking service Availability target High availability guidance
Review the following image to find a general approach of how you can make your resource highly available and add resiliency to account for a site or region failure. The level of availability that is right for you depends on several factors, such as the high availability features that are available for your resource, your business requirements, the [Service Level Agreements](https://cloud.ibm.com/docs/overview?topic=overview-slas) that you have with your clients, and the money that you need to expense. In your Terraform configuration file, you have the option to configure multiple provider blocks for the different regions, zones, or locations where you want to provision your resources. For more information, see [Creating multiple provider configurations](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-provider-referencemultiple-providers).

Supported high availability features depend on the type of IBM Cloud resource that you choose to provision with IBM Cloud Schematics. Some high availability scenarios that are shown in this image might not be available for your resource. Make sure to review the resource documentation to find supported high availability features.

Zoom

![High availability for IBM Cloud resources](https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/schematics-ha-roadmap.png)

Figure 1. High availability for IBM Cloud resources



1. Single zone resources: By default, your IBM Cloud resource is deployed into one zone. This setup does not protect your workloads or data from a zonal or regional failure.
2.
* a field - http.host
* a comparison operator - eq
* a value - "www.example.com"



Not all conditions have the same structure. Additional examples using different structures are discussed in the next section.



 Comparison operators 

The following comparison operators are available for use in expressions:



Table 4. Comparison operators for expressions

 English C-like Description 

 eq == Equal 
 ne != Not equal 
 lt < Less than 
 le <= Less than or equal to 
 gt Great than 
 ge = Greater than or equal to 
 contains Exactly contains 
 matches [Re2](https://github.com/google/re2/wiki/Syntax) inspired regular expression 
 in Value appears in a set of values. Supports ranges using the ".." notation. 
 not ! See Boolean comparison 
 bitwise_and & Compare bit field value 



Currently the CIS UI Visual Expression Builder only supports English operators.

An expression might contain a mix of English and C-like operators. For example, ip.src eq 93.184.216.34 is equivalent to ip.src == 93.184.216.34.

Certain comparison operators apply to specific fields based on type. The following matrix provides examples of which operators are available for various field types:



Table 5. Comparison operators for fields

 English C-like String IP Address Number 

 eq == http.request.uri.path eq "/articles/2008/" ip.src eq 93.184.216.0 cf.threat_score eq 10 
 ne != http.request.uri.path ne "/articles/2010/" ip.src ne 93.184.216.0 cf.threat_score ne 60 
 lt < http.request.uri.path lt "/articles/2009/" cf.threat_score lt 10 
 le <= http.request.uri.path le "/articles/2008/" cf.threat_score le 20 
 gt http.request.uri.path gt "/articles/2006/" cf.threat_score gt 25 
 ge = Greater than or equal to cf.threat_score ge 60
: IBM Cloud Pak® for Data 4.0.2 can be installed on Red Hat® OpenShift® on IBM Cloud® 4.8.

New scoring for NLU enrichments
: Relevance and confidence scores are displayed for NLU enrichments that are returned by search. For example, when you open the JSON view of the document preview from a query result, you can see confidence scores for Entities mentions and relevance scores for Keyword mentions.

Improved Web crawl
: The Web crawl data source supports more customization options, including the ability to ignore a site's robots.txt file. For more information, see [Web crawl](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-connector-web-cp4d).

New upgrade support
: The 4.0.2 release supports in-place upgrade from IBM Watson® Discovery Cartridge for IBM Cloud Pak® for Data 4.0.0. For more information, see [Upgrading Watson Discovery to a newer 4.0 refresh](https://www.ibm.com/docs/SSQNUZ_4.0/svc-discovery/discovery-upgrade-v4.html)





 IBM Cloud Private End Of Support 

Effective 30 September 2021, IBM withdrew support for the following programs:



* IBM Watson Assistant Discovery Extension for IBM Cloud Private 2.1.0–2.1.4
* IBM Watson Discovery for ICP for Data 2.1.0–2.1.4
* IBM Watson Discovery for ICP for Data Add-on 2.1.0–2.1.4
If the 24-hour Service Level Agreement (SLA) is not acceptable, you can [create an IBM Support case](https://cloud.ibm.com/unifiedsupport/cases/form) and request that it be routed to the SNS team.





 Ordering Direct Link Exchange on Classic when there is no VRF present 

For the accounts with no Virtual Routing and Forwarding (VRF) present, the Select VRF field is not displayed in the order form. In this situation, an IBM Support case is generated after you place your order. The case number and details are shown in the IBM Cloud console after you place the order.





 Locations 

This table shows which IBM Cloud data centers offer Direct Link Exchange connectivity:



Table 1: Data centers that offer Direct Link Exchange connectivity

 Exchange Provider IBM Data Center Code 

 AT Tokyo Tokyo 2 
 Ascenty Sao Paulo 1 
 Cologix Montreal 2, Toronto 2 
 Cyrus One Dallas 13 
 DE-CIX Frankfurt 3 
 Equinix Americas: Chicago 1, Dallas 3, New York City 2*, New York City 3*, Sao Paulo 2, San Jose 2, Toronto 2, Toronto 3, Washington DC <br>APAC: Hong Kong 1, Osaka 1, Singapore 2, Sydney 2, Tokyo 1, Tokyo 3 <br>EU: Amsterdam 2, Frankfurt 3, London 1, London 3, Paris 2 
 KINX Seoul 2 
 NextDC Melbourne 2, Sydney 3 





* NYC02 and NYC03 connect to the IBM Cloud backbone through NYC1. The primary reason for these PoPs is to extend connectivity to different site providers from our NYC01 site. When planning your diversity strategy, keep in mind that traffic for NYC02 and NYC03 have a single, shared path to the IBM network.
* The platform access role enables actions to be performed on platform resources, such as creating an instance, connecting instances to apps, and assigning user access.



4. Click Save.



The following table lists the string comparison operators that you can use to build access policies with /v2/policies syntax. For more information about each version, see [Comparing /v1/policies and /v2/policies syntax](https://cloud.ibm.com/docs/account?topic=account-known-issuescompare-syntax).



Table 3. The string comparison operators available for conditions in access policies.

 Operator Description 

 stringEquals Case-sensitive string comparison. Boolean or number values are converted into a string before comparison. 
 stringMatch Case-sensitive string match is performed between the pattern and the target string by using either an asterisk (), question mark (?), or both. An asterisk () represents any sequence of zero or more characters in the string, and a question mark (?) represents any single character. You can also express an asterisk * and question mark ? as a literal value by enclosing each within two sets of curly brackets {{}}. 
 stringExists String must be present but can have any none zero value. 
 stringEqualsAnyOf Case-sensitive exact string matching any of the strings in an array of strings. 
 stringMatchAnyOf Case-sensitive string matching any of the strings in an array of strings. The values can include a multi-character wildcard (), which matches any sequence of zero or more characters, a single-character wildcard (?), matching any single character, or both. You can also express an asterisk * and question mark ? as a literal value by enclosing each within two sets of curly brackets {{}}. 







 Step 7: Set the license requirements 

If users are required to accept any license agreements beyond the IBM Cloud Services Agreement, provide the URL to each agreement. Or, if users can bring their own licenses, you can provide that URL as well.



1. Click Add license agreements > Add.
2. Enter the name and URL, and click Update.
3.
3.2 Logging 



Section 3.2 Logging benchmark results

 Section Recommendation Scored? Level Result Responsibility 

 3.2.1 Ensure that a minimal audit policy is created. Scored 1 [Fail](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-125cis-benchmark-remediations-125) Shared 
 3.2.2 Ensure that the audit policy covers key security concerns. Not Scored 2 [Fail](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-125cis-benchmark-remediations-125) Shared 









 4 Worker node security configuration 

Review the Worker Node Security Configuration results of the version 1.5 CIS Kubernetes benchmark.



 4.1 Worker node configuration files 



Section 4.1 Worker Node Configuration benchmark results

 Section Recommendation Scored? Level Result Responsibility 

 4.1.1 Ensure that the kubelet service file permissions are set to 644 or more restrictive. Scored 1 Pass IBM 
 4.1.2 Ensure that the kubelet service file ownership is set to root:root. Scored 1 Pass IBM 
 4.1.3 Ensure that the proxy kubeconfig file permissions are set to 644 or more restrictive. Scored 1 Pass IBM 
 4.1.4 Ensure that the proxy kubeconfig file ownership is set to root:root. Scored 1 Pass IBM 
 4.1.5 Ensure that the kubelet.conf file permissions are set to 644 or more restrictive. Scored 1 Pass IBM 
 4.1.6 Ensure that the kubelet.conf file ownership is set to root:root. Scored 1 Pass IBM 
 4.1.7 Ensure that the certificate authorities file permissions are set to 644 or more restrictive. Scored 1 Pass IBM 
 4.1.8 Ensure that the client certificate authorities file ownership is set to root:root. Scored 1 Pass IBM 
 4.1.9 Ensure that the kubelet configuration file has permissions set to 644 or more restrictive. Scored 1 Pass IBM
For more information about service availability, see [Service Level Agreements (SLAs)](https://cloud.ibm.com/docs/overview?topic=overview-slas).

The following table lists the high-availability (HA) status for the regions (locations) where the IBM Cloud Activity Tracker service is available:



Table 1. List of locations where the service is available

 Geography Region EU-Supported HA Status 

 North America Dallas (us-south) N/A MZR 
 North America Washington (us-east) N/A MZR 
 Europe Frankfurt (eu-de) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/bcd8b79ca2ed73bfcaefb20051f12cb6400286ab/atracker/images/checkmark-icon.svg) MZR 
 Europe London (eu-gb) N/A MZR 
 Asia Pacific Sydney (au-syd) N/A MZR 



Where



* A geography is a geographic area or larger political body that contains one or more regions.
* A region is 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.

A region contains [multiple availability zones](https://www.ibm.com/cloud/data-centers/) to meet local access, low latency, and security requirements for the region.
* N/A means feature that is not applicable to that geography.
* MZR means multi-zone region. [Learn more](https://cloud.ibm.com/docs/overview?topic=overview-locationsmzr-table).







 Data availability 

The data that is managed by Activity Tracker Event Routing in a region is kept in the data centers near that region.

A multizone region (MZR) consist of 3 or more availability zones that are independent from each other to ensure that single failure events affect only a single zone.

By default, Activity Tracker Event Routing is deployed across 3 zones. Each zone is setup with active/active/active:
3 Control plane configuration 



 3.1 Authentication and authorization 



Section 3.1 Authentication and Authorization benchmark results

 Section Recommendation Scored/Not Scored Level Result Responsibility 

 3.1.1 Client certificate authentication should not be used for users. Not Scored 2 Pass Shared 







 3.2 Logging 



Section 3.2 Logging benchmark results

 Section Recommendation Scored/Not Scored Level Result Responsibility 

 3.2.1 Ensure that a minimal audit policy is created. Scored 1 [Fail](https://cloud.ibm.com/docs/openshift?topic=openshift-cis-benchmark-410ibm-remediations-and-explanations-410) Shared 
 3.2.2 Ensure that the audit policy covers key security concerns. Not Scored 2 [Fail](https://cloud.ibm.com/docs/openshift?topic=openshift-cis-benchmark-410ibm-remediations-and-explanations-410) Shared 









 4 Worker node security configuration 

Review the Worker Node Security Configuration results of the version 1.5 CIS Kubernetes benchmark.



 4.1 Worker node configuration files 



Section 4.1 Worker Node Configuration benchmark results

 Section Recommendation Scored/Not Scored Level Result Responsibility 

 4.1.1 Ensure that the kubelet service file permissions are set to 644 or more restrictive. Scored 1 Pass IBM 
 4.1.2 Ensure that the kubelet service file ownership is set to root:root. Scored 1 Pass IBM 
 4.1.3 Ensure that the proxy kubeconfig file permissions are set to 644 or more restrictive. Scored 1 Pass IBM 
 4.1.4 Ensure that the proxy kubeconfig file ownership is set to root:root. Scored 1 Pass IBM 
 4.1.5 Ensure that the kubelet.conf file permissions are set to 644 or more restrictive. Scored 1 Pass IBM 
 4.1.6 Ensure that the kubelet.conf file ownership is set to root:root. Scored 1 Pass IBM 
 4.1.7 Ensure that the certificate authorities file permissions are set to 644 or more restrictive. Scored 1 Pass IBM
3.2 Logging 



Section 3.2 Logging benchmark results

 Section Recommendation Scored/Not Scored Level Result Responsibility 

 3.2.1 Ensure that a minimal audit policy is created. Scored 1 [Fail](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-120cis-benchmark-remediations-120) Shared 
 3.2.2 Ensure that the audit policy covers key security concerns. Not Scored 2 [Fail](https://cloud.ibm.com/docs/containers?topic=containers-cis-benchmark-120cis-benchmark-remediations-120) Shared 









 4 Worker node security configuration 

Review the Worker Node Security Configuration results of the version 1.5 CIS Kubernetes benchmark.



 4.1 Worker node configuration files 



Section 4.1 Worker Node Configuration benchmark results

 Section Recommendation Scored/Not Scored Level Result Responsibility 

 4.1.1 Ensure that the kubelet service file permissions are set to 644 or more restrictive. Scored 1 Pass IBM 
 4.1.2 Ensure that the kubelet service file ownership is set to root:root. Scored 1 Pass IBM 
 4.1.3 Ensure that the proxy kubeconfig file permissions are set to 644 or more restrictive. Scored 1 Pass IBM 
 4.1.4 Ensure that the proxy kubeconfig file ownership is set to root:root. Scored 1 Pass IBM 
 4.1.5 Ensure that the kubelet.conf file permissions are set to 644 or more restrictive. Scored 1 Pass IBM 
 4.1.6 Ensure that the kubelet.conf file ownership is set to root:root. Scored 1 Pass IBM 
 4.1.7 Ensure that the certificate authorities file permissions are set to 644 or more restrictive. Scored 1 Pass IBM 
 4.1.8 Ensure that the client certificate authorities file ownership is set to root:root. Scored 1 Pass IBM 
 4.1.9 Ensure that the kubelet configuration file has permissions set to 644 or more restrictive. Scored 1 Pass IBM
* RTP network warnings, such as high packet loss or high average jitter, if RTCP is enabled.



"warnings_and_errors": [
{
"message": "CWSMR0032W: A Watson Speech to Text final utterance has a confidence score of 0.1, which does not meet the confidence score threshold of 0.2. The utterance will be ignored.",
"id": "CWSMR0032W"
},
{
"message": "CWSMR0031W: The synthesis stream from the Watson Text To Speech service can't keep up with the playback rate to the caller, so audio might skip. transaction ID=a1b2c3d4e5",
"id": "CWSMR0031W"
}
]

The object for each warning contains the following keys:



Keys for the warnings_and_errors object

 Key Type Description 

 message string The text of the warning message that was logged. 
 id string The unique message identifier. 







 RTP network summary details 

When RTCP is enabled, each realtime_transport_network_summary object provides statistics for the inbound stream in the inbound_stream object and statistics for the outbound stream in the outbound_stream object.

"realtime_transport_network_summary": {
"inbound_stream": {
"maximum_jitter": 5,
"average_jitter": 1,
"packets_lost": 0,
"packets_transmitted": 1000,
"canonical_name": "user@example.com",
"tool_name": "User SIP Phone"
},
"outbound_stream": {
"maximum_jitter": 5,
"average_jitter": 1,
"packets_lost": 0,
"packets_transmitted": 2000,
"canonical_name": "voice.gateway@127.0.0.1",
"tool_name": "IBM Voice Gateway/1.0.0.5"
}
}

Show more