vania-janet/multiturn-rag-retrieval-data huggingface dataset:
By default, a boot volume is attached to the instance when the instance is created. For most virtual server instances, the default boot volume size is 100 GB. The default boot volume size for a z/OS virtual server instance is 250 GB.



1. Create an instance by using the following command.

ibmcloud is instance-create INSTANCE_NAME VPC ZONE_NAME PROFILE_NAME SUBNET --image IMAGE --keys KEYS

For example, the following instance-create command uses the sample values that are found in the [Gathering information](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers&interface=uigather-info-to-create-virtual-servers-cli) section.

ibmcloud is instance-create my-instance r134-35b9cf35-616e-462e-a145-cf8db4062fcf us-south-2 bx2-2x8 0726-198db988-3b9b-4cfa-9dec-0206420d37d0 --image r134-f83ce520-00b5-40c5-9938-a5c82a273f91 --keys r134-89ec781c-9630-4f76-b9c4-a7d204828d61

Where the following argument and option values are used



* INSTANCE_NAME: my-instance
* VPC: r134-35b9cf35-616e-462e-a145-cf8db4062fcf
* ZONE_NAME: us-south-2
* PROFILE_NAME: bx2-2x8
* SUBNET: 0726-198db988-3b9b-4cfa-9dec-0206420d37d0
* IMAGE: Debian 11 image r134-f83ce520-00b5-40c5-9938-a5c82a273f91
By default, a boot volume is attached to the instance when the instance is created. For most virtual server instances, the default boot volume size is 100 GB. The default boot volume size for a z/OS virtual server instance is 250 GB.



1. Create an instance by using the following command.

ibmcloud is instance-create INSTANCE_NAME VPC ZONE_NAME PROFILE_NAME SUBNET --image IMAGE --keys KEYS

For example, the following instance-create command uses the sample values that are found in the [Gathering information](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers&interface=apigather-info-to-create-virtual-servers-cli) section.

ibmcloud is instance-create my-instance r134-35b9cf35-616e-462e-a145-cf8db4062fcf us-south-2 bx2-2x8 0726-198db988-3b9b-4cfa-9dec-0206420d37d0 --image r134-f83ce520-00b5-40c5-9938-a5c82a273f91 --keys r134-89ec781c-9630-4f76-b9c4-a7d204828d61

Where the following argument and option values are used



* INSTANCE_NAME: my-instance
* VPC: r134-35b9cf35-616e-462e-a145-cf8db4062fcf
* ZONE_NAME: us-south-2
* PROFILE_NAME: bx2-2x8
* SUBNET: 0726-198db988-3b9b-4cfa-9dec-0206420d37d0
* IMAGE: Debian 11 image r134-f83ce520-00b5-40c5-9938-a5c82a273f91
The RackWare Management Module (RMM) migration solution provides a seamless means for replatforming on-premises workloads to IBM Cloud® virtual server instances, and allows the adoption of the native capabilities of IBM Cloud. Its intuitive GUI allows you to move the OS, applications, and data from on-premises to IBM Cloud VPC instances.

Virtual Private Cloud (VPC) Virtual Servers for Classic

+1

Building infrastructure



* 45 minutes
* 2022-11-23



[Classic VMware VM to IBM Cloud VPC migration with RMM ](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-migrating-images-vmware-vpc-classic)Classic VMware VM to IBM Cloud VPC migration with RMM

The RackWare Management Module (RMM) migration solution provides a seamless virtual-to-virtual replatforming for VMware virtual machine (VM) to IBM Cloud® virtual server instance migration. It allows the adoption of existing capabilities of IBM Cloud. Its intuitive GUI permits moving the OS, application, and data from VMware ESXi in IBM Cloud classic to IBM Cloud VPC virtual server instances.

Virtual Private Cloud (VPC) Virtual Servers for Classic

+1

Building infrastructure



* 60 minutes
* 2022-04-28



[On-premises VMware VM to IBM Cloud VPC migration with RMM](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-migrating-images-vmware-vpc)On-premises VMware VM to IBM Cloud VPC migration with RMM

To implement a data center transformation, the RackWare Management Module (RMM) migration solution provides a seamless virtual-to-virtual replatforming for VMware virtual machine (VM) to IBM Cloud® virtual server instance migration. It allows the adoption of existing capabilities of IBM Cloud. Its intuitive GUI allows you to move the OS, application, and data from VMware ESXi to IBM Cloud VPC virtual server instance.

Virtual Private Cloud (VPC) Virtual Servers for Classic

+1

Building infrastructure



* 45 minutes
* 2022-11-23
Viewing vCenter Server with Hybridity Bundle instances 

View the summary and detailed information of the VMware vCenter Server® with Hybridity Bundle instances that are provisioned for different user accounts.



 Procedure to view vCenter Server with Hybridity Bundle instances summary 

To view a summary of all the vCenter Server with Hybridity Bundle instances that are provisioned for a user account, complete the following steps:



1. In the IBM Cloud® for VMware Solutions console, click Resources > vCenter Server from the left navigation pane.
2. From the console banner, click your user account icon, and then click the Account field to select the user account that you want to check instances for.
3. In the vCenter Server table, view the list of instances that are provisioned in the selected user account.





Table 1. vCenter Server with Hybridity Bundle instance items

 Item Description 

 Name The name of the instance. 
 Type The type of vCenter Server instance. 
 Version The release version that the instance was deployed in, or upgraded to. 
 Location The IBM Cloud data center where the instance is hosted. 
 Creation time The date and time when the instance was created. 
 Status The status of the instance. 



The instance can have different statuses.



Table 2. vCenter Server with Hybridity Bundle instances status descriptions

 Status Description 

 Creating The instance is being created. 
 Building The instance is being configured. 
 Available The instance is ready to use. 
 Modifying The instance is being modified. 
 Failed The creation, configuration, or modification process failed. 
 Deleting The instance is being deleted. 
 Deletion Error An error occurred when the instance was being deleted. 
 Deleted The instance is deleted. 







 Procedure to view vCenter Server with Hybridity Bundle instances property details 

To view the property details of a vCenter Server with Hybridity Bundle instance:



1. In the vCenter Server table, click an instance name.
2. Under Properties, view the details for the instance.





Table 3. vCenter Server with Hybridity Bundle instances properties

 Property Description 

 Name The name of the instance. 
 ID The ID of the instance. 
 Location The IBM Cloud data center where the instance is hosted.
It is used to manage locks, exchange messages, and balance workload in the SAP system. The ASCS instance includes:



* [Message Server](https://help.sap.com/saphelp_snc700_ehp01/helpdata/en/f9/e2350eca7f4a109eb0a7bc63135e27/frameset.htm) - The SAP message server runs as a separate process, mostly on the same host as the central instance. If an SCS instance (SAP Central Services) or ASCS instance (ABAP SCS) is configured in the system, the message server is part of this instance.
* [Stand-alone Enqueue Server](https://help.sap.com/saphelp_snc700_ehp01/helpdata/en/f9/e2350eca7f4a109eb0a7bc63135e27/frameset.htm) - Part of the central instance (ABAP or Java) that manages the SAP locks. In combination with the enqueue replication server, this single point-of-failure can be made into a high availability solution.
* ABAP Central services instance (ASCS instance) - Contains the ABAP message server and the stand-alone Enqueue Server
* The enqueue replication server instance is only mandatory in a high-availability system.





Optionally, you can install the ASCS instance with an integrated:



* SAP Web Dispatcher. For more information, see [ASCS Instance with Integrated SAP Web Dispatcher](https://help.sap.com/viewer/910828cec5d14d6685da380aec1dc4ae/CURRENT_VERSION/en-US/2e708e2d42134b4baabdfeae953b24c5.html).
* Gateway.
All profiles For more information about available profile options for public instances, see [Public virtual servers](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-about-public-virtual-servers). 
 SSH keys SSH keys allow access to an instance without using a password from corresponding clients for each public key that is implemented on the instance. If you decide to add an SSH key, provide a public key of your SSH key, which you can use to log in to your instance after it is provisioned. 
 Image An image is the deployed operating system for your instance. You can select a number of free options such as CentOS and Ubuntu. Paid options such as Windows Server and Red Hat Enterprise Linux (RHEL) are also available. It's important to note that Windows requires a 100 GB primary disk. 







 Public instance add-ons 

If you choose any OS, control panel, or software add-ons, they must be compatible with your image to avoid an error when you are ordering your instance. For example, you can’t provision a Red Hat image with a Microsoft database.

Depending on your instance billing type (hourly or monthly), some add-ons might not be available.



Table 2. Public instance add-ons

 Field Details 

 OS add-ons If you select monthly billing, you can select the following image add-ons:nR1Soft Server Backup Manager provides high-performance disk-to-disk server backup and a central management and data repository. If you select the R1Soft add-on, you must purchase an R1Soft Backup Agent pack, which is a CDP add-on in the Services section. Selecting one without the other causes an error with your order. For more information about R1Soft and IBM Cloud, see [R1Soft Server Backup Manager](https://www.ibm.com/cloud/backup-and-restore?mhq=R1Soft%20Server%20Backup%20Manager&mhsrc=ibmsearch_a). Veeam Backup and Replication combines automated backup along with restore and replication capabilities. Veeam also provides advanced monitoring, reporting, and capacity planning.
To start the virtual server instance by using the CLI, use the ibmcloud is instance-start command. Specify the ID or name of the virtual server instance that you want to start by using the INSTANCE variable.

ibmcloud is instance-start INSTANCE

For a full list of command options, see [ibmcloud is instance-start](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-referenceinstance-start).





 Stop a virtual server instance using the API 

You can stop the virtual server instance in your IBM Cloud VPC by using the API.

The following example stops a virtual server instance with an instance ID of d6c3902d-1ecf-3a2c-b7ab-eb9143581000.

curl -X POST "https://us-south.iaas.cloud.ibm.com/v1/instances/d6c3902d-1ecf-3a2c-b7ab-eb9143581000/actions?version=2021-06-22&generation=2" -H "Authorization: $iam_token" -d '{"type": "stop"}'

The stop action shuts down the guest operating system and then the virtual server instance is deprovisioned. This change frees the instance resources that were being consumed. The virtual server instance is transitioned to the Stop state. If the instance is stopped, the instance remains in the stopped state and must be started manually. Billing is [suspended](https://cloud.ibm.com/docs/vpc?topic=vpc-suspend-billing) for some compute resources while the instance is stopped. You cannot interact with an instance if it is stopped, but volumes remain provisioned. If the instance is started, normal interaction and billing continues.

A Force stop action triggers a power cycle reset of the virtual server instance.

For more information, see the [Create instance action](https://cloud.ibm.com/apidocs/vpccreate-instance-action) in the Virtual Private Cloud API documentation.





 Start a virtual server instance using the API
Also, when you are choosing the maximum number, make sure that the subnet has enough spare IP addresses to accommodate any new provisioned virtual server instances that are created by the Auto scale feature.
{: tip}

The instance group size values are for demonstrative purpose. No exact formula is used to determine these values as it depends on your business and application requirements. More often than not, it takes several test iterations to find the right values.
{: note}

i. Click Add a policy under Create scaling policies:



* Select Network out (Mbps) for Metric type.
* Enter 1 for Average target utilization.

Again, the resource and utilization values are target-based thresholds. The values that are used here are for demonstrative purpose only. Any values that you use must be based on your requirements and just like the instance group size, it might take a couple of test iterations to find the right values. If multiple scaling policies exist (for example, CPU and memory), then the membership calculation is done for each policy and the policy that has the higher membership wins.



4. Check that you agree that instances are created and reclaimed according to the instance group settings.
5. Click Create instance group.







 Related Content 

For more information about Auto scale, instance templates, and instance groups, see [Creating an instance group for auto scaling](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-auto-scale-instance-group).

For a detailed example, watch the video [Don't let load be the reason for the 404 error](https://video.ibm.com/channel/23944579/video/mv8ajs)
The domain name is used to generate the username and server names of the instance.



The subdomain label is used only for existing VMware vSphere® 6.x instances.



Table 1. Value format for instance and domain names

 Name Value format 

 Domain name <root_domain> 
 vCenter Server login username <user_id>@<root_domain> (Microsoft® Active Directory™ user) or administrator@vsphere.local 
 vCenter Server (with embedded PSC) FQDN <instance_name>-vc.<root_domain>. The maximum length is 50 characters. Any hyphen (-) characters from the instance name are removed. 
 Single Sign-On (SSO) site name <root_domain> 
 Fully qualified VMware ESXi™ server name <host_prefix><n>.<root_domain>, where n is the sequence of the ESXi server. The maximum length is 50 characters. 
 NetBIOS name First string of <root_domain>. The maximum length is 15 characters. 



After the instance is provisioned, do not modify any values that are set during instance order. Otherwise, the instance might become unusable. For example, if public networking shuts down or if servers and Virtual Server Instances (VSIs) move behind a Vyatta mid-provision.
Example output 

OK
Provisioning request for service instance 'crn:v1:staging:public:hpvs:dal13:a/1075962b93044362a562c8deebbfba2e:98338d1f-910b-4895-9410-453a9c4d9709::' was accepted.
To check the provisioning status run:
ibmcloud hpvs instance crn:v1:staging:public:hpvs:dal13:a/1075962b93044362a562c8deebbfba2e:98338d1f-910b-4895-9410-453a9c4d9709::







 hpvs instance-update 

This command updates a Hyper Protect virtual server instance.

ibmcloud hpvs instance-update (NAME | CRN) [--hostname HOST-NAME] [(--rd REGISTRATION-DEFINITION | --rd-path REGISTRATION-DEFINITION-PATH)] [-i IMAGE-TAG] [-e ENV-CONFIG1 -e ENV-CONFIG2 ...] [--force]

NAME
: The name of your new instance. An error message is displayed if you specify a NAME that is not unique, for example,

VS name 'ABC' is ambiguous: more than one VS exist for the provided name: [crn1 crn2].

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 

--hostname HOST-NAME
: The hostname that will be set within the Hyper Protect Virtual Servers container by using this parameter value.

--rd REGISTRATION-DEFINITION
: The encrypted and signed registration definition that is used for [Bring your own server image (BYOI)](https://cloud.ibm.com/docs/hp-virtual-servers?topic=hp-virtual-servers-byoi).
To view your boot images, go to Boot images after you provision the instance.



Refer to the following table for more information on each Power Systems Virtual Server instance field.



Table 2. Power Systems Virtual Server instance fields

 Field Description 

 General Instance name: Specify an apt name for your virtual server instance. <br>Number of Instances : Specify the number of instances that you want to create for the Power Systems Virtual Server. You can apply placement groups only when you are creating a single VM instance. If you choose the Machine type as E980, you can choose [anti-affinity policy](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-power-iaas-faqsaffinity) with maximum of 2 VM instances. <br>Placement group: If you are creating only one instance, you can choose the placement group to control on which host this instance will be hosted on. Select a placement group from the list. To create a new placement group select one of the following options: <br>Same server : Select this option to place the VM on the same host. <br>Different server : Select this option to place the VM on a different host. <br>Colocation rules: If you specify more than one instance, you can select the following naming conventions and colo rules: <br>No preference: Select this option if you do not have a hosting preference. <br>Same server : Select this option to host all instances on the same server. A placement group is automatically created. The instance name previously provided will be used as the group name and cannot be edited. <br>Different server : Select this option to host each instance on a different server. You can use this option if you are concerned about a single-server outage that might affect all Power Systems Virtual Server instances. A placement group is automatically created. The instance name previously provided will be used as the group name and cannot be edited. <br>Numerical prefix : Select this option to add numbers before the name of the virtual server. If, for example, the first Power Systems Virtual Server name is Austin the next name for the virtual instance is 1Austin.
Ordering an instance from an image template 

On the Image Templates page, you can provision a virtual server instance from an image template.



  Before you begin 

First, go to the device menu and make sure that you have the correct account permissions to complete the tasks.



*  Go to your console's device menu. For more information, see [Navigating to devices](https://cloud.ibm.com/docs/image-templates?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-infrapermissioninfrapermission) and [Managing device access](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-managing-device-access).





  Ordering an instance from an image template 

Use the following steps to order an instance from an image template.



1.  Access the Image Templates page by selecting Devices > Manage > Images.
2.  Click the Actions menu for the image template that you want to use and select the type of virtual server that you want to order.
3.  On the Configure your Cloud Server page, complete all of the relevant information.
4.  Click Add to Order to continue.
5.  On the Checkout page, complete any advanced system configuration.
6.  Click the Cloud Service terms and the Third-Party Service Agreement check boxes.
7.  Confirm or enter your payment information and click Submit Order. You are redirected to a screen with your provisioning order number. You can print the screen because it's also your provisioning order receipt.



You receive an email when your instance is provisioned.
View details of a network interface of a virtual server instance.

ibmcloud is instance-network-interface INSTANCE NIC [--output JSON] [-q, --quiet]



 Command options 



* INSTANCE: ID or name of the instance.
* NIC: ID or name of the network interface.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is instance-network-interface-create 

Create a network interface for a virtual server instance.

ibmcloud is instance-network-interface-create NIC_NAME INSTANCE SUBNET [--vpc VPC] [--rip RIP | (--address ADDRESS --auto-delete true | false --ip-name IP_NAME)] [(--sg SG1 --sg SG2 ...)] [--allow-ip-spoofing false | true] [--output JSON] [-q, --quiet]



 Command examples 



* ibmcloud is instance-network-interface-create my-vnic 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 72b27b5c-f4b0-48bb-b954-5becc7c1dcb3
* ibmcloud is instance-network-interface-create my-vnic 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 72b27b5c-f4b0-48bb-b954-5becc7c1dcb3 --rip 0711-5c7f016e-5bd2-42e3-8dff-81519e4e2469
A logging agent collects logs with the extension .log and extensionless files that are stored in the /var/log directory of your pod from all namespaces, including kube-system. The agent then forwards the logs to your IBM Log Analysis service instance. For more information about the service, see the [IBM Log Analysis](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-getting-started) documentation. To enable IBM Log Analysis in your cluster, see [Forwarding cluster and app logs to IBM Log Analysis](https://cloud.ibm.com/docs/containers?topic=containers-healthlogging).

IBM Cloud® Activity Tracker
: To monitor user-initiated administrative activity made in your cluster, Kubernetes Service automatically generates cluster management events and forwards these event logs to IBM Cloud Activity Tracker. To access these logs, [provision an instance of IBM Cloud Activity Tracker](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-getting-started). For more information about the types of IBM Cloud Kubernetes Service events that you can track, see [Activity Tracker events](https://cloud.ibm.com/docs/containers?topic=containers-at_events).

Fluentd with an external server
: To collect, forward, and view logs for a cluster component, you can create a logging configuration by using Fluentd. When you create a logging configuration, the [Fluentd](https://www.fluentd.org/) cluster component collects logs from the paths for a specified source. Fluentd can then forward these logs to an external server that accepts a syslog protocol. To get started, see [Understanding cluster and app log forwarding to syslog](https://cloud.ibm.com/docs/containers?topic=containers-healthlogging).





 Forwarding cluster and app logs to IBM Log Analysis 

Forward logs to an IBM Log Analysis instance.

Use the IBM Cloud Kubernetes Service observability plug-in to create a logging configuration for IBM Log Analysis in your cluster, and use this logging configuration to automatically collect and forward pod logs to IBM Log Analysis.