vania-janet/multiturn-rag-retrieval-data huggingface dataset:
To get consistent workload performance, it's best if all clusters within the same PVDC use the same host profile type. VMware Cloud Director automatically selects and adjusts the placement of workload VMs across the clusters in the PVDC. Placement is not controlled by users with VMware Cloud Director.

A new PVDC is typically created for the following scenarios:



* Separate and isolate different types of VMware workloads. The previous guidance is to use the same host profile type for all clusters in the same PVDC. If different workloads are better suited for different host types, then separate PVDCs are required to ensure each workload runs on the correct host type.
* Run VM workload in different data centers within the region. All clusters in the same PVDC must be in the same data center. Regional high availability across data centers is achieved by creating PVDCs in separate data centers, and then deploying the virtual data center (VDC) and applications into each region. A load balancer is used to route requests to active instances of the target workload.





 Procedure to add PVDCs 



1. In the VMware Solutions console, click Resources > VMware as a Service from the left navigation pane.
2. In the VMware as a Service table, click the Cloud director sites tab, then click an instance name.
3. Click the Infrastructure tab, then click Add provider VDC +.
4. On the Add provider VDC window, specify the settings for the new PVDC.



1. Specify the PVDC name.
2. Select the PVDC location.
3. Click Next.



5. Specify the host details.



1. Specify the cluster name.
2. Select the profile storage type.
3. Select the host profile.
4. Select the host quantity.



* For NFS only storage, select a minimum of 2.
* For vSAN™ storage, select a minimum of 6.



5. Click Next.



6. Specify the attached NFS storage settings.
7.
* [Setting up service-to-service access](https://cloud.ibm.com/docs/codeengine?topic=codeengine-satellite-cesatellite-ce-authority)
* [Setting up Code Engine on Satellite](https://cloud.ibm.com/docs/codeengine?topic=codeengine-satellite-cesatellite-ce-setup)
* [Creating a project in a compute environment](https://cloud.ibm.com/docs/codeengine?topic=codeengine-satellite-cesatellite-ce-project)
* [Why doesn't my compute environment create?](https://cloud.ibm.com/docs/codeengine?topic=codeengine-satellite-cets-sat-ce-envir-create)
* [Why can't I access my app?](https://cloud.ibm.com/docs/codeengine?topic=codeengine-satellite-cets-sat-ce-app-access)







 Subscribing to event producers 

[Getting started with subscriptions](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribing-eventssubscribing-events)



* [Subscriptions for apps and app scaling](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribing-eventssubscribing-events-app-scaling)
* [Subscriptions for jobs and job run limitations](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribing-eventssubscribing-events-jobrun-limits)
* [Eventing metadata](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribing-eventssubscribing-events-cloudevents)
Single-region IBM Cloud for Financial Services reference architecture for VPC with Virtual Servers for VPC 

Now that you've seen the [high-level VPC reference architecture for IBM Cloud for Financial Services](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-about) and looked at some [VPC concepts](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-about), we will take a deeper look at some of the details of a reference architecture that uses virtual servers.

This architecture shows a deployment of the VPC that uses Virtual Servers for VPC as the primary compute.



 Architecture diagram 

Zoom

![IBM Cloud for Financial Services reference architecture for VPC with Virtual Servers for VPC](https://cloud.ibm.com/docs-content/v1/content/9ac5c38b41e0aa1cb4ccc6cc7f547751ec805221/framework-financial-services/vpc/images/vpc-single-region/vpc-single-region-consumer-intranet.svg)

Figure 1. Single-region IBM Cloud for Financial Services reference architecture for VPC with Virtual Servers for VPC





 Management VPC 



 Regions and zones 

The management VPC provides compute, storage, and network services to enable application provider administrators to monitor, operate, and maintain the environment. The intent is to completely isolate management operations from the VPC running consumer workloads.

The management VPC is distributed across three zones in one [multizone region (MZR)](https://cloud.ibm.com/docs/overview?topic=overview-locationsmzr-table). Each zone contains two subnets that are protected by different ACLs.





 Subnets for management tools 

The top subnet in each zone is part of the default security group for the VPC. And, each of those subnets contains an arbitrary number of virtual server instances that use Block Storage for VPC. These instances are where your management tools run.
The below expands on the introducton [Comparing the different SAP-certified IaaS offerings](https://cloud.ibm.com/docs/sap?topic=sap-overviewiaas-offerings-compare-summary), which summarises the benefits of each different Infrastructure option.

You are ready to define the number of host servers and size of those hosts after:



* the business has defined their requirements
* decided which SAP applications to use
* read the SAP installation documentation
* understood the various design considerations



Often your first filter of the infrastructure options will be the minimum SAPS which has been calculated using the SAP Quick Sizer, and this will primarily define the CPU performance requirements. For the official certification documents, see the [SAP Standard Application Benchmarks](https://www.sap.com/about/benchmark.html) which will help to confirm the IaaS you are choosing from IBM Cloud is the correct IaaS for your needs.

Full details of the Profiles available for each Infrastructure option available through IBM Cloud, were provided in the previous topic group which lists all the IaaS Offerings available for either SAP HANA or SAP NetWeaver (and SAP AnyDB):



* SAP HANA profiles



* [Intel Bare Metal server certified profiles for SAP HANA](https://cloud.ibm.com/docs/sap/?topic=sap-hana-iaas-offerings-profiles-intel-bm)
* [Intel Virtual Server certified profiles for SAP HANA](https://cloud.ibm.com/docs/sap/?topic=sap-hana-iaas-offerings-profiles-intel-vs-vpc)
* [IBM Power Virtual Server certified profiles for SAP HANA](https://cloud.ibm.com/docs/sap/?topic=sap-hana-iaas-offerings-profiles-power-vs)
* [VMware SDDC certified profiles for SAP HANA](https://cloud.ibm.com/docs/sap/?topic=sap-hana-iaas-offerings-profiles-vmware)



* SAP NetWeaver profiles
Zone ibmcloud is zones [List all regions](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-referencezones-list) 
 Profile ibmcloud is instances [List all virtual server instances](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-referenceinstances-list) 
 Subnet ibmcloud is subnets [List all subnets](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-referencesubnets-list) 
 Image ibmcloud is image [List all images](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-referenceimages-list) 
 Keys ibmcloud is keys [List all keys](https://cloud.ibm.com/docs/vpc?topic=vpc-infrastructure-cli-plugin-vpc-referencekeys)<br><br>If you don't have any available SSH keys, use [Create a key](https://cloud.ibm.com/docs/vpc?topic=vpc-infrastructure-cli-plugin-vpc-referencekey-create) to create one.<br><br>Note: RSA and Ed25519 are the two types of SSH keys that you can use. However, you can't use the Ed25519 SSH key type with Windows or VMware images. You can use only RSA SSH keys for these images. <br>For more information, see [Getting started with SSH keys](https://cloud.ibm.com/docs/vpc?topic=vpc-ssh-keys). 
 Placement groups ibmcloud is placement-groups [List all placement groups](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-referenceplacement-groups-list) 



Use the following commands to determine the required information for creating a new instance template.



1. List the IBM Cloud VPCs that are associated with your account.

ibmcloud is vpcs
About Terraform 

Terraform is an open source project that lets you specify your cloud infrastructure resources and services by using the high-level scripting HashiCorp Configuration Language (HCL). With HCL, you have one common language to declare the cloud resources that you want and the state that you want your resources to be in

Terraform on IBM Cloud enables predictable and consistent provisioning of IBM Cloud platform, classic infrastructure, and VPC infrastructure resources so that you can rapidly build complex, multi-tier cloud environments, and enable Infrastructure as Code (IaC).



  How does Terraform on IBM Cloud work 

Let's say you want to spin up multiple copies of your cloud environment that uses a cluster of virtual servers, a load balancer, and a database server on IBM Cloud. You could learn how to create each resource, review the API or the commands that you need, and write a bash script to spin up these components. But it's easier, faster, and more orderly to use one language to declare all your requirements, document them in a configuration file, and let Terraform on IBM Cloud do it all for you.





  How to provision Terraform on IBM Cloud and manage cloud services? 

To use Terraform on IBM Cloud, you must create a Terraform configuration file that describes the IBM Cloud resources that you need and how you want to configure them. Based on your configuration, Terraform creates an execution plan and describes the actions that need to be executed to get to the required state. You can review the execution plan, change it, or simply execute the plan. When you change your configuration, Terraform on IBM Cloud can determine what changed and create incremental execution plans that you can apply to your existing IBM Cloud resources.

The following steps show how Terraform on IBM Cloud provisions your services in IBM Cloud.



1.  You declare the IBM Cloud resources that you want in a Terraform configuration file by using HashiCorp Configuration Language (HCL). Store this configuration file in a source code repository that is version-controlled and that allows teams to collaborate, such as GitHub or GitLab.
2.  Configure the IBM Cloud Provider plug-in.
3.  Create a Terraform execution plan that summarizes all the actions that Terraform needs to run to create, update, or delete the IBM Cloud resources in your Terraform template.
4.  Apply the Terraform configuration file in IBM Cloud.
From the catalog, select Compute and choose the server type - Bare Metal Server, Virtual Server, or Virtual Server for VPC (Virtual Private Cloud). For more information, see the [Virtual servers provisioning calculator](https://www.ibm.com/cloud/virtual-servers/calculator/).





 Can I change the configuration of a virtual server? 

After you provision a virtual server, you can upgrade or downgrade your server configuration at any time. For more information, see [Reconfiguring an existing virtual server](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-reconfiguring-virtual-servers). If the item that you want to change is not available from the Device List, you can cancel and reorder or contact [IBM Cloud Sales](https://cloud.ibm.com/catalog?contactmodule) for assistance.





 How do I cancel a virtual server? 

You can cancel a virtual server at any time. Go to the [Device List](https://cloud.ibm.com/classic/devices). Click Actions for the server that you want to cancel, and select the cancel option from the menu. For more information, see [Canceling virtual servers](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-managing-virtual-serverscancel).





 Can I add disk storage to my hourly or monthly virtual server? 

You can upgrade or downgrade disk storage for any virtual server by updating your storage options in the First Disk through Fifth Disk fields in the Configuration screen of the device you want to update. For more information, see [Reconfiguring an existing virtual server](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-reconfiguring-virtual-servers).





 How many hourly virtual servers can I start? 

The number of instances that you can run depends on the maturity level of your account. By default, an account older than 45 days has a limit of 20 instances that can run on public virtual servers, dedicated virtual servers, and bare metal servers, at any time.
Architecture patterns for the vCenter Server deployment default connectivity options 

When you deploy a [VMware vCenter Server instance](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_vcenterserveroverview) in your IBM Cloud® classic infrastructure, the deployment consists of a number of network constructs and VMware® management components.

This architecture pattern gives an overview for standard private and public connectivity options for a standard deployment. This pattern also includes an overview for the standard VMware vCenter Server® components, basic cluster types, and customer topologies deployed as part of the IBM Cloud automation.



 VMware vCenter Server components overview 

When you deploy a vCenter Server instance in your IBM Cloud classic infrastructure, the deployment consists of the components that are presented in the following diagram.

Zoom

![vCenter Server deployment overview](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/arch-pattern-vcs-nsx-t-whatu-get.svg)

Figure 1. vCenter Server deployment overview

The following steps summarize a standard deployment.



1. Depending on the network preference selection, your instance is deployed with both public and private connectivity or private connectivity only.
2. Upon your selection, a vCenter Server instance can be deployed with various bare metal server hardware options. You can select an initial deployment to include one consolidated cluster or separate management and workload clusters. You can optionally deploy a gateway cluster to host Juniper® vSRX or your own routing or firewall device. The solution can be expanded after the initial deployment by adding more hosts to existing clusters, or by adding new clusters.
3. Your clusters can have multiple datastores. You can use VMware vSAN™ with local SSDs or IBM Cloud File Storage for Classic (NFS), where you can have one or more LUNs with different performance and size characteristics. You can expand the volumes as your needs grow.
4.
Fast Path of IBM Cloud Intel Bare Metal 

This page is a collection of shortcuts to the documentation sections for each offering, excluding general information that applies to all offerings, such as SAP Sizing.

Use the links in this section to quickly access relevant documents that you are already familiar with.



 Learn 

An Infrastructure-as-a-Service (IaaS) environment consists primarily of compute, storage, and network components from a specified region (such as the US) and a designated site location (also referred to as zone, which is a data center site). For more information:



* [IBM Cloud Classic Infrastructure environment introduction](https://cloud.ibm.com/docs/sap?topic=sap-classic-env-introduction)



Certified Infrastructure-as-a-Service for SAP HANA database server is available in many variations, each with different capabilities and sizes to fit many different SAP workload scenarios. For more information:



* [Infrastructure certified for SAP - Bare Metal server](https://cloud.ibm.com/docs/sap?topic=sap-iaas-offeringsiaas-intel-bm)



The following is an overview of the SAP-certified profiles with IBM Cloud Bare Metal servers for SAP HANA and SAP NetWeaver. For more information:



* [Intel Bare Metal server certified profiles for SAP HANA](https://cloud.ibm.com/docs/sap?topic=sap-hana-iaas-offerings-profiles-intel-bm)
* [Intel Bare Metal server certified profiles for SAP NetWeaver](https://cloud.ibm.com/docs/sap?topic=sap-nw-iaas-offerings-profiles-intel-bm)
* [Compute Profiles of SAP-certified Bare Metal on Classic Infrastructure](https://cloud.ibm.com/docs/sap?topic=sap-compute-os-design-considerationscompute-baremetal)



Your business and functional requirements determine the SAP solutions powered by the SAP HANA Database Server or SAP NetWeaver Application Server, and therefore determine how your applications are run in the available infrastructure. For more information:
Background for automating SAP HANA stand-alone virtual server instance on IBM Cloud® VPC 



 IBM Cloud® Virtual Private Cloud (VPC) introduction 

IBM Cloud® VPC offers the possibility to quickly provision virtual server instances for VPC with high network performance. VPC infrastructure contains a number of Infrastructure-as-a-Service (IaaS) offerings, including Virtual Servers for VPC. A VPC is a public cloud offering that an enterprise uses to establish its own private cloud-like computing environment on shared [public cloud](https://www.ibm.com/cloud/public) infrastructure. A VPC gives an enterprise the ability to define and control a virtual network that is logically isolated from all other public cloud tenants, creating a private, secure place on the public cloud.

Imagine that a cloud provider’s infrastructure is a residential apartment building with multiple families living inside. Being a public cloud tenant is akin to sharing an apartment with a few roommates. In contrast, having a VPC is like having your own private condominium. No one else has the key, and no one can enter the space without your permission.

A VPC’s logical isolation is implemented by using virtual network functions and security features that give an enterprise customer granular control over which IP addresses or applications can access particular resources. It is analogous to the “friends-only” or “public/private” controls on social media accounts used to restrict who can or can’t see your otherwise public posts.

With IBM Cloud VPC, you can use the UI, CLI, and API to quickly provision virtual server instances for VPC with high network performance. VPC infrastructure contains a number of Infrastructure-as-a-Service (IaaS) offerings, including Virtual Servers for VPC. Use the following information to understand a simple use case for planning, creating, and configuring resources for your VPC, and learn about more VPC overviews and VPC tutorials. [Getting started with Virtual Private Cloud (VPC)](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started)





 SAP HANA in IBM Cloud 

The IBM public cloud is an open, security-rich, and enterprise-ready public cloud for business.
Getting started with Virtual Private Cloud (VPC) 

With IBM Cloud® Virtual Private Cloud (VPC), you can use the UI, CLI, and API to quickly provision virtual server instances for VPC with high network performance. VPC infrastructure contains a number of Infrastructure-as-a-Service (IaaS) offerings, including Virtual Servers for VPC. Use the following information to understand a simple use case for planning, creating, and configuring resources for your VPC, and learn about additional VPC overviews and VPC tutorials.



 Before you begin 



1. Set up your account to access VPC. Make sure that your account is [upgraded to a paid account](https://cloud.ibm.com/docs/account?topic=account-accountfaqschangeacct).
2. Make sure that you have a public SSH key, which is used to connect to the virtual server instance. For example, generate an SSH key on your Linux server by running the following command:

ssh-keygen -t rsa



This command generates two files, id_rsa and id_rsa.pub. The generated public key is in the id_rsa.pub file under an .ssh directory in your home directory, for example, .../.ssh/id_rsa.pub.

For more information, see [SSH keys](https://cloud.ibm.com/docs/vpc?topic=vpc-ssh-keys).



For a complete list of prerequisites for using the API and CLI, see [Setting up your API and CLI environment](https://cloud.ibm.com/docs/vpc?topic=vpc-set-up-environment).





 Creating and configuring a VPC 

To create and configure your VPC and other attached resources:



1. Create a VPC.
2. Create subnets in one or more zones. You can create subnets in suggested prefix ranges or in your own IP ranges that you bring to IBM Cloud.
3.
Introduction to IBM Cloud VPC and Additional Application Server (AAS) to HANA and AnyDB 

You can use Terraform to automate IBM Cloud® VPC provisioning. The VPC provisioned includes virtual server instances with high network performance. The VPC infrastructure contains a number of Infrastructure-as-a-Service (IaaS) offerings, including Virtual Servers. After the VPC is provisioned, the scripts use the Ansible Playbook to install the SAP system. IBM Cloud VPC infrastructure consists of SAP certified hardware that uses Intel Xeon CPUs and additional Intel technologies.



 IBM Cloud VPC introduction 

A VPC is a public cloud offering that an enterprise uses to establish its own private cloud-like computing environment on shared [public cloud](https://www.ibm.com/cloud/public) infrastructure. VPCs give an enterprise the ability to define and control a virtual network that is logically isolated from all other public cloud tenants, creating a private, secure place on the public cloud.

Imagine that a cloud provider’s infrastructure is a residential apartment building and multiple families live inside. Being a public cloud tenant is akin to sharing an apartment with a few roommates. In contrast, having a VPC is like having your own private condominium; no one else has the key, and no one can enter the space without your permission.

A VPC’s logical isolation is implemented by using virtual network functions and security features that give an enterprise customer granular control over which IP addresses or applications can access particular resources. It is analogous to the “friends-only” or “public/private” controls on social media accounts used to restrict who can or can’t see your otherwise public posts.

With IBM Cloud VPC, you can use the UI, CLI, and API to manually provision virtual server instances for VPC with high network performance. VPC infrastructure contains a number of Infrastructure-as-a-Service (IaaS) offerings, including Virtual Servers for VPC. Use the following information to understand a simple use case for planning, creating, and configuring resources for your VPC, and learn about more VPC overviews and VPC tutorials.
* Virtual Private Clouds (VPCs) are automatically enabled for virtual routing and forwarding (VRF). To enable service endpoints for your VPC, continue to [Enabling service endpoints](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointservice-endpoint).



For example, to check if the account is VRF enabled, run the following command:

ibmcloud account show

To enable private endpoints, run the following command:

ibmcloud account update --service-endpoint-enable true





 Step 2: Disable public endpoints in the account 

To disable public endpoints, run the following command:

ibmcloud metrics-router setting update --private-api-endpoint-only TRUE





 Step 3: Check you have access to private endpoints 

After you disable public endpoints, you must configure IBM Cloud Metrics Routing within the private network.

For example, to configure IBM Cloud Metrics Routing in your account, you can provision a VPC VSI. Then, from a terminal, you can run cURL commands to create a target and a route.

For example, complete the following steps to provision a VPC VSI so that you can run cURL commands to create a target and a route in your account:

Deploying a VSI has additional costs.



1. [Generate an ssh key](https://cloud.ibm.com/docs/vpc?topic=vpc-ssh-keys).
2. [Create a VSI](https://test.cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers) in your account.
3. [Connect to the VSI](https://test.cloud.ibm.com/docs/vpc?topic=vpc-vsi_is_connecting_linux) from a terminal in your local environment.
4.