vania-janet/multiturn-rag-retrieval-data huggingface dataset:
: Red Hat OpenShift [4.3.29_1532_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4329_1532) and [3.11.232_1558_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311232_1558).





 16 July 2020 

Ingress ALB change log
: Updated the [nginx-ingress image build to 645 and the ingress-auth image build to 420](https://cloud.ibm.com/docs/containers?topic=containers-cluster-add-ons-changelogkube_ingress_changelog).

Pod and service subnets
: Added information about bringing your own pod and service subnets in [VPC clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-subnetsbasics_subnets) classic or (/docs/openshift?topic=openshift-vpc-subnetsvpc_basics_subnets).





 7 July 2020 

CLI change log
: Updated the Red Hat OpenShift on IBM Cloud CLI plug-in change log page for the [release of version 1.0.118](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_cli_changelog10).





 6 July 2020 

Version change logs
: Worker node fix pack update change log documentation is available.
: Red Hat OpenShift [4.3.27_1528_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4327_1528) and [3.11.232_1555_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311232_1555).





 2 July 2020 

Comparison between IBM Cloud and OCP clusters
: Red Hat OpenShift [4.10.20_1525_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_410),[4.9.40_1545_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_49), [4.8.45_1561_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_48), [4.7.53_1570_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_47), and [4.6.59_1589_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_46).







 June 2022 



 30 June 2022 

Cluster autoscaler add-on
: Versions 1.0.5_694 and 1.1.0_682 are available. See [Cluster autoscaler add-on change log](https://cloud.ibm.com/docs/openshift?topic=openshift-ca_changelog).





 28 June 2022 

IBM Cloud Object Storage plug-in
: Version 2.1.17 of the IBM Cloud Object Storage plug-in [is available](https://cloud.ibm.com/docs/openshift?topic=openshift-cos_plugin_changelog).





 27 June 2022 

Block Storage for VPC
: You can now [set up the Block Storage for VPC add-on with Cloud Identity and Access Management trusted profiles](https://cloud.ibm.com/docs/openshift?topic=openshift-storage-block-vpc-trusted-profiles).





 24 June 2022 

Block Storage for VPC
Key Management Service provider v2.3.8 v2.3.10 Updated Go module dependencies and to use Go version 1.16.9. Updated image for [CVE-2021-22946](https://nvd.nist.gov/vuln/detail/CVE-2021-22946). 
 Load balancer and load balancer monitor for IBM Cloud Provider 1547 1590 Updated to use Go version 1.16.9. 
 Red Hat OpenShift 4.8.14 4.8.18 See the [Red Hat OpenShift release notes](https://docs.openshift.com/container-platform/4.8/release_notes/ocp-4-8-release-notes.htmlocp-4-8-18). Changed the duration of the Kubernetes API server certificate from 825 days to 365 days. Changed the duration of the cluster CA certificate from 30 to 10 years. 
 Red Hat OpenShift Control Plane Operator v4.8.0-20211004 v4.8.0-20211109 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.8.0+20211109). 
 OpenVPN client 2.4.6-r3-IKS-386 2.4.6-r3-IKS-463 Updated image to implement additional IBM security controls. 
 OpenVPN server 2.4.6-r3-IKS-385 2.4.6-r3-IKS-462 Updated image to implement additional IBM security controls. 
 OpenVPN Operator image v1.3.7 v1.3.8 Updated ansible operator base image to version v1.13.1 to resolve CVEs.
OpenVPN server 2.5.6-r1-IKS-628 2.5.6-r1-IKS-647 Update image for [CVE-2022-2097](https://nvd.nist.gov/vuln/detail/CVE-2022-2097) and [CVE-2022-37434](https://nvd.nist.gov/vuln/detail/CVE-2022-37434). 
 Pause container image 3.7 3.8 See the [pause container image release notes](https://github.com/kubernetes/kubernetes/blob/master/build/pause/CHANGELOG.md). 
 Portieris admission controller v0.12.5 v0.12.6 See the [Portieris admission controller release notes](https://github.com/IBM/portieris/releases/tag/v0.12.6) 
 Red Hat OpenShift configuration N/A N/A Updated the [feature gate configuration](https://cloud.ibm.com/docs/openshift?topic=openshift-service-settingsfeature-gates) 
 Red Hat OpenShift Control Plane Operator v4.10.0-20220712 v4.11.0-20220824 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.11.0+20220824). 
 Red Hat OpenShift on IBM Cloud Metrics Server v4.10.0-20220712 v4.11.0-20220824 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.11.0+20220824).
}

Example payload to add multiple services, IP addresses, and VPCs to a network zone.

{
"name": "zone",
"description": "",
"addresses": [
{
"type": "ipAddress",
"value": "192.168.0.0"
},
{
"type": "vpc",
"value": "crn:v1:bluemix:public:is:us-east:a/CRN"
},
{
"type": "vpc",
"value": "crn:v1:bluemix:public:is:us-south:a/CRN"
},
{
"type": "serviceRef",
"ref": {
"service_name": "cloud-object-storage",
"account_id": "ACCOUNT-ID"
}
},
{
"type": "serviceRef",
"ref": {
"service_name": "codeengine",
"account_id": "ACCOUNT-ID"
}
},
{
"type": "serviceRef",
"ref": {
"service_name": "containers-kubernetes",
"account_id": "ACCOUNT-ID"
}
},
{
"type": "serviceRef",
"ref": {
"service_type": "platform_service",
"account_id": "ACCOUNT-ID"
}
},
{
"type": "serviceRef",
"ref": {
"service_name": "iam-groups",
"account_id": "ACCOUNT-ID"
}
}
],
"excluded": []
}





 Creating network zones from the CLI 



1.
Listing network interfaces of server 02b7-02890a7a-e543-4479-92d5-a9d7d5819286 under account IBM Cloud Acc as user xxx@yyy.com...
ID Name Status Type Address Floating IP Interface Type MAC address Allowed VLANs VLAN ID
02b7-ba818812-d5a6-4622-9ea5-c5088a60d724 pci-nic-vmnic0 available primary 10.97.0.6 pci 02:00:03:21:ED:95 100, 200, 300, 400, 500, 1000 -
02b7-94073d6d-6658-4b91-b4e1-b15a15fdbf4d vlan-nic-vsan-vmk2 available secondary 10.97.2.6 vlan 02:00:03:21:ED:98 - 300
02b7-97c2c802-a236-41c7-b6ca-bd9f0145cba2 vlan-nic-vmotion-vmk1 available secondary 10.97.1.5 vlan 02:00:02:21:ED:97 - 200
02b7-159f23b6-67e1-4aca-a4b8-36fede3b8fc7 vlan-nic-vcenter available secondary 10.97.0.132 vlan 02:00:01:22:01:2B - 100
02b7-9d8a9d99-c11a-4573-ad69-737f8878387e vlan-nic-vm-1 available secondary 192.168.0.4 vlan 02:00:01:22:6B:AC - 1000

You should be able to access ping / access other Virtual Machines on the same IBM Cloud VPC subnet from the provisioned Virtual Machine.
Managing access for virtual private endpoints 

Virtual private endpoint gateways use IBM Cloud Identity and Access Management (IAM) platform access roles to manage access to the service's resources. IAM access roles allow account administrators to assign different levels of permission for calling the service's APIs and accessing the UI.

The following table provides example actions that you can take against the VPE service and its resources, depending on the user's assigned roles.



 Platform-access roles 

VPE supports Administrator, Editor, Operator, and Viewer platform-access roles. The following table describes IAM authorization actions for VPEs.



Table 1. IAM platform-access user role and actions

 Role Description of Actions Example Actions 

 Administrator All Operator actions, plus actions that modify the state of an endpoint gateway, such as create, delete, and update. <br><br> * List all endpoint gateways.<br> * List a specific endpoint gateway and view its details.<br> * Create an endpoint gateway and bind a reserved IP to it.[1]<br> * Update the name of an existing endpoint gateway.<br> * Delete an endpoint gateway and unbind its reserved IP address.<br> * Bind a reserved IP address to an endpoint gateway.[2]<br><br><br> 
 Editor All Operator actions, plus actions that modify the state of an endpoint gateway, such as create, delete, and update. <br><br> * List all endpoint gateways.<br> * List a specific endpoint gateway and view its details.<br> * Create an endpoint gateway and bind a reserved IP to it.[3]<br> * Update the name of an existing endpoint gateway.<br> * Delete an endpoint gateway and unbind its reserved IP address.<br> * Bind a reserved IP address to an endpoint gateway.[4]<br><br><br> 
 Operator All Viewer actions, plus the action to bind a reserved IP to an endpoint gateway.
If your VMware Virtual Machines on the VM subnet ($SUBNET_VM1) need outbound internet access, a Public Gateway is needed. A Public Gateway enables a subnet and all its attached virtual or Bare Metal Servers for VPC instances to connect to the internet. After a subnet is attached to the Public Gateway, all instances in that subnet can connect to the internet. Public Gateways use Many-to-1 SNAT.



1. As you already provisioned a Public Gateway ($PUBLIC_GW) in the previous step for this IBM Cloud VPC Zone, you only need to attach that to the VM subnet ($SUBNET_VM1).

ibmcloud is subnetu $VMWARE_SUBNET_VM1 --public-gateway-id $VMWARE_PUBLIC_GW
2. After you have attached your newly created subnet to public gateway, you should be able access Internet from the VM, e.g.:

ping 1.1.1.1

To control outbound Internet access from your virtual machines, you can use security groups or access control lists. In this example, the default security group allows all outbound Internet access.







 Step 2: Establish Inbound Internet Access with Floating IP 

If you want to access the VMware Virtual Machines directly from the Internet, you need to provision a Floating IP to the VLAN NIC. Floating IP addresses are IP addresses that are provided by IBM Cloud platform and are reachable from the public Internet. You can reserve a Floating IP address from the pool of available addresses that are provided by IBM, and you can associate it with a network interface of your server, and VLAN NIC in this case. That VLAN NIC will keep its private IP address, and the Floating IP provides a One-to-One NAT to this private IP. Note that, associating a floating IP address with an instance removes the instance from the public gateway's Many-to-1 SNAT.



1. Create a floating IP for the First Virtual Machines (VM1) VLAN NIC and record the IP.
<br><br> * List all endpoint gateways.<br> * List a specific endpoint gateway and view its details.<br> * Create an endpoint gateway and bind a reserved IP to it.[3]<br> * Update the name of an existing endpoint gateway.<br> * Delete an endpoint gateway and unbind its reserved IP address.<br> * Bind a reserved IP address to an endpoint gateway.[4]<br><br><br> 
 Operator All Viewer actions, plus the action to bind a reserved IP to an endpoint gateway. <br><br> * List all endpoint gateways.<br> * List a specific endpoint gateway and view its details.<br> * Bind a reserved IP address to an endpoint gateway.[5]<br><br><br> 
 Viewer Performs actions that don't change the state of the endpoint gateway. <br><br> * List all endpoint gateways.<br> * List a specific endpoint gateway and view its details.<br><br><br> 



For information about assigning user roles in the console, see [Managing access to resources](https://cloud.ibm.com/docs/account?topic=account-assign-access-resources).





 Viewing VPE resources in the Resource list 

To view VPE resources in the IBM Cloud resource list, users need an IAM policy for the VPE service. VPE resource-type specific policies aren't sufficient.
* [IBM Virtual Router Appliance](https://cloud.ibm.com/docs/virtual-router-appliance?topic=virtual-router-appliance-accessing-and-configuring-the-ibm-virtual-router-appliance)
* [Static and Portable IP Subnets](https://cloud.ibm.com/docs/subnets?topic=subnets-about-subnets-and-ipsabout-subnets-and-ips)
* [IBM QRadar Security Intelligence Platform](https://www.ibm.com/docs/en/qsip)
* [Vyatta documentation](https://cloud.ibm.com/docs/virtual-router-appliance?topic=virtual-router-appliance-supplemental-vra-documentationsupplemental-vra-documentation)
Administrator crn:v1:bluemix:public:iam::::role:Administrator 
 Reader crn:v1:bluemix:public:iam::::serviceRole:Reader 
 Writer crn:v1:bluemix:public:iam::::serviceRole:Writer 
 Manager crn:v1:bluemix:public:iam::::serviceRole:Manager 
 VPNClient crn:v1:bluemix:public:iam::::serviceRole:VPNClient 
 Bare Metal Advanced Network Operator crn:v1:bluemix:public:iam::::serviceRole:BareMetalAdvancedNetworkOperator 
 Bare Metal Console Admin crn:v1:bluemix:public:iam::::serviceRole:BareMetalConsoleAdmin 
 IP Spoofing Operator crn:v1:bluemix:public:iam::::serviceRole:IPSpoofingOperator 
 Console Administrator crn:v1:bluemix:public:iam::::serviceRole:VirtualServerConsoleAdmin 



The following example is for assigning the Viewer role for VPC Infrastructure Services:

Use is for the service name and refer to the Role ID values table to make sure that you're using the correct value for the CRN.



* Curl
* Java
* Python
* Go
* Node



curl -X POST 'https://iam.cloud.ibm.com/v1/policies' -H 'Authorization: Bearer $TOKEN' -H 'Content-Type: application/json' -d '{
"type": "access",
"description": "Object Writer role for Cloud Object Storage",
"subjects": [
{
"attributes":
{
"name": "iam_id",
"value": "IBMid-123453user"
}
]
}'
],
"roles":[
{
When the provisioning process is complete, the new VRA appears in the Gateway Appliances list page. Click the gateway name to open the Gateway Details page, where you can find the IP addresses, login username, and password for the device.

After you order and configure your VRA from the IBM Cloud catalog, you must also configure the device itself with the same settings.





 VLANs and the gateway appliance's role 

A VLAN (virtual LAN) is a mechanism that segregates a physical network into many virtual segments. For convenience, traffic from multiple selected VLANs can be delivered through a single network cable, a process commonly called "trunking."

IBM Cloud® Virtual Router Appliance is delivered in two parts: The VRA servers and the gateway appliance fixture. The gateway appliance provides you with an interface (GUI and API) for selecting the VLANs you want to associate with your VRA. Associating a VLAN with a gateway appliance reroutes (or "trunks") that VLAN and all of its subnets to your VRA, giving you control over filtering, forwarding, and protection. For every VLAN that is associated to the gateway appliance, that VLAN is allowed on the switch ports that the VRA is connected to, and any subnet on that VLAN is statically routed to your VRA's public VRRP IP (if the subnet is a public subnet) or statically routed to your VRA's private VRRP IP (if the subnet is a private subnet). This routing is done at the router that the VRA is behind, which is the Frontend Customer Router (FCR) or the Backend Customer Router (BCR) for public and private traffic respectively.

Be aware that VRRP is disabled by default, and it must be enabled in order for VLAN traffic to work, even on stand-alone Vyattas. This is a consequence of the subnets on the associated VLAN's being routed to the VRRP IP or virtual-address assigned to the VRA.
'VirtualMachine.GuestOperations.Query',
'VirtualMachine.GuestOperations.Modify',
'VirtualMachine.GuestOperations.Execute',
'VirtualMachine.Config.Rename',
'VirtualMachine.Config.AddExistingDisk',
'VirtualMachine.Config.AddNewDisk',
'VirtualMachine.Config.Annotation',
'VirtualMachine.Config.RemoveDisk',
'VirtualMachine.Config.RawDevice',
'VirtualMachine.Config.AddRemoveDevice',
'VirtualMachine.Config.EditDevice',
'VirtualMachine.Config.Settings',
'VirtualMachine.Config.Resource',
'VirtualMachine.Config.AdvancedConfig',
'VirtualMachine.Config.DiskLease',
'VirtualMachine.Config.DiskExtend',
'VirtualMachine.Config.ChangeTracking',
'VirtualMachine.State.CreateSnapshot',
'VirtualMachine.State.RevertToSnapshot',
'VirtualMachine.State.RemoveSnapshot',
'VirtualMachine.State.RenameSnapshot',
'VirtualMachine.Provisioning.MarkAsTemplate',
'VirtualMachine.Provisioning.MarkAsVM',
'VirtualMachine.Provisioning.DiskRandomAccess',
'VirtualMachine.Provisioning.DiskRandomRead',
'VirtualMachine.Provisioning.GetVmFiles',
'VirtualMachine.Provisioning.PutVmFiles',
'Resource.AssignVMToPool',
'Resource.CreatePool',
'Resource.DeletePool',
'Resource.HotMigrate',
'Resource.ColdMigrate',
'Extension.Register',
'Extension.Unregister',
It enables the monitoring, isolation, and resolution of performance bottlenecks in the HCX Interconnects, Migrations, or Protected workloads.







 Related links 



* [VMware Aria Operations 8.12.x Sizing Guidelines](https://kb.vmware.com/s/article/91692)
* [VMware Aria Operations Documentation](https://docs.vmware.com/en/VMware-Aria-Operations/index.html)
* [Updating vSAN clusters](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vum-updating-vsan)
* [vSAN Health Check Information](https://kb.vmware.com/s/article/2114803)
* [Operationalizing VMware NSX](https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/products/nsx/vmware-operationalizing-nsx.pdf)
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.

![solution tutorial icon](https://cloud.ibm.com/media/docs/images/homepage/solution-tutorial.svg) [IBM Cloud Framework for Financial Services](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-about)IBM Cloud Framework for Financial Services Solution guide

Financial institutions can confidently host their mission-critical applications in the cloud and transact quickly and efficiently.

![solution icon](https://cloud.ibm.com/media/docs/images/homepage/magic-wand.svg) [Install software on virtual server instances in VPC](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-app-deploy)Install software on virtual server instances in VPC Solution tutorial

This tutorial walks you through provisioning IBM Cloud® Virtual Private Cloud (VPC) infrastructure and installing software on virtual server instances (VSI) using Infrastructure as Code (IaC) tools like Terraform and Ansible.

![solution tutorial icon](https://cloud.ibm.com/media/docs/images/homepage/solution-tutorial.svg) [Isolating workloads with a secure private network](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-secure-network-enclosure)Isolating workloads with a secure private network Solution tutorial

This tutorial highlights how a Virtual Router Appliance (VRA) can be configured on the IBM Cloud to create a secure private network (enclosure).
When you use the VMware virtual machines (VMs) on VPC subnets architecture, your VMs are attached to VPC subnets and the routing behaves in the same way as with VPC Virtual Servers. The VPC subnets are provisioned from the zone prefix, and the routing works between the VPC without any required changes. You can use both IBM Cloud VPN Gateway for VPC and IBM Cloud Client VPN for VPC with this solution as described in the documentation previously listed.

Zoom

![VPNaaS with VMware on VPC](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/vpc-ryo-diagrams-dl-sub-arch.svg)

Figure 1. VPNaaS with VMware on VPC

When you use NSX-T™ on your VMware solution on VPC, the VMs are attached on the NSX-T overlay segments. They use an IP address range or prefix, which is reachable through VPC route that points to NSX-T Tier-0 private uplink VIP as described in the [VMware NSX-T logical routing on VPC](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vpc-ryo-nsx-t-vpc-routing) topic. You can use both IBM Cloud VPN Gateway for VPC and IBM Cloud Client VPN for VPC with this solution as described in the documentation previously listed.

Zoom

![VPNaaS with VMware on VPC with NSX-T](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/vpc-ryo-diagrams-dl-nsx-t-arch.svg)

Figure 2. VPNaaS with VMware on VPC with NSX-T
Bandwidth allocation with multiple network interfaces 

You can add up to 15 network interfaces for your virtual server instance, depending on the vCPU count that is included in the instance profile.



* 2-16 vCPUs: Up to 5 network interfaces
* 17-48 vCPUs: Up to 10 network interfaces
* 49 or more vCPUs: Up to 15 network interfaces



With multiple network interfaces, bandwidth is distributed evenly across the network interfaces that are attached to the virtual server instance.

For more information, see [Managing network interfaces](https://cloud.ibm.com/docs/vpc?topic=vpc-using-instance-vnics).







 Viewing profile configurations 

You can view available profile configurations by using the IBM Cloud console or the CLI. In the IBM Cloud console, you can select from popular profile configurations that support most common use cases.



 Understanding the naming rule of the profiles 

The following information describes the naming rule of the profiles.

The first character represents the profile families. Different profile families have different ratios of vCPU to memory and other characteristics that are designed for different workloads.



* "b": balanced family of profiles, 1 vCPU to 4 GiB of memory ratio
* "c": compute family of profiles (higher on the CPUs), 1 vCPU to 2 GiB of memory ratio
* "m": memory family of profiles (higher on the memory), 1 vCPU to 8 GiB of memory ratio
* "u": ultra high memory family of profiles, 1 vCPU to 28 GiB of memory ratio
* "v": very high memory family of profiles, 1 vCPU to 14 GiB of memory ratio
* "g": GPU profiles, which is a 1:8 or 1:16 ratio
* "o": storage optimized family of profiles, 1 vCPU to 8 GiB memory ratio and 1 vCPU to 300 GB instance storage ratio



The second character represents the CPU architecture.



* "x": x86_64



The third character represents the generation of the IBM Cloud infrastructure where the profile is provisioned.



* "1": IBM Cloud Virtual Servers for Classic
* "2": IBM Cloud Virtual Servers for VPC
If you want VPS1 to have more IP addresses to separate services that it is providing, you can assign more addresses out of the 129.42.0.0/29 subnet, but you may want to use that subnet only to bring VMs online, not for their services. You have two options: 1) purchase another portable subnet, or 2) purchase a static subnet. Portable subnets provide flexibility but they don't give you access to all of the IP addresses. If you only needed four additional IP addresses, for example, purchasing a static subnet is an efficient option.

You can purchase a static subnet and receive 129.42.0.100/30. You can route the subnet to 129.42.0.3 or VPS1 in this scenario. Doing so provides you with all four IP addresses to use on whatever server is responding to 129.42.0.3, and if you transfer 129.42.0.3 to VPS2, those four new IP addresses from 129.42.0.100/30 will follow. Let's look at the IP address usage again:

129.42.0.0/29 - Secondary portable subnet

129.42.0.0 – Network
129.42.0.1 – Gateway
129.42.0.2 –
129.42.0.3 – VPS1
129.42.0.4 –
129.42.0.5 – VPS2
129.42.0.6 –
129.42.0.7 – Broadcast

129.42.0.100/30 - Secondary static subnet

129.42.0.100 – 129.42.0.3 (VPS1)
129.42.0.101 – 129.42.0.3 (VPS1)
129.42.0.102 – 129.42.0.3 (VPS1)
129.42.0.103 – 129.42.0.3 (VPS1)

In summary, this scenario used a portable subnet to make IP addresses available to all virtual machine hosts, and then made additional IP addresses available to a virtual machine by using a static subnet.