vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Block Storage for VPC offers block-level volumes that are attached to an instance as a boot volume when the instance is created or attached as secondary data volumes. You can configure up to 300 Block Storage for VPC volumes per account in a region. You can request to increase this quota by [opening support case](https://cloud.ibm.com/docs/vpc?topic=vpc-manage-storage-limit) and specifying in which zone you need more volumes.

You can attach only one boot volume to a virtual server instance at a time, but you can attach up to 12 Block Storage for VPC data volumes to a single instance. For other limitations, see [Volume attachment limits](https://cloud.ibm.com/docs/vpc?topic=vpc-attaching-block-storagevol-attach-limits).



 Boot volumes 

When you create an instance from a stock image, a 100 GB, 3,000 IOPS general-purpose boot volume is created and attached to the instance by default. When you create an instance from a custom image, you can specify a boot volume capacity of 10 GB to 250 GB, depending what the image requires. This capacity can be any size between the minimum size that is supported for the selected image and the maximum supported image size. If the custom image is smaller than 10 GB, the boot volume capacity is rounded up to 10 GB. After the boot volume is created, you can expand the boot volume size to the maximum supported size, which is 250 GB.

You cannot create an image from a boot volume that is encrypted with customer-managed keys and is not 100 GB. Such an operation is not supported.

By default, boot volumes are encrypted by IBM-managed encryption. Optionally, you can use your own root keys (CRKs) by choosing customer-managed encryption during instance creation (see [Customer-managed encryption](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-encryption-aboutvpc-customer-managed-encryption)).

By default, boot volumes are deleted when you delete an instance. You can toggle this setting on or off in the instance details.
This return code was added at version 9.0.3 of IBM MQ, clients that are older than version 9.0.3 will not recognize this return code and so are likely to return MQRC_UNEXPECTED_ERROR (2195) instead.

The following features have been disabled:



* The following queue manager attributes: CONNAUTH, CHADEXIT, CLWLEXIT, CLWLDATA, SSLCRYP, SSLKEYR
* Authentication information objects of type IDPWOS & IDPWLDAP
* The following channel attributes: MSGEXIT, MSGDATA, SCYEXIT, SCYDATA, SENDEXIT, SENDDATA, RCVEXIT, RCVDATA
* Listener objects.
* Service objects. Note: You can start or stop an existing service object.
* Process objects.
* The following queue attributes: PROCESS
* COMMINFO objects.









 MQRC_MAX_CONNS_LIMIT_REACHED (2025) when attempting to connect to a queue manager 

While attempting to connect a client application or queue manager to your IBM MQ on Cloud queue manager you receive a return code of MQRC_MAX_CONNS_LIMIT_REACHED (2025) and the client cannot connect.

Additionally, an error message is outputted with title AMQ9694E: Program cannot connect because connection limit reached.



 Explanation 

IBM MQ on Cloud applies limits to queue managers resources based on size. The values of each limit, and what are limited, are detailed in the information about each queue manager size when you create a new queue manager.

One of the limits applied to the queue manager is the number of concurrent client connections, this applies to both client applications and client queue managers. If you attempt to exceed the number of allowed connections your client application is blocked with the return code MQRC_MAX_CONNS_LIMIT_REACHED (2025) and an AMQ9694E error message is printed in the queue manager logs.

Because JMS uses two client connections to pass messages you need to be aware that if your queue manager connection limit is 10 you can only connect 5 JMS clients to your queue manager before reaching the connection limit.





 Solution 

To resolve this problem either:
(https://cloud.ibm.com/docs-content/v1/content/d4595e5202a9a27767cf034e81b038cdf772e0d5/secure-enterprise/includes/security-compliance/includes/security-compliance/images/access-model.svg)

Figure 1. Attachment hierarchy

Attachment A
: In Attachment A, the target scope is the full enterprise. As you can see, all account groups and accounts that exist within the enterprise are evaluated. That is, unless they have been purposefully excluded.

Attachment B
: The target scope of Attachment B is a specific account group within an enterprise. As you can see, the resources in the account group are now being evaluated against the profile that is selected during Attachment A and are evaluated according to the profile selected when Attachment B was created.

Attachment C
: The target scope of Attachment C is a child account. This attachment was created in the account, outside of the context of the enterprise. As you can see, Attachment A is monitoring the resources in the same account, but because Attachment C is created at the account level, resource groups are able to be seen and excluded.

To view the results of an evaluation, you look in the account where the attachment was created. If you use the previous image as an example, attachment A and B's results would exist within the enterprise account, and the enterprise account is charged for the evaluation. However, attachment C's results would exist within the child account.
Restoring files to new CentOS virtual server instance 

The following example shows how you can take a secondary volume that holds a Veeam backup repository and import the repository onto a new CentOS virtual server instance for IBM Cloud VPC.



 Detaching secondary volume from original instance 

The original CentOS instance for VPC needs to be shut down so that it doesn't have access to the secondary volume. The secondary volume can be detached through the IBM Cloud CLI:

ibmcloud is in-vold <Original VPC instance ID> <volume attachment ID>





 Attaching secondary volume to new instance 

The secondary volume is then attached to the new CentOS instance for VPC by running:

ibmcloud is in-vola <volume attachment name> <New VPC instance ID> <volume ID>





 Verifying secondary volume 

After the secondary volume is attached to the new CentOS instance, you need to verify that the secondary volume is available.

Use the following example:

$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 253:0 0 100G 0 disk
├─vda1 253:1 0 1G 0 part /boot
└─vda2 253:2 0 99G 0 part /
vdb 253:16 0 368K 0 disk
vdc 253:32 0 44K 0 disk [SWAP]
vdd 253:48 0 300G 0 disk

In this example, the secondary volume is the vdd device.





 Mounting the volume 

Make a mount point directory and mount the volume.

mkdir /veeam_disk
mount /dev/vdd /veeam_disk





 Importing the backup repository 

The secondary volume is now ready for the Veeam Agent to import the backup repository. Use the following steps to import the backup repository.



1. Start the Veeam Agent:

veeamconfig ui
2. Select Recover Files, Import backup, then select the backup location. In this example, it is:

vdd	virtio /veeam_disk
3. In Browse for backup files, select the appropriate backup job file directory and then select the backup job file.
After the pipeline is run, the change request has an attachment that is named CycloneDX SBOM that can be inspected on the change management providers UI.





 Continuous compliance pipeline 

During the CC summarization the SBOM attachment is treated as follows:



* If an SBOM attachment is found for the evidence type com.ibm.code_bom_check, the attachment is downloaded and it is used for the CC evidence for com.ibm.code_bom_check. Fresh SBOM regeneration does not happen.
* If an SBOM attachment is not found for the evidence type com.ibm.code_bom_check, then ibmcloud cra bom-generate is run to generate the fresh BOM at that point in the standard format. The BOM is also generated in the cyclonedx format if the BOM is opted in by using the cra-generate-cyclonedx-format flag. This freshly-created BOM is used for the CC evidence for com.ibm.code_bom_check.
To restore the ability to SSH into the machine, you can [remove the host](https://cloud.ibm.com/docs/satellite?topic=satellite-host-remove) and reload the operating system.

Not sure how many hosts to attach to your location? See [Sizing your Satellite location](https://cloud.ibm.com/docs/satellite?topic=satellite-location-sizing).



 Downloading the host attachment script for your location 

To attach hosts to your location, you must download a host attachment script. After you download the script, you can run it on your hosts to attach them to your location. You can get the attachment script from the console or by running the sat host attach[command](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencehost-attach). Note that for CoreOS hosts, the attachment script is an ignition (.ign) file. For RHEL hosts, the attachment script is a Shell script.



1. Download the host attachment script.



* To get the host attachment script from the console:



1. Navigate to the [Locations dashboard](https://cloud.ibm.com/satellite/locations), select the location where you want to attach hosts.
2. From the Hosts tab, click Attach host.
3. Optional: Enter any labels that you want to add to your hosts so that you can identify your hosts more easily later. Labels must be provided as key-value pairs. For example, you can use use=satcp or use=satcluster to show that you want to use these hosts for your Satellite control plane or a Red Hat OpenShift cluster. By default, your hosts get a cpu, an os, and a memory label, but you might want to add more to control the auto assignment, such as env=prod or service=database. Note that the default value for os is rhel.
4. Enter a file name for your script or use the name that is generated for you.
5. Select RHEL or RHCOS to download the host script for your host system.
6.
You can choose the frequency of replication by creating a schedule with a cronspec and can replicate as frequently as every hour. Set up replication from the UI, CLI, or by calling the API.
* I want to set up replication. Is there automatic failover?

 I want to set up replication. Is there automatic failover? 

No, choosing to fail over to the replica site is a manual operation, and you must reconcile your data after the failover to the replica share is done. For more information about how failover works for disaster recovery, see [Failover for disaster recovery](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-failover&interface=uifs-failover-dr).
* Can I add tags to my file shares?

 Can I add tags to my file shares? 

Yes. You can specify user and access management tags when you create a file share or update an existing file share. Adding user tags to a file share or replica share can make organizing your resources easier. For more information, see [Add user tags to a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=apifs-add-user-tags). File Storage for VPC also supports access management tags. For more information, see [Access management tags for file shares](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-aboutfs-about-mgt-tags).
* What is the dp2 profile?

 What is the dp2 profile? 

The dp2 profile is the latest file storage profile, offering greater capacity and performance for your file shares. With this profile, ou can specify the total IOPS for the file share within the range for a specific file share size. You can provision shares with IOPS performance from 100 IOPS to 96,000 IOPS, based on share size.
Generating the software bill of materials (SBOM) in cyclonedx format 

OWASP CycloneDX is a lightweight Software Bill of Materials (SBOM) standard that is designed for use in application security contexts and supply chain component analysis. The Continuous Integration (CI) pipeline generates the Software Bill of Materials (BOM) with the help of Code Risk Analyzer. By default, this BOM is generated in the standard format.

To learn more about BOM generation, see [Bill of Materials (BOM)](https://cloud.ibm.com/docs/code-risk-analyzer-cli-plugin?topic=code-risk-analyzer-cli-plugin-cra-cli-pluginbom-generate-command).



 Before you begin 

This feature is based on V2 evidence collection. Make sure that your custom scripts already collect v2 evidence to be able to use the CycloneDX SBOM generation.





 Continuous integration pipeline 

To configure the pipelines to also generate the BOM in cyclonedx format, create a new pipeline environment property that is named cra-generate-cyclonedx-format, and set its value to 1.

After the pipeline is run, the BOM is added as an attachment to the com.ibm.code_bom_check evidence in both standard and cyclonedx format.





 Continuous deployment pipeline 

The continuous deployment pipeline can collect the CycloneDX SBOM attachment of every asset that is being deployed by the run. The pipeline merges these CycloneDX SBOMs and uploads the aggregated CycloneDX SBOM to the change request as an attachment.

To enable this feature, create a new pipeline environment property that is named merge-cra-sbom, and set its value to 1.

After the pipeline is run, the change request has an attachment that is named CycloneDX SBOM that can be inspected on the change management providers UI.





 Continuous compliance pipeline 

During the CC summarization the SBOM attachment is treated as follows:



* If an SBOM attachment is found for the evidence type com.ibm.code_bom_check, the attachment is downloaded and it is used for the CC evidence for com.ibm.code_bom_check.
Verify the assignment was created by listing your assignments.

curl -X GET "https://containers.cloud.ibm.com/global/v2/storage/satellite/getAssignments" -H "accept: application/json" -H "Authorization: Bearer TOKEN"







 Parameter reference 



 21.04 parameter reference 



Table 1. 21.04 parameter reference

 Display name CLI option Type Description Required? Default value 

 Management LIF managementLIF Config The IP address of the Management LIF. true N/A 
 Data LIF dataLIF Config The IP address of the Data LIF. true N/A 
 SVM svm Config The name of the SVM. true N/A 
 User Name username Secret The username to connect to the storage device. true N/A 
 User Password password Secret The password to connect to the storage device. true N/A 
 Limit Volume Size limitVolumeSize Config The maximum volume size (in Gibibytes) that can be requested and the qtree parent volume size. true 50Gi 
 Limit AggregateUsage limitAggregateUsage Config Provisioning fails if usage is above this percentage. true 80% 







 22.04 parameter reference 



Table 2. 22.04 parameter reference

 Display name CLI option Type Description Required? Default value 

 Management LIF managementLIF Config The IP address of the Management LIF. true N/A 
 Data LIF dataLIF Config The IP address of the Data LIF. true N/A 
 SVM svm Config The name of the SVM. true N/A 
 User Name username Secret The username to connect to the storage device. true N/A 
 User Password password Secret The password to connect to the storage device. true N/A 
 Limit Volume Size limitVolumeSize Config The maximum volume size (in Gibibytes) that can be requested and the qtree parent volume size. true 50Gi 
 Limit AggregateUsage limitAggregateUsage Config Provisioning fails if usage is above this percentage.
* [Can I update the Terraform version (TF_VERSION) using a JSON file?](https://cloud.ibm.com/docs/schematics?topic=schematics-workspaces-faqtf-version-update)
* [Can start with a new Terraform state file on each job run?](https://cloud.ibm.com/docs/schematics?topic=schematics-workspaces-faqwks-job-trigger)
* [Can I import an existing Terraform state file?](https://cloud.ibm.com/docs/schematics?topic=schematics-workspaces-faqtf-state-argument)
* [What is the maximum variable size?](https://cloud.ibm.com/docs/schematics?topic=schematics-workspaces-faqwks-name-maxlength)
* [What is the maximum state file size of import?](https://cloud.ibm.com/docs/schematics?topic=schematics-workspaces-faqwks-statefile-limit)
* [How do I fix authentication errors when using the API?](https://cloud.ibm.com/docs/schematics?topic=schematics-workspaces-faqcreateworkspace-authentication-error)







 Troubleshooting 



 Troubleshooting Schematics workspace errors 

[Why do Schematics Workspaces create using the API/UI/CLI fails?](https://cloud.ibm.com/docs/schematics?topic=schematics-wks-create-apiwks-create-api)

[Workspace failures](https://cloud.ibm.com/docs/schematics?topic=schematics-wks-failurewks-failure)



* [Workspace create fails with message Request Entity Too Large](https://cloud.ibm.com/docs/schematics?topic=schematics-wks-failurewks-new-fails1)
Understanding UBC / User Bean counter Values 

Use SLM Mode if UBC is not understood. SLM is easier and provides the same type of control.



 Name Type Description 

 Main parameters 
 numproc system Number of processes and threads 
 numtcpsock system Number of TCP sockets 
 numothersock system Number of sockets other than TCP 
 vmguardpages system Memory allocation guarantee 
 cpuunits cpu CPU power 
 diskspace disk Disk space quota 
 rate network Network bandwidth 
 ratebound network Whether network bandwidth is limited 
 Additional parameters 
 kmemsize system Size of unswappable kernel memory allocated for processes in this Container 
 tcpsndbuf system Total size of TCP send buffers 
 tcprcvbuf system Total size of TCP receive buffers 
 othersockbuf system Total size of UNIX-domain socket buffers, UDP and other datagram protocol send buffers 
 dgramrcvbuf system Receive buffers of UDP and other datagram protocols 
 oomguardpages system The guaranteed amount of memory when the memory is over-booked (out-of-memory kill guarantee) 
 privvmpages system Memory allocation limit 
 lockedpages system Process pages not allowed to be swapped out (pages locked by [mlock(2) ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://linux.die.net/man/2/mlock)) 
 shmpages system Total size of shared memory (interprocess communication or IPC, shared anonymous mappings and tmpfs objects) in pages 
 physpages system Total number of RAM pages used by processes 
 numfile system Number of open files 
 numflock system Number of file locks 
 numpty system Number of pseudo-terminals 
 numsiginfo system Number of siginfo structures 
 dcachesize system Total size of dentry and inode structures locked in memory 
 numiptent system Number of NETFILTER (IP packet filtering) entries 
 cpulimit cpu Limit on CPU consumption
¹If your cap is 1000 IOPS or 16 KB block size, the throughput caps at whatever limit is reached first.

Maximum IOPS can still be obtained when you use smaller block sizes, but throughput is less. The following example shows how throughput decreases for smaller block sizes, when max IOPS is maintained.



* 16 KB * 6000 IOPS == 94 MBps
* 8 KB * 6000 IOPS == 47 MBps
* 4 KB * 6000 IOPS == 23 MBps







 Next steps 

[Start creating file shares](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-create).
If false, source IP spoofing is not allowed on this interface. One of: false, true.
* --primary-network-interface: PRIMARY_NETWORK_INTERFACE_JSON|@PRIMARY_NETWORK_INTERFACE_JSON_FILE, primary network interface in JSON or JSON file. For the data schema, see the primary_network_interface property in the [API documentation](https://cloud.ibm.com/apidocs/vpccreate-instance).
* --network-interface: NETWORK_INTERFACE_JSON|@NETWORK_INTERFACE_JSON_FILE, network interface attachment in JSON or JSON file. For the data schema, see the network_interfaces property in the [API documentation](https://cloud.ibm.com/apidocs/vpccreate-instance).
* --metadata-service, --ms: Enable or disable the Instance Metadata Service. One of: true, false.
* --metadata-service-protocol, --msp: The communication protocol for the metadata service endpoint. Applies only when the metadata service is enabled. One of: http, https. (default: http).
* --metadata-service-response-hop-limit, --msrhl: The hop limit (IP time to live) for IP response packets from the metadata service.
* --host-failure-policy: The action to perform if the compute host experiences a failure. One of: restart, stop. (default: restart).
* --resource-group-id: ID of the resource group. This ID is mutually exclusive with --resource-group-name.
* --resource-group-name: Name of the resource group. This name is mutually exclusive with --resource-group-id.
* --output: Specify output format, only JSON is supported. One of: JSON.
* --interactive, -i:
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is instance-template-create-override-source-template
There are two basic types of compression, lossy and lossless. The audio format and compression algorithm that you choose can have a direct impact on the accuracy of speech recognition.

Audio formats that use lossy compression significantly reduce the size of your audio stream. But compressing the audio too severely can result in lower transcription accuracy. You can't hear the difference, but the service is much more sensitive to such data loss.



 Comparing approximate audio sizes 

Consider the approximate size of the data stream that results from 2 hours of continuous speech transmission that is sampled at 16 kHz and at 16 bits per sample:



* If the data is encoded with the audio/wav format, the two-hour stream has a size of 230 MB, well beyond the service's 100 MB limit.
* If the data is encoded in the audio/ogg format, the two-hour stream has a size of only 23 MB, well beneath the service's limit.



The following table approximates the maximum duration of audio that can be sent for speech recognition with a synchronous HTTP or WebSocket request in different formats. The duration considers the 100 MB service limit. Actual values can vary depending on the complexity of the audio and the achieved compression rate.



Table 5. Maximum duration of audio in different formats

 Audio format Maximum duration of audio (approximate) 

 audio/wav 55 minutes 
 audio/flac 1 hour 40 minutes 
 audio/mp3 3 hours 20 minutes 
 audio/ogg 8 hours 40 minutes 



In testing to compare the different audio formats, IBM® determined that the WAV and FLAC formats delivered the best word error rate (WER). These formats can serve as a baseline for transcription accuracy because they maintain the audio intact with no data loss. The Ogg format with the Opus coded showed a slight degradation of 2% WER relative to the baseline. The MP3 format delivered the worst results, with a 10% degradation of WER relative to the baseline.

The audio/ogg;codecs=opus and audio/webm;codecs=opus formats are generally equivalent, and their sizes are almost identical. They use the same codec internally; only the container format is different.





 Maximizing transcription accuracy