vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Typical examples include bare metal servers, virtual servers, auto scaling groups, load balancers, or non-infrastructure related services, such as Key Protect or Identity and Access Management (IAM) access policies. The resources that are supported in Terraform on IBM Cloud are defined by the IBM Cloud Provider plug-in for Terraform. 
 Terraform configuration file A Terraform configuration file defines the IBM Cloud resources that you want to create. You can configure one resource per file, or combine multiple resources in one file. Terraform configuration files can be written in HashiCorp Configuration Language (HCL) or JSON format, and are stored in a source code repository. For more information, about how to write configuration files, see [creating Terraform configurations](https://developer.hashicorp.com/terraform/language/syntax/configuration). 
 Terraform template A Terraform template includes one or a set of Terraform configuration files that combined can be used to build a specific IBM Cloud solution. For example, you might have a template that creates a multizone cluster in IBM Cloud Kubernetes Service. This cluster consists of multiple IBM Cloud resources in different zones, such as classic infrastructure virtual servers and VLANs. Templates are designed and constructed for reuse by using variables so that you can share these templates with other teams in your organization. 
 Terraform execution plan A Terraform execution plan is a summary of actions that Terraform on IBM Cloud must perform to provision, modify, or remove the IBM Cloud resources of your template.
You might need to refer to your vendors’ supported methods of replication for the tiers, depending on the software components in your architecture.

Virtual Servers for Classic Virtual Private Cloud (VPC)

+2

IBM Cloud Load Balancer,Building infrastructure



* 60 minutes
* 2021-06-25



[Architecture for a resilient infrastructure for a single availability zone](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-ref-arch-saz)Architecture for a resilient infrastructure for a single availability zone

Deploying your application across the availability zone in a multiple-zone region provides the highest resiliency, 4 9's. However, there are scenarios where deploying across the zones is not wanted, such as needing the latency to be minimal or the application is deemed not critical.

Virtual Servers for Classic Virtual Private Cloud (VPC)

+2

IBM Cloud Load Balancer,Building infrastructure



* 60 minutes
* 2022-06-22



[Enabling Auto scale for better capacity and resiliency](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-ha-auto-scale)Enabling Auto scale for better capacity and resiliency

This tutorial shows you how to set up compute (virtual server instance) Auto scale for horizontal scaling. You create an Auto scale instance template that defines the details of the virtual server instances that are created. After you define the template, you define instance groups to set the scaling policies that determine when and how many virtual server instances are added or removed. The instance group setup includes enabling the backend orchestration to add the newly created virtual server instances to the backend server pool for the cloud load balancer.

Virtual Servers for Classic Virtual Private Cloud (VPC)

+2

IBM Cloud Load Balancer,Building infrastructure



* 10 minutes
* 2021-04-20



[Regional snapshots in 3-tier architecture](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-regional-snapshots-3-tier-arch)Regional snapshots in 3-tier architecture

Block storage snapshots can be created in IBM Cloud® VPC Gen2.
You can use VMs for most general-purpose use cases such as testing and development environments, staging, and prod environments, microservices, and business apps. However, there is a tradeoff in performance. If you need high-performance computing for data- or RAM-intensive workloads, consider creating classic clusters with [bare metal](https://cloud.ibm.com/docs/containers?topic=containers-planning_worker_nodesbm) worker nodes.



 Planning considerations for VMs 



 Do I want to use shared or dedicated hardware? 

When you create a standard classic cluster, you must choose whether you want the underlying hardware to be shared by multiple IBM customers (multi tenancy) or to be dedicated to you only (single tenancy). VPC standard clusters can be provisioned on shared infrastructure (multi tenancy) only.

When you create a standard cluster, you must choose whether you want the underlying hardware to be shared by multiple IBM customers (multi tenancy) or to be dedicated to you only (single tenancy).



* In a multi-tenant, shared hardware setup: Physical resources, such as CPU and memory, are shared across all virtual machines that are deployed to the same physical hardware. To ensure that every virtual machine can run independently, a virtual machine monitor, also referred to as the hypervisor, segments the physical resources into isolated entities and allocates them as dedicated resources to a virtual machine (hypervisor isolation).
* In a single-tenant, dedicated hardware setup: All physical resources are dedicated to you only. You can deploy multiple worker nodes as virtual machines on the same physical host. Similar to the multi-tenant setup, the hypervisor assures that every worker node gets its share of the available physical resources.



Shared nodes are usually less costly than dedicated nodes because the costs for the underlying hardware are shared among multiple customers. However, when you decide between shared and dedicated nodes, you might want to check with your legal department to discuss the level of infrastructure isolation and compliance that your app environment requires.

Some classic worker node flavors are available for only one type of tenancy setup. For example, m3c VMs can be provisioned in a shared tenancy setup only.





 How does bandwidth allocation work for VPC Gen 2 worker nodes?
Image ibmcloud is image [List all images](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-referenceimages-list) 
 Boot volume ibmcloud is volumes [List all volumes](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-referencevolumes-list) 
 Profile ibmcloud is instances [List all virtual server instances](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-referenceinstances-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). 
 VPC ibmcloud is vpcs [List all VPCs](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-referencevpcs-list) 
 Subnet ibmcloud is subnets [List all subnets](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-referencesubnets-list) 
 Zone ibmcloud is zones [List all regions](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-referencezones-list)
Considerations for HPC cluster compute types 

HPC workloads have varying requirements in terms of CPU, memory, network, and storage resource requirements.

You start with the following:



* core count
* memory per core
* network bandwidth and latency
* processor clock speed



The goal is to pick a compute configuration that returns the best price performance. An HPC workload can be as simple as a single core job or as complex as a job that needs hundreds to thousands of cores. HPC aggregates computing power (clustering) and can deliver much higher performance and solve large problems.

Most of HPC workloads fall below the 1000 core range. There are some workloads that require a high number of cores up to and including 10k-50k. Execution time for an HPC workload can be simple and last only a few seconds, or it can be complex and take several days.

As an example, EDA (Electronic Design Simulation) workloads have component level simulation jobs that require millions of such jobs ran every day, but each single job requires a single core and approximately 10 seconds. Others such as Optical Proximity Correction can take multiple hours or even days depending on the size of the chip and the size of the HPC cluster.

Typically HPC clusters contain a set of virtual machines and use the cluster to run multiple workloads. It all depends on the workload resource requirements and duration.

To address this range of characteristics, IBM Cloud® provides various VPC virtual machine (VM) configurations in different modes:



* Balanced configurations that provide average 4 GB memory per core and can range 4 - 64 Gbps in network bandwidth
* Compute-intensive configurations that provide 2 GB memory per core and a network of 4 - 80 Gbps
* Memory-intensive configurations that provide 8 - 28 GB memory per core and a network of 2 - 80 Gbps



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

For all of the configurations, the range of core count is 2 - 128 per virtual machine. There is a special ultra high memory virtual machine type that might be applicable for workloads that require more memory per core.
Reference architecture overview 

The IBM Cloud Framework for Financial Services provides three reference architectures that can be used as a basis for meeting the security and regulatory requirements that are defined in the framework. Learn about these reference architectures in the following table.



Table 1. Reference architectures for the IBM Cloud for Financial Services

 Reference architecture Description 

 [IBM Cloud® Virtual Private Cloud (VPC)](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-about) Built by using [IBM Cloud® Virtual Private Cloud](https://cloud.ibm.com/docs/vpc?topic=vpc-about-vpcabout-vpc), which enables an enterprise to establish its own private cloud-like computing environment on shared public cloud infrastructure. The architecture has options for using one or both of [IBM Cloud® Virtual Servers for Virtual Private Cloud](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-detailed-vsi) and [Red Hat® OpenShift® on IBM Cloud®](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-detailed-openshift) 
 [IBM Cloud Satellite®](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-about) Built by using [IBM Cloud Satellite](https://cloud.ibm.com/docs/satellite), so you can create a hybrid environment that brings the scalability and on-demand flexibility of public cloud services to the applications and data that run in your secure private cloud (such as on-premises).
Hosting type A Public virtual server instance, created in a multi-tenant environment, is the default selection for a new instance. You can also select a Dedicated virtual server instance to create the instance in a single-tenant space. To provision a dedicated instance, you must have a dedicated host available or [create one](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-dedicated-hosts-instances). z/OS virtual server instances do not support the dedicated type. 
 Location Locations are composed of regions (specific geographic areas) and zones (fault tolerant data centers within a region). Select the geography, region, and zone where you want your virtual server instance to be created. 
 Name A name is required for your virtual server instance. 
 Resource group Select a resource group for the instance. 
 Operating system Select a a stock image, a custom image from your account, or a custom image that was shared with your account from a private catalog. For more information about stock images, see [x86 virtual server images](https://cloud.ibm.com/docs/vpc?topic=vpc-about-images&interface=ui).<br><br><br><br> * A Custom image is an image that you create externally and import to IBM Cloud®, which you can then import into IBM Cloud VPC.<br> * A Catalog image is a custom image that is imported into a private catalog. <br> For more information about catalog images, see [Custom images in a private catalog](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images&interface=uicustom-image-cloud-private-catalog). <br> Note If you select a catalog image that belongs to a different account, there are additional considerations and limitations to review. See [Using cross-account image references in a private catalog in the UI](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images&interface=uiprivate-catalog-image-reference-vpc-ui).
Commonly this is paired with existing IBM Power or IBM Z infrastructure in on-premises data centers, to create a Hybrid Cloud model which drives modernization using paired capabilities from either on-premises or Cloud that address the business needs (e.g. security, flexibility, speed etc.) and business strategy
* VMware is a Type 2 hypervisor. This option has a minor reduction in the available performance. But this option also has vastly more flexibility and optimization in running SAP workloads, including:
* Full root-access control to all VMware features
* Capability to install more software that uses VMware capabilities (for example, SAP Landscape Management)
* Ability to bridge the network with any existing VMware installations



This content is a high-level summary, for more details please see [Infrastructure certified for SAP](https://cloud.ibm.com/docs/sap?topic=sap-iaas-offerings); in addition there are multiple pages describing each profile available across the infrastructure options, or a compilation list of all profiles available is provided in the [FAQ of Profile List with Benchmarks and Specifications](https://cloud.ibm.com/docs/sap?topic=sap-faq-profile-specs).

Our recommendation is to investigate what your current business requirements are and what are your future requirements for growth. This information helps you understand the short-term and long-term needs for running your SAP Systems. After you know your short-term and long-term needs, complete an SAP Sizing exercise.

This exercise provides you enough information to establish what IaaS and surrounding needs you might have, which can help to evaluate decision points such as:



* Whether to move the existing SAP workload to cloud quickly or steadily (for example, avoid data center expiry fees versus potential business disruption)
* Whether to migrate the existing SAP ECC system to SAP S/4HANA, or build from the ground up on cloud
* What your current sizing of your SAP Systems are, and their projected increases
* How to align your move to cloud and SAP rollouts to meet business needs. For example, connectivity to existing applications in on-premises data centers, intermittent or offline locations such as factories or front-line business operators, mobile device connectivity while retaining security and more.
[IBM Cloud Bare Metal Servers for Virtual Private Cloud](https://cloud.ibm.com/docs/vpc?topic=vpc-about-bare-metal-servers) environment provide a new option to deploy VMware on IBM Cloud. Currently the IBM Cloud VPC environment provides only the automated vSphere Hypervisor (ESXi) Operating System image deployment to Intel Bare Metals on VPC. Therefore, you need to manually install and configure the required VMware components, such as ESXi hosts, vCenter, vSAN or NSX-T components.

This tutorial walks you through creating your own IBM Cloud VPC with multiple subnets as required to support vSphere networking and the provisioning of IBM Cloud Bare Metal Servers for Virtual Private Cloud (BMS) for a basic VMware vSphere deployment. After the IBM Cloud VPC and Bare Metal Servers for VPC have been provisioned, the tutorial covers a manual deployment of the vCenter, creating VMware compute cluster with vSAN or NFS shared storage options. The tutorial also covers optional features, such as using IBM Cloud VPC network for VMware Virtual Machine networking.

This tutorial assumes a working knowledge of VMware vSphere Hypervisor and vCenter Server 7.0 as well as IBM Cloud zones, regions, prefixes, subnets and security groups that build the base IBM Cloud VPC networking and are used to support the vSphere deployment. More information about VMware products can be found in [VMware Docs](https://docs.vmware.com). IBM Cloud VPC concepts and the networking constructs are explained in the [VPC pages of the IBM Cloud™ Docs](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started). More information about planning and deploying bare metal servers on VPC can be found in the [Bare metal server section of IBM Cloud VPC pages](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-for-bare-metal-servers).



 Objectives 



* Understand the Virtual Private Cloud infrastructure used for VMware vSphere deployment.
You will find instructions to download and install these tools for your operating environment in the [Getting started with tutorials](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-tutorials) guide.

To avoid the installation of these tools you can use the [Cloud Shell](https://cloud.ibm.com/shell) from the IBM Cloud console.

With ibmcloud and its plugins, you can automate the creation and configuration of your cloud resources. Virtual Servers, Kubernetes clusters, Cloud Functions, Code Engine, and services, you can provision all of them from the command line.

Terraform enables you to safely and predictably create, change, and improve infrastructure. It is an open source tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned. It is infrastructure as code. You write down what your infrastructure should look like and Terraform will create, update, remove cloud resources as needed.

To support a multi-cloud approach, Terraform works with providers. A provider is responsible for understanding API interactions and exposing resources. IBM Cloud has [its provider for Terraform](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs), enabling users of IBM Cloud to manage resources with Terraform. Although Terraform is categorized as infrastructure as code, it is not limited to Infrastructure-As-A-Service resources. The IBM Cloud Provider for Terraform supports IaaS (bare metal, virtual machine, network services, etc.), CaaS (Kubernetes Service and Kubernetes clusters), PaaS services, and serverless (Cloud Functions and Code Engine) resources.





 Step 2: Write scripts to automate the deployment 

As you start describing your infrastructure-as-code, it is critical to treat files you create as regular code. Thus, store them in a source control management system. Over time this will bring benefits such as using the source control review workflow to validate changes and continuous integration to automatically deploy infrastructure changes.
* How to



* Setting up your IBM Cloud environment



* [Design the structure of your environment](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-bpimplementation)
* [Determining your organization architecture](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-orgstructure)
* [Determine your spaces](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-determinespaces)
* [Managing Cloud Foundry access](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-mngcf)



* Creating and deploying apps



* [Creating Cloud Foundry apps](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-creating_cloud_foundry_apps)
* [Deploying apps](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-deployingapps)
* [Hosting apps in IBM Cloud](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-hosting_apps)
* [Managing connections](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-connect_app)
* [Developing with Visual Studio](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-starter-vs)
* [Download, modify, and redeploy your Cloud Foundry app with the command-line interface](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-cf-deploy-cli)
* [Creating apps with the Node-RED Starter](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-gettingstarted-nodered)
* [Deploying critical applications with IBM Cloud MZR](https://cloud.ibm.com/docs/ha-infrastructure?topic=ha-infrastructure-multi-zone-resiliency) using the IBM Cloud console.
* Configuration and script files for 3-tier applications are available on the [vpc-ha-iac GitHub repository](https://github.com/IBM-Cloud/vpc-ha-iac).
* [Creating a resilient three-tier highly available infrastructure VPC with Terraform](https://cloud.ibm.com/docs/ha-infrastructure?topic=ha-infrastructure-create-three-tier-resilient-vpc).
* [Creating a resilient three-tier highly available infrastructure VPC with Autoscale by using Terraform](https://cloud.ibm.com/docs/ha-infrastructure?topic=ha-infrastructure-create-three-tier-resilient-vpc-autoscale).
VMware Hybrid Cloud migrations 

After the VMware HCX™ Service Mesh and Network Extensions are provisioned and extended, the next step is the migration of virtual machines (VMs).

The following migration types exist:



* vMotion
* Bulk Migration
* Cold Migration





 Operation 

Use the HCX web UI snap-in portal or the vSphere Web Client contextual extension menus to initiate a cross cloud vMotion. In either case, the same migration wizard comes up. For the contextual menus, only a single VM is selected for migration operations. For the portal, multiple VMs can be selected.

Reverse migrating VMs is only possible from the web UI portal that uses the Reverse migration checkbox in the HCX Migration wizard.





 vMotion 

The vMotion capability within HCX extends the vSphere vMotion capability to work across differing versions of vSphere, separate SSO domains, and various types of network connectivity across the internet. HCX assumes that the network used to connect across is not secure and it always moves traffic through encrypted tunnels regardless of the type of connectivity.



 Concepts and best practices for vMotion 

HCX is essentially a vMotion two-way proxy. Each instance of HCX emulates a single VMware ESXi™ host within the vSphere data center, outside any clusters. The HCX instance is a “front” for the cloud gateway fleet component (CGW). A proxy host appears for each HCX site that is linked to the currently viewed site. When a vMotion is initiated to a remote host, the local ESXi host migrates that VM to the local proxy ESXi host.

A vMotion migration is initiated from the remote ESXi proxy host to the destination vSphere physical ESXi host, while it receives data from the source CGW across the tunnel. When vMotion is employed, unlike the bulk migration option, only a single VM migration operation runs at a time. As a result, for many VMs to be migrated, it is recommended to use vMotion only when downtime is not an option or if a risk in rebooting the VM exists.