vania-janet/multiturn-rag-retrieval-data huggingface dataset:
An alternative connectivity pattern requires use of the [VPN for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-using-vpn) service to securely connect from your private network to the management VPC. VPN for VPC can be used as a static, route-based VPN or a policy-based VPN to set up an IPsec site-to-site tunnel between your VPC and your on-premises private network, or another VPC. When using VPN for VPC, you need to place the gateway in a subnet (shown in the lower left subnet in the diagram).





 Bastion host 

Regardless of whether you are using Direct Link or VPN for VPC to connect to the management VPC, you need to ensure that all traffic is routed through a bastion host with session recording. The bastion host solution is depicted in the two rightmost lower subnets in the diagram.





 Connectivity between VPCs 

The management VPC needs to connect to the workload VPC to deploy, configure, and operate the components and workloads that are found in the workload VPC. [Transit Gateway](https://cloud.ibm.com/docs/transit-gateway?topic=transit-gateway-about) is designed specifically for this purpose, and is the means for connecting your management VPC to your workload VPC.







 Workload VPC 

The workload VPC provides compute, storage, and network services to support hosted applications and operations that deliver services to the consumer. Let's take a closer look at the components within the VPC.



 Regions and zones 

Just like the management VPC, the workload VPC is spread across three zones. The workload VPC should be created in the same MZR as the management VPC.





 Connectivity to workload VPC 

If the consumer is in the same organization as the application provider, then just like for the management VPC, Direct Link can provide access to the workload VPC. Alternatively, VPN for VPC can be used for site-to-site VPN connectivity.





 Storage and encryption 



 Block Storage for VPC
The output is returned in a discrete group.<-- </section "id="section-max-example" "> --><-- </section "id="section-max" "> --><-- <section "id="section-min" "> --> min Returns the lowest value in the specified field across all matching documents.<-- <section "id="section-min-syntax" "> --> Syntax min(field)
<-- </section "id="section-min-syntax" "> --><-- <section "id="section-min-example" "> --> Example <-- <table> -->Table 3. Sample product prices| Product | Price || -------- | ----- || I Series | 200 || J Series | 450 || X Series | 325 |<-- </table ""> -->When the min aggregation type is applied to a set of documents in which the price field contains the values that are shown in Table 3, the result is 200. min(price)=200
This aggregation type performs a terminal operation. When combined with other aggregations, the output is not used as input for the next aggregation. The output is returned in a discrete group.<-- </section "id="section-min-example" "> --><-- </section "id="section-min" "> --><-- <section "id="section-nested" "> --> nested Applying nested before an aggregation query restricts the aggregation to the area of the results that are specified.For example, nested(enriched_text.entities) means that only the enriched_text.entities components of any result are used to aggregate against.The following example checks how many mentions are returned per model type. nested(enriched_text.entities).term(enriched_text.entities.model_name)
The result shows that there are a total of 50 recognized entities and all of them are of type NLU. "aggregations":
{
"type": "nested",
"path": "enriched_text.entities",
For more information, see [Document Retrieval project aggregations](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-query-defaultsaggregations-dr).

For more information about how to submit a query, see the Discovery [API reference](https://cloud.ibm.com/apidocs/discovery-dataquery).





 average 

Returns the mean of values of the specified field across all matching documents.



 Syntax 

average(field)





 Example 



Table 1. Sample product prices

 Product Price 

 I Series 200 
 J Series 450 
 X Series 325 



When the average aggregation type is applied to a set of documents in which the price field contains the values that are shown in Table 1, the result is 325.

average(price)=325

This aggregation type performs a terminal operation. When combined with other aggregations, the output is not used as input for the next aggregation. The output is returned in a discrete group.

{
"query":"brake",
"aggregation": "term(field:STATE,count:3).average(field:VEH_SPEED).term(field:CITY,count:2)"
}

For each state returned by the first term aggregation operation, the response shows the average vehicle speed specified in the incident reports. Notice that the second term aggregation uses the output from the first term aggregation, not the average aggregation, as its input.

{
"matching_results": 9064,
"retrieval_details": {
"document_retrieval_strategy": "untrained"
},
"aggregations": [
{
"type": "term",
"field": "STATE",
"count": 3,
"results":
{
"key": "CA",
"matching_results": 1210,
"aggregations":
{
"type": "average",
"field": "VEH_SPEED",
"value": 26.239653512993264
},
{
When you look at the specific resources for the VPC infrastructure and specify Block Storage for VPC as the resource type, you can see the access management tags for the Block Storage for VPC service.







 Deleting a Block Storage for VPC volume and data eradication 

When you delete a Block Storage for VPC volume, that data immediately becomes inaccessible. All pointers to the data on the physical disk are removed. If you later create a volume in the same or another account, a new set of pointers is assigned. The account can't access any data that was on the physical storage because those pointers are deleted. When new data is written to the disk, any inaccessible data from the deleted volume is overwritten.

IBM guarantees that data deleted cannot be accessed and that deleted data is eventually overwritten and eradicated. Further, when you delete a Block Storage for VPC volume, those blocks must be overwritten before that Block Storage for VPC is made available again, either to you or to another customer.

Further, when IBM decommissions a physical drive, the drive is destroyed before disposal. Decommissioned drives are unusable and any data on them is inaccessible.



 Deleting a Block Storage for VPC data volume in the UI 

Deleting a Block Storage for VPC volume completely removes its data. The volume cannot be restored.

You cannot delete an active Block Storage for VPC volume. To delete a volume, first [detach it](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-block-storagedetach) from the virtual server instance. If you took snapshots of the volume, all snapshots must be in a stable state.

To delete a volume, complete the following steps.



1. Go to the list of all Block Storage for VPC volumes. In the [IBM Cloud console](https://cloud.ibm.com/login), go to the menu ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > Block storage volumes.
2.
When you look at the specific resources for the VPC infrastructure and specify Block Storage for VPC as the resource type, you can see the access management tags for the Block Storage for VPC service.







 Deleting a Block Storage for VPC volume and data eradication 

When you delete a Block Storage for VPC volume, that data immediately becomes inaccessible. All pointers to the data on the physical disk are removed. If you later create a volume in the same or another account, a new set of pointers is assigned. The account can't access any data that was on the physical storage because those pointers are deleted. When new data is written to the disk, any inaccessible data from the deleted volume is overwritten.

IBM guarantees that data deleted cannot be accessed and that deleted data is eventually overwritten and eradicated. Further, when you delete a Block Storage for VPC volume, those blocks must be overwritten before that Block Storage for VPC is made available again, either to you or to another customer.

Further, when IBM decommissions a physical drive, the drive is destroyed before disposal. Decommissioned drives are unusable and any data on them is inaccessible.



 Deleting a Block Storage for VPC data volume in the UI 

Deleting a Block Storage for VPC volume completely removes its data. The volume cannot be restored.

You cannot delete an active Block Storage for VPC volume. To delete a volume, first [detach it](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-block-storage&interface=clidetach) from the virtual server instance. If you took snapshots of the volume, all snapshots must be in a stable state.

To delete a volume, complete the following steps.



1. Go to the list of all Block Storage for VPC volumes. In the [IBM Cloud console](https://cloud.ibm.com/login), go to the menu ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > Block storage volumes.
2.
When you look at the specific resources for the VPC infrastructure and specify Block Storage for VPC as the resource type, you can see the access management tags for the Block Storage for VPC service.







 Deleting a Block Storage for VPC volume and data eradication 

When you delete a Block Storage for VPC volume, that data immediately becomes inaccessible. All pointers to the data on the physical disk are removed. If you later create a volume in the same or another account, a new set of pointers is assigned. The account can't access any data that was on the physical storage because those pointers are deleted. When new data is written to the disk, any inaccessible data from the deleted volume is overwritten.

IBM guarantees that data deleted cannot be accessed and that deleted data is eventually overwritten and eradicated. Further, when you delete a Block Storage for VPC volume, those blocks must be overwritten before that Block Storage for VPC is made available again, either to you or to another customer.

Further, when IBM decommissions a physical drive, the drive is destroyed before disposal. Decommissioned drives are unusable and any data on them is inaccessible.



 Deleting a Block Storage for VPC data volume in the UI 

Deleting a Block Storage for VPC volume completely removes its data. The volume cannot be restored.

You cannot delete an active Block Storage for VPC volume. To delete a volume, first [detach it](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-block-storage&interface=uidetach) from the virtual server instance. If you took snapshots of the volume, all snapshots must be in a stable state.

To delete a volume, complete the following steps.



1. Go to the list of all Block Storage for VPC volumes. In the [IBM Cloud console](https://cloud.ibm.com/login), go to the menu ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > Block storage volumes.
2.
This configuration lets you customize the Local SSD Storage and the attachment of either Network Block or File storage options.





 Understanding Bare Metal profile names 

The Bare Metal profile names are contextual and sequential. This example uses an SAP HANA certified server to list and describe the naming conventions:



Table 2. Profile naming for SAP HANA

 Profile name Naming convention component What it means 

 BI.S4.H2.1500 BI Bluemix Infrastructure (former name of IBM Cloud) 
 S4 Series 4 (processor generation) <br><br><br><br> * S2 is Intel Broadwell<br> * S3 is Intel Skylake or Kaby Lake<br> * S4 is Intel Cascade Lake<br><br><br> 
 H HANA-certified server 
 2 2-socket server 
 1500 1500 GB RAM 







 Profiles available on Hourly Consumption Billing 

The following Bare Metal servers are available on Hourly Consumption Billing:



* BI.S3.H2.192
* BI.S3.H2.384
* BI.S4.H2.192 Appliance
* BI.S4.H2.384 Appliance
* BI.S4.H2.768 Appliance
* BI.S4.H2.1500 Appliance
* BI.S4.H2.3000 Appliance
* BI.S4.H2.192 (boot only)
* BI.S4.H2.384 (boot only)
* BI.S4.H2.768 (boot only)
* BI.S4.H2.1500 (boot only)
* BI.S4.H2.3000 (boot only)







 Storage specifications 

The following dual-socket servers are available in the Appliance delivery model for SAP HANA, with preconfigured disk storage.

These Profiles do not use any Network Block or File storage options that are mounted to the Bare Metal server. These Profiles use only Local SSD Storage devices that are physically attached through a RAID Controller inside the server.



 BI.S3.H2.192 Appliance
- name: myvol
mountPath: /usr/share/nginx/html
volumeClaimTemplates:
- metadata:
name: myvol
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 20Gi
iops: "300" required only for performance storage
storageClassName: ibmc-block-retain-bronze
Show more

The following example shows how to deploy NGINX as a stateful set with three replicas. The stateful set does not specify the region and zone where the block storage is created. Instead, the stateful set uses an anti-affinity rule to ensure that the pods are spread across worker nodes and zones. By defining topologykey: failure-domain.beta.kubernetes.io/zone, the Kubernetes scheduler can't schedule a pod on a worker node if the worker node is in the same zone as a pod that has the app: nginx label. For each stateful set pod, two PVCs are created as defined in the volumeClaimTemplates section, but the creation of the block storage instances is delayed until a stateful set pod that uses the storage is scheduled. This setup is referred to as [topology-aware volume scheduling](https://kubernetes.io/blog/2018/10/11/topology-aware-volume-provisioning-in-kubernetes/).

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: ibmc-block-bronze-delayed
parameters:
billingType: hourly
classVersion: "2"
fsType: ext4
iopsPerGB: "2"
sizeRange: '[20-12000]Gi'
type: Endurance
provisioner: ibm.io/ibmc-block
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer
---
apiVersion: v1
kind: Service
metadata:
name: nginx
labels:
app: nginx
spec:
And, security group rules have been added to provide more secure access to the cluster by allowing SSH from only specific nodes.





 January 2022 



 28 January 2022 

IBM Spectrum Symphony enhancements
: You now have the option to use Spectrum Scale for shared storage that's accessible by the Spectrum Symphony compute nodes. For more information, see [Using Spectrum Scale storage](https://cloud.ibm.com/docs/hpc-spectrum-symphony?topic=hpc-spectrum-symphony-using-spectrum-scale-storage). With the latest changes, RHEL 8.2 custom images take the place of RHEL 7.7 and CentOS 7.7 custom images with included optimizations for NFS. Additionally, the security vulnerability for Polkit Local Privilege Escalation Vulnerability (CVE-2021-4034) has been mitigated with changes to the post-provisioning scripts.





 13 January 2022 

Security update
: A new custom image with an upgraded log4j version (2.17) to mitigate Log4Shell vulnerability (CVE-2021-44228) is included in this security update.







 December 2021 



 23 December 2021 

Security update
: A security update is included in this release that addresses the Log4Shell vulnerability (CVE-2021-44228).





 14 December 2021 

Dedicated hosts and additional improvements
: You now have the option to use dedicated hosts for static worker nodes in addition to having an enhanced ssh_command output and hyperthreading by default. For more information, see [Using dedicated hosts](https://cloud.ibm.com/docs/hpc-spectrum-symphony?topic=hpc-spectrum-symphony-using-dedicated-hosts). Further improvements include an update of the stock images that are used for login and storage nodes to RHEL 8.2 and clean up of entitlement and location input properties. Parallelism is now supported in Schematics destroy operations to help overall performance, and due to a bug fix, you can now avoid the Terraform warning regarding interpolation.







 October 2021 



 18 October 2021 

Introducing IBM Spectrum Symphony for HPC workloads
Release notes for IBM Spectrum Symphony 

Use these release notes to learn about the latest updates to IBM® Spectrum Symphony that are grouped by date.



 May 2023 



 31 May 2023 

Spectrum multicluster (SMC) support
: The initial release of Spectrum multicluster (SMC), which connects multiple IBM Spectrum Symphony clusters into a federation cluster, is now available. You can use SMC to redirect IBM Spectrum Symphony sessions to non-busy clusters, deploy and manage service packages, and monitor workload and resources.

Documentation enhancement: Integrating OpenLDAP with IBM Spectrum Symphony
: The newly added [Integrating OpenLDAP with IBM Spectrum Symphony](https://cloud.ibm.com/docs/hpc-spectrum-symphony?topic=hpc-spectrum-symphony-integrate-openldap-spectrum-symphony) tutorial walks you through the steps involved in configuring IBM Spectrum Symphony to use OpenLDAP as the primary directory service for user authentication.







 30 May 2023 

Persistent storage type support when using IBM Spectrum Scale storage
: You now have the option to use bare metal servers to deploy persistent storage for Spectrum Scale storage nodes.

Updated Spectrum Symphony and Spectrum Scale custom images
: Spectrum Symphony and Spectrum Scale custom images were updated to use RHEL 8.6 instead of RHEL 8.4.

Custom image support
: Documentation and scripts to make it easier for users to create and use their own custom images for Spectrum Symphony worker and Spectrum Scale storage nodes are now included in the solution.

Spectrum Symphony version update
: Spectrum Symphony product version was updated from 7.3.1 to 7.3.2.

Spectrum Scale version update
: Spectrum Scale product version was updated from 5.1.5.1 to 5.1.7.0.

Support automated public gateway creation when one is not associated with the subnets of an existing VPC
: When you choose to use an existing VPC, the automation associates the public gateway with all of the subnets if it is already part of the VPC. If the public gateway is not part of the VPC, then it creates a new public gateway and associates it with all subnets to allow internet access from the cluster nodes.

DNS functionality support
Name ibmc-file-bronze <br>ibmc-file-retain-bronze <br>ibmc-file-bronze-gid 
 Type Endurance storage 
 File system NFS 
 IOPS per gigabyte 2 
 Size range in gigabytes 20-12000 Gi 
 Hard disk SSD 
 Reclaim policy ibmc-file-bronze: Delete <br>ibmc-file-retain-bronze: Retain <br>ibmc-file-bronze-gid: Delete 
 Supplemental group ID The supplemental group ID 65531 is automatically set when you use the ibmc-file-bronze-gid storage class to allow non-root users access to your file storage instance. For more information about how to use this storage class or set custom group IDs, see [File storage: Adding non-root user access to persistent storage fails](https://cloud.ibm.com/docs/containers?topic=containers-cs_storage_nonroot). 
 Billing Hourly 
 Pricing [Pricing information](https://cloud.ibm.com/cloud-storage/file/order) 







 Sample customized storage classes 

You can create a customized storage class and use the storage class in your PVC.

IBM Cloud Kubernetes Service provides [pre-defined storage classes](https://cloud.ibm.com/docs/containers?topic=containers-file_storagefile_storageclass_reference) to provision File Storage for Classic with a particular tier and configuration. Sometimes, you might want to provision storage with a different configuration that is not covered in the pre-defined storage classes. You can use the examples in this topic to find sample customized storage classes.

To create your customized storage class, see [Customizing a storage class](https://cloud.ibm.com/docs/containers?topic=containers-file_storagecustom-sc-nfs-creat). Then, [use your customized storage class in your PVC](https://cloud.ibm.com/docs/containers?topic=containers-file_storageadd_file).



 Creating topology-aware storage
For more information, see [Creating a network](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_vcd-ops-guideshared_vcd-ops-guide-create-network).







 Procedure to order a Zerto Cloud Connector from the virtual data center 



1. Under Enabled services on the virtual data center details page, click Order a Zerto Cloud Connector.
2. Select an organization network and enter the IP address for the new VM to deploy to that network.
3. Review the hourly price and click Order. The Zerto Cloud Connector (ZCC) table displays on the virtual data center details page and the status changes to Creating.
4. You must pair the on-premises workloads to IBM Cloud before you can use ZCC. Generate a pairing token when the ZCC status changes to Ready to use.



1. In the Zerto Cloud Connector (ZCC) table, expand Pairing token.
2. Click Generate token. The generated token link expires in 48 hours and a new token is generated.
3. Click the Copy icon ![Copy icon](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/copy.svg) to copy the pairing token key.
4. From the on-premises site, use the pairing token key to link the on-premises virtual data centers to IBM Cloud. For more information, see [Zerto technical documentation](https://help.zerto.com/category/WmWare_9.7).









 Related links 



* [VMware Shared overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_overview)
* [Ordering virtual data centers](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_ordering)
Getting started with Stock images on VPC 

When you provision IBM Cloud® Virtual Servers for Virtual Private Cloud on x86 architecture, you can select from the supported virtual server operating system stock images, the virtual server operating system bundle stock image, or a custom image that you import from IBM Cloud Object Storage. The image that you select determines the operating system that is provisioned for your instance. If the image you select is a virtual server operating system bundle stock image, the software that is part of that bundle is also included in your instance.

In [IBM Cloud console](https://cloud.ibm.com/login), go to Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Compute > Images.

There are 3 different types of images for VPC.



* [Custom images](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images) (includes [Image from volume](https://cloud.ibm.com/docs/vpc?topic=vpc-image-from-volume-vpc))
* Stock images
* [Catalog images](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started-images-on-vpc-catalog)





 Images on VPC - Stock images 

When you provision a virtual server on your VPC, you need to select an image to determine the operating system for the server. The following are the virtual server operating system stock images available when you create a virtual server.



* [x86 virtual server images](https://cloud.ibm.com/docs/vpc?topic=vpc-about-images)
* [s390x virtual server images](https://cloud.ibm.com/docs/vpc?topic=vpc-vsabout-images)