vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Satellite Connector <br><br> * Update the managed master components.<br> * Provide the ability to control access to connectors through IBM IAM.<br><br><br> You are responsible for keeping your container platform infrastructure secure and compliant. 
 Satellite Connector Agent Image <br><br> * Test and publish updates to the Satellite Connector Agent Image in the IBM Container Registry.<br> * Monitor and update the software inside the container image for CVE.<br><br><br> You are responsible for updating the Satellite Connector Agent Image to new versions published to the IBM Container Registry. 







 Disaster recovery 

Disaster 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.



Table 6. Responsibilities for disaster recovery.

 Task IBM responsibilities Your responsibilities 

 Satellite Location <br><br> * Back up location information to recover Satellite location control plane components to an IBM-managed bucket in your IBM Cloud Object Storage instance.<br> * Monitor the health of the location, automatically resolve issues when possible, and alert IBM site reliability engineers when manual intervention is required.<br><br><br> <br><br> * Define the disaster recovery requirements for the environment.<br> * Provide access to the backup in your [IBM Cloud Object Storage instance](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-getting-started-cloud-object-storage) if you need to recover a location.<br><br><br> 
 Satellite Host <br><br> * Back up information for hosts that are assigned to the location control plane to an IBM-managed IBM Cloud Object Storage instance.<br> * Back up information for hosts that are assigned to Satellite clusters to an IBM Cloud Object Storage instance in your account.<br><br><br> <br><br> * Maintain, repair, or replace hardware as needed.<br><br><br>
Overview of use cases 

Various use cases show the strengths of Red Hat® OpenShift® on IBM Cloud® and IBM Cloud services when used together. These stories highlight several industries as well as types of workloads. Even though each use case is presented through the lens of a particular industry, these workloads are typical across various industries. You see workload themes, such as one of the following areas.



* AI and machine learning
* Data and storage
* DevOps
* Identity management





Table 1. Use cases

 Industry Use case 

 Financial services <br><br> * [Trim IT costs and accelerate regulatory compliance](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_uc_financeuc_mortgage)<br> * [Streamline developer productivity to deploy AI tools to partners 4 times faster](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_uc_financeuc_payment_tech)<br><br><br> 
 Government <br><br> * [Secure the exchange of data, connecting public and private organizations](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_uc_govuc_port)<br> * [Improve collaboration velocity with community Developers, combining public-private data](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_uc_govuc_data_mashup)<br><br><br> 
 Healthcare <br><br> * [Migrate workloads from inefficient VMs to easily operated containers for patient systems](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_uc_healthuc_migrate)<br> * [Securely host sensitive data while you grow research with partners](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_uc_healthuc_research)<br><br><br>
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-create-glb-options" "> --><-- <section "id="section-create-glb-examples" "> --> Examples Create a global load balancer in domain 31984fea73a15b45779fa0df4ef62f9b. ibmcloud cis glb-create 31984fea73a15b45779fa0df4ef62f9b --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"
<-- </section "id="section-create-glb-examples" "> --><-- </section "id="section-create-glb" "> --><-- <section "id="section-update-glb" "> --> ibmcloud cis glb-update Update a global load balancer under a given DNS domain.
Both secrets and configmaps are "maps"; so the environment variables set will have a name corresponding to the "key" of each entry in those maps, and the environment variable values will be the value of that "key".
4. To verify whether the backend application is updated with the binding and configmap. You can run the below command and look for the Service Bindings and Environment Variables sections in the output

ibmcloud code-engine application get --name backend
5. Go to the frontend UI and upload text files for text analysis. You should see the uploaded files with Not analyzed tag on them.









 Step 5: Process text files with an automated job 

Now, you have the backend application connected to the frontend application. You have provided all the required credentials through service binding and uploaded files for text analysis. To complete the test, you will create a job to specify workload configuration information that is used each time that the job is run to analyze text using Natural Language Understanding service.



 Create a job 

Jobs, unlike applications which react to incoming HTTP requests, are meant to be used for running container images that contain an executable designed to run one time and then exit. When you create a job, you can specify workload configuration information that is used each time the job is run. You can create a job from the console or with the CLI.

This job will read text files from IBM Cloud Object Storage, and then analyze them using the Natural Language Understanding Service. It will need to have access to service credentials for both services.



1. Run the following command to create a job,

ibmcloud code-engine job create --name backend-job --image icr.io/solution-tutorials/tutorial-text-analysis-code-engine-backend-job --env-from-configmap backend-configuration

You can set the version of Natural Language Understanding service using the --env flag. For versioning, check this [link](https://cloud.ibm.com/docs/natural-language-understanding?topic=natural-language-understanding-versioning)







 Bind the IBM Cloud services to job 



1.
When properly configured and managed, services that are Financial Services Validated work together so you can deliver a solution that conforms to the best practices of the IBM Cloud Framework for Financial Services. The following table shows the required services that are included in the Satellite reference architecture and the complementary optional services that are available.

Generally speaking, you should strive to use only services which are Financial Services Validated in your solutions. However, depending on your circumstance there may be exceptions. See the best practice [Use only services that are IBM Cloud for Financial Services Validated](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-best-practicesbest-practices-financial-services-validated-services) for more details and potential exceptions.



Table 2. Required and optional services for Satellite reference architecture

 Category Required services Optional services 

 Satellite <br><br> * [IBM Cloud Satellite®](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-aboutservices-core-satellite)<br><br><br> 
 Containers <br><br> * [Red Hat® OpenShift® on IBM Cloud®](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-aboutservices-containers-openshift)[1]<br> * [IBM Cloud® Container Registry](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-aboutservices-containers-registry)<br><br><br> 
 Storage <br><br> * [IBM Cloud® Object Storage](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-aboutservices-storage-cos)<br><br><br>
VMware Solutions Dedicated - known issue for IBM Cloud for VMware Mission Critical Workloads
: For Mission Critical Workloads, a known issue with vCenter HA failover exists. If eth0 is not active on the passive node before failover is initiated, the passive node is isolated and fails to take over as the active node. vCenter HA might not activate eth0 when failover is initiated.

VMware Regulated Workloads
: (Updated on 4 May 2021) The VMware Regulated Workloads offering delivers a new multizone architecture to instances that are deployed in 4.1 and later releases. The multizone architecture can help to prevent downtime for cloud applications and to automate failovers within a cloud region.

Security and Compliance Readiness Bundle
: The Security and Compliance Readiness Bundle is a prescriptive offering that provides many of the security and compliance features of IBM Cloud for Financial Services at a lower entry price. The offering is packaged with security and compliance tools and templates for you to use with your preferred regulation standard.

Add-on services
: The 4.1 release provides the following service versions on newly deployed instances.



* BIG-IP VE v15.1.2
* FortiGate Virtual Appliance 6.4.4
* HyTrust CloudControl v6.3
* Veeam v11



Services support for vCenter Server multizone instances
: Starting with the 4.1 release, the following add-on services are supported on vCenter Server multizone instances.



* Caveonix RiskForesight
* HyTrust CloudControl
* Veeam
* vRealize Operations and Log Insight



Caveonix RiskForesight
: Review the following information about Caveonix RiskForesight for the 4.1 release.



* Caveonix RiskForesight is offered as a per-host license for new deployments of Caveonix on VMware Regulated Workloads and Security and Compliance Readiness Bundle instances. For vCenter Server deployments, Caveonix is still offered as license packs that are priced per virtual machine (VM).
* A Caveonix RiskForesight license is valid for five years.
For more information, see [Accessing external resources from the Satellite location](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-connectivity-to-external).







 Configure network flow rules for workload hosts 

The following rules for workload hosts must be implemented within the networking infrastructure (virtual or physical) provided by the operator of the Satellite location.



1. Allow inbound network flows to workload hosts from management resources within your environment, such as a bastion host in your management plane. It is recommended to use networking components capable of controlling Level 7 traffic to limit access to services such as Red Hat OpenShift on IBM Cloud web console based on the FQDN of the request. A combination of network rules and an HTTP proxy can be used as well.
2. Allow bidirectional network flows between workload hosts and control plane hosts of the same Satellite location.
3. Identify and allow network flows to other application resources within the environment that is required by the deployed workloads. For example, databases that are not deployed on the same workload service.
4. Identify and allow network flows to other services deployed in the Satellite location (for example, another Red Hat OpenShift on IBM Cloud cluster) if required by the workload application architecture.
5. Identify and allow the ingress network flows from the edge plane that is used to expose the workload services to application consumers (for example, load balancers).
6. Allow outbound network flows to service endpoints in management plane that is needed for logging and monitoring.
7. Ensure that workload hosts have outbound access to IBM Cloud public endpoints. For more information, see [Accessing external resources](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-connectivity-to-external).







 (Optional) Configure virtual network flow rules within Red Hat OpenShift on IBM Cloud 



1. Configure virtual network flow rules within Red Hat OpenShift on IBM Cloud.
When the reasonCode for an API call is any of the following values, the value of severity is set as follows:



Table 4. Severity value for some reason codes

 reasonCode description severity 

 400 Bad Request warning 
 401 Unauthorized critical 
 403 Forbidden critical 
 409 Conflict warning 
 424 Failed Dependency warning 
 500 Internal Server Error warning 
 502 Bad Gateway warning 
 503 Service Unavailable critical 
 504 Gateway Timeout warning 
 505 HTTP Version Not Supported warning 
 507 Insufficient Storage critical 







 Target fields 

Target fields provide information about the resource that is accessed, created, updated, or deleted by the initiator's action in your account.

The following table lists common target fields that are available for each event:



Table 5. Common target fields

 Field Name Description Value 

 target.id[1] Cloud Resource Name (CRN) of the resource on which the action is executed. For example, crn:v1:bluemix:public:cloud-object-storage:global:a/12345678e6232019c6567c9123456789:fr56et47-befb-440a-a223c-12345678dae1:bucket:bucket1 
 target.name Human-readable name of the resource on which the action is executed. 
 target.typeURI Type of the cloud resource on which the action is executed. For example, iam-am/policy or cloud-object-storage/bucket/acl 
 target.host.address IP Address or URL of the target service 



[1] For events that are generated by Cloud Foundry, the target.id is set to the GUID of the resource.



 target.id (string) 

This field indicates the IBM Cloud resource on which the action is executed.

The format of this field is a CRN. For more information, see [CRN format](https://cloud.ibm.com/docs/account?topic=account-crn).





 target.name (string) 

This field indicates the human readable name of the IBM Cloud resource on which the action is executed.

Make sure that the name of resources does not include sensitive or PII data.
The prior figure illustrates the reuse of a template across the stages of a delivery pipeline. A single template provides a common architecture pattern against which application code can be developed and tested in production like environments. The configuration for each environment is provided by the inputs, customizing each stage of the pipeline, adjusting for scaling, region and networking.







 Customization best practice 

Blueprints best practice is to for templates to be reusable across the instances of an application environment, from dev to stage and production. This is an outcome of [IaC modular architecture best practice](https://cloud.ibm.com/docs/schematics?topic=schematics-infrastructure-as-codeiac-bp-modularity), where the reliability of reusable components increases through testing and hardening via reuse. External configuration of templates customizes a deployment for a blueprint environment. customization is performed by separately define, and updated version blueprint input configurations, with hardcoding of specific configurations avoided within the template itself. The template itself being maintained and versioned separately to the environment specific customization.



 Blueprint customization 

Blueprints is built around reuse. Blueprints' implements layers of configuration that build on reusable shared modules, with layers of customization targeting specific use cases. This provides for independent versioning of components, update and maintenance of templates and of the (externalized) configurations. These layers are described below in increasing order of customization:



* Modules: Reusable components, implementing the layers of an application architecture. Designed for reuse across multiple architectures, teams and organizations. Modules are lightly opinionated to implement security and organization best practices, while allowing for reuse. They are actively maintained and semantically versioned. Module version selection is determined at the template layer.
* Templates: Templates are written to address a range deployments for a specific architecture and application. It is an opinionated implementation of an application architecture out of reusable modules. Templates support external customization of infrastructure scaling, deployment region, application components, network and security configuration. They are semantically versioned and maintained through update of module versions.



* User customizable inputs are externalized for configuration as inputs.
When you create a job, you can specify workload configuration information that is used each time that the job is run. 
 Project A project is a grouping of Code Engine entities such as applications, jobs, and builds. A project is based on a Kubernetes namespace. The name of your project must be unique within your IBM Cloud® resource group, user account, and region. Projects are used to manage resources and provide access to its entities. A project provides the following items.<br><br><br><br> * Provides a unique namespace for entity names.<br> * Manages access to project resources (inbound access).<br> * Manages access to backing services, registries, and repositories (outbound access).<br> * Has an automatically generated certificate for Transport Layer Service (TLS).<br><br><br> 
 Secret A secret provides a method to include sensitive configuration information, such as passwords or SSH keys, to your deployment. By referencing values from your secret, you can decouple sensitive information from your deployment to keep your app or job portable. Anyone who is authorized to your project can also view your secrets; be sure that you know that the secret information can be shared with those users. Secrets contain information in key-value pairs. 
 Service binding Service bindings provide applications and jobs access to IBM Cloud services. 
 Subscription A subscription provides a way of signing up to receive events from a particular event producer. For more information about the different types of event producers and how to subscribe to them, see [Subscribing to event producers](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribing-events).
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/framework-financial-servicesframework-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.





 Reference architectures and deployment guidance 

[Reference architectures](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-reference-architecture-overview) have been defined which can be used as a basis for meeting the security and regulatory requirements defined by the controls. The reference architectures each center on specific IBM Cloud technologies, including:
More information will be provided as it becomes available.</p>"
}
],
"category": "Incident",
"componentNames": "Cloudant",
"continentNames": [
"North America",
"Europe",
"Asia Pacific"
],
"regionNames": [
"Washington DC",
"London",
"Dallas",
"Sydney",
"Tokyo",
"Frankfurt"
],
"regions": [
"us-east",
"eu-gb",
"us-south",
"au-syd",
"jp-tok",
"eu-de"
],
"severity": "Severity 1",
"sourceID": "INC3918600",
"startTime": 1621949594,
"state": "Investigating",
"title": [
{
"language": "en",
"text": "INVESTIGATING: IBM Cloudant - selective services are unavailable"
}
],
"updateTime": 1621954682
}
Show more



 Field values 

The following descriptions provide information about the field values that are being sent inside the payload:

body: This field describes the event that is happening on the platform and concerns you. This field contains a detailed, human readable description of the notification and can be several paragraphs long. It can also contain html formatting. This field is configured to support more languages, although only English is supported currently.

category: The type of the event. This can be incident, maintenance, announcement, or security bulletins.

componentNames: If a service is impacted, this field represents it. This also can be a global value like Component: IBM Cloud, not only a specific service. See the services on the [IBM Cloud catalog page](https://cloud.ibm.com/catalogservices).

regions: This field shows you the location of the event.