vania-janet/multiturn-rag-retrieval-data huggingface dataset:
To generate an API Key, click on Manage (located in top menu bar), select IAM, and then API keys. When entering the value in Schematics, be sure to select the "Sensitive" checkbox.
3. Inspect the remaining variables and update the values as needed. For example, you will most likely need to update the resource group name.

Refer to the readme which accompanies the Terraform code for descriptions on variable names and their usage. In this example, you will see variables for configuring the subnet tiers, whether or not public gateways for a zone are enabled, subnet acl rules, etc.







 Apply VPC Terraform Code 



1. Click the Generate plan to validate the configuration. This is similar to running terraform plan when using the CLI. No changes will be made nor any resources deployed. This will only perform a test run. ![GenerateWorkspace](https://cloud.ibm.com/docs-content/v1/content/d50364af907081c3c38f99c11f35dd9cab4b2510/vpc-journey/images/provision-vpc/schematics-workspace-generate.png)
2. If the generate action completes successfully, click on the Apply plan button to provision this cloud native configuration on VPC.
3. Once the apply plan completes successfully, click on the menu icon (located in the top left corner) and navigate to the VPC Infrastructure page to browse your newly created VPC instance!
4. (Optional) If you would like to delete/destroy the VPC resources which was created, go back to the Schematics Workspace and select Actions > Destroy resources. ![DestroyResources](https://cloud.ibm.com/docs-content/v1/content/d50364af907081c3c38f99c11f35dd9cab4b2510/vpc-journey/images/provision-vpc/destroy-resources.png)









 Additional VPC Deployment Patterns and Resources
To determine which VPC contains the public gateway, run the GET /public_gateways/{id} command and look at the "vpc" value. The equivalent CLI command is ibmcloud is public-gateway <id>.





 vpn_connection_cidr_duplicated 

Message: The <cidr_type> CIDR blocks have duplicated CIDR blocks <cidr_blocks>.

Duplicate CIDR blocks have been provided when creating the connection. Ensure that the CIDR blocks are unique.

For further instructions to fix this problem, refer to the [API documentation](https://cloud.ibm.com/apidocs/vpc-on-classic). If the problem persists, [contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support).





 vpn_connection_cidr_not_created 

Message: A CIDR block could not be added to the VPN connection <vpn_connection_id>.

Provide a valid CIDR that meets the requirements given by the [API documentation](https://cloud.ibm.com/apidocs/vpc-on-classic). If this problem persists, [contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support).





 vpn_connection_cidr_not_deleted 

Message: A CIDR block could not be deleted from the VPN connection <vpn_connection_id>.

Provide a valid CIDR that exists on the connection. A connection must have at least one local and peer CIDR.

To view the connection's CIDR blocks, use the GET /vpn_gateways/<vpn_gateway_id>/connections/<vpn_connection_id> API and check the local_cidrs and peer_cidrs fields. Equivalent CLI command: ibmcloud is vpn-gateway-connection VPN_GATEWAY_ID CONNECTION_ID





 vpn_connection_cidr_not_found
Virtual and bare metal servers On-prem IaaS / data center provider On-prem IaaS / data center provider On-prem IaaS / data center provider On-prem IaaS / data center provider On-prem IaaS / data center provider 
 Virtual storage On-prem IaaS / data center provider On-prem IaaS / data center provider On-prem IaaS / data center provider On-prem IaaS / data center provider On-prem IaaS / data center provider 
 Virtual network On-prem IaaS / data center provider On-prem IaaS / data center provider On-prem IaaS / data center provider On-prem IaaS / data center provider On-prem IaaS / data center provider 
 Hypervisor On-prem IaaS / data center provider On-prem IaaS / data center provider On-prem IaaS / data center provider On-prem IaaS / data center provider On-prem IaaS / data center provider 
 Physical servers and memory On-prem IaaS / data center provider On-prem IaaS / data center provider On-prem IaaS / data center provider On-prem IaaS / data center provider On-prem IaaS / data center provider 
 Physical storage On-prem IaaS / data center provider On-prem IaaS / data center provider On-prem IaaS / data center provider On-prem IaaS / data center provider On-prem IaaS / data center provider 
 Physical network and devices On-prem IaaS / data center provider On-prem IaaS / data center provider On-prem IaaS / data center provider On-prem IaaS / data center provider On-prem IaaS / data center provider 
 Facilities and data centers On-prem IaaS / data center provider On-prem IaaS / data center provider On-prem IaaS / data center provider On-prem IaaS / data center provider On-prem IaaS / data center provider 







 Satellite location control plane and workload clusters 

The following table goes a level deeper and shows the shared responsibilities for the control plane worker nodes and your workload clusters in the Satellite location. In the table, "Shared" means that there is a shared responsibility between the workload provider and the IBM Cloud on-premises PaaS provider.



Table 4. Overview of shared responsibilities in Satellite location.
The rows are read from left to right.
A good example is the [IBM Cloud Kubernetes Service](https://cloud.ibm.com/docs/containers?topic=containers-getting-started).
5. Infrastructure as a Service (IaaS) with Java EE runtime. A good example is the [WebSphere Application Server VM on IBM Cloud](https://cloud.ibm.com/catalog/services/websphere-application-server).



The following table compares elements of each architecture from the perspective of a developer that is creating and operating applications:



Table 1. Architecture comparison

 Topic (1) FaaS on Cloud Functions (2) IaaS with OpenWhisk RYO (3) PaaS (4) CaaS (5) IaaS with Java EE 

 Application unit Single function (usually small block of code in JavaScript, Swift, or Docker container) - can be less than one Kb, but can be larger. Usually not more than few Kb. Same as column (1) Depends on the runtime used. An EAR or WAR file, or other language-specific application bundle, usually relatively large - Kb or even Mb with many services in a bundle, but can be as small as a single service. Docker container is the unit of deployment. VM with App Server with EAR or WAR file and other dependencies - usually sized at GB. 
 Resource footprint Small. The user does not pay or care about memory, CPU, or other resources. Although the action does have some footprint, the user does not need to worry about it. High. The user must first provision IaaS environment and only then install and configure OpenWhisk on top of it. Small. The user pays for memory and CPU for running apps, but nothing for apps that are not running. Small to Medium High. User has to pay for disk storage, memory, CPUs, and possibly other components when the app is running. When it is stopped, only the storage costs occur. 
 Installation and setup None required Hard. All installation is done by the user. None required Moderate. Hardware, networking, OS, and container management tools provided by CaaS vendor. Images, connectivity, and instances provided by the user.
Virtual storage The block, file, or Object Storage buckets ordered and managed through IBM Cloud. IBM owns Cloudant, COS, RabbitMQ, Redis - used by Schematics Client owns and manages the instances. IBM owns the IKS local storage used by Schematics Agents COS that are used by Schematics Agents 
 Virtual network Network resources such as VLAN, VPC, subnets, or IPs provided by classic infrastructure and VPC services that are ordered and managed through IBM Cloud. IBM owned Network resources used by Schematics Client owns and manages the network resources such as ingress, egress policies used by Agents. 
 Hypervisor The software and configuration that is deployed in physical servers to host and manage the lifecycle of virtual servers. IBM owns the IKS used by Schematics Client owns [IKS / ROKS / Kubernetes](https://cloud.ibm.com/docs/containers?topic=containers-responsibilities_iks) cluster only if client uses cluster provided by IBM IKS. 
 Physical servers and memory The physical compute devices and resources, such as cores, memory, and GPUs used to host the virtual or bare metal servers. IBM owns the [IKS](https://cloud.ibm.com/docs/containers?topic=containers-responsibilities_iks) used by Schematics Client owns, if cluster provided by Customer. IBM owns if the cluster is provided by [IKS / ROKS / Kubernetes](https://cloud.ibm.com/docs/containers?topic=containers-responsibilities_iks). 
 Physical storage The physical storage devices and resources, such as disks and storage devices that are used to host the virtual block, file, or Object Storage buckets. IBM owns the [IKS](https://cloud.ibm.com/docs/containers?topic=containers-responsibilities_iks) used by Schematics Client owns, if cluster provided by Customer. IBM owns if the cluster is provided by [IKS / ROKS / Kubernetes](https://cloud.ibm.com/docs/containers?topic=containers-responsibilities_iks).
On IBM Cloud, the benchmarks used two different configurations:



* bx2-8x32
* bx2-16x64



As you can see, SNAP results show that bx2-8x32 provides more performance because of higher effective network bandwidth ratio per core; where Quicksilver does well with bx2-16x64 as it has moderate communication requirements and is mostly near-neighbor to track particle motion across the global domain.

Zoom

![EDA-diagram](https://cloud.ibm.com/docs-content/v1/content/74a831a53989757bd05bd0dea7bb42c9ede61d0f/ibm-spectrum-lsf/images/DoE-Snap-Scaling.png)

Figure 3. SNAP scaling diagram

Zoom

![EDA-diagram](https://cloud.ibm.com/docs-content/v1/content/74a831a53989757bd05bd0dea7bb42c9ede61d0f/ibm-spectrum-lsf/images/DoE-Cores.png)

Figure 4. Quicksilver scaling diagram

Even though the scaling is not as good as the weather model, IBM Cloud can scale up to thousands of cores reasonably with a linear curve.







 Virtual machine use cases 

The choice of virtual machine profile type for IBM Cloud depends on your workload details on cores, memory, and network requirements.



 Single node virtual machine use cases 

This should be the first evaluation as it can provide the best price and performance for running such jobs on IBM Cloud.

You can choose from the following set of virtual machine profiles:



* CX2-16x32 to CX2-128x256
* BX2-16x64 to BX2-128x512
* MX2-16x128 to MX2-128x1024



Depending on the memory required per core, you might pick the MX2 configuration, which can support up to 1 TB on the MX2-128x1024 profile.
: IBM allows a customer to lease just enough compute, storage, and network facilities to run a single instance of their system. This is the lowest cost option, available at data centers around the world, and comes with an availability target of 99.9% uptime, not including planned outages.

Local redundancy
: This next level up provides two instances of the system in a single data center. Target uptime for local redundancy is 99.95% uptime, not including planned outages.

Regional redundancy
: This third level up uses an IBM multizone region (MZR) to provide connections from two independent power vendors, redundant connections to two different network PoPs, and three independent data centers that are spread across a metro area where the customer can lease facilities for three instances of their system, with a target uptime of 99.99% availability, with no exclusions for planned outages.

Global redundancy
: For customers who want a global presence or the highest levels of availability, IBM public cloud offers global redundancy, using two (or more commonly three) MZRs in different geographies, with a target uptime of 99.995% uptime, and no exclusions for planed outages. IBM public cloud customers seem to find this range of options allow them to match their business needs to their desired availability in an effective way.
"ca-tor":"s3.ca-tor.cloud-object-storage.appdomain.cloud"
},
"private":{
"ca-tor":"s3.private.ca-tor.cloud-object-storage.appdomain.cloud"
},
"direct":{
"ca-tor":"s3.direct.ca-tor.cloud-object-storage.appdomain.cloud"
}
},
"br-sao":{
"public":{
"br-sao":"s3.br-sao.cloud-object-storage.appdomain.cloud"
},
"private":{
"br-sao":"s3.private.br-sao.cloud-object-storage.appdomain.cloud"
},
"direct":{
"br-sao":"s3.direct.br-sao.cloud-object-storage.appdomain.cloud"
}
}
},
"single-site":{
"ams03":{
"public":{
"ams03":"s3.ams03.cloud-object-storage.appdomain.cloud"
},
"private":{
"ams03":"s3.private.ams03.cloud-object-storage.appdomain.cloud"
},
"direct":{
"ams03":"s3.direct.ams03.cloud-object-storage.appdomain.cloud"
}
},
"che01":{
"public":{
"che01":"s3.che01.cloud-object-storage.appdomain.cloud"
},
"private":{
"che01":"s3.private.che01.cloud-object-storage.appdomain.cloud"
},
"direct":{
tor01 Public s3.tor01.cloud-object-storage.appdomain.cloud 
 tor01 Private s3.private.tor01.cloud-object-storage.appdomain.cloud 
 tor01 Direct s3.direct.tor01.cloud-object-storage.appdomain.cloud 
 osl01 Public s3.osl01.cloud-object-storage.appdomain.cloud 
 osl01 Private s3.private.osl01.cloud-object-storage.appdomain.cloud 
 osl01 Direct s3.direct.osl01.cloud-object-storage.appdomain.cloud 
 hkg02 Public s3.hkg02.cloud-object-storage.appdomain.cloud 
 hkg02 Private s3.private.hkg02.cloud-object-storage.appdomain.cloud 
 hkg02 Direct s3.direct.hkg02.cloud-object-storage.appdomain.cloud 
 seo01 Public s3.seo01.cloud-object-storage.appdomain.cloud 
 seo01 Private s3.private.seo01.cloud-object-storage.appdomain.cloud 
 seo01 Direct s3.direct.seo01.cloud-object-storage.appdomain.cloud
Getting started with Code Engine workloads in Satellite 

With IBM Cloud® Code Engine on IBM Cloud Satellite, you can run your apps and jobs in a distributed cloud environment, bringing the scalability and flexibility of public cloud services to your secure private cloud. Use your own compute infrastructure in your on-premises data center, edge networks, or other supported cloud providers to create your Satellite location and to power your workloads. By combining the capabilities of Code Engine and Satellite, you can consistently deploy, manage, and control your workloads from a single pane of glass across your infrastructure.

Support for Code Engine workloads in Satellite is currently in Beta and available for allowlisted accounts only. To take part in the Beta, contact support by [opening a case](https://cloud.ibm.com/unifiedsupport/cases/form). Select Application Development & Integration -> Code Engine -> Other. Enter "Request access to Beta" in issue subject. Compute environments and their contents, including projects, secrets, apps, jobs, and job runs that you create during Beta might be reset and will be removed at the end of Beta. Do not use for production.

To use Code Engine on Satellite, you must first create a compute environment in a Satellite location. From within this compute environment, you can deploy apps and run jobs from your own infrastructure. For more information about Satellite, see [Getting started with Satellite](https://cloud.ibm.com/docs/satellite?topic=satellite-getting-started).

Zoom

![Code Engine workloads in Satellite overview](https://cloud.ibm.com/docs-content/v1/content/ad5f41087138b4b1bb795e3b5b0661ac5a105cbd/codeengine/images/ce_on_sat.svg)

Figure 1. Code Engine workloads in Satellite overview



 Limitations for Beta 



* Supported in the eu-de region only.
* No support for building images from source.
* No support for subscriptions.
* No support for SOC2.
* No support for IBM Cloud Framework for Financial Services validation.
Provisioning a virtual server instance from a third-party image 

You can provision a virtual server instance from an image that was created by a third-party vendor. Third-party images are available through the IBM Cloud® catalog Cloud Images link.



 Before you begin 

Before you begin, make sure that you have your IBM Cloud catalog credentials set up.

For the IBM Cloud catalog, you must have an upgraded account to order virtual servers. For more information about upgrading your account, see [Account types](https://cloud.ibm.com/docs/account?topic=account-accounts).





 Selecting a virtual server image 



1. Log in to the [IBM Cloud catalog](https://cloud.ibm.com/catalog) by using your unique credentials.
2. In the Compute section, locate the Cloud Images section and click the third-party image that you want to deploy.
3. Review the custom image details and click Continue. The Virtual server instance - custom image page is displayed with your custom image preselected.







 Reviewing and choosing your deployment options 

For more information, see the following topics:



Table 1. Deployment options

 Deployment options Description 

 [Public virtual server](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-about-public-virtual-serversabout-public-virtual-servers) IBM-managed, multi-tenancy virtual server deployments 
 [Transient virtual server](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-about-vs-transient) IBM-managed, multi-tenancy virtual server deployments offered at a reduced cost and best suited for flexible workloads 
 [Reserved virtual server](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-about-reserved-virtual-serversabout-reserved-virtual-servers) IBM-managed, multi-tenancy virtual server deployments with guaranteed capacity for a contract term 
 [Dedicated virtual server](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-dedicated-virtual-servers) IBM-managed, single-tenancy virtual server deployments
Physical servers and memory On-premises IaaS / data center provider On-premises IaaS / data center provider 
 Physical storage On-premises IaaS / data center provider On-premises IaaS / data center provider 
 Physical network and devices On-premises IaaS / data center provider On-premises IaaS / data center provider 
 Facilities and data centers On-premises IaaS / data center provider On-premises IaaS / data center provider 







 Other on-premises components outside of the IBM Cloud Satellite location 

The workload provider and on-premises IaaS / data center provider are solely responsible for edge plane, management plane, and other applications that you run in the on-premises environment outside of the Satellite location.





 Next steps 



* [Satellite architecture best practices](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-best-practices)
* [Next steps](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-deployment-setup-environmentnext-steps)



[Use deployable architectures to deploy your resources](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-deploy-infrastructure-as-codeshared-deploy-infrastructure-as-code)



* [Next steps](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-deploy-infrastructure-as-codenext-steps)







 Accounts, identity management, and access control 

[IBM Cloud account setup](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-account-setupshared-account-setup)



* [Next steps](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-account-setupnext-steps)



[Organizing IBM Cloud accounts and resources](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-account-organizationshared-account-organization)



* [Organization for a single deployment within an account](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-account-organizationsingle-deployment)



* [VPC reference architecture](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-account-organizationsingle-deployment-vpc)
* [Satellite reference architecture](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-account-organizationsingle-deployment-satellite)



* [Organization for multiple deployments](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-account-organizationmultiple-deployments)
[Common permissions in other cloud providers](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-commoniam-common)



* [AWS permissions](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-commonpermissions-aws)



* [Manually creating a Satellite location in AWS](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-commonpermissions-aws-manual)
* [Automatically creating a Satellite location from a Schematics template in AWS](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-commonpermissions-aws-auto)



* [Azure permissions](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-commonpermissions-azure)
* [Google Cloud Platform permissions](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-commonpermissions-gcp)



[Learning about Satellite architecture, workload isolation, and dependencies](https://cloud.ibm.com/docs/satellite?topic=satellite-service-architectureservice-architecture)



* [Satellite architecture](https://cloud.ibm.com/docs/satellite?topic=satellite-service-architecturearchitecture)



* [Master and worker node components](https://cloud.ibm.com/docs/satellite?topic=satellite-service-architecturearchitecture-master-worker)
* [Latency requirements](https://cloud.ibm.com/docs/satellite?topic=satellite-service-architecturearchitecture-latency)



* [Workload isolation in IBM Cloud Satellite](https://cloud.ibm.com/docs/satellite?topic=satellite-service-architectureworkload-isolation)



* [Workload isolation in the IBM Cloud multizone metro that manages your location](https://cloud.ibm.com/docs/satellite?topic=satellite-service-architectureworkload-isolation-cloud)
Learning about Netezza Performance Server architecture and workload isolation 

IBM® Netezza® Performance Server for IBM Cloud Pak® for Data as a Service uses a multi-tenant-in-a-cluster isolation model.

For Azure, the model uses a separate OpenShift namespace for each customer and each instance. For AWS, the model uses EKS (an AWS-managed Kubernetes platform) for each customer and each instance.



  Netezza Performance Server architecture 

Zoom

![Netezza Performance Server architecture](https://cloud.ibm.com/docs-content/v1/content/da65f8904a6bd1315f9f9194ca407510f517bed8/netezza/images/Netezza-Deployment-diagram.png)

Image 1. The diagram depicts the deployment model and how the workload isolation is ensured.





  Netezza Performance Server workload isolation 

Customer data and compute storage are isolated from other instances. Each provisioned instance has a seperate set of worker nodes and separate Cloud Object Storage buckets for customer data. DR Backups are also stored in a customer-specific encrypted Cloud Object Storage bucket.