vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Virtual private endpoints enable you to connect to supported IBM Cloud services from your VPC network by using the IP addresses of your choosing, allocated from a subnet within your VPC. Virtual private endpoints are an evolution of the private connectivity to IBM Cloud services. They are virtual IP interfaces that are bound to an endpoint gateway created on a per service or service instance basis.

Virtual private endpoints are supported only for paid plans. Check the plan information for your service to learn about the plans that support virtual private endpoints. For more information, see [Virtual Private Endpoints](https://cloud.ibm.com/docs/speech-to-text?topic=watson-virtual-private-endpoints).





 CORS support 

The service supports Cross-Origin Resource Sharing (CORS). By using CORS, web pages can request resources directly from a foreign domain. CORS circumvents the same-origin security policy, which otherwise prevents such requests. Because the service supports CORS, a web page can communicate directly with the service without passing the request through the web server that hosts the page.

For instance, a web page that is loaded from a server in IBM Cloud can call the customization API directly, bypassing the IBM Cloud server. For more information, see [enable-cors.org](https://enable-cors.org/).





 Signed URLs 

Signed URLs provide authentication information as a query string. Although signed URLs provide access for a limited time and with limited permissions, they allow any user with such a URL to access the service, regardless of whether that user has an account. The Speech to Text service does not support signed URLs.





 FISMA support 

IBM Cloud Pak for Data

Federal Information Security Management Act (FISMA) support is available for Speech to Text for IBM Cloud Pak for Data offerings as of version 1.0.1. Speech to Text for IBM Cloud Pak for Data is FISMA High Ready.





 FIPS support 

IBM Cloud Pak for Data

Speech to Text for IBM Cloud Pak for Data supports running on Federal Information Processing Standard (FIPS)-enabled clusters as of version 4.5.1.
For a comprehensive list of which SAP Business Analytics products benefits from SAP router connections, see [SAP Note 1478974](https://launchpad.support.sap.com//notes/1478974).

A jumphost is used to access, manage, and administer SAP virtual server instances from the same customer ZONE directly from their premises. These SAP virtual server instances can be in a separate security zone but should be on same IBM Cloud region. The customer connection to the jumphost follows the same rules as the direct connection from customer premises to the virtual server instance SAP instances. The connection uses the CFN IP and security group 1 firewall rules from a designated public subnet. In this architecture, there are two security groups defined; this arrangement is the simplest method for separating the public and private subnets. You can add more security groups if you require more isolation.





 Virtual server instances on SAP NetWeaver 7.x APAB stack, JAVA stack, and dual stack (ABAP+JAVA) architectural design on IBM Cloud® VPC on Unix 



 Standard system 

In a standard system, all main instances run on a single virtual server instance within a private subnet. [about virtual servers for VPC](https://cloud.ibm.com/docs/vpc-on-classic-vsi?topic=vpc-on-classic-vsi-virtual-private-cloud). The virtual server instance has these components:

Zoom

![Figure 2. Standard installation](https://cloud.ibm.com/docs-content/v1/content/f89cc64b006ca59b35404693959c83d5747fee3e/sap/images/refarch-sap-syb-std-only.svg)

Figure 2. SAP NetWeaver 7.x SYB standard installation with AAS

Architecture of SAP NetWeaver AS for ABAP

SAP tools create a PAS Instance and an ASCS Instance. This method is the standard for Java Stack (System) and is now standard for ABAP Stack.



1. The Primary Application Server (PAS) - An instance is an administrative unit that contains various components of an SAP system.
* UI
* CLI
* API







 Viewing details of an endpoint gateway 

You can view details about a specific endpoint gateway, or see a summary of endpoint gateways for VPC by using the UI, CLI, or API.

Only services that support Virtual Private Endpoints for VPC show up in the list of endpoint gateway targets.



 Viewing details of an endpoint gateway using the UI 

To view details of an endpoint gateway by using the IBM Cloud® console, follow these steps:



1. From the [IBM Cloud console](https://cloud.ibm.com/login), select the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/vpc//images/menu_icon.png), then click VPC Infrastructure > Virtual private endpoint gateways in the Network section.

The Virtual private endpoint gateways for VPC page shows all endpoint gateways for all VPCs in the region.
2. To view the details of a specific gateway, click an individual gateway name.

From the details page, you can view additional information about the endpoint gateway, view its bound reserved IPs and their subnets, delete an endpoint gateway, attach a security group, and more.



Descriptions of the fields for the virtual endpoint gateway details page are:



Table 1. Details about your endpoint gateway

 Field Description 

 Name The name of the endpoint gateway. Click the Edit icon ![Edit icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/vpc//images/edit.png) to update the name. 
 Resource group The resource group of the endpoint gateway. 
 Virtual private cloud The VPC where the endpoint gateway is located. Click to see the VPC's details.
File performance and endurance volume’s data migration is not supported, for this, consider that uses a third-party tool such as rsync. A sample script that uses rsync can be found [here](https://github.com/IBM-Cloud/vpc-migration-tools).
* Is the migration intrusive?

Usually the migration is nonintrusive. It can be done while the server is up and running. However, the source server does need some unused space to do the image capture of the server. In addition, RMM does require SSH (port 22) to be open on both the server and target to run the migration. The CPU consumption for image capture and copying to the target must be minimal.
* What data does the discovery tool identify from VMware vCenter?

The discovery tool discovers guest VMs from VMware and it uploads into RMM as the source for migrating in a typical wave. Each wave is named by ESXi host IP address from which guest VMs are discovered.
* Does the migration solution support auto-provisioning of the target server?

Yes. With RMM Auto-Provision feature, you can auto-provision the target server. For more informaation, see "Bare metal to virtual server migration on a private network that uses RMM": option 2 of Step 1: [Set up and provision VPC and virtual server instance](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-migrating-images-vmware-vpccloud-vpc-vsi-setup).
* Why is IBM Cloud® making the transition from Advanced Monitoring by Nimsoft to IBM Cloud Monitoring?

IBM Cloud is committed to providing you the highest quality of service and is making the transition to a new monitoring offering. IBM Cloud Monitoring offers an improved customer experience, robust functionality, and customizable dashboards for your resource monitoring needs. For more information, see [IBM Cloud Monitoring](https://cloud.ibm.com/docs/monitoring?topic=monitoring-getting-started).
* What benefits does IBM Cloud Monitoring provide?
IBM Cloud Load Balancer,High availability and resiliency for infrastructure



* 45 minutes
* 2021-09-03



[Setting up a Red Hat OpenShift for HPC cluster](https://cloud.ibm.com/docs/hpc-openshift?topic=hpc-openshift-setting-up-red-hat-openshift-hpc-cluster)Setting up a Red Hat OpenShift for HPC cluster

While IBM values the use of inclusive language, terms that are outside of IBM's direct influence are sometimes required for the sake of maintaining user understanding. As other industry leaders join IBM in embracing the use of inclusive language, IBM will continue to update the documentation to reflect those changes.

Virtual Private Cloud (VPC) IBM Cloud Load Balancer

+3

Monitoring,Log Analysis,Red Hat OpenShift for HPC



* 60 minutes
* 2022-04-14



[Setting up an HPC cluster](https://cloud.ibm.com/docs/ibm-spectrum-lsf?topic=ibm-spectrum-lsf-using-hpc-cluster)Setting up an HPC cluster

The HPC cluster consists of a login node, a storage node where the block storage volume is attached, 1 - 3 LSF management nodes, and a number of LSF worker nodes.

Virtual Servers for Classic Virtual Private Cloud (VPC)

+2

IBM Cloud Load Balancer,IBM Spectrum LSF



* 60 minutes
* 2023-03-24



[Hosting web applications from a secure private network](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-web-app-private-network)Hosting web applications from a secure private network

This tutorial takes you through the creation of a scalable and secure Internet facing web application hosted in private network secured using a virtual router appliance (VRA), VLANs, NAT and firewalls. The application comprises a load balancer, two web application servers and a MySQL database server. It combines three tutorials to illustrate how web applications can be securely deployed on the IBM Cloud IaaS platform using classic networking.
containers-kubernetes.account-subnet.list Subnets in the IBM Cloud classic infrastructure account are listed. 
 containers-kubernetes.account-subnet-vlan-spanning.get Details on whether the IBM Cloud account has VLAN spanning enabled are returned. 
 containers-kubernetes.account-user-config.get Details on whether a user can create in a certain region and resource group are returned. 
 containers-kubernetes.account-vpc.get Details for a virtual private cloud (VPC) instance are returned. 
 containers-kubernetes.account-vpc.list Virtual private cloud (VPC) instances in the IBM Cloud account are listed. 
 containers-kubernetes.account-worker-reservation.create A reservation for worker nodes is created. 
 containers-kubernetes.account-worker-reservation.get Details of a reservation are returned. 
 containers-kubernetes.account-worker-reservation.list Reservations are listed. 







 Cluster add-on events 

The following list of the cluster add-on events are sent to IBM Cloud Activity Tracker.



Cluster add-on events

 Action Description 

 containers-kubernetes.cluster-addon.disable A cluster add-on is disabled. 
 containers-kubernetes.cluster-addon.enable A cluster add-on is enabled. 
 containers-kubernetes.cluster-addon.list Cluster add-ons are listed. 
 containers-kubernetes.cluster-addon.update A cluster add-on is updated. 
 containers-kubernetes.cluster-addon-dashboard.start The Kubernetes dashboard proxy is started. 
 containers-kubernetes.cluster-addon-debugtool-dashboard.start The diagnostics and debug tool add-on dashboard is started. 
 containers-kubernetes.cluster-addon-terminal.start Deprecated: Starts the Kubernetes web terminal proxy. 







 Fluentd logging events 

The following list of Fluentd logging events for a cluster are sent to IBM Cloud Activity Tracker.



Fluentd logging events

 Action Description
Connecting to z/OS virtual server instances 

A z/OS virtual server instance is typically a private backend infrastructure component that must never be directly accessed from the outside world. Even environments that are used for development, testing, or demonstration must follow good practices for logical isolation.

To learn how to use subnets to securely isolate and control traffic to backend infrastructure such as a z/OS virtual server instance, you can refer to the following tutorials:



* [Public front end and private backend in a Virtual Private Cloud](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-public-app-private-backend)
* [Securely access remote instances with a bastion host](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-secure-management-bastion-server)
* [About client-to-site VPN servers](https://cloud.ibm.com/docs/vpc?topic=vpc-vpn-client-to-site-overview)



After you connected to the VPC network by using the client-to-site VPN server, you can access the z/OS virtual server instance by using the private IP address.



 Before you begin 

Make sure that you locate the private IP address before you connect to the z/OS instances. Private IP addresses are IP addresses that are provided by the system and are only reachable within the VPC network. You can find the private IP address of your z/OS virtual server instance under the Reserved IP address column on the console after the instance is created successfully.

If your z/OS virtual server instance is created by using the z/OS dev and test stock image, you can refer to the [Reserved configurations](https://www.ibm.com/docs/en/wazi-aas/1.0.0?topic=vpc-configurations-in-zos-stock-images) table to add additional ports to the security group of your instance.





 Step 1. Configuring the password 

Before you can log in to a z/OS virtual server instance, you must change the password for the default user ID ibmuser.
To implement a data center transformation, the RackWare Management Module (RMM) migration solution provides a seamless virtual-to-virtual replatforming for VMware virtual machine (VM) to IBM Cloud® virtual server instance migration. It allows the adoption of existing capabilities of IBM Cloud. Its intuitive GUI allows you to move the OS, application, and data from VMware ESXi to IBM Cloud VPC virtual server instance.

Virtual Private Cloud (VPC) Virtual Servers for Classic

+1

Building infrastructure



* 45 minutes
* 2022-11-23



[Creating a cluster in your Virtual Private Cloud (VPC)](https://cloud.ibm.com/docs/containers?topic=containers-vpc_ks_tutorial)Creating a cluster in your Virtual Private Cloud (VPC)

Create an IBM Cloud® Kubernetes Service cluster in your Virtual Private Cloud (VPC).

Kubernetes service Virtual Private Cloud (VPC)



* 30 minutes
* 2023-07-07



[Setting up a bastion host that uses Teleport](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-connectivity-bastion-tutorial-teleport)Setting up a bastion host that uses Teleport

This tutorial shows you one way that can be used to meet the IBM Cloud Framework for Financial Services requirements that are related to bastion host. There are various ways to implement a compliant bastion solution, but we show you how to configure a bastion host in your VPC by using Teleport Enterprise Edition, along with Object Storage and App ID for enhanced security. You will learn how to set up a Teleport-based solution that meets the previously described IBM Cloud Framework for Financial Services requirements.

Object Storage App ID

+2

Virtual Private Cloud (VPC),IBM Cloud Framework for Financial Services



* 2 hours
* 2023-05-11
The same placement group can be used for instances that are provisioned on shared public servers in different VPCs.



 Benefits 

Placement groups give you a measure of control over the host on which a new public virtual server is placed in relation to other virtual servers in the same placement group.

They support high availability workloads by making sure that virtual server instances in the group do not share a physical host or power supply. This technology is an added layer of assuredness for the resiliency of your virtual server instances if an unexpected power disruption or host failure occurs.

You can build a workload high availability application within a data center knowing that your virtual servers are isolated from each other. You can be assured that your applications are provisioned on the cloud data center infrastructure to maximize availability with unique host server hardware.







 Understanding placement strategies 

Placement groups for VPC have two different anti-affinity strategies for high availability. Using placement strategies minimizes the chance of service disruption with virtual server instances that are placed on different hosts or into an infrastructure with separate power and network supplies.



 Host spread strategy (host anti-affinity) for high availability. 

A host spread placement group strategy guarantees that each instance is placed on separate compute hosts. This placement group strategy avoids the host from being a single point of failure. This placement policy supports a maximum of 12 instances per placement group.

Instance provisioning fails if an instance cannot be placed on a different node than all other instances in the placement group.





 Power spread strategy (power anti-affinity) for high availability. 

A power spread placement group strategy guarantees each instance is placed on computer hosts with separate power and network supplies to minimize the chances of service disruption. This placement group strategy supports a maximum of four instances per placement group.

Instance provisioning fails if the instance cannot be placed on a different power supply than all other instances in the placement group.

If a placement group is not specified when the instance is provisioned, the default placement strategy is to distribute customer instances among as many different physical hosts as possible. This approach is a best effort basis and does not guarantee the instances are placed on different physical hosts. To guarantee different physical hosts, specify a placement group during instance provisioning.







 Using placement groups with instance groups
The transit DNS instance can resolve x-transit.com and has its own forwarding rules to the enterprise and spokes to resolve the rest. Similarly the spokes rely on the transit DNS instance to resolve the enterprise, transit and the other spokes.
8. Optionally explore the other DNS instances and find similarly named DNS zones and A records for the other test instances.







 DNS Testing 

There is a set of curl DNS tests that are available in the pytest script. These tests will curl using the DNS name of the remote. There are quite a few so run the tests in parallel:

pytest -n 10 -m dns







 Step 4: Virtual Private Endpoint Gateways 

VPC allows private access to IBM Cloud Services through [Virtual Private Endpoint (VPE) for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-about-vpe). The VPEs allow fine grain network access control via standard IBM Cloud VPC controls:



* [Security Groups](https://cloud.ibm.com/docs/vpc?topic=vpc-using-security-groups).
* [VPC Network Access Control Lists](https://cloud.ibm.com/docs/vpc?topic=vpc-using-acls).
* [Routing tables and routes](https://cloud.ibm.com/docs/vpc?topic=vpc-about-custom-routes).



Zoom

![Adding virtual private endpoint gateways](https://cloud.ibm.com/docs-content/v1/content/f84e2238288b7f0355715a4c355609ce7ac48fb0/solution-tutorials/images/vpc-transit/vpc-transit-vpe.svg)

Adding virtual private endpoint gateways



1. Create a IBM Cloud Databases for Redis instance and VPEs for the transit and each of the spoke VPCs, by applying the vpe_transit_tf and vpe_spokes_tf layers:
* UI
* CLI
* API







 Attaching a Block Storage for VPC volume 

When you create a IBM® Cloud Block Storage for Virtual Private Cloud volume for a virtual server instance, the volume is attached to the instance by default. When you detach a volume, it exists as an unattached volume that you can later reattach. These available volumes are displayed in the list of [all Block Storage for VPC volumes](https://cloud.ibm.com/docs/vpc?topic=vpc-viewing-block-storageviewvols). You can attach the volume to another instance from the list of all Block Storage for VPC volumes, or when you view details about an instance.



 Volume attachment limits 

You can attach only one Block Storage for VPC boot volume to a virtual server instance at a time, but you can attach up to 12 Block Storage for VPC data volumes to a single instance.

When you create a Hyper Protect Virtual Servers for IBM Cloud® Virtual Private Cloud instance, only one data volume can be added currently. Even if you attach more volumes, they are not used by the instance.

You can't use the UI to attach Block Storage for VPC volumes to IBM Cloud® Kubernetes Service Cluster worker nodes. For more information about using the CLI to attach volumes to cluster nodes, see [Storing data on Block Storage for VPC](https://cloud.ibm.com/docs/containers?topic=containers-vpc-block).





 Attaching a Block Storage for VPC volume to a virtual server instance 

You can attach a volume to a virtual server instance from the list of block storage volumes, volume details page, or from the instance details page.



 Attaching a volume to an instance from the list of volumes 

From the list of all Block Storage for VPC volumes, follow these steps.



1. 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.
For more information about VPC subnets, see [Characteristics of subnets in the VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-about-networking-for-vpcsubnets-in-the-vpc).



* The default CIDR size of each VPC subnet is /24, which can support up to 253 worker nodes. If you plan to deploy more than 250 worker nodes per zone in one cluster, consider creating a subnet of a larger size.
* After you create a VPC subnet, you can't resize it or change its IP range.
* Multiple clusters in the same VPC can share subnets.
* VPC subnets are bound to a single zone and can't span multiple zones or regions.
* After you create a subnet, you can't move it to a different zone, region, or VPC.
* If you have worker nodes that are attached to an existing subnet in a zone, you can't change the subnet for that zone in the cluster.
* The 172.16.0.0/16, 172.18.0.0/16, 172.19.0.0/16, and 172.20.0.0/16 ranges are prohibited.







 Worker-to-master and user-to-master communication using Virtual private endpoints or cloud service endpoints 

Red Hat OpenShift on IBM Cloud uses different types of service endpoints to establish a connection from authorized cluster users and worker nodes to the Kubernetes master. Authorized cluster users communicate with the Kubernetes master through cloud service endpoints. Depending on your cluster version, worker nodes communicate with the Kubernetes master through cloud service endpoints or VPC virtual private endpoints.

Before you create a cluster, you must enable your account to use service endpoints. To enable service endpoints, run ibmcloud account update --service-endpoint-enable true.

In VPC clusters in Red Hat OpenShift on IBM Cloud, you can't disable the private cloud service endpoint or set up a cluster with the public cloud service endpoint only.

Your VPC cluster is created with both a public and a private cloud service endpoint by default.