vania-janet/multiturn-rag-retrieval-data huggingface dataset:
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) 
 Bare Metal Servers for VPC ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) 
 Block Storage Snapshots for VPC !
is_vpc_address_prefix](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/is_vpc_address_prefix)<br> * [ibm_is_vpc_route](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/is_vpc_route)<br> * [ibm_is_vpc_routing_table](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/is_vpc_routing_table)<br> * [ibm_is_vpc_routing_table_route](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/is_vpc_routing_table_route)<br> * [ibm_is_vpn_gateway](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/is_vpn_gateway)<br> * [ibm_is_vpn_gateway_connection](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/is_vpn_gateway_connection)<br> * [ibm_
VPC landing zone configurations 

This solution is verified and supported only with the Power Virtual Server with VPC landing zone deployments that use preconfigured configurations (presets) for VPC landing zone. These presets must be selected or inserted when deploying the VPC landing zone either separately or as part of a new Power infrastructure with VPC landing zone deployment. For more informtion about supported presets and provisioned trusted zones, data flows, and endpoints, see [VPC landing zone configurations](https://cloud.ibm.com/docs/powervs-vpc?topic=powervs-vpc-powervs-automation-presets).
This action overrides the Public Gateway of that specific VLAN interface in VPC subnet, if that is provisioned to a subnet with attached Public Gateway.





 Related links 



* [IBM Cloud VPC getting started](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started)
* [IBM Cloud VPC Bare Metal Servers](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-for-bare-metal-servers)
* [IBM Cloud VPC RYO VMware reference architecture](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vpc-ryo-arch-overview)
* [IBM Cloud Direct Link overview](https://cloud.ibm.com/docs/dl?topic=dl-get-started-with-ibm-cloud-dl)
* [IBM Cloud Transit Gateway overview](https://cloud.ibm.com/docs/transit-gateway?topic=transit-gateway-getting-started)
* [IBM Cloud VPC VPN overview](https://cloud.ibm.com/docs/vpc?topic=vpc-vpn-overview)
* [VPC IaaS endpoints](https://cloud.ibm.com/docs/vpc?topic=vpc-service-endpoints-for-vpcinfrastructure-as-a-service-iaas-endpoints)
* [VMware on Bare Metal VPC tutorial](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmware)
volume_iops Number to represent the IOPS configuration for block storage to be used for the NFS instance (valid only for volume_profile=custom, dependent on volume_capacity). Enter a value in the range 100 - 48,000. For possible options of IOPS, see [Custom IOPS profile](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilescustom). No 300 
 volume_profile Name of the block storage volume type to be used for NFS instance. For possible options, see [Block storage profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profiles). No general_purpose 
 vpc_cidr_block Creates the address prefix for the new VPC when the vpc_name variable is empty. Only a single address prefix is allowed. For more information, see [Setting IP ranges](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-addressing-plan-design). No 10.241.0.0/18 
 vpc_cluster_login_private_subnets_cidr_blocks The CIDR block that's required for the creation of the login cluster private subnet. Modify the CIDR block if it has already been reserved or used for other applications within the VPC or conflicts with any on-premises CIDR blocks if you are using a hybrid environment. Provide only one CIDR block for the creation of the login subnet. Since the login subnet is used only for the creation of the login virtual server instance, provide a CIDR range of /28. No 10.241.4.0/28 
 vpc_cluster_private_subnets_cidr_blocks The CIDR block that's required for the creation of the compute and storage cluster private subnet. Modify the CIDR block if it has already been reserved or used for other applications within the VPC or conflicts with any on-premises CIDR blocks if you are using a hybrid environment. Provide only one CIDR block for the creation of the compute and storage subnet.
[solution tutorial icon](https://cloud.ibm.com/media/docs/images/homepage/solution-tutorial.svg) [VSI on VPC landing zone - QuickStart variation](https://cloud.ibm.com/docs/deployable-reference-architectures?topic=deployable-reference-architectures-vsi-ra-qs)VSI on VPC landing zone - QuickStart variation Reference architecture

The QuickStart variation of the VSI on VPC landing zone deployable architecture creates a fully customizable Virtual Private Cloud (VPC) environment in a single region. The solution provides virtual servers in a secure VPC for your workloads. The QuickStart variation is designed to deploy quickly for demonstration and development.

Deployable![ref architecture icon](https://cloud.ibm.com/media/docs/images/homepage/reference-architecture.svg) [VSI on VPC landing zone - Standard variation](https://cloud.ibm.com/docs/deployable-reference-architectures?topic=deployable-reference-architectures-vsi-ra)VSI on VPC landing zone - Standard variation Reference architecture

The Standard variation of the VSI on VPC landing zone deployable architecture is based on the IBM Cloud for Financial Services reference architecture. The architecture creates a customizable and secure infrastructure, with virtual servers, to run your workloads with a Virtual Private Cloud (VPC) in multizone regions.

Deployable![ref architecture icon](https://cloud.ibm.com/media/docs/images/homepage/reference-architecture.svg)
VPC resource attributes 

When you use Terraform or the IBM Cloud® Command Line Interface (CLI) to create, update, or delete IBM Cloud Identity and Access Management (IAM) access policies, you can specify the target VPC resource by using resource attributes.

Resource attributes are in the form of name=value,name=value....

You can select a resource object by entering the ID of the object. Or, you can enter the wildcard * in value to denote all applicable objects. For example, the attribute vpcId: set the access policy to be applicable to all the VPCs in the account. You can also specify which resource group the policy is applied to in the command.

The following example CLI command gives the user name@example.comViewer role for all the VPCs in the current account:

ibmcloud iam user-policy-create name@example.com --roles Viewer --service-name is --attributes "vpcId="

For more information about using the CLI to create and modify IAM access policy, see [ibmcloud iam user-policy-create](https://cloud.ibm.com/docs/account?topic=cli-ibmcloud_commands_iamibmcloud_iam_user_policy_create).

For more information about using Terraform to create IAM access policy, see the resources.attributes input parameter for the following IAM policies:



* [ibm_iam-access_group_policy](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-iam-resourcesiam-access-group-policy)
* [ibm_iam_service_policy](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-iam-resourcesiam-service-policy)
* [Regions and zones](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-detailed-vsivpc-architecture-detailed-regions-zones)
* [Connectivity to workload VPC](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-detailed-vsivpc-architecture-detailed-workload-connectivity)
* [Storage and encryption](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-detailed-vsivpc-architecture-detailed-services-encryption)
* [Using IBM Cloud services outside of a VPC](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-detailed-vsivpc-architecture-detailed-connectivity-services)



* [Variation with edge/transit VPC for public internet access](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-detailed-vsiedge-vpc-architecture)
* [Next steps](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-detailed-vsinext-steps)



[VPC with Red Hat OpenShift on IBM Cloud reference architecture](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-detailed-openshiftvpc-architecture-detailed-openshift)



* [Architecture diagram](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-detailed-openshiftvpc-openshift-diagram)
SAO04 IBM Power VS SL-SAO04-POWERVSCX-1-1 <br>SL-SAO04-POWERVSCX-1-2 SL-SAO04-POWERVSCX-2-1 <br>SL-SAO04-POWERVSCX-2-2 



2. Select the remaining options and create the Direct Link Connect instance as described in [Ordering Direct Link (2.0) Connect](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-ordering-direct-link-connectorder-direct-link-connect-2.0).







 Routing considerations for VPC 

If traffic is sent from the Power Systems Virtual Server to your on-premises public IP address, and if the virtual server instance has a public floating IP, you might need a special configuration in the VPC. Otherwise, the traffic goes through the virtual machine's public interface instead of a private interface.

For proper VPC configuration, the on-premises IP address must meet the following requirements:



* The IP address range for a private network must be within the following blocks, which are reserved by the Internet Assigned Numbers Authority (IANA):



* Class A — 10.0.0.0 — 10.255.255.255 (16,777,216 total hosts)
* Class B — 172.16.0.0 — 172.31.255.255 (1,048,576 total hosts)
* Class C — 192.168.0.0 — 192.168.255.255 (65,536 total hosts)



* VM instances within the VPC must not have a floating IP.
* Use the Delegate-VPC action to create a route to the on-premises public subnet in the VPC default routing table.



For more information, see [Routing considerations for IANA-registered IP assignments](https://cloud.ibm.com/docs/vpc?topic=vpc-interconnectivityrouting-considerations-iana).
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) 
 Dedicated Host for VPC ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) 
 Direct Link Connect Hosted Globally Hosted Globally Hosted Globally Hosted Globally 
 Direct Link Dedicated Hosted Globally Hosted Globally Hosted Globally Hosted Globally 
 Event Notifications ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) 
 Event Streams !
: Optional: Do not show the message of the day or update reminders.



 Example vlan ls command 

ibmcloud oc vlan ls --zone dal10







 ibmcloud oc vlan spanning get 

Classic infrastructure

View the VLAN spanning status for an IBM Cloud infrastructure account. VLAN spanning enables all devices on an account to communicate with each other through the private network, regardless of its assigned VLAN.

The VLAN spanning option is disabled for clusters that are created in a VRF-enabled account. When VRF is enabled, all VLANs in the account can automatically communicate with each other over the private network. To check whether a VRF is enabled, use the ibmcloud account show command. For more information, see [Planning your cluster network setup: Worker-to-worker communication](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_basicsworker-worker).

ibmcloud oc vlan spanning get --region REGION [--output json] [-q]

Minimum required permissions
: Viewer platform access role for IBM Cloud Kubernetes Service

Command options:

--region REGION
: Specify a region in Red Hat OpenShift on IBM Cloud: jp-osa, jp-tok, au-syd, eu-de, eu-gb, us-east, or us-south.

--output json
: Optional: Prints the command output in JSON format.

-q
: Optional: Do not show the message of the day or update reminders.



 Example vlan spanning get command 

ibmcloud oc vlan spanning get --region us-south









 vpcs command 

Virtual Private Cloud

List all VPCs in the targeted resource group. If no resource group is targeted, then all VPCs in the account are listed.

ibmcloud oc vpcs [--provider vpc-gen2] [--output json] [-q]

Minimum required permissions:



* Viewer platform access role for IBM Cloud Kubernetes Service



Command options:

--provider vpc-gen2
* ibmcloud is vpc-address-prefix-update my-vpc my-prefix --name my-renamed-prefix --default false --output JSON







 Command options 



* VPC: ID or name of the VPC.
* PREFIX: ID or name of the VPC address prefix.
* --name: New name of the address prefix.
* --default: This flag indicates whether this is the default prefix for this zone in this VPC. One of: false, true.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is vpc-address-prefixes 

List all address prefixes.

ibmcloud is vpc-address-prefixes VPC [--output JSON] [-q, --quiet]



 Command options 



* VPC: ID or name of the VPC.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is vpc-create 

Create a VPC.

ibmcloud is vpc-create VPC_NAME [--classic-access] [--address-prefix-management auto | manual] [--resource-group-id RESOURCE_GROUP_ID | --resource-group-name RESOURCE_GROUP_NAME] [--output JSON] [-q, --quiet]



 Command examples 



* ibmcloud is vpc-create my-vpc --classic-access
* ibmcloud is vpc-create my-vpc --address-prefix-management auto
* ibmcloud is vpc-create my-vpc --resource-group-id fee82deba12e4c0fb69c3b09d1f12345
If you require one or more address prefixes you should define as part of resource provisioning in the configuration file. To configure multiple address prefix with arguments define the code as stated in the code block. For more information, see [ibm_is_vpc_address_prefix data source](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/is_vpc_address_prefixesattribute-reference).

 {: codeblock}
resource "ibm_is_vpc" "testacc_vpc" {
name = "testvpc"
}

resource "ibm_is_vpc_address_prefix" "testacc_vpc_address_prefix" {
name = "test"
zone = "us-south-1"
vpc = ibm_is_vpc.testacc_vpc.id
cidr = "10.240.0.0/24"
}

resource "ibm_is_vpc_address_prefix" "testacc_vpc_address_prefix2" {
name = "test2"
zone = "us-south-1"
vpc = ibm_is_vpc.testacc_vpc.id
cidr = "10.240.0.0/24"
}

Show more





 How do I define a policy which has all resource groups? 

A access group policy is a way to organize your account having create, modify, or delete an IAM access groups, where user can grant permissions to members with appropriate privileges such as Manager, Viewer and Administrator. For more information, about [ibm_access_group_policy resource](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/iam_access_group_policy) and [iam_service_policy resource](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/iam_service_policy).

 {: codeblock}
subnet is.subnet.public-gateway.attach Public Gateway was attached to Subnet 
 subnet is.subnet.public-gateway.detach Public Gateway was detached from Subnet 
 subnet is.subnet.public-gateway.read A subnet public-gateway attachment was retrieved 







 Virtual private endpoints events 

The following table lists the actions that are related to virtual private endpoints and the generation of events.



Table 9. Actions that generate events for virtual private endpoints

 Resource Action Description 

 endpoint-gateway is.endpoint-gateway.endpoint-gateway.create Endpoint gateway was created 
 endpoint-gateway is.endpoint-gateway.endpoint-gateway.delete Endpoint gateway was deleted 
 endpoint-gateway is.endpoint-gateway.endpoint-gateway.update Endpoint gateway was updated 







 VPC events 



Table 10. Actions that generate events for VPC

 Resource Action Description 

 vpc is.vpc.vpc.create VPC was created 
 vpc is.vpc.vpc.update VPC was updated 
 vpc is.vpc.vpc.delete VPC was deleted 
 vpc is.vpc.vpc.read One or more VPC was retrieved 
 vpc is.vpc.address-prefix.create Address Prefix was added to VPC 
 vpc is.vpc.address-prefix.update VPC Address Prefix was updated 
 vpc is.vpc.address-prefix.delete Address Prefix was removed from VPC 
 vpc is.vpc.address-prefix.read One or more address prefixes were retrieved 
 vpc is.vpc.vpc-route.create Route was added to VPC 
 vpc is.vpc.vpc-route.update VPC Route was updated 
 vpc is.vpc.vpc-route.delete Route was removed from VPC 







 VPN gateway events 

The following table lists the actions that are related to site-to-site VPN gateways and the generation of events.



Table 11. Actions that generate events for site-to-site VPN gateways

 Resource Action Description 

 vpn is.vpn.vpn-gateway.create VPN gateway was created
When a process runs on Unix/Linux, the operating system identifies a user with a user ID (UID) and/or group with a group ID (GID). These IDs determine which system resources a user or group can access. When you [create a file share](https://cloud.ibm.com/apidocs/vpc-betacreate-share), you can specify the new initial_owner property and specify a uid, gid, or both sub-properties to control access to the share. For more information, see [Add supplemental IDs when you create a file share from the API](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-create&interface=apifs-add-supplemental-id-api).







 24 August 2021 



 For all version dates 

VPN client-to-site servers. Until now, the Virtual Private Network (VPN) for VPC service supported only site-to-site connectivity, which connects your on-premises network to the IBM Cloud. This beta release adds client-to-site connectivity, which allows remote devices to securely connect to the VPC network using an OpenVPN software client. This solution is useful for telecommuters who want to connect to the IBM Cloud from a remote location, such as a home office. For more information, see [About VPN servers (client-to-site)](https://cloud.ibm.com/docs/vpc?topic=vpc-vpn-client-to-site-overview) or check out the new [API methods](https://cloud.ibm.com/apidocs/vpc-betalist-vpn-servers).

This feature is now generally available. See the [VPC API change log](https://cloud.ibm.com/docs/vpc?topic=vpc-api-change-log5-july-2022).







 17 August 2021 



 For all API version dates 

File storage for VPC. Accounts that have been granted special approval to preview this feature can now increase file share size in gigabyte increments up to 32 TB (depending on the file share's profile).
Modify the CIDR block if it has already been reserved or used for other applications within the VPC or conflicts with any on-premises CIDR blocks when using a hybrid environment. Provide only one CIDR block for the creation of the compute subnet. No 10.241.0.0/24 
 vpc_region Name of the IBM Cloud region where the resources need to be provisioned (for example, us-east, us-south). For more information, see [Region and data center locations for resource deployment](https://cloud.ibm.com/docs/overview?topic=overview-locations). Yes None 
 vpc_storage_cluster_dns_domain IBM Cloud DNS Services domain name to be used for the storage cluster. No strgscale.com 
 vpc_storage_cluster_private_subnets_cidr_blocks The CIDR block that's required for the creation of the storage cluster private subnet. Modify the CIDR block if it has already been reserved or used for other applications within the VPC or conflicts with any on-premises CIDR blocks when using a hybrid environment. Provide only one CIDR block for the creation of the storage subnet. No 10.241.1.0/24
* [Required permissions for VPC resources](https://cloud.ibm.com/docs/vpc?topic=vpc-resource-authorizations-required-for-api-and-cli-calls)
* [IBM Cloud Activity Tracker events](https://cloud.ibm.com/docs/vpc?topic=vpc-at-eventsevents-load-balancers)
* [FAQs for application load balancers](https://cloud.ibm.com/docs/vpc?topic=vpc-load-balancer-faqs)
* [Quotas](https://cloud.ibm.com/docs/vpc?topic=vpc-quotasload-balancer-quotas)
-q
: Optional: Do not show the message of the day or update reminders.



 Example vlan ls command 

ibmcloud ks vlan ls --zone dal10







 ibmcloud ks vlan spanning get 

Classic infrastructure

View the VLAN spanning status for an IBM Cloud infrastructure account. VLAN spanning enables all devices on an account to communicate with each other through the private network, regardless of its assigned VLAN.

The VLAN spanning option is disabled for clusters that are created in a VRF-enabled account. When VRF is enabled, all VLANs in the account can automatically communicate with each other over the private network. To check whether a VRF is enabled, use the ibmcloud account show command. For more information, see [Planning your cluster network setup: Worker-to-worker communication](https://cloud.ibm.com/docs/containers?topic=containers-plan_basicsworker-worker).

ibmcloud ks vlan spanning get --region REGION [--output json] [-q]

Minimum required permissions
: Viewer platform access role for IBM Cloud Kubernetes Service

Command options:

--region REGION
: Specify a region in IBM Cloud Kubernetes Service: jp-osa, jp-tok, au-syd, eu-de, eu-gb, us-east, or us-south.

--output json
: Optional: Prints the command output in JSON format.

-q
: Optional: Do not show the message of the day or update reminders.



 Example vlan spanning get command 

ibmcloud ks vlan spanning get --region us-south









 vpcs command 

Virtual Private Cloud

List all VPCs in the targeted resource group. If no resource group is targeted, then all VPCs in the account are listed.

ibmcloud ks vpcs [--provider vpc-gen2] [--output json] [-q]

Minimum required permissions:



* Viewer platform access role for IBM Cloud Kubernetes Service



Command options:

--provider vpc-gen2