vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Free PE 2560
Allocated PE 5119
PV UUID dehWT5-VxgV-SJsb-ydyd-1Uck-JUA9-B9w0cO

--- Physical Segments ---
Physical extent 0 to 5118:
Logical volume /dev/vg00/vol_projects
Logical extents 6399 to 11517
Physical extent 5119 to 7678:
FREE
Show more
2. Resize Logical Volume.

 lvextend -l +100%FREE -r /dev/vg00/vol_projects
Size of logical volume vg00/vol_projects changed from 49.99 GiB (12798 extents) to 59.99 GiB (15358 extents).
Logical volume vg00/vol_projects successfully resized.
resize2fs 1.42.9 (28-Dec-2013)
Filesystem at /dev/mapper/vg00-vol_projects is mounted on /projects; on-line resizing required
old_desc_blocks = 7, new_desc_blocks = 8
The filesystem on /dev/mapper/vg00-vol_projects is now 15726592 blocks long.

 lvdisplay
--- Logical volume ---
LV Path /dev/vg00/vol_projects
LV Name vol_projects
VG Name vg00
LV UUID z1lukZ-AuvR-zjLr-u1kK-eWcp-AHjX-IcnerW
LV Write Access read/write
LV Creation host, time acs-kyungmo-lamp.tsstesting.com, 2021-12-07 19:34:39 -0600
LV Status available
 open 1
LV Size 59.99 GiB <--- new logical volume size
Current LE 15358
Segments 4
Allocation inherit
Read ahead sectors auto
- currently set to 8192
Block device 253:2
Show more
3. Verify file system size.

 df -Th /projects
Item: js_large_file_c697db513f8211e9b1228597cf8e3a32.bin (20971520 bytes).
DONE!

Deleting item: js_large_file_c697db513f8211e9b1228597cf8e3a32.bin
Item: js_large_file_c697db513f8211e9b1228597cf8e3a32.bin deleted!
DONE!

Deleting item: js_file_c697db503f8211e9b1228597cf8e3a32.txt
Item: js_file_c697db503f8211e9b1228597cf8e3a32.txt deleted!
DONE!

Deleting bucket: js.bucket.c697b4403f8211e9b1228597cf8e3a32
Bucket: js.bucket.c697b4403f8211e9b1228597cf8e3a32 deleted!
DONE!
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]/.

--id (string)
: Unique identifier for integration. Required.

The maximum length is 100 characters. The minimum length is 1 character. The value must match regular expression /[a-zA-Z0-9-:_]/.









 Send notifications 



 ibmcloud event-notifications Send notifications 



* Action: Use below command to send notifications in cli version 0.0.7.

ibmcloud event-notifications send-notifications --instance-id INSTANCE-ID --subject SUBJECT --severity SEVERITY --id ID --source SOURCE --en-source-id EN-SOURCE-ID --type TYPE --time TIME [--data DATA] [--push-to PUSH-TO] [--message-fcm-body MESSAGE-FCM-BODY] [--message-apns-headers MESSAGE-APNS-HEADERS] [--message-apns-body MESSAGE-APNS-BODY] [--datacontenttype DATACONTENTTYPE] [--specversion SPECVERSION]
* Action: Use below command to send notifications in cli version 0.0.8 and higher.
! ! '
<-- </section "id="section-project-create-examples" "> --><-- </section "id="section-project-cli-create-command" "> --><-- <section "id="section-project-cli-list-command" "> --> ibmcloud project list List existing projects. Projects are sorted by ID. Note: If the --all-pages option is not set, the command will only retrieve a single page of the collection. ibmcloud project list --start START] --limit LIMIT] ! ! ! ! !
<-- <section "id="section-project-list-cli-options" "> --> Command options --start (string): Marks the last entry that is returned on the page. The server uses this parameter to determine the first entry that is returned on the next page. If this parameter is not specified, the logical first page is returned.
The default value is ``. The maximum length is 512 characters. The minimum length is 0 characters. The value must match regular expression /^\S+$/.
--limit (int64): Determine the maximum number of resources to return. The number of resources that are returned is the same, with the exception of the last page.
The default value is 10. The maximum value is 100. The minimum value is 1.
--all-pages (bool): Invoke multiple requests to display all pages of the collection for list.<-- </section "id="section-project-list-cli-options" "> --><-- <section "id="section-project-list-examples" "> --> Example ibmcloud project list --start=exampleString --limit=10
<-- </section "id="section-project-list-examples" "> --><-- <section "id="section-project-list-cli-output" "> --> Example output A projects list results example {
"limit" : 10,
The value must match regular expression /[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}/.

--id (string)
: The ID of the secret version. Required.

The maximum length is 36 characters. The minimum length is 7 characters. The value must match regular expression /^([0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}|current|previous)$/.

--secret-version-metadata-patch (generic map)
: JSON Merge-Patch content for update_secret_version_metadata.

Provide a JSON string option or specify a JSON file to read from by providing a filepath option that begins with a @, e.g. --secret-version-metadata-patch=@path/to/file.json.

--version-custom-metadata (generic map)
: The secret version metadata that a user can customize.





 Example 

ibmcloud secrets-manager secret-version-metadata-update --secret-id=0b5571f7-21e6-42b7-91c5-3f5ac9793a46 --id=eb4cf24d-9cae-424b-945e-159788a5f535 --version-custom-metadata='{"anyKey": "anyValue"}'







 ibmcloud secrets-manager secret-version-action-create 

Create a secret version action. This operation supports the following actions:



* private_cert_action_revoke_certificate: Revoke a version of a private certificate.



ibmcloud secrets-manager secret-version-action-create --secret-id SECRET-ID --id ID --secret-version-action-prototype SECRET-VERSION-ACTION-PROTOTYPE
It can be any string of 4 - 30 characters.

--cr-pwd-path FILE-PATH
: Is the path to the file that contains the container repository password.

To ensure there are no trailing spaces in the file path, you can specify it as vi -b file_name , :set noeol, :wq.

--no-auth
: Is the parameter that must be set if the image does not require authorization to download. In this case, you don't need to provide cr-username and cr-pwd-path parameters. If you do, these parameters are ignored.

--allowed-env-keys ENV-KEYS
: Specifies the allowed environment variable keys as a comma-separated list. The keys must be strings of 1 - 64 characters.

--no-env
: This parameter can be set if the image does not require any allowed environment variables. In this case, you don't need to provide the allowed-env-keys parameter. If you do, it is ignored.

--image-key-id IMAGE-KEY-ID
: The ID of the root key that was used to sign the image. It must contain 64 characters long. If the image-key-id is not specified, the command first tries to determine the ID automatically by requesting the container registry notary service. You are prompted for this parameter for Docker Hub images.

--fingerprint FINGERPRINT
: If the image is in ICR, the fingerprint of the gpg key that is used to sign the image must be provided. You can get the fingerprint by using the gpg --list-keys name_of_the_key command. For example, when you run the gpg --list-keys latestnewkey command, the following snippet is an example of the output:

pub rsa4096 2023-01-12 [SCEA] [expires: 2024-04-28]
322A65D5B50BF16F5FDB6D7173943217FCD72F51
uid [ultimate] latestnewkey
<latestnewkey@example.com>
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]/.

[--force]
: Activate to force resource deletion (to bypass the confirmation prompt).







 ibmcloud event-notifications source delete 



* Action: Delete specific Source.

ibmcloud event-notifications source delete --instance-id INSTANCE-ID --id ID
* Parameters to provide:

--id ID (string)
: Unique identifier for source. Required.

The maximum length is 100 characters. The minimum length is 1 character. The value must match regular expression /[a-zA-Z0-9-:_]/.

[--instance-id INSTANCE-ID] (string)
: The 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]/.

[--force]
: Activate to force resource deletion (to bypass the confirmation prompt).









 Destinations 

Operate on IBM Cloud Event Notifications destination.

ibmcloud event-notifications destination --help



 ibmcloud event-notifications destination create 



* Action: Create a destination.

ibmcloud event-notifications destination create --name NAME --type TYPE [--description DESCRIPTION] [--certificate CERTIFICATE] [--certificate-content-type CERTIFICATE-CONTENT-TYPE] [--config CONFIG] [--instance-id INSTANCE-ID]
* Parameters to provide:

--instance-id (string)
The max_background option sets the global maximum number of such concurrent asynchronous requests. By default, it is set to 12, but setting it to an arbitrary high value (1000) prevents read requests from being blocked, even when reading a large number of files simultaneously.
4. max_stat_cache_size=100000 reduces the number of redundant HTTP HEAD requests sent by s3fs and reduces the time it takes to list a directory or retrieve file attributes. Typical file system usage makes frequent access to a file’s metadata via a stat() call which maps to HEAD request on the object storage system. By default, s3fs caches the attributes (metadata) of up to 1000 objects. Each cached entry takes up to 0.5 KB of memory. Ideally, you would want the cache to be able to hold the metadata for all of the objects in your bucket. However, you may want to consider the memory usage implications of this caching. Setting it to 100000 will take no more than 0.5 KB * 100000 = 50 MB.
5. multipart_size=52 will set the maximum size of requests and responses sent and received from the COS server, in MB scale. s3fs sets this to 10 MB by default. Increasing this value also increases the throughput (MB/s) per HTTP connection. On the other hand, the latency for the first byte served from the file will also increase. Therefore, if your use-case only reads a small amount of data from each file, you probably do not want to increase this value. Furthermore, for large objects (say, over 50 MB) throughput increases if this value is small enough to allow the file to be fetched concurrently using multiple requests. I find that the optimal value for this option is around 50 MB. COS best practices suggest using requests that are multiples of 4 MB, and thus the recommendation is to set this option to 52 (MB).
6. parallel_count=30 sets the maximum number of requests sent concurrently to COS, per single file read/write operation. By default, this is set to 5. For very large objects, you can get more throughput by increasing this value.
limit=page_size+1, Fetch page_size + 1 documents
start_key=documents-1]"id"] !! + 'u0000'
).get_result()
pageSize := core.Int64Ptr(5)
postAllDocsOptions := service.NewPostAllDocsOptions(
"orders",
)
postAllDocsOptions.SetLimit(pageSize)

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

for len(allDocsResult.Rows) > 0 {
documents := allDocsResult.Rows
b, err := json.MarshalIndent(documents, "", " ")
if err = nil {
panic(err)
}
fmt.Printf(string(b))
// The startKeyDocId of the next request becomes the last document id appended with u0000
postAllDocsOptions.SetStartKey(documentslen(documents)-1]! .ID + "u0000")
allDocsResult, _, err = service.PostAllDocs(postAllDocsOptions)
if err = nil {
panic(err)
}
}
See the following example of a first response: {
"total_rows": 11,
"offset": 0,
"rows":
{ "id": "4eee973603bf77f30b1f880ed83df76a" ....},
{ "id": "4eee973603bf77f30b1f880ed83f469a" ....},
{ "id": "65fa623a384648740ec1f39b495d591c" ....},
* Maximum number of translation pairs: 500,000 for all corpora combined.
* Maximum (cumulative) file size: 250 MB for all corpora combined.
* You can submit multiple parallel corpus files by repeating the parallel_corpus multipart form parameter.





 Parallel corpus example 

The following is a small piece of an English to French parallel corpus that was downloaded from the [MultiUN collection](http://opus.nlpl.eu/MultiUN.php) available on the OPUS open parallel corpus website. You can download a compressed version of the entire TMX file: [en-fr.tmx.gz](http://opus.nlpl.eu/download.php?f=MultiUN/en-fr.tmx.gz).

<?xml version="1.0" encoding="UTF-8" ?>
<tmx version="1.4">
<header creationdate="Tue Jan 29 12:49:40 2013"
srclang="en"
adminlang="en"
o-tmf="unknown"
segtype="sentence"
creationtool="Uplug"
creationtoolversion="unknown"
datatype="PlainText" />
<body>
<tu>
<tuv xml:lang="en"><seg>RESOLUTION 55/100</seg></tuv>
<tuv xml:lang="fr"><seg>RÉSOLUTION 55/100</seg></tuv>
</tu>
<tu>
<tuv xml:lang="en"><seg>Adopted at the 81st plenary meeting, on 4 December 2000, on the recommendation of the Committee (A/55/602/Add.2 and Corr.1, para. 94),The draft resolution recommended in the report was sponsored in the Committee by: Bolivia, Cuba, El Salvador, Ghana and Honduras. by a recorded vote of 106 to 1, with 67 abstentions, as follows:</seg></tuv>
[Import icon](https://cloud.ibm.com/docs-content/v1/content/a2b18c153837bce00a5b4de496e4b4ca64bbf56e/assistant-data/images/importGA.png), and then drag a file or browse to select a file from your computer.

Important: The maximum CSV file size is 10 MB. If your CSV file is larger, consider splitting it into multiple files and importing them separately.

The file is validated and imported, and the system begins to train itself on the new data.



You can view the imported intents and the corresponding examples on the Intents tab. You might need to refresh the page to see the new intents and examples.





 Resolving intent conflicts 

The Watson Assistant application detects a conflict when two or more intent examples in separate intents are so similar that Watson Assistant is confused as to which intent to use.

To resolve conflicts:



1. From the Intents page, review any intents with conflicts.

![Shows an intent list with a conflict](https://cloud.ibm.com/docs-content/v1/content/a2b18c153837bce00a5b4de496e4b4ca64bbf56e/assistant-data/images/intent-conflicts.png)
2. Click an intent with a conflict to open it. Find the user example that is causing the conflict, and then click Resolve conflicts.

![Shows an intent with a user example list where one of the user examples has a Resolve conflicts button](https://cloud.ibm.com/docs-content/v1/content/a2b18c153837bce00a5b4de496e4b4ca64bbf56e/assistant-data/images/intent-resolve-conflicts.png)
3. Choose whether to delete the example from the intent or to move it to another intent.

!
Optional fields
allowed_virtual_guest_ids = ["28961689"]
allowed_subnets = ["10.146.139.64/26"]
allowed_ip_addresses = ["10.146.139.84"]
snapshot_capacity = 10
hourly_billing = true

 Optional fields for snapshot
snapshot_schedule {
schedule_type = "WEEKLY"
retention_count = 20
minute = 2
hour = 13
day_of_week = "SUNDAY"
enable = true
}
}

For more information about the arguments and attributes, see [ibm_storage_block](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/storage_block).





 Provision Performance File Storage for Classic with Terraform 

You can use the following example to create a 20 GB block storage volume with custom 100 IOPS performance level.

resource "ibm_storage_file" "fs_performance" {
type = "Performance"
datacenter = "dal09"
capacity = 20
iops = 100

 Optional fields
allowed_virtual_guest_ids = ["28961689"]
allowed_subnets = ["10.146.139.64/26"]
allowed_ip_addresses = ["10.146.139.84"]
hourly_billing = true
}

For more information about the arguments and attributes, see [ibm_storage_file](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/storage_file).

By default, you can provision a combined total of 700 File Storage for Classic volumes. To increase the number of your volumes, contact your sales representative. Read about increasing limits [here](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-managinglimits).
ContactInfo,fullUSphone,/(d{3})-(d{3})-(d{4})/
ContactInfo,internationalPhone,/^((?+?[0-9])?)?[0-9_- ()]$/
ContactInfo,email,/b[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+.[A-Za-z]{2,}b/
ContactInfo,website,/(https?://)?([da-z.-]+).([a-z.]{2,6})([/w .-])/?$/

Save the CSV file with UTF-8 encoding and no byte order mark (BOM). The maximum CSV file size is 10MB. If your CSV file is larger, consider splitting it into multiple files and uploading them separately. Open your dialog skill and then click the Entities tab.
2. Click the upload icon ![Upload icon](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/upload.png).
3. Drag a file, or browse to select a file from your computer, and then click Upload.

The file is validated and uploaded, and the system begins to train itself on the new data.



You can view the uploaded entities on the Entities tab. You might need to refresh the page to see the new entities.





 Deleting entities 

You can select a number of entities for deletion.

When you delete an entity, you remove any values, synonyms, patterns, or annotations that are associated with the entity. This data cannot be retrieved later. All dialog nodes that reference these entities or values must be updated manually to no longer reference the deleted content.



1. Go to the Entities page.
curl -k -sS -X PATCH "$api_endpoint/v1/volumes/$1?generation=$generation&version=$api_version" -H "Authorization: Bearer $iam_token" -d '
{
"capacity": 200
} ' | jq .
5. Validate if the latest capacity is 250 G.

root@ubuntu-18-04: lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 252:0 0 250G 0 disk
├─vda1 252:1 0 99.9G 0 part /
├─vda14 252:14 0 4M 0 part
└─vda15 252:15 0 106M 0 part /boot/efi
vdb 252:16 0 370K 0 disk
vdc 252:32 0 44K 0 disk
root@ubuntu-18-04: growpart /dev/vda 1

If the capacity is not 250 G, issue the following command to grow the partition size to cover maximum available space.

root@ubuntu-18-04: growpart /dev/vda 1
CHANGED: partition=1 start=227328 old: size=209487839 end=209715167 new: size=524060639,end=524287967
root@ubuntu-18-04: lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 252:0 0 250G 0 disk
├─vda1 252:1 0 249.9G 0 part /
├─vda14 252:14 0 4M 0 part
└─vda15 252:15 0 106M 0 part /boot/efi
vdb 252:16 0 370K 0 disk
vdc 252:32 0 44K 0 disk
6. Issue the command df -kh to test if the file system got resized. If it shows no changes, issue the following command to resize the file system (xfs or ext4) along with modifications for physical volume, volume group, and logical volume.

root@ubuntu-18-04: resize2fs /dev/vda1
This limitation does not apply to expiration rules. 
 Transition Container Days, StorageClass Rule Limit 1 transition rule, and 1000 rules in total. 
 Days Non-negative integer None Transition Must be a value equal to or greater than 0. 
 Date Date None Transition Must be in ISO 8601 Format and the date must be in the future. 
 StorageClass String None Transition Must be set to GLACIER or ACCELERATED. 
 ExpiredObjectDeleteMarker Boolean None Expiration Must be true or false. 
 NoncurrentVersionExpiration Container NoncurrentDays NoncurrentVersionExpiration Limit 1 
 NoncurrentDays Positive Integer None Transition Must be a value greater than 0. 
 AbortIncompleteMultipartUpload Container DaysAfterInitiation Rule Limit 1 
 DaysAfterInitiation Non-negative Integer None AbortIncompleteMultipartUpload Must be a value greater than 0. 



IBM Cloud Object Storage IaaS (non-IAM) accounts are unable to set the transition storage class to ACCELERATED.

<LifecycleConfiguration>
<Rule>
<ID>{string}</ID>
<Status>Enabled</Status>
<Filter>
<Prefix/>
</Filter>
<Transition>
<Days>{integer}</Days>
<StorageClass>GLACIER</StorageClass>
</Transition>
</Rule>
</LifecycleConfiguration>

The required Content-MD5 header needs to be the binary representation of a base64-encoded MD5 hash. The following snippet shows one way to achieve the content for that particular header.

echo -n (XML block) | openssl dgst -md5 -binary | openssl enc -base64



Example request

PUT /apiary?lifecycle HTTP/1.1
Content-Type: text/plain
Host: s3.us.cloud-object-storage.appdomain.cloud
Authorization: {authorization-string}
Content-Type: text/plain
Content-MD5: M625BaNwd/OytcM7O5gIaQ==
Content-Length: 305

Example request
log.warning("Sample message 1", {'app': 'sample-app'})
log.info("Sample message 2", {'app': 'sample-app'})
Show more
2. From the command line, run the following command:

python3 send-logs.py







 Limits when you send logs 

Consider the following limits when you send logs to an IBM Log Analysis instance:



* Body size: Maximum size of 10 MB at ingestion.
* Message size: Maximum size of 16 KB at ingestion. After 16K, the data is truncated at ingestion.
* Metadata size: Maximum size of 32 KB.
* Hostname length: Maximum size of 256 characters.
* App name length: Maximum size of 512 characters.
* Log Level: Maximum size of 80 characters.
* Tags: Maximum size of 80 characters.
* Depth of nested fields: 3 is the maximum number of nested fields that are parsed at ingestion.
* Number of unique fields: A maximum of 500 fields are indexed per day.
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 
 4,000-7,999 300-48,000 
 8,000-9,999 500-48,000 
 10,000-12,000 1,000-48,000 
 Up to 24,000 Up to 96,000 [by special request](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-expandCapacityincreasecapacityover12TB) 
 Up to 18,000 Up to 180,000 [by special request](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-expandCapacityincreasecapacityover12TB) 







 BI.S4.H2.192 (boot only) 

Link to Profile: [BI.S4.H2.192 (boot only)](https://cloud.ibm.com/gen1/infrastructure/provision/bm?imageItemId=13467&packageId=1109&presetId=1089)



 Required configuration of disk mount points and Partitions 



 Array Partition Name Size (GB) 

 RAID1-A /dev/sda 
 /dev/sda1 /boot 50 
 /dev/sda2 / 150 
 /dev/sda3 /usr/sap 150 
 /dev/sda4 /hana/log remaining capacity 
 RAID1-B /dev/sdb 
 /dev/sdb1 /hana/shared 250 
 /dev/sdb2 /hana/data remaining capacity 









 BI.S4.H2.384 (boot only)
The list items must match regular expression /^([0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}|default)$/. The maximum length is 201 items. The minimum length is 0 items.

--all-pages (bool)
: Invoke multiple requests to display all pages of the collection for secrets.





 Example 

ibmcloud secrets-manager secrets --offset=0 --limit=10 --sort=created_at --search=example --groups=default





 Example output 

Example secret metadata collection response

{
"first" : {
"href" : "https://us-south.secrets-maanger.cloud.ibm.com/88b75b20-aa21-4174-85c9-1feb3cc93c9a/api/v2/secrets?limit=50"
},
"previous" : {
"href" : "https://us-south.secrets-maanger.cloud.ibm.com/88b75b20-aa21-4174-85c9-1feb3cc93c9a/api/v2/secrets?offset=50&limit=50"
},
"last" : {
"href" : "https://us-south.secrets-maanger.cloud.ibm.com/88b75b20-aa21-4174-85c9-1feb3cc93c9a/api/v2/secrets?offset=200&limit=50"
},
"limit" : 50,
"next" : {
"href" : "https://us-south.secrets-maanger.cloud.ibm.com/88b75b20-aa21-4174-85c9-1feb3cc93c9a/api/v2/secrets?offset=150&limit=50"
},
"offset" : 100,