vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Max dimension size of a thread block (x,y,z): (1024, 1024, 64)
Max dimension size of a grid size (x,y,z): (2147483647, 65535, 65535)
Maximum memory pitch: 2147483647 bytes
Texture alignment: 512 bytes
Concurrent copy and kernel execution: Yes with 2 copy engine(s)
Run time limit on kernels: No
Integrated GPU sharing Host Memory: No
Support host page-locked memory mapping: Yes
Alignment requirement for Surfaces: Yes
Device has ECC support: Enabled
Device supports Unified Addressing (UVA): Yes
Device supports Managed Memory: Yes
Device supports Compute Preemption: Yes
Supports Cooperative Kernel Launch: Yes
Supports MultiDevice Co-op Kernel Launch: Yes
Device PCI Domain ID / Bus ID / location ID: 0 / 175 / 0
Compute Mode:
< Default (multiple host threads can use ::cudaSetDevice() with device simultaneously) >

deviceQuery, CUDA Driver = CUDART, CUDA Driver Version = 11.4, CUDA Runtime Version = 11.7, NumDevs = 1
Result = PASS

In this example, you see a GPU was used to execute the job because the GPU was scheduled in the worker node. If the limit is set to 2, only 2 GPUs are shown.



Now that you deployed a test GPU workload, you might want to set up your cluster to run a tool that relies on GPU processing, such as [IBM Maximo Visual Inspection](https://www.ibm.com/products/maximo/remote-monitoring).





 Deploying Cloud Paks, licensed software, and other integrations 

You can deploy IBM Cloud Paks™, licensed software, and other 3rd party integrations to Red Hat OpenShift on IBM Cloud clusters. You have various tools to deploy integrations, such as IBM Cloud service binding, managed add-ons, Helm charts, and more. After you install an integration, follow that product's documentation for configuration settings and other instructions to integrate with your apps.
console.log(documents);
} else { // otherwise, hide the last document:
console.log(documents.slice(0, documents.length - 1))
}
allDocsResult = (await service.postAllDocs({
db: 'orders',
limit: pageSize + 1,
startKey: documentsdocuments.length - 1] .id
})).result;
}
}

paginate(5)
import json
from ibmcloudant.cloudant_v1 import CloudantV1

service = CloudantV1.new_instance()
page_size = 5

response = service.post_all_docs(
db='orders',
limit=page_size+1, Fetch page_size + 1 documents
).get_result()

while len(response"rows"]) > 1:
documents = response'rows']
 on the last page, show all documents:
if len(documents) <= page_size:
print(json.dumps(documents, indent=2))
else: otherwise, hide the last document:
print(json.dumps(documents0:-1], indent=2))
response = service.post_all_docs(
db='orders',
limit=page_size+1, Fetch page_size + 1 documents
start_key=documents-1]'id'] !!
).get_result()
pageSize := core.Int64Ptr(5)
postAllDocsOptions := service.NewPostAllDocsOptions(
"orders",
)
postAllDocsOptions.SetLimit(pageSize + 1)

allDocsResult, _, err := service.PostAllDocs(postAllDocsOptions)
if err = nil {
panic(err)
}

for len(viewResult.Rows) > 1 {
documents := allDocsResult.Rows
Make sure to use a different subnet than the one that is used for the primary interface.
4. Leave the default MTU value of 1500 bytes.



* Although the default maximum transmission unit (MTU) is 1,500, you can change it to 9,000 if you are using jumbo frames. Your ESXi host and physical infrastructure need to support jumbo frames. By default, IBM Cloud supports an MTU size of 9,000 bytes with no configuration changes needed.



5. Click Apply.



The AltaVault appliance is now configured to allow communications between itself, IBM Cloud Object Storage, and Veeam Backup & Replication.







 Veeam Backup & Replication 

Veeam Backup & Replication software provides complete backup, replication, and recovery capabilities for VMs and their data. Veeam Backup & Replication can be fully integrated with an AltaVault Cloud Gateway Appliance, making for a seamless backup and recovery experience.



 Deploy Veeam Backup & Replication 

A trial version of Veeam Backup & Replication Version 8 is used in the example.



 Prerequisites 

Before you proceed with deployment, make sure that the following prerequisites are satisfied:



* Have an existing AltaVault appliance that is configured for use with IBM Cloud Object Storage and Veeam Backup & Replication.
* Obtain a copy of Veeam Backup & Replication for VMware environments, which is a single executable file. Contact your Veeam Representative for a copy or download a [30-day trial version ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://www.veeam.com/vm-backup-recovery-replication-software.html).
* Obtain a license file for use with Veeam Backup & Replication. In most cases, this file is emailed to the email address that was used to download Veeam Backup & Replication. If you did not receive this file, contact your Veeam Representative.

The license file is used to activate full Veeam Backup & Replication functionality.
: The Content-Type header of the recognize methods now supports audio/wav for Waveform Audio File (WAV) files, in addition to audio/flac and audio/l16. For more information, see [audio/wav format](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-audio-formatsaudio-formats-wav).

Limits on maximum amount of audio for speech recognition
: The service now has a limit of 100 MB of data per session in streaming mode. You specify streaming mode by specifying the value chunked with the header Transfer-Encoding. One-shot delivery of an audio file still imposes a size limit of 4 MB on the data that is sent. For more information, see [Audio transmission](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-inputtransmission).

New header to opt out of contributing to service improvements
: The GET /v1/sessions/{session_id}/observe_result, POST /v1/sessions/{session_id}/recognize, and POST /v1/recognize methods now include the header parameter X-WDC-PL-OPT-OUT to control whether the service uses the audio and transcription data from a request to improve future results. The WebSocket interface includes an equivalent query parameter. Specify a value of 1 to prevent the service from using the audio and transcription results. The parameter applies only to the current request. The new header replaces the X-logging header from the beta API. See [Controlling request logging for Watson services](https://cloud.ibm.com/docs/watson?topic=watson-gs-logging-overview).

Changes to HTTP error codes
: The service can now respond with the following HTTP error codes:
"href": "https://us-south.iaas.cloud.ibm.com/v2/resource_groups/678523bcbe2b4eada915d32640909956",
"id": "678523bcbe2b4eada915d32640909956",
"name": "Default"
},
"resource_type": "share",
"size": 4800,
"user_tags": [],
"zone": {
"href": "https://us-south.iaas.cloud.ibm.com/v1/regions/us-south/zones/us-south-1",
"name": "us-south-1",
"resource_type": "zone"
}
}





 List all mount targets of a file share with the API 

Make a GET /shares/{share_id}/mount_targets request to list all mount targets of a file share.

See the following example.

curl -X GET "$vpc_api_endpoint/v1/shares/$share_id/mount_targets?version=2023-07-05?limit=50&generation=2&maturity=beta" -H "Authorization: $iam_token"

A successful response looks like the following example:

{
"first": {
"href": "https://us-south.iaas.cloud.ibm.com/v1/shares/199d78ec-b971-4a5c-a904-8f37ae710c63/mount_targets?limit=50"
},
"limit": 50,
"mount_targets": [
{
"access_control_mode": "security_group",
"created_at": "2023-07-05T01:59:46.000Z",
App networking All pods that are deployed to a worker node are assigned a private IP address in the 172.30.0.0/16 range and are routed between worker nodes on the worker node private IP address of the private VPC subnet. To expose the app on the public network, you can create a Kubernetes LoadBalancer service, which provisions a VPC load balancer and public hostname address for your worker nodes. For more information, see [Exposing apps with VPC load balancers](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-lbaas). 
 Storage For persistent storage, use [block](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-block). For the number of volumes that can be attached per worker node, see [Volume attachment limits](https://cloud.ibm.com/docs/vpc?topic=vpc-attaching-block-storagevol-attach-limits). The storage class limits the volume size to 20TB and IOPS capacity to 20,000. For non-persistent storage, secondary storage on the local worker node is not available. 
 User access You can use [IBM Cloud IAM access policies](https://cloud.ibm.com/docs/vpc?topic=vpc-iam-getting-started) to authorize users to create infrastructure, manage your cluster, and access cluster resources. The cluster can be in a different resource group than the VPC. 
 Integrations VPC supports a select list of supported IBM Cloud services, add-ons, and third-party integrations. For a list, see [Supported IBM Cloud and third-party integrations](https://cloud.ibm.com/docs/openshift?topic=openshift-supported_integrations). 
 Locations and versions VPC clusters are available worldwide in the [multizone location](https://cloud.ibm.com/docs/openshift?topic=openshift-regions-and-zoneszones-vpc).
If you delete a VPC subnet that your cluster used, any load balancers that use IP addresses from the subnet might experience issues, and you might be unable to create new load balancers.<br><br><br> 
 VPC load balancer See [VPC load balancer limitations](https://cloud.ibm.com/docs/containers?topic=containers-vpc-lbaaslbaas_limitations). 







 Storage 

Keep in mind that the [service](https://cloud.ibm.com/docs/containers?topic=containers-limitationstech_limits) limitations also apply.



VPC cluster storage limitations

 Category Description 

 Storage class for profile sizes For more information, see [available volume profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profiles). 
 Supported types You can set up Block Storage for VPC, IBM Cloud Object Storage and Cloud Databases only.<br><br><br><br> * [Block Storage for VPC](https://cloud.ibm.com/docs/containers?topic=containers-vpc-block) is available as a cluster add-on. Make sure to [attach a public gateway to all the VPC subnets](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-vpc-resources-with-cli-and-api&interface=cliattach-public-gateway-cli) that the cluster uses so that you can provision Block Storage for VPC.<br> * [IBM Cloud Object Storage](https://cloud.ibm.com/docs/containers?topic=containers-storage_cos_install) is available as a Helm chart.<br><br><br> 
 Volume attachments See [Volume attachment limits](https://cloud.ibm.com/docs/vpc?topic=vpc-attaching-block-storagevol-attach-limits).
: Unique identifier for IBM Cloud Event Notifications instance.

The maximum length is 36 characters. The minimum length is 36 characters. The value must match regular expression /[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]/.

[--sources SOURCES] ([TopicCreateSourcesItem[]](https://cloud.ibm.com/docs/cli?topic=cli-event-notifications-clien-cli-topic-example-schema))
: The list of sources.
* Example:



* The following example shows the format of the TopicCreateSourcesItem[] object.

[
{
"id" : "exampleString",
"rules" :
{
"enabled" : true,
"event_type_filter" : "$.",
"notification_filter" : "exampleString"
}
]
}
]
* The following example shows the format of the TopicUpdateSourcesItem[] object.

[
{
"id" : "exampleString",
"rules" :
{
"enabled" : true,
"event_type_filter" : "exampleString",
"notification_filter" : "exampleString",
"rule_id" : "exampleString"
}
]
}
]









 ibmcloud event-notifications topic list 



* Action: List all Topic.

ibmcloud event-notifications topic list [--limit LIMIT] [--offset OFFSET] [--search SEARCH] [--instance-id INSTANCE-ID]
* Parameters to provide:

--limit LIMIT (int64)
: The page limit for paginated results.

The maximum value is 100. The minimum value is 1.

--offset OFFSET (int64)
Go to the list of all file shares. From the [IBM Cloud console](https://cloud.ibm.com/login), go to menu icon ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > File Shares.
2. Click the name of a file share to see the details page.



The editable name and [status](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managingfile-storage-vpc-status) of the file share is shown. If you applied user or access management tags to the file share, they are listed. Click Add tags to apply new [tags](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-about&interface=uifs-about-fs-tags) to the share.

The following table describes the information on files shares details page.



Table 2. File shares details page

 Field Value 

 File share details 
 Name The file share name. Click the pencil icon to change the name. 
 Zone Zone for the file share (for example, Dallas 2). 
 Max IOPS Maximum IOPS for the IOPS tier, custom, or dp2 [profile](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profiles) associated with the file share. 
 Resource group Resource groups associated with the file share in your account. 
 Replication role Source file share or replica. 
 Encryption Specifies provider-managed or [customer-managed encryption](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-encryption). 
 Encryption instance For customer-managed encryption, link to the Key Protect or Hyper Protect Crypto Services instance. 
 Key ID Copiable customer root key ID. 
 ID For customer-managed encryption, the UUID generated when you created the file share. 
 Size File share size in GB. 
 Created Date the file share was created.
The system uses an IBM Db2 database with external [IBM Cloud Block Storage for Classic](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-getting-startedgetting-started) or [IBM Cloud File Storage for Classic](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-getting-startedgetting-started) (4 IOPS/GB). The calculation for the IOPS is:



* 6,000 IOPS/1,500 GB = 4 IOPS/GB needed for external storage. It is assumed that 3,000 GB is for backup at 2 IOPS/GB (medium performance.





Table 1. Sample storage layout based on IOPS calculation

 File system of volumes <br> Storage type IOPS/GB GB IOPS <br> 

 / 1 Internal N/A 150 GB N/A 
 /boot 1 Internal N/A 0.25 GB N/A 
 swap 1 Internal N/A 256 GB N/A 
 /db2 (including logs) 1 Internal N/A 250 GB N/A 
 sapdata 1 External 4 IOPS/GB 1,500 GB 6,000 
 backup/log and backup 1 External 2 IOPS/GB 3,000 GB 6,000 









 Sample storage configurations on VPC Infrastructure 

The following sections demonstrate storage configurations in various different SAP workload scenarios, when you are using VPC Infrastructure.



 Sample storage configuration for SAP AnyDB with IBM Db2 that uses Intel Virtual Server 

For SAP AnyDB that uses IBM Db2 on mx2-32x256 profile the volumes that are needed are:



* 1x 500 GB volumes; one block storage volume of 500 GB size, with a custom volume profile that supports up to 10,000 Max IOPS attached to the Virtual Server
* 1x 2,000 GB volume; one block storage volume of 2,000 GB size, with a lower 4,000 IOPS (medium performance) attached to the Virtual Server for backups





 Disk mount points and volumes for IBM Db2 

After you attach the two data volumes, two new virtual disks will appear in the Virtual Server, see the following table. In this example, those disks are vdd, vde, and vdf.
Also, you might want to increase your file share's IOPS during peak times for your application and decrease IOPS during off-peak hours.

By using this feature, you can:



* Adjust IOPS up or down by selecting a different [IOPS tier](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profilesfs-tiers). IOPS is adjusted within the tier. The degree to which IOPS can be increased is determined by the maximum that is allowed by the file share's [IOPS tier profile](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profiles). You can adjust IOPS for an IOPS tier based on share size or select the next profile that allows for increased performance.

Maximum IOPS for a file share for a 3 IOPS/GB tier profile is 96,000 IOPS. All other profiles are capped at 48,000 IOPS. For 96,000 IOPS to be realized, a single file share must be accessed by multiple virtual server instances. A single file share that is accessed by one instance is limited to 48,000 IOPS.
* Adjust IOPS when you're using a [custom IOPS](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profilescustom) or [dp2](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profilesdp2-profile) profile. The IOPS range is based on the file share size. For example, for a file share that's 25 GB, you can increase IOPS anywhere in the range 100-1,000 IOPS with a custom profile. If you later [increase the size of a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-expand-capacity) to the next highest band, you can increase the IOPS again.
* Adjust IOPS from an IOPS tier profile to a custom or dp2 profile.
* [April 2023](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-relnotesschematics-apr23)



* Review the release notes for April 2023.
* [18 April 2023](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-relnotesschematics-apr1723)



* Schematics documentation realigns the workspace documentation



* [13 April 2023](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-relnotesschematics-apr1323)



* Schematics updates the deprecation of Terraform versions



* [6 April 2023](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-relnotesschematics-apr623)



* Release Schematics command-line plug-in





* [March 2023](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-relnotesschematics-mar23)



* Review the release notes for March 2023.
* [30 March 2023](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-relnotesschematics-mar3023)



* Release configuring Kubernetes cluster for an agent.
* Enhancement of Schematics worker runtime.
* IAM allowed IP addresses replaced with context based restrictions.
* The terraform.tfstate state file size maximum limit is less than 2 MB.



* [22 March 2023](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-relnotesschematics-mar2223)



* Schematics Agent beta-1 release.
* Release Schematics command-line plug-in.
Host storage and attached devices 

Review the following storage requirements for hosts assigned to the location control plane and hosts assigned to services. Note that depending on the services you want to use, the storage requirements for hosts assigned to those services vary. For specific service requirements, refer to the service documentation.

Hosts must have a boot device with an ext4 file system and enough space to boot the host and run the operating system. While a minimum of 10 GiB is required, 25 GiB is recommended. In addition, /tmp and /usr must each have at least 1.5 GiB available. Hosts can't have a device mounted to /var/data. The /boot partition must be a minimum of 1 GiB in size.

Zoom

![Host storage](https://cloud.ibm.com/docs-content/v1/content/c8335d66af691d19e837116fd633481c477061eb/satellite//images/sat_architecture_host_storage.svg)

Figure 1. Satellite host storage requirements

Boot device (Operating system)
: Hosts must have a boot device with an ext4 file system and enough space to boot the host and run the operating system. While a minimum of 10 GiB is required, 25 GiB is recommended.

Bootstrap device (Container image storage)
: Hosts must have a second device with a minimum of 100 GiB of unmounted and unformatted device space. For hosts assigned to the control plane, the attached storage device must support at least 1000 IOPs. For example, a 10 IOPs/GiB device with at least 100 GiB capacity. The required IOPS varies with the number of clusters in the location, and the activity of the masters for those clusters. For more information, see [How many clusters can I run before I need to add capacity to the control plane?](https://cloud.ibm.com/docs/satellite?topic=satellite-location-sizingcontrol-plane-how-many-clusters).

Additional storage for hosts assigned to services (like clusters)
To connect your cluster to resources in an on-premises network or another VPC, see [Using VPN with your VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-vpn-onprem-example). 
 Subnets <br><br> * See [VPC networking limitations](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-subnetsvpc_basics_limitations).<br> * Do not delete the subnets that you attach to your cluster during cluster creation or when you add worker nodes in a zone. If you delete a VPC subnet that your cluster used, any load balancers that use IP addresses from the subnet might experience issues, and you might be unable to create new load balancers.<br><br><br> 
 VPC load balancer See [VPC load balancer limitations](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-lbaaslbaas_limitations). 







 Storage 

Keep in mind that the [service](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_limitationstech_limits) limitations also apply.



VPC cluster storage limitations

 Category Description 

 Storage class for profile sizes For more information, see [available volume profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profiles). 
 Supported types You can set up IBM Cloud Object Storage and Cloud Databases only. 
 Volume attachments See [Volume attachment limits](https://cloud.ibm.com/docs/vpc?topic=vpc-attaching-block-storagevol-attach-limits). 
 Portworx Review the [Portworx limitations](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_portworx_planportworx_limitations). 
 Block Storage for VPC The default storage class in VPC clusters can not be changed.
For example, see the Db2 documentation here: [Required File Systems for IBM Db2 for Linux, UNIX, and Windows](https://help.sap.com/viewer/ce9e270ad34949969c16d09d1b099a26/CURRENT_VERSION/en-US/713eb64f45c6448c8dbe8a51b85680ee.html).







 Sample storage configurations for SAP HANA 

Further information about [storage specifications for Virtual Server](https://cloud.ibm.com/docs/sap?topic=sap-hana-iaas-intel-vs-vpc-storage-specs) are available, the below shows only the configuration steps required.



 mx2-16x128 and mx2-32x256 profiles 

For Virtual Server created based on the mx2-16x128 and mx2-32x256 profiles there are:



* 3x 500 GB volumes; three block storage volumes of 500 GB size, with a custom volume profile that supports up to 10,000 Max IOPS attached to the Virtual Server
* 1x 2,000 GB volume; one block storage volume of 2,000 GB size, with a lower 4,000 IOPS (medium performance) attached to the Virtual Server for backups



After attaching the three data volumes, three new virtual disks will appear in the virtual server, see the table that follows. In this example, those disks are vdd, vde and vdf.

The disks are visible in the operating system of the virtual server as follows:

[root@hana256-vsi ] fdisk -l

Disk /dev/vdd: 536.9 GB, 536870912000 bytes, 1048576000 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/vde: 536.9 GB, 536870912000 bytes, 1048576000 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
"StorageClass": "STANDARD",
"Key": "abfc4-filename-00004",
"Owner": {
"DisplayName": "{storage-account-uuid}",
"ID": "{storage-account-uuid}"
},
"Size": 20950
}
]
}
Show more





 Configure a Static Website 

aws --endpoint-url=https://<endpoint> s3 website s3://<bucketname>/ --index-document index.html --error-document error.html







 Next Steps 

The detailed description of the RESTful API for IBM Cloud Object Storage can be found in the [S3 Compatibility API Documentation](https://cloud.ibm.com/apidocs/cos/cos-compatibility) or the [Configuration API Documentation](https://cloud.ibm.com/apidocs/cos/cos-configuration).