vania-janet/multiturn-rag-retrieval-data huggingface dataset:
See [available profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-profiles) and [pricing](https://www.ibm.com/cloud/vpc/pricing).

cell_ihs_setup_vsi
: When set to true, sets up the IBM HTTP Server VSI in a WAS.Cell topology. The default is true. Only applicable when deploy_was_topology is WAS.Cell.

cell_ihs_vsi_profile
: The instance profile for the IBM HTTP Server VSI in a WAS.Cell topology. The default is cx2-2x4. See [available profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-profiles) and [pricing](https://www.ibm.com/cloud/vpc/pricing). Only applicable when deploy_was_topology is WAS.Cell.

cell_node_count
: The number of custom nodes you want to provision for WAS.Cell, which must be between 1 and 20 (inclusive). This parameter is ignored for WAS.Base."

cell_node_vsi_profile
: The instance profile for custom node VSIs in a WAS.Cell topology. The default is cx2-2x4. See [available profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-profiles) and [pricing](https://www.ibm.com/cloud/vpc/pricing). Only applicable when deploy_was_topology is WAS.Cell.

vsi_os_admin_name
: The VSI Administrator username that is used to log in to VSI. The value must be 1-30 characters long and must only contain letters and numbers. The value must not contain virtuser or wsadmin. The default is virtuser.

vsi_websphere_admin_name
: The WebSphere Administrator username that is used to log in to administrative console and VSI. The value must be 1-30 characters long and must only contain letters and numbers.
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.

The tutorial includes steps for deploying a virtual server image to a target IBM Cloud Virtual Private Cloud (VPC). As a result, you incur associated infrastructure charges.



 Before you begin 



1. Verify that you're using a Pay-As-You-Go or Subscription account. See [Viewing your account type](https://cloud.ibm.com/docs/account?topic=account-account_settingsview-acct-type) for more details.
2. Virtual server images for VPC must first be imported and validated in your VPC. If your virtual server image is already imported and validated in your VPC, you can skip these steps:



1. Create your [VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started).
2. Create an instance of [IBM Cloud Object Storage](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-getting-started-cloud-object-storage) and upload your image to a bucket.
3. [Import and validate](https://cloud.ibm.com/docs/vpc?topic=vpc-importing-custom-images-vpc&interface=ui) your custom image in your VPC. Do this for each region in which you want your software to be available and verify that the SHA or checksum matches for the imported image in each region.



3. Make sure you're assigned the IBM Cloud Identity and Access Management (IAM) editor role or higher on the catalog management service.
FAQs for VPC 



 Can I connect my VPC to my other IBM Cloud workloads? 

Yes, you can set up access to your IBM Cloud® classic infrastructure from one VPC in each region. For more information, see [Setting up access to classic infrastructure](https://cloud.ibm.com/docs/vpc?topic=vpc-setting-up-access-to-classic-infrastructure).





 Can a subnet's size be changed after it is created? 

No, a subnet cannot be resized after it is created.





 What is the limit on the number of characters in a VPC name? 

Currently, the limit is 100. If this limit is exceeded, you might receive an "internal error" message.





 Can any of my VPC resource names begin with a number? 

No, although the name can contain numbers, it must begin with a letter.





 Are there restrictions on what characters that I can use in a name? 

Yes, the UI blocks consecutive double dashes, underscores, and periods from being part of a virtual server instance name.





 During the public gateway creation, do I need to reserve the floating IP address, or does the system automatically reserve it? Can I see that floating IP address when I query all of the floating IP addresses? 

The VPC API automatically creates a floating IP along with the public gateway if an existing floating IP is not specified. And yes, that floating IP shows up in the list.





 Who enforces that only one public gateway can exist per zone for a VPC? 

The VPC API service enforces this limit.





 Does the VPC public gateway have a timeout function? 

Yes, the VPC public gateway has a fixed, 4-minute timeout for TCP connections, and it is not configurable.





 How do you obtain the Cloud Resource Name (CRN) of a VPC? 

To obtain the CRN of a VPC, click menu!
Verify the VPC your created earlier, resource groups and the location, and the zone.



4. Set the Image to Ubuntu Linux and pick any version of the image.
5. Select Memory with 2vCPUs and 16 GB RAM as your profile. To check other available profiles, click View all profiles.
6. Under SSH keys, select the SSH key that you created earlier.
7. Under Networking, select the VPC you created.
8. Under Network interfaces, click the Edit icon for Security Groups.



1. Select subnet-app as the subnet.
2. Clear the default security group and check app-sg.
3. Click Save.



9. Click Create virtual server instance.
10. Repeat steps 1-8 to provision the others virtual server instances.
11. Install the necessary packages to support your application server such as tomcat.



Use this task to provision virtual server instances for db:



1. Go to Subnets.
2. Verify that the subnet-db status is available.
3. Click subnet-db.
4. Click Attached resources.
5. In Attached instances, click Create.



1. Enter db-vsi1 as your virtual server's unique name.
2. Verify the VPC your created earlier, resource group and the location, and the zone.



6. Set the Image to Ubuntu Linux and pick any version of the image.
7. Select Balanced with 4vCPUs 16 GB RAM as your profile or change to a different balanced profile that is more suitable for your application.
8. Under SSH keys, select the SSH key that you created earlier.
9. Leave Add to instance placement group cleared.
10. Under Data Volumes, click Create to add more volumes.



1. These volumes are block volumes, so choose the appropriate size and IOPs that meet your db requirements.
2. Create as many volumes as needed.



11. Under Networking select the VPC that you created.
12.
Configure routing for IBM Cloud VPC and NSX-T Logical Routers 

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.

This tutorial is part of [series](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmwarevpc-bm-vmware-objectives), and requires that you have completed the related tutorials in the presented order.

In this tutorial, a Bare Metal Servers for VPC VLAN interfaces will be created for your NSX-T Tier 0 logical router external uplinks. Tier 0 logical router or Gateway will be connected to one or more the IBM Cloud VPC subnets. When the interfaces are created, IP routing is configured between IBM Cloud VPC and the NSX-T overlay networks. This phase is optional, if you plan to use NSX-T for your Virtual Machine networking.



 Objectives 

You will first create Bare Metal Servers for VPC VLAN interfaces for your NSX-T Tier 0 logical router (or also known as T0 gateway) external interfaces (or also called as uplinks). These interfaces will be attached to two IBM Cloud VPC subnets. These IP addresses will be used as next-hops for IP routing. Static routes will be configured - first in NSX-T T0 gateway and then in IBM Cloud VPC.

Zoom

![NSX-T based VMware Solution in IBM Cloud VPC](https://cloud.ibm.com/docs-content/v1/content/f84e2238288b7f0355715a4c355609ce7ac48fb0/solution-tutorials/images/solution63-ryo-vmware-on-vpc/vpc-ryo-diagrams-nsx-t-vpc-routing.svg)

Figure 1. NSX-T based VMware Solution in IBM Cloud VPC





 Before you begin 

This tutorial requires:
Learn more about [suspended billing for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-suspend-billing). 
 <br><br> * Configure spending alerts for your account<br><br><br> You can enable spending notifications for Pay-As-You-Go or Subscription accounts, these alerts are configurable for the entire account or for individual services. [Set up spending notifications](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-spending). 
 <br><br> * Manage subscriptions and usage<br><br><br> Setting up a subscription is covered in [Set up accounts and an enterprise checklist](https://cloud.ibm.com/docs/overview?topic=overview-get-started-checklisttable2-accounts). You can add more subscriptions and monitor subscription usage on the Commitments and subscriptions page in the IBM Cloud console. Learn more about [managing subscriptions](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-subscriptions). 
 <br><br> * Manage commitments, subscriptions, and usage<br><br><br> Setting up a commitment or subscription is covered in Set up accounts and an enterprise checklist. You can add more commitments or subscriptions as well as monitor usage on the Commitments and Subscriptions page in the IBM Cloud console. Learn more about [Enterprise Savings Plan](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-committed-use) and [Managing subscriptions](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-subscriptions). 
 <br><br> * View invoices and build your own reports<br><br><br> To manage and view your invoices, visit the [Invoices](https://cloud.ibm.com/billing/invoices) page from the billing and usage dashboard in the IBM Cloud console.
In the IBM Cloud Usage view, locate the VMware as a Service service. Locate the Organization plan to find the Veeam usage across all virtual data centers in that organization.



Table 1. Licenses and fees for Veeam

 Metric Frequency Description 

 VEEAM_BACKUP_SERVICE_BASE_CHARGE Monthly Provisioning charge per instance where Veeam is enabled. 
 VEEAM_BACKUP_HOST_CHARGE Monthly Utilization charge on the number of bare metal servers with VMs utilizing Veeam backups. 
 VEEAM_LICENSES Monthly Veeam license charge for every VM under backup. The monthly charge is for the highest number of VMs under backup at any time period in the month. 
 TOTAL_VEEAM_BLOCK_STORAGE_GB Hourly Charge per GB of block storage used for all backups. 
 TOTAL_VEEAM_OBJECT_STORAGE_GB Hourly Charge per GB of object storage used for all backups. 



For the Veeam service, all backups go to both the block storage cross data center and to Cloud Object Storage.





 Backup data storage and encryption 

Veeam Backup and Replication backup storage uses a unique scale-out backup repository (SOBR) object for each customer. The SOBR is programmatically configured for each customer, with a dedicated location on each disk and a generated backup file encryption password. The SOBR includes an extent that is backed by IBM block storage in each of the physical data centers within the specific region. For example, if the virtual data center is in Dallas 10, the SOBR has extents in either Dallas 12 or Dallas 13 depending on which one has more storage when the Veeam service was added. The SOBR includes a customer-specific Cloud Object Storage bucket for more cost-effective long-term storage and as a second copy. Depending on the regions and compliance requirements of each geography, the Cloud Object Storage buckets remain in the same country, which is sometimes the same physical site.

When you decide to use the Veeam self-service portal to create backup jobs, identify which VM instances from any virtual data center in the organization participate in the backup job. Those backups are stored in the organizations SOBR.

You can manage (restore or delete) backups in the Veeam self-service portal.
A plan that offers a vGPU support for VSI reservation and charge based on the maximum number of virutal server (also known as Concurrent User) provisioned at any moment of the given month.

The total capacity offered is:



* A vGPU VSI configuration: 4 vCPU, 16GB RAM, vGPU: 1GB GPU memory, 100GB Disk



Pricing (billed monthly)



* Tier 1: $150/concurrent VSI for the first 1-49 virutal servers
* Tier 2: $142.50/concurrent VSI for 50-99 virutal servers
* Tier 3: $135.00/concurrent VSI for 100-199 virutal servers
* Tier 4: $127.50/concurrent VSI for 200-499 virutal servers
* Tier 5: $120/concurrent VSI for 500-999 virutal servers
* Tier 6: $117/concurrent VSI for 1000-1,499 virutal servers
* Tier 7: $112.50/concurrent VSI for 1500-2,999 virutal servers
* Tier 8: $105.00/concurrent VSI for additional virutal servers passing 3,000



Additional Persistent Storage



* $2 per 10 GB per user per month
Setting up Block Storage for VPC 

[Block Storage for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-aboutvpc-storage-encryption) provides hypervisor-mounted, high-performance data storage for your virtual server instances that you can provision within a VPC.

You can choose between predefined storage tiers with GB sizes and IOPS that meet the requirements of your workloads. To find out if Block Storage for VPC is the right storage option for you, see [Choosing a storage solution](https://cloud.ibm.com/docs/openshift?topic=openshift-storage-plan). For pricing information, see [Pricing for Block Storage for VPC](https://cloud.ibm.com/vpc-ext/provision/vs).

The Block Storage for VPC add-on is installed and enabled by default on VPC clusters. Later, you can disable or reenable the add-on by using the [addon disable](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_addon_disable) or [addon enable](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_addon_enable) command in the CLI. PVC creation and app deployment are not disrupted when the add-on is disabled. Existing volumes and data are not impacted.



 Quick start for IBM Cloud Block Storage for VPC 

In this quick start guide, you create a 10Gi 5IOPS tier Block Storage for VPC volume in your cluster by creating a PVC to dynamically provision the volume. Then, you create an app deployment that mounts your PVC.

Your Block Storage for VPC volumes can be mounted by multiple pods as long as those pods are scheduled on the same node.



1. Create a file for your PVC and name it pvc.yaml.

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
Why am I still seeing charges for block storage devices after deleting my cluster? 

Virtual Private Cloud

Classic infrastructure

  What’s happening 

You have already deleted your cluster but your account is still charged for the storage volumes associated with the cluster.

  Why it’s happening 

When you delete your cluster, you have the option to delete the storage volumes used by the cluster. If you select no, the storage volumes remain in your account, and continue incurring charges until they are deleted.

  How to fix it 

Delete the storage volumes from your account.



1.  Find the cluster ID of the deleted cluster. This ID will be used to remove associated block storage volumes. If you don't have the cluster ID of the deleted cluster, run ibmcloud ks cluster ls and a make a note of the cluster IDs whose block storage volumes you want to keep.

ibmcloud ks cluster ls
2.  Find the remaining volumes that are associated with the deleted cluster.

Classic clusters:

ibmcloud ks storage volume ls --provider classic | awk '{print $1 " " $8}'

Example output for Classic Block Storage volumes. Note the volume ID and the cluster ID.

102413596 blntvemw0j6snjt04jr0

VPC clusters:

ibmcloud ks storage volume ls --provider vpc-gen2 | awk '{print $1 " " $8}'
3.  Remove the volumes.

Classic clusters:

ibmcloud sl block volume-cancel VOLUME_ID

VPC clusters:

ibmcloud is vold VOLUME_NAME_OR_ID
4.  Optional: Verify there are no more volumes associated with the deleted cluster.

Classic clusters:

ibmcloud ks storage volume ls --provider classic | awk '{print $1 " " $8}'

VPC clusters:

ibmcloud ks storage volume ls --provider vpc-gen2 | awk '{print $1 " " $8}'
Pricing for Key Protect on Satellite 

Unlike the pricing for Key Protect on IBM Cloud, the pricing for Key Protect on Satellite is not based on key versions. Instead, reflecting the different use cases and infrastructure maintenance requirements for Satellite-based deployments, users are charged a flat rate for each location where they want Key Protect installed and then an additional rate depending on the quota of keys they select at deployment time.

Because of the way Key Protect structures its billing system, you cannot delete the first instance you deploy unless you plan to uninstall Key Protect from your Satellite location completely.



 Details 

Pricing is for Key Protect on Satellite only and does not include the price of a Satellite location or the price to install IBM Cloud Database (ICD) creation in your location.

Pricing for Key Protect on Satellite is based on two metrics:



* Base price: a monthly base price charged for the installation of Key Protect into a Satellite location. This is $780 a month per location. Note that there is no additional charge for creating multiple instances in a location.
* Key quota: the maximum number of [non-deleted keys](https://cloud.ibm.com/docs/key-protect?topic=key-protect-pricing-plan-satellitepricing-plan-satellite-non-deleted) which is defined when Key Protect is deployed in the Satellite location. This quota covers the number of keys per location, not per instance. If you choose to create a second instance, it is bound by the quota selected for the location. You do not need to increase your quota. Keys cost $1 per key, while quotas can be requested in batches of 100 keys. Because the minimum quota that can be selected is 100, the minimum quota charge is $100. If 200 keys are selected, for example, the charge is $200. This quota of keys can be changed later by opening a service ticket. If you attempt to exceed your key quota, you will get an error.



If you change quotas in the middle of a billing cycle (for example, going from 100 keys to 200 keys) you are charged whichever quota is larger. This charge is not prorated by the amount of time a particular quota was selected and is based on the maximum quota during a particular billing cycle.
Troubleshooting File Storage for VPC 

When you create or manage File Storage for VPC, you might encounter issues. Often, you can recover by following a few steps. Issues, symptoms, likely causes, and resolutions are described in the following sections.

IBM Cloud® File Storage for VPC is available for customers with special approval to preview this service in the Frankfurt, London, Madrid, Dallas, Toronto, Washington, Sao Paulo, Sydney, Osaka, and Tokyo regions. Contact your IBM Sales representative if you are interested in getting access.



 CBR error during file share operations 

 What’s happening 

A shares_access_forbidden error occurs when the context-based restriction (CBR) feature is used during file share operations, such as creating or updating a file share. In this case, the user request is forbidden, which is not the expected behavior.

 Why it’s happening 

An issue exists with the [IAM CBR feature](https://cloud.ibm.com/docs/account?topic=account-context-restrictions-whatis). Because the file service depends on the IAM CBR, performing share operations results in an error.

An error occurs after you set up CBR by [creating a network zone](https://cloud.ibm.com/docs/vpc?topic=vpc-cbr&interface=clicreating-network-zones) and [context-based rule](https://cloud.ibm.com/docs/vpc?topic=vpc-cbr&interface=clicreating-rules), and then performing a file share operation.

For example, first, you would add shares service to a network zone.

 {: screen}
ibmcloud cbr zone-create --name network-zone-1 --description "Example zone 1" --addresses 198.51.100.0 --vpc VPC-1 --service-ref service_name=shares


To complete setting up CBR, you would then create a context-based rule and specify shares as the service name and share ID for resource attributes.

 {: screen}
For more information, refer to the infrastructure provider documentation.









 Limitations for Red Hat OpenShift clusters in IBM Cloud Satellite 

See [Satellite cluster limitations](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_limitationssatellite_limits).





 Pricing for clusters in Satellite 

Review the table for information on charges related to Red Hat OpenShift clusters in IBM Cloud Satellite. For information about Location pricing, see [Satellite pricing](https://cloud.ibm.com/docs/satellite?topic=satellite-sat-pricing).

Looking for an estimate? Try the [Cost estimator](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-costcost) or review the [Pricing model](https://www.ibm.com/products/satellite/overview)



Red Hat OpenShift cluster on Satellite charges.

 Type of charge Clusters created after 15 November 2022 Clusters created before 15 November 2022 What the charge covers 

 Cluster management fee A flat monthly fee for the cluster, charged hourly. Per vCPU hour of the hosts that are assigned to the cluster as worker nodes The benefits of Red Hat OpenShift on IBM Cloud, such as installation and security patch updates of OpenShift Container Platform for your worker nodes; managing your cluster with a suite of API, CLI, and UI tools; integration with IBM Cloud platform tooling such as IAM; continuous monitoring by IBM Site Reliability Engineers; access to IBM Cloud support; and more. 
 Worker node management fee Per vCPU hour of the hosts that are assigned to the cluster as worker nodes. Per vCPU hour of the hosts that are assigned to the cluster as worker nodes. The benefits of IBM Cloud Satellite, such as to create the cluster on any compatible infrastructure that you want; tooling to consistently deploy apps, storage drivers, and endpoints across the location; integration with IBM Cloud platform tooling such as IAM; continuous monitoring by IBM Site Reliability Engineers; access to IBM Cloud support; and more. 
 OCP licensing fee Per vCPU hour.
The on-premises data center in this tutorial will be simulated using a VSI within a VPC.

The preferred mechanism to connect VPCs is [Transit Gateway](https://cloud.ibm.com/interconnectivity/transit). Simulation of an on-premises environment with VPC, VSI and VPN is used only for illustration.

In addition:



* Check for user permissions. Be sure that your user account has sufficient permissions to create and manage VPC resources. For a list of required permissions, see [Granting permissions needed for VPC resources](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-user-permissions-for-vpc-resources).
* You need an SSH key to connect to the virtual servers. If you don't have an SSH key, see the [instructions for creating a key](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-ssh-keys&interface=ui).







 Step 1: Use Schematics to create the resources 



1. Log in to [IBM Cloud](https://cloud.ibm.com/).
2. Navigate to [Create Schematics Workspaces](https://cloud.ibm.com/schematics/workspaces/create?repository=https://github.com/IBM-Cloud/vpc-tutorials/tree/master/vpc-site2site-vpn&terraform_version=terraform_v1.2) Under the Specify Template section, verify:



1. Repository URL is https://github.com/IBM-Cloud/vpc-tutorials/tree/master/vpc-site2site-vpn
2. Terraform version is terraform_v1.2



3. Under Workspace details,



1. Provide a workspace name : vpnsts.
2. Choose a Resource Group and a Location.
3. Click on Next.



4. Verify the details and then click on Create.
5.