vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Planning for Cyber Recovery 

Review the following requirements before you order your Cyber Recovery instance. Plan your instance based on the IBM Cloud® data center location, your capacity requirements, and services requirements.



 Account requirements 

The account that you are using must meet certain requirements. For more information, see [Signing up for required accounts](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-signing_required_accounts).





 IBM Cloud data center availability 

The Cyber Recovery deployment has strict requirements on the physical infrastructure. Therefore, you can deploy instances only in IBM Cloud data centers that meet the requirements.



 Data centers available 

The following IBM Cloud data centers are available for Cyber Recovery.

Asia-Pacific

Europe

NA East



Table 1. Available IBM Cloud data centers for Cyber Recovery

 Geography Data center Pod 

 Asia-Pacific CHE01 01 
 Asia-Pacific OSA21 01 
 Asia-Pacific OSA22 01 
 Asia-Pacific OSA23 01 
 Asia-Pacific SNG01 02 
 Asia-Pacific SYD01 01-02 
 Asia-Pacific SYD04 01 
 Asia-Pacific SYD05 01 
 Asia-Pacific TOK02 01-02 
 Asia-Pacific TOK04 01 
 Asia-Pacific TOK05 01 









 Services for Cyber Recovery 

The following services and components are required for Cyber Recovery instances.



* [Veeam Backup and Replication 12](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-veeamvm_overview) is required and also included. For Veeam, a Linux hardened repository is selected for you.
* An edge gateway is required. You can bring your own gateway appliance or choose from the following options:



* Gateway cluster with Juniper® vSRX
* Gateway cluster with FortiGate® Virtual Appliance
* FortiGate Security Appliance
* [Glossary of HCX terms](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-hcx_glossary)
* [Contacting IBM Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support)
* [VMware Hybrid Cloud Extension overview](https://cloud.vmware.com/vmware-hcx)
* [VMware Hybrid Cloud Extension documentation](https://cloud.vmware.com/vmware-hcx/resources)
"images": [{"id": "r134-14903434-faf0-4a66-b861-7b35198de393", "name": "virtual-server-image", "region": "us-south"}]
}
}'
Show more







 ibmcloud catalog offering list 

Run the following command to get details about the products in your private catalogs. This command provides a filter by private catalog, product, and version.

ibmcloud catalog offering list [--catalog CATALOG] [--offering OFFERING_NAME] [--version VERSION] [--output FORMAT]



 Command options 

--catalog CATALOG
: The catalog name or ID.

--output FORMAT (optional)
: Specifies output format. The default is terminal compatible and the only supported alternative is JSON, for example, --output json.





 Example 

List all of the products that are in the dev-catalog catalog.

ibmcloud catalog offering list --catalog dev-catalog





 Output 

The command returns the following output:

Name ID Current State Version Locator
Cloud Pak for Automation cb90274e-398b-4373-9b28-d6428d3302df
|__OpenShift
|__19.0.2 New 7b7e590f-259b-437b-b1f4-39e8615ed837.21d1d712-80ab-4318-9d05-73c6caaaee23
Cloud Pak for Data 8993c7b1-1794-4447-9275-db83faa08ee4
|__OpenShift
|__2.1.0.2 New 7b7e590f-259b-437b-b1f4-39e8615ed837.ab6ba56f-788d-4d6b-b880-a1001fca8451
harbor 927adb44-6784-4bec-a771-f639900f07f1
* [Provision a IBM Cloud VPC for VMware deployment](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmware-vpcvpc-bm-vmware-vpc)
* [Provision IBM Cloud DNS Services for VMware deployment](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmware-dnsvpc-bm-vmware-dns)
* [Provision bare metal servers for VMware deployment](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmware-bmsvpc-bm-vmware-bms)
* [Provision vCenter Appliance](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmware-vcentervpc-bm-vmware-vcenter)
* [Provision vSAN storage cluster](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmware-vsanvpc-bm-vmware-vsan) or [Provision NFS storage and attach to cluster](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmware-nfsvpc-bm-vmware-nfs)



[Login](https://cloud.ibm.com/docs/cli?topic=cli-getting-started) with IBM Cloud CLI with username and password, or use the API key. Select your target region and your preferred resource group.
Logging (ibmcloud logging) CLI 

The IBM Cloud® command-line interface (CLI) provides extra capabilities for service offerings. This information describes how you can use the CLI to list and export information for IBM Log Analysis service instances for an account.

Exporting using the UI uses the [V1 export API](https://cloud.ibm.com/apidocs/log-analysisexport) and is limited to the functionality provided by that version of the API.



 Prerequisites 



* Install the [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started).
* Install the Logging CLI by running the following command:

ibmcloud plugin install logging



You're notified on the command line when updates to the IBM Cloud CLI and plug-ins are available. Be sure to keep your CLI up to date so that you can use the latest commands. You can view the current version of all installed plug-ins by running ibmcloud plugin list.





 ibmcloud logging service-instances 

Use this command to list the service instances for IBM Log Analysis.

ibmcloud logging service-instances [OPTIONS]



 Command options 

--service-name <NAME> | --sn <NAME>
: Name of the service.

--region <NAME> | -r <NAME>
: Name of the region, for example, us-south or eu-gb. If not specified, the region logged into or targeted will be used.

--all-regions
: Services hosted across all regions.

-g <GROUP>
: Resource Group associated with the hosted service.

--all-resource-groups
: Services hosted across all resource groups.

--quiet | -q
: Supresses verbose output.

--output <TYPE>
: A comma-separated list of output preferences enclosed in double-quotes ("). If only a single preference is specified, the double-quotes can be omitted. Supported options are WIDE and JSON.

If JSON is specified, output will be returned in JSON format.
IBM Cloud App ID 99.999% [Understanding high availability and disaster recovery for App ID](https://cloud.ibm.com/docs/appid?topic=appid-ha-dr) 
 IBM Cloud Certificate Manager 99.999% [Understanding high availability and disaster recovery for Certificate Manager](https://cloud.ibm.com/docs/certificate-manager?topic=certificate-manager-ha-dr) 









 Service level objectives for other IBM Cloud services 



Table 18. Service level objectives (SLOs) for other IBM Cloud services

 Service Availability target 

 Any product not listed 99.99%
[High availability for IBM Cloud resources](https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/schematics-ha-roadmap.png)

Figure 1. High availability for IBM Cloud resources



1. Single zone resources: By default, your IBM Cloud resource is deployed into one zone. This setup does not protect your workloads or data from a zonal or regional failure.
2. Multiple resources across zones: You can create multiple instances and spread these instances across zones, such as [multizone clusters in IBM Cloud Kubernetes Service](https://cloud.ibm.com/docs/containers?topic=containers-ha_clustersmz-clusters) or a [Virtual Private Cloud with subnets in different zones](https://cloud.ibm.com/docs/vpc?topic=solution-tutorials-vpc-multi-regionvpc-multi-region). This setup protects your workloads and data in case of a zonal failure. Note that this setup might not be available for your resource.
3. Multiple resources across regions: You can create multiple instances and spread these instances across regions, such as [multiple clusters in IBM Cloud Kubernetes Service](https://cloud.ibm.com/docs/containers?topic=containers-ha_clustersmz-clusters). This setup provides the highest availability for your workloads and data in case of a zonal or regional failure. Note that this setup might not be available for your resource.
ibmcloud sat subscription update --subscription myapp_prod_subscription --name myapp_staging_subscription --group mygroup --version 1.0









 Other commands 

Review other commands for managing Satellite resources, such as commands from other IBM Cloud services that might be useful.



 ibmcloud sat messages 

View current messages from IBM Cloud Satellite.

ibmcloud sat messages



 Minimum required permissions 

None





 Command options 

None







 Red Hat OpenShift on IBM Cloud commands (ibmcloud oc) 

For commands to manage Red Hat OpenShift clusters in your Satellite locations, such as ibmcloud oc cluster create satellite, see the [Red Hat OpenShift on IBM Cloud documentation](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clisat_commands).
* [Before you begin](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-logging-operational-tutorialopenshift-cluster-logging-prerequisites)
* [Provision Red Hat® OpenShift® on IBM Cloud®](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-logging-operational-tutorialsetup-openshift)
* [Provision a Red Hat OpenShift on IBM Cloud worker pool](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-logging-operational-tutorialprovision-worker-pool)
* [Install the Elasticsearch Operator](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-logging-operational-tutorialinstall-elasticsearch-operator)
* [Install the Cluster Logging Operator](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-logging-operational-tutorialinstall-logging-operator)
* [Create a cluster logging instance](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-logging-operational-tutorialcreate-logging-instance)



* [Starting Kibana](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-logging-operational-tutoriallaunching-kibana)



* [Set up virtual server instance logging with Fluentd](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-logging-operational-tutorialsetting-up-vsi-logging-with-fluentd)
You can access the app through IBM provided domain. Run the below command for the URL

oc get route/$MYPROJECT
3. Copy the HOST/PORT value and paste the URL in a browser to see your app in action at http://<HOST/PORT>. Also, set an environment variable pointing to the hostname

export HOST=<HOST>







 Secure the default IBM provided domain route 



1. To create a secured HTTPS route encrypted with the default certificate for Red Hat OpenShift on IBM Cloud, you can use the create route command.

oc create route edge $MYPROJECT-https --service=$MYPROJECT --port=3000
2. For the HTTPS HOST URL, run oc get routes. Copy and paste the URL with HTTPS(https://<HOST>){: external} next to the route $MYPROJECT-https in a browser.









 Step 3: Monitor the app 

In this section, you will learn to monitor the health and performance of your application. Red Hat OpenShift on IBM Cloud Container Platform ships with a pre-configured and self-updating monitoring and alerting stack.



1. In the Red Hat OpenShift on IBM Cloud web console, switch to the Administrator view.
2. Under Observe, select Metrics.
3. Run the below command with the route URL that generates load. The command will endlessly send requests to the application.

while sleep 1; do curl --max-time 2 -s http://$HOST/load/50; done
4. In the expression box, enter sum(node_namespace_pod_container:container_cpu_usage_seconds_total:sum_irate{namespace="<MYPROJECT>"}) by (container), replace <MYPROJECT> by your project name and click Run queries to see the total container cpu usage in seconds on a graph.
5. Under Observe, select Dashboards.
6. Click on the Dashboard dropdown and select Kubernetes / Compute Resources / Namespace (Workloads).
7.
ibmcloud oc worker-pool create satellite 

Satellite

Create a worker pool for your Red Hat OpenShift cluster in IBM Cloud Satellite.

ibmcloud oc worker-pool create satellite --cluster CLUSTER --host-label LABEL [--host-label LABEL ...] --name NAME [--operating-system SYSTEM] --size-per-zone WORKERS_PER_ZONE --zone ZONE [--label LABEL ...] [--output OUTPUT] [-q]

Minimum required permissions: IBM Cloud IAM Administrator platform access role for Satellite.

Command options:

-c, --cluster CLUSTER
: Required. The name or ID of the cluster.

--host-label, -hl LABEL
: Required. Enter at least one existing label that describes Satellite hosts, formatted as -hl key=value pairs, so hosts with matching labels can be automatically assigned to this worker pool. The labels that you specify must match the host labels exactly. For example, if you want a host that has 3 labels to be assigned to this worker pool, you must specify all 3 labels in 3 repeated options. To find available host labels, run ibmcloud sat host get --host <host_name_or_ID> --location <location_name_or_ID>.

--name POOL_NAME
: Required. The name that you want to give your worker pool.

--operating-system REDHAT_7_64|REDHAT_8_64|RHCOS
: Optional. The operating system of the worker nodes in your cluster. For a list of available operating sysems by cluster version, see [Available Red Hat OpenShift versions](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_versionsopenshift_versions_available). Note that to use your RHCOS hosts in your clusters, you must create a Red Hat CoreOS-enabled location and a cluster that runs version 4.9 or later.
IBM Cloud Kubernetes Service CLI reference 

Refer to these commands to create and manage both community Kubernetes or Red Hat OpenShift clusters in IBM Cloud® Kubernetes Service.



* Community Kubernetes: [Install the Kubernetes CLI plug-in](https://cloud.ibm.com/docs/containers?topic=containers-cli-install).
* OpenShift: [Install the Red Hat OpenShift CLI plug-in](https://cloud.ibm.com/docs/containers?topic=containers-cli-install).



In the command line, you are notified when updates to the ibmcloud CLI and plug-ins are available. Be sure to keep your CLI up-to-date so that you can use all available commands and options.

Looking for ibmcloud cr commands? See the [IBM Cloud Container Registry CLI reference](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregcli). Looking for kubectl commands? See the [Kubernetes documentation](https://kubectl.docs.kubernetes.io/).



 IBM Cloud Kubernetes Service commands 

The following tables list the ibmcloud ks command groups. For a complete list of all ibmcloud ks commands as they are structured in the CLI, see the [IBM Cloud Kubernetes Service CLI map](https://cloud.ibm.com/docs/containers?topic=containers-icks_map).



IBM Cloud Kubernetes Service CLI command groups

 Command group Description 

 [Cluster commands](https://cloud.ibm.com/docs/cli?topic=cli-kubernetes-service-clicluster) Create, view, and modify clusters and cluster settings, such as add-on, subnet, and master settings. 
 [Worker commands](https://cloud.ibm.com/docs/cli?topic=cli-kubernetes-service-cliworker_node_commands) View and modify worker nodes for a cluster.
IBM Cloud Kubernetes Service CLI reference 

Refer to these commands to create and manage both community Kubernetes or Red Hat OpenShift clusters in IBM Cloud® Kubernetes Service.



* Community Kubernetes: [Install the Kubernetes CLI plug-in](https://cloud.ibm.com/docs/containers?topic=containers-cli-install).
* OpenShift: [Install the Red Hat OpenShift CLI plug-in](https://cloud.ibm.com/docs/containers?topic=containers-cli-install).



In the command line, you are notified when updates to the ibmcloud CLI and plug-ins are available. Be sure to keep your CLI up-to-date so that you can use all available commands and options.

Looking for ibmcloud cr commands? See the [IBM Cloud Container Registry CLI reference](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregcli). Looking for kubectl commands? See the [Kubernetes documentation](https://kubectl.docs.kubernetes.io/).



 IBM Cloud Kubernetes Service commands 

The following tables list the ibmcloud ks command groups. For a complete list of all ibmcloud ks commands as they are structured in the CLI, see the [IBM Cloud Kubernetes Service CLI map](https://cloud.ibm.com/docs/containers?topic=containers-icks_map).



IBM Cloud Kubernetes Service CLI command groups

 Command group Description 

 [Cluster commands](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clicluster) Create, view, and modify clusters and cluster settings, such as add-on, subnet, and master settings. 
 [Worker commands](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-cliworker_node_commands) View and modify worker nodes for a cluster.
"expires_in": 3600,
"expiration": 1493747503
}

You can find your new IBM Cloud IAM token in the access_token, and the refresh token in the refresh_token field of your API output.
2. Continue working with the Red Hat OpenShift on IBM Cloud API documentation]https_containers.cloud.ibm.com_global_swagger-global-api] ! ! ! by using the token from the previous step.<-- </ol> --><-- </section "id="section-cs_api_refresh" "> --><-- <section "id="section-cs_cli_refresh" "> --> Refreshing IBM Cloud IAM access tokens and obtaining new refresh tokens with the CLI You can use the command line to set the cluster context]] , download the kubeconfig file for your Red Hat OpenShift cluster, and generate an IBM Cloud Identity and Access Management (IAM) ID token and a refresh token to provide authentication.You can use IBM Cloud IAM]] ! ! ! !
IBM Cloud File Storage for Classic plug-in and monitor 427 429 Updated universal base image (UBI) to resolve CVEs. Updated Go to version 1.19.6 and updated dependencies. 
 Key Management Service provider v2.6.3 v2.6.4 Updated Go to version 1.19.7 and updated dependencies. 
 Load balancer and load balancer monitor for IBM Cloud Provider 2383 2420 Updated the image to resolve CVEs. 
 OpenVPN Operator image v1.4.20 v1.4.22 Updated ansible-operator to v1.28.0 to fix CVEs. 
 Red Hat OpenShift on IBM Cloud. 4.9.55 4.9.57 See the [Red Hat OpenShift on IBM Cloud release notes](https://docs.openshift.com/container-platform/4.9/release_notes/ocp-4-9-release-notes.htmlocp-4-9-57). 
 Red Hat OpenShift on IBM Cloud Control Plane Operator, Metrics Server, and toolkit v4.9.0-20230220 v4.9.0-20230314 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.9.0+20230314). 







 Change log for worker node fix pack 4.9.57_1584_openshift, released 27 March 2023 

The following table shows the changes that are in the worker node fix pack 4.9.57_1584_openshift. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 4.9.57_1580_openshift

 Component Previous Current Description 

 RHEL 7 Packages N/A N/A N/A 
 RHEL 8 Packages N/A N/A N/A 
 Red Hat OpenShift on IBM Cloud. N/A N/A N/A
IBM Cloud Controller Manager v1.25.9-7 v1.25.11-1 Updated to support the Kubernetes 1.25.11 release. Updated Go dependencies and to Go version 1.19.10. Updated calicoctl and vpcctl. 
 IBM Cloud File Storage for Classic plug-in and monitor 431 433 Updated Go to version 1.20.4. Updated UBI base image. 
 Key Management Service provider v2.6.6 v2.6.7 Updated Go dependencies and to Go version 1.19.10. 
 Load balancer and load balancer monitor for IBM Cloud Provider 2486 2584 Updated Go dependencies and to Go version 1.19.9. Updated base image. 
 Red Hat OpenShift on IBM Cloud 4.12.16 4.12.20 [https://docs.openshift.com/container-platform/](https://docs.openshift.com/container-platform/) 
 OpenVPN client 2.5.8-r0-IKS-674-amd64 2.6.4-r0-IKS-34-amd64 Upgrade openvpn to version 2.6.4-r0. 
 OpenVPN server 2.5.8-r0-IKS-673-amd64 2.6.4-r0-IKS-33-amd64 Upgrade openvpn to version 2.6.4-r0. 
 OpenVPN Operator image v1.4.23 v1.4.25 Updated OpenVPN configuration to provide shutdown grace period before terminating connections. 







 Change log for worker node fix pack 4.12.21_1547_openshift, released 19 June 2023 

The following table shows the changes that are in the worker node fix pack 4.12.21_1547_openshift. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 4.12.19_1546_openshift

 Component Previous Current Description 

 Red Hat OpenShift on IBM Cloud.
* New! IBM Cloud® Secrets Manager
* HPCS Router add-on
* Cloud Image Key Synchronizer add-on
* Block Storage for VPC add-on.
* Worker node fix pack



* [7 April 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-apr0722)



* Red Hat OpenShift on IBM Cloud clusters in Mexico City (MEX01) are deprecated and become unsupported later this year.
* Red Hat OpenShift on IBM Cloud default version update.
* CLI change log update



* [6 April 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-apr0622)



* Master fix pack update





* [March 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-mar22)



* [30 March 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-mar3022)



* Cluster autoscaler add-on



* [28 March 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-mar2822)



* Worker node fix pack update.



* [24 March 2022](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-relnotesopenshift-mar2422)



* IBM Cloud Object Storage plug-in
* Block Storage for VPC add-on.
* HPCS Router add-on
* Cloud Image Key Synchronizer add-on
Example command to create a version 4.11 configuration.

ibmcloud sat storage config create --location LOCATION --name NAME --template-name odf-local --template-version 4.11 --param "auto-discover-devices=AUTO-DISCOVER-DEVICES" [--param "osd-device-path=OSD-DEVICE-PATH"] --param "num-of-osd=NUM-OF-OSD" [--param "worker-nodes=WORKER-NODES"] --param "odf-upgrade=ODF-UPGRADE" --param "billing-type=BILLING-TYPE" [--param "ibm-cos-endpoint=IBM-COS-ENDPOINT"] [--param "ibm-cos-location=IBM-COS-LOCATION"] [--param "ibm-cos-access-key=IBM-COS-ACCESS-KEY"] [--param "ibm-cos-secret-key=IBM-COS-SECRET-KEY"] --param "cluster-encryption=CLUSTER-ENCRYPTION" --param "iam-api-key=IAM-API-KEY" --param "perform-cleanup=PERFORM-CLEANUP" --param "kms-encryption=KMS-ENCRYPTION" [--param "kms-instance-name=KMS-INSTANCE-NAME"] [--param "kms-instance-id=KMS-INSTANCE-ID"] [--param "kms-base-url=KMS-BASE-URL"] [--param "kms-token-url=KMS-TOKEN-URL"] [--param "kms-root-key=KMS-ROOT-KEY"] [--param "kms-api-key=KMS-API-KEY"] --param "ignore-noobaa=IGNORE-NOOBAA"

Example command to create a version 4.12 configuration.