vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Overview for automating SAP workload HA deployment on IBM Cloud® Virtual Private Cloud (VPC) with Terraform and Ansible 

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 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) 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. For more information about VPC, see [Getting started with Virtual Private Cloud (VPC)](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started).
Automating SAP workload deployment on IBM Cloud® Virtual Private Cloud (VPC) with Terraform and Ansible 

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 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. For more information about VPC, see [Getting started with Virtual Private Cloud (VPC)](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started).
Automating SAP workload deployment on IBM Cloud® Virtual Private Cloud (VPC) with Terraform and Ansible 

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 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. For more information about VPC, see [Getting started with Virtual Private Cloud (VPC)](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started).
SAP app virtual server instance disks: * 1x 40 GB disk with 10 IOPS / GB - SWAP * 1 x 128 GB disk with 10 IOPS / GB – DATA * 1 floating IP address that you use to access your VPC virtual server instance over the public network





 Support 

There are no warranties of any kind, and there is no service or technical support available for these materials from IBM®. As a recommended practice, review carefully any materials that you download from this site before using them on a live system.

Though the materials provided herein are not supported by the IBM Service organization, your comments are welcomed by the developers, who reserve the right to revise, re-adapt or remove the materials at any time. To report a problem, or provide suggestions or comments, open a GitHub issue.





 Before you begin 



1. If you do not have Terraform installed, [Install the Terraform CLI and the IBM Cloud Provider plug-in](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-setup_cli).

If you are using Terraform 0.13 and higher, you do not need to install the IBM Cloud Provider Plug-in. You modify the configuration files provided on the 1-Tier VPC for SAP GitHub repository to specify the plug-in version to use.

If you are using Terraform 1.12.x and earlier, follow these IBM Cloud Provider Plug-in [installation instructions](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-setup_cliinstall-provider-v12). Do not configure the plug-in.

Do not do any IBM Cloud Provider Plug-in configuration because those files are provided for you.
2. [Create or retrieve an IBM Cloud API key](https://cloud.ibm.com/docs/account?topic=account-userapikeycreate_user_key). The API key is used to authenticate with the IBM Cloud platform and to determine your permissions for IBM Cloud services.
3.
Creating a cluster in your Virtual Private Cloud (VPC) 

Create an IBM Cloud® Kubernetes Service cluster in your Virtual Private Cloud (VPC).

With IBM Cloud Kubernetes Service clusters on VPC, you can create your cluster in the next generation of the IBM Cloud platform, in your [Virtual Private Cloud](https://cloud.ibm.com/docs/vpc?topic=vpc-about-vpc). VPC gives you the security of a private cloud environment with the dynamic scalability of a public cloud. VPC uses the next version of IBM Cloud Kubernetes Service [infrastructure providers](https://cloud.ibm.com/docs/containers?topic=containers-infrastructure_providersinfrastructure_providers), with a select group of v2 API, CLI, and console functionality. You can create only standard clusters for VPC.



 Objectives 

In the tutorial lessons, you create an IBM Cloud Kubernetes Service cluster in a Virtual Private Cloud (VPC). Then, you deploy an app and expose the app publicly by using a load balancer.





 Audience 

This tutorial is for administrators who are creating a cluster in IBM Cloud Kubernetes Service in VPC for the first time.





 Prerequisites 

Complete the following prerequisite steps to set up permissions and the command-line environment.

Permissions
: If you are the account owner, you already have the required permissions to create a cluster and can continue to the next step. Otherwise, ask the account owner to [set up the API key and assign you the minimum user permissions in IBM Cloud IAM](https://cloud.ibm.com/docs/openshift?topic=openshift-access_referencecluster_create_permissions).

Command-line tools
: For quick access to your resources from the command line, try the [IBM Cloud Shell](https://cloud.ibm.com/shell). Otherwise, set up your local command-line environment by completing the following steps.



1.
Privately connecting to IBM Cloud services 

An increased focus on security is required by customers that use cloud-based services for production workloads. For many customers, accessing services in a secure manner is not only a sensible corporate policy, but in some cases required by compliance regulations. IBM® has enhanced the connectivity options for customers who require isolated connectivity options for their workloads by providing the options of virtual private endpoints (VPE) for Virtual Private Cloud (VPC) and IBM Cloud® service endpoints.

To interact with the product APIs, you can use public endpoints, VPE for VPC, or service endpoints.



* Public endpoints: You can connect to resources in all regions in your account over the IBM Cloud public network.
* VPE for VPC: After you create private endpoints in your VPC, you can connect by using a private IP address that's accessible only from your VPC. This option is available for VPC users.
* Service endpoints: After you enable virtual routing and forwarding (VRF) and turn on service endpoints for your account, you can connect by using a private IP address that's accessible only through the IBM Cloud private network. This option is available for classic infrastructure users.



By using VPE for VPC or service endpoints, you can privately connect to IBM Cloud platform services and service products in the catalog that support this type of private connectivity.

Go to the [API docs](https://cloud.ibm.com/docs?tab=api-docs) for the service that you want to connect to and see the Endpoint URLs section to view the endpoints for that service.



 Virtual private endpoints for VPC 

VPE for VPC provides private connectivity to select IBM Cloud services originating from the VPC network of your choosing, without traversing the public backbone. All connectivity is contained within IBM Cloud. By using a service that supports VPE for VPC, you can connect to the service from your VPC network by assigning the IP address of your choosing, which is allocated from a subnet within your VPC.

VPEs are virtual IP interfaces that are bound to an endpoint gateway created on a per service or service instance basis, depending on the service operation model.
Introduction to IBM Cloud VPC and SAP on IBM Cloud for SAP NetWeaver 7.x and ASE SYB 

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.
See the list of [required permissions](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-user-permissions-for-vpc-resources) for VPC.
* Understand the capability differences between VMware and VPC infrastructures (the following list is not exhaustive):



* VPC does not support shared volumes or file-based volumes
* GPU is not supported in VPC
* Encrypted volumes are not supported





To improve data transfer rate, adjust the bandwidth allocation of the RMM server. For more information, see [Adjusting bandwidth allocation using the UI](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-virtual-server-instances&interface=uiadjusting-bandwidth-allocation-ui).





 Step 1: Order RMM 

The RMM tool is available in the IBM Cloud catalog. After you order, a virtual server with RMM software is installed into your VPC of choice. The RMM server has a public IP address for reachability and a default login.



1. Order the RMM server from the [IBM Cloud catalog](https://cloud.ibm.com/catalog/content/IBM-MarketPlace-P2P-1.3-22935832-bd76-49ab-b53e-12fc5d04c266-global).
2. After you order, log in to the RMM server.
3. In the RMM server, change the default password, create users, and create an SSH key.
4. Upload the SSH key to IBM Cloud VPC.







 Step 2: Bring Your Own License (BYOL) from RackWare 



1. Generate a license file in /etc/rackware by running the following command:

rwadm relicense
2. You need to purchase the license from RackWare by emailing the generated license file to [licensing@rackwareinc.com](mailto:licensing@rackwareinc.com) or [sales@rackwareinc.com](mailto:sales@rackwareinc.com).
With IBM Cloud Kubernetes Service, you can create a standard cluster in a [Virtual Private Cloud (VPC)](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started). A VPC gives you the security of a private cloud environment with the dynamic scalability of a public cloud.

Before you can create a VPC cluster, you must have a VPC and at least one VPC subnet that you provision by using the IBM Cloud console, CLI, or API. You manage these resources in the VPC dashboard directly. When you create your cluster, worker nodes are automatically provisioned as [Virtual Servers for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-about-advanced-virtual-servers) instances and you can view and manage these instances in IBM Cloud Kubernetes Service only.

To add persistent storage to your VPC cluster, you can use the [Block Storage for VPC add-on](https://cloud.ibm.com/docs/containers?topic=containers-vpc-block). The add-on sets up pre-defined Kubernetes storage classes, the storage provider, and the storage driver in your cluster so that you can provision Block Storage for VPC by using Kubernetes persistent volume claims (PVCs).

To secure your cluster network traffic, you can modify the default security group for your worker nodes. For more information, see [Security in your IBM Cloud VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-security-in-your-vpc).

To connect to a different VPC or to an on-prem data center, use the [VPN for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-vpn-onprem-example) service.







 Kubernetes community and open source integrations 

Because you own the standard clusters that you create in IBM Cloud Kubernetes Service, you can choose to install third-party solutions to add extra capabilities to your cluster.
For more information, see [GPU profiles](https://test.cloud.ibm.com/docs/vpc?topic=vpc-profiles&interface=uigpu). To request access to this profile, you must open a [support case](https://cloud.ibm.com/unifiedsupport/supportcenter).







 April 2023 





 27 April 2023 

Documentation enhancement: Deploying an application for financial transactions with Confidential Computing on Hyper Protect Virtual Server for VPC
: The newly added [Deploying an application on Hyper Protect Virtual Server for VPC tutorial](https://cloud.ibm.com/docs/vpc?topic=vpc-financial-transaction-confidential-computing-on-hyper-protect-virtual-server-for-vpc) walks you through how to deploy the PayNow application with Confidential Computing on Hyper Protect Virtual Server for VPC.

UI update to enable deletion of nested resources
: When you delete a resource, such as a VPC or a subnet, any attached resources must be deleted first before you can delete the VPC. The UI is updated to display a side panel listing all the resources that are still attached to the VPC that must be deleted. You can delete these resources from this side panel and then continue with deleting the VPC.

Export custom images (GA)
: The ability to export custom images to IBM Cloud Object Storage, a feature previously available in beta, is now generally available. For more information, see [Exporting a custom image to IBM Cloud Object Storage](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-custom-images&interface=uicustom-image-export-to-cos).



 6 April 2023 

Image lifecycle management for custom images (beta)
: For customers with special access to this feature, you can use the UI, CLI, and API to manage the lifecycle of your custom images with the following three statuses. You can move the image back and forth through all the statuses. You can also schedule status changes to manage the entire lifecycle of the image.
Provisioning an IBM Cloud virtual server for VPC 

Use IBM Cloud Provider plug-in to provision a VPC, and set up networking for your VPC, and provision a virtual server for VPC in your IBM Cloud account. A VPC allows you to create your own space in IBM Cloud so that you can run an isolated environment in the public cloud with custom network policies.



 Objectives 

In this tutorial, you will learn to provisions:



* 1 VPC where you provision your VPC virtual server instance
* 1 security group and a rule for this security group to allow SSH connection to your virtual server instance
* 1 subnet to enable networking in your VPC
* 1 VPC virtual server instance
* 1 floating IP address that you use to access your VPC virtual server instance over the public network



Keep in mind that a VPC virtual server instance is an IBM Cloud VPC infrastructure resource that incurs costs. Be sure to review the [available plans](https://cloud.ibm.com/vpc/provision/vs) before you proceed.





 Audience 

This tutorial is intended for system administrators who want to learn how to provision an IBM Cloud virtual server for a VPC by using IBM Cloud Provider.





 Prerequisites 



* Install the [latest Terraform on IBM Cloud](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-setup_clitf_installation) and the latest [IBM Cloud Provider plug-in for Terraform on IBM Cloud](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-setup_cliinstall_provider).
* Retrieve your [IBM Cloud credentials, upload an SSH key, and configure the IBM Cloud Provider plug-in](https://cloud.ibm.com/docs/ssh-keys?topic=ssh-keys-getting-started-tutorialgetting-started-tutorial).







 Step 1: Create the Terraform configuration files 



1.
Use a VPC/VPN gateway for secure and private on-premises access to cloud resources 

This tutorial will incur costs. Use the [Cost Estimator](https://cloud.ibm.com/estimator/review) to generate a cost estimate based on your projected usage.

IBM offers a number of ways to securely extend an on-premises computer network with resources in the IBM Cloud. This allows you to benefit from the elasticity of provisioning cloud resources when you need them and removing them when no longer required. Moreover, you can easily and securely connect your on-premises capabilities to the IBM Cloud services.

This tutorial provides the automation to create resources that demonstrate Virtual Private Network (VPN) connectivity between on-premises servers and cloud resources like IBM Cloud® Virtual Private Cloud Virtual Service Instances (VSIs) and IBM Cloud data services. DNS resolution to cloud resources is also configured. The popular [strongSwan](https://www.strongswan.org/) VPN Gateway is used to represent the on-premises VPN gateway.



 Objectives 



* Access a virtual private cloud (VPC) environment from an on-premises data center
* Securely reach cloud services using private endpoint gateways
* Use DNS on-premises to access cloud resources over VPN



The following diagram shows the resources created by this tutorial

Zoom

![Architecture](https://cloud.ibm.com/docs-content/v1/content/f84e2238288b7f0355715a4c355609ce7ac48fb0/solution-tutorials/images/solution46-vpc-vpn/vpc-site2site-vpn-tutorial.png)

Figure 1. Architecture diagram of the tutorial

A terraform configuration will create the following resources:



1. The infrastructure (VPC, Subnets, Security Groups with rules, Network ACL and VSIs).
2. The Object Storage and Databases for PostgreSQL private endpoint gateways to data services.
3. The strongSwan open source IPsec gateway software is used on-premises to establish the VPN connection with the cloud environment.