vania-janet/multiturn-rag-retrieval-data huggingface dataset:
For more information, see [About placement groups](https://cloud.ibm.com/docs/vpc?topic=vpc-about-placement-groups-for-vpc) or dive into the new [API methods](https://cloud.ibm.com/apidocs/vpclist-placement-groups).







 10 August 2021 



 For all version dates 

LinuxONE (s390x processor architecture). You can now [create virtual server instances](https://cloud.ibm.com/apidocs/vpccreate-instance) on LinuxONE in IBM Cloud® using new virtual server instance profiles. Instances provisioned with these profiles will have a VCPU architecture of s390x and interoperate with other VPC storage and networking features such as block storage volumes, floating IPs, and security groups. For more information, see [x86 instance profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-profiles&interface=apibalanced-s390x-profiles), and [Service limitations](https://cloud.ibm.com/docs/vpc?topic=vpc-limitations).







 27 July 2021 



 For version 2021-07-27 or later 

Instances. When you [create an instance](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers) using a version query parameter of 2021-07-27 or later, the value for the boot volume's capacity is now based on the image's minimum_provisioned_size. If you use a version query parameter of 2021-07-26 or earlier, the value for the boot volume's capacity will continue to be 100 GB.







 29 June 2021 



 For all version dates 

Keys. Pagination has been added to the [List all keys](https://cloud.ibm.com/apidocs/vpclist-keys) method. Pagination will not occur until your account includes more than 50 keys in a region, but we recommend that you update your existing client applications in preparation. Contact IBM support if you need assistance.







 15 June 2021 



 For all version dates
"id": "a342dbfb-3ea7-48d1-96e8-2825ec5feab4",
"href": "https://resource-controller.cloud.ibm.com/v2/resource_groups/
a342dbfb-3ea7-48d1-96e8-2825ec5feab4",
"name": "Default"
},
"volume_attachments": [],
"created_at": "2022-06-26T16:03:22.000Z"
}





 Next steps 

When you refresh the list of block storage volumes in the UI, the new volume appears at the beginning of the list of volumes with "customer managed" as the encryption type. When the volume is created, it shows a status of Available. For stand-alone volumes, the Attachment Type column is blank (-). The Action menu (...) at the end of a table row provides a link for [attaching a block storage volume to an instance](https://cloud.ibm.com/docs/vpc?topic=vpc-attaching-block-storage).

Interested in setting up key rotation for your customer-managed root keys? For more information, see [Key rotation for VPC resources](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-key-rotation).
Create a configuration file to define your persistent volume claim (PVC) and save the configuration as a .yaml file. The following example creates a claim that is named mypvc by using the ibmc-vpc-file-5iops-tier storage class, billed monthly, with a gigabyte size of 10Gi.

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: my-pvc
spec:
accessModes:
- ReadWriteMany
resources:
requests:
storage: 10Gi
storageClassName: ibmc-vpc-file-5iops-tier

name
: Enter the name of the PVC.

accessMode
: Specify one of the following options.



* ReadWriteMany: The PVC can be mounted by multiple pods. All pods can read from and write to the volume.
* ReadOnlyMany: The PVC can be mounted by multiple pods. All pods have read-only access.
* ReadWriteOnce: The PVC can be mounted by one pod only. This pod can read from and write to the volume.



storage
: Enter the size of the File Storage for VPC, in gigabytes (Gi). After your storage is provisioned, you can't change the size of your File Storage for VPC. Make sure to specify a size that matches the amount of data that you want to store.

storageClassName
: The name of the storage class that you want to use to provision File Storage for VPC. You can choose to use one of the [IBM-provided storage classes](https://cloud.ibm.com/docs/containers?topic=containers-storage-file-vpc-sc-ref) or [create your own storage class](https://cloud.ibm.com/docs/containers?topic=containers-vpc-blockcustom-sc-vpc-block). If you don't specify a storage class, the PV is created with the default storage class ibmc-vpc-file-3iops-tier.
2. Create the PVC.
This subsection is used to specify values for env variables if they are defined by the workload provider.





 The logging subsection 

The minimum subsection that is required for this section is the logging subsection. For more information, see [Logging for Hyper Protect Virtual Servers for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-logging-for-hyper-protect-virtual-servers-for-vpc).

The following snippet is an example of the logging subsection:

logging:
logDNA:
hostname: <host name of the Log Analysis instance>
ingestionKey: <ingestion Key of the Log Analysis instance>
port: <port default-6514>





 The env - volumes subsection 

Read the [workload - volumes](https://cloud.ibm.com/docs/vpc?topic=vpc-about-contract_sehpcr_contract_volumes) subsection of the workload section before you continue with this section. As already mentioned, for auto disk encryption of the attached data volume (currently only one disk is supported), you must provide two customer seeds, one in the workload - volumes subsection, and the other in the env- volumes subsection. The seeds can be any random text of your choice.

This is an example of the env - volumes subsection:

volumes:
test:
seed: env phrase

The name of the volume must be the same as that in the [workload - volumes](https://cloud.ibm.com/docs/vpc?topic=vpc-about-contract_sehpcr_contract_volumes) subsection.

As mentioned, you can integrate with Hyper Protect Crypto Services to generate a third seed and wrap it with your root key. See the following example. For more information, See [Securing your data](https://cloud.ibm.com/docs/vpc?topic=vpc-hyper-protect-virtual-server-mng-data).

volumes:
test:
kms:
* Updated instance-create , instance-create-from-template , instance-template-create and instance-template-create-override-source-template commands to support Enterprise Image Sharing.
* Updated ike-policy-create , ike-policy-update , ipsec-policy-create and ipsec-policy-update commands to support Additional Cipher Suites for VPN.







 Removed commands 



* N/A









 v5.2.0 

Version 5.2.0 was released on 2022-09-16.



 New commands 



* N/A







 Updated commands 



* Updated load-balancer-update command to support application load balancer subnet patch.







 Removed commands 



* N/A









 v5.1.0 

Version 5.1.0 was released on 2022-08-19.



 New commands 



* N/A







 Updated commands 



* Updated instance-create, instance-volume-attachment-add, instance-template-create commands to support user tags.







 Removed commands 



* N/A









 v5.0.1 

Version 5.0.1 was released on 2022-07-29.



 New commands 



* N/A







 Updated commands 



* N/A







 Removed commands 



* N/A







 Note 



* Fixed VPC CRI relogin issue.









 v5.0.0 

Version 5.0.0 was released on 2022-07-14.



 New commands 



* N/A







 Updated commands 



* Updated vpc-routing-table-create and vpc-routing-table-update commands to support custom routes for a VPN server.
* Updated security-group-target, security-group-target-add and security-group-target-remove commands to support a VPN server target.
* Updated vpn-server-create, and vpn-server-update commands to support the secrets manager.







 Removed commands 



* Removed VPC route commands vpc-routes,vpc-route, vpc-route-create, vpc-route-update and vpc-route-delete.







 Note 



* VPN server commands are available.









 v4.2.0
VPC reference architecture for IBM Cloud for Financial Services 

[IBM Cloud® Virtual Private Cloud (VPC)](https://cloud.ibm.com/docs/vpc?topic=vpc-about-vpcabout-vpc) is a public cloud offering that lets an enterprise establish its 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. The VPC reference architecture for the IBM Cloud for Financial Services is designed to provide a framework for building a VPC-based offering according to the [best practices and requirements](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-best-practices) of the IBM Cloud Framework for Financial Services. We detail this architecture and provide guidance for deploying, configuring, and managing it.



 Architecture diagram 

Zoom

![High-level VPC reference architecture for IBM Cloud for Financial Services](https://cloud.ibm.com/docs-content/v1/content/9ac5c38b41e0aa1cb4ccc6cc7f547751ec805221/framework-financial-services/vpc/images/vpc-high-level/vpc-high-level-v2.svg)

Figure 1. High-level VPC reference architecture for IBM Cloud for Financial Services

Central to the architecture are two VPCs, which provide for separation of concerns between provider management functionality and consumer workloads.

Management VPC
: Provides compute, storage, and network services to enable the application application provider's administrators to monitor, operate, and maintain the environment.

Workload VPC
: Provides compute, storage, and network services to support hosted applications and operations that deliver services to the consumer.

Other key features to note:



* Supports a single tenant.
* Resides in one or more [multizone regions](https://cloud.ibm.com/docs/overview?topic=overview-locations).
* The external IP is allocated when the public gateway is created.
* The external IP is released when the public gateway is deleted.







 Classic access 

The [classic access](https://cloud.ibm.com/docs/vpc?topic=vpc-setting-up-access-to-classic-infrastructure) feature for VPC is accomplished by reusing the VRF identifier from the IBM Cloud® classic infrastructure account as the VRF identifier for VPC. This implementation allows the VPC's implicit router function to join the same MPLS VPN that is used by the classic infrastructure account. Thus, the VPC has access to classic resources and to anything else that's reachable by using existing Direct-Link connections.
A finite pool of IP addresses is used for NAT operations on the VPC gateway. One IP address is required per VPC per zone.
* What does a VPN health status indicate?

Status descriptions are as follows:



* Heathy - Indicates that your VPN server is operating correctly.
* Degraded - Indicates that your VPN server has compromised performance, capacity, or connectivity.
* Faulted - Indicates that your VPN server is completely unreachable and inoperative.
* Inapplicable - Indicates that the health state does not apply because of the current lifecycle state. A resource with a lifecycle state of failed or deleting will have a health state of inapplicable. A Pending resource might also have this state.



* Why can't I save the password/passcode in the VPN client?

The passcode generated from [IBM IAM](https://iam.cloud.ibm.com/identity/passcode) is a Time-based One-Time Passcode (TOTP), which cannot be reused. You must regenerate it each time.
* If I update a VPN server with connected VPN clients, what happens to the VPN clients?

The VPN clients are disconnected along with the VPN server. All VPN clients need to re-connect with the VPN server again. When you use the user ID and passcode authentication, you have to retrieve the passcode and initiate the connection from your VPN client.
* Why is the VPN client disconnected?

The VPN server administrator can specify an idle time of the VPN client. When there is no traffic from the VPN client during the idle time window, the VPN server disconnects the client automatically. You must reinitiate the VPN session from your VPN client if it is disconnected.
* If I delete a VPN server with connected VPN clients, what happens to the VPN clients?

The VPN clients are disconnected along with the VPN server.
* What happens to a VPN server if I try to delete the subnet that the VPN server is on?

You cannot delete the subnet if any VPN servers are present.
VPC Terraform templates to provision resource using Schematics workspace

 Template Description Provision 

 [Multiple VSIs on VPC with block storage volume and a load balancer](https://github.com/Cloud-Schematics/vpc-vsi-with-volumes-and-lb) Provision multiple virtual servers each with a block storage volume on VPC, across a number of subnets, and connected with a single load balancer. ![Auto deployment button](https://cloud.ibm.com/docs-content/v1/content/4cd6263f39a034d265ddb4b0a5e6d50c55d13ee8/ibm-cloud-provider-for-terraform/images/autodeploy_button.png)[Deploy to IBM Cloud](https://cloud.ibm.com/schematics/workspaces/create?repository=https://github.com/Cloud-Schematics/vpc-vsi-with-volumes-and-lb&terraform_version=terraform_v0.12) <br> 
 [Multiple VPC running on production workload with a bastion worker for Rolling deployment](https://github.com/Cloud-Schematics/vpc-bastion-rolling-deploy) Provisioning VSIs on a VPC infrastructure to separate subnet for running production workload and a bastion worker for Rolling deployment. ![Auto deployment button](https://cloud.ibm.com/docs-content/v1/content/4cd6263f39a034d265ddb4b0a5e6d50c55d13ee8/ibm-cloud-provider-for-terraform/images/autodeploy_button.png)[Deploy to IBM Cloud](https://cloud.ibm.com/schematics/workspaces/create?repository=https://github.com/Cloud-Schematics/vpc-bastion-rolling-deploy&terraform_version=terraform_v1.0) <br>
messageID Required ID of the log that is generated. 
 msg_timestamp Required The timestamps when the log is generated. 
 resolution Optional Guidance on how to proceed if you receive this log record. 
 documentsURL Optional More information on how to proceed if you receive this log record. 
 generation Required Defines the VPC source of the log. Valid options are 1 for VPC Classic, and 2 for VPC Gen 2. 







 Log messages 

The following tables list the message IDs that are generated by VPC services:



 Flow log collector 

Table 2 outlines the message IDs that are generated by the flow log collector service:



Table 2. Message IDs that are generated by Flow Log Collector

 Message ID Type Learn More 

 is.flow-log-collector.00001E err [Failed to write Flow Log file for the past 24 hours. Dropping flow log for Virtual Server <ServerName>](https://cloud.ibm.com/docs/vpc?topic=vpc-fl-ts-error-failed-write) 
 is.flow-log-collector.00002E err [Unauthorized access to Cloud Object Storage bucket <BucketName>](https://cloud.ibm.com/docs/vpc?topic=vpc-fl-ts-error-unauth-access-cos) 
 is.flow-log-collector.00003E err [Cloud Object Storage bucket <BucketName> was not found](https://cloud.ibm.com/docs/vpc?topic=vpc-fl-ts-error-cos-bucket) 



Flow log collector generates hourly logs.





 Dedicated Host 

Table 3 outlines the message IDs that are generated for dedicated hosts:



Table 3. Message IDs that are generated for dedicated hosts

 Message ID Type Learn More 

 dedicated-host.00001 err [Failed to create dedicated host <Dedicated Host ID> due to insufficient capacity in zone.](https://cloud.ibm.com/docs/vpc?topic=vpc-why-did-a-dedicated-host-fail-to-create-)
Custom route states are:<br><br><br><br> * Pending - In the process of being provisioned in the specified VPC and zone.<br> * Stable - Provisioning was successful.<br> * Deleting - A Stable or Failed route is in the process of being deleted.<br> * Deleted - Deletion was successful.<br> * Failed - The route is not functional. From this state, you can delete only the route.<br><br><br> 
 Zone xxx 
 Action Values are:<br><br><br><br> * Deliver - Routes the packet to the next hop target. You can add multiple routes with the same address prefix. The virtual router performs equal-cost, multi-path routing (ECMP) by using the different next hop IP addresses.<br> * Drop - Drops the packet.<br> * Delegate - Routes the packet by using the system routing table. 1<br><br><br> 
 Next hop The IP address of the next hop to which to route packets. 
 Route origin Origin of the route. 



1 - A system routing table is maintained for each VPC. A VPC can have a presence in multiple zones, and the VPC's system routing table is different in each zone. It is used for routing traffic when no matching route is found in the custom routing table that is associated with the subnet of which the traffic is egressing.





 Listing routes of a routing table from the CLI 

Before you begin, make sure to [set up your CLI environment](https://cloud.ibm.com/docs/vpc?topic=vpc-infrastructure-cli-plugin-vpc-reference).

To view details of a route by using the CLI, run the following command:

ibmcloud is vpc-routing-table-route VPC ROUTING_TABLE ROUTE [--json]

Where:



* VPC is the ID of the VPC.
* ROUTING_TABLE is the ID of the VPC routing table.
* ROUTE is the ID of the VPC route.
* --json formats output in JSON.
2. In your resource definition of your Terraform configuration file, specify the provider configuration that you want to use. If you do not specify a provider, the default provider configuration is used.

resource "ibm_container_cluster" "cluster" {
provider = ibm.east
...
}

resource ibm_is_vpc "vpc" {
name = "myvpc"
}
3. Follow the [steps](https://cloud.ibm.com/docs/schematics?topic=schematics-manage-lifecycledeploy-resources) to deploy your IBM Cloud resources.
curl -X GET "$vpc_api_endpoint/v1/regions/us-south/zones?version=$api_version&generation=2" -H "Authorization: $iam_token"
* Call the GET Profiles API to see the profiles available for your virtual server instances, in JSON format. At least one object should return.

Add | json_pp after the curl command to get a readable JSON string.

curl -X GET "$vpc_api_endpoint/v1/instance/profiles?version=$api_version&generation=2" -H "Authorization: $iam_token"
* Call the GET Images API to return the images available for your instances, in JSON format. At least one object should return.

curl -X GET "$vpc_api_endpoint/v1/images?version=$api_version&generation=2" -H "Authorization: $iam_token"
* Call the GET VPCs API to see any VPCs that were already created under your account, in JSON format.

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



To learn how to create resources by using the API, see [Creating VPC resources with CLI and API](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-vpc-resources-with-cli-and-api&interface=cli).
ibmcloud is instance-create INSTANCE_NAME VPC ZONE_NAME PROFILE_NAME SUBNET --image-id IMAGE_ID [--boot-volume @BOOT_VOLUME_JSON_FILE] [--volume-attach @VOLUME_ATTACH_JSON_FILE]...







 Provisioning instances with customer-managed encryption volumes with the API 

You can provision instances with customer-managed encryption volumes by calling the Virtual Private Cloud (VPC) API.

Make a POST/instances request to create an instance and new volume encrypted using your own encryption keys. The encryption_key parameter identifies the CRN of your customer root key, shown in the example as crn:[...key:...].

The following example creates an instance with a boot volume with customer-managed encryption and two secondary volumes with customer-managed encryption.

curl -X POST "$vpc_api_endpoint/v1/instances?version=version=2020-03-10&generation=2" -H "Authorization: $iam_token" -d '{
"boot_volume_attachment": {
"volume": {
"name": "boot-volume-1"
"profile": {
"name": "general-purpose"
},
"encryption_key": {
"crn": "crn:[...key:...]"
}
}
},
"volume_attachments": [
{
"volume": {
"name": "my-volume-1"
"capacity": 50,
"profile": {
"name": "general-purpose"
},
"encryption_key": {
"crn": "crn:...key:...]"
}
}
},
{
"volume": {
"name": "my-volume-2"
"capacity": 20,
"profile": {
"name": "general-purpose"
},
"encryption_key": {
When the [IEE254I](https://www.ibm.com/docs/en/zos/2.5.0?topic=iee399i-iee254i) message is displayed, the ID is included in the VM EXT NAME.





 Viewing instance status and lifecycle_state in the API 



* status



* This property provides the current status of the virtual server instance through the [Retrieve an instance](https://cloud.ibm.com/apidocs/vpc/latestget-instance) request. The values that status returns are specialized for virtual server instances and indicate if it is running, stopped, or transitioning. For more information, see the [Virtual Private Cloud API](https://cloud.ibm.com/apidocs/vpc/latest) content.



* lifecycle_state



* This property provides the current state of a resource through the [Retrieve an instance](https://cloud.ibm.com/apidocs/vpc/latestget-instance) request. The values that lifecycle_state provides are generic and are meant to apply to a variety resources, such as [Placement groups](https://cloud.ibm.com/docs/vpc?topic=vpc-about-placement-groups-for-vpc). lifecycle_state can return values that overlap with status. lifecycle_state also includes values that detail if a resource is suspended.









 Setting the host failure auto restart using the UI 

To set the host failure auto restart for an existing instance, complete the following steps.



1. In [IBM Cloud console](https://console.cloud.ibm.com), navigate to Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Compute > Virtual server instances.
2. On the Virtual server instances page, click the Actions icon !
* ibmcloud is vpc-routing-table-route-update vpc1001 routing-table-vpc1001-1-name vpc-route-cli-demo-1001 --priority 3 --next-hop 541c6bbf-6109-44bd-b2c9-176c6e11bc59 --vpngw aaa-default-vpn-gateway-1 --name vpc-route-cli-demo-1003







 Command options 



* VPC: ID or name of the VPC.
* ROUTING_TABLE: ID or name of the VPC routing table.
* ROUTE: ID or name of the VPC route.
* --name: New name of the route.
* --priority: The route's priority. Smaller values have higher priority. Values can range between 0-4. (default: 2).
* --next-hop: If the action is deliver, then the IP address, VPN connection ID, or name of the next-hop that packets are delivered to. For other action values, it must be omitted or specified as 0.0.0.0.
* --vpngw: ID or name of the VPN gateway. This option is required only if the next-hop is specified as VPN connection in name format.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is vpc-routing-table-route-delete 

Delete one or more VPC routes.

ibmcloud is vpc-routing-table-route-delete VPC ROUTING_TABLE (ROUTE1 ROUTE2 ...) [--output JSON] [-f, --force] [-q, --quiet]



 Command options 



* VPC: ID or name of the VPC.
* ROUTING_TABLE: ID or name of the VPC routing table.
* ROUTE1: ID or name of the VPC route.
r134-f83ce520-00b5-40c5-9938-a5c82a273f91 ibm-debian-11-3-minimal-amd64-4

VPC ID Name
r134-35b9cf35-616e-462e-a145-cf8db4062fcf my-vpc

Zone us-south-2
Resource group ID Name
cdc21b72d4e647b195de988b175e3d82 Default

Created 2023-03-23T21:50:24+00:00
Boot volume ID Name Attachment ID Attachment name
- - 0726-7ccd4284-e59d-45d8-932a-9e52f62f187a landing-faucet-prankish-sprout

Information about the network interfaces that are created for the new instance aren't returned after the instance is created. You can view the information by using the ibmcloud is instance INSTANCE command as described in the following step. The status displays pending until the instance is created.

For more information about some additional features that you can include as command options on the instance-create command, see the following topics: [Create a volume attachment JSON](https://cloud.ibm.com/docs/vpc?topic=vpc-attaching-block-storage&interface=clivolume_attachment_json), [Enable or disable the metadata service](https://cloud.ibm.com/docs/vpc?topic=vpc-imd-configure-service&interface=cliimd-enable-on-instance-cli), and [Creating a placement group](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-placement-group&interface=clicreating-placement-group-CLI).

For a full list of command options, see [ibmcloud is instance-create](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-referenceinstance-create).
2.