vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Clone the tutorial [source code repository](https://github.com/IBM-Cloud/vpc-tutorials):

git clone https://github.com/IBM-Cloud/vpc-tutorials.git
2. Define a variable named CHECKOUT_DIR pointing to the source code directory:

cd vpc-tutorials
export CHECKOUT_DIR=$PWD
3. Change to the tutorial directory:

cd $CHECKOUT_DIR/vpc-app-deploy
4. Copy the configuration file:

cp export.template export
5. Edit the export file and set the environment variable values:



* TF_VAR_ibmcloud_api_key is an IBM Cloud API key. You can create one [from the console](https://cloud.ibm.com/iam/apikeys).
* TF_VAR_ssh_key_name is the name of the VPC SSH public key identified in the previous section. This is the public key that will be loaded into the virtual service instances to provide secure SSH access via the private key on your workstation. Use the CLI to verify it exists:

ibmcloud is keys
* TF_VAR_resource_group_name is a resource group where resources will be created. See [Creating and managing resource groups](https://cloud.ibm.com/docs/account?topic=account-rgs).
* TF_VAR_region is a region where resources will be created. This command will display the regions:

ibmcloud is regions
* TF_VAR_zone is a zone where resources will be created. This command will display the zones:

ibmcloud is zones



6. Load the variables into the environment:

source export

Make sure to always use the same terminal window in the next sections or to set the environment variables if you use a new window.
Yes, for certain versions of Red Hat Enterprise Linux (RHEL) and Windows operating systems, you can bring your own license (BYOL) to the IBM Cloud VPC when you import a custom image. These images are registered and licensed by you. You maintain control over your license and incur no additional costs by using your license. For more information, see [Bring your own license](https://cloud.ibm.com/docs/vpc?topic=vpc-byol-vpc-about).





 How does IBM handle maintenance? 

For more information, see [Understanding Cloud Maintenance Operations](https://cloud.ibm.com/docs/vpc?topic=vpc-about-cloud-maintenance).





 What happens if my virtual server host fails? 

For more information, see [Understanding Cloud Maintenance Operations](https://cloud.ibm.com/docs/vpc?topic=vpc-about-cloud-maintenance).





 What are the disks that I see associated with my new Windows virtual server instance? 

When you provision a Windows virtual server instance with a stock image, disk manager might show unexpected disks. After a new Windows instance is provisioned from a stock image, a cloud-init disk and a swap disk are present. The cloud-init disk might display a size of 378 KB. The swap disk might display a size of 44 KB; the swap disk is turned off eventually. These small disks are working as designed. You are not to attempt to delete or format either of these disks that are associated with your new Windows virtual server instance.





 What is image from volume and how does it relate to virtual server instances? 

You can create a custom image from a boot volume that is attached to a virtual server instance. Then, you can use the custom image to provision new virtual server instances. For more information, see [About creating an image from a volume](https://cloud.ibm.com/docs/vpc?topic=vpc-image-from-volume-vpc).





 What is the virtual server instance identifier and SMBIOS system-uuid?
Using the IBM Cloud console to create VPC resources 

You can create and configure an IBM Cloud® Virtual Private Cloud (VPC) by using the IBM Cloud console.



 Objectives 

To create and configure your VPC and other attached resources, do the steps in the sections that follow, in this order:



1. Create a VPC and subnet to define the network. When you create your subnet, attach a public gateway if you want to allow all resources in the subnet to communicate with the public internet.
2. To limit the subnet's inbound and outbound traffic, you can configure an access control list (ACL). By default, all traffic is allowed.
3. Create a virtual server instance. By default, a boot volume is attached to the instance. For most virtual server instances the default boot volume size is 100 GB. The default boot volume size for a z/OS virtual server instance is 250 GB.
4. If you want more storage, create a block storage volume and attach it to your instance.
5. To define the inbound and outbound traffic that is allowed for the instance, configure its security group.
6. If you want your instance to be reachable from the internet, reserve and associate a floating IP address.
7. To distribute requests over multiple instances, create a load balancer.
8. To enable your VPC to connect securely to another private network, such as your on-premises network or another VPC, create a virtual private network (VPN).



After you enter data on the provisioning pages, you can click the Get sample API call button to view the sequence of API requests that correspond to your settings. Viewing the API calls is a good way to learn about the API and understand actions and their dependencies.





 Audience 

This tutorial is intended for software developers and system administrators who are creating a VPC environment and deploying an instance for the first time.





 Before you begin 

Set up your account to access VPC.
Linking secure private networks over the IBM network 

This tutorial describes the use of Classic Infrastructure. Most workloads can be implemented using [IBM Cloud® Virtual Private Cloud](https://cloud.ibm.com/docs/vpc) resources. Use IBM Cloud VPC to create your own private cloud-like computing environment on shared public cloud 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. Specifically, [Direct Link](https://cloud.ibm.com/docs/vpc?topic=vpc-interconnectivity), [virtual server instances](https://cloud.ibm.com/docs/vpc?topic=vpc-vsi_best_practices), [security groups](https://cloud.ibm.com/docs/vpc?topic=vpc-using-security-groups), [network ACLs](https://cloud.ibm.com/docs/vpc?topic=vpc-using-acls) and [transit gateway](https://cloud.ibm.com/docs/transit-gateway).

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

As the need for global reach and 24-7 operations of web application increases, the need to host services in multiple cloud data centers increases. Data centers across multiple locations provide resilience in the case of a geographic failure and also bring workloads closer to globally distributed users reducing latency and increasing perceived performance. The [IBM Cloud network](https://www.ibm.com/cloud/data-centers/) enables users to link workloads hosted in secure private networks across data centers and locations.

This tutorial presents setup of a privately routed IP connection over the IBM Cloud private network between two secure private networks hosted in different data centers. All resources are owned by one IBM Cloud account.
For IBM Blockchain Platform cost estimation purposes, 1 VPC = 1 CPU = 1 vCPU = 1 Core. The term "VPC" is also used to refer to a type of infrastructure on IBM Cloud and is unrelated to this topic.

For a total cost estimate, remember that your blockchain network consists of an Kubernetes cluster on IBM Cloud that contains IBM Blockchain Platform components and uses storage of your choice. Your Kubernetes cluster on IBM Cloud and the storage that you choose incur separate charges. You will not be charged for the cluster that the Operational Tooling instance, also known as the console, is running on. See the [Architecture reference](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-overviewibp-console-overview-architecture) topic for an illustration. More details on how to calculate charges are described below.



 Benefits of the new pricing model 



* No membership fees: Freedom from membership fees means that you can invest directly in your blockchain components.
* Estimation clarity: A simple hourly pricing model makes cost estimation clear and easy by using the cost estimator tool that is available in the IBM Cloud dashboard.
* No minimum fee required: Pay for only what you use, no minimum VPC hourly package is required, which makes it very inexpensive to get started.
* Scalability of compute: You have the option to scale your compute up during peak usage periods or down to a minute fraction of capacity for when the compute is not needed to minimize expense.



In summary, these features remove the complexity of accounting for membership limitations or purchasing compute ahead of your needs.





 Find out how to preview the platform free for 30 days 

You can preview the IBM Blockchain Platform at no charge for 30 days when you link your IBM Blockchain Platform service instance to an IBM Cloud Kubernetes free cluster.

Limitations of the free preview



* Performance will be limited by throughput, storage, and functionality. Read more about the [limitations of free clusters](https://cloud.ibm.com/docs/containers?topic=containers-cs_ovcluster_types).
* IBM Cloud will delete your Kubernetes cluster after 30 days.
VPNs for VPC overview 

IBM Cloud has two VPN services. VPN for VPC offers site-to-site gateways, which connect your on-premises network to the IBM Cloud VPC network. Client VPN for VPC offers client-to-site servers, which allow clients on the internet to connect to VPN servers, while still maintaining secure connectivity.



 Site-to-site gateways 

IBM Cloud VPN for VPC provides a simple, yet powerful solution for highly scalable and robust site-to-site VPN gateways. With this service, you can create site-to-site VPN tunnels for secure, encrypted connectivity. Connect from on-premises sites to IBM Cloud through a VPN gateway on an IBM Cloud VPC, and a peer gateway on-premises.

This service provides a mixture of industry-standard security and encryption options as well as support for Pre-Shared Key (PSK) authentication. This service also provides the ability to quickly add and remove VPN connections with the option to use pre-defined configurations. For more information, see [About site-to-site VPN gateways](https://cloud.ibm.com/docs/vpc?topic=vpc-using-vpn).

Features include the following:



* Secure tunnels - Create a VPN in route-based or policy-based mode to set up IPsec site-to-site tunnels between your VPC and your on-premises private network, or another VPC.
* High availability - Built on two VPN devices, provides appliance-level redundancy.
* Pre-defined and custom encryption proposals - Choose from multiple pre-defined proposals for a quick, secure VPN configuration with completely customizable Internet Key Exchange (IKE) Phase 1 and Phase 2 encryption settings.
* Monitoring - View the monitoring dashboard to see the current status of all tunnels and connections. You can also suspend and restart your individual VPN connections at any time.







 Client-to-site servers 

IBM Cloud Client VPN for VPC provides an open-source compatible client-to-site VPN solution that allows users to connect to IBM Cloud resources through secure, encrypted connections.
By completing this tutorial, you learn how to create a private catalog, import the sample, validate that it can be installed on a selected deployment target, and make the virtual server image available to users who have access to your account.

Object Storage Virtual Private Cloud (VPC)

+1

Managing your account, resources, and access



* 20 minutes
* 2023-03-03



[Onboarding a virtual server image for VPC](https://cloud.ibm.com/docs/account?topic=account-catalog-vsivpc-tutorial)Onboarding a virtual server image for VPC

This tutorial walks you through how to onboard a sample virtual server image for virtual private cloud (VPC) to your account. By completing this tutorial, you learn how to create a private catalog, import the image, validate that it can be installed on a selected deployment target, and make the virtual server image available to users who have access to your account. As you complete the tutorial, adapt each step to match your organization's goal.

Object Storage Virtual Private Cloud (VPC)

+1

Managing your account, resources, and access



* 20 minutes
* 2022-08-25



[AWS, Azure, GCP, and OCI workloads to IBM Cloud VPC migration with RMM](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-migrating-images-cloud-rackware)AWS, Azure, GCP, and OCI workloads to IBM Cloud VPC migration with RMM

The RackWare Management Module (RMM) migration solution provides a seamless virtual-to-virtual replatforming from other cloud service providers (AWS, Azure, GCP, and OCI (bare metal)) to IBM Cloud® virtual server instance migration, which allows the adoption of the existing capabilities of IBM Cloud. Its intuitive GUI allows you to move the OS, application, and data from other cloud service providers to IBM Cloud VPC instances.

Virtual Private Cloud (VPC) Virtual Servers for Classic

+1

Building infrastructure



* 45 minutes
* 2022-11-23
Learn about [cloud service endpoint source addresses](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-behind-the-curtaincse-source-addresses) and how [DNS resolves shared cloud service endpoints](https://cloud.ibm.com/docs/vpc?topic=vpc-service-endpoints-for-vpcdns-domain-name-system-resolver-endpoints).







 5 November 2019 



 For all version dates 

This API release supports the following changes:



* [Load balancers](https://cloud.ibm.com/apidocs/vpclist-load-balancers) API is available as beta
* [VPN gateways](https://cloud.ibm.com/apidocs/vpclist-vpn-gateways) are available as beta
* Pagination is now supported for [instances](https://cloud.ibm.com/apidocs/vpclist-instances)
* Classic access to VPCs (also known as classic peering) is supported
* CLI
* API







 Creating VPC resources with CLI and API 

In addition to creating a VPC, you can also create VPC resources such as an instance, a subnet, and a block storage volume.

If you are looking for information to create VPC resources by using IBM Cloud console, see [Using the IBM Cloud console to create VPC resources](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-using-the-ibm-cloud-console).



 Using the CLI to create VPC resources 

You can create and configure an IBM Cloud® Virtual Private Cloud using the IBM Cloud® CLI.

To create and configure your virtual private cloud (VPC) and other attached resources, perform the steps in the sections that follow, in this order:



1. Create a VPC and subnet to define the network.
2. If you want to allow all resources in the subnet to communicate with the public internet, attach a public gateway.
3. Create a virtual server instance. By default, a boot volume is attached to the instance. For most virtual server instances the default boot volume size is 100 GB. The default boot volume size for a z/OS virtual server instance is 250 GB.
4. If you want more storage, create a block storage volume and attach it to your instance.
5. To define the inbound and outbound traffic that's allowed for the instance, configure its security group.
6. If you want your instance to be reachable from the internet, reserve and associate a floating IP address.





 Before you begin 

Make sure that you set up your CLI [environment](https://cloud.ibm.com/docs/vpc?topic=vpc-set-up-environmentcli-prerequisites-setup).





 Log in to IBM Cloud 

ibmcloud login --sso -a cloud.ibm.com

This command returns a URL and prompts for a passcode. Go to that URL in your browser and log in. If successful, you get a one-time passcode.
To find from a specified site location to IBM Cloud and which network service providers are available, use [Cloud Pathfinder for IBM Cloud](https://ibm.find.cloud) (powered by [Cloudscene](https://cloud.ibm.com/docs/cloudscene.com))







 VPC VPN Gateway 

To connect to a virtual server on VPC through a secure IPsec tunnel, a VPN Gateway is created for the VPC. For a tutorial that describes the setup of connectivity to the VPC VPN Gateway using the open source strongSwan IPSec-based VPN client on an external network, refer to the tutorial [Use a VPC/VPN gateway for secure and private on-premises access to cloud resources](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-site2site-vpn).





 IBM Cloud Direct Link 2.0 

Network back-bone infrastructure of a customer site can be directly connected to IBM Cloud, by using IBM Cloud Direct Link. On-premises resources can be connected to multiple VPCs, and VPC can provide Bring-your-own-IP or other custom IP ranges.

Technical requirements and restrictions exist in the availability of IBM Cloud Direct Link in different regions. A detailed description of IBM Cloud Direct Link can be found in [Getting started with IBM Cloud® Direct Link](https://cloud.ibm.com/docs/dl/getting-started?topic=dl-get-started-with-ibm-cloud-dl).





 Accessing the classic infrastructure 

Optional setup.

IBM Cloud VPC infrastructure can access other resources on IBM Cloud Classic Infrastructure, such as high-performance IBM Cloud® Bare Metal Servers designed for SAP HANA.

You have multiple options to achieve this access, notably a one-to-one association, or IBM Cloud® Transit Gateway with increased flexibility. This is described in the above section [Interconnectivity between IBM Cloud network](https://cloud.ibm.com/docs/sap?topic=sap-determine-accessdetermine-access-interconnectivity).

All options require upgrading the IBM Cloud account to be VRF-enabled.
The IBM Cloud Provider plug-in for Terraform on IBM Cloud uses these configuration files to install SAP NetWeaver 7.X with ASE SYB v16 on the specified VPC in your IBM Cloud account.





 Support 

There are no warranties of any kind, and there is no service or technical support available for these materials from {{site.data.keyword.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, readapt or remove the materials at any time. To report a problem, or provide suggestions or comments, open a GitHub issue.





 Before you begin 

Before you use the scripts in the Bastion cli or Schematics:



* Set up your account to access the VPC. Make sure that your account is [upgraded to a paid account](https://cloud.ibm.com/docs/account?topic=account-accountfaqschangeacct).
* If you have not already, create a Bastion server to store the SAP kits. For more information, see [Automate SAP bastion server - SAP media storage repository](https://cloud.ibm.com/docs/sap?topic=sap-sap-bastion-server).
* Download the SAP kits from the SAP Portal to your Deployment Server. Make note of the download locations. Ansible decompresses the files. For more information, see the readme file.
* [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.
* [Create or retrieve your SSH key ID](https://cloud.ibm.com/docs/ssh-keys?topic=ssh-keys-getting-started-tutorial). You need the 40-digit UUID for the SSH key, not the SSH key name.
Install the [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started).
2. Install the VPC CLI plug-in.

ibmcloud plugin install vpc-infrastructure

The VPC CLI actions use the extension is. To learn how to use the CLI commands, you can run:

ibmcloud is help
ibmcloud is help vpc-create
ibmcloud is help instance-create

To learn how to create resources by using the CLI, see [Creating VPC resources](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-vpc-resources-with-cli-and-api&interface=cli).





 Accessing CLI through the VPC API private endpoint 

To set the CLI to use the VPC API private endpoint, follow these steps:

If you need to download the IBM Cloud CLI and associated plug-ins, you must be able to access the public repository where they are located.



1. Ensure that the core IBM Cloud CLI and VPC infrastructure service plug-in are updated to the latest version:

ibmcloud update
ibmcloud plugin update vpc-infrastructure
2. To switch to API private endpoint mode, enter the following command:

ibmcloud login -a private.cloud.ibm.com

Currently, API private endpoint mode supports only us-south and us-east regions.









 API prerequisites 

Before you can use the API to create your VPC, you must get an IAM token, store the endpoint as a variable, and verify that you have access to the VPC API service.

The following examples use the us-south regional endpoint. To view additional API endpoints, see [Virtual Private Cloud API](https://cloud.ibm.com/apidocs/vpcapi-endpoint).



 Step 1: Store your API key as a variable 

Run the following command to store the API key for your account in an environment variable.
Automating SAP HANA stand-alone virtual server instance on IBM Cloud® VPC by using Terraform and Ansible 

Terraform on IBM Cloud® enables predictable and consistent provisioning of IBM Cloud VPC infrastructure resources so that you can rapidly build complex, cloud environments. IBM Cloud VPC infrastructure consists of SAP certified hardware using Intel Xeon CPUs and additional Intel technologies.

For more information about Terraform on IBM Cloud, see [Terraform on IBM Cloud getting started tutorial](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-getting-started).

To create resources with Terraform, you use Terraform configuration files that describe 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 run to create the resources. You can review the execution plan, change it, or run 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.



 What is created 

Terraform on IBM Cloud enables predictable and consistent provisioning of IBM Cloud solutions. For more information about Terraform on IBM Cloud, see Terraform on IBM Cloud getting started tutorial. Terraform is used to provision of the infrastructure components in IBM Cloud.

To automate this process, the current solution uses a Terraform script to deploy a VPC and a VSI with SAP certified storage and network configuration. The VPC contains one subnet and one security group with three rules:



* Allow all outbound traffic from the VSI
* Allow inbound DNS traffic (UDP port 53
* Allow inbound SSH traffic (TCP port 22)



During configuration you can specify an existing VPC to use, instead of creating a new VPC.

For the detailed steps about using Terraform to create only a VPC for SAP, see [Creating single-tier Virtual Private Cloud for SAP by using Terraform](https://cloud.ibm.com/docs/sap?topic=sap-create-terraform-single-tier-vpc-sap).





 Script files