vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Microsoft Hyper-V VM to IBM Cloud VPC migration with RMM 

The RackWare Management Module (RMM) solution simplifies the overall migration process of moving the operating system, applications, and data from Microsoft Hyper-V VM to IBM Cloud® Virtual Servers for Virtual Private Cloud. The migration can occur either over the public or private interface of the compute resource. The only requirement is that RMM is able to access both the source and target server over SSH.

This guide demonstrates how to complete a migration from your Microsoft Hyper-V VM on-premises or in IBM Cloud classic to IBM Cloud VPC.



 Supported operating systems 



* RHEL 7.x, 8.x
* Ubuntu 18.04.x, 20.04.x
* Debian 9.x, 10.x
* Windows 2012, 2012 R2, 2016, 2019







 Before you begin 



* Check for correct permissions for IBM Cloud VPC.
* For each volume on the source server, 20 percent of the unused space must be available to store the snapshot that is created by RMM.
* Copy the RMM SSH public key to both the source and target servers.



* This procedure can require modifying the servers' host route table or security rules.
* Update the name server or DNS.



* The order of the target server, the CPU, and memory does not need to match, but the volumes must be equal to or greater than the source.
* Make sure to have a /etc/fstab entry for automatic mounting of any file system on the target server.



To improve the data transfer rate, adjust the bandwidth allocation of the RMM server. For more information, see [Adjusting bandwidth allocation using the UI](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-virtual-server-instances&interface=uiadjusting-bandwidth-allocation-ui).





 Step 1: Order RMM 

You can order RMM-BYOL from the IBM Cloud catalog. A virtual server with the RMM software is installed into the VPC that you provide when you order. The RMM server has a public IP address for reachability.
[Create an access group](https://cloud.ibm.com/docs/account?topic=account-access-getstartedcreate-access-group) within the resource group that gives privileges to create images in your resource group.



1. Go to Manage > Access (IAM)> Access Groups and click Create.
2. Enter the name and description for your access group and click Create.





 Assigning permissions 

When an access group is created, a policy must be applied to set permissions in the resource group.



1. On the access group page, select the Access policies tab. Click Assign access.
2. Select IAM Services and VPC Infrastructure Services.
3. Click Services based on attributes.
4. Under Add attributes, select Resource group.
5. From the list, select the resource group that you want to use.
6. Select Resource type under Add attributes and select the resource type Image Service for VPC. Optionally, you can choose a particular image ID for the policy.
7. Select an RBAC permission role. Roles are displayed in Table 1.
8. Click Add.
9. Click Assign.





Table 1. RBAC roles

 RBAC role Role permissions 

 Viewer A user with this role can view images. 
 Operator A user with this role can use images. 
 Editor A user with this role can create and delete images 



You now have access group permissions in the resource group. To assign users to this access group, click the Users tab of the access group and Add Users.







 Using an image with custom access controls within your VPC 

Virtual server instances and images can be in different resource groups. This difference allows for straight control of each resource type independently. You can start virtual server instances from the custom images if the user has appropriate authority to both resource groups.

Make sure that any user that needs to deploy a custom image has at least the Operator or Editor role in the previous access group. If they have only the Viewer role, then they can't deploy the custom image.
"metadata_region_backup": "REGION",
"private_api_endpoint_only": false
}'

Where:

ENDPOINT
: Is the API endpoint in the region where you plan to configure or manage a target. For more information, see [Endpoints](https://cloud.ibm.com/docs/atracker?topic=atracker-endpointsendpoints_api).

default_targets
: Is a list of target IDs. If no routing rules cause events to be sent to other targets, these targets will received the events.

permitted_target_regions
: Is the list of regions that can be used to define a target. A maximum of two permitted target regions can be specified.

metadata_region_primary
: Is the region where the metadata associated with route and target definitions is stored.

metadata_region_backup
: Is the region where the metadata associated with route and target definitions is stored as a backup location.

private_api_endpoint_only
: Specifies whether nor not a private endpoint can be used. If true only a private endpoint can be used.





 HTTP response codes 

When you use the IBM Cloud Activity Tracker Event Routing REST API, you can get standard HTTP response codes to indicate whether a method completed successfully.



* A 200 response always indicates success.
* A 4xx response indicates a failure.
* A 5xx response usually indicates an internal system error.



See the following table for some HTTP response codes:



Table 2. List of HTTP response codes

 Status code Status Description 

 200 OK The request was successful. 
 201 OK The request was successful. A resource is created. 
 400 Bad Request The request was unsuccessful. You might be missing a parameter that is required. 
 401 Unauthorized The IAM token that is used in the API request is invalid or expired. 
 403 Forbidden The operation is forbidden due to insufficient permissions. 
 404 Not Found The requested resource doesn't exist or is already deleted. 
 429 Too Many Requests Too many requests hit the API too quickly. 
 500 Internal Server Error Something went wrong in IBM Cloud Activity Tracker Event Routing processing.
[Peer enrollment and TLS certificate expiration](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/peer-cert-expiry.png)

Figure 6. Peer enrollment and TLS certificate expiration



1. Open the peer and click the Settings icon.
2. Click Update certificates. You can renew either the Enrollment certificate or the TLS certificate or both, based on their expiration dates.
3. In the drop-down box for each certificate type, select Re-enroll certificate if the certificate has not expired, or Enroll certificate if it has already expired.
4. When you click Update certificates, the peer is restarted. Verify the renewal is successful by clicking the refresh icon and examining the updated enrollment and TLS certificate expiration dates.

Zoom

![Certificate refresh button](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/cert-refresh.png)

Figure 7. Certificate refresh button



While the console does not allow you to set custom expiration dates for certificates, notice that the Peer TLS certificate expiration date is in 15 years, so that renewal of this TLS certificate is not required again next year. However, the peer enrollment certificate expires again in one year, so you will need to renew it again before that date.

An alternative to renewing these certificates is to simply deploy a new peer, and then delete the peer with expired certificates. You would need to configure the new peer on the network in the same way the existing peer is configured, namely:



* Join it to the same channel or channels.
When you use the IBM Cloud Metrics Routing REST API, you can get standard HTTP response codes to indicate whether a method completed successfully.



* A 200 response always indicates success.
* A 4xx response indicates a failure.
* A 5xx response indicates an internal system error.



See the following table for some HTTP response codes:



Table 2. List of HTTP response codes

 Status code Status Description 

 200 OK The request was successful. 
 201 OK The request was successful. A resource is created. 
 400 Bad Request The request was unsuccessful. You might be missing a parameter that is required. 
 401 Unauthorized The IAM token that is used in the API request is invalid or expired. 
 403 Forbidden The operation is forbidden due to insufficient permissions. 
 404 Not Found The requested resource doesn't exist or is already deleted. 
 429 Too Many Requests Too many requests hit the API too quickly. 
 500 Internal Server Error Something went wrong in IBM Cloud Metrics Routing processing.
--json or -j Deprecated Prints the output in the JSON format. 
 --output or -o Optional Returns the command-line output in JSON format. Currently only JSON file format is supported. 



Example

ibmcloud schematics workspace action --id myworkspace-a1aa1a1a-a11a-11





 ibmcloud schematics workspace delete 

Delete a workspace from your IBM Cloud account. The deletion of your workspace does not remove any IBM Cloud resources that you provisioned with this workspace. You can access and work with your resources from the IBM Cloud dashboard directly, but you cannot use IBM Cloud Schematics to manage your resources after you delete the workspace.

IBM Cloud Schematics supports 50 API requests per minute, per host, and per customer. The host can be us-east, us-south, eu-gb, or eu-de region. You need to wait before calling the command again. The table describes the delete workspace and destroy resources with the action.

Decide if you want to delete the workspace, any associated resources, or both. This action cannot be undone. If you remove the workspace and keep the resources, you need to manage the resources with the resource list or CLI.



delete workspace and associated resource

 Action Delete workspace Delete all associated resources 

 Delete workspace True False 
 Delete only resources False True 
 Delete workspace and the resources provisioned by workspace True True 
 Resources destroyed using command-line or resource list, and want to delete workspace True False 



Syntax

ibmcloud schematics workspace delete --id WORKSPACE_ID [--force]

Command options



Schematics Workspaces delete flags

 Flag Required / Optional Description 

 --id or -i Required The unique identifier of the workspace that you want to remove. To find the ID of your workspace, run ibmcloud schematics workspace list command. 
 --force or -f Optional Force the deletion of your workspace without command-line prompts. 



Example
For more information, see [End of general support for vSphere 6.5 and vSAN 6.5 or 6.6](https://kb.vmware.com/s/article/83223) and [VMware product lifecycle matrix](https://lifecycle.vmware.com//).

Instances with IBM Cloud bare metal servers with vSphere 6.7 cannot be ordered post 21 June 2022. IBM Cloud support for ordering all update levels of VMware vSphere 6.5 ended on 10 October 2021, and VMware vSphere 6.5 cannot be ordered post 21 June 2022.

IBM Cloud recommends an upgrade to vSphere 7.x. If you ordered your servers from the VMware Solutions console, the VMware vSphere offering, you have the following options.



* Check whether your server and its hardware options are compatible with vSphere 7.0. For more information, see [VMware compatibility guide](https://www.vmware.com/resources/compatibility/search.php). Alternatively, you can upgrade your vCenter Server, set up vSphere Update Manager (VUM) or vSphere Lifecycle Manager, and run hardware compatibility checks for the upgrade.
* Order new IBM Cloud bare metal servers with vSphere 7.x from the VMware Solutions console, the VMware vSphere offering, configure your vSphere host and vCenter Server, and migrate the workloads. After the workloads are migrated, you can remove the ESXi hosts from vCenter and decommission the old servers from the IBM Cloud portal.







 I have VMware Solutions - vCenter Server with NSX-V, IBM Cloud Bare Metal Servers with vSphere 6.5 or 6.7, and the support is ending. What do I need to do to keep the environment supported, and what options do I have? 

General support for vSphere 6.x ended on 15 October 2022.
Verify that the driver is removed from your cluster.



1. List of the storage classes in your cluster and verify that the storage classes are removed.

oc get sc
2. List the pods in the kube-system namespace and verify that the storage driver pods are removed.

oc get pods -n kube-system | grep azure



4. Optional: Remove the storage configuration.



1. List the storage configurations.

ibmcloud sat storage config ls
2. Remove the storage configuration.

ibmcloud sat storage config rm --config <config_name>











 Parameter reference 



 1.9.0 parameter reference 



Table 1. 1.9.0 parameter reference

 Display name CLI option Type Description Required? Default value 

 Tenant ID tenantId Secret Tenant ID : The Azure tenant ID that you want to use for your configuration. You can find your tenant ID in the Azure portal or by running the az account tenant list command. true N/A 
 Subscription ID subscriptionId Secret Your Azure subscription ID. From the Azure portal, search for Subscription to find a list of your subscriptions. You can also find your subscription ID by running the az account subscription list command. true N/A 
 Azure Active Directory Client ID aadClientId Secret Your Azure Active Directory Client ID. You can find your Client ID in the Azure portal or by running the az ad sp list --display-name appDisplayName command. true N/A 
 Location location Config The location of your Azure hosts. You can find the location of your virtual machines in the Azure portal or by running the az vm list command. Example location: useast. true N/A 
 Azure Active Directory Client Secret aadClientSecret Secret Your Azure Active Directory Client Secret. You can find your client secret in the Azure portal under the App registrations menu. true N/A 
 Resource Group resourceGroup Config The name of your Azure resource group. You can find your resource group detail in the Azure portal or by running the az group list command. true N/A
Schematics state move flags

 Flag Required / Optional Description 

 --id or -i Required The unique ID of the workspace for which you want to move an instance or resource. To find the ID of your workspace, run ibmcloud schematics workspace list command. 
 --source or -s Required Enter the source address of an item to move. 
 --destination or -d Required Provide the destination address of an item. 



Example

ibmcloud schematics workspace state mv --id myworkspace-a1aa1a1a-a11a-11 -s testsourceresource -d null_resource.sleep





 ibmcloud schematics workspace state rm 

Removes an instance or resources from the Terraform state. For example, if you remove an instance from the state, the Schematics Workspaces instance continues running, but Terraform plan cannot see that instance. You can use the workspace ID to retrieve the logs by using the [ibmcloud schematics logs](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-logs) command.

ibmcloud schematics workspace state rm --id WORKSPACE_ID [--options OPTIONS] --address PARAMETER

Command options



Schematics state remove flags

 Flag Required / Optional Description 

 --id or -i Required The unique identifier of the workspace for which you want to remove the instance or resource. To find the ID of your workspace, run ibmcloud schematics workspace list command. 
 --options or -o Optional Enter the option flag that you want to remove. 
 --address or -adr Required Enter the address of the resource to mark as taint. 



Example

ibmcloud schematics workspace state rm --id myworkspace-a1aa1a1a-a11a-11 --address null_resource.sleep --destination null_resource.slept







 Workspaces commands 

Review the commands that you can use to set up and work with your IBM Cloud Schematics Workspace.



 ibmcloud schematics workspace action
If the version parameter is not declared in your versions.tf file, the latest version of the provider plug-in is automatically used in Schematics. For more information, refer to [Version constraints for the Terraform providers](https://cloud.ibm.com/docs/schematics?topic=schematics-version-constraintsprovider-version-contraint).
* How can I deploy one resources in two different IBM Cloud account?

Use alias concept for deploying resource into your different IBM Cloud account as you can target provider with different accounts. For more information, about the configuration, see [Creating multiple provider configurations](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-provider-referencemultiple-providers).
* Can I automate the certificates to the Secrets Manager by using Terraform provider?

No, currently there is no option for automation for moving the certificates to the Secrets Manager. As part of the workaround you can create a Secrets Manager with [ibm_resource_instance](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/resource_instance).

resource "ibm_resource_instance" "secret_manager" {
name = "test"
service = "secrets-manager"
plan = "trial"
location = "us-south"
resource_group_id = ibm_resource_group.group.id
parameters = {
kms_info = data.ibm_resource_instance.kms.id
kms_key = ibm_kms_key.secrets_manager_root_key.id
}
}



WebSphere Application Server



* What products can I install with WebSphere Application Server?

You can install a WebSphere Application Server traditional environment on a virtual server instance (VSI) on IBM Cloud. For a description of the topologies that you can install with WebSphere Application Server, see [Topologies](https://cloud.ibm.com/docs/was-for-vsi?topic=was-for-vsi-topologies).
In the navigation menu, select Observability.
3. Select Monitoring.

The list of instances that are available on IBM Cloud is displayed.
4. Select your instance. Then, click Open dashboard.



IIt may take some time before you see the server entry while the information is initally collected and processed by the monitoring agent.

You only can monitor one instance per browser. You could have multiple tabs for the same instance.





 Step 5: Monitor your Ubuntu server 

You can monitor your Ubuntu server in the Overview view that is available through the Web UI. This view is your starting point to troubleshoot and monitor your infrastructure. It is the default homepage of the Web UI.

In the section Hosts & containers, you can find the entry for your Ubuntu server. Click Hosts & containers![Hosts & containers](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/switch_hosts.png) to switch data sources. Then, select your Ubuntu server. The data that is displayed corresponds to the selected server.

To configure color-coding for a column, complete the following steps:



1. Select a column by hovering your mouse over the column title. Then, click the pencil icon.
2. Toggle Enable to enable color-coding.
3. Set values for the different thresholds.







 Next steps 



* Create a custom dashboard. For more information, see [Working with dashboards](https://cloud.ibm.com/docs/monitoring?topic=monitoring-dashboardsdashboards).
* Learn about alerts. For more information, see [Working with alerts](https://cloud.ibm.com/docs/monitoring?topic=monitoring-monitoringmonitoring_alerts).
* Learn how to manage logs.
4. Review your Order Summary.
5. Select I read and agree to the following Third-Party Service Agreements.

You can create your server, save the order as a quote to provision later, or add the order to an estimate, which might include multiple services.
6. Click Create to be redirected to the Checkout page after your order is verified.



You are redirected to a page with your order number. The page is your receipt; print the page for your records. You also receive a confirmation email with the subject Your IBM Cloud Order ## has been approved. The ## is your order number.

Depending on your order, the server is available for use within one to four hours after the order is submitted. You can check Device Details from the IBM Cloud console (Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon-hamburger.svg) > Resource List > Devices) for the status of the provisioning steps. Click the Device Name that matches your given Hostname and Domain to see its status.





 Bring your own license 

If you have your own operating system license, you install it on your Bare Metal Servers based on the vendor's instructions. For more information, see [The no OS option](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-bm-no-osbm-no-os).





 Access your server 

A public IP is used for remote access, so you can connect to your server through an ssh client (for example, PuTTY on Microsoft Windows). Use the public IP address displayed in the Device List (Classic Infrastructure > Devices) for your device. The root password for your server is also displayed. Click Show Password to see it.





 Partitioning and file systems 

For the three-tier example, a 192 GB database server with one logical disk (on RAID10) and a 32 GB application server with one logical disk (on RAID 1) were ordered. Both servers come with one large root file system that is equal to the total size of disk (with some space that is used for /boot).
Instances with IBM Cloud bare metal servers with vSphere 6.7 cannot be ordered post 21 June 2022. IBM Cloud support for ordering all update levels of vSphere 6.5 ended on 10 October 2021, and vSphere 6.5 cannot be ordered post 21 June 2022.

IBM Cloud recommends an upgrade to vSphere 7.x. If you ordered your servers from the Bare metal catalog for IBM Cloud Classic Infrastructure, you have the following options.



* Check whether your server and its hardware options are compatible with vSphere 7.0. For more information, see [VMware compatibility guide](https://www.vmware.com/resources/compatibility/search.php). Alternatively, if you are running vCenter, you can upgrade your vCenter, set up vSphere Update Manager (VUM) or vSphere Lifecycle Manager, and run Hardware Compatibility Checks for the upgrade.
* Order new IBM Cloud bare metal servers with vSphere 7.x from the Bare metal catalog for IBM Cloud Classic Infrastructure or from the VMware Solutions console, the vSphere offering. Configure your vSphere host and vCenter Server and migrate the workloads. After the workloads are migrated, you can remove the VMware ESXi™ hosts from vCenter Server and decommission the old servers through the IBM Cloud portal.







 I have VMware Solutions - VMware vSphere, IBM Cloud bare metal servers with vSphere 6.5 or 6.7, and the support is ending. I am not using NSX for my workloads. What do I need to do to keep the environment supported, and what options do I have? 

General support for vSphere 6.x ended on 15 October 2022. For more information, see [End of general support for vSphere 6.5 and vSAN 6.5 or 6.6](https://kb.vmware.com/s/article/83223) and [VMware product lifecycle matrix](https://lifecycle.vmware.com//).

Instances with IBM Cloud bare metal servers with vSphere 6.7 cannot be ordered post 21 June 2022.