vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* [ibm_iam-access_group_policy](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-iam-resourcesiam-access-group-policy)
* [ibm_iam_service_policy](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-iam-resourcesiam-service-policy)
* [ibm_iam_user_policy](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-iam-resourcesiam-user-policy)
* [ibm_iam_user_invite](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-iam-resourcesiam-user-invite) (iam_policy.resource.attributes)



See Table 1 for the full list of VPC resource attributes.



Table 1. VPC resource attributes

 Resource Resource Attribute 

 Auto Scale for VPC instanceGroupId:<instance-group-id> 
 Backup service backupPolicyId: <backup-policy-id> 
 Block Storage for VPC volumeId: <volume-id> 
 Bare metal server bareMetalServerId: <bare-metal-server-id> 
 Dedicated Host for VPC dedicatedHostId:<dedicated-host-id> 
 File Storage shareId: <share-id> 
 Floating IP for VPC floatingIpId: <fip-id> 
 Flow Logs for VPC flowLogCollectorId: <flc-id> 
 Image Service for VPC imageId:<image-id> 
 Load Balancer for VPC loadBalancerId: <load-balancer-id> 
 Network ACL networkAclId: <nacl-id> 
 Placement Group for VPC placementGroupId: <placement-group-id>
Power Virtual Server with VPC landing zone - as new deployment 

New deployment of the Power Virtual Server with VPC landing zone creates VPC services and a Power Virtual Server workspace and interconnects them.

A proxy service for public internet access from the PowerVS workspace is configured. You can optionally configure some management components on VPC (such as an NFS server, NTP forwarder, and DNS forwarder).



 Architecture diagram 

Zoom

![Architecture diagram for 'Power Virtual Server with VPC landing zone' - variation 'PowerVS workspace'.](https://cloud.ibm.com/docs-content/v1/content/9610604e9f8dcd5f7b6b138dd22ba445300be7f5/deployable-reference-architectures/terraform-ibm-powervs-infrastructure/full-stack/deploy-arch-ibm-pvs-inf-full-stack.svg)

Figure 1. Single-zone PowerVS workspace accessible over secure landing zone





 Design requirements 

Zoom

![Design requirements for 'Power Virtual Server with VPC landing zone' - variation 'PowerVS workspace'.](https://cloud.ibm.com/docs-content/v1/content/9610604e9f8dcd5f7b6b138dd22ba445300be7f5/deployable-reference-architectures/terraform-ibm-powervs-infrastructure/full-stack/heat-map-deploy-arch-ibm-pvs-inf-full-stack.svg)

Figure 2. Scope of the solution requirements

IBM Cloud® Power Virtual Servers (PowerVS) is a public cloud offering that an enterprise can use to establish its own private IBM Power computing environment on shared public cloud infrastructure. PowerVS is logically isolated from all other public cloud tenants and infrastructure components, creating a private, secure place on the public cloud. This deployable architecture provides a framework to build a PowerVS offering according to the best practices and requirements from the IBM Cloud.





 Components 



 VPC architecture decisions 



Table 1. VPC architecture decisions
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) 
 Virtual Private Endpoint for VPC ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) !
IBM virtual servers for VPC on POWER (Beta)
: Create POWER-based instances for all virtual server families, including the addition of the GPU family (for POWER only). For more information, see [Profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-profiles).

UI enhancement
: On the VPC details page, a new section is available to view source IP addresses for any cloud service endpoints you enabled. For more information, see [Service endpoints](https://cloud.ibm.com/docs/vpc?topic=vpc-service-endpoints-for-vpc).

CLI plug-in release 0.5.9
: Target a specific resource group by using the '[-g YOUR_GROUP]' command option. If you specify the target resource group by using the ibmcloud target [-g YOUR_GROUP]command, the output displays only VPC resources inside of the specified resource group. This update also introduces enhancements to some of the commands for get and list, showing more detail for your VPC, instances, and instance profiles. For more information, see [VPC CLI reference](https://cloud.ibm.com/docs/vpc?topic=vpc-infrastructure-cli-plugin-vpc-reference).





 02 December 2019 

Access control lists
: Use an access control list (ACL) to control all incoming and outgoing traffic in IBM Cloud® Virtual Private Cloud. For more information, see [Setting up network ACLs](https://cloud.ibm.com/docs/vpc?topic=vpc-using-acls).







 November 2019 



 14 November 2019 

VPC layout
: View resources that are associated with a VPC in the IBM Cloud console. For more information, see [Viewing resources associated with a VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-using-the-ibm-cloud-consolevpc-layout).





 07 November 2019 

Load balancer (Beta)
No 10.241.4.0/28 
 vpc_cluster_private_subnets_cidr_blocks The CIDR block that's required for the creation of the compute and storage cluster private subnet. Modify the CIDR block if it has already been reserved or used for other applications within the VPC or conflicts with any on-premises CIDR blocks if you are using a hybrid environment. Provide only one CIDR block for the creation of the compute and storage subnet. Make sure to select a CIDR block size that accommodates the maximum number of management, storage, and both static and dynamic worker nodes that you expect to have in your cluster. For more information on CIDR block size selection, see [Choosing IP ranges for your VPC](https://cloud.ibm.com/vpc?topic=vpc-choosing-ip-ranges-for-your-vpc). No 10.241.0.0/22 
 vpc_name Name of an existing VPC in which the cluster resources are deployed. If no value is given, then a new VPC is provisioned for the cluster. [Learn more](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-vpc-resources-with-cli-and-api). No _NOT_SET_ 
 vpc_scale_storage_dns_domain IBM Cloud DNS Services domain name to be used for the Spectrum Scale storage cluster. Note: The domain name should not be the same as vpc_worker_dns_domain when spectrum_scale_enabled is set to "true". No dnsscale.com 
 vpc_worker_dns_domain IBM Cloud DNS Services domain name to be used for the compute cluster, for example, "test.example.corp". No dnsworker.com 
 vpn_enabled Set the value as true to deploy a VPN gateway for VPC in the cluster. No false 
 vpn_peer_address The peer public IP address to which the VPN is connected. No _NOT_SET_
The sample code block helps to create the resources of the same type in a sequential order.

 {: codeblock}
resource "ibm_is_vpc" "res_a" {
name = "test1"
}
resource "ibm_is_vpc" "res_b" {
name = "test2"
depends_on = [ibm_is_vpc.res_a]
}






 How do I enable the User list visibility for the IAM in Terraform? 

Currently, Schematics do not support enabling user list visibility. For more information, about user list visibility, see [ibm_iam_account_settings](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/iam_account_settings).





 Can I configure the ibm_container_cluster Terraform resource to control the IPs on the IBM Cloud Object Storage bucket? 

No, currently, the API does not support IPs on the IBM Cloud Object Storage bucket. For more information, about the argument and attribute reference for the container cluster, see [ibm_container_cluster](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/container_cluster).





 Can I retrieve a list of all the existing Virtual Servers for VPCs from all the regions by using Terraform? 

Yes, but the VPC API’s are region specific so ibm_is_vpcs gives only one region VPC. If user requires one or more regions, you should define or use the alias during the resource provisioning, as shown in the code block.

 {: codeblock}
provider "ibm" {
region = "eu-de"
}

provider "ibm" {
alias = "dal"
region = "us-south"
}

data ibm_is_vpcs eu-de{
}
data ibm_is_vpcs dal {
provider = ibm.dal
}

output "vpcs" {
value = concat(
tolist(data.ibm_is_vpcs.eu-de.vpcs),
ibmcloud is vpc-update VPC --name NEW_NAME [--output JSON] [-q, --quiet]



 Command examples 



* ibmcloud is vpc-update 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 --name my-renamed-vpc
* ibmcloud is vpc-update my-vpc --name my-renamed-vpc







 Command options 



* VPC: ID or name of the VPC.
* --name: New name of the VPC.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is vpcs 

List all VPCs.

ibmcloud is vpcs [--resource-group-id RESOURCE_GROUP_ID | --resource-group-name RESOURCE_GROUP_NAME | --all-resource-groups] [--classic-access true | false] [--output JSON] [-q, --quiet]



 Command options 



* --resource-group-id: ID of the resource group. This ID is mutually exclusive with --resource-group-name.
* --resource-group-name: Name of the resource group. This name is mutually exclusive with --resource-group-id.
* --all-resource-groups: Query all resource groups.
* --classic-access: This flag lists VPCs that have classic access enabled. If unspecified, it returns all VPCs with and without classic access enabled. One of: true, false.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



--------------------









 Virtual private endpoint gateways
Release notes for the Power Virtual Server with VPC landing zone deployable architecture 

Use these release notes to learn about the latest updates to the Power Virtual Server with VPC landing zone. The entries grouped by date.



  10 July 2023 

Introducing Power Virtual Server with VPC landing zone
:   The Power Virtual Server with VPC landing zone deployable architecture is released. You can use the deployable architecture to create an isolated PowerVS landscape connected with VPC landing zone.
VSI on VPC landing zone - QuickStart variation 

The QuickStart variation of the VSI on VPC landing zone deployable architecture creates a fully customizable Virtual Private Cloud (VPC) environment in a single region. The solution provides virtual servers in a secure VPC for your workloads. The QuickStart variation is designed to deploy quickly for demonstration and development.



 Architecture diagram 

Zoom

![Architecture diagram for the QuickStart variation of VSI on VPC landing zone](https://cloud.ibm.com/docs-content/v1/content/9610604e9f8dcd5f7b6b138dd22ba445300be7f5/deployable-reference-architectures/terraform-ibm-landing-zone/vsi-quickstart.drawio.svg)

Figure 1. QuickStart variation of VSI on VPC landing zone





 Design requirements 

Zoom

![Design requirements for VSI on VPC landing zone](https://cloud.ibm.com/docs-content/v1/content/9610604e9f8dcd5f7b6b138dd22ba445300be7f5/deployable-reference-architectures/terraform-ibm-landing-zone/heat-map-deploy-arch-slz-vsi-quickstart.svg)

Figure 2. Scope of the design requirements





 Components 



 VPC architecture decisions 



Table 1. Architecture decisions

 Requirement Component Reasons for choice Alternative choice 

 <br><br> * Provide infrastructure/application administration access to monitor, operate, and maintain the environment.<br> * Limit the number of infrastructure/application administration entry points to ensure security audit.<br><br><br> Management VPC service Create a separate VPC service where SSH connectivity from outside is allowed
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is vpc-default-security-group 

View details of the default security group of a VPC.

ibmcloud is vpc-default-security-group VPC [--output JSON] [-q, --quiet]



 Command options 



* VPC: ID or name of the VPC.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is vpc-delete 

Delete one or more VPCs.

ibmcloud is vpc-delete (VPC1 VPC2 ...) [--output JSON] [-f, --force] [-q, --quiet]



 Command options 



* VPC1: ID or name of the VPC.
* VPC2: ID or name of the VPC.
* --output: Specify output format, only JSON is supported. One of: JSON.
* --force, -f: Force the operation without confirmation.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is vpc-update 

Update a VPC.

ibmcloud is vpc-update VPC --name NEW_NAME [--output JSON] [-q, --quiet]



 Command examples 



* ibmcloud is vpc-update 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 --name my-renamed-vpc
* ibmcloud is vpc-update my-vpc --name my-renamed-vpc







 Command options 



* VPC: ID or name of the VPC.
VSI on VPC landing zone - QuickStart variation 

The QuickStart variation of the VSI on VPC landing zone deployable architecture creates a fully customizable Virtual Private Cloud (VPC) environment in a single region. The solution provides virtual servers in a secure VPC for your workloads. The QuickStart variation is designed to deploy quickly for demonstration and development.



 Architecture diagram 

Zoom

![Architecture diagram for the QuickStart variation of VSI on VPC landing zone](https://cloud.ibm.com/docs-content/v1/content/bbc046343d620cb2210cb1c62a46d7601ae08e00/secure-infrastructure-vpc/includes/deployable-reference-architectures/terraform-ibm-landing-zone/includes/deployable-reference-architectures/terraform-ibm-landing-zone/vsi-quickstart.drawio.svg)

Figure 1. QuickStart variation of VSI on VPC landing zone





 Design requirements 

Zoom

![Design requirements for VSI on VPC landing zone](https://cloud.ibm.com/docs-content/v1/content/bbc046343d620cb2210cb1c62a46d7601ae08e00/secure-infrastructure-vpc/includes/deployable-reference-architectures/terraform-ibm-landing-zone/includes/deployable-reference-architectures/terraform-ibm-landing-zone/heat-map-deploy-arch-slz-vsi-quickstart.svg)

Figure 2. Scope of the design requirements





 Components 



 VPC architecture decisions 



Table 1. Architecture decisions

 Requirement Component Reasons for choice Alternative choice 

 <br><br> * Provide infrastructure/application administration access to monitor, operate, and maintain the environment.<br> * Limit the number of infrastructure/application administration entry points to ensure security audit.<br><br><br> Management VPC service Create a separate VPC service where SSH connectivity from outside is allowed
"href": "https://us-south.iaas.cloud.ibm.com/v1/shares/207721a9-aff9-4b16-9823-fe68096aeac3/mount_targets/ce244454-0919-45e2-b14b-f4285afcd856",
"id": "ce244454-0919-45e2-b14b-f4285afcd856",
"name": "my-share-mount-target",
"resource_type": "share_mount_target",
"vpc": {
"crn": "crn:...]",
"href": "https://us-south.iaas.cloud.ibm.com/v1/vpcs/c8b8fa2d-ccf7-4f42-9d38-df6d123c867d",
"id": "c8b8fa2d-ccf7-4f42-9d38-df6d123c867d",
"name": "my-vpc",
"resource_type": "vpc"
}
}
],
"name": "my-share-3",
"profile": {
"family": "defined-performance",
"href": "https://us-south.iaas.cloud.ibm.com/v1/share/profiles/dp2",
"name": "dp2",
"resource_type": "share_profile"
},
"replication_role": "source",
"replication_status": "active",
"replication_status_reasons": [],
"resource_group": {
"crn": "crn:[...]",
VPE for VPC IP addresses uses a multizone region, logical endpoint gateway to connect to a service endpoint on the IBM Cloud private backbone. The endpoint gateway is designed to support the best practice of binding a single IP from each zone of the VPC.

You can create an endpoint gateway with zero IP addresses and bind IP addresses as each zone is brought online. When you create an endpoint gateway, a DNS zone and records are created. The VPE service automatically upgrades your virtual server instances to use the private DNS as the default DNS resolver. For more information about creating VPEs, see [Creating an endpoint gateway](https://cloud.ibm.com/docs/vpc?topic=vpc-ordering-endpoint-gateway&interface=ui).

As more IBM Cloud services are enabled for VPE for VPC, each service instance requires you to configure its endpoint gateway, but it uses the same topologies and best practices. For more information about provisioning and best practice guidelines, see the documentation that is provided by the individual service.





 Related links 



* [IBM Cloud VPC getting started](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started)
* [IBM Cloud VPC Bare Metal Servers](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-for-bare-metal-servers)
* [IBM Cloud VPC RYO VMware reference architecture](https://cloud.ibm.com/docs/vmwaresolutions?topic=vpc-ryo-overview)
* [IBM Cloud Direct Link overview](https://cloud.ibm.com/docs/dl?topic=dl-get-started-with-ibm-cloud-dl)
* [IBM Cloud Transit Gateway overview](https://cloud.ibm.com/docs/transit-gateway?topic=transit-gateway-getting-started)
* [IBM Cloud VPC VPN overview](https://cloud.ibm.com/docs/vpc?topic=vpc-vpn-overview)
"resource_type": "share_mount_target",
"vpc": {
"crn": "crn:...]",
"href": "https://us-south.iaas.cloud.ibm.com/v1/vpcs/c2d941de-27f5-432c-b4d0-37a8491c3216",
"id": "c2d941de-27f5-432c-b4d0-37a8491c3216",
"name": "my-vpc",
"resource_type": "vpc"
}
}
],
"name": "my-share",
"profile": {
"href": "https://us-south.iaas.cloud.ibm.com/v1/share/profiles/dp2",
"family": "defined-performance",
"name": "dp2",
"resource_type": "share_profile"
},
"replication_role": "none",
"replication_status": "none",
"replication_status_reasons": [],
"resource_group": {
"crn": "crn:[...]",
"href": "https://us-south.iaas.cloud.ibm.com/v2/resource_groups/678523bcbe2b4eada915d32640909956",
"id": "678523bcbe2b4eada915d32640909956",
"name": "Default"
},
"resource_type": "share",
"size": 4800,
"user_tags": [],
"zone": {
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) 
 Placement Groups for VPC ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) !
hana_components = "server" default	value is: "server"

SAP HANA Installation kit path
kit_saphana_file = "/storage/HANADB/51054623.ZIP"

For each IBM Cloud VPC region, IBM allocates temporary storage on a dedicated Jump host (Deployment server). The Jump host is used for any IBM client to be able to download and decompress the necessary SAP and DB kits for their solutions in scope. Then, the kits variables (paths) need to be updated into the dedicated Terraform variables in order for the Ansible playbook to identify them correctly during SAP and Db2 automation.
6. Edit the sapsingletierdb2/terraform/main.tf file and specify the VPC to use. You can have the scripts create a new VPC or you can use an existing VPC. By default the scripts use an existing VPC. If you are using an existing VPC, be sure that the VPC name is in the input.auto.tfvars file.

To create a new VPC, uncomment the source = "./modules/vpc" line and comment out the source = "./modules/vpc/existing" line.

To use an existing VPC, make sure the source = "./modules/vpc/existing" line is uncommented and leave the source = "./modules/vpc" line commented out.

/module "vpc" {
 source		= "./modules/vpc"
source		= "./modules/vpc/existing"
ZONE			= var.ZONE
VPC			= var.VPC
SECURITYGROUP 	= var.SECURITYGROUP
SUBNET		= var.SUBNET
}
/
7. Initialize the Terraform CLI.

terraform init
8. Create a Terraform execution plan. The Terraform execution plan summarizes all the actions that are done to create the virtual private cloud instance in your account.

terraform plan

You must enter an SAP HANA main password.
au-syd-3 172.21.128.0/18 
 jp-osa-1 172.24.0.0/18 
 jp-osa-2 172.24.64.0/18 
 jp-osa-3 172.24.128.0/18 
 ca-tor-1 10.249.0.0/18 
 ca-tor-2 10.249.64.0/18 
 ca-tor-3 10.249.128.0/18 
 br-sao-1 172.26.0.0/18 
 br-sao-2 172.26.64.0/18 
 br-sao-3 172.26.128.0/18 



The Madrid region only supports dedicated host profiles with instance storage. For more information, see [Dedicated host profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-dh-profiles&interface=ui).

To prevent address prefixes from being created, you can add the "address_prefix_management": "manual" parameter when you create the VPC by using the API:

curl -H "Authorization:$iam_token" "$iaas_endpoint/v1/vpcs?generation=2&version=$api_version" -X POST -d '{ "name": "my-access-vpc", "address_prefix_management": "manual", "classic_access": true}'







 Converting your account to VRF 

The VRF conversion process involves a network disruption while the VLANs and their subnets are detached from the ACL backbone and then attached to the Customer VRF. This process results in a few moments of packet loss for traffic that is entering or exiting the VLANs. Packets within the VLAN continue to flow. In the cases where a network gateway, such as a FortiGate Security Appliance or Virtual Router Appliance is involved, no disruption occurs among the VLANs attached to that gateway. The servers see no network outage themselves, and most workloads automatically recover when the traffic flow resumes.
: The modals for provisioning and attaching a public gateway and for creating an SSH key are now replaced with a redesigned side pane.







 January 2020 



 10 January 2020 

New Washington DC region
: The Washington DC region endpoint (us-east) is now in service at http://us-east.iaas.cloud.ibm.com. For more information, see [Endpoint URLs](https://cloud.ibm.com/apidocs/vpcendpoint-url) in the IBM Cloud VPC API. See also [Creating a VPC in a different region](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-in-a-different-region).

CLI plug-in release 0.5.10
: For more information, see [VPC CLI reference](https://cloud.ibm.com/docs/vpc?topic=vpc-infrastructure-cli-plugin-vpc-reference).



* You now have an Example section in command help for creating and updating commands. Example: ibmcloud is help instance-create, ibmcloud is help instance-update, or ibmcloud is help volume-create.
* Use the resource group filter in list commands. Example: ibmcloud is vpcs --resource-group-name Littleton.
* JSON output format support for the ibmcloud is target --json command.
* ipv4 and primary-network-interface options for instance-create. Options help specify the primary private IP for the primary network interface when you create an instance.









 December 2019 



 09 December 2019 

IBM virtual servers for VPC on POWER (Beta)
: Create POWER-based instances for all virtual server families, including the addition of the GPU family (for POWER only). For more information, see [Profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-profiles).

UI enhancement
: On the VPC details page, a new section is available to view source IP addresses for any cloud service endpoints you enabled.