vania-janet/multiturn-rag-retrieval-data huggingface dataset:
During a time-sensitive merger, a US regional bank needed to integrate two entities’ IT operations securely and bring consistency across container platforms in on-premises branch locations without adding overhead. Satellite enabled the customer to establish a location that used its existing data center infrastructure and create multiple Red Hat OpenShift on IBM Cloud clusters so that teams could build and host containerized workloads in a consistent way and pay only for what they consumed. This scenario is an example of using Satellite for platform modernization.

The following diagram shows a high-level overview of the architecture that is used by this financial institution.

Zoom

![High-level modification of Satellite reference architecture for the first institution](https://cloud.ibm.com/docs-content/v1/content/9ac5c38b41e0aa1cb4ccc6cc7f547751ec805221/framework-financial-services/satellite/images/satellite-use-cases/satellite_use_case_1_beta2_04_06.svg)

Figure 1. High-level modification of Satellite reference architecture for the first institution

Key features of their approach include:



* Using VMWare or other virtualization infrastructure to provide the hosts in the Satellite location.
* Leveraging a proxy that they manage for traffic to and from the Satellite location.
* Running Satellite-enabled Red Hat OpenShift on IBM Cloud for their workloads and exploring other Satellite-enabled services in later phases when they become Financial Services Validated.
* Hosting on-premises databases on virtual machines outside the Satellite location within the enterprise.
* Placing management tools in virtual servers within their IBM Cloud account.
* Using the following services on IBM Cloud:



* IAM for identity and access management
* Activity Tracker Event Routing event routing to collect IBM Cloud audit events
* Object Storage for backup and archiving data









 Multinational bank 

A multinational bank wanted to ensure they were following local requirements for data residency by keeping data in country when they were accessing public cloud services. The Satellite reference architecture was a perfect fit for them.

The following diagram shows a high-level overview of the architecture that is used by this second institution.

Zoom

!
AIX and IBM i production application hosting 

The client wants to run an enterprise-level workload in an infrastructure as a service (IaaS) environment with the ability to leverage the IBM Cloud services.



  Client needs 



*  Traditional IaaS value
*  Modernize core business by using the IBM Cloud portfolio
*  Flexible option to bursting and scaling their on-premises environment or to host temporary capacity
*  Interested in or have an evolving strategy for a consumption-based option
*  Looking to move away from operating a data center







  Examples 



*  Oracle© and Db2 Workloads
*  Custom Enterprise applications
*  Modernization and extending the value of their enterprise systems with IBM Cloud native applications
*  Customer acquiring a business and needs the temporary capacity while moving or merging multiple data centers







  Solution components 



*  IBM® Power Systems™ Virtual Server
*  PowerHA (optional)
*  Mass data migration (MDM)
*  Direct Link and Direct Link Dedicated for on-premises connectivity
*  Cloud Object Storage for optional backup and custom image hosting
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-ratelimit-analytics-options" "> --><-- <section "id="section-ratelimit-analytics-examples" "> --> Examples Get rate limit analytics for domain 31984fea73a15b45779fa0df4ef62f9b. ibmcloud cis ratelimit-analytics 31984fea73a15b45779fa0df4ef62f9b --recent 6h --time-delta 3600 -i "cis-demo" --output json
<-- </section "id="section-ratelimit-analytics-examples" "> --><-- </section "id="section-ratelimit-analytics" "> --><-- </section "id="section-metrics" "> --><-- <section "id="section-mtls-enable-cli-ref" "> --> MTLS enable <-- <section "id="section-access-enable" "> --> ibmcloud cis access-enable Enable Mutual TLS for a given service instance (Enterprise plan only). ibmcloud cis access-enable -i, --instance INSTANCE] ! ! ! ! ! ! ! ! 
<-- <section "id="section-command-options-access-enable" "> --> Command options -i , --instance value: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.<-- </section "id="section-command-options-access-enable" "> --><-- <section "id="section-command-example-access-enable" "> --> Examples Enable Mutual TLS for instance cis-demo. ibmcloud cis access-enable -i cis-demo
High availability for VPC reference architecture 

The [High availability (HA) overview](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-high-availability) desribes how HA is important for all cloud-based applications. In this article, you will learn more specifics about HA in the VPC reference architecture.



 Your workloads on VPC infrastructure 



 Workloads in multizone regions 



 Distribute workloads across zones 

Recall that all VPCs exist in a single region referring to the geographic area in which a VPC is deployed. It is recommended that you distribute your workloads across multiple zones within a region as the first step in creating an HA solution. That is, if one zone goes down, the other zones can continue to support the workload. You should use [Application Load Balancer for VPC (ALB)](https://cloud.ibm.com/docs/vpc?topic=vpc-load-balancers) to distribute your traffic across zones in a region.





 Scale based on resource demands 

Even with multiple zones, you should take additional steps to ensure that your environment can be scaled out based on the resources used by your workloads to enhance resiliency.

For example, by using [Auto Scale for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-auto-scale-instance-group), you can improve performance and costs by dynamically creating virtual server instances to meet the demands of your environment. You set scaling policies that define your desired average utilization for metrics like CPU, memory, and network usage. The policies that you define determine when virtual server instances are added or removed from your instance group.

For Red Hat OpenShift on IBM Cloud, you can use the cluster-autoscaler add-on to scale the worker pools in your cluster automatically to increase or decrease the number of worker nodes in the worker pool based on the sizing needs of your scheduled workloads.
IR-3 (2) - Coordination with Related Plans 



  Control requirements 

IR-3 (2) - 0
:   The organization coordinates incident response testing with organizational elements responsible for related plans.





  Additional IBM Cloud for Financial Services specifications 



*  Testing must also include the time it takes for resources to assemble in response to an incident, event, or crisis.
*  The 3rd/4th Party Response Teams must be included as part of the exercises.







  NIST supplemental guidance 

Organizational plans related to incident response testing include, for example, Business Continuity Plans, Contingency Plans, Disaster Recovery Plans, Continuity of Operations Plans, Crisis Communications Plans, Critical Infrastructure Plans, and Occupant Emergency Plans.
[Roles for Satellite reference architecture RACI matrix](https://cloud.ibm.com/docs-content/v1/content/9ac5c38b41e0aa1cb4ccc6cc7f547751ec805221/framework-financial-services/satellite/images/satellite-raci-roles/satellite_raci_roles_05_17_beta2.svg)

Figure 1. Roles for Satellite reference architecture RACI matrix



Table 2. Roles for deploying, managing, and operating all components of the Satellite reference architecture
The rows are read from left to right. The first column is the title for the role. The next columns describe the role.

 Role Description 

 Workload consumer Line-of-business organization that uses the workload or represents the internal or external users of the workload. 
 Workload provider Client IT development and operations team responsible for developing, deploying, and managing the workload and user responsibility for the PaaS layer (for example, by providing updated operating system images or requesting worker node upgrades). 
 IBM Cloud on-premises PaaS provider IBM Cloud development and operations teams responsible for the Satellite components deployed on-premises. Many supporting services, processes, and operations run in IBM Cloud. 
 On-premises IaaS / data center provider Client IT operations and facilities teams responsible for the data center, networking, hardware, and virtualization that supports the on-premises PaaS and workload. 
 IBM Cloud IaaS / data center provider IBM Cloud development and operations teams responsible for the direct Satellite management capabilities and supporting services that run in IBM Cloud. 







 Overview of shared responsibilities 

Review the following table of who is responsible for particular cloud resources when using Satellite. In the table, "Shared" means that there is a shared responsibility between the workload provider and the IBM Cloud on-premises PaaS provider.



Table 3. Overview of shared responsibilities.
The rows are read from left to right. The resource area of comparing responsibilities is in the first column. The next five columns describe whether you, IBM , or both have shared responsibilities for a particular area.
High availability overview 

Ensuring high availability (HA) is important for all cloud-based applications, and it is all the more critical for regulated workloads that the IBM Cloud for Financial Services is intended to host. In short, consumers depend on your application and cannot afford downtime. Using the VPC reference architecture and following the controls of the IBM Cloud Framework for Financial Services help you achieve that goal. When building an HA solution in IBM Cloud, you need to consider your workloads that run in virtual servers or Red Hat OpenShift on IBM Cloud and the HA characteristics of all of the other IBM Cloud services your solution depends on.



 HA for the reference architectures 

See the following resources depending on which reference architecture you are using:



* [High availability for VPC reference architecture](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-high-availability)
* [High availability for Satellite reference architecture](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-high-availability)







 HA in IBM Cloud services 

Your HA strategy needs to consider all of the IBM Cloud services in your deployment. The following table provides references to additional information on HA for each service in the reference architecture.



Table 1. High availability information for IBM Cloud services in the reference architectures

 Category VPC reference architecture Satellite reference architecture Optional for both 

 Core <br><br> * [VPC infrastructure services](https://cloud.ibm.com/vpc?topic=vpc-ha-dr-vpc)[1]<br><br><br> <br><br> * [Satellite](https://cloud.ibm.com/docs/satellite?topic=satellite-ha)<br><br><br>
* Meet with the event team to review the details of the event.
* Review critical functions and services that are required.
* Highlight key dates and times for actions.
* Assemble the team to ensure that plans are understood and actions are defined.



* A support plan with crisis management, including:



* Review the plan from previous years' event and post feedback actions.
* Revise the plan to ensure that roles and responsibilities are understood.
* Ensure that all service teams are aware of the event and ready for any activity that requires quick assistance or resolution.
* Ensure that any maintenance activity is known and understood.



* A create and practice plan. Actions include:



* A dry run of plan and expected or probable issue management.
* Test that the alert notifications are working as expected.
* Post an event review.



* An event postmortem review and retrospective, including:



* A postmortem with service teams to highlight any areas for improvement.
* Documenting and updating the plan for future events.











 Advanced Support 

Advanced Support is for environments with a limited number of business-critical applications.





 Basic Support 

Basic Support is provided for non-production environments or workloads that don't require traditional severities and response times.





 Support level and enterprises 

The level of support that is assigned to an [IBM Cloud enterprise](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-what-is-enterprise) defaults to the highest support plan within the enterprise. All child accounts within the enterprise also default to the highest support plan.





 Technical support team 

IBM Cloud supports our customers with a worldwide team of experts that are available 24 hours a day, seven days a week. These resources are at strategic IBM locations around the world. IBM Cloud support resources, which are known as the Advanced Customer Support team, is made up of technical engineers that have specific domain knowledge to triage and troubleshoot problems quickly and effectively.

The teams are organized by technology domains, which include compute, network, security, storage, VPC, Kubernetes service, Red Hat OpenShift on IBM Cloud, Satellite, databases, app development, and cognitive solutions.
The rows are read from left to right. The first column is the title for the set of tasks. The next column describe the tasks.

 Types of tasks Description 

 [Incident and operations management](https://cloud.ibm.com/docs/satellite?topic=satellite-responsibilitiesincident-and-ops) Includes tasks such as monitoring, event management, high availability, problem determination, recovery, and full state backup and recovery. 
 [Change management](https://cloud.ibm.com/docs/satellite?topic=satellite-responsibilitieschange-management) Includes tasks such as deployment, configuration, upgrades, patching, configuration changes, and deletion. 
 [Identity and access management](https://cloud.ibm.com/docs/satellite?topic=satellite-responsibilitiesiam-responsibilities) Includes tasks such as authentication, authorization, access control policies, and approving, granting, and revoking access. 
 [Security and regulation compliance](https://cloud.ibm.com/docs/satellite?topic=satellite-responsibilitiessecurity-compliance) Includes tasks such as security controls implementation and compliance certification. 
 [Disaster Recovery](https://cloud.ibm.com/docs/satellite?topic=satellite-responsibilitiesdisaster-recovery) Includes tasks such as providing dependencies on disaster recovery sites, provision disaster recovery environments, data and configuration backup, replicating data and configuration to the disaster recovery environment, and failover on disaster events. 







 Additional roles for shared responsibility matrix 

The two-party view of responsibility doesn't adequately account for the broader set of roles (often represented by teams or even different companies) that need to collaborate to ensure that the overall solution provides a secure platform for workloads and data. In the following diagram and table, a broader set of roles is defined.

Zoom

![Roles for Satellite reference architecture RACI matrix](https://cloud.ibm.com/docs-content/v1/content/9ac5c38b41e0aa1cb4ccc6cc7f547751ec805221/framework-financial-services/satellite/images/satellite-raci-roles/satellite_raci_roles_05_17_beta2.svg)

Figure 1.
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-update-glb-options" "> --><-- <section "id="section-update-glb-examples" "> --> Examples Update global load balancer 699d98642c564d2e855e9661899b7252 in domain 31984fea73a15b45779fa0df4ef62f9b. ibmcloud cis glb-update 31984fea73a15b45779fa0df4ef62f9b 699d98642c564d2e855e9661899b7252 --json '{"description":"Example global load balancer.","name":"www.example.com","ttl":60,"fallback_pool":"17b5962d775c646f3f9725cbc7a53df4","default_pools":"17b5962d775c646f3f9725cbc7a53df4","9290f38c5d07c2e2f4df57b1f61d4196"],"region_pools":{"WNAM":"de90f38ced07c2e2f4df50b1f61d4194","9290f38c5d07c2e2f4df57b1f61d4196"],"ENAM":"00920f38ce07c2e2f4df50b1f61d4194"] ! ! ! }}' -i "cis-demo"
"<em>Cloud</em> computing"
],
"text":
" Sanovi Technologies, a privately held <em>company</em> that provides <em>hybrid</em> <em>cloud</em> recovery, <em>cloud</em> migration",
"IBM to Acquire Sanovi Technologies to Expand Disaster Recovery Services for <em>Hybrid</em> <em>Cloud</em>nnPublished",
" undergoing digital and <em>hybrid</em> <em>cloud</em> transformation.nnURL: http://www.ibm.com/press/us/en/pressrelease/50837.wss",
" and business continuity software for enterprise data centers and <em>cloud</em> infrastructure. Adding"
],
"enriched_text.categories.label":
"/business and industrial/<em>company</em>/bankruptcy"
],
"enriched_text.entities.type":
"<em>Company</em>"
],
"html":
" Technologies, a privately held <em>company</em> that provides <em>hybrid</em> <em>cloud</em>n recovery, <em>cloud</em> migration and business",
" Disaster Recovery Services for <em>Hybrid</em> <em>Cloud</em></title></head>n<body>nnn<p>Published: Thu, 27 Oct 2016 07:01",
" digital and <em>hybrid</em> <em>cloud</em> transformation.</p>n<p>URL: http://www.ibm.com/press/us/en/pressrelease/50837.wss</p>nnnn</body></html>",
" continuity software for nenterprise data centers and <em>cloud</em> infrastructure. Adding these ncapabilities"
] ! !
}
}
Show more
Expert sizing type refers to a sizing exercise where customer-specific data is analyzed and used to put more detail on the sizing result for the hardware requirements of an SAP application (such as network, CPU, Memory, Storage).

According to SAP, expert sizing typically includes "exploring some business processes in more detail, both on functional and technical level" (quotation source: [Sizing Types - Expert Sizing](https://www.sap.com/about/benchmark/sizing.html)).

Therefore, with expert sizing, there are no standardized tools used to conduct the sizing it will often require significant effort and SAP expertise. Projects that use expert sizing often use an external consulting and system implementations business partner to assist the internal SAP team.

For expert sizing, the following steps are likely to be performed (source: [Sizing Types - Expert Sizing](https://www.sap.com/about/benchmark/sizing.html)):



* Identify the most important queries/apps/scenarios
* Identify, how they are used, for example, filter criteria, authorizations
* Run these queries/apps/scenarios on representative test data (quality of test data and quantity of test data). Ideally, on a recent copy of the production data
* Measure resource consumption (CPU/memory) and response times
* Perform a forecast calculation based on the expected usage of the queries/apps/scenarios







 TDI deployment method 

Supported hardware for SAP HANA depends on the deployment method. The TDI deployment method uses custom-defined hardware by SAP-certified hardware partners that use flexible OS or SAP HANA versions; these can be configured to any size (under the maximum configuration tested by SAP).

Partners (such as Cloud Service Providers) offer TDI with various configuration options and redundancy options. Thes options depend on whether you select scale-up or scale-out sizing, and must be installed by an appointed SAP HANA certified administrator. These may include:



* Redundant power supplies and fans and uninterrupted power supply (UPS)
* Enterprise grade error-correcting memories
* Fully redundant network switches and routers
* Disk storage systems use batteries to guarantee writing even in the presence of power failure
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. The FR remains focused on incident resolution at all times and is not expected to communicate directly with customers; they remain in regular contact with the Client Communicator on duty. It is important to note that the First Responder is precisely that, the first responder - he/she is not solely responsible for solving every incident.



The first responder will respond to alerts and off hours Severity 1 cases to:



* Determine the impact of the alert or case
* Determine the cause of the alert or case
* Initiate corrective action if appropriate
* Alert the Client Communicator if escalation is determined necessary.



The IBM first responder’s priority will be to restore service. The IBM client communicator is notified if there are any challenges to restoring service. The IBM client communicator will lead the recovery activities and escalate to any personnel required to resolve the issue, while also ensuring that continuous communication is maintained with the customer throughout the length of the incident.

Escalation Manager / Discipline Team Members Additional support for IRT members is provided by an Escalation Manager as well as dedicated Database and Network discipline team members. These specific SRE individuals are assigned to the IRT schedule to also provide coverage.





 Client Requests for RCA 

RCA (Root Cause Analysis)

For Severity 1 incidents, IBM SRE and the Incident Response Team (IRT) have a primary goal to restore service and remediate any disruption as soon as possible. Addressing the symptoms of an issue can often be sufficient enough to successfully restore service, but the underlying root cause may not have been identified during this process due to time constraints. A Root Cause Analysis (RCA) can be requested by customers for further analysis to help identify the underlying cause.
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-get-glb-events-options" "> --><-- <section "id="section-get-glb-events-examples" "> --> Examples Get glb events in instance cis-demo. ibmcloud cis glb-events -s "2020-05-20" -u "2020-05-22" --origin-name "dal09" --origin-healthy true -i "cis-demo"
<-- </section "id="section-get-glb-events-examples" "> --><-- </section "id="section-get-glb-events" "> --><-- </section "id="section-glb" "> --><-- <section "id="section-logpull-section" "> --> Logpull <-- <section "id="section-cli-logpull" "> --> ibmcloud cis logpull Manipulate Logpull services by using the following logpull commands. ibmcloud cis logpull DNS_DOMAIN_ID --available-fields --output FORMAT] ! ! ! ! ! ! ! !
<-- <section "id="section-command-options-logpull" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.--available-fields: List of all available fields.--ray-id value: Lookup logs by specific Ray ID.--fields value: Define field set in return. This must be specified as a comma separated list without any spaces, and all fields must exist. The order in which fields are specified doesn't matter, and the order of fields in the response is not specified. Note that fields are expected to be case sensitive.--start value: The (inclusive) beginning of the requested time frame.