vania-janet/multiturn-rag-retrieval-data huggingface dataset:
"name": "my-share-name1",
"profile": {
"name": "tier-5iops"
},
"user_tags": [],
"zone": {
"name": "us-south-1"
}
}'
Show more

The following example request creates a file share and mount target, specifying API version 2023-07-11 or later. The access_control_mode and virtual_network_interface properties are specified in the example. The new share is based on the dp2 profile.

curl -X POST "$vpc_api_endpoint/v1/shares?version=2023-07-11&generation=2&maturity=beta" -H "Authorization: $iam_token" -d '{
"size": 10,
"name": "my-share-sc-2",
"profile": {
"name": "dp2"
},
"zone": {
"name": "us-south-3"
},
"mount_targets": [
"virtual_network_interface": {
"primary_ip": {
"name": "my-primary-ip1",
"address": "192.0.2.0",
"href": "https://us-south.iaas.cloud.ibm.com/v1/subnets/aea5fe79f-52c3-4f05-86ae-9540a10489f5/reserved_ips/6fd4925d-7774-4e87-829e-7e5765d454ad",
"id": "6fd4925d-7774-4e87-829e-7e5765d454ad",
"name": "my-reserved-ip",
"auto_delete": "false"
}
},
"transit_encryption": {
"user_managed"
}
* String
* Boolean
* ScalarList



The following other reserved names cannot be used as identifiers:



* Dictionary
* Regex
* Consolidate
* Block
* BlockTok
* Sentence
* Tokenize
* RegexTok
* PosTag







 Constants 

Constants are fixed values that can be one of these data types: String, Integer, Float, or Boolean.

Constants are used in the select list of a select or extract clause, or as arguments in built-in or UDF functions and predicates. AQL supports the following types of constants:



* String constant

A string that is enclosed in single quotation marks (‘), for example ‘a string’.
* Integer constant

A 32-bit signed integer value that is not enclosed in quotation marks, for example 10 or -1.
* Float constant

A single-precision 32-bit floating point value, not enclosed in quotation marks, for example 3.14 or -1.2.
* Boolean constant

The value true or false not enclosed in quotation marks.
* Null constant

The value null that is not enclosed in quotation marks.







 Expressions 

An AQL expression is a combination of one or more scalar values and functions that evaluates to a single scalar value.

Expressions can be one of four types:



* a constant
* a column reference
* a scalar function call
* an aggregate function call





 Constant 

An expression can be a constant of type Integer, Float, or String, as in the following example:

select 'positive' as polarity

The expression is the string constant positive.





 Column reference 

An expression can be a column reference, as in the following example:

create view Person as
select F.name as firstname, L.name as lastname
from FirstName F, LastName L
where FollowsTok(F.name, L.name, 0, 0);

This view identifies text that can be interpreted as a person’s full name (for example, “Samuel Davis”, “Vicky Rosenberg”).
Wherever you mount the file share, the root folder uses that user ID and group ID owner. You set the UID or GID, or both when you create a share in a POST /shares call.

If you change the supplemental IDs (UID or GID) from the virtual server instance, it is not possible to determine that it was changed. As a result, initial_owner does not change in the API database but changes only in the file storage system.

Table 1 shows UID and GID values that you can set and values that are reserved.



Table 1. Unix/Linux® supplemental ID values.

 ID value Description 

 UID 
 UID 0 Reserved for root. 
 UID 1–99 Reserved for predefined accounts. 
 UID 100–999 Reserved by the system for administrative system accounts and groups. 
 UID 1000–10000 Used by applications account. 
 UID 10000+ Available for user accounts. 
 GID 
 GID 0 Reserved for root. 
 GID 1–99 Reserved for the system and application use. 
 GID 100+ Allocated for the user’s group. 



To set supplemental IDs when you create a share, make a POST /shares call and specify the initial_owner property with the supplemental IDs. See the following example.

curl -X POST 
"$vpc_api_endpoint/v1/shares?version=2023-05-06&generation=2&maturity=beta"
-H "Authorization: $iam_token" 
-d '{
"initial_owner": {
"gid": 101,
"uid": 10001
},
"size": 4800,
"name": "share-name",
"profile": {
"name": "tier-10iops"
},
"zone": {
"name": "us-south-1"
}
.
.
.
}'
Show more







 Creating a file share and mount target with Terraform 

To use Terraform, download the Terraform CLI and configure the IBM Cloud® Provider plug-in.
Wherever you mount the file share, the root folder uses that user ID and group ID owner. You set the UID or GID, or both when you create a share in a POST /shares call.

If you change the supplemental IDs (UID or GID) from the virtual server instance, it is not possible to determine that it was changed. As a result, initial_owner does not change in the API database but changes only in the file storage system.

Table 1 shows UID and GID values that you can set and values that are reserved.



Table 1. Unix/Linux® supplemental ID values.

 ID value Description 

 UID 
 UID 0 Reserved for root. 
 UID 1–99 Reserved for predefined accounts. 
 UID 100–999 Reserved by the system for administrative system accounts and groups. 
 UID 1000–10000 Used by applications account. 
 UID 10000+ Available for user accounts. 
 GID 
 GID 0 Reserved for root. 
 GID 1–99 Reserved for the system and application use. 
 GID 100+ Allocated for the user’s group. 



To set supplemental IDs when you create a share, make a POST /shares call and specify the initial_owner property with the supplemental IDs. See the following example.

curl -X POST 
"$vpc_api_endpoint/v1/shares?version=2023-05-06&generation=2&maturity=beta"
-H "Authorization: $iam_token" 
-d '{
"initial_owner": {
"gid": 101,
"uid": 10001
},
"size": 4800,
"name": "share-name",
"profile": {
"name": "tier-10iops"
},
"zone": {
"name": "us-south-1"
}
.
.
.
}'







 Creating a file share and mount target with Terraform 

To use Terraform, download the Terraform CLI and configure the IBM Cloud® Provider plug-in.
In the console, reserved IP addresses that are labeled "unbound" might be bound to a resource that can't be displayed.

Issue: The instance metadata API does not currently support reserved IPs.

Workaround: Continue to use the primary_ipv4_address property to retrieve the IP address for each network interface on an instance. See the [VPC Metadata API](https://cloud.ibm.com/apidocs/vpc-metadata).

Issue: When you use the VPC API to [list floating IP addresses on a bare metal server network interface](https://cloud.ibm.com/apidocs/vpclist-bare-metal-server-network-interface-floating-), you might get an incomplete list of the floating IP addresses associated with the bare metal server network interface.

The floating IP associated with a bare metal network interface is not available before the network interface status is available.

Workarounds:



* Wait for the bare metal server network interfaces to be available before listing the floating IP addresses on the interfaces.
* [List all floating IPs](https://cloud.ibm.com/apidocs/vpclist-floating-ips) to view those associated with bare metal server interfaces that are not yet available.







 Network load balancers fail if port settings fall outside the supported range 

Issue: Cannot create network load balancers with specific port ranges

Currently, the port_min and port_max properties are supported only when routing mode is enabled, and only when the entire port range is specified (port_min of 1 and port_max of 65535). Support for allowing an arbitrary port range to be specified is planned for a future release.





 Checksum not available for some public images 

Issue: When you use the API or CLI to list images, some public stock images might not include a checksum. The checksum is for informational purposes only for stock images. No fix is available.





 Boot volume has larger minimum provisioned size when you create a custom image by using IFV
* --address: The IP address to reserve, which must not already be reserved on the subnet.
* --auto-delete: If set to true, this reserved IP automatically deletes when the target is deleted. One of: true, false. (default: true).
* --ip-name: The user-defined name for this reserved IP. Names must be unique within the subnet that the reserved IP resides in. Names beginning with ibm- are reserved for provider-owned resources.
* --allow-ip-spoofing: Disables the source and destination checks on this interface. If false, source IP spoofing is not allowed on this interface. One of: false, true.
* --primary-network-interface: PRIMARY_NETWORK_INTERFACE_JSON|@PRIMARY_NETWORK_INTERFACE_JSON_FILE, primary network interface in JSON or JSON file. For the data schema, see the primary_network_interface property in the [API documentation](https://cloud.ibm.com/apidocs/vpccreate-instance).
* --network-interface: NETWORK_INTERFACE_JSON|@NETWORK_INTERFACE_JSON_FILE, network interface attachment in JSON or JSON file. For the data schema, see the network_interfaces property in the [API documentation](https://cloud.ibm.com/apidocs/vpccreate-instance).
* --default-trusted-profile: ID or name of the trusted profile.
* --default-trusted-profile-auto-link: If set to true, the system creates a link to the specified target trusted profile during instance creation. Regardless of whether a link is created by the system or manually by using the IAM Identity service, it automatically deletes when the instance is deleted. One of: true,false. (default: true).
* --metadata-service, --ms: Enable or disable the Instance Metadata Service. One of: true, false.
* --metadata-service-protocol, --msp: The communication protocol for the metadata service endpoint. Applies only when the metadata service is enabled.
Select whether you want to have the system choose a reserved IP for you automatically, choose from a list of existing reserved IPs, or enter one yourself.
3. Select an address, if you require a specific IP address (optional).
4. Click Reserve IP.







 Deleting a reserved IP 

To delete (release) a reserved IP using the UI, navigate to Subnets > Reserved IPs and click the actions menu ![actions menu](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/vpc/images/overflow.png) next to the reserved IP that you want to delete. Select Release.







 Working with reserved IPs from the CLI 

You can use the CLI to create, update, and delete reserved IP addresses.

Before you begin, make sure to [set up your CLI environment](https://cloud.ibm.com/docs/vpc?topic=vpc-infrastructure-cli-plugin-vpc-reference).



 Creating a reserved IP from the CLI 

To reserve a VPC private IP address using the CLI, run the following command:

ibmcloud is subnet-reserved-ip-create SUBNET [--vpc VPC] [--name NAME] [--auto-delete true | false] [--target TARGET] [--output JSON] [-q, --quiet]

Where:



* SUBNET is the ID of the subnet.
* --vpc is the ID or name of the VPC. This option is only required if you want to specify the unique resource by name inside this VPC.
* --name is the user-defined name for this reserved IP. Names must be unique within the subnet that the reserved IP resides in. Names beginning with ibm- are reserved for provider-owned resources.
* --auto-delete determines how the auto-delete feature is set. If set to true, this reserved IP automatically deletes when the target is deleted.
* A sample NSX Logical Switch is deployed to be used by the customer workload VMs.
* A sample router is deployed for potential east-west communication between local workloads that are connected to layer 2 (L2) networks. This router is a NSX-T™ Tier 1 Router for NSX-T and an NSX Distributed Logical Router for NSX-V.
* An NSX Edge appliance is deployed and configured to perform network address translation (NAT). NAT is done from the range of IP addresses of the workload logical switch to a public IP address on the NAT rules.
* (NSX-V only) If you installed the Veeam® service, the NSX Manager is configured to do a daily backup of the NSX configurations. For more information, see [Veeam 9.5](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-veeam_considerations).





 Configuring the networking settings for your VMs 

To take advantage of NSX for your workload VMs, you must configure a number of settings by completing the following steps when you create your VMs:



1. Set the network adapter of the VM to the workload logical switch:



1. On the New Virtual Machine dialog box, click the Customize Hardware tab.
2. On the new device menu, select Network and click Add.
3. On the newly added network adapter, select the workload logical switch from the menu. The following examples show the name of the workload logical switch:



* For NSX-T - overlay-ls
* For NSX-V - vxw-dvs-17-virtualwire-1-sid-6000-Workload





Ensure that you do not select the Workload Transit switch.
2. Identify an available IP address for the VM:



* The IP address must be in the range of 192.168.10.0/24. The IP address 192.168.10.1 is reserved (see Step 3).
Reserved Font Name" refers to any names specified as such after the copyright statement(s)."Original Version" refers to the collection of Font Software components as distributed by the Copyright Holder(s)."Modified Version" refers to any derivative made by adding to, deleting, or substituting -- in part or in whole -- any of the components of the Original Version, by changing formats or by porting the Font Software to a new environment."Author" refers to any designer, engineer, programmer, technical writer or other person who contributed to the Font Software.PERMISSION & CONDITIONS Permission is hereby granted, free of charge, to any person obtaining a copy of the Font Software, to use, study, copy, merge, embed, modify, redistribute, and sell modified and unmodified copies of the Font Software, subject to the following conditions:<-- <ol> -->1. Neither the Font Software nor any of its individual components, in Original or Modified Versions, may be sold by itself.2. Original or Modified Versions of the Font Software may be bundled, redistributed and/or sold with any software, provided that each copy contains the above copyright notice and this license. These can be included either as stand-alone text files, human-readable headers or in the appropriate machine-readable metadata fields within text or binary files as long as those fields can be easily viewed by the user.3. No Modified Version of the Font Software may use the Reserved Font Name(s) unless explicit written permission is granted by the corresponding Copyright Holder. This restriction only applies to the primary font name as presented to the users.4. The name(s) of the Copyright Holder(s) or the Author(s) of the Font Software shall not be used to promote, endorse or advertise any Modified Version, except to acknowledge the contribution(s) of the Copyright Holder(s) and the Author(s) or with their explicit written permission.5. The Font Software, modified or unmodified, in part or in whole, must be distributed entirely under this license, and must not be distributed under any other license.
It is not supported to use a bring-your-own subnet range not defined under [RFC 1918](https://tools.ietf.org/html/rfc1918) IANA reserved IPv4 private network address spaces because this would not permit connectivity to an existing internal network when used with a Public Gateway (PGW) and Floating IPs.





 Classic Infrastructure with VMware 

If the existing business operates SAP on VMware, it is possible to use IBM Cloud for VMware along with VMware HCX and IBM Cloud® Direct Link to create a bridged bidirectional network between existing Datacenter with VMware and IBM Cloud for VMware. This uses the existing VMware service mesh routing into VMware HCX and into overlay from VMWare NSX on IBM Cloud for VMware, which creates:



* An encrypted Migration Tunnel that uses HCX Cloud Gateway (CGW) + HCX WAN Optimizer (WAN-OPT)
* An encrypted Application Tunnel that uses HCX High Throughput Layer 2 Concentrator (HT L2C)



More information and is described on [IBM Cloud for VMware Solutions - VMware HCX overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-hcx_considerations).









 Network Topology considerations 

Dependent on the count and configuration of SAP Systems that are combined with the arrangement of the network flows between these systems for security or performance reasons, the Network Topology will be significantly different. The design of this topology reflects the requirements from the business for security, performance, cost, flexibility, and connectivity.

Using the Enterprise Resource Planning (ERP) business application, for example, an SAP System hosting the Production instance that uses the SAP System Tiering approach using High Availability of SAP NetWeaver and SAP HANA:



* SAP NetWeaver, there are at least four hosts instead of 1:



* Central Services (ASCS)
* Primary Application Server (PAS), also known as Central Instance (CI)
* Enqueue Replication Server Instance (ERS)
* Additional Application Server (AAS)



* SAP HANA, there are at least 2 hosts (possibly 3) instead of 1:
* ibmcloud is subnet-reserved-ip-create 2201-3f2e33d4-2140-44b4-843c-d73e03d585f1 --name my-reserved-ip --address 10.240.64.10 --output JSON







 Command options 



* SUBNET: ID or name of the subnet.
* --vpc: ID or name of the VPC. It is only required to specify the unique resource by name inside this VPC.
* --name: The user-defined name for this reserved IP. Names must be unique within the subnet that the reserved IP resides in. Names beginning with ibm- are reserved for provider-owned resources.
* --address: The IP address to reserve, which must not already be reserved on the subnet. If not specified, an available address on the subnet is automatically selected.
* --auto-delete: Indicates whether this reserved IP member automatically deletes when either target is deleted, or the reserved IP is unbound. Must be false if the reserved IP is unbound. One of: true, false. (default: false).
* --target: The ID or name of the target resource. The following types are supported target resource types: endpoint_gateway.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is subnet-reserved-ip-update 

Update a reserved IP.

ibmcloud is subnet-reserved-ip-update SUBNET RESERVED_IP [--vpc VPC] [--name NEW_NAME] [--auto-delete true | false] [--output JSON] [-q, --quiet]



 Command examples
* --sgs: Comma-separated security group IDs or names for primary network interface.
* --rip: ID or name of the existing reserved IP.
* --address: The IP address to reserve, which must not already be reserved on the subnet.
* --auto-delete: If set to true, this reserved IP automatically deletes when the target is deleted. One of: true, false. (default: true).
* --ip-name: The user-defined name for this reserved IP. Names must be unique within the subnet that the reserved IP resides in. Names beginning with ibm- are reserved for provider-owned resources.
* --allow-ip-spoofing: Disables the source and destination checks on this interface. If false, source IP spoofing is not allowed on this interface. One of: false, true.
* --primary-network-interface: PRIMARY_NETWORK_INTERFACE_JSON|@PRIMARY_NETWORK_INTERFACE_JSON_FILE, primary network interface in JSON or JSON file. For the data schema, see the primary_network_interface property in the [API documentation](https://cloud.ibm.com/apidocs/vpccreate-instance).
* --network-interface: NETWORK_INTERFACE_JSON|@NETWORK_INTERFACE_JSON_FILE, network interface attachment in JSON or JSON file. For the data schema, see the network_interfaces property in the [API documentation](https://cloud.ibm.com/apidocs/vpccreate-instance).
* --default-trusted-profile: ID or name of the trusted profile.
* --default-trusted-profile-auto-link: If set to true, the system creates a link to the specified target trusted profile during instance creation. Regardless of whether a link is created by the system or manually by using the IAM Identity service, it automatically deletes when the instance is deleted. One of: true,false. (default: true).
* --metadata-service, --ms: Enable or disable the Instance Metadata Service. One of: true, false.
For more information, see [Placement groups](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-placement-groups).







 September 2018 



 26 September 2018 

Reserved servers now available
: Reserved servers offer guaranteed resources for future deployments and with one or three year contract terms, offers you cost savings. You can reserve up to 20 virtual server instances of a specific size. Reserved capacity must be provisioned first before other virtual server instances. For more information, see [Reserved virtual servers](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-about-reserved-virtual-servers).
Message: The reserved IP is in use and cannot be deleted.

To see a list of reserved IP addresses, use the GET /v1/subnets/{subnet_id}/reserved_ips API, or the CLI command ibmcloud is subnet-reserved-ip and make sure that the specified reserved IP address is not in use.





 reserved_ip_owned_by_provider 

Message: The specified reserved IP is owned by the provider.

To see a list of reserved IPs, use the GET /v1/subnets/{subnet_id}/reserved_ips API, or the CLI command ibmcloud is subnet-reserved-ip and make sure that the specified reserved IP is not owned by a provider.





 address_is_already_reserved 

Message: The specified address is already reserved on the subnet.

To see a list of reserved IPs, use the GET /v1/subnets/{subnet_id}/reserved_ips API, or the CLI command ibmcloud is subnet-reserved-ip and make sure that the specified address is not already reserved.





 security_group_active_transactions 

Message: The interface cannot be attached or detached until the instance appears in Active state.

The instance must be active before its network interfaces can be attached to a security group. Use GET /v1/instances/{id}?version=$version&generation=1 or ibmcloud is instance to check on the status of the instance. Once the status is running, try again. If this problem persists, [contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support).





 security_group_already_attached 

Message: The interface is already attached to the security group.

The interface is already attached to the security group. Use GET /v1/security_groups/{id}/network_interfaces?version=$version&generation=1 or ibmcloud is security-group-network-interfaces to view attached interfaces.
On the Bare metal server details page, scroll to the Network Interfaces section and click Edit of a network interface.
4. On Edit network interface, select a reserved floating IP or Reserve a new floating IP.
5. Click Save







 Attach a floating IP by using the CLI 

You need the following information to attach a floating IP to the bare metal server:



* Bare metal server ID
* Network interface ID
* Floating IP ID



Use the [List the network interfaces](https://cloud.ibm.com/docs/vpc?topic=vpc-infrastructure-cli-plugin-vpc-referencebare-metal-server-network-interfaces) command to find the ID of the network interface. Use the [ibmcloud is floating-ips](https://cloud.ibm.com/docs/vpc?topic=vpc-infrastructure-cli-plugin-vpc-referencefloating-ips) command to find the reserved floating IP IDs, or, use the [ibmcloud is floating-ip-reserve](https://cloud.ibm.com/docs/vpc?topic=vpc-infrastructure-cli-plugin-vpc-referencefloating-ip-reserve) command to reserve a new one.

After you collect all the required information, use the following command to attach the floating IP to the bare metal server:

ibmcloud is bare-metal-server-network-interface-floating-ip-add $bare_metal_server_id $network_interface_id $floating_ip_id





 Attach a floating IP by using the API 

You need the following information to attach a floating IP to a network interface of the bare metal server:



* Bare metal server ID
* Network interface ID
* Floating IP ID



Use the [List all network interfaces](https://cloud.ibm.com/apidocs/vpclist-bare-metal-server-network-interfaces) command to find the ID of the network interface.