vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Accounts that have been granted special approval to preview this feature can now [update the IOPS of an existing file share](https://cloud.ibm.com/apidocs/vpc-betaupdate-share). For a file share using a custom profile, specify the iops property. For a file share using a profile in the tiered profile family, specify another tier within the tiered family, which will set the iops based on the share's size.

You can also change a share between the tiered and custom profile families so long as the requested iops and size are supported by the requested profile. For more information about file share profiles, see [File Storage for VPC profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profiles). For information about adjusting IOPS with a profile, or changing between tiered and custom profiles, see [Adjusting file share IOPS](https://cloud.ibm.com/docs/vpc?topic=vpc-adjusting-share-iops&interface=api).







 31 May 2022 



 For all version dates 

AMD support for instances and dedicated hosts. Accounts that have been granted special approval to preview this feature can select new profiles for [dedicated hosts](https://cloud.ibm.com/apidocs/vpc-betalist-dedicated-host-profiles) and [instances](https://cloud.ibm.com/apidocs/vpc-betalist-instance-profiles). When provisioning or managing an instance or dedicated host, use the new vcpu_manufacturer property to choose between profiles from different processor manufacturers.

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







 24 May 2022 



 For all version dates 

Backup for VPC. Accounts with special approval to preview this feature can now [create](https://cloud.ibm.com/apidocs/vpc-betacreate-backup-policy-plan) up to four plans for backup policies.
When you [create a block storage volume from the IBM Cloud console](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-block-storage), select Tiers.

Alternately, select Custom and then select an IOPS value within the range for that volume size. Click the storage size link to see a table of size and IOPS ranges.





 From the CLI 

To view the list of available profiles by using the CLI, run the following command:

ibmcloud is volume-profiles

$ ibmcloud is volume-profiles
Listing volume profiles in region us-east under account TEST as user test.user@ibm.com...
Name Family
general-purpose tiered
5iops-tier tiered
10iops-tier tiered
custom custom

To view details of the profile, run the ibmcloud is volume-profile command with the name of the profile that you are interested in seeing.

The following example shows the details of the 10iops-tier.

$ ibmcloud is volume-profile 10iops-tier
Getting volume profile 10iops-tier under account Test Account as user test.user@ibm.com...

Name 10iops-tier
Family tiered
Adjustable IOPS false
Boot capacity Max Min
250 10

Capacity Max Min Default Step
4800 10 10 1

IOPS Max Min Default Step
48000 10 10 1

Unattached capacity update supported false
Unattached iops update supported false

For more information about available command options, see [ibmcloud is volume-profile](https://cloud.ibm.com/docs/cli?topic=cli-vpc-referencevolume-profile).





 With the API 

To see the available profiles, make a GET /volume/profiles call.

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

To see details of a specific profile, make a GET /volume/profile request and specify the name of the profile.
Why can't I find the reserved IP addresses that are associated with an endpoint gateway? 

A reserved IP address is part of a subnet. If the subnet gets deleted, all reserved IP addresses that belong to the subnet are deleted.

  What’s happening 

Cannot find reserved IP addresses that are associated with an endpoint gateway.

  Why it’s happening 

It is possible that the reserved IP address that is associated with the endpoint gateway was automatically deleted with the subnet.

  How to fix it 

You can re-create a reserved IP address, but cannot recover reserved IP addresses that were associated with a deleted subnet.
Dive into the APIs to [import an encrypted image](https://cloud.ibm.com/apidocs/vpccreate-image) and [provision an instance](https://cloud.ibm.com/apidocs/vpccreate-instance) from that encrypted image. See also [Creating an encrypted custom image](https://cloud.ibm.com/docs/vpc?topic=vpc-create-encrypted-custom-image).







 31 August 2020 



 For all version dates 

Network load balancers. You can now use the [load balancers API](https://cloud.ibm.com/apidocs/vpclist-load-balancer-profiles) to distribute traffic among multiple server instances within the same region of your VPC. To learn how to create and manage a network load balancer, see [About IBM Cloud Network Load Balancer for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-network-load-balancers).

The network load balancers API is shared between IBM Cloud application load balancers and network load balancers.







 25 August 2020 



 For all version dates 

This API release supports the following changes:



* Create an instance group of a fixed size and use it as a stand-alone feature
* Use the instance group manager to manage the instance group, which can associate an auto scale policy with that group



For more information, see [Creating an instance group for auto scaling](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-auto-scale-instance-group).

The following new methods are available for [instance groups](https://cloud.ibm.com/apidocs/vpclist-instance-groups):



* GET and POST for /instance_groups
* DELETE, GET, and PATCH for /instance_groups/{id}
* DELETE for /instance_groups/{instance_group_id}/load_balancer
* GET and POST for /instance_groups/{instance_group_id}/managers
* UI
* CLI
* API







 Managing IP addresses 

The reserved IPs capability on VPC allows you to reserve IP addresses for use on your resources. You can specify a particular address or allow the system to select any available address. You can also make a new IP reservation with or without a target with which to bind the address.



 Before you begin 

Reserved IPs are a sub-resource of subnets. Identity and Access Management (IAM) does not currently have support for sub-resources, so reserved IPs "inherit" permissions from the subnet.

To see the IAM permissions required for reserved IPs, see [Subnets calls](https://cloud.ibm.com/docs/vpc?topic=vpc-resource-authorizations-required-for-api-and-cli-callssubnets-authorizations-required-for-api-and-cli-calls).

VPC does not support fragmented IP packets. Fragmented packets are dropped at the edge.





 Creating reserved IPs in the UI 

To create a reserved IP, follow these steps:



1. From the IBM Cloud menu, select VPC Infrastructure > Subnets.
2. Select an existing subnet, or create a new one.
3. Click the Reserved IPs tab.
4. Click Create +.



The following sections describe working with reserved IP addresses with different attributes.



 Creating an unassociated reserved IP 

To create an unassociated reserved IP, follow these steps:



1. Enter a name for your reserved IP.
2. Select whether you want to have the system choose a reserved IP for you automatically, choose from a list of existing reserved IPs, or enter one yourself.
3. Select an address, if you require a specific IP address (optional).
4. Click Reserve IP.







 Deleting a reserved IP 

To delete (release) a reserved IP using the UI, navigate to Subnets > Reserved IPs and click the actions menu !
Message: Pool protocol is missing.

Pool protocol is a required field. Provide the pool protocol in your request. The acceptable values are http and tcp.





 pool_not_found 

Message: The pool with ID <pool_id> cannot be found.

Provide an existing pool ID.





 pool_over_quota 

Message: Pool cannot be created. Quota of pools for the load balancer resource has reached maximum limit.

The quotas per resource are specified in [Quotas and limits for VPC](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-quotas).





 public_gateway_in_use 

Message: Cannot delete a public gateway when it is in use.

The public gateway currently is attached to one or more subnets. You must detach the public gateway from all subnets before you can delete it.

To see which subnet is using the public gateway, use the GET /v1/subnets?version=$version&generation=1 API. Equivalent CLI command: ibmcloud is subnets. To detach the public gateway from the subnet, use the API command DELETE /v1/subnets/{subnet_id}/public_gateway?version=$version&generation=1 or the CLI command ibmcloud is subnet-public-gateway-detach.





 rate_limit_exceeded 

Message: Too many requests within a short time.

This error message is returned if too many requests are received within a specified time interval. Wait a while and try again.





 reserved_ip_in_use 

Message: The reserved IP is in use and cannot be deleted.

To see a list of reserved IP addresses, use the GET /v1/subnets/{subnet_id}/reserved_ips API, or the CLI command ibmcloud is subnet-reserved-ip and make sure that the specified reserved IP address is not in use.





 reserved_ip_owned_by_provider 

Message: The specified reserved IP is owned by the provider.
Bring your own license 

For Red Hat Enterprise Linux® and Windows operating systems, you can bring your own license (BYOL) to the IBM Cloud® VPC when you import a custom image. These images are registered and licensed by you. You maintain control over your license and incur no additional costs by using your license. Acquisition and activation of the license is between you and the OS vendor.



 BYOL concepts 

With the BYOL feature, you can use your own license for a custom image that you create at your site and then upload to IBM Cloud Object Storage. When you import your custom image from IBM Cloud Object Storage to the VPC, IBM Cloud provides Red Hat Enterprise Linux and Windows BYOL operating system options that you must select to indicate that you are using a BYOL operating system. You use your BYOL custom images to create virtual server instances, just as you would from a stock image.

The BYOL feature on LinuxONE (s390x processor architecture) supports Red Hat Enterprise Linux (RHEL), and SUSE Linux Enterprise Server (SLES) operating systems.

Images with a Red Hat Enterprise Linux BYOL or a Windows BYOL operating system can be used to provision an instance on a public or dedicated host.

You don't have extra licensing charges for any virtual server instances that you create by using your BYOL custom image. For auditing and reporting purposes, IBM Cloud retains information for virtual server instances that you create from BYOL custom images.





 BYOL for Red Hat Enterprise Linux operating systems 

You can use your own license for a [custom RHEL image](https://cloud.ibm.com/docs/vpc?topic=vpc-create-linux-custom-image) that you create on premises. This BYOL custom image is a single qcow2 or vhd file that you upload to IBM Cloud Object Storage and then import to the VPC. When you import your BYOL custom image, you must select a BYOL operating system from the list of OS versions. Supported Linux versions are 64-bit RHEL 7 and RHEL 8.

To see all of the operating system versions from the API, make a GET /operating_systems call. In the response, you see Red Hat Enterprise Linux BYOL OS versions among the list of operating systems.
2022-03-29 API migration 

As described in [Versioning](https://cloud.ibm.com/apidocs/vpcapi-versioning), most changes to the VPC APIs are fully backward compatible and therefore are made available to all clients, regardless of the API version the client requests. However, the 2022-03-29 release of the VPC API necessitated incompatible changes in support of the reserved IP addresses feature:



* IP addresses are now modeled as objects (resources), rather than strings.
* Security groups must now be associated with targets rather than network interfaces.



If your clients continue to specify version 2022-03-28 or earlier of the VPC API, no changes are required, but those clients remain unable to fully benefit from reserved IP addresses. For more information about reserved addresses, see [Managing IP addresses](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-ip-addresses).

Even if you are not planning to use reserved IP addresses, to avoid regressions in client functionality, be sure to read and follow the [action needed](https://cloud.ibm.com/docs/vpc?topic=vpc-2022-03-29-migrationaction-needed) before your client specifies version 2022-03-29 or later.

The [VPC Instance Metadata API](https://cloud.ibm.com/apidocs/vpc-metadata) does not yet support reserved IP addresses. Clients that use the metadata API do not require changes to use version 2022-03-29 or later.



 Action needed 

Before the client specifies version 2022-03-29 or later, follow these actions to avoid regressions in client functionality.



 Migrating use of IP addresses 

Before you migrate a client to API version 2022-03-29 or later, review your code for any use of the primary_ipv4_address property.
Release notes for Planning Analytics as a Service 

Use these release notes to learn about the latest updates to Planning Analytics as a Service, grouped by date. Release notes are available for a minimum of three years. All updates to components within Planning Analytics as a Service are cumulative and include new features and fixes from prior releases.



 21 June 2023 

Planning Analytics Workspace update
: Planning Analytics Workspace within Planning Analytics as a Service has been updated to version 2.0.88.
: For more information on new and changed features in Planning Analytics Workspace 2.0.88, see [What's new in Planning Analytics Workspace](https://www.ibm.com/docs/en/planning-analytics/2.0.0?topic=workspace-2088-whats-new-june-21-2023). To see which issues were fixed in this Planning Analytics Workspace update, review the [Planning Analytics Workspace 2.0.88 fix list](https://www.ibm.com/support/pages/system/files/inline-files/ibm_fixlist_planning_analytics_workspace_2088_sc.pdf).

Planning Analytics Spreadsheet Services update
: Planning Analytics Spreadsheet Services/TM1 Web within Planning Analytics as a Service has been updated to version 2.0.88.
: For more information on new and changed features in Planning Analytics Spreadsheet Services/TM1 Web version 2.0.88, see [What's new in Planning Analytics Spreadsheet Services](https://www.ibm.com/docs/en/planning-analytics/2.0.0?topic=web-2088-feature-updates-june-16-2023). To see which issues were fixed in this Planning Analytics Spreadsheet Services update, review the [Planning Analytics Spreadsheet Services 2.0.88 fix list](https://www.ibm.com/support/pages/system/files/inline-files/ibm_fixlist_planning_analytics_spreadsheet_services_2088_sc.pdf).

Planning Analytics Engine update
: Planning Analytics Engine within Planning Analytics as a Service is version 12.2.0.





 16 May 2023 

Planning Analytics Workspace update
Certain IP address ranges are reserved. More information about reserved IP ranges is available in our overview of [Using your VPC with Regions and Subnets](https://cloud.ibm.com/docs/vpc-on-classic-network?topic=vpc-on-classic-network-working-with-ip-address-ranges-address-prefixes-regions-and-subnets).





 validation_invalid_ipv4_cidr 

Message: The value is not a valid IPv4 CIDR.

Must be a IPv4 internal CIDR block with a 0 host part.

Certain IP address ranges are reserved. More information about reserved IP ranges is available in our overview of [Using your VPC with Regions and Subnets](https://cloud.ibm.com/docs/vpc-on-classic-network?topic=vpc-on-classic-network-working-with-ip-address-ranges-address-prefixes-regions-and-subnets).





 validation_invalid_ipv6_cidr 

Message: The value is not a valid IPv6 CIDR.

Currently, IPv6 is not supported, use an IPv4 address.





 validation_invalid_address 

Message: The value is not a valid address.

Must be a valid IP address.

A list of individually reserved IP addresses is given in the [Regions and Subnets](https://cloud.ibm.com/docs/vpc-on-classic-network?topic=vpc-on-classic-network-working-with-ip-address-ranges-address-prefixes-regions-and-subnets) document.





 validation_invalid_ipv4_address 

Message: The value is not a valid IPv4 address.

Provide a valid IPv4 address.





 validation_invalid_ipv6_address 

Message: The value is not a valid IPv6 address.

Give a valid IPv6 address. Currently, IPv6 is not supported; use an IPv4 address.





 validation_invalid_field_type 

Message: The value type does not match the field type.
As an example, the load balancer can be configured to receive incoming web/HTTP traffic on front-end port 80, while the back-end servers are listening on custom port 81.

The supported front-end ports/protocols are HTTP, HTTPS, and TCP. The supported back-end ports/protocols are also HTTP, HTTPS, and TCP. Incoming HTTPS traffic must be terminated at the load balancer to allow for plain text HTTP communication with the back-end server. If the back-end protocol is HTTPS, the traffic is encrypted between load balancer and back-end servers.



 Considerations 



* During the initial configuration, you can define up to two front-end ports only. After a load balancer is created, you can edit port configuration to define additional ports, up to the maximum of 10 ports.
* All 10 front-end ports must map to the same set of back-end server instances.
* The maximum number of server instances that can be placed behind a load balancer is 50.
* The port range of 56500 to 56520 is reserved for management purposes and cannot be used as front-end virtual ports.
* TCP port 56501 is used for management. If you choose to allocate load balancer public IP addresses from your public VLAN, ensure that traffic to this management port as well as your application's ports are not blocked by any firewalls you might have deployed on your public VLANs. This is not required if you choose the IBM system pool option to allocate load balancer public IP addresses.









 Load-balancing methods 

The following three load-balancing methods are available for distributing traffic among back-end application servers:



* Round Robin - Round Robin is the default load-balancing method. With this method, the load balancer forwards incoming client connections in round-robin fashion to the back-end servers. As a result, all back-end servers receive roughly an equal number of client connections.
* Weighted Round Robin - With this method, the load balancer forwards incoming client connections to the back-end servers in proportion to the weight assigned to these servers. Each server is assigned a default weight of 50, which you can customize to any value in the range 0 - 100.
You can now use the subscription kafka commands to create, update, list, delete, and get information about Kafka event subscriptions.<br> * Fixed various bugs.<br><br><br> 
 1.35.0 16 June 2022 <br><br> * Added support for Linux 64 bit ARM for Code Engine CLI.<br> * Fixed various bugs.<br> * Updated translations for the CLI.<br><br><br> 
 1.34.0 09 June 2022 Important: This version introduces support for running builds from local or repository source code with a single CLI command. You can now use the buildrun submit command to run one build run without the need to reference a build configuration.<br><br><br><br> * The --build option to reference a build configuration is no longer required on the buildrun submit command. You can specify the --name option with other build options to run a single build with the buildrun submit command. The --build option is still available if you are referencing a build configuration.<br> * Added the following build options to the buildrun submit command: --commit, --context-dir, --dockerfile, --git-repo-secret, --registry-secret, --size, and --strategy.<br> * The subscription cron, and subscription cos commands are grouped into their subscription types (cron and cos) in the CLI Reference [Code Engine CLI Reference](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli). There are no changes to the commands themselves.<br> * Fixed various bugs.<br><br><br> 
 1.33.1 02 June 2022 <br><br> * Fixed various bugs.<br> * Upgraded to Go 1.18.3.<br><br><br> 
 1.33.0 26 May 2022 <br><br> * Updated the build create command so that the --image and --registry-secret options are no longer required.
* UI
* CLI
* API







 Binding and unbinding a reserved IP address 

You can bind and unbind a reserved IP address to an endpoint gateway by using the UI, CLI, and API.



 Binding and unbinding a reserved IP address in the UI 

You can bind or unbind a reserved IP address to an endpoint gateway by using the UI.



 Binding a reserved IP address 

To reserve or bind an IP address by using the IBM Cloud® console:



1. From the [IBM Cloud console](https://cloud.ibm.com/login), select the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/vpc//images/menu_icon.png), then click VPC Infrastructure > Virtual private endpoint gateways in the Network section. The Virtual private endpoint gateways for VPC page appears.
2. Highlight the row of the gateway in the table, then click Reserve or bind IP from the Actions menu ![Actions menu](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/vpc/images/overflow.png). Alternatively, you can click the gateway name and access this link from the endpoint gateway's details page.

If you did not reserve or bind an IP during endpoint gateway creation, this link appears in the IP address column in the table.
3. From the Reserved IP side panel, have IBM select an IP address for you from the subnet that is listed, or select from existing IPs.

You can bind only one reserved IP to one endpoint gateway from each zone. To bind a reserved IP to an endpoint gateway, you must have an existing subnet. You need to also make sure that no subnets of the VPC that are bound to the same zone.
4.
[max_replication_slots](https://www.postgresql.org/docs/current/runtime-config-replication.html)



* Default - 10
* Restarts database - YES
* Notes - The maximum number of simultaneously defined replication slots. The default and minimum number of slots is 10. Twenty slots are reserved for internal use by your deployment for High-Availability (HA) purposes. To use slots, you need to set the value above 20 and have one slot per consumer. It is recommended to add one extra slot over the minimum per expected consumer. Using wal2json and not increasing max_replication_slots can impact HA and read-only replicas. If you are not using wal2json, you should leave this setting at the default.



[max_wal_senders](https://www.postgresql.org/docs/current/runtime-config-replication.html)



* Default - 12
* Restarts database - YES
* Notes - The maximum number of simultaneously running WAL sender processes. The default and minimum is 12. One wal_sender per consumer is required. Twenty slots are reserved for internal use by your deployment for High-Availability (HA) purposes. You need to set the value higher than 20 and it is recommended to add one extra wal_sender over the minimum per expected consumer. Using wal2json and not increasing max_wal_senders can impact HA and read-only replicas. If you are not using wal2json, you should leave this setting at the default.