vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Provisioning reserved capacity and instances 



 Before you begin 

You can provision your reserved capacity and instances through the IBM Cloud® catalog. You must provision your reserved capacity before your virtual server instances.

If you are not the account administrator, your user account must include the Manage Reserved Capacities permission. The account administrator can grant user's permission from the Portal Permissions tab in the console. For more information about updating permissions, see [Managing infrastructure access](https://cloud.ibm.com/docs/account?topic=account-mngclassicinframngclassicinfra).





 Provisioning reserved capacity 

In the IBM Cloud catalog, complete the following steps to provision your reserved capacity.



1. Open the [reserved virtual server instance](https://cloud.ibm.com/gen1/infrastructure/provision/vs?guestType=reserved&cm_sp=Cloud-Product-_-OnPageNav-IBMCloudPlatform_IBMVirtualMachines-_-VSI_Prod_Midpage) page from the catalog.
2. To create new reserved capacity, select New capacity +. From the Reserved capacity page, enter or select the following information:





Table 1. Reserved capacity provisioning selections

 Field Value 

 Name A name is required for your reserved capacity. 
 Virtual server capacity Select the number of instances you want to assign to this reserved capacity (limit of 20 instances). 
 Plan Terms Choose between either a 1 or 3-year contract term. 
 Location Select the specific location that is required for your workloads. Locations are composed of regions; each region is a separate geographic area. Note: You can't select individual locations for each virtual server instance that you provision within this reserved capacity. Your selection is the location for all virtual server instances that you provision within this reserved capacity. 
 Pod Select the pod specific to your location. 
 Profile Select from popular profiles or all available vCPU and RAM combinations of SAN-backed storage (balanced, memory, or compute). Note: You cannot combine different profile sizes within the set of virtual server instances that are assigned to this capacity or change them later. The set of virtual server instances you reserve must be the same size. 







 Provisioning reserved instances
vRA or SRA supported, replication between SDS and or Physical XIV devices. Snapshots supported; application recovery through IBM FlashCopy Manager. 
 Reliability Single point of failure without HA. Tolerates up to three host failures with seven plus hosts. Failure domains are introduced in v6.0. Single point of failure (enclosure and RAID controller) and no HA. Single point of failure (enclosure and RAID controller) and no HA. Highly redundant multipath I/O (MPIO) connection. Highly redundant iSCSI MPIO connections: any node can manage the cluster. 



For more information, see the following links.



* NetApp OnTap Edge: Not available on the IBM Cloud catalog – bring your own solution.



* [Data ONTAP installation and administration guide](https://library.netapp.com/ecm/ecm_download_file/ECMP1200031)
* [Data ONTAP Express setup guide](https://library.netapp.com/ecm/ecm_download_file/ECMP1369085)



* [NetApp Private Storage for IBM Cloud](http://www.netapp.com/us/solutions/cloud/private-storage-cloud/softlayer.aspx)
* Spectrum Accelerate: Not available on the IBM Cloud catalog – bring your own solution.



* [Working with an IBM Spectrum Accelerate system](https://www.ibm.com/support/knowledgecenter/STJTAG/com.ibm.help.xivgen3.doc/MT/UG/xiv_mt_deploying_spectrum_accelerate.html)













 Shared storage options 

IBM Cloud® offers great File Storage options that you can use to connect to VMware in a multi-tenant environment.



 File Storage 

You can order the Bare Metal Servers from the IBM Cloud catalog with ESX. In the IBM Cloud catalog, you can also provision IBM Cloud® File Storage in the same availability zone as your host.
See the [Order the first virtual server](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-secure-network-enclosuresecure-network-enclosure-order_virtualserver) instructions in the [Isolate workloads with a secure private network](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-secure-network-enclosure) tutorial for details of how to specify the <Private VLAN ID> when ordering a virtual server. Also remember to select your SSH key uploaded earlier in the tutorial to allow access to the virtual servers.
3. It is strongly recommended NOT to use the file storage service for this tutorial due to poor rsync performance copying the Wordpress files to shared storage. This does not affect the overall tutorial. The steps relating to creating the file storage and setting up mounts can be ignored for the app servers and db. Alternatively all the [Install and configure the PHP application on the application servers](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-highly-available-and-scalable-web-applicationhighly-available-and-scalable-web-application-php_application) steps need to be performed on both app servers. Prior to completing the steps in [Install and configure the PHP application on the application servers](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-highly-available-and-scalable-web-applicationhighly-available-and-scalable-web-application-php_application), first create the directory /mnt/www/ on both app servers. This directory was original created in the now removed file storage section.

mkdir /mnt/www



At the end of this step the load balancer should be in a healthy state and the Wordpress site accessible on the internet. The virtual servers making up the web application are protected from external access via the internet by the VRA firewall and the only access is via the load balancer.
* UI
* CLI
* API







 Creating instances on dedicated hosts 

After you created a dedicated host in your IBM Cloud VPC, you can provision virtual server instances on the dedicated host by using the IBM Cloud console, the CLI, or the API.



 Creating instances on dedicated hosts by using the console 

After you created a dedicated host, you can start provisioning virtual server instances on the dedicated host by using the IBM Cloud console.

The profile family and class must match for the dedicated host or dedicated group and instances that are provisioned on them. For more information, see [Dedicated host profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-dh-profiles).

To create an instance on a dedicated host:



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 > Dedicated hosts.
2. If you want to create an instance on a specific dedicated host, on the Dedicated hosts tab click the Actions icon ![More Actions icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/action-menu-icon.svg) for the host where you want the instance to be created and select New instance.
3. If you want to create an instance on any dedicated host within a dedicated group, on the Dedicated groups tab click the Actions icon !
* SERVER: ID or name of the server.
* --vnc: Get the WebSocket URI for the VNC console, it doesn't open the VNC console.
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is bare-metal-server-create 

Create a bare metal server.

ibmcloud is bare-metal-server-create --zone ZONE_NAME --profile PROFILE --image IMAGE --keys KEYS ((--pnic-subnet PRIMARY_NIC_SUBNET [--vpc VPC]) [--pnic-name PRIMARY_NIC_NAME] [--pnic-rip PNIC_RIP | (--pnic-rip-address PNIC_RIP_ADDRESS --pnic-rip-auto-delete true | false --pnic-rip-name PNIC_RIP_NAME)] [--pnic-sgs PNIC_SGS] [--pnic-allowed-vlans PNIC_ALLOWED_VLANS] [--pnic-ein true | false] [--pnic-ais false | true]) [--name NAME] [--user-data DATA] [--network-interfaces NETWORK_INTERFACES_JSON | @NETWORK_INTERFACES_JSON_FILE] [--enable-secure-boot false | true] [--tpm-mode tpm_2 | disabled] [--resource-group-id RESOURCE_GROUP_ID | --resource-group-name RESOURCE_GROUP_NAME] [-i, --interactive] [--output JSON] [-q, --quiet]



 Command examples
[Available pricing plans](https://cloud.ibm.com/docs-content/v1/content/29e0ddc9fd7149f916889ba6a4d131cc3528c9bc/hp-virtual-servers/image/hpvs_plans.jpg)

Figure 2. Available pricing plans
9. Click Create to provision a virtual server instance.



The virtual server instance appears in the Resource list. Use your browser's refresh function to check whether the instance's status switched from Inactive (the server is being provisioned) to Active (the server is provisioned). Because of the configuration process, provisioning can take 5 - 30 minutes. When your instance has a status of Active (provisioned), click the instance in the Name field to open the dashboard. If the configuration fails, the instance status stays as Inactive, and if you click the instance in the Name field, an error message is displayed.

![Resource list with a virtual server](https://cloud.ibm.com/docs-content/v1/content/29e0ddc9fd7149f916889ba6a4d131cc3528c9bc/hp-virtual-servers/image/hpvs_resource_list.jpg){: caption="Figure 3. Resource list with a virtual server that shows one server that is being provisioned (Inactive) and one server that is already provisioned (Active)" caption-side="bottom"}





 Creating a virtual server from the CLI 

To create a virtual server from the CLI, you must first install the [CLI](https://cloud.ibm.com/docs/hpvs-cli-plugin), then run the following command:
[solution tutorial icon](https://cloud.ibm.com/media/docs/images/homepage/solution-tutorial.svg) [Creating a virtual data center in a VMware as a Service with Terraform](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vmware-as-a-service-tf)Creating a virtual data center in a VMware as a Service with Terraform Solution tutorial

This tutorial is to demonstrate the basic steps to operationalize an IBM Cloud® for VMware as a Service – single tenant instance after initial instance provisioning. This tutorial should take about 20-30 minutes to complete and assumes that IBM Cloud® for VMware as a Service – single tenant instance and a virtual data center (VDC) have already been provisioned. This tutorial uses an example Terraform template, which can be customized and modified for your use case, if needed.

![solution tutorial icon](https://cloud.ibm.com/media/docs/images/homepage/solution-tutorial.svg) [Deploy isolated workloads across multiple locations and zones](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-multi-region)Deploy isolated workloads across multiple locations and zones Solution tutorial

This tutorial walks you through steps for setting up highly available and isolated workloads by provisioning IBM Cloud® Virtual Private Clouds (VPCs). You will create virtual server instances (VSIs) in multiple zones within one region to ensure the high availability of the application. You will create additional VSIs in a second region and configure a global load balancer (GLB) to provide high availability between regions and reduce network latency for users in different geographies.

!
Server Virtual Desktop Infrastructure Deliver a desktop experience from a server OS for a single user. 
 Desktop Virtual Desktop Infrastructure Deliver a pooled or dedicated desktop experience from single-session OS machines. 



When you select your workload requirements, you need to select how many of each type of user who needs to be supported. For more information about the user types, see the following table.



Table 4. Workload user types

 Field Details 

 Task Worker Uses a light workload and runs fewer applications that are not resource-intensive. Starts and stops applications less frequently. 
 Knowledge Worker Uses multiple applications in well-balanced intensive workloads. 
 Power User Uses resource-intensive applications, such as graphics or software development applications. 







 Bare metal server configuration 

All of your bare metal servers are configured identically based on your selections.



Table 5. Server configuration details

 Field Details 

 Hostname root and domain Your hostname and domain are saved in the server operating system and are used to identify servers. 
 Location The data center location must match the geographical area of your Citrix resource location. 
 Image An image is the deployed operating system for your servers. 
 Profile Consider selecting from the listed server profiles, which are based on provided workload sizings by using Citrix best practices. You can select the All servers tab to choose from more supported server profiles. 







 File storage 

NFS file storage options:



Table 6. NFS File storage details

 Field Details 

 Size You can enter a file storage size 20 - 12,000 GB. The minimum recommended size is 100 GB. 
 Snapshot space Select how much snapshot space you want for your file storage volume. For more information about snapshots, see [Snapshots](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-snapshots). 
 IOPS tier By default, the IOPS tier is 4 IOPS/GB, which is designed for higher-intensity workloads. These workloads are typically characterized by having a high percentage of data active at any time. 



vSAN storage for VMware options:



Table 7. vSAN File storage details

 Field Details
For more information, see [Intel Software Guard Extension](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-bm-intel-sgx).





 16 March 2018 

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. You need to connect the add-on storage to your bare metal server after your server provisions. For more information, see the block and file storage add-on section of [Bare metal server options](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-about-bmbm-block-and-file-add-on).





 02 March 2018 

Custom bare metal servers
: IBM Cloud® Bare Metal Servers are single-tenant physical servers that provide you performance and control with low-level access to the hardware resources. You can create a custom IBM Cloud® Bare Metal Servers. For more information, see [Building a custom Bare Metal Server](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-ordering-baremetal-server).
* ibmcloud is bare-metal-server-create --name my-server-name --zone us-east-1 --profile bmx2d-24x384 --image cfdaf1a0-5350-4350-fcbc-97173b510844 --keys 7ab1ee27-564c-4730-a1ad-9b9466589250,9727e31a-74d4-45cd-8f39-1ef7484b5f3e --pnic-subnet bdea9c01-ada2-46ba-a314-4b3240477a5f --pnic-rip-address 10.240.128.38 --pnic-rip-auto-delete true --pnic-rip-name cli-rip1 --network-interfaces '[{"name": "cli-snic", "allow_ip_spoofing": true, "enable_infrastructure_nat": true, "interface_type": "pci", "allowed_vlans": 1, 2, 3, 4], "subnet": {"id":"2302-d368b797-2955-464b-aa42-588edd4c389f"}, "primary_ip":{"address": "10.240.128.41"}, "security_groups": {"id": "72b27b5c-f4b0-48bb-b954-5becc7c1dcb8"}, {"id": "72b27b5c-f4b0-48bb-b954-5becc7c1dcb3"}]}]' Create a bare metal server with secondary network interface with new reserved IP. Configurations of the two secondary interfaces are specified in JSON format. See help text for '--network-interfaces' option.







 Command options 



* --name: Name of the server.
* --zone: Name of the zone.
* --profile: Name of the bare metal server profile.
* UI
* CLI
* API
* Terraform







 Creating virtual server instances 

You can create one or more virtual server instances in your IBM Cloud VPC by using the IBM Cloud console, CLI, API, or Terraform.



 Creating a virtual server instance with the UI 

Use the following steps to create a virtual server instance.



1. In the [IBM Cloud console ![External link icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/launch-glyph.svg)](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 and begin by entering the information in Table 1.



Table 1. Selections to begin instance provisioning

 Field Value 

 Architecture Select the processor architecture that your instance is created with. x86 means x86_64 bit processor, and s390x is z Systems or LinuxONE (s390x processor architecture). 
 Hosting type A Public virtual server instance, created in a multi-tenant environment, is the default selection for a new instance. You can also select a Dedicated virtual server instance to create the instance in a single-tenant space. To provision a dedicated instance, you must have a dedicated host available or [create one](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-dedicated-hosts-instances). A dedicated host is required if you use a Windows custom image and [your own license](https://cloud.ibm.com/docs/vpc?topic=vpc-byol-vpc-aboutbyol-vpc-windows).
Viewing your server 

When the server status changes to Running, use the following command to view it.

ibmcloud is bare-metal-server $bare_metal_server_id --output JSON







 Next steps 

When the bare metal server status changes to Running, you can connect to it.



* For x86 architecture, you can connect to VMware ESXi Direct Console User Interface (DCUI) and ESXi's web client. For more information, see [Connecting to ESXi bare metal servers](https://cloud.ibm.com/docs/vpc?topic=vpc-connect-to-ESXi-bare-metal-servers).
* For s390x architecture, you can connect to the s390x bare metal server by using the SSH key and its floating IP. For more information, see [Connecting to s390x bare metal servers](https://cloud.ibm.com/docs/vpc?topic=vpc-connect-to-s390x-bare-metal-servers).
On the Add ESXi server side panel, enter the number of bare metal servers that you want to add. You can keep the Maintenance mode checkbox selected to add servers during maintenance mode.

When you provision new ESXi servers, virtual machines (VMs) are immediately migrated to the new servers if you do not select the Maintenance mode checkbox. You do not receive a confirmation message before the migration begins.
7. Complete the bare metal server configuration.



* From the list, you can select a bare metal server configuration that is being used by the existing ESXi servers in the cluster. Then, click Next. This option is not available under the following conditions:



* The bare metal configuration that is used by the existing ESXi servers in the cluster is Broadwell.
* The storage type of the cluster is Local disks.



* You can also choose a new bare metal server configuration by selecting the option from the list and clicking Next. Select the CPU model and the amount of RAM.



8. Click Next and complete the networking settings.



* You can continue to use the previously selected primary subnets.
* You can specify different primary subnets. Then, use the lists to select the Public primary subnet and Private primary subnet.
* If you want to customize the hostnames prefix individually, toggle the Configure hostnames individually switch on.



9. In the Details section, review the estimated pricing, ensure that the account to be charged is correct, and review and accept the terms. Then, click Add.







 Results after you add ESXi servers to Cyber Recovery instances 



1. You might experience a slight delay on the console while the instance status changes from Available to Modifying. Allow the operation to complete before you make more changes to the instance.
2. You are notified by email that your request to add ESXi servers is being processed. On the console, the status of the cluster that is associated with the ESXi servers is changed to Modifying.
3. If you do not see the new ESXi servers added to the list in the cluster, check your email or console notifications for more details.
* If original instance is not deleted (for example, backups are still available) a new instance can be created by restoring from a backup, should that become necessary.



* The backups that are taken in the original MZR are still accessible even if that MZR is unavailable; they are stored in cross-regional IBM Cloud Object Storage buckets.



4. If a read-only replica is promoted to leader, the original leader is no longer viable.
5. To move the data or workload back to the original MZR, create a read-replica in the original MZR and promote it to be the leader. This does create a new instance of the database, not a restore of the original instance.





 Additional database options 

Cloud Databases offers several open source database systems as fully managed services. They are:



* [Databases for PostgreSQL](https://cloud.ibm.com/catalog/services/databases-for-postgresql)
* [Databases for EnterpriseDB](https://cloud.ibm.com/catalog/services/databases-for-enterprisedb)
* [Databases for DataStax](https://cloud.ibm.com/catalog/services/databases-for-cassandra)
* [Databases for Redis](https://cloud.ibm.com/catalog/services/databases-for-redis)
* [Databases for Elasticsearch](https://cloud.ibm.com/catalog/services/databases-for-elasticsearch)
* [Databases for etcd](https://cloud.ibm.com/catalog/services/databases-for-etcd)
* [Databases for MongoDB](https://cloud.ibm.com/catalog/services/databases-for-mongodb)
* [Messages for RabbitMQ](https://cloud.ibm.com/catalog/services/messages-for-rabbitmq)



All of these services share the same characteristics:



* For high availability, they are deployed in clusters. Details can be found in the documentation of each service:
Virtual server instances on SAP NetWeaver 7.x APAB stack, JAVA stack, and dual stack (ABAP+JAVA) architectural design on IBM Cloud® VPC on Unix 



 Standard system 

In a standard system, all main instances run on a single virtual server instance within a private subnet. For more information, see [About virtual server instances for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-about-advanced-virtual-servers). The virtual server instance has these components:

Zoom

![Figure 2. Standard installation](https://cloud.ibm.com/docs-content/v1/content/f89cc64b006ca59b35404693959c83d5747fee3e/sap/images/refarch-sap-db2-std-only.svg)

Figure 2. SAP NetWeaver 7.x with Db2 standard installation with AAS

Architecture of SAP NetWeaver AS for ABAP

SAP tools create a PAS Instance and an ASCS Instance. This method is the standard for Java Stack (System) and is now standard for ABAP Stack.



1. The Primary Application Server (PAS) - An instance is an administrative unit that contains various components of an SAP system. The components of an instance are parameterized in a shared instance profile. Each instance is identified by a system ID and an instance number and includes:



* [SAP Web Dispatcher](https://help.sap.com/saphelp_snc700_ehp01/helpdata/en/f9/e2350eca7f4a109eb0a7bc63135e27/frameset.htm) & Work Process (DIA,BTC,UPD,SPOOL) - The SAP Web Dispatcher lies between the internet and your SAP system. The SAP Web Dispatcher is the entry point for HTTP and HTTPs requests into your system, which consists of one or more SAP NetWeaver application servers. As a “software web switch”, the SAP Web dispatcher can reject or accept connections.