vania-janet/multiturn-rag-retrieval-data huggingface dataset:
The row headers provide the platform role name and the column headers identify the specific information available about each role.

 Role Description 

 Administrator As a Virtual Network Interface administrator, you can Read, List, Attach, Detach, Create, Update, and Delete Virtual Network resources on the account and provide policies to other users on the account. 
 Editor As a Virtual Network Interface editor, you can Read, List, Attach, Detach, Create, Update, and Delete Virtual Network resources. 
 Operator As a Virtual Network Interface operator, you can Read, List, Attach, and Detach Virtual Network resources. 
 Viewer As a Virtual Network Interface viewer, you can Read, and List Virtual Network resources. 







 Block Storage for VPC 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use is.volume for the service name.

Platform roles

Actions



Table 101. Platform roles - Block Storage for VPC
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the platform role name and the column headers identify the specific information available about each role.

 Role Description 

 Administrator As an administrator, you can perform all platform actions based on the resource this role is being assigned, including assigning access policies to other users. 
 Editor As an editor, you can perform all platform actions except for managing the account and assigning access policies. 
 Operator As an operator, you can perform platform actions required to configure and operate service instances, such as viewing a service's dashboard. 
 Viewer As a viewer, you can view service instances, but you can't modify them. 







 Virtual Private Cloud 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use is.vpc for the service name.

Platform roles

Actions



Table 102. Platform roles - Virtual Private Cloud
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the platform role name and the column headers identify the specific information available about each role.
virtual server 

A server that shares its resources with other servers to support applications. See also [virtual machine](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx2043165).





 VLAN 

See [virtual local area network](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx2438470).





 VM 

See [virtual machine](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx2043165).





 volume 

A fixed amount of physical or virtual storage on a data storage medium.





 VPC 

See [virtual private cloud](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx4585403).





 VPN 

See [virtual private network](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx2043188).





 VPN as a service 

A private connection between two endpoints, which remains private and can be encrypted even when the data is transferred across a public network.







 W 



 WAR 

See [web archive](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx2116506).





 WAR file 

See [web archive](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx2116506).





 web app 

See [web application](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx2116500).





 web application (web app) 

An application that is accessible by a web browser and that provides some function beyond static display of information, for instance by allowing the user to query a database. Common components of a web application include HTML pages, JSP pages, and servlets. See also [app](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx4281528).





 web archive (WAR)
Gateway routing Use a virtual or physical network appliance (Virtual Router Appliance, Vyatta, Juniper vSRX, Fortinet FSA) Traffic routing is handled by public gateway and floating IP services 
 Network address translation (NAT) Use a virtual or physical network appliance (Virtual Router Appliance, Vyatta, Juniper vSRX, Fortinet FSA) Supported by the Bring-your-own-IP (BYOIP) functionality 
 IPsec Virtual private network (VPN) Use a virtual or physical network appliance (Virtual Router Appliance, Vyatta, Juniper vSRX, Fortinet FSA) Supported by the VPN-as-a-service offering 
 Elastic load balancing Cloud Load Balancer Load Balancer for VPC 
 Global load balancing Cloud Internet Services, Citrix Netscaler MPX Cloud Internet Services 
 Hybrid connectivity NAT solution to bridge between IBM Cloud and your IT environment Bring your own private IP address without NAT or IPSec tunnels <br>Note: You can enable your VPC to access classic infrastructure resources. 







 Storage differentiators 

See the following table for the storage differences between classic and VPC.



Table 3. Storage comparison

 Classic infrastructure VPC infrastructure 

 Robust set of storage services, block storage (iSCSI), and file storage (NFS-based) offerings Block storage as primary boot disk (with basic lifecycle management), and secondary data volumes <br>Note: Volume encryption is available during provisioning. 







 Security differentiators 

See the following table for the security differences between classic and VPC.



Table 4. Security comparison

 Classic infrastructure VPC infrastructure 

 Vyatta, Fortigate, Juniper vSRX, Security Groups for virtual servers Security groups, Network access control lists (ACLs) 







 API differentiators 

See the following table for the API differences between classic and VPC.



Table 5. API comparison

 Classic infrastructure VPC infrastructure 

 Existing SoftLayer API (SLAPI) New developer-friendly, REST-based API 







 Next steps 

To review all our VPC infrastructure capabilities, see [About virtual private cloud](https://cloud.ibm.com/docs/vpc?topic=vpc-about-vpc).
VNF limitations 

High Availability (HA) Virtual Network Function (VNF) deployments have the following known limitations.



*  The Virtual Network Function (VNF) must share one subnet with the Network Load Balancer (NLB).
*  Routing public internet "ingress" traffic to a VNF is not supported.
*  Auto-scaling with the VNF is not supported.
Pricing Hourly and monthly billing, plus suspend billing features Hourly, suspend billing, and sustained usage discount 
 Virtual server families Public, dedicated, transient, reserved Public, dedicated 
 Profiles All profiles, including the GPU profiles Balanced, compute, memory profiles with higher RAM and vCPU options 
 Supported images Full set of pre-stock images, plus custom images Limited set of pre-stock images, plus the ability to import a custom image 
 Platform integration IAM and resource group integration for a unified experience 



Suspend billing supports only hourly, SAN instances that are provisioned with a public profile from one of the Balanced, Compute, Memory, or Variable compute families.





 Network differentiators 

See the following table for the networking differences between classic and VPC.



Table 2. Network comparison
This table has row and column headers. The row headers identify possible features. The column headers identify the differentiators between classic infrastructure and VPC infrastructure. To understand the differences between environments, navigate to the row and find the details for the feature that you're interested in.

 Category Classic infrastructure VPC infrastructure 

 Location construct Data centers and PODs <br>(Might require VLAN spanning to connect two different pods or data centers, and purchasing gateways to control and route traffic) Regional model that abstracts infrastructure so you don't need to worry about pod locations. 
 Network functions and services Physical and virtual appliances from multiple vendors Cloud-native network functions (VPNs, LBaaS) <br>(VPC isolation, dedicated resources carved out of public cloud, with more options for VPNs, LBaaS, multiple vNIC instances, and larger subnet sizes) 
 IP addresses IPv6 addresses supported IPv4 addresses only 
 Gateway routing Use a virtual or physical network appliance (Virtual Router Appliance, Vyatta, Juniper vSRX, Fortinet FSA) Traffic routing is handled by public gateway and floating IP services 
 Network address translation (NAT) Use a virtual or physical network appliance (Virtual Router Appliance, Vyatta, Juniper vSRX, Fortinet FSA) Supported by the Bring-your-own-IP (BYOIP) functionality
Related material 



1. Virtual Routing and Forwarding (VRF) is an alternative to the use of VLAN Spanning to connect networks across an IBM Cloud Account. VRF is mandatory for all clients using [IBM Cloud® Direct Link](https://cloud.ibm.com/docs/direct-link?topic=direct-link-overview-of-virtual-routing-and-forwarding-vrf-on-ibm-cloud). [Overview of Virtual Routing and Forwarding (VRF) on IBM Cloud](https://cloud.ibm.com/docs/direct-link?topic=direct-link-overview-of-virtual-routing-and-forwarding-vrf-on-ibm-cloud)
2. [The IBM Cloud network](https://www.ibm.com/cloud/data-centers/)
Virtual routing and forwarding on IBM Cloud 

By definition, virtual routing and forwarding (VRF) is a technology that is included in IP network routers. It is delivered as an inherent backbone service.



 Connectivity options for IBM Cloud 

Dispersed cloud resources are resources in more than one location or in more than one subnet or VLAN. These types of resources require a routing function to communicate among themselves, even within a private network context. This document describes a "multiple isolation" tenancy communication option, which often is called a customer VRF. It is implemented as an MPLS Layer-3 VPN (RFC 4364) across the global IBM Cloud® backbone.

In general, the IBM Cloud platform offers two options for routing across our private network, providing connectivity across pods and data centers:



1. Multiple isolation: A dedicated logical network per tenant, which allows no interaction with other tenants’ logical networks.
2. Shared tenancy: A common logical network, which is shared by all tenants who use this model, with separation provided by automated Access Control Lists (ACLs), and enabled with VLAN spanning. This option is not described in this document.



The term "customer VRF" is used to describe multiple isolation network connectivity.





 VRF overview: Multiple isolation technology 

VRF allows multiple instances of a routing table to exist in a router and to work simultaneously. With VRF, each cloud tenant's VRF network is segmented within its routing table. This segmentation allows for IP address overlaps, and it doesn’t create any interaction or interference with other tenant VRFs. IBM Cloud uses a large majority of the 10.0.0.0/8 network, which might overlap with many remote networks, for example networks deployed at customer data centers.

Using VRF, IBM Cloud tenants are allowed to use remote IP addresses that normally would not be allowed to overlap in the Global table. When accessing VPC only, IBM still reserves the following RFC 1918, link-local addresses, and multicast addresses, which are not routable from this VRF service:



* 169.254.0.0/16
* 224.0.0.0/4
* 166.9.0.0/16 ( used by the private endpoint service)
Compute services 

Your server is the base of your infrastructure. Depending on your needs, you have various options, or you can mix it up if that's what your environment requires. Check out the following table for a summary of your compute options.



 Virtual servers 



Table 1. Compute options - Virtual Servers

 Option Description 

 [Virtual Servers for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-about-advanced-virtual-servers) Scalable virtual servers for VPC that are purchased with cores and memory allocations. 
 [Hyper Protect Virtual Servers](https://cloud.ibm.com/docs/hp-virtual-servers?topic=hp-virtual-servers-getting-started) Hyper Protect Virtual Servers is an IBM Cloud™ service that provides highly secure virtual servers that can run Linux applications and containerized workloads. 
 [Power Systems Virtual Server](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-getting-started) A Power Systems Virtual Server integrates your AIX and IBM i capabilities into the IBM Cloud™ experience. 







 VPC infrastructure 



Table 2. Compute options - VPC

 Option Description 

 [Virtual Servers for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-about-advanced-virtual-servers) Scalable virtual servers for VPC that are purchased with cores and memory allocations. 







 Classic infrastructure 



Table 3. Compute options - Classic

 Option Description 

 [Bare Metal Servers](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-about-bmabout-bm) Hourly or monthly, single-tenant servers that are dedicated to you and not shared in any part, including server resources, with other customers. 
 [Virtual Servers](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-getting-started-tutorial) Scalable virtual servers that are purchased with cores and memory allocations.
How Cloud Functions works 

IBM Cloud® Functions service is an event-driven compute platform, also referred to as Serverless computing, or as Function as a Service (FaaS), that runs code in response to events or direct invocations.



 Cloud Functions terminology 

Learn the basic concepts of the technology behind Cloud Functions. Then, test your knowledge and [!take a quiz](https://quizzes.12dekrh4l1b4.us-south.codeengine.appdomain.cloud/functions/terms_quiz/quiz.php)



Table 1. Cloud Functions Terms

 Term Description 

 Namespace [Namespaces](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-namespaces) contain Cloud Functions entities, such as actions and triggers, and belong to a resource group. You can let users access your Cloud Functions entities by granting them access to the namespace. 
 Action An [action](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-actions) is a piece of code that performs one specific task. An action can be written in the language of your choice, such as small snippets of JavaScript or Swift code or custom binary code embedded in a Docker container. You provide your action to Cloud Functions either as source code or a Docker image. An action performs work when it is directly invoked by using the Cloud Functions API, CLI, or iOS SDK. An action can also automatically respond to events from IBM Cloud services and third-party services by using a trigger. 
 Sequence A set of actions can be chained together into a [sequence](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-sequences) without having to write any code. A sequence is a chain of actions, invoked in order, where the output of one action is passed as input to the next action. By creating a sequence, you can combine existing actions together for quick and easy reuse. A sequence can then be invoked just like an action, through a REST API or automatically in response to events.
Virtual routing and forwarding on IBM Cloud 

By definition, virtual routing and forwarding (VRF) is a technology that is included in IP network routers. It is delivered as an inherent backbone service.



 Connectivity options for IBM Cloud 

Dispersed cloud resources are resources in more than one location or in more than one subnet or VLAN. These types of resources require a routing function to communicate among themselves, even within a private network context. This document describes a "multiple isolation" tenancy communication option, which is often called a customer VRF. It is implemented as an MPLS Layer-3 VPN (RFC 4364) across the global IBM Cloud® backbone.

In general, the IBM Cloud platform offers two options for routing across our private network, providing connectivity across pods and data centers:



1. Multiple isolation: A dedicated logical network per tenant, which allows no interaction with other tenants’ logical networks.
2. Shared tenancy: A common logical network, which is shared by all tenants who use this model, with separation provided by automated Access Control Lists (ACLs), and enabled with VLAN spanning. This option is not described in this document.



The term "customer VRF" is used to describe multiple isolation network connectivity.





 VRF overview: Multiple isolation technology 

VRF allows multiple instances of a routing table to exist in a router and to work simultaneously. With VRF, each cloud tenant's VRF network is segmented within its routing table. This segmentation allows for IP address overlaps, and it doesn’t create any interaction or interference with other tenant VRFs. IBM Cloud uses a large majority of the 10.0.0.0/8 network, which might overlap with many remote networks, for example networks deployed at customer data centers.

Using VRF, IBM Cloud tenants are allowed to use remote IP addresses that normally would not be allowed to overlap in the Global table. IBM still reserves the following RFC 1918, link-local addresses, and multicast addresses, which are not routable from this VRF service:



* 10.0.0.0/14
* 10.200.0.0/14
* 10.198.0.0/15
* 169.254.0.0/16
VMware vSphere NSX overview 

VMware NSX® is a software networking and security virtualization platform that delivers the operational model of a virtual machine for the network. Virtual networks reproduce the Layer2 - Layer7 network model in software, allowing complex multitier network topologies to be created and provisioned programmatically in seconds, without the need for extra IBM Cloud private networks. NSX also provides a new model for network security. Security profiles are distributed to and enforced by virtual ports and move with virtual machines.

NSX supports the VMware software-defined data center strategy. By extending the virtualization capabilities of abstraction, pooling and automation across all data center resources and services, the software-defined data center architecture simplifies and speeds the provisioning and management of compute, storage, and networking resources through policy-driven automation. By virtualizing the network, NSX delivers a new operational model for networking that breaks through current physical network barriers and enables VMware and IBM Cloud to achieve better speed and agility with reduced costs.

NSX includes a library of logical networking services - logical switches, logical routers, logical firewalls, logical load balancers, logical VPN, and distributed security. You can create custom combinations of these services in isolated software-based virtual networks that support existing applications without modification, or deliver unique requirements for new application workloads. Virtual networks are programmatically provisioned and managed independent of IBM Cloud networking constructs. This decoupling from hardware introduces agility, speed, and operational efficiency that can transform data center operations. Benefits of NSX include the following features:



* Data center automation
* Self-service networking services
* Rapid application deployment with automated network and service provisioning
* Isolation of development, test, and production environments on the same bare metal infrastructure
* Single Account multi-tenant clouds



NSX can be configured through the vSphere Web Client, a command line interface (CLI), and REST API. The core network services that are offered by NSX are:



 Logical switches 

A cloud deployment or a virtual data center might have various applications across multiple tenants. These applications and tenants require isolation from each other for security, fault isolation, and avoiding overlapping IP addressing issues.
Service Router Provides gateway services<br><br><br><br> * NAT<br> * Load Balancer<br> * Gateway firewall<br> * North-south routing<br> * VPN<br> * DNS Forwarding<br> * DHCP<br><br><br> 



Some key NSX-T concepts do not correspond to NSX-V functions. You need to review the following concepts so you can understand the NSX-T design implementation.



* A gateway cluster is one or more VMs or physical machines that participate in an NSX-T virtual fabric. They are endpoints for the overlay network transport zones and VLAN backed transport zones. A gateway cluster can support a single T0 gateway instance.
* A T0 gateway is a virtual router instance, but not a VM. Multiple T0 gateway instances can run within a gateway cluster each with its own routing table and functions. A gateway cluster must exist before you can create a T0 router instance.
* A transport zone can span endpoints across different platforms and multiple vSphere vCenter instances. No cross-vCenter linked NSX is required. Transport zones can be excluded from specific endpoints.
* Uplink failover order is created independent of a particular logical switch as they are created in profiles as “Uplink Profiles” and are applied to a particular logical switch based on VLAN. It's possible to need a differing failover order or load balancing of physical uplinks for the same VLAN. Therefore, the uplink profile for a particular VLAN can contain multiple entries for “Teaming” with different a failover order and load balancing. When you assign the uplink profile to a logical switch, the specific teaming profile is chosen.
* The manager VM and the controller VM function are combined, which results in three NSX-T manager VMs being deployed. If on the same subnet, they use an internal network load balancer. If across different subnets, an external load balancer is required.







 Resource requirements 

In this design, the NSX-T controller Manager VMs are deployed on the management cluster.
VMware as a Service overview 

IBM Cloud® for VMware as a Service provides the VMware Cloud Director™ platform as a managed service. IBM® performs the configuration, hosting, operations, and lifecycle management of the VMware® software so you can quickly deploy your VMware-based cloud computing environments.

Compute resources are available as dedicated hosts, by using IBM Cloud bare metal servers, with multiple host configurations available to address various workload requirements.

Zoom

![VMware as a Service architecture](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/includes/vmware-service/common/includes/vmware-service/images/vmware-aas-archi.svg)

Figure 1. VMware as a Service architecture



 VMware as a Service features and functions 

The VMware as a Service offering has the following features:



* VMware stack management up to the hypervisor level



* IBM-managed infrastructure
* IBM-managed VMware components and services



* Dedicated hosts and multiple host profiles for creating VMware vCenter clusters
* Multiple performance options for attached vSAN™ and Network File Storage (NFS v3)
* Optional data protection through the Veeam® Backup and Replication service
* Monthly billing
* Unique provider-managed encryption keys per instance with encrypted VMware storage profiles
* Single sign-on (SSO) with role-based authentication and authorization from IBM Cloud IAM (Identity and Access Management) to VMware Cloud Director
* Improved provisioning speed, availability, and resilience
* Regional-level High Availability through creating VMware Cloud Director provider virtual data centers (PVDCs) and vCenter clusters in multiple data centers in the same region.
* Full compatibility to run existing VMware workloads. Migration of existing IBM Cloud, on-premises or other workloads are fully supported.
* Each VMware as a Service instance contains the following VMware components:



* Dedicated VMware ESXi™ hosts