vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Cascade Lake bare metal servers are available only for VMware vSphere Enterprise Plus 6.7u3 instances.



Table 2. Options for Cascade Lake bare metal servers

 CPU model options Cores GHz RAM options 

 Dual Intel Xeon Silver 4210 processor 20 2.2 64 GB, 96 GB, 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB 
 Dual Intel Xeon Gold 5218 processor 32 2.3 64 GB, 96 GB, 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB 
 Dual Intel Xeon Gold 6248 processor 40 2.5 64 GB, 96 GB, 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB 
 Dual Intel Xeon Gold 6250 processor 16 3.9 64 GB, 96 GB, 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB 
 Dual Intel Xeon Platinum 8260 processor 48 2.4 64 GB, 96 GB, 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 



The Quad Intel Xeon Gold 6248 processor is available if you add new clusters or new ESXi servers for existing hybridity instances.





 Number of bare metal servers 

You can order 4-59 servers. All servers have the same configuration.







 vSAN storage settings 

VMware vSAN™ 6.6 is included with your vCenter Server with Hybridity Bundle instance order. Specify the following vSAN options:



* Size for vSAN capacity disks - Select an option for the capacity disks that you need.
* Number of vSAN capacity disks - Specify the number of capacity disks that you want to add.
* If you want to add more capacity disks, select the High performance with Intel Optane checkbox. This option provides two extra capacity disk bays that are useful for workloads that require less latency and higher IOPS throughput.

The High performance with Intel Optane option is available only for Skylake and Cascade Lake CPU models.
To add custom data sets, use the following steps:



1. Click the menu icon ![hamburger icon](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/ContinuousDelivery/images/icon_hamburger.svg), and select DevOps.
2. On the Toolchains page, select your toolchain.
3. From your toolchain's Overview page, on the IBM Cloud tools card, click DevOps Insights.
4. Click Quality Dashboard.
5. Click the Overflow icon ![ellipsis icon](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/ContinuousDelivery/images/overflow-icon-2.svg) > Configure data set.
6. Click Add Quality Data Set.
7. Select Custom Quality Data Sets.
8. Complete all required fields, and click Submit



If a custom data set is deleted, any test results for that custom data set are deleted. For more information about deleting data sets, see [Deleting your DevOps Insights data](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-deleting_data).
For more information, see [Encrypting data source information](https://cloud.ibm.com/docs/services/cognos-dashboard-embedded?topic=cognos-dashboard-embedded-encryptingdatasourceinformationencryptingdatasourceinformation).

When your DDE application initially shows, a + icon is availble to add a data source. You are advised to listen to the event (user clicks + icon) by using the following code:

dashboardAPI.on(‘addSource:clicked’, cb)



For more information about the on method, see "

[https://dde.us-south.containers.mybluemix.net/daas/jsdoc/cognos/api/DashboardApi.html#on](https://dde.us-south.containers.mybluemix.net/daas/jsdoc/cognos/api/DashboardApi.htmlon)".

You then can add a data source to a dashboard in Cognos Dashboard Embedded, by calling the addSources() method.





 JDBC data sources 

You can specify a database connection, for the following supported JDBC connections:



* Db2
* PostgreSQL
* Oracle
* MS SQLServer



![JDBCdatasources](https://cloud.ibm.com/docs-content/v1/content/2781097afe16f2d329d7a606ddd260fb1a3e355c/services/cognos-dashboard-embedded/jdbc.jpg)



 Sample JDBC source specification: 

{
"xsd": "https://ibm.com/daas/module/1.0/module.xsd",
"source": {
"id": "StringID",
"jdbc": {
"jdbcUrl": "jdbc:sqlserver://vottdts16:1433;DATABASE=AdventureWorks",
cx2-32x64 IBM Cloud Virtual Server -- 32 64 35,800 Intel Cascade Lake SP 2.00 -- -- VPC 
 cx2-48x96 IBM Cloud Virtual Server -- 48 96 53,700 Intel Cascade Lake SP 2.00 -- -- VPC 
 cx2-64x128 IBM Cloud Virtual Server -- 64 128 71,600 Intel Cascade Lake SP 2.00 -- -- VPC 
 cx2-96x192 IBM Cloud Virtual Server -- 96 192 107,400 Intel Cascade Lake SP 2.00 -- -- VPC 
 cx2-128x256 IBM Cloud Virtual Server -- 128 256 143,200 Intel Cascade Lake SP 2.00 -- -- VPC 
 bx2-2x8 IBM Cloud Virtual Server -- 2 8 2,306 Intel Cascade Lake SP 4.00 -- -- VPC 
 bx2-4x16 IBM Cloud Virtual Server -- 4 16 4,613 Intel Cascade Lake SP 4.00 -- -- VPC 
 bx2-8x32 IBM Cloud Virtual Server -- 8 32 9,225 Intel Cascade Lake SP 4.00 -- -- VPC 
 bx2-16x64 IBM Cloud Virtual Server -- 16 64 18,450 Intel Cascade Lake SP 4.00 -- -- VPC 
 bx2-32x128 IBM Cloud Virtual Server -- 32 28 36,900 Intel Cascade Lake SP 4.00 -- -- VPC 
 bx2-48x192 IBM Cloud Virtual Server -- 48 192 55,350 Intel Cascade Lake SP 4.00 -- -- VPC 
 bx2-64x256 IBM Cloud Virtual Server -- 64 256 81,685 Intel Cascade Lake SP 4.00 -- -- VPC 
 bx2-96x384 IBM Cloud Virtual Server -- 96 384 122,528 Intel Cascade Lake SP 4.00 -- -- VPC 
 bx2-128x512 IBM Cloud Virtual Server -- 128 512 163,370 Intel Cascade Lake SP 4.00 -- -- VPC 
 mx2-2x16 IBM Cloud Virtual Server -- 2 16 2,571 Intel Cascade Lake SP 8.00 -- -- VPC
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) 
 watsonx.data ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) 







 Infrastructure 

Infrastructure services are available to be deployed in data centers. Each column header that ends with a number represents a data center or multizone region (MZR). Columns marked (MZR) represent a location where resources are automatically deployed and managed across several data centers.



 Americas 

The following infrastructure resources are available in North and South America. Match the resource row with the column representing the data center or multizone region. A check mark indicates the resource is available in that location. The Dallas (MZR), Washington DC (MZR), and Sao Paulo (MZR) columns represent multizone regions where deployment is managed automatically across several data centers.

Canada

United States

Brazil



Table 4. Americas infrastructure availability - Canada
Use the buttons for the countries to change the context of the table. This table has row and column headers. The row headers identify the service. The column headers identify where that service is located. To understand where a service is located in the table, navigate to the row, and find the for the location you are interested in.

 Service Montreal 01 Toronto 01 

 Bare Metal Servers for Classic !
Viewing the virtual data center summary 

You can view a summary of all the IBM Cloud® for VMware Solutions Shared virtual data centers that are provisioned for the user account.

Optionally, validate that you are in the correct account for your instance. From the console banner, click the Avatar icon ![Avatar icon](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/i-avatar-icon.svg), and then click the Account field to select the user account where you want to view virtual data centers.



 Procedure to view the virtual data center summary 



1. From the IBM Cloud for VMware Solutions console, click Resources > VMware Shared from the left navigation pane.
2. In the VMware Shared table, view the list of data center sites and the virtual data centers that are provisioned for each site.





Table 1. Data center site details

 Item Description 

 Site The name of the site where the instance is hosted. 
 Region The region where the instance is hosted. 
 Creation time The date and time when the instance was created. 
 Instances The number of virtual data center instances provisioned for the site. 



Expand the instance site to view the summary of each virtual data center that is provisioned for the user account.



Table 2. Virtual data center details by site

 Item Description 

 Name The name of the virtual data center. 
 Type The pricing plan for the virtual data center: On-demand or Reserved. 
 Location The IBM Cloud data center where the virtual data center is hosted. 
 Creation time The date and time when the virtual data center was created. 
 Status The status of the virtual data center. 



The virtual data center can have different statuses.



Table 3. Status descriptions for virtual data centers

 Status Description 

 Creating The virtual data center is being created. 
 Available The virtual data center is ready to use. 
 Modifying The virtual data center is being modified. 
 Deleting The virtual data center is being deleted. 







 Related links
mx2-16x128 IBM Cloud Virtual Server -- 16 128 20,565 Intel Cascade Lake SP 8.00 TDI OLTP and SAP Business One for HANA VPC 
 mx2-32x256 IBM Cloud Virtual Server -- 32 256 41,130 Intel Cascade Lake SP 8.00 TDI OLTP and SAP Business One for HANA VPC 
 mx2-48x384 IBM Cloud Virtual Server -- 48 384 56,970 Intel Cascade Lake SP 8.00 TDI OLTP and SAP Business One for HANA VPC 
 vx2d-16x224 IBM Cloud Virtual Server -- 16 224 17,046 Intel Cascade Lake SP 14.00 TDI OLTP VPC 
 vx2d-44x616 IBM Cloud Virtual Server -- 44 616 46,875 Intel Cascade Lake SP 14.00 TDI OLAP/OLTP VPC 
 vx2d-88x1232 IBM Cloud Virtual Server -- 88 1,232 93,750 Intel Cascade Lake SP 14.00 TDI OLAP/OLTP VPC 
 vx2d-144x2016 IBM Cloud Virtual Server -- 144 2,016 153,410 Intel Cascade Lake SP 14.00 TDI OLAP/OLTP VPC 
 vx2d-176x2464 IBM Cloud Virtual Server -- 176 2,464 187,500 Intel Cascade Lake SP 14.00 TDI OLAP/OLTP VPC 
 ux2d-8x224 IBM Cloud Virtual Server -- 8 224 8,623 Intel Cascade Lake SP 28.00 TDI OLTP VPC 
 ux2d-16x448 IBM Cloud Virtual Server -- 16 448 17,246 Intel Cascade Lake SP 28.00 TDI OLTP VPC 
 ux2d-36x1008 IBM Cloud Virtual Server -- 36 1,008 38,803 Intel Cascade Lake SP 28.00 TDI OLTP VPC 
 ux2d-48x1344 IBM Cloud Virtual Server -- 48 1,344 51,737 Intel Cascade Lake SP 28.00 TDI OLTP VPC 
 ux2d-72x2016 IBM Cloud Virtual Server -- 72 2,016 77,606 Intel Cascade Lake SP 28.00 TDI OLTP VPC
If you have an account with IBM Cloud, your personal data is held by IBM Cloud. The IBM Data Processing Addendum (Addendum) applies to the processing of client's personal data by IBM on behalf of client in order to provide IBM standard services.
[IBM DPA](https://www.ibm.com/support/customer/zz/en/dpa.html)

Databases for etcd processes limited client Personal Information (PI) in the course of running the service and optimizing the user experience.

Databases for etcd provides a [data sheet Addendum (DSA)](https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=5EE00B106DCB11E8A0B560E89C071ECC) with its policies as a Data processor regarding content and data protection.





 HIPAA 

Databases for etcd meets the required IBM controls that are commensurate with the Health Insurance Portability and Accountability Act of 1996 (HIPAA) Security and Privacy Rule requirements. These requirements include the appropriate administrative, physical, and technical safeguards required of Business Associates in 45 CFR Part 160 and Subparts A and C of Part 164. HIPAA must be requested at the time of provisioning and requires a representative to sign a Business Associate Addendum (BAA) agreement with IBM.





 PCI DSS 

Databases for etcd are compliant with the Payment Card Industry Data Security Standard (PCI DSS). IBM Cloud completes annual PCI DSS assessments by using an approved Qualified Security Assessor (QSA), and the resulting Attestations of Compliance (AOCs) and Service Responsibility Matrix (SRM) guides are available upon customer request. Auditors reviewed Databases for etcd for compliance under PCI DSS version 3.2.1 at Service Provider Level 1.

Customers are responsible for the storing, processing, and transmission of their cardholder data, and can create cardholder data environments (CDEs) that can store, transmit, or process cardholder data by using Databases for etcd. Customers can request and use the IBM Cloud AOCs and SRM guides when they seek their own PCI DSS certifications.
For more information, see the [Administration Guide for SAP Data Hub](https://help.sap.com/doc/70ce58a2ed23404fac27ae36c8f76900/2.7.latest/en-US/loio70ce58a2ed23404fac27ae36c8f76900.pdf).

For productive setups, we recommend preparing the required SSL certificates using the preferred tools. For non-productive setups, note that the SAP Data Hub installer can generate self-signed certificates.





 Red Hat OpenShift Cluster Storage 

SAP Data Hub requires access to persistent storage that is attached to the OpenShift cluster. For importing, exporting, and checkpointing SAP Vora database tables, SAP Data Hub requires access to a persistent shared file system or object store. In the IBM Cloud environment you will use IBM Cloud Object Storage,
EDM-1 - Quality Assurance 



  Control requirements 

EDM-1 - 0
:   Maintain customer data per agreed upon data quality standards with the customer and mitigate any breach of agreed upon standards with the customer data management team. If a data quality breach is a recurring event, than the issue will be added to the organization's Plan of Action and Milestones (POA&M) document for remediation.





  Additional IBM Cloud for Financial Services specifications 



*  This control is required for ISVs.
Advanced administration with IBM Data Server Manager 

Every IBM® Db2® on Cloud instance comes with a built-in console. This console provides the ability to load data into your Db2 on Cloud instance, run SQL, and monitor core metrics for your instance, including resource usage, responsiveness, and throughput. If you need more advanced capabilities, including monitoring multiple data warehouses at once, then we suggest connecting your Db2 on Cloud instance to [IBM Db2 Data Management Console](https://www.ibm.com/us-en/marketplace/data-server-manager).

By connecting Db2 on Cloud to Data Server Manager, you can access advanced diagnostic real time and historical monitoring, statement tracking and optimization, application locking details, storage, memory, and over 20 other KPIs for your IBM® Db2® Warehouse on Cloud instance.

With Data Server Manager, numerous alerts for performance optimization and availability are also available for around-the-clock automated monitoring of your Db2 on Cloud instance.
MEX01 data center no longer available
: (Updated on 14 November 2022) The Mexico 01 IBM Cloud data center is closing on 31 January 2023. This data center is no longer available for deployments.

VMware vSphere 7.0u2 - deprecated
: (Updated on 14 November 2022) The vSphere 7.0u2 option is no longer available for adding hosts to vCenter Server instances and scaling existing vSphere clusters. For existing instances with vSphere 7.0u2, you can add only ESXi servers with vSphere 7.0u3.

Dark mode temporarily unavailable
: Starting with 14 November 2022, the UI Dark mode is temporarily unavailable. Until it becomes enabled again, use Light mode.

Hostname prefix updates
: You can now customize the hostnames prefix individually when you order VMware vCenter Server instances, order new VMware vSphere clusters, and add hosts and clusters to existing instances.

Updates to VMware vCenter Server instances and VMware vSphere clusters
: The following upgrades are applied to newly deployed instances, clusters, and hosts.



* VMware vSphere ESXi 7.0 Update 3f (build 20036589)
* VMware vSphere ESXi 6.7 P08 (build 19997733)



Considerations for selecting a new NSX Data Center SP edition
: Beginning with the V5.0 release, if you have a BYOL for VMware NSX-T that is not a Data Center SP license, you can now order NSX Data Center SP licenses to replace your licenses. You are responsible to select the appropriate NSX Data Center SP license edition based on your needs.

Also, beginning with this release, if you have a BYOL Data Center SP edition license, you can start renting NSX Data Center SP edition licenses from IBM. If you already rent an NSX Data Center SP edition license from IBM, you can upgrade and downgrade. If you have VMware HCX and an NSX Data Center Enterprise Plus license, you cannot downgrade your license. If you uninstall HCX, you can then downgrade your license.

Add-on services upgrades
Enter weatherDS in the Name text field. Use any alphanumeric characters, dashes, and underscores in a data source name.
6. Click New.
7. By default, the Connector setting shows In-memory db and the other settings are blank. Keep the default settings for now, and API Designer automatically saves the new data source. The In-memory data source is built into LoopBack and is suitable only for development and initial testing. When you are ready to connect your models to a real data source such as a database server:



* Change the Connector setting.
* Install the data source connector as explained in the IBM Knowledge Center topic, [Installing LoopBack connectors](https://www.ibm.com/support/knowledgecenter/SSMNED_5.0.0/com.ibm.apic.toolkit.doc/tapim-connector-install.htmltask_i2p_dnw_vv).
* Enter the connector settings (host name, port, database name, user name, password) as appropriate for your Connector type, and click ![Save icon](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/save-icon.png).



API Designer automatically tests the connection to the data source. A successful test displays the message Success - Data source connection test succeeded.
8. Click ![Test Connection icon](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/db-test-icon.png) to test the data source connection. The message "Data source connection test succeeded" is displayed.
9. Click All Data Sources. The data source will appear in the list of data sources, and the editor updates the server/datasources.json file with settings for the new data source.







 Add a model
bx2-96x384 IBM Cloud Virtual Server -- 96 384 122,528 Intel Cascade Lake SP 4.00 -- -- VPC 
 bx2-128x512 IBM Cloud Virtual Server -- 128 512 163,370 Intel Cascade Lake SP 4.00 -- -- VPC 
 mx2-2x16 IBM Cloud Virtual Server -- 2 16 2,571 Intel Cascade Lake SP 8.00 -- -- VPC 
 mx2-4x32 IBM Cloud Virtual Server -- 4 32 5,141 Intel Cascade Lake SP 8.00 -- -- VPC 
 mx2-64x512 IBM Cloud Virtual Server -- 64 512 81,015 Intel Cascade Lake SP 8.00 -- -- VPC 
 mx2-96x768 IBM Cloud Virtual Server -- 96 768 121,523 Intel Cascade Lake SP 8.00 -- -- VPC 
 mx2-128x1024 IBM Cloud Virtual Server -- 128 1,024 162,030 Intel Cascade Lake SP 8.00 -- -- VPC 
 vx2d-2x28 IBM Cloud Virtual Server -- 2 28 2,131 Intel Cascade Lake SP 14.00 -- -- VPC 
 vx2d-4x56 IBM Cloud Virtual Server -- 4 56 4,262 Intel Cascade Lake SP 14.00 -- -- VPC 
 vx2d-8x112 IBM Cloud Virtual Server -- 8 112 8,523 Intel Cascade Lake SP 14.00 -- -- VPC 
 ux2d-2x56 IBM Cloud Virtual Server -- 2 56 2,156 Intel Cascade Lake SP 28.00 -- -- VPC 
 ux2d-4x112 IBM Cloud Virtual Server -- 4 112 4,312 Intel Cascade Lake SP 28.00 -- -- VPC 
 BI.S3.NW192 (VMware) IBM Cloud for VMware 36 72 192 70,965 Intel Skylake SP 2.67 -- -- Classic 
 BI.S3.NW384 (VMware) IBM Cloud for VMware 36 72 384 71,487 Intel Skylake SP 5.33 -- -- Classic
* Click Next, and then click Create. The Schematics workspace is created with the name that you specified.



5. Go to Schematics Workspace Settings, and in the Variable section, click "burger icons" to update the following parameters:



* Update the ssh_key_name with your IBM Cloud SSH key name, such as "openshift-ssh-key", that is created in a specific region in IBM Cloud.
* Update the api_key value with the API key value. Mark it as sensitive to hide the API key in the IBM Cloud console.
* Update the region value where the cluster is deployed.
* Update the cluster_prefix value to the specific cluster prefix for your Red Hat OpenShift cluster.
* Update the worker_nodes_per_zone value according to your requirement.









 Next steps 

After you've successfully created a workspace, you can begin [Generating a plan](https://cloud.ibm.com/docs/hpc-openshift?topic=hpc-openshift-generate-plan&interface=ui) to validate all of the configuration properties.





 Before you begin 

Before you get started, make sure that you've completed the prerequisites found in [Setting up the IBM Cloud Schematics CLI](https://cloud.ibm.com/docs/hpc-openshift?topic=hpc-openshift-setting-up-cli).





 Creating a workspace using the CLI 

The first step when using Schematics is to create a workspace with the specific configuration parameters defined in the corresponding Terraform source code.

Use the following CLI command to create a workspace with your config.json file. Make sure that the config.json file exists in the directory where you run the command.

ibmcloud schematics workspace new -f hpc_workspace_config.json --github-token GITHUB_TOKEN

The --github-token parameter is optional and only needed if you are using a private GitHub repository.
SQL Database for Cloud data 

This tutorial may incur costs. Use the [Cost Estimator](https://cloud.ibm.com/estimator/review) to generate a cost estimate based on your projected usage.

This tutorial shows how to provision a SQL (relational) database service. As administrator, you create a table and load a large data set (city information) into the database. Then, you deploy a web app "worldcities" to [Code Engine](https://cloud.ibm.com/codeengine/). The app allows regular users to look up records from the cloud database. The app is written in Python using the [Flask framework](https://flask.palletsprojects.com).

Zoom

![Architecture diagram](https://cloud.ibm.com/docs-content/v1/content/f84e2238288b7f0355715a4c355609ce7ac48fb0/solution-tutorials/images/solution5/cloud-sql-database.svg)

Figure 1. Architecture diagram of the tutorial



 Objectives 



* Provision a SQL database
* Create the database schema (table) and load data
* Deploy a pre-built containerized app to Code Engine
* Connect the app and database service (share credentials)
* Monitor, Secure, Backup & Recovery of cloud databases







 Before you begin 

This tutorial requires:



* IBM Cloud CLI with the Code Engine plugin,
* git to clone the source code repository.



To avoid the installation of these tools you can use the [Cloud Shell](https://cloud.ibm.com/shell) from the IBM Cloud console.

You will find instructions to download and install these tools for your operating environment in the [Getting started with tutorials](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-tutorials) guide.



1. Clone the [Github repository for this tutorial](https://github.com/IBM-Cloud/cloud-sql-database) and change into its directory.