vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Understanding high availability for IBM Cloudant 

High availability (HA) is a core discipline in an IT infrastructure to keep your apps up and running, even after a partial or full site failure. The main purpose of high availability is to eliminate potential points of failures in an IT infrastructure.

To provide HA within a data center, all data is stored in triplicate across three separate physical servers in a cluster. You can provision accounts in multiple data centers, then use continuous data replication to provide HA across data centers. IBM® Cloudant® for IBM Cloud® data isn't automatically backed up, but supported tools are provided to handle backups. Review the [Disaster recovery and backup guide](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-disaster-recovery-and-backup) to explore all HA and backup considerations to meet your application requirements.



 Responsibilities 

To find out more about responsibility ownership for using IBM Cloud® products between IBM and the customer, see [Shared responsibilities for IBM Cloud products](https://cloud.ibm.com/docs/overview?topic=overview-shared-responsibilities).

For more information about responsibilities when you use IBM Cloudant, see [Shared responsibilities for IBM Cloudant](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-cloudant-responsibilities).





 What level of availability do I need? 

You can achieve high availability on different levels in your IT infrastructure and within different components of your cluster. The level of availability that works for you depends on several factors, such as your business requirements, the service level agreements (SLAs) that you have with your customers, and the resources that you want to expend.





 What level of availability does IBM Cloud offer? 

The level of availability that you set up for your cluster impacts your coverage on the IBM Cloud high availability service level agreement terms.

Service level objectives (SLOs) describe the design points that the IBM Cloud services are engineered to meet. IBM Cloudant is designed to achieve the following availability target.



Table 1. SLA for IBM Cloudant

 Availability target Target Value 

 Availability % 99.99%
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 goal of IRT is to ensure our customer's applications are running when they should, and to provide effective and timely customer communication during availability incidents or Severity 1 cases during off hours. IRT is sometimes referred to as the "on call" team.

Please note IRT is not considered standard support. It is for emergency and Sev1 cases only. Please see our Support & Operations section for standard support details and hours of operation.

How is the IBM SRE Incident Response Team (IRT) organized?

The IRT is organized into a 2-person rotating schedule on 8-hour cycles over 7 days. This means that there are two IRT members for each 8 hour period: a Client Communicator and a First Responder. IBM SRE uses a region based “follow the sun” support model. The IRT schedule is maintained and updated by IBM on a regular basis.

Client Communicator



* The Client Communicator (CC) is responsible for ensuring that any customer affected by a Severity 1 incident or alert is receiving prompt and frequent communication regarding the status of their incident. This resource does not necessarily have technical skills or access to investigate / act upon systems that are failing. The CC may also be expected to triage requests that do not fall within the definition of Severity 1 and communicate with the customer regarding these issues.



First Responder



* The First Responder (FR) is a technical role that requires access to systems that may be in a failed or failing state, as well as the skills required to understand what can be done to recover affected environment(s). It may not be possible for the FR to correct all problems and he/she should be equipped to escalate issues to specific individuals for resolution if necessary.
CP-2 (8) - Identify Critical Assets 



  Control requirements 

CP-2 (8) - 0
:   The organization identifies critical information system assets supporting essential missions and business functions.





  Additional IBM Cloud for Financial Services specifications 



*  The Business Impact Analysis must undergo annual review and approval. Changes to the Business Impact Analysis should be communicated to the customer, reviewed, and approved within 90 days of significant changes to the system.







  NIST supplemental guidance 

Organizations may choose to carry out the contingency planning activities in this control enhancement as part of organizational business continuity planning including, for example, as part of business impact analyses. Organizations identify critical information system assets so that additional safeguards and countermeasures can be employed (above and beyond those safeguards and countermeasures routinely implemented) to help ensure that organizational missions/business functions can continue to be conducted during contingency operations. In addition, the identification of critical information assets facilitates the prioritization of organizational resources. Critical information system assets include technical and operational aspects. Technical aspects include, for example, information technology services, information system components, information technology products, and mechanisms. Operational aspects include, for example, procedures (manually executed operations) and personnel (individuals operating technical safeguards and/or executing manual procedures). Organizational program protection plans can provide assistance in identifying critical assets.
Understanding high availability and disaster recovery 

Use the built-in Red Hat OpenShift, Kubernetes, and IBM Cloud® features to make your Red Hat OpenShift cluster more highly available and to protect your app from downtime when a component in your cluster fails.



 About high availability 

High availability (HA) is a core discipline in an IT infrastructure to keep your apps up and running, even after a partial or full site failure. The main purpose of high availability is to eliminate potential points of failures in an IT infrastructure. For example, you can prepare for the failure of one system by adding redundancy and setting up failover mechanisms.

What level of availability is best?
: You can achieve high availability on different levels in your IT infrastructure and within different components of your cluster. The level of availability that is correct for you depends on several factors, such as your business requirements, the Service Level Agreements that you have with your customers, and the resources that you want to expend.

What level of availability does IBM Cloud offer?
: See [How IBM Cloud ensures high availability and disaster recovery](https://cloud.ibm.com/docs/overview?topic=overview-zero-downtime).

The level of availability that you set up for your cluster impacts your coverage under the [IBM Cloud HA service level agreement terms](https://cloud.ibm.com/docs/overview?topic=overview-slas). For example, to receive full HA coverage under the SLA terms, you must set up a multizone cluster with a total of at least 6 worker nodes, two worker nodes per zone that are evenly spread across three zones.

What are the other cluster components that support highly available architecture?
: See [Overview of potential points of failure in Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/docs/openshift?topic=openshift-hafault_domains).

Where is the service located?
: See [Locations](https://cloud.ibm.com/docs/openshift?topic=openshift-regions-and-zonesregions-and-zones).

What am I responsible to configure disaster recovery options for?
Understanding high availability and disaster recovery 

Use the built-in Kubernetes and IBM Cloud® Kubernetes Service features to make your cluster more highly available and to protect your app from downtime when a component in your cluster fails.



 About high availability 

High availability (HA) is a core discipline in an IT infrastructure to keep your apps up and running, even after a partial or full site failure. The main purpose of high availability is to eliminate potential points of failures in an IT infrastructure. For example, you can prepare for the failure of one system by adding redundancy and setting up failover mechanisms.

What level of availability is best?
: You can achieve high availability on different levels in your IT infrastructure and within different components of your cluster. The level of availability that is correct for you depends on several factors, such as your business requirements, the Service Level Agreements that you have with your customers, and the resources that you want to expend.

What level of availability does IBM Cloud offer?
: See [How IBM Cloud ensures high availability and disaster recovery](https://cloud.ibm.com/docs/overview?topic=overview-zero-downtime).

The level of availability that you set up for your cluster impacts your coverage under the [IBM Cloud HA service level agreement terms](https://cloud.ibm.com/docs/overview?topic=overview-slas). For example, to receive full HA coverage under the SLA terms, you must set up a multizone cluster with a total of at least 6 worker nodes, two worker nodes per zone that are evenly spread across three zones.

What are the other cluster components that support highly available architecture?
: See [Overview of potential points of failure in IBM Cloud Kubernetes Service](https://cloud.ibm.com/docs/containers?topic=containers-hafault_domains).

Where is the service located?
: See [Locations](https://cloud.ibm.com/docs/containers?topic=containers-regions-and-zonesregions-and-zones).

What am I responsible to configure disaster recovery options for?
Red Hat®, JBoss®, OpenShift®, Fedora®, Hibernate®, Ansible®, CloudForms®, RHCA®, RHCE®, RHCSA®, Ceph®, and Gluster® are trademarks or registered trademarks of Red Hat, Inc. or its subsidiaries in the United States and other countries.

Salesforce is a trademark of Salesforce.com, Inc.

Box is a trademark of Box, Inc.

Other company, product, and service names may be trademarks or service marks of others.





 Terminology 

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.
For more information about network isolation, see [FS Cloud Boundary Protection](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-best-practicesbest-practices-boundary-protection).
* Not all application models can share infrastructure

Shared application infrastructure makes sense only for sets of applications that have similar architectures. For example, sets of applications that use stateless microservices, containers, and managed database services can easily be deployed together. Other applications that are based on VM images with local storage will need separate application infrastructure. It is best practice to identify 2 or 3 common architectural patterns so that a small number of application hosting deployable architectures can be built and used for many applications.
* Interactions with centralized networking and services



* Transit gateway



Connecting the shared infrastructure VPC to the central transit gateway requires a process where both the centralized operations team and the BU operations team coordinate to connect the VPC.



* Hyper Protect Crypto Services and other centralized services

Authorizing the connection across accounts requires a process where both the centralized operations team and the BU operations team coordinate to create a service-to-service authorization for the consuming applications.



* Hosting multiple applications on Kubernetes

Red Hat OpenShift and Kubernetes are designed for efficient hosting of multiple applications. However, it is best practice to leverage Kubernetes names spaces for application isolation and istio for application network ingress and egress controls. The cluster configuration to support an application must be automated, and that automation owned by the shared infrastructure hosting project. However, application owners can provide information to tailor the automation to there needs. Note that application owners should not have permission to modify the configuration of the shared infrastructure directly.
Understanding your responsibilities when you use the landing zone deployable architectures 

Learn about the management responsibilities and terms and conditions that you have when you use one of the landing zone deployable architectures.



* For more information about the responsibilities for you and for IBM® when you use a deployable architecture, see [Understanding your responsibilities when you use deployable architectures](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-responsibilities-deployable-architectures).
* 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 using IBM Cloud® products](https://cloud.ibm.com/docs/overview?topic=overview-shared-responsibilities).
* For the overall terms of use, see [IBM Cloud Terms and Notices](https://cloud.ibm.com/docs/overview/terms-of-use?topic=overview-terms).
* For more information about the shared responsibilities for each Financial Services Validated service, see [Responsibilities for operating services in your deployment](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-responsibilities) in IBM Cloud Framework for Financial Services.



Review the following sections for the specific responsibilities for you and for IBM when you use a landing zone deployable architecture.



 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.

The landing zone deployable architectures do not identify specific responsibilities in this area.





 Change management 

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



Table 2. Responsibilities for change management
The rows are read from left to right. The first column describes the task that the customer or IBM might be responsible for. The second column describes IBM responsibilities for that task. The third column describes your responsibilities as the customer for that task.

 Task IBM responsibilities Your responsibilities 

 Keep deployed services and resources up to date Apply fixes and updates to the compute resources that are created from the deployable architecture.
"out_of_vocabulary_words": 401,
"status": "analyzed"
}

The status field has one of the following values:



* analyzed indicates that the service has successfully analyzed the corpus.
* being_processed indicates that the service is still analyzing the corpus.
* undetermined indicates that the service encountered an error while processing the corpus.



Use a loop to check the status of the corpus every 10 seconds until it becomes analyzed. For more information about checking the status of a model's corpora, see [Listing corpora for a custom language model](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-manageCorporalistCorpora).







 Add words to the custom language model 

Although adding corpora is the recommended means of adding words to a custom language model, you can also add individual custom words to the model directly. The service parses custom words for the custom model just as it does the contents of words from corpora.

If you have only one or a few words to add to a model, using corpora to add the words might not be practical or even viable. The simplest approach is to add a word with only its spelling. But you can also indicate how the word is to be displayed and one or more pronunciations for the word.



* For more information about adding words to a custom model that is based on a previous-generation model, see [Working with custom words for previous-generation models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-corporaWordsworkingWords).
* For more information about adding words to a custom model that is based on next-generation model, see [Working with custom words for next-generation models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-corporaWords-ngworkingWords-ng).



After you add words to a custom model, examine the new custom words to check for typographical and other errors. This check is especially important when you add multiple words at one time.
: The reference architectures and guidance form a set of requirements if you want to pursue a designation of [IBM Cloud for Financial Services Validated](https://cloud.ibm.com/docs/overview?topic=overview-what-is-fscloudbecoming-fs-validated) from IBM. The Financial Services Validated designation signifies that you have successfully evidenced compliance to the control requirements of the IBM Cloud Framework for Financial Services and may improve your ability to market to financial institutions. Even though these should be considered requirements, there is a process for requesting the approval of deviations when certain aspects of the guidance may not be feasible or make sense for a given application.

Financial institution
: The reference architectures and guidance form a set of recommendations. As a financial institution, you know your controls better than IBM does. So, you have latitude in terms of following the guidance depending on what your internal controls dictate and the level of risk you are willing to take. IBM does not formally validate the applications of financial institutions.

In addition, the framework is intended to cover the two types of applications that you might deliver as an application provider:



* Software as a service (SaaS) – You develop and operate the application that is deployed on the IBM Cloud by using one of the reference architectures for the IBM Cloud for Financial Services.
* Software – You develop the application software, and another organization deploys and operates the application on their infrastructure in their own IBM Cloud account.







 Control implementation overview templates 

The templates that are referenced in this section are available under NDA only. Work with your IBM account representative to get access.

The framework's control implementation overview (CIO) templates provide detailed implementation and evidence guidance for all of the framework's control requirements. Each of the templates provides guidance specific to the underlying IBM Cloud technology used in one of the [reference architectures](https://cloud.ibm.com/docs/overview?topic=overview-what-is-fscloudframework-reference-architectures). They are referred to as "templates" because they allow you to assess how well your solution meets each of the control requirements. A completed CIO template is a requirement for any ecosystem partner seeking to be Financial Services Validated.
After reviewing the [overview](https://cloud.ibm.com/docs/satellite?topic=satellite-responsibilitiesoverview-by-resource), see what tasks you and IBM share responsibility for each area and resource when you use IBM Cloud Satellite.



 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 2. Responsibilities for incident and operations

 Task IBM responsibilities Your responsibilities 

 General <br><br> * Provide 24x7 customer support for Satellite locations.<br> * Provide [customer support plans](https://cloud.ibm.com/docs/get-support?topic=get-support-support-plans) to help resolve problems that you might encounter.<br><br><br> <br><br> * Procure the underlying compute, network, and storage infrastructure in your own environments that Satellite uses to extend IBM Cloud to these environments.<br><br><br> 
 Satellite Location <br><br> * Provide an interface to initiate operational activities, such as to create and delete locations.<br> * Set up a highly available location control plane that is fully managed for you in an IBM Cloud multizone metro.<br> * Monitor the health of the location, automatically resolve issues when possible, and alert IBM site reliability engineers when manual intervention is required.<br> * Automatically forward location events to your IBM Cloud Activity Tracker instance.<br><br><br> <br><br> * Use the provided tools to [create a location](https://cloud.ibm.com/docs/satellite?topic=satellite-locations), [add hosts](https://cloud.ibm.com/docs/satellite?topic=satellite-attach-hosts) to the location, [assign hosts](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-control-plane) with sufficient compute resources for the control plane worker components, and [debug](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-locations-debug) any issues that might happen in the location.<br><br><br>
* Built-in HA tools in IBM Cloud Kubernetes Service balance the workload within each geographic region, including self-healing and load balancing.







 Step 3: Analyze and prevent fraud 



* Deploy IBM Watson for Financial Services to prevent and detect fraud.
* Using the toolchains and Helm deployment tools, the apps are also deployed to the IBM Cloud Kubernetes Service clusters across the globe. Then, workloads and data meet regional regulations.









 Results 



* Lifting the existing monolithic VMs into cloud-hosted containers was a first step that allowed the Development Exec to save on capital and operations costs.
* With infrastructure management taken care of by IBM, the Development team was freed up to deliver updates 10 times daily.
* In parallel, the provider implemented simple time-boxed iterations to get a handle on the existing technical debt.
* With the number of transactions they process, they can scale their operations exponentially.
* At the same time, new fraud analysis with Watson increased the speed of detection and prevention, reducing fraud 4 times more than the region’s average.