vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Domain Registration Agreement 

This Domain Registration Agreement ("Agreement") is between SoftLayer Technologies, Inc. ("SoftLayer", an IBM Company) and You and is effective on the date You accept it electronically. This Agreement represents the entire agreement between You and IBM Cloud regarding Your use of IBM Cloud’s Domain Name Registration Services (the “Services”). You acknowledge that You have read, understand and agree to be bound by Agreement, along with any new, different or additional terms, conditions or policies which IBM Cloud may establish from time to time. Your use – or continued use – of the Services after being provided notice of this Agreement constitutes acceptance of the Agreement. You agree to be bound by this Agreement for transactions entered into by You or anyone acting as Your Agent, and by anyone who uses the account You have established with IBM Cloud. You acknowledge that IBM Cloud is a registrar bound by an agreement with the Internet Corporation for Assigned Names and Numbers ("ICANN"). You agree that IBM Cloud may modify this Agreement in order to comply with applicable law and the terms and conditions set forth by ICANN from time to time.



 Fees 

You agree to pay IBM Cloud for the Services You purchase at the time they are provided. You understand that ICANN requires IBM Cloud to collect a small registration fee when You register a domain name, and You agree to pay such fees. Payments are non-refundable. If for any reason IBM Cloud is unable to charge Your payment method for the full amount owed, or if IBM Cloud is charged a penalty for any fee it previously charged to Your payment method, You agree that IBM Cloud may pursue all available remedies in order to obtain payment, including immediate cancellation, without notice, of any domain names registered or renewed by You or on Your behalf. IBM Cloud reserves the right to charge a reasonable service fee for administrative tasks outside the scope of its regular Services, including customer service issues that cannot be handled over email but require personal service, and disputes that require legal services. These charges will be billed to the payment method on file for You.





 Domain Name Renewals
You can check the default IO scheduler settings and try different schedulers to ensure optimization for your specific workload.
* [Enable Jumbo Frames](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-jumboframes) and configure them to be the same on the entire network path from source device <-> switch <-> router <-> switch <-> target device. If the entire chain isn't set the same, it defaults to the lowest setting along the chain. IBM Cloud® has network devices set to 9,000 currently. For best performance, all customer devices need to be set to the same 9,000 value.

Setting MTU to 9000 on your hosts has the following benefits:



* Data can be transmitted in fewer frames.
* Data can be transmitted in faster because fewer packets require fewer bytes of format information that is stored in the packet header.
* Throughput is increased by reducing the number of CPU cycles and instructions for packet processing.
* Jumbo frames provide less opportunity for packets to arrive out of order or to be lost, resulting in fewer retransmissions. Fewer retransmissions mean less time that is spent in TCP recovery. The result is greater throughput.



* Use NFSv3 protocol when possible. Network File System (NFS) is a networking protocol for distributed file sharing. It allows remote hosts to mount file systems over a network and interact with those file systems as if they are mounted locally. NFSv3 supports safe asynchronous writes and is more robust at error handling than the previous NFSv2. It supports 64-bit file sizes and offsets, allowing clients to access more than 2 GB of file data. NFSv3 natively supports no_root_squash that allows root clients to retain root permissions on the NFS share. NFSv4.1 is also supported. When File Storage for Classic is used in a VMware® deployment, NFSv4.1 might be the better choice for your implementation.
For more information about how to remove an entity extractor enrichment from a collection, see [Managing enrichments](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-manage-enrichments).



 Entity extractor output 

When the enrichment recognizes one of your custom entities in a document, an entry is added to the enriched_text.entities section of the JSON representation of the document. The section contains occurrences of entities that are recognized by your custom model along with entities that are recognized by the built-in Entities enrichment. The built-in enrichment uses the Watson NLP service to identity entites that are part of what it calls the Natural Language Understanding type system. For more information about the built-in Entities enrichment, see [Entities](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-nlunlu-entities).

The following JSON output is produced by a custom model that is named literature that recognizes family member mentions.

Zoom

![Shows the JSON output of a document with a custom entity mention.](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/discovery-data/images/json-literature.png)

Figure 11. JSON representation of a custom entity mention





 Monitoring performance over time 

You can retrain your entity extractor model at any time. Each time that you train the model, review the performance metric scores to determine whether your most recent changes increase or decrease the model's scores.



1. To compare one test run against another, click View score history.

The history view shows the last 5 training runs.

To retain the score information for more than the most recent 5 training runs, you can export the metrics in comma-separated value format, and track the scores in a separate application. Click the tabular representation icon !
You didn't provide the correct GitHub URL, or you provided a GitHub token, which is not required to clone a public repo. A GitHub access token is only required to access a private repo.

 How to fix it 

Do not provide a GitHub token, and check to see whether the GitHub token was provided in the github_token parameter while creating a workspace by using the public repo.





 Why is IBM Cloud Schematics not able to create a workspace? 

 What’s happening 

Schematics isn't able to create a workspace, and you are seeing the following error message: You don't have the required to create a workspace in any resource groups. You must be assigned the manager role on the Schematics service in at least one resource group. Contact your account administrator for access.

 Why it’s happening 

You don't have the required access to create a workspace in any resource groups. You must be assigned the manager role on the Schematics service in at least one resource group.

 How to fix it 

Contact your account administrator and get assigned with the manager role on the Schematics service in at least one resource group.





 Why is IBM Cloud Schematics not able to provision the cluster and fails with an error message for the lsf_license_confirmation variable? 

 What’s happening 

Schematics isn't able to provision the cluster, and you are seeing the following error message: Error: Invalid value for variable "lsf_license_confirmation"

 Why it’s happening 

You entered a value other than "true" for the property lsf_license_confirmation.

The property lsf_license_confirmation only accepts "true" as a valid value. A "true" value indicates that you have agreed to one of the following two conditions:



1. If you are deploying a production cluster, you have confirmed with your business team that you have enough licenses to deploy the IBM Spectrum LSF on IBM Cloud and that these licenses are covered for use under the International Program License Agreement (IPLA).
2.
It's possible to attach Block Storage for Classic with only a single path, but it is important that connections are established on both paths to ensure no disruption of service.

$ sudo multipath -ll
mpathb (360014051f65c6cb11b74541b703ce1d4) dm-1 LIO-ORG,TCMU device
size=1.0G features='0' hwhandler='0' wp=rw
|-+- policy='service-time 0' prio=1 status=active
| - 7:0:0:2 sdh 8:112 active ready running
-+- policy='service-time 0' prio=1 status=enabled
- 8:0:0:2 sdg 8:96 active ready running
mpatha (36001405b816e24fcab64fb88332a3fc9) dm-0 LIO-ORG,TCMU device
size=1.0G features='0' hwhandler='0' wp=rw
|-+- policy='service-time 0' prio=1 status=active
| - 7:0:0:1 sdj 8:144 active ready running
-+- policy='service-time 0' prio=1 status=enabled
- 8:0:0:1 sdi 8:128 active ready running

If MPIO isn't configured correctly, your storage device might disconnect and appear offline when a network outage occurs or when IBM Cloud® teams perform maintenance. MPIO ensures an extra level of connectivity during those events, and keeps an established session to the LUN with active read/write operations.

In the example,36001405b816e24fcab64fb88332a3fc9 is the WWID that is persistent while the volume exists. It is recommended that your application uses the WWID. It's also possible to assign more easier-to-read names by using "user_friendly_names" or "alias" keywords in multipath.conf.
Use GET /v1/security_groups/{id}?version=$version&generation=1 or ibmcloud is security-group to view the security groups details and VPC. Use GET /v1/instances/{id}?version=$version&generation=1 or ibmcloud is instance to view the instance details and VPC.





 security_group_order_bindings 

Message: Cannot delete the security group while it has pending instance orders.

If an instance was created with security group(s) specified on the network interfaces, the instance and network interfaces must be active before the security group can be deleted. Use GET /v1/security_groups/{id}/network_interfaces?version=$version&generation=1 or ibmcloud is security-group-network-interfaces to view attached network interfaces and their status. Once the status of the interfaces is 'available', try again. If this problem persists, [contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support).





 security_group_port_max_less_than_port_min 

Message: TCP/UDP max port cannot be less than min port.

The maximum port value cannot be less than the minimum port value. Specify a maximum port value that is larger than the minimum port value.





 security_group_port_range_both_or_neither 

Message: Port range must be unset, or both a minimum and maximum port must be set for 'tcp' and 'udp'.

Rules with a 'tcp' or 'udp' protocol may have an unset port range (to apply the rule to all traffic), or they may specify a port range. To restrict traffic to a single port, set both the minimum and maximum port to the port value. For example, the following command would create a rule to allow SSH on port 22: ibmcloud is security-group-rule-add <id> inbound tcp --port-min 22 --port-max 22.
2. Validate that multiple paths exist.

multipath -ll

This command reports the paths. If it is configured correctly, then each volume has a single group, with a number of paths equal to the number of iSCSI sessions. It's possible to attach Block Storage for Classic with only a single path, but it is important that connections are established on both paths to ensure no disruption of service.

$ sudo multipath -ll
mpathb (360014051f65c6cb11b74541b703ce1d4) dm-1 LIO-ORG,TCMU device
size=1.0G features='0' hwhandler='0' wp=rw
|-+- policy='service-time 0' prio=1 status=active
| - 7:0:0:2 sdh 8:112 active ready running
-+- policy='service-time 0' prio=1 status=enabled
- 8:0:0:2 sdg 8:96 active ready running
mpatha (36001405b816e24fcab64fb88332a3fc9) dm-0 LIO-ORG,TCMU device
size=1.0G features='0' hwhandler='0' wp=rw
|-+- policy='service-time 0' prio=1 status=active
| - 7:0:0:1 sdj 8:144 active ready running
-+- policy='service-time 0' prio=1 status=enabled
- 8:0:0:1 sdi 8:128 active ready running

If MPIO isn't configured correctly, your storage device might disconnect and appear offline when a network outage occurs or when IBM Cloud® teams perform maintenance. MPIO ensures an extra level of connectivity during those events, and keeps an established session to the LUN with active read/write operations.

In the example,36001405b816e24fcab64fb88332a3fc9 is the WWID that is persistent while the volume exists. We recommend that your application uses the WWID.
Supported parameters for provisioning a service instance with Terraform

 Parameter Description 

 name Required. The name of your Hyper Protect Crypto Services instance. 
 location Required. The region abbreviation, such as us-south, that represents the geographic area where the operational crypto units of your service instance are located. For more information, see [Regions and locations](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-regions). As recovery crypto units are available only in us-south and us-east, only these two regions are supported if you want to use Terraform for instance initialization. 
 plan Required. The pricing plan for your service instance. 
 units Required. The number of operational crypto units for your service instance. Valid values are 2 or 3. 
 failover_units Optional. The number of failover crypto units for your service instance. Valid values are 0, 2, or 3, and it must be less than or equal to the number of operational crypto units. If you set it 0, cross-region high availability will not be enabled. Currently, you can enable this option only in the us-south and us-east region. If you do not specify the value, the default value is 0. 
 service_endpoints Optional. The network access to your service instance. Valid values are public-and-private and private-only. If you do not specify the value, the default setting is public-and-private. 
 tags Optional. Tags that are associated with your instance are used to organize your resources. For more information about tags, see [Working with tags](https://cloud.ibm.com/docs/account?topic=account-tag). 
 resource_group_id Optional. The resource group where you want to organize and manage your service instance. If you do not specify the value, the default resource group is Default. 
 signature_threshold Required. The number of administrator signatures that is required to execute administrative commands. The valid value is in the range 1 - 8. You need to set it to at least 2 to enable quorum authentication. 
 revocation_threshold Required.
Selecting a profile that is not secure execution enabled will cause the provisioning to fail.



After the instance is resized, you are billed the hourly rate of the new instance profile.

You can track the instance resize in Activity Tracker and IBM® Log Analysis for troubleshooting and audit purposes.



 Resizing virtual servers on dedicated hosts 

Virtual servers that run on dedicated hosts can be resized only to profiles that are supported by the dedicated host that the instance is hosted on. For example, a virtual server that is provisioned with a profile from the Memory family can resize to other profiles that belong to the Memory family.

Resizing virtual servers on dedicated hosts is not supported for LinuxONE (s390x processor architecture).





 Resizing virtual servers with instance storage 

When you stop a virtual server instance with an instance storage profile, that storage is temporary storage and is available only while your virtual server is running. Data on the drive is unrecovered after the instance stops.





 Resizing virtual servers with data volumes 

Attached data volumes remain intact and are attached in the resized instance.

When resizing an instance to a smaller profile (one with fewer vCPUs), it might be necessary to adjust the instance’s storage bandwidth allocation. To successfully resize, the instance’s storage bandwidth must be at least 500 Mb/s less than the preallocated bandwidth in the target profile.

For example:



* Current profile: mx2-8x64 (total bandwidth: 16000 Mb/s, 12000 Mb/s network, 4000 Mb/s storage) (Assume that the instance is using default network and storage bandwidth allocation.)
* Target profile: bx2-2x8 (total bandwidth: 4000 Mb/s, 3000 Mb/s network, 1000 Mb/s storage)

The resize operation will fail because the current amount of storage bandwidth (4000 Mb/s) is not at least 500 Mb/s less than the target profile’s total bandwidth (4000 Mb/s). To successfully resize, you must adjust the instance’s storage bandwidth amount to 3500 Mb/s or less prior to attempting the resize operation.







 Resizing instances associated with instance templates and instance groups
See [FAQ](https://cloud.ibm.com/docs/CDN?topic=CDN-faqsare-there-any-restrictions-on-what-port-numbers-are-allowed) for allowed port numbers.
* certificateType: Type of certificate being used by a mapping. Can be WILDCARD_CERT or SHARED_SAN_CERT. Value is 0 for HTTP mappings.
* cname: Canonical name record that aliases the hostname. It can be provided by the user, or system-generated. If user-provided, it should be less than 64 alphanumeric characters, and it must be unique. If not provided, one is generated when the mapping is created.
* akamaiCname: Canonical name record that aliases the hostname. It's generated by Akamai, and can provide a shorter DNS lookup time.
* respectHeaders: A Boolean value that, if set to 'true', causes TTL settings in the origin to override CDN TTL settings.
* header: Specifies Host header information that is used by the origin server.
* status: The mapping's status. Status can be CNAME_CONFIGURATION, SSL_CONFIGURATION, RUNNING, STOPPED, DELETED, or ERROR.
* bucketName: Bucket name for your S3 object storage.
* fileExtension: File extensions that are allowed to be cached.
* path: The path to your S3 object storage. Usually found in the object store URL or API section of your service.
* cacheKeyQueryRule: The following options are available to configure Cache Key behavior:



* include-all: Include all query arguments Default
* ignore-all: Ignore all query arguments
* ignore: space separated query-args: Ignores those specific query arguments. For example, "ignore: query1 query2"
* include: space separated query-args: Includes those specific query arguments. For example, "include: query1 query2"





Of particular note is the uniqueId, which is generated when a mapping is created and is used as a parameter to subsequent API calls.
SC-10 - Network Disconnect 



  Control requirements 

SC-10 - 0
:   The information system terminates the network connection associated with a communications session at the end of the session or after [IBM Assignment: no longer than 30 minutes for RAS-based sessions or no longer than 60 minutes for non-interactive user sessions] of inactivity.





  Implementation guidance 

See the resources that follow to learn more about how to implement this control.



*  [Connecting application provider to the management VPC](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-connectivity-management)







  IBM Cloud for Financial Services profile 

The rules related to this control that follow are part of the IBM Cloud for Financial Services v1.2.0 profile in [IBM Cloud® Security and Compliance Center](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-getting-started).



*  Check that sign out for active sessions is set to # seconds or less for IBM Cloud accounts
*  Check whether App ID access tokens are configured to expire within # minutes







  NIST supplemental guidance 

This control applies to both internal and external networks. Terminating network connections associated with communications sessions include, for example, de-allocating associated TCP/IP address/port pairs at the operating system level, or de-allocating networking assignments at the application level if multiple application sessions are using a single, operating system-level network connection. Time periods of inactivity may be established by organizations and include, for example, time periods by type of network access or for specific network accesses.
In the event of a regional disaster, you must complete the following steps to establish cross-region high availability:



1. [Check the DR recovery region](https://cloud.ibm.com/docs/atracker?topic=atracker-ha_drha_dr_recovery_region).
2. If you have a target and a route configured in the recovery region, your auditing events will be routed to the target that is specified for that region.

If the region that goes down is also collecting global events in your account, you must update the route in the recovery region to collect global events.
3. If the recovery region is not configured, you must configure Activity Tracker Event Routing in the region. [Learn more](https://cloud.ibm.com/docs/atracker?topic=atracker-getting-started).



When Activity Tracker Event Routing recovers in the region that is down, your configuration is restored. If you had to enable collection of global auditing events in the recovery region, you must update the route to stop global events in that region.





 DR recovery time 

The following table indicates the estimated recovery times in the event of a DR situation:



Table 4. Recovery objectives for DR

 Recovery objective for DR Estimated time 

 Maximum Tolerable Downtime (MTD) / Recovery Time Objective (RTO) Less than 24 hours 
 Recovery Point Objective (RPO) Less than 24 hours
Use [fdisk for drives that are less than 2 TB](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-mountingLinuxfdisk) and [parted for a disk bigger than 2 TB](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-mountingLinuxparted).



 Creating a file system with fdisk 



1. Get the disk name.

fdisk -l | grep /dev/mapper

The disk name that is returned looks similar to /dev/mapper/XXX.
2. Create a partition on the disk.

fdisk /dev/mapper/XXX

The XXX represents the disk name that is returned in Step 1.
3. Create a file system on the new partition.

fdisk –l /dev/mapper/XXX



* The new partition is listed with the disk, similar to XXXp1, followed by the size, Type (83), and Linux®.
* Take a note of the partition name, you need it in the next step. (The XXXp1 represents the partition name.)
* Create the file system:

mkfs.ext3 /dev/mapper/XXXp1



4. Create a mount point for the file system, and mount it.



* Create a partition name PerfDisk or where you want to mount the file system.

mkdir /PerfDisk
* Mount the storage with the partition name.

mount /dev/mapper/XXXp1 /PerfDisk
* Check that you see your new file system listed.

df -h



5. Add the new file system to the system's /etc/fstab file to enable automatic mounting on boot.



* Append the following line to the end of /etc/fstab (with the partition name from Step 3).

/dev/mapper/XXXp1 /PerfDisk ext3 defaults,_netdev 0 1