vania-janet/multiturn-rag-retrieval-data huggingface dataset:
[Provision the instance](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers).
4. Navigate to Advanced options and enable Metadata.



For more information about creating virtual server instances, see [Creating virtual server instances by using the UI](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers).







 Disable the metadata service by using the UI 

This procedure shows how to disable the metadata service for an instance on which it is enabled. By default, the metadata service is disabled when you create a new instance.



1. In the [IBM Cloud console](https://cloud.ibm.com/login), go to menu icon ![menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Compute > Virtual server instances.
2. Click an instance from the list to go to its details page.
3. Under Metadata, the click the toggle button off (appears gray).





 Enable or disable the metadata service on instance templates by using the UI 

When you create an [instance template](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-auto-scale-instance-group&interface=uicreating-instance-template), the enable metadata service toggle is disabled by default. Click the toggle to enable the service.

When you view the details of an existing instance template, the page indicates whether metadata was enabled or not for the template. You can't change the instance template metadata setting after you create the template.







 Enable or disable instance metadata from the CLI 

Use the CLI to enable the metadata service when you create a new instance or on an existing instance.

Before you begin:



1. Before you can use the CLI, you must install the IBM Cloud CLI and the VPC CLI plug-in.
Error message troubleshooting 

This topic provides information on common error messages that you might encounter while creating or updating an instance of IBM Cloud® Load Balancer.



Error messages

 Error Explanation Solution 

 The maximum number of load balancers 'n' has been reached. Only 50 load balancer instances are allowed per account. Ensure you have 50 or less load balancer instances per account. 
 The maximum number of given protocols 'n' in load balancer product order has been reached. Only two protocols can be added while provisioning a load balancer. If you need more protocols, then after provisioning, you can add up to ten from the Protocols tab in the Load Balancer management flow. For more information, see [monitoring and managing your service](https://cloud.ibm.com/docs/loadbalancer-service?topic=loadbalancer-service-monitoring-and-managing-your-service). 
 The maximum number of given server instances 'n' in load balancer product order has been reached. Only ten servers can be added while provisioning a load balancer. If you need additional servers, then after provisioning, you can add up to 50 from the Server Instances tab in the Load Balancer management flow. For more information, see [monitoring and managing your service](https://cloud.ibm.com/docs/loadbalancer-service?topic=loadbalancer-service-monitoring-and-managing-your-service). 
 Load balancer name must be a string and have at least 1 and up to 40 characters. The load balancer name is mandatory. Use only alphanumeric characters (or special characters '-' and '.') for the name. The name must not begin or end with a special character, and must be limited to 40 characters in length. Enter a unique load balancer name. For example, "ui-servers" or "backend-servers". 
 Format error found in given load balancer name. The load balancer name is mandatory. Use only alphanumeric characters (or special characters '-' and '.') for the name.
You can have a total of 128 VMware ESXi™ servers in a multisite configuration across all instances.

If your configuration requires a multisite deployment with more than 128 ESXi servers, open an IBM Support ticket by following the steps in [Contacting IBM Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support).

The following graphic depicts the overall view of the vCenter Server multisite deployment.

Zoom

![vCenter Server multisite deployment](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/multisite-hub-spoke.svg)

Figure 1. vCenter Server multisite deployment

The model contains the following layers:



* Primary instance - To deploy the first instance in a multisite configuration, you define that instance as primary during the instance order process.
* Secondary instances - In a multisite configuration, you define the instances that are attached to the primary instance as secondary instances during the order process.



You can assign only one secondary instance to a primary instance at a time. You cannot assign multiple secondary instances to a primary instance at the same time. To do that, you must go through the order process again and select the previously defined primary instance as a primary instance for the secondary instance. You must repeat the process for all secondary instances that you want to create.

You can have a maximum of 15 (one primary and 14 secondary) instances that are deployed in a multisite configuration.

Deleting vCenter Server instances that are part of a multisite configuration requires special planning. For more information, see [Deleting vCenter Server instances in a multisite configuration](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_deletinginstance_multi).





 Related links
Bandwidth allocation is also realized when you add a secondary volume using POST / volume_attachments or delete a volume using DELETE volume_attachments.





 Retrieving the virtual server instance identifier 

When a virtual server instance is created, that instance is automatically assigned an instance identifier (ID), which includes the SMBIOS system-uuid as a portion of the ID. The ID can be up to 64 bytes in length and it consists of digits, lower-case letters, underscores, and dashes.

IDs are immutable, globally unique, and never reused, so the ID uniquely identifies a particular instantiation of a virtual server instance across all of IBM Cloud. The ID, including the SMBIOS system-uuid portion, is static and persists for the lifecycle of the virtual server instance until that virtual server instance is deleted.

From within your virtual server, you can retrieve the instance identifier in one of the following ways:

Linux

dmidecode -s system-family

Windows

Get-WmiObject Win32_ComputerSystem | Select-Object -ExpandProperty SystemFamily

From within your virtual server, you can retrieve the SMBIOS system-uuid in one of the following ways:

Linux

dmidecode -s system-uuid

Windows

Get-WmiObject Win32_ComputerSystemProduct | Select-Object -ExpandProperty UUID

For z/OS virtual server instances, you can SSH into the instance, and then run the DISPLAY IPLINFO command. When the [IEE254I](https://www.ibm.com/docs/en/zos/2.5.0?topic=iee399i-iee254i) message is displayed, the ID is included in the VM EXT NAME.





 Viewing instance status and lifecycle_state in the API 



* status



* This property provides the current status of the virtual server instance through the [Retrieve an instance](https://cloud.ibm.com/apidocs/vpc/latestget-instance) request. The values that status returns are specialized for virtual server instances and indicate if it is running, stopped, or transitioning.
They are responsible for processing incoming requests that are assigned to them by the ICM. Each server process is multi-threaded, and can therefore process many requests simultaneously.



2. System Central Services instance (SCS instance) - Central services form the basis of communication and synchronization for the AS Java cluster. They are responsible for lock administration, message exchange, and load balancing within the cluster. Central services that are run on one physical machine and constitute a separate instance. This [SAP Central Services Instance (SCS)](https://help.sap.com/viewer/5bdacafd0bbd41648f4b80093a1bf9d6/7.4.19/en-US/480728f74c6a3837e10000000a42189b.html) comprises:



* Message Server - The message server keeps a list of all server processes in the AS Java cluster and provides information about their availability to Internet Communication Manager (ICM). It also represents the infrastructure for data exchange between the participating server processes.
* Enqueue Server - The enqueue server manages logical locks. The enqueue server runs on the Central Services instance of the Java cluster. It manages the lock table in the main memory and receives requests for setting or releasing locks. It maps the logical locks to the database.





SAP HANA for standard system



* Primary application server instance (PAS) - The global directories of the ASCS instance can be used as the global file system. That means that the host with the ASCS instance is the SAP global host. However, you can also separately install the global directories on any host of your SAP system landscape.  You can also use the SAP transport host or the host with the global file system (SAP global host) as your primary application server instance host.  Optionally, you can install one or more additional application server instances.
* Database instance (DB) - To assist your project's planning phase, more design considerations are provided at SAP AnyDB – SAP HANA database with IBM Cloud for SAP.
Notice that users in the account that have permissions to view logs through the logging web UI can export data by using the API if they have an active service key. A user, with a policy in IAM to view logs, can also view service keys that an administrator has created. If you do not want users to be able to export data locally, service keys must be deleted.





 Step 7. Archiving logs 

When you archive logs from a logging instance to a Object Storage (COS) bucket, consider the following information:



* When you provision an instance of the COS service, this instance is a global one in your account. It is not region bound.
* You must configure a bucket that complies with the EU-Supported and GDPR regulations. For the list of COS EU-supported endpoints, see [EU-supported endpoints](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-endpointsendpoints-eu-managed).

For example, consider the following scenarios:



* For a bucket with single site resiliency, you can create the bucket in Amsterdam or Milan.
* For a bucket with regional resiliency, you can create the bucket in the EU-DE location to keep the data in Frankfurt.
* For a bucket with cross region resiliency, you can create the bucket in the eu-geo location. Data is kept within the EU geography across datacenters that are located in Milan, Amsterdam, and Frankfurt.



* You must restrict user access to manage archived log files in these buckets.
* Users are responsible for downloading files to EU-supported locations.



To learn how to configure archiving for your logging instance, see [Archiving logs](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-archiving).





 Step 8. Querying archived logs with SQL Query service 

Data Engine provides a serverless, no-ETL solution to easily query data stored in COS. [Learn more](https://cloud.ibm.com/docs/sql-query?topic=sql-query-overview).
Testing serverless apps 

Test each entity that you create to verify that your serverless app is working or to troubleshoot where an issue might be occurring.



 Testing actions from the console 

Whenever you create or update an action or sequence in the console, test it by using the Invoke option.



1. From the [Action](https://cloud.ibm.com/functions/create) menu, select an action or a sequence.
2. Select Invoke.







 Testing actions from the CLI 

You can test actions by running the [ibmcloud fn action invoke](https://cloud.ibm.com/docs/openwhisk?topic=cloud-functions-cli-plugin-functions-clicli_action_invoke) command. You can test the action with or without parameters.

ibmcloud fn action invoke --result ACTION_NAME --param PARAMETER VALUE

The following invocation runs a Hello world example.

ibmcloud fn action invoke --result myAction --param name stranger

The following example shows possible output from the previous invocation.

{
"greeting": "Hello stranger!"
}



 Testing parameters stored in JSON files 

You can pass a file of JSON-formatted parameters.

ibmcloud fn action invoke --result ACTION_NAME --param-file JSON_FILE

The following example shows possible output from the previous invocation.

{
"payload": "Hello, Dorothy from Kansas"
}





 Testing parameters entered in JSON format 

You can pass JSON-formatted parameters with your invocation.

ibmcloud fn action invoke --result ACTION_NAME -p person '{"PARAM_NAME": "PARAM_VALUE", "PARAM_NAME": "PARAM_VALUE"}'

The following example shows possible output from the previous invocation.

{
"payload": "Hello, Dorothy from Kansas"
}





 Testing blocking actions 

The invocation of the action can be blocking or non-blocking. Invocations are non-blocking by default.
You can provision an instance with an existing volume by specifying the existing volume's id or crn subproperty as the value of the boot_volume_attachment property.

The existing, bootable volume must be an unattached bootable volume that has the same operating system and architecture as the instance profile. Use the [list volumes](https://cloud.ibm.com/apidocs/vpc/latestlist-volumes) filter and reference the attachment_state property and operating_system property to view a volume's eligibility.

For example, to see unattached volumes in us-south-1 with an x86 operating system.

curl -X GET "$vpc_api_endpoint/v1/volumes?version=2023-02-08&generation=2?attachment_state=unattached&zone.name=us-south-1&operating_system.architecture=amd64"
-H "Authorization: Bearer $iam_token"

By default, a boot volume that is created as part of provisioning a virtual server instance is deleted when the instance is deleted. You can control this behavior by setting the delete_volume_on_instance_delete property to true when you create the instance or update the boot volume attachment.

Use the [POST /instances](https://cloud.ibm.com/apidocs/vpc/latestcreate-instance) method to create an instance with the information you gathered. The following call is an example of provisioning an instance by using an existing boot volume.

curl -X POST "$vpc_api_endpoint/v1/instances?version=2023-02-08&generation=2"
-H "Authorization: Bearer $iam_token"
-d '{
"boot_volume_attachment": {
"volume": {
"id": "r006-feec3e99-995e-4e8f-896b-48b42c7d05a7"
}
},
"keys": [
{
"id": "363f6d70-0000-0001-0000-00000013b96c"
Cannot connect to storage * Configure to send email one time when the Lost Storage Connectivity, Lost Storage Path Redundancy, Degraded Storage Path Redundancy, or Lost connection to NFS server critical events occur. [Identifying Fibre Channel, iSCSI, and NFS storage issues on ESX/ESXi hosts (1003659)g](https://kb.vmware.com/s/article/1003659) 
 Migration error * Configure to send email one time when the Cannot migrate VM, Migration error, Migration host error, Cannot relocate VM, or VM orphaned critical events occur. [vMotion or Storage vMotion of a VM fails with the error: The migration has exceeded the maximum switchover time of 100 seconds (2141355)](https://kb.vmware.com/s/article/2141355) 
 Exit standby error Not configured in vCenter Server instances as the use of DPM is not recommended. vSphere Distributed Power Management (DPM) provides power savings in on-premises deployments by dynamically consolidating workloads during periods of low resource utilization. VMs are migrated onto fewer hosts and the needed ESX hosts that are not needed are powered off. No power consumption savings can be realized by powering off IBM Cloud bare metal servers. 



The asterisk (*) denotes a stateless alarm. vCenter does not keep data on stateless alarms, does not compute, or display their status. Stateless alarms cannot be acknowledged or reset.





 Preconfigured alarms - vSAN 



* Alarm name - The name of the alarm visible in vCenter.
* Guidance - IBM Cloud for VMware Solutions guidance on the use of this alarm.
* More Information - Additional information available from IBM® or VMware to help with the resolution of these alarms when triggered.



If you have a vSAN cluster, the additional preconfigured alarms in the following table apply.



Table 2. Preconfigured alarms - vSAN

 Alarm name Guidance Details 

 Host flash capacity exceeds the licensed limit for vSAN Not considered essential for notification. Alarm that is reviewed as part of proactive daily checks. No additional information
Connecting to Linux instances 

After you created your Linux instance, you can connect to it by completing these steps.



  Getting connected 



1.  To connect to your instance, use your private key and run the following command:

ssh -i <path to your private key file> root@<floating ip address>

The user login 'root' is disabled by default in Fedora Core OS. The user login 'core' can be used to log in to Fedora Core OS instances.

You receive a response similar to the following example. When prompted to continue connecting, type yes.

The authenticity of host 'xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx)' can't be established.
ECDSA key fingerprint is SHA256:abcdef1Gh/aBCd1EFG1H8iJkLMnOP21qr1s/8a3a8aa.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'xxx.xxx.xxx.xxx' (ECDSA) to the list of known hosts.

You are now accessing your server.
2.  When you are ready to end your connection, run the following command:

 exit
Click Create virtual server instance when you are ready to provision.







 Next steps after an instance is created in the UI 

After the instance is created, you need to [associate a floating IP address to the instance](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-using-the-ibm-cloud-consolereserving-a-floating-ip-address). Then, you can connect to your instance. For more information, see [Connecting to your Linux instance](https://cloud.ibm.com/docs/vpc?topic=vpc-vsi_is_connecting_linux), [Connecting to your Windows instance](https://cloud.ibm.com/docs/vpc?topic=vpc-vsi_is_connecting_windows), or [Connecting to your z/OS instance](https://cloud.ibm.com/docs/vpc?topic=vpc-vsi_is_connecting_zos).

If you have an existing instance with a floating IP address, it isn't necessary to assign a second floating IP to another instance. You can connect to the first instance with a floating IP, then SSH to the second instance by using the private subnet IP address that is automatically assigned to it.





 Creating a virtual server instance by using the CLI 

You can create instances by using the command-line interface (CLI). If you would like to use user tags or access management tags to manage your resources, see [Working with tags](https://cloud.ibm.com/docs/account?topic=account-tag&interface=cli).

IBM Cloud CLI is not supported on LinuxONE (s390x processor architecture). However, you can install the CLI on another supported platform and use it with LinuxONE (s390x processor architecture) virtual server instances.



 Before you begin 



* Download, install, and initialize the following CLI plug-ins.



* IBM Cloud CLI
* The infrastructure-service plug-in
Enable or disable instance metadata by using the UI 

From the IBM Cloud® console, you can enable or disable the instance metadata service.



 Enable the metadata service for an existing instance by using the UI 

Use the UI to enable the metadata service on an existing instance.



1. Go to the list of instances. In the [IBM Cloud console](https://cloud.ibm.com/login), go to menu icon ![menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Compute > Virtual server instances.
2. Click the name of an instance to go to the details page.
3. On the details page, scroll to Metadata.
4. Click the toggle (appears green).







 Enable the metadata service when you create a new instance by using the UI 

The following procedure shows how to enable the metadata service when you create a new virtual server instance.



1. In the [IBM Cloud console](https://cloud.ibm.com/login), go to menu icon ![menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Compute > Virtual server instances.
2. Click Create.
3. [Provision the instance](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers).
4. Navigate to Advanced options and enable Metadata.



For more information about creating virtual server instances, see [Creating virtual server instances by using the UI](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers).







 Disable the metadata service by using the UI
"id": "b31c1a5a-122a-4e32-a10b-f2c31271de85",
"instance": {
"crn": "crn:...]",
"href": "https://us-south.iaas.cloud.ibm.com/v1/instances/33bd5872-7034-462b-9f3e-d400c49d347a",
"id": "33bd5872-7034-462b-9f3e-d400c49d347a",
"name": "instance-1",
"resource_type": "instance"
},
"name": "volume-attachment-1",
"type": "data"
}
],
"zone": {
"href": "https://us-south.iaas.cloud.ibm.com/v1/regions/us-south/zones/us-south-2",
"name": "us-south-2"
}
}





 Additional properties for boot volumes 

When you request to view details of boot volumes, two extra properties are returned in a GET /volumes and GET /volumes/{id} response.



* The active property indicates whether the virtual server instance to which a volume is attached is running or stopped. When active = true, the instance is running and operations that require a running instance such as creating an [image from that boot volume](https://cloud.ibm.com/docs/vpc?topic=vpc-create-ifvimage-from-volume-vpc-api) also work.
* The busy property indicates whether this volume is performing an operation that must be serialized. If an operation requires serialization, the operation fails unless this property is false.



Example response:

"active": "true",
"busy": "false",
"capacity": 100,
"created_at": "2022-12-08T06:26:17Z",
: Displays results in the requested format. The only valid value is json.
2. Run the following command to view details about the specific server instance:

ibmcloud hpvs instance (NAME | CRN) [--output json]

NAME
: The name of your instance.

Specify the CRN if your instance name is not unique.

CRN
: The server's Cloud resource name (CRN). Specify the CRN if NAME is not unique. You can run the ibmcloud hpvs instances command to get the CRN.

Command options

--output
: Displays results in the requested format. The only valid value is json.

Example output

Name hpvs-env-test
CRN crn:v1:bluemix:public:hpvs:..............::
Location <location>
Cloud tags
Cloud state active
Server status running
Plan Free
Public IP address 52.x.x.x
Internal IP address 172.x.x.x
Storage 50 GiB
Memory 2048 MiB
Processors 1 vCPUs
Image type self-provided
Image OS self-defined
Image name de.icr.io/hpvs_test/ubuntu:v2
Environment TEST_VAR=value
TEST_VAR2=value2
Last operation update succeeded
3. Complete the following steps to sign the images by using Red Hat simple signing:



1. Create a batch file and add the following content to it:

Key-Type: RSA
Key-Length: 4096
Subkey-Type: RSA
Subkey-Length: 4096
Name-Real: latestnewkey
Name-Email: latestnewkey@example.com
Expire-Date: 472
2. Create the keys.

gpg --pinentry-mode loopback --passphrase="" --generate-key --batch <batchfile>
3. Export the public key.