vania-janet/multiturn-rag-retrieval-data huggingface dataset:
: 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/framework-financial-services?topic=framework-financial-services-aboutbecoming-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/framework-financial-services?topic=framework-financial-services-aboutframework-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.
* Using an orchestration framework like the open-source [Terragrunt](https://terragrunt.gruntwork.io/){: external) tool to manage the deployment and dependency management of linked Terraform workspaces.



Schematics Blueprints takes the orchestration approach to scaling environments. This builds on the IaC best practice of modular architectures and the reusable modules in the IBM Cloud module library. The benefits and challenges of these two approaches to scaling are discussed in the following sections.



 Remote state data sources 

[Remote-state data sources](https://cloud.ibm.com/docs/schematics?topic=schematics-remote-state) as implemented in Terraform and Schematics play an important role in enabling sharing of resource information between Terraform workspaces and teams.

Data sources allow responsibility for different elements of infrastructure to be delegated to different teams with information shared between workspaces (and teams) as read-only resources. Using data sources, common infrastructure resources like the components of a network backbone, can be shared between environments and teams without risk of unintended change.

One of the downsides of embedding remote_state data sources into Terraform automation code is the impact on the reusable of the modules across environments. Modules are specific to the remote-state they expect to receive as input and are dependent on the remote_state already existing.

More importantly for large environments, there is a lack of visibility of the remote-state dependency between workspaces. Consequently there is no dependency management, sequencing of module deployments or notification of dependency changes.

The solution is to externalize the dependencies and use orchestration.





 Orchestration and modules 

The alternative to data sources, is to make the passing of resource information between environments and workspaces explicit. Resource dependencies between workspaces are externalized at the workspace level. Here an orchestration framework performs dependency management, determining execution order and the passing of resource data between workspaces. This is the approach to scaling adopted by open source solutions like [Terragrunt](https://terragrunt.gruntwork.io/){: external) and other IaC automation frameworks, including Schematics Blueprints.
Understanding high availability for VMware as a Service 

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.



 Responsibilities 

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

For more information about your responsibilities when using VMware as a Service, see [Understanding your responsibilities when using VMware as a Service](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-vmaas-understand-responsib).





 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 workload. The level of availability that is right 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? 

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



Table 1. SLO for VMware as a Service

 Availability target Target value Method 

 Availability % 99.9% Single instance in a single zone. Your workload is restarted on other hosts if a host failure occurs. 
 Availability % 99.99% Multiple instances that are distributed across multiple zones or regions. Workload is not automatically restarted across zones or regions, but must be designed and implemented for continuous availability or warm standby between zones or regions. 



The SLO is not a warranty and IBM will not issue credits for failure to meet an objective. Refer to the SLAs for commitments and credits that are issued for failure to meet any committed SLAs.
RTO 

See [recovery time objective](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx3167918).





 rule 



* The set of allowed contexts that are associated with an IBM Cloud resource. The defined contexts dictate a user's or service's access to that resource.
* A set of conditional statements that are used to determine whether a build can be promoted. See also [profile](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx2034950), [scope](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx2037763).







 rule set 

A set of rules that define patterns for annotating text. If a pattern applies, then the actions of the rule are performed on the matched annotations. A rule typically specifies the condition that must match, an optional quantifier, a list of additional constraints that the matched text must fulfill, and the actions to be taken when a match occurs, such as creating a new annotation or modifying an existing annotation.





 runtime 

The set of resources used to run the application.







 S 



 SaaS 

See [software as a service](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx4585386).





 sandbox catalog 

A catalog in which approvals for publishing and lifecycle actions are bypassed so that it can be used for testing APIs under development.





 scale 

To increase platform (or system) capacity by adding more application or service instances





 SCM 

See [source control management](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx3579285).





 scope 

A grouping of resources that can be validated or evaluated for security and compliance.
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-opt-update-ddos-attack-l7-alert" "> --><-- <section "id="section-update-ddos-attack-l7-alert-examples" "> --> Examples Update a ddos attack alert policy a2633e68-1a64-2512-a321-b64a17c7db7a. ibmcloud cis alert-policy ddos-attack-l7-alert-update a2633e68-1a64-2512-a321-b64a17c7db7a --name test1 --emails test1@cn.ibm.com --webhooks b2633e68-9a64-4519-b361-a64a67c8db8e --enabled true -i "cis-demo"
<-- </section "id="section-update-ddos-attack-l7-alert-examples" "> --><-- </section "id="section-update-ddos-attack-l7-alert" "> --><-- <section "id="section-update-pool-toggle-alert" "> --> ibmcloud cis alert-policy pool-toggle-alert-update Update an alert policy for pool toogle alert. ibmcloud cis alert-policy pool-toggle-alert-update POLICY_ID --name NAME (--emails EMAILS | --webhooks WEBHOOKS) --enabled (true | false) --pools POOLS --trigger-condition (enabled | disabled | either) --include-future-pools (true | false)] --description DESCRIPTION] -i, --instance INSTANCE] --output FORMAT] ! ! ! ! ! !
<-- <section "id="section-opt-update-pool-toggle-alert" "> --> Command options POLICY_ID: The ID of alert policy.
Depending on the source environment complexity and the skills, experience and time commitments of your team, you might want to engage professional services. This action is done to plan and run the migration for you.



 Zone deployment 

Your source vCenter Server® instance with NSX-V environment is in one of the following deployment patterns:



* Simple - one single zone, with all VMware ESXi™ hosts deployed in one data center.
* Medium - two or more single zones, often used as production in one zone and development or DR in another zone.
* Medium - two or more single zones in a site deployment with no cross vCenter NSX-V.
* High - two or more single zones in a multisite deployment with cross vCenter NSX-V.
* High - multizone, with ESXi hosts deployed in multiple data centers.



IBM Cloud® for VMware Solutions offers standard deployment models, and multisite deployments require manual customization to build the want network topology.

This is a key parameter and defines the classification of the migration project and the required VMware NSX-T™ skills.





 Size 

The size parameter is based on the number of virtual machines and clusters. This parameter defines the scale and the length of the migration project. Larger environments are more complex, but not always.

This is not a key parameter. Therefore, if you have more than 1000 VMs, it does not classify the migration project as High complexity.





 vCenter deployment 

Is your vCenter deployed as independent or is it using the vCenter HA pattern? vCenter HA is not deployed as part of automation. If you want to deploy it, you must do the customization post deployment manually.

This is not a key parameter. However, it is related to the zone deployment category.





 ADDNS customization 

The primary use of vCenter Server instance ADDNS is to provide Active Directory™ and Domain Name Services to the infrastructure only. If you don't customize ADDNS, then the classification is Simple.

If you customize the service, such as by integrating it with your own AD or by using it for AD or DNS of workloads, you must do additional work.
If you are working with English-language legal contracts, enable the Content Intelligence feature to apply a contracts enrichment that can recognize and tag contract-related concepts in your data. Use this project type to automate complex business processes, such as contract review and negotiation. This project type can help to increase productivity, minimize costs, and reduce your legal exposure.

Only users of installed deployments (IBM Cloud Pak for Data) or Premium or Enterprise plan managed deployments can create this type of project.

In addition to the enrichments that are applied to a typical document retrieval project, the following enrichments are made automatically:



* Content from tables in the source document is tagged so that it can be found later.
* Contract details, such as payment terms or parties that are involved in the contract, are identified and tagged.



For any collection that you add to the project, optical character recognition (OCR) is enabled automatically so that text from scanned documents or other images is processed.

When you apply the contracts enrichment, you cannot use Smart Document Understanding to annotate documents. A pretrained SDU model that can recognize contract-related information is applied automatically. The Table understanding enrichment is automatically applied.

For more information, see [Understanding contracts](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-contracts-schema).





 Conversational Search 

The Conversational Search project returns information from a connected data collection as answers to questions that customers ask a chatbot, which is also known as an assistant.

Use IBM Watson® Assistant and Discovery together to give your assistant access to technical content and other knowledge base resources without having to relocate or copy your corporate data. The built-in synchronization capabilities mean that your assistant can share the most up-to-date information available. Use the integrations that are provided with Watson Assistant to deploy an assistant that connects to this project to various platforms, including your company website, in minutes.

The documents that you add to this type of project are not enriched automatically.

If you need to perform more complex searches from your virtual assistant, you might want to create a Document Retrieval project instead of Conversational Search project.
High availability and recovery 

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. Review what options you have to make your IBM Cloud Satellite® location highly available.

What level of availability do I need?
: You can achieve high availability on different levels in your backing infrastructure for the Satellite location, the Satellite location control plane, and within the different components of the clusters that you deploy to the location. The level of availability that is right 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?
: For IBM Cloud, see [How IBM Cloud ensures high availability and disaster recovery](https://cloud.ibm.com/docs/overview?topic=overview-zero-downtime).
: For Satellite, review the following topics.
: 

* [High availability of the Satellite control plane master](https://cloud.ibm.com/docs/satellite?topic=satellite-haha-control-plane-master).
* [High availability of the Satellite control plane worker nodes](https://cloud.ibm.com/docs/satellite?topic=satellite-haha-control-plane-worker).
* [High availability of IBM Cloud services](https://cloud.ibm.com/docs/satellite?topic=satellite-haha-cloud-services).



Where is the service located?
: See [Supported IBM Cloud locations](https://cloud.ibm.com/docs/satellite?topic=satellite-sat-regions).

What am I responsible to configure backup and recovery options for?
: See [Your responsibilities](https://cloud.ibm.com/docs/satellite?topic=satellite-responsibilitiesdisaster-recovery).



 Understanding high availability in IBM Cloud Satellite
smulampa-wsgroup us-east.workspace.smulampa-wsgroup.95a4d82d Sample workspace testing Terraform v1.0.11 FAILED False
smulampa-schematics-agent-service-workspace us-east.workspace.smulampa-schematics-agent-service-workspace.6936524b schematics agents service workspace Terraform v1.0.11 DRAFT False
smulampa-cos-module-workspace us-east.workspace.smulampa-cos-module-workspace.b77841ac smulampa-cos-module-workspace Terraform v1.0.11 INACTIVE False

OK


On successful update, it returns the updated details of an existing workspace.

For more information, see [troubleshooting section](https://cloud.ibm.com/docs/schematics?topic=schematics-wks-create-api&interface=cli).







 Displaying the workspace list through API 



1. Follow the [steps](https://cloud.ibm.com/docs/schematics?topic=schematics-setup-apics_api) to retrieve your IAM access token and authenticate with IBM Cloud Schematics by using the API.
2. Displaying the details of list of all existing workspace.

Example:

GET /v1/workspaces HTTP/1.1
Host: schematics.cloud.ibm.com
Content-Type: application/json
Authorization: <auth_token>
Cache-Control: no-cache
Postman-Token: b30e81a0-ae99-978c-c7e3-664371ddd1ea
3. Verify that the workspace is successfully listed with list of all workspace that were created.

curl -X GET https://schematics.cloud.ibm.com/v1/workspaces -H "Authorization: <iam_access_token>"
4.
Scope ibm_scope The scope is the account associated with this metric. 
 Service name ibm_service_name cloud-object-storage 







 Additional Attributes 

The following attributes are available for segmenting one or more attributes as described in the reference above. Please see the individual metrics for segmentation options.



Table 5: COS specific attributes

 Attribute Attribute Name Attribute Description 

 IBM COS Bucket storage class ibm_cos_bucket_storage_class Storage class of the bucket 
 Service instance ibm_service_instance The service instance segment identifies the guid of the instance the metric is associated with. 









 Next Steps 

You will want to manage the data the Monitoring instance is collecting for you. From management to setting alerts, you can [get started](https://cloud.ibm.com/docs/Monitoring-with-Sysdig?topic=Monitoring-with-Sysdig-getting-started) monitoring your data quickly and efficiently.
" 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
Shared infrastructure project n Manages the infrastructure as code for deploying dev and prod workload accounts and the shared infrastructure within those accounts 
 IaC Dev Project 1 Manages the infrastructure as code for deploying dev and test IaC accounts. These accounts are used for developing and testing deployable architectures 
 Application - Infrastructure Sets n Conceptual grouping - groups a set of application projects and the project that deploys the infrastructure to host those applications 



Zoom

![BU Admin service diagram. All of the information is conveyed in the surrounding text.](https://cloud.ibm.com/docs-content/v1/content/f18e964848e0337fedc42d43e246fa446f4b9646/enterprise-account-architecture/images/bu-hub-2.svg)

Figure 2. BU administration account services

Supporting the infrastructure as code elements in the BU administration account are Schematics workspaces and the Schematics agent. Schematics enables the use of deployable architectures that are stored in private Git repos that are hosted on the corporate network. This account also hosts the management and edge VPCs used in the VPC landing zone reference architecture if required by the BU.



Table 2. Components

 Component Quantity Description 

 Schematics agent 1 Used to enable privately hosted custom deployable architectures in the private catalog 
 Schematics workspaces n Orchestrated by projects, used to deploy the deployable architectures, and store the terraform state. One workspace per configuration within each project. 
 Management/Edge VPC 1 Hosts the shared management and edge resources for the business unit. This can include public load balancers, bastion hosts, and custom management services. 



The schematics agent can be deployed in the Management/Edge VPC, but the agent should not be accessible from the public internet.

Additional Components not shown in the diagram:



Table 3. Additional components

 Component Quantity Description 

 Activity Tracker 1 Provides an audit trail for activity within the account 
 IBM Cloud Logging 1 Provides log monitoring for the infrastructure hosting the Schematics Agent 
 IBM Cloud Monitoring 1 Provides performance and error monitoring for the Schematics Agent 
 Event Notifications 1 Provides notifications for Projects
* Security enhancements such as multifactor authentication (MFA), vSphere Trust Authority (vTA), and in–flight encryption for vSAN



vSphere 7 is also the exclusive basis for VMware Regulated Workloads.

For more information about end of life procedures for IBM Cloud infrastructure services and Third–Party software products, see [Lifecycle policy for IBM Cloud products](https://www.ibm.com/cloud/cloud-prod-life). If you have any questions or need assistance, email [clouddigitalsales@us.ibm.com](mailto:clouddigitalsales@us.ibm.com) or open a support ticket in the VMware Solutions console.



 Related links 



* [End of Support for NSX-V instance deployments](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-eos-nsx-v)
* [End of Support for vSphere 6.7 instance deployments](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-eos-vsphere67)