vania-janet/multiturn-rag-retrieval-data huggingface dataset:
About Block Storage for VPC 

IBM® Cloud Block Storage for Virtual Private Cloud provides hypervisor-mounted, high-performance data storage for your virtual server instances that you can provision within an IBM Cloud® Virtual Private Cloud (VPC). The [VPC infrastructure](https://cloud.ibm.com/docs/vpc?topic=vpc-about-vpc) provides rapid scaling across zones and extra performance and security.



 Overview 

Block Storage for VPC supports all [virtual server profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilesvsi-profiles-relate-to-storage).

Block Storage for VPC volume data is stored redundantly across multiple physical disks in an Availability Zone to prevent data loss due to failure of any single component.

Block Storage for VPC provides primary boot volumes and secondary data volumes. Boot volumes are automatically created and attached during instance provisioning. Data volumes can be created and attached during instance provisioning as well, or as stand-alone volumes that you can later attach to an instance. To protect your data, you can use your own encryption keys or choose IBM-managed encryption.

You pay for only the capacity that you need. Block Storage for VPC capacity ranges from 10 GB up to 16,000 GB for all available [profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-aboutblock-storage-profiles-intro). For data volumes attached to a virtual server instance, you can [increase volume capacity](https://cloud.ibm.com/docs/vpc?topic=vpc-expanding-block-storage-volumes) in GB increments up to 16,000 GB capacity, depending on your volume profile. You can also [increase or decrease IOPS](https://cloud.ibm.com/docs/vpc?topic=vpc-adjusting-volume-iops) for a volume that is attached to an instance.

You can also apply user tags and access management tags to your boot and data volumes anytime. Add tags when you create a volume or update an existing volume with the UI, CLI, API and Terraform.
About Block Storage for VPC 

IBM® Cloud Block Storage for Virtual Private Cloud provides hypervisor-mounted, high-performance data storage for your virtual server instances that you can provision within an IBM Cloud® Virtual Private Cloud (VPC). The [VPC infrastructure](https://cloud.ibm.com/docs/vpc?topic=vpc-about-vpc) provides rapid scaling across zones and extra performance and security.



 Overview 

Block Storage for VPC supports all [virtual server profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilesvsi-profiles-relate-to-storage).

Block Storage for VPC volume data is stored redundantly across multiple physical disks in an Availability Zone to prevent data loss due to failure of any single component.

Block Storage for VPC provides primary boot volumes and secondary data volumes. Boot volumes are automatically created and attached during instance provisioning. Data volumes can be created and attached during instance provisioning as well, or as stand-alone volumes that you can later attach to an instance. To protect your data, you can use your own encryption keys or choose IBM-managed encryption.

You pay for only the capacity that you need. Block Storage for VPC capacity ranges from 10 GB up to 16,000 GB for all available [profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-about&interface=uiblock-storage-profiles-intro). For data volumes attached to a virtual server instance, you can [increase volume capacity](https://cloud.ibm.com/docs/vpc?topic=vpc-expanding-block-storage-volumes) in GB increments up to 16,000 GB capacity, depending on your volume profile. You can also [increase or decrease IOPS](https://cloud.ibm.com/docs/vpc?topic=vpc-adjusting-volume-iops) for a volume that is attached to an instance.

You can also apply user tags and access management tags to your boot and data volumes anytime. Add tags when you create a volume or update an existing volume with the UI, CLI, API and Terraform.
Isolate workloads by provisioning a dedicated host, attaching an encrypted data volume to a VSI, expanding the attached data volume, and resizing the VSI after the fact.

Virtual Private Cloud (VPC) Databases For PostgreSQL

+2

Schematics,Object Storage



* 2 hours
* 2023-05-05



[Securely access remote instances with a bastion host](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-secure-management-bastion-server)Securely access remote instances with a bastion host

This tutorial walks you through the deployment of a bastion host to securely access remote instances within a Virtual Private Cloud (VPC). A bastion host is an instance that is provisioned with a public IP address and can be accessed via SSH. Once set up, the bastion host acts as a jump server, allowing secure connection to instances provisioned without a public IP address.

Virtual Private Cloud (VPC)



* 1 hour
* 2023-05-05



[Using the IBM Cloud console to create VPC resources](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-using-the-ibm-cloud-console)Using the IBM Cloud console to create VPC resources

You can create and configure an IBM Cloud® Virtual Private Cloud (VPC) by using the IBM Cloud console.

Virtual Private Cloud (VPC)



* 30 minutes
* 2023-06-29



[Creating a custom image from volume and provisioning an instance in the UI](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-and-using-an-image-from-volume)Creating a custom image from volume and provisioning an instance in the UI

This tutorial demonstrates how to create a custom image from the boot volume of a virtual server instance, and then use that image to create a new instance.

Virtual Private Cloud (VPC)



* 15 minutes
* 2023-04-26
For reliability, the primary and auxiliary storage volumes are local disks instead of storage area networking (SAN). Reliability benefits include higher throughput when serializing bytes to the local disk and reduced file system degradation due to network failures. The auxiliary disk is encrypted by default.
* VPC compute VMs: VPC VMs have one primary disk that is a block storage volume that is attached via the network. The storage layer is not separated from the other networking layers, and both network and storage traffic are routed on the same network. The primary storage disk is used for storing data such as the OS file system, container runtime, and kubelet, and is [encrypted by default](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-aboutvpc-storage-encryption).
* To prevent default pod evictions, 10% of the Kubernetes data disk (auxiliary disk in classic, primary boot disk in VPC) is reserved for system components.









 Available flavors for VMs 

The following table shows available worker node flavors for classic and VPC clusters. Worker node flavors vary by cluster type, the zone where you want to create the cluster, the container platform, and the infrastructure provider that you want to use. To see the flavors available in your zone, run ibmcloud oc flavors --zone <zone>.

To view a list of available VM flavors by zone, review the following pages.



* [Classic flavors](https://cloud.ibm.com/docs/openshift?topic=openshift-classic-flavors)
* [VPC Gen 2 flavors](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-flavors)*



* VPC: For more information about network performance caps for virtual machines, see [VPC profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-profiles). The network speeds refer to the speeds of the worker node network interfaces. The maximum speed available to your worker nodes is 25Gbps.
Bare Metal Servers for VPC versus bare metal server on classic infrastructure 

With Bare Metal Servers for VPC, you can enjoy the security and performance of the private cloud with the flexibility and scalability of the public cloud. Compared to the classic bare metal infrastructures, Bare Metal Servers for VPC provides better connectivity and networking throughput by using VPC concepts.

Bare Metal Servers for VPC has local NVMe, which you can use to create VMWare vSAN. For more information about file storage, see [About File Storage for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-about).



 Bare metal servers versus virtual server instances 

In general, you choose bare metal servers over virtual server instances if you need access to the actual hardware to run a hypervisor such as VMware's ESXi, or run real-time workloads.

Bare Metal Servers for VPC sets up a VMware virtualization environment in a VPC. Bare Metal Servers for VPC offers improved security compared to a virtual server instance as customers fully manage the physical resources of a bare metal server until it is decommissioned. By contrast, virtual server instances can share resources such as CPU, memory, and processes, across an IBM managed hypervisor.

Keep the following lifecycle operations differences in mind:



* For bare metal servers, you can restart, or power the server off and on. When you power off a server, the server is powered off physically, but the data on it is preserved, and you continue to be billed.
* For virtual server instances, you can restart, stop, and start the instance. But these functions don't impact the physical server status. Billing is suspended for some types of instances when powered off. However, any persistent storage continues to be billed. For more information about suspend billing, see [Suspend billing for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-suspend-billing).









 Next steps 

See to the following topics to start planning and creating your bare metal servers on VPC:
Deployment Journey Overview 

IBM Cloud® Virtual Private Cloud(VPC) allows you to establish your own virtual private cloud by defining a virtual network that is logically isolated from all other public cloud tenants. The underlying software defined networking (SDN) and virtual network functions allows you to quickly establish the network constructs and on-prem connectivity needed to run your workload. The information contained within this document is meant to serve as a technical guide for beginning with a new IBM Cloud Account and leading towards a fully configured VPC network environment.

Welcome to the Deployment Journey for VPC on IBM Cloud! Use the sidebar on the left to navigate between the journey points.



 Journey Map 

![Architecture](https://cloud.ibm.com/docs-content/v1/content/d50364af907081c3c38f99c11f35dd9cab4b2510/vpc-journey/images/overview/journey-map.png)





 Assumptions 

This deployment guide will be assuming the following points. Please note that while your circumstance may not be exactly identical, you will still benefit from the overall journey steps and concepts covered in this guide.



* You are already familar with the concepts introduced in the "Tour IBM Cloud" videos available on the [Getting Started with IBM Cloud](https://cloud.ibm.com/cloud/get-started) page.
* Access groups will need to be defined so only certain users have the ability to create and manage the VPC network settings (i.e. CIDR ranges, Subnet ACL rules, etc.,).
* You have a networking background and familar with concepts such as IP Addressing, subnets, routing, etc.,
* Focus will be on establishing the underlying network connectivity to support VPC based workloads.



* Note: A separate deployment guide will cover the compute resources which runs within the VPC like IBM Kubernetes Services (IKS), Red Hat OpenShift, IBM Code Engine, and VPC Virtual Server Instances (VSIs).
About Bare Metal Servers for VPC 

You can provision dedicated, Bare Metal Servers for VPC on your own software-defined, private cloud and deploy to multizone regions. A bare metal server is ideal for expanding capacity of applications that benefit from elastic, quick provisioning, and deprovisioning. Accelerate deployment with preset server profiles for your high-performance workloads.

You get the full suite of IBM Cloud VPC networking benefits, plus 4x faster networking throughput (up to 100 Gbps). Using a VPC for your dedicated, bare metal servers helps you isolate and provision network segments on the cloud, where you then can deploy and manage your compute, storage, and networking.



 Key features 

The following information lists the key features that are included with a bare metal server.



 Workload profiles 

You can choose different bare metal server profiles to match your individual workload needs and help accelerate deployment of your compute resources. You get maximum performance without oversubscribing. IBM Cloud VPC Infrastructure for bare metal servers provides profiles with or without secondary NVMe drives.



* Balanced profiles are ideal for common high-performance cloud workloads.
* Memory profiles are ideal for more memory intensive cloud workloads.



For more information, see [Profiles for Bare Metal Servers for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-bare-metal-servers-profile).





 Advanced Intel® Xeon® CPUs 

IBM Cloud Bare Metal Servers for VPC Infrastructure are deployed only with second Gen Intel® Xeon® Platinum 8260 processors that are built for cloud-enterprise applications, HPC workloads, IoT workloads, enhanced networking, and security.





 SmartNIC technology 

Get 4x faster network throughput up to 100 Gbps.







 Benefits 



 BYOL 

Renting licenses can get expensive. Bringing your own license is an option for IBM Cloud Bare Metal Servers for VPC.





 Rapid scaling 

Scale your dedicated, bare metal server environment for your needs quickly. Often, in 10 minutes or less when resources are available.





 Network orchestration 

A network orchestration layer handles the networking for all bare metal servers that are within an IBM Cloud VPC across regions and zones.
Using VPEs for VPC to privately connect to Container Registry 

You can use IBM Cloud® virtual private endpoints (VPE) for Virtual Private Cloud (VPC) to connect to IBM Cloud® Container Registry from your VPC network by using the IP addresses of your choice, which are allocated from a subnetwork within your VPC.

Any Container Registry VPE gateways that were created before 11 November 2022 are deprecated and must be replaced by 15 December 2022. For more information, see [Changes to Container Registry VPE gateways from 11 November 2022](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_notices_vpe&interface=ui).

VPEs are virtual IP interfaces that are bound to an endpoint gateway created on a per service, or service instance, basis (depending on the service operation model). The endpoint gateway is a virtualized function that scales horizontally, is redundant and highly available, and spans all

availability zonesof your VPC. Endpoint gateways enable communications from virtual server instances within your VPC and IBM Cloud service on the private backbone. VPE for VPC gives you the experience of controlling all the private addressing within your cloud. For more information, see [About virtual private endpoint gateways](https://cloud.ibm.com/docs/vpc?topic=vpc-about-vpe).

If you have an IBM Cloud VPC instance and want to connect the VPC instance to IBM Cloud Container Registry for your Container Registry services, you can create a VPE gateway for your VPC to access IBM Cloud Container Registry within your VPC network. Any connections to IBM Cloud Container Registry that originate from within the VPC automatically go through the Container Registry VPE gateway, if one exists. For more information, see [Getting started with Virtual Private Cloud](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started).

When you connect to Container Registry from the IBM Cloud console, you must go through a browser in your VPC to ensure that the connection goes through the Container Registry VPE gateway.
IBM Cloud VPC concepts and the networking constructs are explained in the [VPC pages of the IBM Cloud™ Docs](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started). More information about planning and deploying bare metal servers on VPC can be found in the [Bare metal server section of IBM Cloud VPC pages](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-for-bare-metal-servers).



 Objectives 



* Understand the Virtual Private Cloud infrastructure used for VMware vSphere deployment.
* Create a IBM Cloud VPC, subnets and bare metal server instances for a vSphere deployment.
* Manually deploy vCenter and create a compute cluster.
* Create shared storage for your compute cluster either by using vSAN or VPC file share (NFS).
* Use IBM Cloud VPC networking for your VMware Virtual Machines.



The following diagram presents an overview of the base deployment in IBM Cloud VPC. The deployment is based on IBM Cloud® Bare Metal Servers for Virtual Private Cloud and uses [subnets](https://cloud.ibm.com/docs/vpc?topic=vpc-about-networking-for-vpc) to host the servers' network interfaces and [access control lists and security groups](https://cloud.ibm.com/docs/vpc?topic=vpc-security-in-your-vpc) to secure the network access. VMware vSAN with local ESXi host embedded SSDs or IBM Cloud VPC file share are the storage options for datastores to be used for VMware Virtual Machines. IBM Cloud VPC subnets can also be used to host network interfaces of VMware Virtual machines. Alternatively NSX-T can be used for Virtual Machines, but this is not mandatory.

Zoom

!
* IBM Cloud Direct Link, which meets use case 4 by providing the ability to attach your remote networks (on-premises) to your virtual networks within IBM Cloud VPC or IBM Cloud classic via this same private backbone.



By default, a VPC is private, and remains private until it is configured to enable public connectivity. For instance, a VPC might be connected to a public gateway or associated with floating IPs.



 Architecture 



 Single-region, multi-zone VPC virtual network 

Zoom

![Architecture of a single-region, multi-zone VPC virtual network](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/vpc/images/private-network-connectivity.png)

Figure 1. Architecture of a single region, multi-zone VPC virtual network





 Multi-region, multi-zone VPC virtual networks 

Zoom

![Architecture of multi-region, multi-zone VPC virtual networks](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/vpc/images/private-network-connectivity2.png)

Figure 2. Architecture of multi-region, multi-zone VPC virtual networks





 Connection from a remote network (on-premises) to IBM Cloud 

Zoom

![Direct Link on-premises interconnect use case](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/vpc/images/direct-link-dedicated.png)

Figure 3. Direct Link on-premises interconnect use case
Using a virtual private endpoint 

After you created your VPC and you want to connect to Key Protect service for your data encryption needs, you can create a virtual private endpoint in your VPC to access Key Protect service within your VPC network.

You can configure the VPE to use the IP addresses of your choice, which are allocated from a subnet within your VPC. VPEs are bound to a [VPE gateway](https://cloud.ibm.com/docs/vpc?topic=vpc-about-vpe) and serve as an intermediary that enables your workload to interact with Key Protect.

To connect to Key Protect by using a virtual private endpoint, you must use the Key Protect API, SDK, or Terraform. The Key Protect UI has to be accessed through public network from your VPC.



 Before you begin 

Before you target a virtual private endpoint for Key Protect:



* Ensure that you have [provisioned a Virtual Private Cloud](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started).
* Ensure that you have conducted [planning for Virtual Private Endpoints](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-considerations).
* Ensure that [correct access controls](https://cloud.ibm.com/docs/vpc?topic=vpc-vpe-configuring-acls) are set for your virtual private endpoint.
* Understand the [limitations](https://cloud.ibm.com/docs/vpc?topic=vpc-limitations-vpe) of having a virtual private endpoint.
* Ensure that you have [created](https://cloud.ibm.com/docs/vpc?topic=vpc-ordering-endpoint-gateway) and understand how to [access](https://cloud.ibm.com/docs/vpc?topic=vpc-accessing-vpe-after-setup) a VPE gateway.
Getting started with IBM Cloud Virtual Private Networking 

Virtual Private Networking (VPN) access enables users to manage all servers remotely and securely over the IBM Cloud® private network. A VPN connection from your location to the private network allows out-of-band management and server rescue through an encrypted VPN tunnel. VPN tunnels can be initiated to any IBM Cloud data center or PoP allowing you geographic redundancy.

With VPN access, you can:



* Establish a VPN connection to the private network via SSL, or IPsec.
* Access your server through its primary private IP address by SSH or RDP.
* Connect to your server’s IPMI IP address for low-level server management or rescue needs.



A number of services require access through the private network, and VPN is one method that allows private network access. A VPN is good to use when you need to log in to the private network, do your work, and then log out. For example, this access often is needed to reach the KVM of the server.

Each user on an account can be given VPN access and can be limited regarding the subnets to which it needs access. The account user must have VPN access enabled and a VPN password specified before attempting to log in to VPN services.

SSL VPN is a shared VPN service, which is free of charge. It is not recommended for production use.



 Use case scenarios 



Table 1: Recommended VPN options

 If you plan to: Recommended VPN option: 

 Access your server on classic through its private IP address (10.x.x.x) by SSH or RDP for a short duration <br>Perform low-level server management with the KVM console of your classic server <br>Apply critical security updates to your server with public interface shut down <br>Establish a single person, short-lived, private network connection for occasional server and application management SSL VPN 
 Manage multiple servers for development or test workloads on classic through an encrypted VPN tunnel <br>Transfer large files regularly among different servers <br>Establish a long-lived network path for managing servers and the customer-deployed applications they host IPsec VPN
The deployment is based on IBM Cloud® Bare Metal Servers for Virtual Private Cloud and uses [subnets](https://cloud.ibm.com/docs/vpc?topic=vpc-about-networking-for-vpc) to host the servers' network interfaces and [access control lists and security groups](https://cloud.ibm.com/docs/vpc?topic=vpc-security-in-your-vpc) to secure the network access. VMware vSAN with local ESXi host embedded SSDs or IBM Cloud VPC file share are the storage options for datastores to be used for VMware Virtual Machines. IBM Cloud VPC subnets can also be used to host network interfaces of VMware Virtual machines. Alternatively NSX-T can be used for Virtual Machines, but this is not mandatory.

Zoom

![Architecture Overview - Base Deployment](https://cloud.ibm.com/docs-content/v1/content/f84e2238288b7f0355715a4c355609ce7ac48fb0/solution-tutorials/images/solution63-ryo-vmware-on-vpc/Self-Managed-Simple-20210813v1-Non-NSX-based.svg)

Figure 1. Architecture Overview - Base Deployment

You need to plan and decide your IBM Cloud VPC networking solution for the VMware deployment before you start. This tutorial provides a simple example where a fully dedicated IBM Cloud® Virtual Private Cloud is created for the VMware deployment, but you may customise your network solution if you so wish. You may also use [IBM Cloud interconnectivity](https://cloud.ibm.com/docs/vpc?topic=vpc-interconnectivity) options. These are recommended for enterprise connectivity use cases.

You need to plan and decide your VMware deployments storage solution before you order the bare metal servers.