vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Click the overflow menu (ellipsis).
3. Select Rename.
4. Enter a new name and click Rename.



Valid mount target names can include a combination of lowercase alpha-numeric characters (a-z, 0-9) and the hyphen (-), up to 63 characters. Mount target names must begin with a lowercase letter.





 Update a file share profile in the UI 

You can change the profile for a file share from the current profile to another IOPS tier profile, to a custom profile, or to a high-performance dp2 profile. Your billing adjusts based on the type of profile that you choose.



1. Go to the [file shares details](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-view&interface=uifs-view-single-share-ui) page.
2. Click the pencil icon next to the current profile or use the Actions menu and select Edit IOPS profile. A side panel shows the current profile, file share size, and maximum IOPS.
3. For New profile, click the down arrow. You can select a new IOPS tier, a custom profile, or dp2. For Custom IOPS or dp2, specify a new max IOPS based on the file share size. The file share price is automatically calculated based on your seletion.
4. Click Save and continue.







 Delete file shares and mount targets in the UI 

To delete a file share, you must first delete all its associated mount targets.

If the file share is configured for replication, you need to take extra steps. For more information, see [Deleting a replica file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-manage-replication&interface=apifs-delete-replicas).



 Delete mount target of a file share in the UI 

To delete a mount target, the file share must be in a stable state.



1.
Kubernetes CPU limit 1 3 5 
 Kubernetes Memory Request 1024 MB 3072 MB 6144 MB 
 Kubernetes Memory Limit 1024 MB 3072 MD 6144 MB 
 Dragent Memory Watchdog 512 MB 1024 MB 2048 MB 
 Cointerface Memory Watchdog 512 MB 2048 MB 4096 MB 



The Monitoring agent has its own memory watchdog to prevent runaway memory consumption on the host in case of memory leaks. The [agent configuration file](https://cloud.ibm.com/docs/monitoring?topic=monitoring-change_kube_agent) can be modified to meet your environment needs.

By default the following is configured:

watchdog:
max_memory_usage_mb: 1024
max_memory_usage_subprocesses:
sdchecks: 128
sdjagent: 256
mountedfs_reader: 32
statsite_forwarder: 32
cointerface: 512
promscrape: 640

The max_memory_usage value corresponds to the dragent process in the agent. All values are specified in MB. For example if you want to change the configuration to match the watchdog settings for a large environment you would specify the following:

watchdog:
max_memory_usage_mb: 2048
max_memory_usage_subprocesses:
sdchecks: 128
sdjagent: 256
mountedfs_reader: 32
statsite_forwarder: 32
cointerface: 4096
promscrape: 640

The value for promscape depends on the amount of timeseries and label data to be scraped on a particular node. The cluster size does not affect promscape memory usage.
The storage required for the SAP file systems - /usr/sap, /hana/shared, /hana/data, and /hana/log - is not provided, significantly reducing the server cost.

To run SAP HANA on a boot-only server, you must add IBM Cloud storage to the server.

SAP HANA Tailored Data Center Integration (TDI) requirements must be met to run SAP HANA as Production for the SAP System/s, or in a production-like environment. To fulfill SAP HANA TDI key performance indicators (TDIs), storage performance must meet minimum values.



 IBM Cloud File Storage for Classic with Boot-only services 

To run SAP HANA in production and production-like setups that use IBM Cloud File Storage for Classic, based on the Network File System (NFS) protocol, requires:



* Minimum of 8 K IOPS for /hana/log
* Minimum of 7 K IOPS for /hana/data



You can share storage areas for /hana/shared with /hana/log or /hana/data if these areas are too large for your particular use case.

For non-production use, you can use one storage area for /hana/shared, /hana/log, and /hana/data.

These minimums are for either Endurance or Performance options available with IBM Cloud File Storage for Classic:



* Endurance storage is a predefined IOPS per GB of storage, for example, 0.25 up to 10 IOPS per GB.
* Performance storage has different ranges of IOPS per GB, depending on the total size of the storage device. This option is more customizable.



This table compares the file storage (using NFS protocol) and the performance IOPS range for the capacity:



Table 3. IBM Cloud File Storage for Classic Performance storage GB and IOPS

 File Storage capacity (GB) Performance custom IOPS 

 20-39 100-1,000 
 40-79 100-2,000 
 80-99 100-4,000 
 100-499 100-6,000 
 500-999 100-10,000 
 1,000-1,999 100-20,000 
 2,000-2,999 200-40,000 
 3,000-3,999 200-48,000
provisioner: ibm.io/ibmc-file
parameters:
type: "Performance"
classVersion: "2"
sizeIOPSRange: |-
"[20-39]Gi:[100-1000]"
"[40-79]Gi:[100-2000]"
"[80-99]Gi:[100-4000]"
"[100-499]Gi:[100-6000]"
"[500-999]Gi:[100-10000]"
"[1000-1999]Gi:[100-20000]"
"[2000-2999]Gi:[200-40000]"
"[3000-3999]Gi:[200-48000]"
"[4000-7999]Gi:[300-48000]"
"[8000-9999]Gi:[500-48000]"
"[10000-12000]Gi:[1000-48000]"
mountOptions: nfsvers=<nfs_version>
Show more







 Removing persistent storage from a cluster 

When you set up persistent storage in your cluster, you have three main components: the Kubernetes persistent volume claim (PVC) that requests storage, the Kubernetes persistent volume (PV) that is mounted to a pod and described in the PVC, and the IBM Cloud infrastructure instance, such as classic file or block storage. Depending on how you created your storage, you might need to delete all three components separately.



 Understanding your storage removal options 

Removing persistent storage from your IBM Cloud account varies depending on how you provisioned the storage and what components you already removed.

Is my persistent storage deleted when I delete my cluster?
: During cluster deletion, you have the option to remove your persistent storage. However, depending on how your storage was provisioned, the removal of your storage might not include all storage components.
* 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.



Table 2. Sample storage configuration

 File system Volume Storage type IOPS/GB GB IOPS <br> 

 / vdal Pre-configured boot volume N/A 100 GB 3,000 
 /boot vda2 Pre-configured boot volume N/A 0.25 GB 3,000 
 /db2 vdd (can vary) Data volume 20 IOPS/GB 500 GB 10,000 
 backup/log and backup vde (can vary) Data volume 5 IOPS/GB 2,000 GB 4,000 



Table 1 shows a basic layout of the file system to support an IBM Db2 installation. Generally, an IBM Db2 installation uses subdirectories that can be segmented into independent volumes.

For example, "/db2/<DBSID>", "/db2/<DBSID>/log_dir", and several "sapdata<n>", where the folder "log_dir" contains the online logs files of the database and the "sapdata<n>" contains the data itself. 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
Setting this value too high can exceed your database's memory limits, which can cause it to crash.
* Default: 50
* Minimum: 10
* Maximum: 100
* Restarts database? - true



[innodb_flush_log_at_trx_commit](https://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.htmlsysvar_innodb_flush_log_at_trx_commit)



* Description: Controls the balance between strict [ACID](https://dev.mysql.com/doc/refman/5.7/en/glossary.htmlglos_acid) compliance for [commit](https://dev.mysql.com/doc/refman/5.7/en/glossary.htmlglos_commit) operations and higher performance that is possible when commit-related I/O operations are rearranged and done in batches. You can achieve better performance by changing the default value but then you can lose transactions in a crash.
* Default: 2
* Minimum: 0
* Maximum: 2
* Restarts database? - false



[innodb_log_buffer_size](https://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.htmlsysvar_innodb_log_buffer_size)



* Description: The size in bytes of the buffer that InnoDB uses to write to the [log files](https://dev.mysql.com/doc/refman/5.7/en/glossary.htmlglos_log_file) on disk.
* Default: 33554432
* Minimum: 1048576
* Maximum: 4294967295
* Restarts database? - true



[innodb_log_file_size](https://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.htmlsysvar_innodb_log_file_size)
Maximum Texture Dimension Size (x,y,z) 1D=(131072), 2D=(131072, 65536), 3D=(16384, 16384, 16384)
Maximum Layered 1D Texture Size, (num) layers 1D=(32768), 2048 layers
Maximum Layered 2D Texture Size, (num) layers 2D=(32768, 32768), 2048 layers
Total amount of constant memory: 65536 bytes
Total amount of shared memory per block: 49152 bytes
Total shared memory per multiprocessor: 65536 bytes
Total number of registers available per block: 65536
Warp size: 32
Maximum number of threads per multiprocessor: 2048
Maximum number of threads per block: 1024
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.
VOLUME GROUP: rootvg VG IDENTIFIER: 00f6db0a00004c000000016b94f02
VG STATE: active PP SIZE: 32 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 639 (20448 megabytes)
MAX LVs: 256 FREE PPs: 477 (15264 megabytes)
LVs: 12 USED PPs: 162 (5184 megabytes)
OPEN LVs: 11 QUORUM: 2 (Enabled)
TOTAL PVs: 1 VG DESCRIPTIORS: 2
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 1 AUTO ON: yes
MAX PPs per VG: 32512
MAX PPs per PV: 1016 MAX PVs: 32
LTG size(Dynamic): 512 kilobyte(s) AUTO SYNC: no
HOT SPARE: no BB POLICY: relocatable
PV RESTRICTION: none INFINITE RETRY: no
DISK BLOCK SIZE: 512 CRITICAL VG: no
FS SYNC OPTION: no CRITICAL PVs: no

Show more

Running the df -g command displays information about the total space and available space on a file system. In this instance, the rootvg volume group has enough space for creating a new file system, expanding an existing one, and storing the mksysb source image.

The storage information is shown as follow:

 df -g
Filesystem GB blocks Free %Used Iused %Iused Mounted on
/dev/hd4 0.09 0.06 41% 2619 17% /
/dev/hd2 2.16 0.26 89% 36565 37% /usr
/dev/hd9var 0.19 0.16 17% 953 3% /var
/dev/hd3 0.22 0.22 1% 33 1% /tmp
/dev/hd1 0.03 0.03 2% 7 1% /home
/dev/hd11admin 0.12 0.12 1% 5 1% /admin
/proc - - - - - /proc
* Default: 33554432
* Minimum: 1048576
* Maximum: 4294967295
* Restarts database? - true



[innodb_log_file_size](https://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.htmlsysvar_innodb_log_file_size)



* Description: The size in bytes of each [log file](https://dev.mysql.com/doc/refman/5.7/en/glossary.htmlglos_log_file) in a [log group](https://dev.mysql.com/doc/refman/5.7/en/glossary.htmlglos_log_group).
* Default: 67108864
* Minimum: 4194304
* Maximum: 274877906900
* Restarts database? - true



[innodb_lru_scan_depth](https://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.htmlsysvar_innodb_lru_scan_depth)



* Description: A parameter that influences the algorithms and heuristics for the [flush](https://dev.mysql.com/doc/refman/5.7/en/glossary.htmlglos_flush) operation for the InnoDB [buffer pool](https://dev.mysql.com/doc/refman/5.7/en/glossary.htmlglos_buffer_pool). A setting smaller than the default is generally suitable for most workloads. A value that is much higher than necessary might impact performance. Consider increasing the value only if you have spare I/O capacity under a typical workload.
* Default: 256
* Minimum: 128
* Maximum: 2048
* Restarts database? - false
The following values can be configured for the Database crawl seed file. To set these values, open the file config/seeds/database-seed.conf and specify the following values specific to your use cases:



* url - The URL of the table or view to retrieve. Defines your custom SQL database seed URL. The structure is:



* database-system://host:port/database?[per=num]&[sql=SQL]



Testing a seed URL shows all of the enqueued URLs. For example, testing the following URL for a database containing 200 records:



* sqlserver://test.mycompany.com:1433/WWII_Navy/?per=100&sql=select%20%20from%20vessel&



shows the following enqueued URLs:



* sqlserver://test.mycompany.com:1433/WWII_Navy/?key-val=0&
* sqlserver://test.mycompany.com:1433/WWII_Navy/?key-val=100&
* sqlserver://test.mycompany.com:1433/WWII_Navy/?key-val=200&



While testing the following URL shows the data retrieved from row 43:



* sqlserver://test.mycompany.com:1433/WWII_Navy/?per-1&key-val=43



* hops - Internal use only.
* default-allow - Internal use only.
* user-password - Credentials for the database system. The username and password need to be separated by a :, and the password must be encrypted using the vcrypt program shipped with the Data Crawler. For example: username:[vcrypt/3]]passwordstring
* max-data-size - Maximum size of the data for a document. This is the largest block of memory that is loaded at one time. Only increase this limit if you have sufficient memory on your computer.
* filter-exact-duplicates - Internal use only.
* timeout - Internal use only.
2017-09-01T11:00:42.36-0400 [API/0] OUT App instance exited with guid eecfba3b-430c-4a6b-b71f-ac72816fe152 payload: {"instance"=>"77dbb981-16d0-3a05-3235-9a4b", "index"=>0, "reason"=>"CRASHED", "exit_description"=>"2 error(s) occurred:nn* 2 error(s) occurred:nn Exited with status 137 (out of memory)n cancelledn cancelled", "crash_count"=>1, "crash_timestamp"=>1504278042244633291, "version"=>"6497b5b5-67d4-4c5a-b1af-362e522a029d"}
2017-09-01T11:00:43.35-0400 [CELL/0] OUT Successfully destroyed container

A possible solution is to set the --max_old_space_size option on the app's start command in the package.json file. This option represents part of the app's memory footprint and should be set to a value less than the total memory available to the app. Read about [Large memory spikes and Heroku](https://github.com/nodejs/node/issues/3370) for a more in-depth discussion of this topic.

"scripts": {
"start": "node --max_old_space_size=800 server.js"
}







 ASP.NET Core 

 What’s happening 

The app fails to deploy with the message: API/0App instance exited ... payload: {... "reason"=>"CRASHED", "exit_status"=>-1, ...}.

 Why it’s happening 

If you receive a similar message when you push your ASP.net app, it is most likely because your app exceeds either the memory or disk quota limits. Increase the quotas for memory or disk space for your app.
Dictionary file:<br><br><br><br> * CSV file in UTF-8 format<br> * ZIP of dictionaries downloaded from another workspace<br><br><br><br>Term entries file:<br><br><br><br> * CSV file in UTF-8 format<br><br><br> <br><br> * CSV file in UTF-8 format<br> * ZIP of dictionaries to use in another workspace<br><br><br> File size limitations:<br><br><br><br> * 1 MB per CSV term entries file<br> * 16 MB per CSV read-only dictionary file<br> * 15,000 entries per dictionary, except a read-only dictionary<br> * 64 dictionaries per workspace<br><br><br> 







 Machine learning model 

Table 2: Machine learning model



 Task Typical usage Supported input formats Supported output formats Limits and requirements 

 Document management Upload a small, representative subset of documents Upload documents that contain annotations previously added by a human annotator, a machine learning model, or a UIMA analysis engine You cannot ingest the entire corpus from IBM Watson Explorer for calculating high value documents for annotation. <br><br> * CSV file in UTF-8 format<br> * Text in UTF-8 format<br> * HTML<br> * PDF files (scanned and password-protected files are not supported)<br> * Microsoft Word DOC or DOCX files (password-protected files are not supported)<br> * ZIP file that contains documents downloaded from another workspace<br> * ZIP file that contains documents in UIMA CAS XMI format<br><br><br> ZIP archive file of documents <br><br> * 40,000 characters per document<br> * 10,000 documents per workspace<br> * 1,000 document sets (including annotation sets) per workspace<br> * 5 MB per file and 200 MB per upload (TXT, PDF, DOC, DOCX, and HTML files)<br><br><br> 
 Document annotation Manage human annotation.
Dictionary file:<br><br><br><br> * CSV file in UTF-8 format<br> * ZIP of dictionaries downloaded from another workspace<br><br><br><br>Term entries file:<br><br><br><br> * CSV file in UTF-8 format<br><br><br> <br><br> * CSV file in UTF-8 format<br> * ZIP of dictionaries to use in another workspace<br><br><br> File size limitations:<br><br><br><br> * 1 MB per CSV term entries file<br> * 16 MB per CSV read-only dictionary file<br> * 15,000 entries per dictionary, except a read-only dictionary<br> * 64 dictionaries per workspace<br><br><br> 







 Machine learning model 

Table 2: Machine learning model



 Task Typical usage Supported input formats Supported output formats Limits and requirements 

 Document management Upload a small, representative subset of documents Upload documents that contain annotations previously added by a human annotator, a machine learning model, or a UIMA analysis engine You cannot ingest the entire corpus from IBM Watson Explorer for calculating high value documents for annotation. <br><br> * CSV file in UTF-8 format<br> * Text in UTF-8 format<br> * HTML<br> * PDF files (scanned and password-protected files are not supported)<br> * Microsoft Word DOC or DOCX files (password-protected files are not supported)<br> * ZIP file that contains documents downloaded from another workspace<br> * ZIP file that contains documents in UIMA CAS XMI format<br><br><br> ZIP archive file of documents <br><br> * 40,000 characters per document<br> * 10,000 documents per workspace<br> * 1,000 document sets (including annotation sets) per workspace<br> * 5 MB per file and 200 MB per upload (TXT, PDF, DOC, DOCX, and HTML files)<br><br><br>
oc logs nvidia-devicequery-ppkd4

Example output

/cuda-samples/sample Starting...

CUDA Device Query (Runtime API) version (CUDART static linking)

Detected 1 CUDA Capable device(s)

Device 0: "Tesla P100-PCIE-16GB"
CUDA Driver Version / Runtime Version 11.4 / 11.7
CUDA Capability Major/Minor version number: 6.0
Total amount of global memory: 16281 MBytes (17071734784 bytes)
(056) Multiprocessors, (064) CUDA Cores/MP: 3584 CUDA Cores
GPU Max Clock rate: 1329 MHz (1.33 GHz)
Memory Clock rate: 715 Mhz
Memory Bus Width: 4096-bit
L2 Cache Size: 4194304 bytes
Maximum Texture Dimension Size (x,y,z) 1D=(131072), 2D=(131072, 65536), 3D=(16384, 16384, 16384)
Maximum Layered 1D Texture Size, (num) layers 1D=(32768), 2048 layers
Maximum Layered 2D Texture Size, (num) layers 2D=(32768, 32768), 2048 layers
Total amount of constant memory: 65536 bytes
Total amount of shared memory per block: 49152 bytes
Total shared memory per multiprocessor: 65536 bytes
Total number of registers available per block: 65536
Warp size: 32
Maximum number of threads per multiprocessor: 2048
Maximum number of threads per block: 1024
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
If your .tgz file size if greater than 40 MB. Then, use rm -rf .git .gitignore command to reduce the size of the .tgz file and then create tar czfv <reponame>.tgz ..

tar czvf observability.tgz .

Example output

a .
a ./output.tf
a ./main.tf
a ./.README.md.swp
a ./LICENSE
a ./observability.png
a ./diagrams
a ./observability.tgztar: ./observability.tgz: Can't add archive to itself

a ./README.md
a ./.secrets.baseline
a ./observability.drawio
a ./variables.tf
a ./local.tf
a ./version.tf
a ./diagrams/observability.png
a ./diagrams/observability.drawio







 Step 2: Creating a release 

Create a release in your source code repository to deliver and manage versions of your software. You can create new releases with release notes.



1. Find your existing repository in GitHub to upload your TGZ file.
2. Open the GitHub release page for your repository by appending /releases to your repository URL as shown in the following example.

https://github.com/<gh_org>/<gh_repo>/releases
3. Click Draft a new release.
4. Click Choose a tag, type a version number, a title, and an optional description for your release. Use the tagging suggestions in the GitHub UI to find a supported tag version.
5. If you had created a tag, use the drop-down menu to select the branch that contains the project you want to release.
6. Drag your TGZ file from your local machine to the Attach binary file by dropping them here or selecting them section.
7.
<br>.tf, .tfvars, .md, .yaml, .sh, .txt, .yml, .html, .gitignore, .tf.json, license, .js, .pub, .service, _rsa, .py, .json, .tpl, .cfg, .ps1, .j2, .zip, .conf, .crt, .key, .der, .jacl, .properties, .cer, .pem, .tmpl, .netrc. 
 SANDBOX_ANSIBLEACTIONWHITELISTEXTN From the Ansible Git repositories following are the allowed file extensions. <br>.tf, .tfvars, .md, .yaml, .sh, .txt, .yml, .html, .gitignore, license, .js, .pub, .service, _rsa, .py, .json, .tpl, .cfg, .ps1, .j2, .zip, .conf, .crt, .key, .der, .cer, .pem, .bash, .tmpl. 
 SANDBOX_BLACKLISTEXTN From the Git repositories following are the blocked file extensions. <br>.php5, .pht, .phtml, .shtml, .asa, .asax, .swf, .xap, .tfstate, .tfstate.backup, .exe. 
 SANDBOX_IMAGEEXTN From the Git repositories following are the allowed image file extensions. <br>.tif, .tiff, .gif, .png, .bmp, .jpg, .jpeg, .so. 
 SANDBOX_MAX_FILE_SIZE Maximum size of a file that is allowed from the Git repositories is 2 MB. (Yet to be implemented)
analysis-stempel The Stempel (Polish) Analysis plug-in integrates the Lucene stempel (polish) analysis module into Elasticsearch. 
 analysis-ukrainian The Ukrainian Analysis plug-in integrates the Lucene UkrainianMorfologikAnalyzer into Elasticsearch. 
 ingest-attachment An ingest processor that uses Apache Tika to extract contents. 
 mapper-size The Mapper Size plug-in allows document to record their uncompressed size at index time. 
 repository-s3 The S3 repository plug-in adds the repositories that are used for automated backups of your data. 



More details on the plug-ins are available in the [Elasticsearch documentation](https://www.elastic.co/guide/en/elasticsearch/plugins/current/index.html).