vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* Edge/DLR/VXLANs in combination with BGP metric-based routing to facilitate an active-active site design with automated failover.
* Each site has the concept of their own set of Edges, DLRs, and VXLANs.
* Under normal circumstances, any VMs connected to DLR-A, for example VM-A, are in IBM Cloud availability zone #1 and traffic is both ingress and egress locally.
* During a vMotion activity for VM-A, traffic still ingresses and egresses through the IBM Cloud availability zone #1.
* During a site or edge failure, traffic routes out of the remaining available site.









 Related links 



* [vCenter Server BOM](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_bom)
* [Planning vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_planning)
* [Ordering vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_orderinginstance-req)
* [Attached storage for vCenter Server](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-storage-benefitsstorage-benefits)
* [Expanding File Share capacity](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-expandCapacityexpandCapacity)
[Architecture](https://cloud.ibm.com/docs-content/v1/content/f84e2238288b7f0355715a4c355609ce7ac48fb0/solution-tutorials/images/solution66-vmware-as-a-service/vmwaas-example-diagrams-tf-vmwaas-basic.svg)

Figure 1. Architecture diagram of the tutorial



1. Use IBM Cloud Console to create a virtual data center in your single tenant instance. Your instance may have one or more virtual data centers, so you can have a dedicated virtual data center for testing purposes. This example virtual data center uses only a 2 IOPS/GB storage pool.
2. When a virtual data center is created, an edge gateway and external networks are created automatically. External network provides you Internet access and an IP address block of /29 with 6 usable public IP addresses is provided.
3. Terraform templates are used to create virtual data center networks, virtual machines as well as firewall and network address translation rules. The creation is fully controlled though variables. Terraform authenticates to the VMware Cloud Director API with a user name and password. Access tokens will be supported in the near future.
4. Three virtual data center networks are created: two routed (application-network-1 and db-network-1) and one isolated (isolated-network-1). Routed virtual data center networks are attached to the edge gateway while isolated virtual data center network is a standalone network. You can create more networks based on your needs.
5. A jump server (jump-server-1) is created with the Windows 2022 Operating System. The server is attached to the application-network-1. You can access the virtual machine though the VM console, or using RDP though the DNAT rule created on the Edge Gateway.
6. One example virtual machine (application-server-1) is created on the application-network-1. The application-server-1 has an additional disk e.g. for logging. You can create more VMs or disks based on your needs.
7.
DNS concepts 

This document contains some concepts and definitions related to the internet's domain name system (DNS) and how it affects your IBM Cloud® Internet Services (CIS) deployment.

The Domain Name System (DNS) underpins the web we use every day. It works transparently in the background, converting human-readable website names into computer-readable, numerical IP addresses that follow the [internet's RFC 1918 guidelines for IPv4 and RFC 4193 for IPv6](https://en.wikipedia.org/wiki/Private_network). In short, DNS servers match domain names, such as ibm.com, to their associated IP addresses, which most people do not need to know.

The DNS system looks up this IP address and host name information on a network of linked DNS servers across the internet, similarly to how people might look for someplace using a phone book or a map.



 Name servers 

A name server implements services that provide responses to queries against a directory service. It translates meaningful, text-based web or host identifiers into IP addresses.

Name server delegation takes place when a name server for a domain receives a request for a subdomain's records and responds with the name server's reference to the delegate server. This capability allows you to decentralize the management of a large domain (such as ibm.com).

A custom domain name server allows you to utilize the DNS provider's servers with the customized reference name of your own domain. For example, you can define your name server to be ns1.cloud.ibm.com instead of ns1.acme.com.





 Secure DNS 

DNSSec is a technology to digitally 'sign' DNS data so you can be assured it is valid. To eliminate vulnerability from the internet, DNSSec must be deployed at each step in the lookup, from root zone to final domain name (for example, www.icann.org).





 Root record CNAME flattening 

IBM CIS supports a feature called "CNAME Flattening." Using this method, root records can overcome the IETF RFC restriction that if a root record is a CNAME, it cannot have any other records for that domain.
BI.S4.H4.3000 IBM Cloud Bare Metal (Local SSD) <br><br> * [OLAP Record](https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN//solutions?filters=iaas&id=s:2212)<br> * [OLTP Record](https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN//solutions?filters=iaas&id=s:2248)<br><br><br> 
 BI.S4.H4.6000 IBM Cloud Bare Metal (Local SSD) <br><br> * [OLTP Record](https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN//solutions?filters=iaas&id=s:2247)<br> * [OLAP Scale-Out Record](https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN//solutions?filters=iaas&id=s:2213)<br><br><br> 
 BI.S4.H8.6000 IBM Cloud Bare Metal (Local SSD) <br><br> * [OLTP Record](https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN//solutions?filters=iaas&id=s:2303)<br> * [OLAP Scale-Out Record](https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN//solutions?filters=iaas&id=s:2305)<br><br><br>
_reserved_ips](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/is_subnet_reserved_ips)<br> * [ibm_is_subnets](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/is_subnets)<br> * [ibm_is_virtual_endpoint_gateway](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/is_virtual_endpoint_gateway)<br> * [ibm_is_virtual_endpoint_gateway_ips](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/is_virtual_endpoint_gateway_ips)<br> * [ibm_is_virtual_endpoint_gateways](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/is_virtual_endpoint_gateways)<br> * [ibm_is_volume](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/is_volume)<br> * [ibm_is_volume_profile]
However, if you are interested in quickly finding the information related specifically to one of the IaaS offerings, then you may consider using the Fast Path Site Maps for [Intel Bare Metal](https://cloud.ibm.com/docs/sap?topic=sap-fast-path-site-map-intel-bm), [Intel Virtual Servers](https://cloud.ibm.com/docs/sap?topic=sap-fast-path-site-map-intel-vs-gen2), [IBM Power Virtual Servers](https://cloud.ibm.com/docs/sap?topic=sap-fast-path-site-map-power-vs) and [VMware SDDC](https://cloud.ibm.com/docs/sap?topic=sap-fast-path-site-map-vmware-sddc).



 Certifications summary 



* SAP S/4HANA (AnyPremise edition), which uses SAP HANA scale-up
* SAP BW/4HANA, which uses SAP HANA scale-up
* SAP BW/4HANA, which uses SAP HANA scale-out



For more details on SAP S/4HANA scale-out with IBM Cloud, please read [SAP S/4HANA additional design considerations](https://cloud.ibm.com/docs/sap?topic=sap-s4hana) which describes while this is possible, IBM-SAP prefer to discuss first to understand the business requirements. This is to avoid transactional performance issues which may occur with SAP S/4HANA scale-out.





 Benchmarks summary 



* SAP S/4HANA (AnyPremise edition), which uses SAP HANA scale-up (world record, as of writing - 2020-07-01)
* SAP BW/4HANA, which uses SAP HANA scale-up (world record, as of writing - 2020-07-01)
* SAP BW/4HANA, which uses SAP HANA scale-out









 SAP's Platform-as-a-Service (PaaS) offerings 

IBM Cloud also enables the use of cloud-native SAP technologies. IBM-SAP work on multiple open source projects together and both companies use similar technology underpinnings.
The sum of the size of these objects is the maximum estimate of data that is scanned that you would be charged for. But as Data Engine accesses only one field, and data is stored as Parquet, it is much less. Calculating the precise price of the query is not possible in advance because much of it depends on the data itself. Parquet, for example, stores compressed columns, so if the column can be compressed effectively, even less data needs to be read. You also find some further details in the blog post [Data Engine releases serverless transformation and partitioning of data in open formats](https://www.ibm.com/cloud/blog/announcements/sql-query-releases-serverless-transformation-and-partitioning-of-data-in-open-formats) about Data Engine ETL capabilities and how they affect scanned data.







 Timestamps 

Values of the timestamp data type are created with Coordinated Universal Time (UTC) zone by default. So, for instance, the expressions timestamp('2009-07-30 04:17:52'), to_timestamp('2016-12-31', 'yyyy-MM-dd'), or current_timestamp all results in a Coordinated Universal Time timestamp value and the input string expressions are assumed to be in Coordinated Universal Time.

If you want to create a Coordinated Universal Time timestamp from a string expression that represents a different time zone, use [to_utc_timestamp](https://cloud.ibm.com/docs/sql-query?topic=sql-query-sqlfunctionsto_utc_timestamp), as in to_utc_timestamp('2016-08-31', 'Asia/Seoul').
Some storage solutions, such as file and block storage, are data center-specific and can't be shared across zones in a multizone cluster setup.

If you want to make your data accessible across zones or regions, make sure to consult your legal department to verify that your data can be stored in multiple zones or a different country.

Understand other storage characteristics that impact your choice.
: Consistency: The guarantee that a read operation returns the latest version of a file. Storage solutions can provide strong consistency when you are guaranteed to always receive the latest version of a file, or eventual consistency when the read operation might not return the latest version. You often find eventual consistency in geographically distributed systems where a write operation first must be replicated across all instances.
: Performance: The time that it takes to complete a read or write operation.
: Durability: The guarantee that a write operation that is committed to your storage survives permanently and does not get corrupted or lost, even if gigabytes or terabytes of data are written to your storage at the same time.
: Resiliency: The ability to recover from an outage and continue operations, even if a hardware or software component failed. For example, your physical storage experiences a power outage, a network outage, or is destroyed during a natural disaster.
: Availability: The ability to provide access to your data, even if a data center or a region is unavailable. Availability for your data is usually achieved by adding redundancy and setting up failover mechanisms.
: Scalability: The ability to extend capacity and customize performance based on your needs.
: Encryption: The masking of data to prevent visibility when data is accessed by an unauthorized user.



 Non-persistent storage 

Virtual Private Cloud

Classic infrastructure

Satellite

You can use non-persistent storage options if your data is not required to be persistently stored or if you want to unit-test your app components. The following image shows available non-persistent data storage options in Red Hat OpenShift on IBM Cloud.

Zoom

!
For more information about regions, see [Locations for resource deployment](https://cloud.ibm.com/docs/overview?topic=overview-locations) and [Service and infrastructure availability by location](https://cloud.ibm.com/docs/overview?topic=overview-services_region).



Managing billing and usage



* What is a GB-hour?

Runtime and container usage is charged based on the following variables:



* How much memory your runtime or container uses, in gigabytes (GB).
* The duration that memory is used.



Multiply the two values together, and the result is the GB-hour.
* How are bandwidth overage charges calculated for Bare Metal Servers and Virtual Servers?

IBM Cloud systems monitor all inbound and outbound traffic for a server regardless of the type of traffic. Based on the allocated bandwidth for a server, overages are assessed for excess traffic, which is monitored at the network switch level. Monitor your bandwidth usage with bandwidth graphs. For information, see [Viewing bandwidth graphs](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-bm-view-bandwidth-graphs).
* How do I prevent bandwidth overages?

If you provision multiple servers, you can potentially reduce future bandwidth overage charges by pooling your servers' bandwidth. For more information, see [Optimizing your bandwidth usage](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-bm-view-bandwidth-graphsbm-optimize-bandwidth-usage). Contact an [IBM Cloud Sales](https://cloud.ibm.com/catalog?contactmodule) representative to request a quote for additional server bandwidth.
* What's the difference between a Pay-As-You-Go and Subscription account?

With Pay-As-You-Go accounts, you're billed monthly for your resource usage. Your resource usage consists of recurring and fluctuating costs. This account type is a good fit for developers or companies that want to explore the entire IBM Cloud catalog but have smaller or variable workloads.
├── (A)Data-Services-Operations {ID: account-data-services-operations, BU: Operations}
└── (A)Data-Services-Support {ID: account-data-services-support, BU: Support}

ID -> Unique identifier of the entity
E -> Enterprise entity
AG -> Account group entity
A -> Account entity
BU -> Billing unit
Show more

Given this structure, the Cloud-Provider enterprise has the following effective billing units:



* The Cloud-Provider enterprise has three effective billing units: Administration, Operations, and Support.
* The Platform-Services account group has one effective billing unit: Operations.
* The Solutions, AI-Services, and Data-Services account groups have two effective billing units: Operations and Support.





 Example queries and responses 

Enterprise Cloud-Provider reports

Query: https://enterprise.cloud.ibm.com/v1/resource-usage-reports?enterprise_id=enterprise-cloud-provider&month=2019-06

This query returns three reports:



* Usage aggregated towards (E)Cloud-Provider:(BU)Administration
* Usage aggregated towards (E)Cloud-Provider:(BU)Operations
* Usage aggregated towards (E)Cloud-Provider:(BU)Support



Enterprise Cloud-Provider children reports

Query: https://enterprise.cloud.ibm.com/v1/resource-usage-reports?enterprise_id=enterprise-cloud-provider&month=2019-06&children=true

This query returns four reports:



* Usage aggregated towards (A)Administration:(BU)Administration
* Usage aggregated towards (AG)Platform-Services:(BU)Operations
* Usage aggregated towards (AG)Solutions:(BU)Operations
* Usage aggregated towards (AG)Solutions:(BU)Support



Account group Solutions reports

Query: https://enterprise.cloud.ibm.com/v1/resource-usage-reports?account_group_id=group-solutions&month=2019-06

This query returns two reports:



* Usage aggregated towards (AG)Solutions:(BU)Operations
* Usage aggregated towards (AG)Solutions:(BU)Support
Managing data sets 

Data sets are defined to identify the types of tests that you run in your development process to define the passing criteria for an application. When you define rules in a policy, IBM Cloud® DevOps Insights provides seven pre-defined data sets that you can use to run in your development process. Or, use custom data sets to represent the various types of tests. You can have policy rules for each data set and define rules for custom data sets. Separate policies can be created for each application. Data sets appear on the Quality Dashboard page after you start populating data for the data set.

For more information about viewing the Quality Dashboard, see [DevOps data aggregation](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-devops-data-aggregation).

For more information about defining a policy, see [Defining policies and rules](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-defining-policies-rules).



 Viewing data sets 

View your current data sets by browsing your Quality Dashboard page. You can rearrange your data in the table to be in a more convenient order. To view your data sets, use the following steps:



1. From the IBM Cloud console, 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. Select Quality Dashboard.
5. Click the Overflow icon !
[Google Compute Engine persistent disk Container Storage Interface (CSI) Driver](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-gcp-compute-persistent-disk-csi-driverstorage-gcp-compute-persistent-disk-csi-driver)



* [Prerequisites](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-gcp-compute-persistent-disk-csi-driversat-storage-gcp-csi-prereq)
* [Creating and assigning a configuration in the console](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-gcp-compute-persistent-disk-csi-drivergcp-compute-persistent-disk-csi-driver-config-create-console)
* [Creating a configuration in the CLI](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-gcp-compute-persistent-disk-csi-drivergcp-compute-persistent-disk-csi-driver-config-create-cli)
* [Creating a configuration in the API](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-gcp-compute-persistent-disk-csi-drivergcp-compute-persistent-disk-csi-driver-config-create-api)
* [Deploying an app that uses Google Compute Engine persistent disk](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-gcp-compute-persistent-disk-csi-driversat-storage-gcp-deploy-app)
* [Creating a storage assignment in the console](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-gcp-compute-persistent-disk-csi-driverstorage-gcp-compute-persistent-disk-csi-driver-include-assignment-create-console)
* UI: The web application that virtual assistant builders use to create skills and assistants.







 Data sources 

The Watson Assistant microservices use the following resources:



* Elastic: The elastic data store stores customer messages. These user conversation logs that can be reviewed from the Analtyics page or searched from the /logs API endpoint. Introduced with the 1.5.0 release.
* Etcd: A popular distributed key-value storage solution. Ectd is used by Litelinks clients and servers (Store, Dialog, NLU, Master, TAS, ED-MM) for service discovery. It is used by microservices from the language understanding pipeline (NLU, Master, TAS, ED-MM) to store metadata. For more information, see [Etcd store](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-architecturearchitecture-etcd).
* Kafka: A queuing system for incoming customer messages. Introduced with the 1.5.0 release.
* PostgreSQL: A popular relational database. This database is used only by the Store microservice and it is the primary store for workspaces, skills, and assistants. The deployment and pod names that are related to PostgreSQL are prefixed as ${release-name}-store-postgres. For more information, see [PostgreSQL data store](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-architecturearchitecture-postgres).
* Multicloud Object Gateway: Multicloud Object Gateway is an object storage service that implements the Amazon S3 API. It is used by the language understanding pipeline microservices (clu-controller, clu-serving, clu-training, tf-mm, ed-mm, and dragonfly) to store and load trained models for intent and entity classification. It is used by the authoring and runtime service (store) to store versioned data of the skills and also used as a temporary storage for asynchronous uploads for the authoring experience.
"offering": {
"name": "Cloud Object Storage",
"type": {
"group": "crn_service_name",
"key": "cloud-object-storage",
"kind": "service",
"id": "dff97f5c-bc5e-4455-b470-411c3edbe49c"
}
},
"resources": [
{
"crn": "crn:v1:staging:public:cloud-object-storage:global:a/2dded3de4a4d4a098ebd0998be5cc845:723a59c4-9338-43fe-9dc4-e4a87cc78c8e::",
"note": "Resource note"
}
]
}'

OfferingType offeringType = new OfferingType.Builder()
.group(OfferingType.Group.CRN_SERVICE_NAME)
.key("cloud-object-storage")
.build();
Offering offeringPayload = new Offering.Builder()
.name("Cloud Object Storage")
.type(offeringType)
.build();
CreateCaseOptions createCaseOptions = new CreateCaseOptions.Builder()
.type("technical")
.subject("Example technical case")
.description("This is an example case description. This is where the problem would be described.")
.offering(offeringPayload)
.severity(4)
.build();

Response<Case> response = service.createCase(createCaseOptions).execute();
Case xCase = response.getResult();

System.out.println(xCase);

offering_type = OfferingType(
group='crn_service_name',
key='cloud-object-storage'
)
offering_payload = Offering(
name='Cloud Object Storage',
Glossary terms for IBM Cloud 

This glossary provides terms and definitions for IBM Cloud®.

The following cross-references are used in this glossary:



* See refers you from a nonpreferred term to the preferred term or from an abbreviation to the spelled-out form.
* See also refers you to a related or contrasting term.





 A 



 access control list 

A list that statelessly manages inbound and outbound traffic for a subnet through the use of rules. An access control list helps provide security at the subnet level.





 access group 

A set of users and service IDs organized into a group that is used as the subject of an access policy for assigning all group members the same access.





 access policy 

A method for granting users, service IDs, and access groups access to account resources. An access policy includes a subject, target, and role.





 access token 

A value used by the consumer to gain access to the protected resources on behalf of the user, instead of using the user's service provider credentials.





 account 

A unit within the representation of an organizational structure. It can include resources, such as servers, access controls, and configurations. See also [enterprise account](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx9863395).





 account group 

An organizational unit for accounts within an enterprise. An account group can contain accounts or other account groups. See also [enterprise](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx2026915).





 accuracy 

A measure of the correctness of the decisions and predictions that are made by machine learning models, which are often part of AI systems. See also [precision](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx2003831), [recall](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx2154357).





 accuracy analysis 

Analyzing machine learning model scores to determine whether changes are needed to improve accuracy.





 action