vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Open-source licenses 

The IBM® license agreement and any applicable information on the web download page for IBM products refers Licensee to this file for details that concern notices applicable to code included in IBM Cloud Hyper Protect Crypto Services.

Notwithstanding the terms and conditions of any other agreement Licensee might have with IBM or any of the related or affiliated entities (collectively "IBM"), the third-party code that is identified below is subject to the terms and conditions of the IBM license agreement for the Program and not the license terms that might be contained in the notices below. The notices are provided for informational purposes.

This Notices file might identify information that is not used by, or that was not shipped with, the Program as Licensee installed it.

IBM doesn't represent or warrant that the information in this NOTICES file is accurate. Third-party websites are independent of IBM and IBM doesn't represent or warrant that the information on any third-party website referenced in this NOTICES file is accurate. IBM disclaims any liability for errors and omissions or for any damages accruing from the use of this NOTICES file or the contents, including without limitation URLs or references to any third-party websites.



 Hyper Protect Crypto Services notices and information 

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
NON-IBM-LICENSE INFORMATION FOR EXCLUDED COMPONENTS

Hyper Protect Crypto Services

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

TABLE OF CONTENTS

THIS NON-IBM-LICENSE FILE CONSISTS OF THE FOLLOWING SECTIONS:

CC-BY-SA-1.0
CC-BY-SA-2.0
CC-BY-SA-2.5
CC-BY-SA-3.0
GPL V2
GPL V3
Because the number of nodes needed for a quorum is updated automatically when nodes are added to the consenter set, it is a best practice to make sure that all of the nodes in the consenter set are servicing the channel before attempting to add a new node. This is because the consenter set is updated before the node has finished provisioning. For example, if you have three nodes servicing a channel, you will have a quorum as long as two nodes are up. When attempting to add a new node, the consenter set will index to three nodes being needed (out of four). In a case where only two nodes are up out of three when a new node is added, and the new node fails to provision for any reason, you will only have two nodes available out of the three that are needed.





 Overview 

Adding a node to the ordering service is, at a high level, a three step process.



1. Create the node to be added to an existing ordering service.
2. Add the node to the ordering system channel (this step can be omitted on ordering clusters that do not use a system channel). While this might seem logically similar to creating the node, it involves a different step. For more information, see [Adding the node to the ordering system channel](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-add-remove-ordereribp-console-add-remove-orderer-consenter-system-channel).
3. [Add the node to any application channels](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-add-remove-ordereribp-console-add-remove-orderer-consenters-add) where you want it to become a consenter.
For most entity examples, enabling the bulk label feature is helpful. You might want to skip it if a term has more than one meaning in different contexts. In that case, evaluate each occurrence individually. Remember, if you enable the bulk label feature, you can check the accuracy of the labels that were added automatically and make corrections when necessary as you review the document.

After you enable the bulk label feature, a notification is displayed that indicates how many occurrences of an entity example were found in the current document. From the current page, the labeling tool cannot access other documents to report how many occurrences exist in other documents from the collection. However, the mention count is shown in the Entity types panel. When you first open other documents, you can check the mention counts to see how many mentions were labeled automatically.

Did the bulk label feature miss an occurrence?

Occurrences of the term are not labeled if they occur in the same phrase in which the term is already labeled. For example, the first occurrence of the term husband is not labeled when the bulk label feature is switched on for the second occurrence of the term in the following sentence.

Zoom

![Shows when an overlapping occurrence is not given a label by the bulk label feature.](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/discovery-data/images/not-bulk-labeled.png)

Figure 9. Treatment of overlapping labels





 Entity example suggestions 

After you label enough examples, suggested entity type examples are displayed. The system learns from the types of examples you label, and applies what it learns to identify potential new examples. For example, after you label red, orange, yellow, green, and blue as examples of the color entity type, the Example suggestions panel might show indigo and violet as suggested examples for you to label. Suggestions are not displayed until after you label many examples of an entity type.

The following example shows suggestions that are made for family member mentions.

Zoom

![Shows suggestions for family member entities.]
Click the IBM Digital Provider Agreement link to review the agreement.
4. Select I understand and agree to the IBM Digital Provider Agreement, and click Save.







 Step 2: Provide your product name and type 

When you add a product, you can add a new product or import an existing product from a private catalog. For the purposes of this tutorial, add a new product.



1. From the IBM Cloud Partner Center, click Create.
2. Provide the name of your Operator bundle as it appears in the Red Hat registry in the product name field. For the purposes of this tutorial, you can enter Akka Cluster Operator.
3. Select the product type. For the purposes of this tutorial, select Deployable software.

The product type that you select is used for tax assessment purposes.
4. Click Add.







 Step 3: Define your catalog entry and product page 

Provide details that are displayed on your catalog entry and product page when your Operator bundle is published in the IBM Cloud catalog.



1. Click Product details > Add logo, and enter the URL to your company or product logo, such as http://svgur.com/i/TTP.svg.
2. Provide a short description of your product, which is displayed on your catalog entry. For the purposes of this tutorial, you can enter This Operator is a developer tool.
3. From the Category list, select an option that best fits how users might use your product, for example, Developer tools. Categories are used to organize products in the catalog based on common solutions, function, or use.
4. Enter keywords that users might use when they search the catalog for your product, for example, dev tools and operator.
5. Provide a list of features that highlights your product's attributes and benefits for users.

Use a descriptive title and 1 - 2 sentences for each feature. You want the information to be visually scannable for users.
6. Provide a detailed description of your product that explains its value and what users gain by using it. The detailed description is displayed at the beginning of your product page in the catalog.
Remediate technical changes in MAS through Maxadmin X 
 Remediate technical changes in MAS at OS Level X 
 Deploy Attachments X 
 Import Database X 
 Finalize any changes needed X 
 Ensure any integrations X 
 Test Changes X 
 Remediate errors Secondary Primary 







 Test 2 

This is similar to test 1, except the focus is ensuring all steps are documented and accurate timings taken for the final migration of production. This is a dress rehearsal for the go live as well as to ensure all issues identified in the first test have been resolved. This test should take place close to the final cut-over date (within a few weeks).



Table 1. Test 2 Responsibilities

 Task IBM Client (or Designate) 

 Export data from SaaS Flex and transfer to MAS X 
 Remediate technical changes in MAS through Maxadmin X 
 Remediate technical changes in MAS at OS Level X 
 Import Database X 
 Finalize any changes needed X 
 Finalize integrations X 
 Test Changes X 
 Remediate errors Secondary Primary 
 Ensure timings for all steps recorded X X 







 Live on MAS-Dedicated 

The final execution of the steps in the scheduled migration window. Once complete, the customer is now live on the Dedicated Service offering.



Table 1. Go Live Responsibilities

 Task IBM Client (or Designate) 

 Export data from SaaS Flex and transfer to MAS X 
 Remediate technical changes in MAS through Maxadmin X 
 Remediate technical changes in MAS at OS Level X 
 Deploy Attachments X 
 Import Database X 
 Finalize any changes needed X 
 Finalize Integrations X 
 Test Changes X 
 Go Live X 







 Post Live MAS-Dedicated Activities 

This is the support for customers after the go live. Any new issue is investigated and resolved and then the client moves to steady state.





 Roles and Responsibilities 

Both IBM and the client have critical roles in the successful transition to the Maximo Application Suite Dedicated offering. These responsibilities are summarized in the attached spreadsheet below (MAS-Dedicated Migration Swimlanes).
Remediate technical changes in MAS through Maxadmin X 
 Remediate technical changes in MAS at OS Level X 
 Deploy Attachments X 
 Import Database X 
 Finalize any changes needed X 
 Ensure any integrations X 
 Test Changes X 
 Remediate errors Secondary Primary 







 Test 2 

This is similar to test 1, except the focus is ensuring all steps are documented and accurate timings taken for the final migration of production. This is a dress rehearsal for the go live as well as to ensure all issues identified in the first test have been resolved. This test should take place close to the final cut-over date (within a few weeks).



Table 1. Test 2 Responsibilities

 Task IBM Client (or Designate) 

 Export data from SaaS Flex and transfer to MAS-SaaS X 
 Remediate technical changes in MAS through Maxadmin X 
 Remediate technical changes in MAS at OS Level X 
 Import Database X 
 Finalize any changes needed X 
 Finalize integrations X 
 Test Changes X 
 Remediate errors Secondary Primary 
 Ensure timings for all steps recorded X X 







 Live on MAS-SaaS 

The final execution of the steps in the scheduled migration window. Once complete, the customer is now live on the SaaS Service offering.



Table 1. Go Live Responsibilities

 Task IBM Client (or Designate) 

 Export data from SaaS Flex and transfer to MAS-SaaS X 
 Remediate technical changes in MAS through Maxadmin X 
 Remediate technical changes in MAS at OS Level X 
 Deploy Attachments X 
 Import Database X 
 Finalize any changes needed X 
 Finalize Integrations X 
 Test Changes X 
 Go Live X 







 Post Live MAS-SaaS Activities 

This is the support for customers after the go live. Any new issue is investigated and resolved and then the client moves to steady state.





 Roles and Responsibilities 

Both IBM and the client have critical roles in the successful transition to the Maximo Application Suite SaaS offering. These responsibilities are summarized in the attached spreadsheet below (MAS-SaaS Migration Swimlanes).
If you'd like, you can follow the instructions for [Planning for custom images](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images) to create your own custom image with additional software and use that to build the Spectrum Scale storage cluster through this offering. No hpcc-scale5151-rhel86 
 scale_storage_node_count Total number of storage cluster instances that you need to provision. A minimum of 3 nodes and a maximum of 18 nodes are supported if the storage_type selected is scratch. A minimum of 3 nodes and a maximum of 10 nodes are supported if the storage_type selected is persistent. No 3 
 scale_storage_node_instance_type Specify the virtual server instance storage profile type name to be used to create the Spectrum Scale storage nodes for the Spectrum Symphony cluster. For more information, see [Instance profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-profiles&interface=ui) No cx2d-8x16 
 spectrum_scale_enabled Setting this to 'true' enables Spectrum Scale integration with the cluster. Otherwise, Spectrum Scale integration is disabled (default). By entering 'true' for the property, you have also agreed to one of the two conditions: (1) You are using the software in production and confirm you have sufficient licenses to cover your use under the International Program License Agreement (IPLA). (2) You are evaluating the software and agree to abide by the International License Agreement for Evaluation of Programs (ILAE). Note: Failure to comply with licenses for production use of software is a violation of [IBM International Program License Agreement](https://www.ibm.com/software/passportadvantage/programlicense.html) No false 
 ssh_key_name Comma-separated list of names of the SSH key that is configured in your IBM Cloud account and is used to establish a connection to the Symphony management node. Ensure that the SSH key is present in the same resource group and region where the cluster is being provisioned.
Private and Public 
 How many VLANs do I need? Private = 3, Public = 1 
 How many IP addresses do I need? 8 - 16 for each VLAN 
 What router do the VLANs need to be behind? It doesn't matter that the VLANs are all in the same pod. 
 Which pod do the VLANs need to be in? They all go in the same pod in . 



After the VLANs are provisioned, make note of the VLAN numbers, subnet range, and gateway, and assign them to logical vSphere networks. You can use the worksheet in Appendix A: VLAN worksheet to record the VLAN and the associated information. For example:



Table 3. Primary VLAN sample

 VLAN Type VLAN Number IP Range Gateway Purpose 

 Primary Private 1101 10.X.Y.Z/28 10.X.Y.1 Management 
 Primary Private 1102 10.A.B.C/29 10.A.B.1 Storage 
 Primary Private 1103 10.Q.R.S/29 10.Q.R.1 Virtual machines 
 Primary Public 2101 75.S.T.U/29 75.S.T.1 Public access 



Note: Do not continue to the next step until the VLANs are provisioned.





 Step 2 Ordering portable private IP addresses 

In Step 2, a request is made to create portable private subnets for management VMs, VM kernel storage access, and VMs in the capacity cluster. You need to determine how many addresses you need for each VLAN subnet. In the representative environment, order the following addresses:



* Management VLAN - 1x8 addresses /29 – One address for vCenter Appliance; one address for DNS and Active Directory.
* Storage VLAN - 1x16 addresses /28 – Create two subnets on the same VLAN for storage and two VM kernel ports on each ESXi hosts by using different subnets to access the shared storage devices.
* VM VLAN - 1x32 addresses /27 – These addresses are used to assign IP addresses to VMs in the capacity cluster.
You agree that this Agreement, including the policies it refers to (i.e. our Dispute Resolution Policy, etc.) constitute the complete and only agreement between You and IBM Cloud regarding the services contemplated herein.





 Venue; Waiver of Trial by Jury 

This Agreement shall be deemed entered into in the state of Texas. Except for disputes concerning the user of a domain name registered with IBM Cloud, the laws and judicial decisions of Dallas County, Texas, shall be used to determine the validity, construction, interpretation and legal effect of this Agreement. You agree that any action relating to or arising out of this Agreement shall be brought in the courts of Dallas County, Texas. You agree to waive the right to trial by jury in any proceeding that takes place relating to or arising out of this Agreement.





 Notices 

You agree that, with the exception of notices concerning breach of this Agreement, all notices from IBM Cloud to You may be posted on our web site, or sent to the email address You have on file with IBM Cloud, and will be deemed delivered within three days after posting/sending. Notices concerning breach will be sent either to the email address You have on file with IBM Cloud or mailed first class postage to the postal address You have on file with IBM Cloud. In both cases, delivery shall be deemed to have been made five days after the date sent. Notices from You to IBM Cloud shall be made by email, sent to the address we provide on our web site.





 Provisions Specific to All Registrations 

You agree to be bound by the rules, policies, and agreements of each Registry from which You purchase a domain registration, which may include, but are not limited to, Top Level Domain Registries and Second Level Domain Registries.





 Provisions Specific to .COM, and .NET Registrations Indemnification 

You agree to indemnify, defend and hold harmless the .COM, .NET and .NAME Registry Operator, VeriSign, Inc., and its directors, officers, employees, agents, and affiliates from and against any and all claims, damages, liabilities, costs and expenses, including reasonable legal fees and expenses arising out of or relating to the Registered Name holder's domain name registration.





 Provisions Specific to .ORG Registrations Indemnification
Yes, you can add user tags and access management tags to your volumes. User tags are used by the backup service to automatically create backup snapshots of the volume. Access management tags help organize access to your Block Storage for VPC volumes. For more information, see [Tags for Block Storage for VPC volumes](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-about&interface=uistorage-about-tags).







 Performance questions 



 What is IOPS and how do it relate to my Block Storage for VPC volume performance? 

Input/output operations per second (IOPS) is used to measure the performance of your Block Storage for VPC volumes. A number of variables impact IOPS values, such as the balance of read/write operations, queue depth, and data block sizes. In general, the higher the IOPS of your Block Storage for VPC volumes, the better the performance. For more information about expected IOPS for Block Storage for VPC profiles, see [Profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profiles). For more information about how block size affects performance, see [Block storage capacity and performance](https://cloud.ibm.com/docs/vpc?topic=vpc-capacity-performancehow-block-size-affects-performance).





 Is the allocated IOPS enforced by instance or by volume? 

IOPS is enforced at the volume level.





 What are IOPS profiles and how do they affect volume performance? 

IOPS profiles define IOPS/GB performance for volumes of various capacities. You can select from three predefined [IOPS tiers](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilestiers) that offer reliable IOPS performance for your workload requirements. You can also define [custom IOPS](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilescustom) and specify a range of IOPS for a volume size that you choose.
You can use this option if you are concerned about a single-server outage that might affect all Power Systems Virtual Server instances. A placement group is automatically created. The instance name previously provided will be used as the group name and cannot be edited. <br>Numerical prefix : Select this option to add numbers before the name of the virtual server. If, for example, the first Power Systems Virtual Server name is Austin the next name for the virtual instance is 1Austin. <br>Numerical postfix : Select this option to add numbers after the name of the virtual server. If, for example, the first Power Systems Virtual Server name is Austin the next name for the virtual instance is Austin1. <br>VM pinning : Select this option to pin your virtual machine. You can choose either a soft or hard pinning policy. <br>[Learn more](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-power-iaas-faqspinning). <br>Note: When you create multiple instances of the virtual server, you must select On from the Shareable field for each data volume that you add. If you do not want the data volume to be shareable, you can add the data volume after you create the virtual server. For IBM i OS you cannot have shareable data volumes. 
 Machine type Specify the machine type. The machine type that you select determines the number of cores and memory that is available. For more information about hardware specifications, see [S922](https://www.ibm.com/downloads/cas/KQ4BOJ3N), and [E980 (Data centers other than Dallas and Washington)](http://www-01.ibm.com/support/docview.wss?uid=ssm1platformaix9080-M9S-vios-only). 
 Cores There is a core-to-vCPU ratio of 1:1. For shared processors, fractional cores round up to the nearest whole number. For example, 1.25 cores equals 2 vCPUs. 
 Memory Select the amount of memory for the Power Systems Virtual Server.
Table 1 shows examples of how block size and IOPS affect the throughput. Average IO size x IOPS = Throughput in MB/s.

 Block Size (KB) IOPS Throughput (MB/s) 

 4 1,000 4 
 8 1,000 8 
 16 1,000 16 
 32 500 16 
 64 250 16 
 128 128 16 
 512 32 16 
 1024 16 16 







 Authorized hosts 

Another factor to consider is the number of hosts that are using your volume. When only a single host that is accessing the volume, it can be difficult to realize the maximum IOPS available, especially at extreme IOPS counts (10,000s). If your workload requires high throughput, it would be best to configure at least a couple servers to access your volume to avoid a single-server bottleneck.





 Network connection 

The speed of your Ethernet connection must be faster than the expected maximum throughput from your volume. Generally, don't expect to saturate your Ethernet connection beyond 70% of the available bandwidth. For example, if you have 6,000 IOPS and are using a 16-KB block size, the volume can handle approximately 94-MBps throughput. If you have a 1-Gbps Ethernet connection to your volume, it becomes a bottleneck when your servers attempt to use the maximum available throughput. It's because 70 percent of the theoretical limit of a 1-Gbps Ethernet connection (125 MB per second) would allow for 88 MB per second only.

To achieve maximum IOPS, adequate network resources need to be in place. Other considerations include private network usage outside of storage and host side and application-specific tunings, and other settings).

Storage traffic is to be isolated from other traffic types, and not be directed through firewalls and routers. Keeping the storage traffic in a dedicated VLAN also helps preventing MTU mismatch when Jumbo frames are enabled. For more information, see [Enabling Jumbo Frames](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-jumboframes).

Storage traffic is included in the total network usage of Public Virtual Servers.