vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Supported for Dedicated and Connect offerings through automation. Need to store the MD5 secret in Key Protect or an HPCS instance in the customer account. 
 Default BGP IP address range for automation 10.254.0.0/16 169.254.0.0/16 
 Manual IP address range supported None 172.16.0.0/12, 192.168.0.0/16, 10.254.0.0/16, any public IP addresses 
 BGP ASN supported Allowed to use any ASN outside these blocked ranges: 0, 13884, 36351, 64512, 64513, 65100, 65201 – 65234, 65402 – 65433, 65500, and 4201065000 – 4201065999 2-byte range: 1 - 64495 or 64999 <br>2-byte or 4-byte range: 131072 - 4199999999 <br>4-byte range: 4201000000 - 4201064511 <br>Excluded ASNs: 0, 13884, 36351, 64512, 64513, 65100, 65201‍–‍65234, 65402‍–‍65433, 65500, and 4201065000‍–‍4201065999. 
 Billing Supports only monthly flat rate billing. Metered based on the data utilization and unmetered flat rate support. 
 VPC connectivity No VPC connectivity — can connect only to SoftLayer classic networks. Supports connectivity to multiple VPCs and connects to SoftLayer classic networks. 
 Cross-account connectivity Allows classic network connectivity within the account only. Allows VPC connectivity between IBM Cloud accounts, except for classic-access VPCs (see Adding a cross-account (VPC only) connection for details). 
 Bring Your Own IP (BYIOP) No BYOIP support. Supports BYOIP for non-overlapping RFC-1918 IP ranges between VPC networks and on-premise networks (see [Routing considerations for IANA-registered IP assignments](https://cloud.ibm.com/docs/vpc?topic=vpc-interconnectivity) for details). 
 Pricing Global routing has a monthly flat rate charge. Free global routing.
[VMware ESXi](https://cloud.ibm.com/docs/vpc?topic=vpc-bare-metal-imagebare-metal-images-vmware-esxi-considerations) x86-64 





 Special considerations for Red Hat Enterprise Linux 8.4 

By default, the release lock feature for RHEL 8.4 is disabled. To prevent the RHEL from going beyond version 8.4 when you run an update, run the following commands from the command line:

 subscription-manager release --set=8.4

 yum clean all





 Special considerations for VMware ESXi images 



* If you want to use TPM with a ESXi image, make sure that secure boot mode is enabled.
* The ESXi 7.x option provides ESXi in licensed mode and is activated during the provisioning process. Billing applies for IBM Cloud® rented licenses.
* ESXi on Bare Metal Servers for VPC is charged monthly and is calculated per CPU based on the selected profile. If you choose to rent VMware ESXi with your server, you are subject to a prorated monthly cost for the license instead of an hourly rate. Proration amount is variable based on your billing anniversary date.



For more information about how to license ESXi, see [Licensing ESXi hosts](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.esxi.install.doc/GUID-28D25806-748B-49C0-97A1-E7DE5CB335A9.html).





 Special considerations for Ubuntu images 

Ubuntu images don't include the VMD device driver in the standard kernel package that is needed to view attached NVMe drives on the system. To obtain this driver, install the linux-modules-extra-ibm package and then run modprobe vmd.

 export DEBIAN_FRONTEND=noninteractive
 apt update
Dedicated Host Very High Memory profile option for Intel x86-64 virtual server instances.

 Dedicated host profile vCPU Cores GiB RAM Instance storage 

 vx2d-host-176x2464 176 88 2464 5280 GB 



For more information about instance profiles that include instance storage in the Very High Memory family, see [very high memory profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-profilesvhmemory).

Dedicated hosts have a network performance cap of 80 Gbps. Instances provisioned on the host share bandwidth across the instances.





 Ultra High Memory with instance storage 

The Ultra High Memory with instance storage profile is best for in-memory OLTP databases, such as SAP. They are optimized for running memory intensive applications and in-memory databases such as SAP HANA, Memcached, or Redis. This profile family offers our highest vCPU to memory ratio with 28 GiB of memory for every 1 vCPU of compute and up to 5.7 TiB of available RAM.

The Ultra High Memory profile is hosted exclusively on the latest generation Intel® Xeon® Platinum 8280L Cascade Lake server with 112 cores that are running a base speed of 2.7 GHz and an all-core turbo frequency of 4.0 GHz. The Ultra High Memory profile is provisioned with temporary SSD-backed [Instance Storage](https://cloud.ibm.com/docs/vpc?topic=vpc-instance-storage) at no additional charge.

If you provision a dedicated host with an Ultra High Memory profile, any virtual server instances that are provisioned on the dedicated host must also be provisioned with an Ultra High Memory profile. All Ultra High Memory profiles include instance storage that is designated by the d in the profile name, for example ux2d.

The following Ultra High Memory profile is available for dedicated hosts.

Intel x86-64



Table 11. Intel x86-64 ultra high memory profile for dedicated hosts
Dedicated Host Ultra High Memory profile option for Intel x86-64 virtual server instances.

 Dedicated host profile vCPU Cores GiB RAM Instance storage 

 ux2d-host-200x5600 200 100 5600 6000 GB
Both examples assume an IBM Cloud Kubernetes service cluster and the default CouchDB database is used as the peer database. It also assumes peers are deployed with Fabric v2.x images instead of Fabric v1.4 images.



* The Test network scenario is suitable for getting started with your first use case with IBM Blockchain and testing smart contracts.
* The Join a network scenario includes two peers, and a Certificate Authority (CA) that is required for organization membership.



* These peers can join a production IBM Blockchain Platform network that is hosted elsewhere.
* Nodes can always be dialed back to a minimal utilization state (0.001 CPU) when they are not in use to [lower costs](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-govern-components).
* Because this scenario could be used for a production environment:



* The default compute resources have been doubled to provide greater capacity.
* The [Silver](https://cloud.ibm.com/docs/containers?topic=containers-file_storagefile_storageclass_reference) storage class is chosen for faster performance.









Table 1. Pricing examples for a test network and joining a network

 Pricing options** (1 VPC = 1 CPU = 1 vCPU) Test Network Join a Network 

 CPU allocation 1.25 vCPU <br>Includes: <br>- 1 peer (0.7 vCPU) <br>- 2 CAs (0.1 vCPU x 2) <br>- 1 ordering node (0.35 vCPU) 2.9 vCPU <br>Includes: <br>- 2 peers (for HA) <br>(2x default compute = 2 x 0.7 x 2) <br>- 1 CA (0.1) <br> 
 Hourly cost: IBM Blockchain Platform $0.46 USD <br>(1.25 vCPU x $0.29 USD/VPC-hr) $0.81 USD <br>(2.9 vCPUx $0.29 USD/VPC-hr )
List the PVCs in your cluster and note the NAME of the PVC, the STORAGECLASS, and the name of the PV that is bound to the PVC and shown as VOLUME.

kubectl get pvc

Example output

NAME STATUS VOLUME CAPACITY ACCESSMODES STORAGECLASS AGE
claim1-block-bronze Bound pvc-06886b77-102b-11e8-968a-f6612bb731fb 20Gi RWO ibmc-block-bronze 78d
claim-file-bronze Bound pvc-457a2b96-fafc-11e7-8ff9-b6c8f770356c 4Gi RWX ibmc-file-bronze-retain 105d
claim-file-silve Bound pvc-1efef0ba-0c48-11e8-968a-f6612bb731fb 24Gi RWX ibmc-file-silver 83d
2. Review the ReclaimPolicy and billingType for the storage class.

kubectl describe storageclass <storageclass_name>

If the reclaim policy says Delete, your PV and the physical storage are removed when you remove the PVC. Note that VPC Block Storage is not removed automatically, even if you used a Delete storage class to provision the storage. If the reclaim policy says Retain, or if you provisioned your storage without a storage class, then your PV and physical storage are not removed when you remove the PVC. You must remove the PVC, PV, and the physical storage separately.

If your storage is charged monthly, you still get charged for the entire month, even if you remove the storage before the end of the billing cycle.
3. Remove any pods that mount the PVC. List the pods that mount the PVC. If no pod is returned in your CLI output, you don't have a pod that uses the PVC.
Within VPC Infrastructure Services access, Dedicated Host for VPC access is given as a set of permissions, including access to dedicated hosts, dedicated host groups, and to provision instances on dedicated hosts. If you want to assign granular access for users to a specific resource, such as a dedicated host group, you can create a separate [resource group](https://cloud.ibm.com/docs/account?topic=account-rgs) for that resource with a separate access policy and minimum access role assigned. For more information about dedicated host permissions, see [Required permissions](https://cloud.ibm.com/docs/vpc?topic=vpc-resource-authorizations-required-for-api-and-cli-calls).

You can also view usage information for your dedicated hosts including estimated charges and resources that are used. For more information, see [Viewing your usage](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-viewingusage).





 Dedicated host groups 

A dedicated host group is a collection of dedicated hosts in a single region and zone. When you create a dedicated host, you must assign it to a dedicated host group. A dedicated host can be a member of only one group.

You can create dedicated host groups that contain dedicated hosts for a distinct function. For example, if you have multiple business units within your organization, you might want to separate the physical compute infrastructure that is used by each business. If you want to assign compute resources to be used by only one business group within your organization, you can create a group with dedicated hosts for that unique goal.

When you provision an instance, you can provision it to either a dedicated host or to a dedicated host group.





 Creating dedicated hosts and groups by using the console 

You can create one or more dedicated hosts in your IBM Cloud VPC by using the IBM Cloud console.

Before you can create a dedicated host, you need to [create an IBM Cloud VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-using-the-ibm-cloud-console).

If you do not already have a dedicated group, you must create it as part of this task.
Windows Server 2012 r2 full standard 10 October 2023 Pay-as-you-Go / BYOL 
 Windows Server 2019 Standard Edition with SQL Server 2019 Web Edition 08 January 2030 Pay-as-you-Go 



BYOL: For Windows operating systems, you can bring your own license (BYOL) to 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.

SQL Server: For more information about Windows operating systems with SQL Server, see the [About Microsoft SQL on VPC](https://cloud.ibm.com/docs/microsoft?topic=microsoft-mssql-about) documentation for information on creating the SQL server.
The simplified model is based on the amount of CPU (or VPC) that your IBM Blockchain Platform nodes consume on an hourly basis, at a flat rate of $0.29 USD/VPC-hour, where 1 VPC = 1 CPU. See this topic on [Pricing](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-saas-pricing) for more details.





 Getting started 

For information about how to deploy IBM Blockchain Platform for IBM Cloud, see [Getting started with IBM Blockchain Platform for IBM Cloud](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-deploy-iksibp-v2-deploy-iks).

For more information about how to use the console to start deploying nodes and building consortium, see the [Building your network](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-networkibp-console-build-network) tutorial. This tutorial guides you through the process of using the console to create a sample network with three organizations, one ordering organization, two peer organizations, and a channel with two peers joined to it. You can use this sample network to for demos or proofs of concept or adjust and expand the steps in the tutorial to create your own custom blockchain configuration.





 Architecture reference 

The following illustrations show the components of your blockchain network and how they interact with your cluster.



 IBM Blockchain Platform on IBM Cloud Kubernetes Service Architecture 

Zoom

![IKS Sample network structure](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/cloudkubernetes.svg)

Figure 1. Architecture diagram of IBM Blockchain Platform on IBM Cloud Kubernetes Service

Notice how a single instance of the console, also known as Operational Tooling, is created for each IBM Blockchain Platform Service Instance.
For a detailed step-by-step guide, see [VMware VM on-premises to IBM Cloud VPC with RMM](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-migrating-images-vmware-vpc).

For frequently asked questions and answers, see [FAQs for VMware (on-premises and classic) to VPC migration](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-faqs-vmware).





 Cloud to VPC infrastructure migration 

You can use RMM solution to migrate from other cloud providers to IBM Cloud VPC.

Zoom

![Architecture](https://cloud.ibm.com/docs-content/v1/content/8aa0853d34cf2349f1d2db8e5c61e6422a580169/cloud-infrastructure/images/AnyCloud_final.svg)

Figure 5. Other cloud providers to VPC migration

You can migrate your workloads from the following cloud providers:



* AWS
* Azure
* GCP
* OCI (bare metal)



For a detailed step-by-step guide, see [AWS, Azure, GCP, and OCI workloads to IBM Cloud VPC](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-aws-azure-gcp-and-oci-workloads-to-ibm-cloud-vpc-vsi-migration-with-rackware-rmm).







 DIY automation 

There are several do-it-yourself (DIY) automation scripts made available to migrate workloads and data to IBM Cloud. The automation scripts are starter scripts that you can modify or adapt to your environment.

Since these scripts are open-sourced and without charge for use, there is no support or SLAs.
--------------------







 ibmcloud is vpc-address-prefix-delete 

Delete one or more address prefixes.

ibmcloud is vpc-address-prefix-delete VPC (PREFIX1 PREFIX2 ...) [--output JSON] [-f, --force] [-q, --quiet]



 Command options 



* VPC: ID or name of the VPC.
* PREFIX1: ID or name of the VPC address prefix.
* PREFIX2: ID or name of the VPC address prefix.
* --output: Specify output format, only JSON is supported. One of: JSON.
* --force, -f: Force the operation without confirmation.
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is vpc-address-prefix-update 

Update an address prefix.

ibmcloud is vpc-address-prefix-update VPC PREFIX [--name NEW_NAME] [--default false | true] [--output JSON] [-q, --quiet]



 Command examples 



* ibmcloud is vpc-address-prefix-update 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 fee82deba12e4c0fb69c3b09d1f12345 --name my-renamed-prefix --default false --output JSON
* 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.
provisioner: vpc.block.csi.ibm.io
reclaimPolicy: Retain
- apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
annotations:
version: 2.0.2_285
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
razee/force-apply: "true"
name: ibmc-vpc-block-retain-custom
parameters:
billingType: hourly
classVersion: "1"
csi.storage.k8s.io/fstype: ext4
encrypted: "false"
encryptionKey: ""
iops: "400"
profile: custom
region: ""
resourceGroup: ""
sizeIOPSRange: |-
[10-39]GiB:[100-1000]
[40-79]GiB:[100-2000]
[80-99]GiB:[100-4000]
[100-499]GiB:[100-6000]
[500-999]GiB:[100-10000]
[1000-1999]GiB:[100-20000]
sizeRange: '[10-2000]GiB'
tags: ""
zone: ""
provisioner: vpc.block.csi.ibm.io
reclaimPolicy: Retain
- apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
annotations:
version: 2.0.2_285
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
razee/force-apply: "true"
name: ibmc-vpc-block-retain-general-purpose
parameters:
billingType: hourly
classVersion: "1"
csi.storage.k8s.io/fstype: ext4
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
razee/force-apply: "true"
name: ibmc-vpc-block-retain-general-purpose
parameters:
billingType: hourly
classVersion: "1"
csi.storage.k8s.io/fstype: ext4
encrypted: "false"
encryptionKey: ""
profile: general-purpose
region: ""
resourceGroup: ""
sizeRange: '[10-2000]GiB'
tags: ""
zone: ""
provisioner: vpc.block.csi.ibm.io
reclaimPolicy: Retain
kind: List
metadata:
annotations:
version: 2.0.2_285
name: ibm-vpc-block-csi-driver
namespace: kube-system

Show more
provisioner: vpc.block.csi.ibm.io
reclaimPolicy: Delete
- apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
annotations:
version: 2.0.3_354
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
razee/force-apply: "true"
name: ibmc-vpc-block-general-purpose
parameters:
billingType: hourly
classVersion: "1"
csi.storage.k8s.io/fstype: ext4
encrypted: "false"
encryptionKey: ""
profile: general-purpose
region: ""
resourceGroup: ""
sizeRange: '[10-2000]GiB'
tags: ""
zone: ""
provisioner: vpc.block.csi.ibm.io
reclaimPolicy: Delete
- apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
annotations:
version: 2.0.3_354
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
razee/force-apply: "true"
name: ibmc-vpc-block-retain-10iops-tier
parameters:
billingType: hourly
classVersion: "1"
csi.storage.k8s.io/fstype: ext4
encrypted: "false"
encryptionKey: ""
profile: 10iops-tier
region: ""
resourceGroup: ""
sizeRange: '[10-2000]GiB'
tags: ""
zone: ""
provisioner: vpc.block.csi.ibm.io
reclaimPolicy: Retain
- apiVersion: storage.k8s.io/v1
kind: StorageClass
[40-79]GiB:[100-2000]
[80-99]GiB:[100-4000]
[100-499]GiB:[100-6000]
[500-999]GiB:[100-10000]
[1000-1999]GiB:[100-20000]
sizeRange: '[10-2000]GiB'
tags: ""
zone: ""
provisioner: vpc.block.csi.ibm.io
reclaimPolicy: Delete
- apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
annotations:
version: 2.0.2_285
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
razee/force-apply: "true"
name: ibmc-vpc-block-general-purpose
parameters:
billingType: hourly
classVersion: "1"
csi.storage.k8s.io/fstype: ext4
encrypted: "false"
encryptionKey: ""
profile: general-purpose
region: ""
resourceGroup: ""
sizeRange: '[10-2000]GiB'
tags: ""
zone: ""
provisioner: vpc.block.csi.ibm.io
reclaimPolicy: Delete
- apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
annotations:
version: 2.0.2_285
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
razee/force-apply: "true"
name: ibmc-vpc-block-retain-10iops-tier
parameters:
billingType: hourly
classVersion: "1"
csi.storage.k8s.io/fstype: ext4
app: ibm-vpc-block-csi-driver
razee/force-apply: "true"
name: ibmc-vpc-block-retain-custom
parameters:
billingType: hourly
classVersion: "1"
csi.storage.k8s.io/fstype: ext4
encrypted: "false"
encryptionKey: ""
iops: "400"
profile: custom
region: ""
resourceGroup: ""
sizeIOPSRange: |-
[10-39]GiB:[100-1000]
[40-79]GiB:[100-2000]
[80-99]GiB:[100-4000]
[100-499]GiB:[100-6000]
[500-999]GiB:[100-10000]
[1000-1999]GiB:[100-20000]
sizeRange: '[10-2000]GiB'
tags: ""
zone: ""
provisioner: vpc.block.csi.ibm.io
reclaimPolicy: Retain
- apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
annotations:
version: 2.0.3_354
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
razee/force-apply: "true"
name: ibmc-vpc-block-retain-general-purpose
parameters:
billingType: hourly
classVersion: "1"
csi.storage.k8s.io/fstype: ext4
encrypted: "false"
encryptionKey: ""
profile: general-purpose
region: ""
resourceGroup: ""
sizeRange: '[10-2000]GiB'
tags: ""
zone: ""
provisioner: vpc.block.csi.ibm.io
reclaimPolicy: Retain
kind: List
tags: ""
zone: ""
provisioner: vpc.block.csi.ibm.io
reclaimPolicy: Delete
- apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
annotations:
version: 2.0.3_354
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
razee/force-apply: "true"
name: ibmc-vpc-block-general-purpose
parameters:
billingType: hourly
classVersion: "1"
csi.storage.k8s.io/fstype: ext4
encrypted: "false"
encryptionKey: ""
profile: general-purpose
region: ""
resourceGroup: ""
sizeRange: '[10-2000]GiB'
tags: ""
zone: ""
provisioner: vpc.block.csi.ibm.io
reclaimPolicy: Delete
- apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
annotations:
version: 2.0.3_354
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
razee/force-apply: "true"
name: ibmc-vpc-block-retain-10iops-tier
parameters:
billingType: hourly
classVersion: "1"
csi.storage.k8s.io/fstype: ext4
encrypted: "false"
encryptionKey: ""
profile: 10iops-tier
region: ""
resourceGroup: ""
sizeRange: '[10-2000]GiB'
tags: ""
zone: ""
provisioner: vpc.block.csi.ibm.io
reclaimPolicy: Retain
For supported instance profiles in the Memory family, see [memory profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-profilesmemory). Instance profiles that are provisioned on a dedicated host in the Memory family must include an mx2 prefix in the instance profile name. Profiles with instance storage include d in the profile name, for example mx2d.

Dedicated hosts have a network performance cap of 80 Gbps. Instances provisioned on the host share bandwidth across the instances.





 Very High Memory with instance storage 

The Very High Memory with instance storage profile with a high memory ratio of 14 GiB of memory to 1 vCPU of compute is best for OLAP workloads and SAP-related services such as SAP NetWeaver. The Very High Memory profile includes temporary SSD-backed [Instance Storage](https://cloud.ibm.com/docs/vpc?topic=vpc-instance-storage) at no additional charge.

Hosted exclusively on the Intel® Xeon® Platinum 8260 Cascade Lake with 96 cores of compute that are running at a base speed of 2.4 GHz and an all-core turbo frequency of 3.1 GHz, a dedicated host that is provisioned with a Very High Memory profile delivers maximum speed and performance.

If you provision a dedicated host with a Very High Memory profile, any virtual server instances that are provisioned on the dedicated host must also be provisioned with a Very High Memory profile. All Very High Memory profiles include instance storage that is designated by the d in the profile name, for example vx2d.

The following Very High Memory profile is available for dedicated hosts.

Intel x86-64



Table 10. Intel x86-64 very high memory profiles for dedicated hosts
Dedicated Host Very High Memory profile option for Intel x86-64 virtual server instances.

 Dedicated host profile vCPU Cores GiB RAM Instance storage 

 vx2d-host-176x2464 176 88 2464 5280 GB 



For more information about instance profiles that include instance storage in the Very High Memory family, see [very high memory profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-profilesvhmemory).