vania-janet/multiturn-rag-retrieval-data huggingface dataset:
The Compute profile family of dedicate hosts on Intel® x86-64 systems are deployed on either Intel®'s quad processor Xeon® Platinum 8260 Cascade Lake with 96 cores that are running at a base speed of 2.4 GHz and an all-core turbo frequency of 3.1 GHz or Intel®'s quad processor Xeon® Gold 6248 Cascade Lake with 80 cores that are running at a base speed of 2.5 GHz and an all-core turbo frequency of 3.1 GHz.

The following Compute profiles are available for dedicated hosts.

Intel x86-64



Table 3. Intel x86-64 Compute profile for dedicated hosts
Dedicated Host Compute profiles options for Intel x86-64 virtual server instances.

 Dedicated host profile vCPU Cores GiB RAM Instance storage 

 cx2-host-152x304 152 76 304 <br><br> * <br><br><br> 
 cx2d-host-152x304 152 76 304 5700 GB 



For supported instance profiles in the Compute family, see [compute profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-profilescompute). Instance profiles that are provisioned on a dedicated host in the Compute family must include a cx2 prefix in the instance profile name. Profiles with instance storage include d in the profile name, for example cx2d.

Dedicated hosts have a network performance cap of 80 Gbps. Instances provisioned on the host share bandwidth across the instances.





 Memory 

The Memory profile is best for memory intensive workloads, such as large caching workloads, intensive database applications, or in-memory analytics workloads. The Memory with instance storage profile is best for memory intensive workloads, such as large caching workloads, intensive database applications, or in-memory analytics workloads.

The Memory with instance storage profile provisions your host with the capability for hosting instances that include [instance storage](https://cloud.ibm.com/docs/vpc?topic=vpc-instance-storage).
Understanding High availability for App Configuration 

IBM App Configuration is a highly available, multi-tenant, regional service.



 Service High Availability (HA) 

An availability zone is a logically and physically isolated location within an IBM Cloud region where your data is processed and hosted.



* An availability zone has independent power, cooling, and network infrastructures that are isolated from other zones to strengthen fault tolerance by avoiding single points of failure between zones.
* An availability zone offers high bandwidth and low inter-zone latency within a region.



A region (location) is a geographically and physically separate group of one or more availability zones with independent electrical and network infrastructures that are isolated from other regions.



* Regions are designed to remove shared single points of failure with other regions and provide low inter-zone latency within the region.
* Each region has three different data centers (DC) for redundancy.
* In each supported region, traffic is load balanced across infrastructure in multiple availability zones, with no single point of failure.
* If all the data centers in a region fail, App Configuration becomes unavailable in that region.







 Availability zones for App Configuration 

The following table lists the high-availability (HA) status for the regions (locations) where the IBM Cloud App Configuration service is available:



Table 1. HA status for the regions

 Geography Region HA Status 

 Asia-Pacific Sydney (au-syd) MZR 
 Europe London (eu-gb) MZR 
 North America Dallas (us-south) MZR 
 North America Washington DC (us-east) MZR 



Where:



* A geography is a geographic area or larger political body that contains one or more regions.
* A region is a defined geographic territory.



* A region might be a specific postal code area, a town, a city, a state, a group of states, or even a group of countries.
* A region contains [multiple availability zones](https://www.ibm.com/cloud/data-centers/) to meet local access, low latency, and security requirements for the region.



* MZR means multi-zone region. [Learn more](https://cloud.ibm.com/docs/overview?topic=overview-locationsmzr-table).
Single data centers are not colocated with IBM Cloud services, such as IAM or Key Protect, and offer no resiliency in a site outage or destruction.

If a networking failure results in a partition where the data center is unable to access IAM, authentication and authorization information is read from a cache that might become stale. This cached data might result in a lack of enforcement of new or altered IAM policies for up to 24 hours.

Public

Private

Direct



Table 3. Single Data Center Endpoints

 Region Type Legacy Endpoint New Endpoint 

 Amsterdam, Netherlands Public s3.ams03.objectstorage.softlayer.net s3.ams03.cloud-object-storage.appdomain.cloud 
 Chennai, India Public s3.che01.objectstorage.softlayer.net s3.che01.cloud-object-storage.appdomain.cloud 
 Milan, Italy Public none s3.mil01.cloud-object-storage.appdomain.cloud 
 Montrèal, Canada Public s3.mon01.objectstorage.softlayer.net s3.mon01.cloud-object-storage.appdomain.cloud 
 Paris, France Public s3.par01.objectstorage.softlayer.net s3.par01.cloud-object-storage.appdomain.cloud 
 San Jose, US Public none s3.sjc04.cloud-object-storage.appdomain.cloud 
 São Paulo, Brazil Public s3.sao01.objectstorage.softlayer.net s3.sao01.cloud-object-storage.appdomain.cloud 
 Singapore Public none s3.sng01.cloud-object-storage.appdomain.cloud
For Cascade Lake servers, you can choose the following CPU models and a supported RAM size, which depends on the NSX networking solution.

NSX-T instances



Table 1. Options for Cascade Lake bare metal servers - NSX-T instances

 CPU model Cores GHz RAM 

 Dual Intel Xeon Silver 4210 processor 20 2.2 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB 
 Dual Intel Xeon Gold 5218 processor 32 2.3 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB 
 Dual Intel Xeon Gold 6248 processor 40 2.5 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB 
 Dual Intel Xeon Gold 6250 processor 16 3.9 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB 
 Dual Intel Xeon Platinum 8260 processor 48 2.4 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB 
 Quad Intel Xeon Gold 6248 processor 80 2.5 384 GB, 768 GB, 1.5 TB, 3 TB 
 Quad Intel Xeon Platinum 8260 processor 96 2.4 384 GB, 768 GB, 1.5 TB, 3 TB 







 SAP-certified Cascade Lake 

For SAP-certified Cascade Lake servers, you can select from the following configurations:



Table 2. Options for SAP-certified Cascade Lake - NetWeaver and HANA

 CPU model SAP certification Cores GHz RAM Storage type 

 Dual Intel Xeon Gold 5218 processor (Cascade Lake, BI.S4.NW192) NetWeaver 32 2.3 192 GB Up to 12 Drivers 
 Dual Intel Xeon Gold 5218 processor (Cascade Lake, BI.S4.NW384) NetWeaver 32 2.3 384 GB Up to 12 Drivers 
 Dual Intel Xeon Gold 6248 processor (Cascade Lake, BI.S4.NW768) NetWeaver 40 2.5 768 GB Up to 12 Drivers 
 Dual Intel Xeon Platinum 8260 processor (Cascade Lake, BI.S4.NW768_v2) Netweaver 48 2.4 768 GB Up to 12 Drivers
Downloading and installing the Data Crawler 

The Data Crawler is no longer supported or available for download beginning [17 April 2019](https://cloud.ibm.com/docs/discovery?topic=discovery-release-notes17apr19). This content is provided for existing installations only. See [Connecting to Data Sources](https://cloud.ibm.com/docs/discovery?topic=discovery-sources) for other available connectivity options.

The Data Crawler collects the raw data that is eventually used to form search results for Discovery. When crawling data repositories, the crawler downloads documents and metadata, starting from a user-specified seed URL. The crawler discovers documents in a hierarchy, or otherwise linked from the seed URL, and enqueues these for retrieval.



 Prerequisites 



* Java Runtime Environment version 8 or higher

Your JAVA_HOME environment variable must be set correctly, or not be set at all, to run the Crawler.
* Red Hat Enterprise Linux 6 or 7, or Ubuntu Linux 15 or 16. For optimal performance, the Data Crawler must run on its own instance of Linux, whether it is a virtual machine, a container, or hardware.
* Minimum 2 GB RAM on the Linux system







 Download and install the Data Crawler 



1. Open a browser and log into your [IBM Cloud® account](https://cloud.ibm.com/).
2. From your IBM Cloud dashboard, select the Discovery instance you previously created.
3. In the Automate the upload of content to the Discovery service section, click the appropriate link to download the Data Crawler for Linux in DEB, RPM, and ZIP formats.
4. Verify that you are running Java Runtime Environment version 8 or higher. Run the command java -version, and look for 1.8.
SA-15 (9) - Use of Live Data 



  Control requirements 

SA-15 (9) - 0
:   The organization approves, documents, and controls the use of live data in development and test environments for the information system, system component, or information system service.





  Additional IBM Cloud for Financial Services specifications 



*  Customer data must not be placed into non-production environments. Customer data must not be consumed or utilized for the purposes of testing services.







  Implementation guidance 

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



*  [Development processes and software integrity](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-development-processes)







  NIST supplemental guidance 

The use of live data in preproduction environments can result in significant risk to organizations. Organizations can minimize such risk by using test or dummy data during the development and testing of information systems, information system components, and information system services.
Data Overages The number of data overages incurred for the current month's billing cycle. 







 Gateway Info Panel 

By clicking the Settings button ![Setting Button](https://cloud.ibm.com/docs-content/v1/content/690bf9a59650e0582967be8899e39840589532f7/SecureGateway/images/settingIcon.png?raw=true) on any of the gateway tiles, you can see:



* The security token required to use the API or to connect a client, depending on whether the token is being enforced on client connections.
* The gateway ID required to use the API or to connect a client.
* The node your gateway has been created on. This is the server your client will connect to.
* When the gateway was created
* When the gateway was last modified
* A link to regenerate the certificate and key associated with the gateway. These files are only used with legacy destinations that do not contain their own certificate/key pair for mutual authentication on the client.



The following tasks can also be completed from the Gateway Info panel:



* Edit or view more information about your gateway and security token. A new panel is displayed when you select this option.
* Disable or enable the gateway.
* Delete the gateway.









 Dashboard for a particular gateway 

By clicking on one of the gateway tiles, the dashboard for that particular gateway is displayed. Similar to the main Secure Gateway dashboard, you can quickly see the following details:



* The inbound data flow across this gateway in the past 12 hours.
* The outbound data flow across this gateway in the past 12 hours.
* A graph displaying the past 12 hours of usage on a per destination basis.
* Your existing destinations, their current status.



![Dashboard for a particular gateway](https://cloud.ibm.com/docs-content/v1/content/690bf9a59650e0582967be8899e39840589532f7/SecureGateway/images/viewGateway.png?raw=true)



 Destination Info Panel 

By clicking the Settings button !
Data virtualization (federation) 

Db2 data virtualization (also known as federation) is supported by Db2 Warehouse on Cloud. Data virtualization gives you single-query access to all of your data that is on multiple distributed databases anywhere in your organization. You can access data that is on any of your Db2 or Informix data sources, both in the cloud and on premises.

This function is supported on all versions of Db2 Warehouse on Cloud.



 Use Cases 



 Consolidate data sources 

By federating your data sources that are located both in the cloud and on premises anywhere in your organization, your virtualized data appears to be retrieved from a single source. Data virtualization eliminates the burdensome and costly data migration process, giving you the ability to analyze all of your data efficiently and cost effectively.





 Attach to Db2 on Cloud 

Users of products in the Db2 family can federate data from Db2 on Cloud and Db2 Warehouse on Cloud databases. From a common interface to access the data, you can easily add, query, and analyze your data without complex ETL processes and without any additional code.





 Increase database capacity beyond fixed limits 

Federation gives you the ability to increase the capacity of an on-premises database by federating with a database on the cloud. Data virtualization in this case is a great option if your on-premises database is running out of storage. Increasing the capacity of a database with federation is useful for new development because developers don't need to change a database already in production. You can also federate between two Db2 Warehouse on Cloud databases to increase the database capacity beyond the current limits of the Flex plan.







 Getting started 

The following steps are an example of how you go about federating your disparate data sources to appear as if the data is retrieved from a single source. The following example illustrates the federation of two Db2 Warehouse on Cloud databases:



 On the Db2 Warehouse on Cloud target machine 

Host name: targetdotcom



1. Create a table testdata in schema admin2.
2. From the Db2 Warehouse on Cloud console, load the testdata table with data as user admin2 with password YYYY.







 On a Db2 Warehouse on Cloud machine being used as a federation source
lakehouse.engines.update An event is generated when you update an engine. 
 lakehouse.engines.delete An event is generated when you delete an engine. 
 lakehouse.engines.pause An event is generated when you pause an engine. 
 lakehouse.engines.resume An event is generated when you resume an engine. 







 Events for buckets 



Table 3. Lists of bucket events

 Action Description 

 lakehouse.buckets.create An event is generated when you create a bucket. 
 lakehouse.buckets.get An event is generated when you get buckets. 
 lakehouse.buckets.update An event is generated when you update a bucket. 
 lakehouse.buckets.delete An event is generated when you delete a bucket. 
 lakehouse.buckets.activate An event is generated when you activate a bucket. 







 Events for catalogs 



Table 1. Lists of catalog events

 Action Description 

 lakehouse.catalogs.create An event is generated when you create a catalog. 
 lakehouse.catalogs.get An event is generated when you get catalogs. 
 lakehouse.catalogs.update An event is generated when you update a catalog. 
 lakehouse.catalogs.delete An event is generated when you delete a catalog. 







 Events for databases 



Table 4. Lists of database events

 Action Description 

 lakehouse.databases.create An event is generated when you create a database. 
 lakehouse.databases.get An event is generated when you get databases. 
 lakehouse.databases.update An event is generated when you update a database. 
 lakehouse.databases.delete An event is generated when you delete a database. 







 Events for authentication 



Table 5. Lists of events for authentication

 Action Description 

 lakehouse.authtoken.create An event is generated when a user logs in. 
 lakehouse.authtoken.delete An event is generated when a user logs out. 







 Events for engine users 



Table 6. Lists of engine user events

 Action Description 

 lakehouse.engineusers.create An event is generated when you create an engine user. 
 lakehouse.engineusers.update An event is generated when you update an engine user.
You can find full information about the mapping between regions and data centers in [Region and data center locations for resource deployment](https://cloud.ibm.com/docs/overview?topic=overview-locations).



After you choose your region, click Create to create the logging instance, then configure it by clicking Configure the platform service logs.





 Log output examples 

The following output is an example of IBM Cloud Application Load Balancer for VPC datapath logging:

Sep 28 11:25:04 is-load-balancer crn:v1:bluemix:public:is:us-south:a/8c8a02225526799f56330a6701d939eb::load-balancer:r134-6ba32c0e-830c-483c-871a-0240c10662cf
{"PRIORITY":"info", "MSG_timestamp":"2020-09-28T03:25:03.136101+00:00", "SentByHost":"150.238.66.162", "MESSAGE":" Connect from 222.72.143.92:38605 to 10.240.128.5:62776 (r134-6ba32c0e-830c-483c-871a-0240c10662cf/HTTP)", "logSourceCRN":"crn:v1:bluemix:public:is:us-south:a/8c8a02225526799f56330a6701d939eb::load-balancer:r134-6ba32c0e-830c-483c-871a-0240c10662cf", "saveServiceCopy":false}

The logs contain the log header and the JSON string.

The log header is built with datetime (Sep 28 11:25:04), log source (is-load-balancer) and log source CRN (crn:v1:bluemix:public:is:us-south...).
Witness cluster (Multizone VMware instance only) 

New deployments of VMware Regulated Workloads multizone instances are no longer supported. You can still add or delete clusters, add or delete ESXi servers or NFS storage, and add or remove services for existing multizone instances.



 Cluster name 

The witness cluster name is set to mcv-xx-witness by default, where xx represents two randomly generated alphabetic characters. You can also specify a new witness cluster name, which must meet the following requirements.





 Witness cluster name requirements 



* Only lowercase alphabetic, numeric, and dash (-) characters are allowed.
* The witness cluster name must start with a lowercase alphabetic character.
* The witness cluster name must end with a lowercase alphabetic or numeric character.
* The maximum length of the witness cluster name is 10 characters.
* The witness cluster name must be unique within the regulated workload instance.







 CPU model and RAM 

You can choose the following CPU models and a supported RAM size:



Table 1. Options for Cascade Lake bare metal servers

 CPU model Cores GHz RAM 

 Dual Intel® Xeon® Silver 4210 (Cascade Lake) 20 2.2 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB 
 Dual Intel Xeon Gold 5218 (Cascade Lake) 32 2.3 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB 
 Dual Intel Xeon Gold 6248 (Cascade Lake) 40 2.5 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB 
 Dual Intel Xeon Gold 6250 (Cascade Lake) 16 3.9 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB 
 Dual Intel Xeon Platinum 8260 (Cascade Lake) 48 2.4 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB 
 Quad Intel Xeon Gold 6248 (Cascade Lake) 80 2.5 384 GB, 768 GB, 1.5 TB, 3 TB 
 Quad Intel Xeon Platinum 8260 (Cascade Lake) 96 2.4 384 GB, 768 GB, 1.5 TB, 3 TB 







 Number of bare metal servers
Replication across regions is not permitted.

See Table 1 for the complete list of data center availability and replication targets within each region.



Table 1 - This table shows the complete list of data centers with enhanced capabilities in each region. Every region is a separate column. Some cities, such as Dallas, San Jose, Washington DC, Amsterdam, Frankfurt, London, and Sydney have multiple data centers.

 US 1 US 2 Latin America Canada Europe Asia-Pacific Australia 

 <br><br> * DAL05<br> * SJC01<br> * WDC01<br><br><br> <br><br> * SJC03<br> * SJC04<br> * WDC04<br> * WDC06<br> * WDC07<br> * DAL09<br> * DAL10<br> * DAL12<br> * DAL13<br><br><br> <br><br> * SAO01<br> * SAO04<br> * SAO05<br><br><br> <br><br> * TOR01<br> * TOR04<br> * TOR05<br> * MON01<br><br><br> <br><br> * AMS03<br> * FRA02<br> * FRA04<br> * FRA05<br> * LON02<br> * LON04<br> * LON05<br> * LON06<br> * PAR01<br> * MAD04<br> * MAD05<br> * MIL01<br><br><br> <br><br> * TOK02<br> * TOK04<br> * TOK05<br> * OSA21<br> * OSA22<br> * OSA23<br> * SNG01<br> * CHE01<br><br><br> <br><br> * SYD01<br> * SYD04<br> * SYD05<br><br><br> 



Data centers in US 1 can replicate with only each other.
Replication across regions is not allowed.

See Table 1 for the complete list of data center availability and replication targets within each region.



Table 1 - This table shows the complete list of data centers with enhanced capabilities in each region. Every region is a separate column. Some cities, such as Dallas, San Jose, Washington DC, Amsterdam, Frankfurt, London, and Sydney have multiple data centers.

 US 1 US 2 Latin America Canada Europe Asia-Pacific Australia 

 <br><br> * DAL05<br> * SJC01<br> * WDC01<br><br><br> <br><br> * SJC03<br> * SJC04<br> * WDC04<br> * WDC06<br> * WDC07<br> * DAL09<br> * DAL10<br> * DAL12<br> * DAL13<br><br><br> <br><br> * SAO01<br> * SAO04<br> * SAO05<br><br><br> <br><br> * TOR01<br> * TOR04<br> * TOR05<br> * MON01<br><br><br> <br><br> * AMS03<br> * FRA02<br> * FRA04<br> * FRA05<br> * LON02<br> * LON04<br> * LON05<br> * LON06<br> * PAR01<br> * MIL01<br> * MAD04<br> * MAD05<br><br><br> <br><br> * TOK02<br> * TOK04<br> * TOK05<br> * OSA21<br> * OSA22<br> * OSA23<br> * SNG01<br> * CHE01<br><br><br> <br><br> * SYD01<br> * SYD04<br> * SYD05<br><br><br> 



Data centers in US 1 region can replicate with only each other.
Location Region Data center Subnet First IP 

 Chennai in-che che01 10.162.8.127/26 10.162.8.65 
 Chennai in-che che01 10.163.20.127/25 10.163.20.1 
 Chennai in-che che01 10.162.115.103/29 10.162.115.97 
 Chennai in-che che01 10.162.132.79/29 10.162.132.73 









 ca-tor List 



 Public Subnets 



Table 3. ca-tor Public Subnets

 Location Region Data center Subnet First IP 

 Toronto ca-tor tor01 158.85.91.111/28 158.85.91.97 
 Toronto ca-tor tor01 158.85.120.63/26 158.85.120.1 
 Toronto ca-tor tor01 169.55.136.127/25 169.55.136.1 
 Toronto ca-tor tor01 169.55.142.191/27 169.55.142.161 
 Toronto ca-tor tor01 158.85.95.183/29 158.85.95.177 
 Toronto ca-tor tor01 169.55.130.215/29 169.55.130.209 
 Toronto ca-tor tor04 163.74.68.95/28 163.74.68.81 
 Toronto ca-tor tor04 163.74.69.159/27 163.74.69.129 
 Toronto ca-tor tor04 163.74.72.127/26 163.74.72.65 
 Toronto ca-tor tor04 163.74.73.255/25 163.74.73.129 
 Toronto ca-tor tor04 163.74.68.55/29 163.74.68.49 
 Toronto ca-tor tor04 163.74.68.63/29 163.74.68.57 
 Toronto ca-tor tor05 163.75.67.111/28 163.75.67.97 
 Toronto ca-tor tor05 163.75.68.95/27 163.75.68.65 
 Toronto ca-tor tor05 163.75.75.63/26 163.75.75.1