vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Bare metal server images 

When you provision a bare metal server on your VPC, you need to select an image to determine the operating system for the server.



 Supported images 

The following operating systems are available as images when you create a bare metal server.



Table 1. Bare metal server images

 Image Architecture 

 CentOS 7.x x86-64 
 CentOS Stream 9.x x86-64 
 [Custom image](https://cloud.ibm.com/docs/vpc?topic=vpc-bare-metal-imagebare-metal-custom-images) x86-64 
 Debian 11 x86-64 
 Microsoft Windows 2016 Full standard, 2019 Full standard, 2022 Full standard x86-64 
 [Red Hat Enterprise Linux](https://cloud.ibm.com/docs/vpc?topic=vpc-bare-metal-imagebare-metal-images-rhel-considerations) 8.4, 8.6 x86-64 
 Red Hat Enterprise Linux for SAP x86-64 
 SUSE Red Hat Enterprise Linux for SAP<br><br>For more information about SAP and bare metal servers, see [SAP fast path for IBM Cloud Intel bare metal servers](https://cloud.ibm.com/docs/sap?topic=sap-fast-path-site-map-intel-bm). x86-64 
 [Ubuntu](https://cloud.ibm.com/docs/vpc?topic=vpc-bare-metal-imagebare-metal-images-ubuntu-considerations) 22, 20.04 x86-64 
 [VMware ESXi](https://cloud.ibm.com/docs/vpc?topic=vpc-bare-metal-imagebare-metal-images-vmware-esxi-considerations) x86-64 





 Special considerations for Red Hat Enterprise Linux 8.4 

By default, the release lock feature for RHEL 8.4 is disabled. To prevent the RHEL from going beyond version 8.4 when you run an update, run the following commands from the command line:

 subscription-manager release --set=8.4

 yum clean all
[solution tutorial icon](https://cloud.ibm.com/media/docs/images/homepage/solution-tutorial.svg) [Provision Bare Metal Servers for VPC for VMware deployment](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmware-bms)Provision Bare Metal Servers for VPC for VMware deployment Solution tutorial

This tutorial will show how to provision Bare Metal Servers for VPC into IBM Cloud VPC, and how to provision network interfaces for vSphere VMkernel adapters (VMK) adapters.

![solution tutorial icon](https://cloud.ibm.com/media/docs/images/homepage/solution-tutorial.svg) [Provision Bare Metal Servers for VPC network interfaces for NSX-T ](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmware-nsx-t-vlannics)Provision Bare Metal Servers for VPC network interfaces for NSX-T Solution tutorial

In this tutorial, Bare Metal Servers for VPC VLAN network interfaces are created for NSX-T management and edge components. This phase is optional, if you plan to use NSX-T for your Virtual Machine networking.

![solution tutorial icon](https://cloud.ibm.com/media/docs/images/homepage/solution-tutorial.svg) [Provision IBM Cloud DNS Services for VMware deployment](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmware-dns)Provision IBM Cloud DNS Services for VMware deployment Solution tutorial

In this tutorial, you will deploy IBM Cloud DNS Services for a VMware Deployment in IBM Cloud VPC. IBM Cloud DNS Services will be used and your IBM Cloud VPC will be configured to access and use the deployed DNS serrvice.

!
FAQs for bare metal to bare metal migration 



 What is RMM server? 

RMM server is a software appliance that is offered by RackWare that replatforms your server from an IBM Cloud® classic bare metal server to an IBM Cloud classic bare metal server.





 Where can I find more information about RackWare RMM server? 

For RMM server overview information, see [RackWare's Cloud Migration documentation](https://www.rackwareinc.com/cloud-migration).

For RMM server usage guide information, see [RackWare RMM User's Guide for IBM Cloud](https://www.rackwareinc.com/rackware-rmm-users-guide-for-ibm-cloud).





 How do I install the RMM server? 

This software is available in the IBM Cloud catalog in the Migration Tools category. After you complete the appropriate information, a virtual server instance is installed in a new VPC with the RMM already installed.





 What are the limitations for the bare metal to bare metal migration? 

For more information on limitations of the bare metal to bare metal migration, see [Bare metal to bare metal migration limitations](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-p-p-migration-bare-metal-overviewp-p-migration-bare-metal-limitations).





 What are supported operating systems for bare metal to bare metal migration? 

For more information on supported operating systems, see the [Bare metal to bare metal migration supported operating systems](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-p-p-migration-bare-metal-overviewp-p-migration-bare-metal-supported-os).





 How does RackWare handle bare metal servers with NIC bonding? 

The RMM migration tool does support migration over the bonded interface for classic to classic migration as well as on-premises to VPC migration. User intervention is not needed for migration with bonded interface.





 Is RMM a free service? 

RackWare RMM is a Bring-Your-Own-License (BYOL) subscription-based service.
ibmcloud sl vs options 

List options for creating virtual server instance:

ibmcloud sl vs options [OPTIONS]

Examples:

ibmcloud sl vs options

This command lists all the options for creating a virtual server instance, eg.datacenters, cpu, memory, os, disk, network speed, etc.





 ibmcloud sl vs pause 

Pause an active virtual server instance:

ibmcloud sl vs pause IDENTIFIER [OPTIONS]

Command options:

-f, --force
: Force operation without confirmation.

Examples:

ibmcloud sl vs pause 12345678 -f

This command pauses virtual server instance with ID 12345678 without asking for confirmation.





 ibmcloud sl vs power-off 

Power off an active virtual server instance:

ibmcloud sl vs power-off IDENTIFIER [OPTIONS]

Command options:

--hard
: Perform a hard shutdown.

--soft
: Perform a soft shutdown.

-f, --force
: Force operation without confirmation.

Examples:

ibmcloud sl vs power-off 12345678 --soft

This command gracefully powers off a virtual server instance with ID 12345678.





 ibmcloud sl vs power-on 

Power on a virtual server instance:

ibmcloud sl vs power-on IDENTIFIER [OPTIONS]

Command options:

-f, --force
: Force operation without confirmation.

Examples:

ibmcloud sl vs power-on 12345678

This command powers on a virtual server instance with ID 12345678.





 ibmcloud sl vs ready 

Check whether a virtual server instance is ready for use:

ibmcloud sl vs ready IDENTIFIER [OPTIONS]

Command options:

--wait
: Wait until the virtual server is finished provisioning for up to X seconds.

Examples:

ibmcloud sl vs ready 12345678 --wait 30

This command checks virtual server instance with ID 12345678 status to see whether it is ready for use continuously and waits up to 30 seconds.





 ibmcloud sl vs reboot
VMware vCenter Server 

For more information about [VMware vCenter Server](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_vcenterserveroverview) instances, see the following topics:



*  [Planning for vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_planning)
*  [Procedure to order vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_orderinginstance-procedure)
*  [Adding clusters to vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingclusters)
*  [Adding ESXi servers to vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservers)
*  [Adding NFS storage to vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingnfs)
*  [Ordering services for vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservices)
Click Sevices and select the category Analytics.
3. Search for Analytics Engine and then click on the tile to open the service instance creation page.
4. Choose the location in which you want the service instance to be deployed. Currently, us-south and eu-de are the only supported regions.
5. Select a plan. Currently, Standard Serverless for Apache Spark is the only supported serverless plan.
6. Configure the instance by entering a name of your choice, selecting a resource group and adding tags.
7. Select the default Spark runtime. You can choose between Spark 3.1 and Spark 3.3 runtimes. The runtime pre-installs the spatio-temporal, data skipping and Paquet modular encryption packages by default.
8. Select the IBM Cloud Object Storage instance from your account that you want to use as the instance home to store instance related data.
9. Add Spark configuration values to override default Apache Spark settings.
10. Click Create to provision the service instance in the background.

The newly created service is listed in your [IBM Cloud® resource list](https://cloud.ibm.com/resources) under *Services.







 Creating a service instance using the IBM Cloud command-line interface 

To create a service instance using the IBM Cloud® command-line interface:



1. Download and configure the IBM Cloud® CLI. Follow the instructions in [Getting started with the IBM Cloud® CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started).
2. Set the API endpoint for your region and log in:

ibmcloud api https://cloud.ibm.com
ibmcloud login
3. Get the list of the resource groups for your account and select one of the returned resource group as the target resource group in which to create the IBM Analytics Engine serverless instance:

ibmcloud resource groups
ibmcloud target -g <resource_group_name>
4. Create a service instance:
For more information, see the aws ec2 run-instances[command reference](https://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html).

Example command to run AWS EC2 instances.

aws ec2 run-instances --count COUNT --instance-type INSTANCE-TYPE --launch-template LaunchTemplateName=AWS-LAUNCH-TEMPLATE --user-data file://ATTACH-SCRIPT-LOCATION





 AWS instance types 

Review the following suggested [AWS EC2 instance types](https://aws.amazon.com/ec2/instance-types/) that you can use as hosts in IBM Cloud Satellite. You can use other AWS instance types as long as they meet the [minimum host requirements](https://cloud.ibm.com/docs/satellite?topic=satellite-host-reqs) for Satellite.



AWS instance types

 Instance vCPU Memory (GiB) Storage disk (GiB) Network bandwidth (Gbps) 

 m5d.xlarge 4 16 At least 100 GB SSD attached Up to 10 
 m5d.2xlarge 8 32 At least 100 GB SSD attached Up to 10 
 m5d.4xlarge 16 64 At least 100 GB SSD attached Up to 10 







 Security group settings for AWS 

As described in the [host networking requirements](https://cloud.ibm.com/docs/satellite?topic=satellite-reqs-host-network), your AWS hosts must have access to connect to IBM Cloud Satellite. If you use hosts in a virtual private cloud (VPC), you can create a security group similar to the following example. You can get the owner, group, user, and VPC IDs from your AWS provider resources.

The following example is a security group that you might create for AWS.

{
"Description": "Security group for IBM Cloud Satellite hosts",
"GroupName": "Satellite",
"IpPermissions": [{
"FromPort": 80,
"IpProtocol": "tcp",
"IpRanges": {
Using Object Storage as the instance home 

The instance home can be associated with the IBM Analytics Engine serverless instance:



* At the time the [instance is created](https://cloud.ibm.com/docs/AnalyticsEngine?topic=AnalyticsEngine-cos-serverlessdefine-instance)
* After the instance was created by using the [instance_home API](https://cloud.ibm.com/docs/AnalyticsEngine?topic=AnalyticsEngine-cos-serverlessusing-api)





 Defining IBM Cloud Object Storage as the instance home 

To define Object Storage as the instance home for your IBM Analytics Engine serverless instance:



1. Provision an Object Storage service instance in IBM Cloud®. See [Creating a new service instance](https://cloud.ibm.com/docs/cloud-object-storage/iam?topic=cloud-object-storage-provision).
2. After the instance was provisioned, generate service credentials and retrieve the HMAC access key ID.
3. Use the retrieved credentials to create an instance.





 Getting the Object Storage credentials 

You need to add the access credentials to the Object Storage instance in the JSON payload when you create an IBM Analytics Engine serverless instance and specify the instance home storage for the instance.

To get the Object Storage credentials:



1. Select the Object Storage instance under Storage from your IBM Cloud® resource list.
2. Select Service credentials in the navigation pane.
3. Click New credential and choose the following options:



1. Enter a credential name of your choice.
2. Choose the Writer role.
3. Under Advanced options:





* Choose Auto Generate for the Service ID.
* Turn on the option to include HMAC credential.





1. Click Add.



Zoom

![Shows creating Cloud Object storage credentials.]
Security model 

IBM Analytics Engine serverless instances provide a security architecture that is designed to enable administrators and developers to create secure Spark clusters.

The following sections describe how the security model of IBM Analytics Engine serverlesss instances manages the access to and control of the secure instances.



 Controlling access to IBM Analytics Engine activities 

Access to IBM Analytics Engine serverless instances is controlled by IAM authentication and authorization. IAM is the Identity and Access Management service of IBM Cloud®. User authentication and access control happens through IAM when you log in with your IBMId. See how to [retrieve the IAM token](https://cloud.ibm.com/docs/AnalyticsEngine?topic=AnalyticsEngine-retrieve-iam-token-serverless).

As an administrator or creator of the service instance, you can grant or deny access to other users with whom you may want to share the service instance. All activities on the service instance life cycle management, like modifying the instance configuration, submitting and tracking Spark applications or customizing the instance with custom library sets are controlled through IAM authentication and authorization. See [Granting permissions to users](https://cloud.ibm.com/docs/AnalyticsEngine?topic=AnalyticsEngine-grant-permissions-serverless) to understand which operations are supported and what is the level of access required for each of those operations.





 Encrypting at Rest 

IBM Cloud Object Storage is the recommended data store to store the data required for executing Spark jobs on the cluster. IBM Cloud Object Storage comes with default built-in encryption. See [Encrypting your data](https://cloud.ibm.com/docs/cloud-object-storage/basics?topic=cloud-object-storage-encryptionencryption).

In addition, or as an alternative to using IBM Cloud Object Storage storage encryption in analytic scenarios for large-scale data, you can use Parquet modular encryption, especially when fine-grained access control is important. See [Working with Parquet modular encryption](https://cloud.ibm.com/docs/AnalyticsEngine?topic=AnalyticsEngine-parquet-encryption-serverless).





 Encrypting endpoints
Setting up a bare metal server 

You can set up a Bare Metal Server as a dedicated server.



 Before you begin 



* Go to your console's device menu. For more information, see [Navigating to devices](https://cloud.ibm.com/docs/bare-metal?topic=virtual-servers-navigating-devices).
* Make sure that you have any necessary account permissions and device access. Only the account owner, or a user with the Manage Users classic infrastructure permission, can adjust the permissions.



For more information about permissions, see [Classic infrastructure permissions](https://cloud.ibm.com/docs/account?topic=account-mngclassicinfra) and [Managing device access](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-managing-device-access).





 Setting up a bare metal server 

Use the following steps to set up a Bare Metal Server:



1. From the menu, click Devices > Device list and find your system. All of your devices are detailed in the Device List, where you can manage devices, upgrade devices, or generate bandwidth usage charts.
2. Choose to manage your server in one of the following ways:



* Click the Device Name arrow to view a summary and manage your devices from the Snapshot view.
* Click the Device Name of the server to view a detailed list and manage your devices from the Device Details screen.



3. Record the IP address and credentials for the server in a safe location so that you can access the details quickly without needing to log in each time you need them. You can record these details for both an individual device and for all devices associated with your account:



* View individual device IPs from the Device List.
* View individual device root passwords in the Snapshot View for the device.
* View multiple device IPs by using the Download CSV option from the Device List. Then, select Download CSV from the Settings cog to download a full list of devices and details in spreadsheet format.



4. Update the credentials for operating systems and other software.
* Replication - [vSphere Replication Virtual Appliance](https://pubs.vmware.com/srm-51/index.jsp?topic=%2Fcom.vmware.srm.install_config.doc%2FGUID-E654F2D8-7D56-4A81-9568-E85172A7022D.html)
* Replication and disaster recovery
* Reliability - Tolerates up to three host failures with seven or more hosts. Failure domains were introduced in v6 of VMware.



The most recent version of vSAN is available from the IBM Cloud® catalog with CPU license billing base.





 QuantaStor 

You can use the [OSNexus Solution Design Guide](http://wiki.osnexus.com/index.php?title=Solution_Design_Guide) to help you connect VMware with QuantaStor.



* Recommended workloads - Tiers 2 and 3
* Performance - Variable based on the number of drives, RAID, and disk use (iSCSI or NFS)
* Scalability - v3 single frame supports 128 TB with no scale up or scale out.
* Protocols - iSCSI, NFS, and SMB
* Cost - High for both CapEx and OpEx
* HA - Not available
* Replication - Built-in replication features, SRA not available. Can use vSphere Replication Appliance too
* Reliability - Single point of failure for the enclosure and RAID controller.







 NetApp Data OnTap Select 

NetApp® ONTAP® Select on IBM Cloud®, a software-defined storage virtual appliance, extends existing data management capabilities by implementing NetApp ONTAP software as a service on IBM Cloud® dedicated bare metal servers. You can provision storage resources with agility and flexibility while your data is protected by using NetApp’s advanced data management functions. Such as the fast and efficient NetApp Snapshot® copies, FlexClone® copies, and SnapMirror® replication. NetApp ONTAP Select accelerates application DevOps and reduces the complexity and increased processor usage that are associated with physical storage systems.
Skylake servers are not supported for VMware vSphere® Enterprise Plus 7.0u1 instances.

NSX-T instances

NSX-V instances



Table 1. Options for Skylake bare metal servers - NSX-T instances

 CPU model Cores GHz RAM 

 Dual Intel® Xeon® Silver 4110 processor 16 2.1 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB 
 Dual Intel Xeon Gold 5120 processor 28 2.2 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB 
 Dual Intel Xeon Gold 6140 processor 36 2.3 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB 



VMware NSX-V is no longer supported for new deployments of vCenter Server instances V4.7 and later.





 Cascade Lake 

For Cascade Lake servers, you can choose the following CPU models and a supported RAM size, which depends on the NSX networking solution.

NSX-T instances

NSX-V instances



Table 2. Options for Cascade Lake bare metal servers - NSX-T instances

 CPU model Cores GHz RAM 

 Dual Intel Xeon Silver 4210 processor 20 2.2 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB 
 Dual Intel Xeon Gold 5218 processor 32 2.3 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB 
 Dual Intel Xeon Gold 6248 processor 40 2.5 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB 
 Dual Intel Xeon Gold 6250 processor 16 3.9 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB 
 Dual Intel Xeon Platinum 8260 processor 48 2.4 128 GB, 192 GB, 384 GB, 768 GB, 1.5 TB 
 Quad Intel Xeon Gold 6248 processor 80 2.5 384 GB, 768 GB, 1.5 TB, 3 TB 
 Quad Intel Xeon Platinum 8260 processor 96 2.4 384 GB, 768 GB, 1.5 TB, 3 TB
[Veeam on bare metal server deployment model for all-in-one server](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/veeam-bms-deployment-models-all-in-one.svg)

Figure 2. Veeam on bare metal server deployment model for all-in-one server

You can use other IBM Cloud Storage options as a capacity tier storage for redundancy or long-term retention with Veeam scale-out backup repository functions, if your compliance requirements allow the usage of shared storage resources. For example, Object Storage can be used to provide a highly durable place for low-cost and long-term backup storage when these backups do not require high levels of restore performance.

The backup solution is self-managed and you can customize it post deployment. For more information, see [Post deployment customization options with self-managed vCenter Server](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-veeam-bms-archi-post-deployment).



 Related links 



* [Veeam Backup & Replication](https://www.veeam.com/vm-backup-recovery-replication-software.html?ad=menu-products)
* [Veeam Help Center technical documentation](https://www.veeam.com/documentation-guides-datasheets.html?ad=menu-resources)
Refer to VMware® documentation for more details on capabilities and limitations.





 Multisite – single tenant 

Multisite – single tenant is also a common use case and network deployment pattern. This topology provides seamless site recovery by using dynamic routing protocols, such as BGP. The vCenter Server automation does not deploy multisite topology automatically. However, you can customize the default single-site topology post initial vCenter Server deployment. When you have the compute capacity in the required data center, you can deploy the required extra edge nodes manually. Then, you can create a new edge cluster for the Tier-0 and Tier-1 gateways though NSX-T. This overlay topology is highly scalable and it is possible to automate, for example by using Ansible and Terraform.

This option is suitable for customers with workloads that run on a multiple data center, single tenant, and do not have overlapping IP addresses inside their own workloads.

Overlapping IP addresses refers to overlay segments between customer environments that run on the vCenter Server instance.

The following diagram shows an example of a multisite – single tenant network topology. It consists of a two layer Tier-0 design with three edge clusters. For this, consider two edge clusters in the two data centers or zones in a multizone region. And also, one edge cluster deployed across the multizone region with edge nodes in each participating zone or data center.

Zoom

![Multisite – single tenant example topology](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/v2t-diagrams-2-zone.svg)

Figure 4. Multisite – single tenant example topology



1. The vCenter Server automation deploys a single site solution, which can be manually expanded to support the target multisite topology. The deployment includes a single vCenter and three NSX-T Managers that are deployed on the cluster on the initial IBM Cloud data center location.