vania-janet/multiturn-rag-retrieval-data huggingface dataset:
When you provision a bare metal server, you have the following enhancement options to help make managing your server easier. Keep in mind that these options might vary depending on your server configuration.



 Dynamic inventory 

You can now see what servers are available in what data center when you provision a bare metal server. If a server is not available in the data center you selected, hover over the server name. A list is displayed that indicates the data centers in which the server is available. For more information about provisioning a bare metal server, see [Selecting from fast provisioning servers](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-bm-select-popular-servers).





 Network redundancy 

Port redundancy provides networking failover by maintaining a primary and secondary network port. If the primary port fails, the secondary (redundant) port enables.

Only one port is active at a time.

The following network redundancy options are available for bare metal servers.



Table 4. Network redunancy options

 Redundancy options Description 

 Automatic redundancy (Recommended option) Automatically configures the redundant ports for interface teaming through LACP (Link Aggregation Control Protocol) to preserve connectivity during routine maintenance. 
 User-managed redundancy Must have interface teaming configured on the host operating system to use network redundancy. Without interface teaming, connectivity during routine maintenance is not preserved. 
 No redundancy This is the only option for legacy data centers that don’t support automatic redundancy. This option is not recommended in a new data center. 
 Interface teaming (link aggregation) Combines, in parallel, multiple network connections to provide redundancy and increase network throughput. 



VMWare requires user-managed links.

For more information about network options, see [Network options](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-network-options).





 Block and file storage add-on 

If you need extra storage, IBM makes it easy! You can now order block and file storage (20 - 12,000 GB) when you provision a bare metal server.

Your add-on storage isn't automatically connected to your bare metal server.
"name": "serverless-instance",
"region_id": "us-south",
"account_id": "d628eae2ccxxxx3bb0c9dxxxx",
"reseller_channel_id": "",
"resource_plan_id": "8afxxxx-xxxx-xxxx-xxxx-946d843xxxx",
"resource_group_id": "65828fxxxx594594816exxx",
"resource_group_crn": "crn:v1:staging:public:resource-controller::a/d628eae2ccxxxx3bb0c9dxxxx::resource-group:65828fxxxx594594816exxx",
"target_crn": "crn:v1:staging:public:globalcatalog::::deployment:8afxxxx-xxxx-xxxx-xxxx-946d843xxxx%3Aus-south",
"parameters": {
"default_config": {
"spark.driver.cores": "1",
"spark.driver.memory": "512m",
"spark.executor.cores": "1",
"spark.executor.instances": "1"
},
"default_runtime": {
"additional_packages": "parquet-modular-encryption"],
"spark_version": "3.0.0"
},
"instance_home": {
"endpoint": "s3.direct.us-south.cloud-object-storage.appdomain.cloud",
"guid": "902xxxx-xxxx-xxxx-xxxx-4127da8xxxx",
"hmac_access_key": "xxxxxxxxx",
"hmac_secret_key": "xxxxxxxx",
"provider": "ibm-cos",
[solution tutorial icon](https://cloud.ibm.com/media/docs/images/homepage/solution-tutorial.svg) [Serverless web app and eventing for data retrieval and analytics](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-serverless-github-traffic-analytics)Serverless web app and eventing for data retrieval and analytics Solution tutorial

In this tutorial, you create an application to automatically collect GitHub traffic statistics for repositories and provide the foundation for traffic analytics. GitHub only provides access to the traffic data for the last 14 days. If you want to analyze statistics over a longer period of time, you need to download and store that data yourself. In this tutorial, you deploy a serverless app in a IBM Cloud Code Engine project. The app manages the metadata for GitHub repositories and provides access to the statistics for data analytics. The traffic data is collected from GitHub either on-demand in the app or when triggered by Code Engine events, e.g., daily. The app discussed in this tutorial implements a multi-tenant-ready solution with the initial set of features supporting a single-tenant mode.

![solution tutorial icon](https://cloud.ibm.com/media/docs/images/homepage/solution-tutorial.svg) [Serverless web application and API with Code Engine](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-serverless-webapp)Serverless web application and API with Code Engine Solution tutorial

In this tutorial, you will create a serverless web application using a bucket in Object Storage and implementing the application backend using IBM Cloud Code Engine and IBM Cloudant as JSON document database.

!
Location: us-south
State: provisioning
Type: service_instance
Sub Type:
Service Endpoints: public
Allow Cleanup: false
Locked: false
Created at: 2021-11-29T07:20:40Z
Updated at: 2021-11-29T07:20:42Z
Last Operation:
Status create in progress
Message Started create instance operation
Show more

Make a note of the instance ID from the output. You will need the instance ID when you call instance management or Spark application management APIs. See [Spark application REST API](https://cloud.ibm.com/docs/AnalyticsEngine?topic=AnalyticsEngine-spark-app-rest-api).
5. [Track instance readiness](https://cloud.ibm.com/docs/watsonxdata?topic=watsonxdata-lh-provisioning-serverlesslh-instance-readiness).







 Creating a service instance by using the Resource controller REST API 

An IBM Analytics Engine serverless instance must reside in an IBM Cloud® resource group. As a first step toward creating an IBM Analytics Engine serverless instance through the Resource controller REST API, you must have the resource group ID and serverless plan ID close at hand.

To create a service instance by using the Resource controller REST API:



1. Get the resource group ID by logging in to the IBM Cloud® CLI and running the following command:

ibmcloud resource groups

Sample result:

Retrieving all resource groups under account <Account details..>
OK
Name ID Default Group State
Default XXXXX true ACTIVE
2. Use the following resource plan ID for the Standard Serverless for Apache Spark plan:

8afde05e-5fd8-4359-a597-946d8432dd45
3. Get the IAM token. For instructions, see [steps](https://cloud.ibm.com/docs/AnalyticsEngine?topic=AnalyticsEngine-retrieve-iam-token-serverless).
4. Create an instance by using the Resource controller REST API:
Leave Container image selected and use icr.io/solution-tutorials/tutorial-serverless-api-webapp:latest as Image reference. It uses an already existing container image.
4. Go to and expand the section Runtime settings. Increase the Min number of instances to 1 and reduce Max number of instances to 2. The minimum of one makes the app more responsive during the initial tests. You could reduce it later to zero again.
5. Under Instance resources, select 0.25 vCPU / 0.5 GB for CPU and memory. Not much of resources is needed for this type of app.
6. Click Create to deploy the new backend app for the guestbook.
7. Create a service binding to the database.



1. Click Service bindings tab.
2. Click Create.
3. Click IBM Cloud service instance and choose your database from the drop down.
4. Click Add.



8. Wait for the provioning to report as green and ready. Click on Test application, then on Application URL. The backend app should load and return a page saying healthy. Remember or copy the application URL because it is needed for the next part.



Instead of using the pre-built container image, you could build the image on your own. This can be done either outside of or [with the help of Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-plan-build). If not using the pre-built container image and if [using a private container registry additional steps might be needed](https://cloud.ibm.com/docs/codeengine?topic=codeengine-deploy-app-private). You can find the source at [https://github.com/IBM-Cloud/serverless-guestbook/tree/ce](https://github.com/IBM-Cloud/serverless-guestbook/tree/ce)







 Step 3: Deploy the web app
A need is created for an elastic system where normal workload might be small, but needs to scale quickly with predictable response time. So the ability to handle many simultaneous events with no prior warning to the system is desirable. It is difficult to build a system to meet these requirements that use traditional server architectures. As they tend to either be underpowered, and unable to handle peak load in traffic, or be over-provisioned and highly expensive.

It is possible to implement IoT applications that use traditional server architectures. However, usually the combination of different services and data bridges requires high performance and flexible pipelines. Spanning from IoT devices up to cloud storage, and an analytics platform. Often pre-configured bridges lack the programmability to implement and fine-tune a particular solution architecture. Given the variety of pipelines, and the lack of standardization around data fusion in general (IoT in particular), it is common to see environments where the pipeline requires custom data transformation. These custom data transformations apply to format conversion, filtering, or augmentation. Cloud Functions is an excellent tool to implement such a transformation, in a serverless manner, where the custom logic is hosted on a fully managed and elastic cloud platform.

Look at the following sample IoT application that uses Cloud Functions, Node-RED, Cognitive, and other services: [Serverless transformation of IoT data-in-motion with Cloud Functions](https://medium.com/openwhisk/serverless-transformation-of-iot-data-in-motion-with-openwhisk-272e36117d6c).





 API backend 

Serverless computing platforms give developers a rapid way to build APIs without servers. Cloud Functions supports automatic generation of REST API for actions.

Additionally, Cloud Functions actions can be connected to an API Management tool of choice. Similar to other use cases, all considerations for scalability, and other Qualities of Services apply.

See the following example that includes a discussion of [using Serverless as an API backend](https://martinfowler.com/articles/serverless.htmlACoupleOfExamples).





 Mobile back end 

Many mobile applications require server-side logic.
Only static compute nodes can be deployed on dedicated hosts.
* When using Spectrum Scale for shared storage in the cluster.



* Where can I find the custom image name to image ID mappings for each cloud region?

The mappings can be found in the image-map.tf file and the scale-image-map.tf file in this public [GitHub repository](https://github.com/IBM-Cloud/hpc-cluster-symphony).
* Why can't I disable hyper threading?

Hyper threading is used on Intel® microprocessors, which allows a single microprocessor to act like two separate processors to the operating system. With the latest release of Spectrum Scale that's accessible by Spectrum Symphony compute nodes, the automation code uses the RHEL 8.4 custom image version (see [Release notes](https://cloud.ibm.com/docs/hpc-spectrum-symphony?topic=hpc-spectrum-symphony-release-noteshpc-spectrum-symphony-jun3022)). An issue with that image version has been identified that impacts being able to disable hyper threading. When the issue is resolved, there will be an update to this feature.
* Why does the egosh command not work if tried immediately after Schematics provisions the cluster?

This is expected behavior. Even after the Schematics web console shows that the cluster is successfully provisioned, there are still some tasks that run in the background for several minutes. Allow a few minutes (typically 2 minutes is sufficient) after the cluster gets provisioned for egosh to be available.
* Why does cluster creation using dedicated hosts fail sometimes with the error status of dedicated host is failed?

In some regions, dedicated hosts have a limitation on the number of virtual server instances that can be placed on them at one time. You can try to provision the cluster with a smaller number of virtual server instances to overcome this.



Power Systems Virtual Servers



* What is IBM Power Systems Virtual Server?

IBM Power Systems Virtual Server is a hosted infrastructure offering that allows you to quickly integrate with the Internet for on-demand provisioning.
ibmcloud resource service-instance-create MyServiceInstance ibmanalyticsengine standard-serverless-spark us-south -p @provision.json

You can give the service instance any name you choose. Note that currently, standard-serverless-spark is the only supported serverless plan and us-south and eu-de the only supported regions.

The provision.json file contains the provisioning parameters for the instance that you want to create.

The endpoint to your IBM Cloud® Object Storage instance in the payload JSON file must be the direct endpoint. Direct endpoints provide better performance than public endpoints and do not incur charges for any outgoing or incoming bandwidth.

Following is a sample provision.json file.

{
"default_runtime": {
"spark_version": "3.3"
},
"instance_home": {
"region": "us-south",
"endpoint": "https://s3.direct.us-south.cloud-object-storage.appdomain.cloud",
"hmac_access_key": "<your-hmac-access-key",
"hmac_secret_key": "<your-hmac-secret-key"
},
"default_config": {
"key1": "value1",
"key2": "value2"
}
}

The IBM Cloud® response to the create instance command:

Creating service instance MyServiceInstance in resource group Default of account <your account name> as <your user name>...
OK
Service instance MyServiceInstance was created.

Name: MyServiceInstance
ID: crn:v1:staging:public:ibmanalyticsengine:us-south:a/d628eae2cc7e4373bb0c9d2229f2ece5:1e32e-afd9-483a-b1-724ba5cf4::
The [list all bare metal servers](https://cloud.ibm.com/apidocs/vpc/latestlist-bare-metal-servers) and [retrieve a bare metal server](https://cloud.ibm.com/apidocs/vpc/latestget-bare-metal-server) methods now provide lifecycle_reasons and lifecycle_state properties. A bare metal server that violates IBM Cloud’s [Acceptable Use Policy](https://www.ibm.com/services/us/imc/html/aup1.html) will now have its lifecycle_state property set to suspended. A suspended bare metal server is automatically powered off and you cannot update, delete, or power it on. For more information, see [Viewing bare metal status and lifecycle_state in the API](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-bare-metal-servers&interface=api) and [Resource suspension](https://cloud.ibm.com/docs/vpc?topic=vpc-resource-suspension).







 11 April 2023 



 For all version dates 

Console type configuration for bare metal server profiles. When you [retrieve a bare metal server profile](https://cloud.ibm.com/apidocs/vpc/latestget-bare-metal-server-profile) or [list all bare metal server profiles](https://cloud.ibm.com/apidocs/vpc/latestlist-bare-metal-server-profiles), the response now provides a console_types property that denotes the console type configuration for a bare metal server with this profile.

Network interface configuration for bare metal server profiles. When you [retrieve a bare metal server profile](https://cloud.ibm.com/apidocs/vpc/latestget-bare-metal-server-profile) or [list all bare metal server profiles](https://cloud.ibm.com/apidocs/vpc/latestlist-bare-metal-server-profiles), the response now provides a network_interface_count property.
* CATALOG-OFFERING: is crn:v1:public:globalcatalog-collection:global:a/efe5afc483594adaa8325e2b4d1290df:0b322820-dafd-4b5e-b694-6465da6f008a:offering:136559f6-4588-4af2-8585-f3c625eee09d
* KEYS: r134-89ec781c-9630-4f76-b9c4-a7d204828d61
* PLACEMENT_GROUP: c5f1f366-b92a-4080-991a-aa5c2e33d96b



Information about the network interfaces that are created for the new instance aren't returned after the instance is created. You can view the information by using the ibmcloud is instance INSTANCE command as described in the following step.

The status of the virtual server instance displays pending until the instance is created.

For a full list of command options, see [ibmcloud is instance-create](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-referenceinstance-create).
2. Next, run the following instance details command to verify that you can see your new instance and view the network interfaces that were created for the new instance. For INSTANCE specify the ID that was assigned to your new virtual server instance in the previous step.

ibmcloud is instance INSTANCE

The status now shows running. Check the Network Interfaces section to locate the ID of the network interface.
3. Request a floating IP address to associate to your instance by using the following command. For FLOATING_IP_NAME specify a name for your floating IP, and for TARGET_INTERFACE specify the ID of the network interface that you identified in the previous step.

ibmcloud is floating-ip-reserve FLOATING_IP_NAME --nic TARGET_INTERFACE

Record the floating IP Address to use later.
No, a virtual server instance can be provisioned in only one VPC.
* During floating IP assignment in a VPC, a customer must specify the network interface of the instance, is that correct?

Yes. Initially, assigning the floating IP to the primary network interface of a server helps establish the data path. Later, you can associate the floating IP to a different network interface if you want. Alternatively, you can manually configure routing for the interface in the guest operating system. For more information, see [Adding or editing network interfaces](https://cloud.ibm.com/docs/vpc?topic=vpc-using-instance-vnicsediting-network-interfaces).
* Imagine that instance1 in a VPC has only vNIC1 and it is attached to Subnet1. Subnet1 is attached to a Public Gateway (PGW). Can a customer still assign a floating IP to instance1?

Yes, a server can be on a subnet that is attached to a public gateway and also have a floating IP. The assignment of floating IP to an instance is not related to whether a public gateway is attached to the subnet. A floating IP associated to an instance takes precedence over the public gateway that is attached to the subnet.
* What regions are available?

You can create virtual server instances for IBM Cloud® Virtual Private Cloud in Dallas (us-south), Washington DC (us-east), London (eu-gb), Sydney (au-syd), Tokyo (jp-tok), Osaka (jp-osa), Frankfurt (eu-de), Madrid (eu-es), Toronto (ca-tor), and São Paulo (br-sao).
* Can I use existing virtual server instances from my classic infrastructure with an IBM Cloud VPC?

You can migrate a virtual server instance from the classic infrastructure to a VPC. You need to create an image template, export it to IBM Cloud Object Storage, and then customize the image to meet the requirements of the VPC infrastructure.
* With the server processor model number, go to the [Intel Processor Finder](http://processorfinder.intel.com) and use this number to find more information about the processor and whether it supports Enhanced Intel SpeedStep Technology.



EIST is an established technology. It's not common that you need to turn off EIST. However, if you decide that you don't want to use this feature, open a support case with the Support Team to disable this feature. The server is restarted when you disable EIST.





 What if my bare metal server has out-of-date firmware? 

It's important to keep firmware updated to make sure that your bare metal server has optimal device compatibility and stability. If a Bare Metal Servers firmware version is out of date, firmware can be updated by selecting the bare metal server from the device list and click Update Firmware from the action menu.

You can also initialize a firmware update during the [OS Reload](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-reloading-the-os) process within the [IBM Cloud](https://cloud.ibm.com/).

You can't initialize a firmware update when a bare metal server is powered ON. Make sure that the bare metal server is powered OFF before you initialize a firmware update.





 What happens to drives in bare metal servers when I cancel the server? 

When a server is cancelled, the reclaim process starts and any associated drives are wiped by using DOD 5220.22-M algorithms. These algorithms use a 3-pass overwrite process to securely erase data. The reclaim is tracked through the serial numbers on the drives. After the drives are wiped, the server moves into provisioning for reassignment.





 What happens to a bare metal drive if it malfunctions? 

A drive malfunction prompts manual intervention and the drive is set to end of life. The end of life process initiates when the drive malfunctions or if the age or size is beyond support. When any of these conditions occur, the drive is wiped as mentioned in the previous section.
Bare metal server options 

Your IBM Cloud® bare metal server is an hourly or monthly, single-tenant server that is dedicated to you. Your server isn't shared in any part, including server resources, with other customers. You manage your server, which is provisioned without a hypervisor, and deployed in one or more data centers. Multiple Bare Metal Servers can communicate on the IBM Cloud virtual private network as if stationed on the same rack.



 Servers for every workload 

IBM Cloud has Bare Metal Servers to fit every workload. For more information, see [Bare metal servers](https://www.ibm.com/cloud/bare-metal-servers).



 Fast provisioning servers 

IBM Cloud offers preconfigured servers that meet the needs of most use cases. These servers are considered "fast provision" because your compute options (number of cores, speed, RAM, and number of drives) are preset. Preset servers are ready to configure 30 - 40 minutes after provisioning.





 Custom-based servers 

If one of the fast provisioning servers don't meet your workload needs, you can customize your Bare Metal Servers to meet your needs. Customized servers are generally provisioned in 2 - 4 hours. The provisioning time depends on complexity, quantity, and testing options.





 SAP-certified bare metal servers 

IBM Cloud Bare Metal Servers are certified to support your SAP HANA and SAP NetWeaver workloads. For more information, see [SAP-certified infrastructure](https://www.ibm.com/cloud/sap/certified-infrastructure).





 VMware-certified servers 

IBM Cloud® provides the unique capability for you to provision dedicated Bare Metal Servers so you can deploy your own VMware®-based private cloud. For more information, see [Getting started with VMware](https://cloud.ibm.com/docs/vmware?topic=vmware-vmware-getting-started).







 Advanced hardware options 

IBM Cloud offers advanced hardware options to fit your workload needs.



 Intel Sapphire Rapids CPUs (Beta) 

Sapphire Rapids processors are currently available as a beta offering and are available in only the DAL10 data center.