vania-janet/multiturn-rag-retrieval-data huggingface dataset:
IBM Cloud Connect is a software-defined network interconnect service that brings secure connectivity to client locations around the world. For more information, see [Connecting Power Systems Virtual Server instances and networks](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-connecting-networks).

IBM Cloud Connect is only available to IBM clients within the US.





 How is network bandwidth billed? 

IBM Cloud Classic environment: Inbound bandwidth is unlimited and not charged. Outbound bandwidth is charged per GB tier with bandwidth offered as an allotment for each month. As an example, for your compute instances, 250 GB is included with each monthly virtual server and 20 TB is included with each monthly bare metal server. Extra bandwidth can also be purchased per packages. For more information, see [Bandwidth packages](https://www.ibm.com/cloud/bandwidth).

IBM Power Systems Virtual Server environment: Inbound bandwidth is unlimited and not charged. Bandwidth is not charged when you use a public network. If you are using a private network with DirectLink Connect, you are charged IBM Cloud Classic environment rates.





 What monitoring services are available? 

IBM does not provide status and performance monitoring for the Power Systems Virtual Server. Clients must use their own on-premises tools.





 What performance and capacity planning services do you provide for IBM i? 

IBM uses the same tools that are on an on-premises system.





 IBM i and solution certification 

You can find self-certification and listing information on the [IBM Global Solutions Directory](https://www.ibm.com/partnerworld/public/find-partner-solution).





 How do I delete a workspace? 

To delete a workspace (and all its resources), use the left navigation to navigate the workspace page. Find the workspace to be deleted and click on the overflow menu on the top right corner of the tile. Click Delete and confirm the request from the pull-down menu by typing Delete in the text field. Finally, click the red Delete button to initiate the request.





 How do I delete a single virtual server instance? 

There are two methods to delete a virtual server instance.
Configure NAT for Internet access from a private 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, [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 [public gateways](https://cloud.ibm.com/docs/vpc?topic=vpc-about-networking-for-vpcexternal-connectivity).

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.

In today’s world of web based IT applications and services, few applications exist in isolation. Developers have come to expect access to services on the Internet, whether it is open-source application code and updates or ‘third party’ services providing application functionality via REST APIs. Network Address Translation (NAT) masquerade, is a commonly used approach to securing the access to Internet hosted service from private networks. In NAT masquerade, private IP addresses are translated to the IP address of the out-bound public interface in a many-to-one relationship, shielding the private IP address from public view.

This tutorial presents the setup of Network Address Translation (NAT) masquerade on a Virtual Router Appliance (VRA) to connect to a secured subnet on the IBM Cloud private network.
* API







 IBM Cloud Application Load Balancer for VPC API example 

To make API calls, you must use a REST client. For example, you can use a curl command to retrieve all existing load balancers:

curl -X GET "$vpc_api_endpoint/v1/load_balancers?version=$api_version&generation=2" -H "Authorization: $iam_token"

For detailed information on APIs available for application load balancers in your VPC environment, see the load balancers section in the [VPC API reference](https://cloud.ibm.com/apidocs/vpclist-all-load-balancers).

In the following example, use the API to create an application load balancer in front of two VPC virtual server instances (192.168.100.5 and 192.168.100.6) running a web application that listens on port 80. The load balancer has a front-end listener, which allows secure access to the web application by using HTTPS. You can use the API to get details of the load balancer after it is created, and to delete the load balancer.

The example steps that follow skip the prerequisite steps of using the [IBM Cloud console](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-using-the-ibm-cloud-console), [CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-using-cli), or [API](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-using-the-rest-apis) to provision a VPC, subnets, and instances.

You can also create a load balancer using the UI or CLI.
Logging in as a Virtual Server Instance Compute Resource Identity 

You can use a trusted profile to set up fine-grained authorization for applications that are running in compute resources. As a result, you aren't required to create service IDs or API keys for the compute resources. The IBM Cloud CLI supports logging in and authenticating to IBM Cloud using a IBM Cloud Virtual Server Instance (VSI) for VPC compute resource.

For more information about managing trusted profiles and establishing trust with compute resources, see [Establishing trust with compute resources](https://cloud.ibm.com/docs/account?topic=account-create-trusted-profile&interface=uicreate-profile-compute).



 Using the CLI to log in 

To use the IBM Cloud CLI Virtual Server Instance for VPC compute resource identity login feature, you must enable the Instance Metadata service for VPC service on the VSI and link the instance to a trusted profile. For more information about enabling the Instance Metadata service, see [About Instance Metadata for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-imd-about&interface=ui). Once enabled and the VSI has been linked to a trusted profile, the CLI can use the [Instance Identity token service](https://cloud.ibm.com/docs/vpc?topic=vpc-imd-about&interface=uiimd-vpc-access-token) to acquire a JSON web token and exchange it for an IAM token.

Certain IBM Cloud Kubernetes Service CLI commands are currently not supported when logged in as a VPC compute resource including [ibmcloud ks cluster config](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_config).



 Log in with the CLI 

When you use the VPC VSI option to log in, you can optionally specify the trusted profile parameter to enter at login. If provided, the CLI will use this trusted profile to authenticate to IBM Cloud. Otherwise, the VSI's default linked trusted profile linked during instance provisioning will be used.
If you are using the CLI, run the command ibmcloud is subnets to list all the subnets for the VPC. Then, run the command ibmcloud is subnet <subnet-id> for each subnet in the VPC, and check for conflicts with the value of IPv4 CIDR in the CLI output.





 new_account_provisioning_disabled 

Message: Provisioning of resources for accounts new to VPC are disabled for VPC Gen1. Please use VPC Gen2.

Due to the end of life of VPC Gen 1, new accounts are not able to provision new resources and will see this error when doing so. Use VPC Gen 2 to provision new resources.





 not_authorized 

Message: The request is not authorized.

You may see this error is if your IAM token is missing or expired. For instructions on how to generate a token, refer to [Creating a VPC using the REST APIs](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-creating-a-vpc-using-the-rest-apis). If the token is not expired, make sure the account you are using is authorized to use this function and you have the [correct permissions](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-managing-user-permissions-for-vpc-resources).

If you have correct authorization but you are still getting this error, [contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support).





 not_found 

Message: Please check whether the resource you are requesting exists.

You referenced a resource that does not exist or one to which you do not have access. Review your request to ensure that you specified the proper IDs and references.

If the resource is an operating system, you can use the request, GET /v1/operating_systems to list valid options.
: IBM Cloud® Network Load Balancer for VPC (NLB) now supports the creation of private network load balancers. A private NLB is a load balancer only accessible from within the VPC network and/or where the client has reachability to the VPC network (for example, through Direct Link or a transit gateway). To create private load balancers, you must have a dedicated subnet with no custom routes configured for the subnet. For information on creating a private NLB, refer to [Creating a network load balancer for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-nlb-ui-creating-network-load-balancer).





 19 March 2021 

Virtual server instance console
: The virtual server instance console feature is now generally available in the following regions: Dallas, Frankfurt, London, Osaka, and Washington DC. For more information, see [Accessing virtual server instances by using VNC or serial consoles](https://cloud.ibm.com/docs/vpc?topic=vpc-vsi_is_connecting_console).

Bring you own license (GA)
: You can bring your own license (BYOL) when you import a RedHat Enterprise Linux (RHEL) or Windows® custom image to IBM Cloud VPC. Because these images are registered and licensed by you, you maintain control over your licenses and with no additional cost. Acquisition and activation of the license is between you and and the OS vendor. For more information, see [Bring your own license](https://cloud.ibm.com/docs/vpc?topic=vpc-byol-vpc-about).

Dedicated hosts (GA)
: Dedicated hosts are available in all regions. Use a dedicated host to carve out a single-tenant compute node for IBM Cloud VPC. For more information, see [Creating dedicated hosts and groups](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-dedicated-hosts-instances)





 12 March 2021 

New profiles
: The Balanced, Compute, and Memory profile families now include three new profiles with 64, 96, and 128 vCPUs.
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. Copy this passcode and paste it as a response on the prompt. After the authentication steps, you'll be prompted to choose your account. If you have access to multiple users, select the user you want to log in as.

When you are prompted to select a region, select us-south.

Respond to any remaining prompts to finish logging in.





 Select the generation of VPC 

Use the following command to configure the CLI plug-in to target generation 2 virtual server instances for VPC.

ibmcloud is target --gen 2





 Create a VPC 

Use the following command to create a VPC named my-vpc.

ibmcloud is vpc-create my-vpc

From the output that's returned, save the ID in a variable so you can use it later, for example:

vpc="0738-59de4046-3434-4d87-bb29-0c99c428c96e"

The previous example does not create a VPC with classic access. If you require the VPC to have access to your classic resources, see [Setting up access to classic infrastructure](https://cloud.ibm.com/docs/vpc?topic=vpc-setting-up-access-to-classic-infrastructure). You can only enable a VPC for classic access while creating it. In addition, you can only have one classic access VPC in your account at any time.





 Create a private catalog 

This step is optional. If you plan share images from a private catalog, the private catalog must be created first.
Scale workloads in shared and dedicated VPC environments 

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 walks you through the steps of setting up isolated workloads in a shared (multi-tenant) environment and a dedicated (single-tenant) environment. Provision an IBM Cloud® Virtual Private Cloud (VPC) with subnets spanning multiple availability zones (AZs) and virtual server instances (VSIs) that can scale according to your requirements to ensure the high availability of your application. Furthermore, configure load balancers to provide high availability between zones within one region. Configure Virtual Private Endpoints (VPE) for your VPC providing private routes to services on the IBM Cloud.

Isolate workloads by provisioning a dedicated host, attaching an encrypted data volume to a VSI, expanding the attached data volume, and resizing the VSI after the fact.

You will provision all of these services and VPC resources using IBM Cloud Schematics, which provides Terraform-as-a-Service capabilities. The Terraform template defines the IBM Cloud resources to be created, updated, or deleted.



 Objectives 



* Learn how to set up a multi-zone VPC with instance autoscaling.
* Understand the concepts of public and private load balancing.
* Learn how to scale instances dynamically or periodically.
* Learn the use of dedicated hosts.



Zoom

![Architecture](https://cloud.ibm.com/docs-content/v1/content/f84e2238288b7f0355715a4c355609ce7ac48fb0/solution-tutorials/images/solution62-vpc-scaling-dedicated/architecture_diagram.svg)

Figure 1. Architecture diagram of the tutorial



1. The frontend app deployed on VSI(s) communicates to the backend app via the private load balancer.
2. The backend app securely communicates with the cloud services via a virtual private endpoint (VPE).
3.
* VPC clusters: A Load Balancer for VPC is automatically created in your VPC for your cluster. For cost information, see [Pricing for Load Balancer for VPC](https://cloud.ibm.com/vpc-ext/provision/vs).







 Storage 

When you provision storage, you can choose the storage type and storage class that is correct for your use case. Charges vary depending on the type of storage, the location, and the specs of the storage instance. Some storage solutions, such as file and block storage offer hourly and monthly rates that you can choose from.

To choose the correct storage solution, see [Planning highly available persistent storage](https://cloud.ibm.com/docs/containers?topic=containers-storage-plan). For more information, see:



* [File Storage for Classic](https://www.ibm.com/products/file-storage)
* [Block Storage for Classic](https://www.ibm.com/products/block-storage)
* [File Storage for VPC](https://www.ibm.com/products/file-storage)
* [Block Storage for VPC](https://www.ibm.com/products/block-storage)
* [IBM Cloud Object Storage](https://www.ibm.com/cloud/object-storage)
* [Portworx Enterprise pricing](https://cloud.ibm.com/catalog/services/portworx-enterprise)







 IBM Cloud services 

Each service that you integrate with your cluster has its own pricing model. Review each product documentation and use the IBM Cloud console to [estimate costs](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-costcost).





 Operators and other third-party integrations 

Operators and other [third-party integrations](https://cloud.ibm.com/docs/containers?topic=containers-supported_integrations) are a convenient way to add services to your cluster from community, third-party, your own, or other providers.
Granting user permissions for VPC resources 

IBM Cloud® Virtual Private Cloud uses role-based access control that enables account administrators to control their users' access to VPC resources. Access can be assigned to individual users or to groups of users by using IBM Cloud Identity and Access Management (IAM).

For more information about IAM roles, see [IAM roles and actions](https://cloud.ibm.com/docs/vpc?topic=vpc-iam-getting-startediam-roles). For more information about the minimum IAM roles that a user or service ID need to interact with an IBM Cloud® Virtual Private Cloud (VPC) infrastructure resource, see [Required permissions](https://cloud.ibm.com/docs/vpc?topic=vpc-resource-authorizations-required-for-api-and-cli-calls).

This document shows examples of how the account administrator can use the IBM Cloud console to grant the correct permissions for managing VPC infrastructure resources. It covers the following scenarios:



* Full-access scenario: Assign an access policy so a new user can create and use all VPC infrastructure resources (including VPCs).
* Limited access scenario: Assign an access policy so an existing user can create and use only virtual server instances.
* Team access scenario: Set up resource groups and access groups to allow two separate teams to create and use the VPC resources that are assigned to their team.



You can also manage permissions through the CLI or API. For more information, see [How do I use IBM Cloud IAM](https://cloud.ibm.com/docs/account?topic=account-iamoverviewhowto).



 Full-access scenario 

This scenario shows how to invite a new IBM Cloud user to your account and give them access to VPC infrastructure so they can view, create, and update all VPC resources in the Default resource group.

To give a new user access to all VPC infrastructure resources:



1. Go to the [IAM Users](https://cloud.ibm.com/iam/users) page in the IBM Cloud console and click Invite users.
2.
This tutorial creates a cluster that runs version 1.26.







 Step 1: Create a cluster in VPC 

Create an IBM Cloud Kubernetes Service cluster in your IBM Cloud Virtual Private Cloud (VPC) environment. For more information about VPC, see [Getting Started with Virtual Private Cloud](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started).



1. Log in to the account, resource group, and IBM Cloud region where you want to create your VPC environment. The VPC must be set up in the same multizone metro location where you want to create your cluster. In this tutorial you create a VPC in us-south. For other supported regions, see [Multizone metros for VPC clusters](https://cloud.ibm.com/docs/containers?topic=containers-regions-and-zoneszones-vpc). If you have a federated ID, include the --sso option.

ibmcloud login -r us-south [-g <resource_group>] [--sso]
2. Create a VPC for your cluster. For more information, see the docs for creating a VPC in the [console](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-using-the-ibm-cloud-console) or [CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-vpc-resources-with-cli-and-api&interface=clicreate-a-vpc-cli).



1. Create a VPC called myvpc and note the ID in the output. VPCs provide an isolated environment for your workloads to run within the public cloud. You can use the same VPC for multiple clusters, such as if you plan to have different clusters host separate microservices that need to communicate with each other. If you want to separate your clusters, such as for different departments, you can create a VPC for each cluster.

ibmcloud is vpc-create myvpc
2.
IBM Cloud File Storage for VPC add-on change log 

File Storage for VPC is available for allowlisted accounts in the Washington D.C., Dallas, Frankfurt, London, Sydney, Sao Paulo, and Tokyo regions. Contact your IBM Sales representative if you are interested in getting access.

File Storage for VPC is available in Beta. Do not use this add-on for production workloads.

View information for patch updates to the IBM Cloud File Storage for VPC add-on in your Red Hat OpenShift on IBM Cloud clusters.

Patch updates
: Patch updates are delivered automatically by IBM and don't contain any feature updates or changes in the supported add-on and cluster versions.

Release updates
: Release updates contain new features for the IBM Cloud File Storage for VPC or changes in the supported add-on or cluster versions. You must manually apply release updates to your IBM Cloud File Storage for VPC add-on. To update your IBM Cloud File Storage for VPC add-on, see [Updating the IBM Cloud File Storage for VPC add-on](https://cloud.ibm.com/docs/openshift?topic=openshift-storage-file-vpc-managing).

To view a list of add-ons and the supported cluster versions in the CLI, run the following command.

ibmcloud oc cluster addon versions --addon vpc-file-csi-driver

To view a list of add-ons and the supported cluster versions, see the [Supported cluster add-ons table](https://cloud.ibm.com/docs/openshift?topic=openshift-supported-cluster-addon-versions).



 Version 1.1 



 Change log for version 1.1, released 3 July 2023 



* Updates the following sidecar images:



* storage-secret-sidecar to v1.2.24.
* csi-node-driver-registrar to v2.7.0.
* livenessprobe to v2.9.0.
* csi-provisioner to v3.4.1.
* csi-resizer to v1.7.0.
Provision IBM Cloud VPC Subnets and configure Distributed Virtual Switch Portgroups for VMs 

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.

This tutorial presents a simple example to deploy a VMware virtual machine running on VMware cluster and attached to IBM Cloud VPC subnet using a VLAN interface and allow the virtual machine to vMotion between hosts.



 Objectives 

In this tutorial, you will create a VMware virtual machine running on VMware cluster using IBM Cloud VPC and Bare Metal Servers for VPC network constructs. Your virtual machine will be attached to IBM Cloud VPC subnet using bare metal server's VLAN NIC.

Zoom

![Virtual machines attached to IBM Cloud VPC subnet](https://cloud.ibm.com/docs-content/v1/content/f84e2238288b7f0355715a4c355609ce7ac48fb0/solution-tutorials/images/solution63-ryo-vmware-on-vpc/Self-Managed-Simple-20210813v1-Non-NSX-based-VMs.svg)

Figure 1. Virtual machines attached to IBM Cloud VPC subnet





 Before you begin 

This tutorial requires:



* Common [prereqs](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmwarevpc-bm-vmware-prereqs) for VMware Deployment tutorials in IBM Cloud VPC



This tutorial is part of series, and requires that you have completed the related tutorials.