vania-janet/multiturn-rag-retrieval-data huggingface dataset:
This deployment facilitate communication to all components that are addressed out of the IBM Cloud RFC1918 address space. These components include vSphere hosts, vCenter, Platform Services Controller (PSC), NSX Manager, and NSX Controllers™. An NSX Load Balancer is used along with a VIP for HA.
* Customer workloads use IP addressing from the BYOIP address space so this design uses Remote Collectors that are hosted in a VXLAN. These remote collectors are not configured as part of the IBM Cloud® for VMware Solutions automation and must be manually implemented by the client.



Zoom

![Operations Manager components diagram](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/opsmgmt-vropscomponent.svg)

Figure 2. Operations Manager components

The VMware Aria Operations Analytics Cluster is accessed by using a management user interface or by using an API and it integrates with the following components:



* vCenter
* VMware Aria Operations™ for Logs



The client can manually integrate into the following products if they are deployed.



* VMware Aria® Automation™
* VMware Aria Business



VMware Aria Operations collects data from the following items.



* vSphere - vCenter, PSC, vSphere hosts
* NSX - NSX Manager, NSX Controllers, and NSX Edges
* VMware Aria Operations for Logs



The client can configure VMware Aria Operations manually to collect data from VMware Aria Automation and VMware Aria Business for Cloud.



 System requirements 

The analytics cluster consists of one primary node, one primary replica node, and two data nodes to enable scaling out and high availability. More data nodes are added to scale up. The analytics cluster can scale to a maximum of eight medium-sized nodes.

Primary/replica node system settings

Data node system settings



Table 1. Operations Manager primary/replica node system settings

 Attribute Specification 

 vCPU 8 
 Memory 32 GB
* @provision.json: Structure the JSON file as shown in the following example. Use the access and secret key from the response the of Cloud Object Storage service key creation call.



Example of the provision.json file
: Sample JSON file:

{
"default_runtime": {
"spark_version": "3.1" },
"instance_home": {
"region": "us-south",
"endpoint": "https://s3.direct.us-south.cloud-object-storage.appdomain.cloud",
"hmac_access_key": "<your-hmac-access-key>",
"hmac_secret_key": "<your-hmac-secret-key>"}
}

Example
: Enter:

ibmcloud resource service-instance-create test-ae-service ibmanalyticsengine standard-serverless-spark us-south -p @ae_provision.json

Response
: The example returns:

Creating service instance test-ae-service in resource group <Resource Group Name> of account <Account Name> as <email id>...

OK

Service instance test-ae-service was created.
Name: test-ae-service
ID: crn:v1:bluemix:public:ibmanalyticsengine:us-south:a/183aac93b485e:181eabe1-709781b::
GUID: 181ea9ee01b
Location: us-south
State: provisioning
Type: service_instance
Sub Type:
Service Endpoints: public
Allow Cleanup: false
Locked: false
Created at: 2022-01-03T08:40:25Z
Updated at: 2022-01-03T08:40:26Z
Last Operation:
Status create in progress
Message Started create instance operation
Show more
2. Check the status of the Analytics Engine service:

Action
: Enter:
If the SAP instances are managed by only cluster tools, the implementation of sap_cluster_connector is not necessary.

Install the packages for the resource agent and the SAP Cluster Connector library. For more information, see [How to enable the SAP HA Interface for SAP ABAP application server instances managed by the RHEL HA Add-On](https://access.redhat.com/solutions/3606101)

On both nodes, run the following commands.

If needed, use subscription-manager to enable the SAP NetWeaver repository. The [RHEL for SAP Subscriptions and Repositories](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_for_sap_solutions/8/html/rhel_for_sap_subscriptions_and_repositories/asmb_enable_repo_rhel-for-sap-subscriptions-and-repositories-8con_hana_rhel-for-sap-subscriptions-and-repositories-8) documentation describes how to enable the required repositories.

subscription-manager repos --enable="rhel-8-for-ppc64le-sap-netweaver-e4s-rpms"

Install the required packages.

dnf install -y resource-agents-sap sap-cluster-connector





 Configuring SAP Cluster Connector 

Add user ${sid}admto the haclient group.

On both nodes, run the following command.

usermod -a -G haclient ${sid}adm





 Adapting the SAP instance profiles 

Modify the start profiles of all SAP instances that are managed by SAP tools outside the cluster. Both ASCS and ERS instances can be controlled by the RHEL HA Add-On cluster and its resource agents. Adjust the SAP instance profiles to prevent an automatic restart of instance processes.

On NODE1, navigate to the SAP profile directory.

cd /sapmnt/${SID}/profile

Change all occurrences of Restart_Program to Start_Program in the instance profile of both ASCS and ERS.
Service name Description 

 IBM Cloud Object Storage The service instance that is owned by the customer who controls access to the instance by using IAM policies contains customer data, SQL query results, and metaindex information that describes value distribution in actual data objects. All data is encrypted in transit and at rest. To learn more, see [IBM Cloud Object Storage](https://cloud.ibm.com/docs/cloud-object-storage). 
 IBM® Db2® on Cloud Used to store SQL results in user-provided instances. To learn more, see [IBM Db2 on Cloud](https://cloud.ibm.com/docs/Db2onCloud). 
 IBM® Key Protect for IBM Cloud® The user-provided instances provide keys for envelope encryption of customer data in the job status database (IBM Cloudant) and passwords or apikeys for access to customer Db2. To learn more, see [IBM Key Protect for IBM Cloud](https://cloud.ibm.com/docs/key-protect). 
 IBM Cloud® Activity Tracker with LogDNA Data Engine integrates with IBM Cloud Activity Tracker with LogDNA to forward location audit events to the IBM Cloud Activity Tracker service instance that is set up and owned by you. To learn more, see [IBM Cloud Activity Tracker](https://cloud.ibm.com/docs/Activity-Tracker-with-LogDNA). 
 IBM® Event Streams for IBM Cloud® The user-provided instance contains the data that is streamed from a topic to a bucket of your choice. To learn more, see [Stream landing](https://cloud.ibm.com/docs/sql-query?topic=sql-query-event-streams-landing). 







 Other dependencies 



Table 3. Other

 Service name Description 

 IBM Cloud® Databases for Redis Used as UI session store and for caching of Cloudant data. To learn more, see [IBM Cloud Databases for Redis](https://cloud.ibm.com/docs/databases-for-redis). 









 Dependencies to third-party services 



Table 4. Dependencies

 Service name Description
"service_name": "cloud-object-storage",
"account_id": "ACCOUNT-ID"
},
{
"type": "serviceRef",
"ref": {
"service_name": "codeengine",
"account_id": "ACCOUNT-ID"
},
{
"type": "serviceRef",
"ref": {
"service_name": "containers-kubernetes",
"account_id": "ACCOUNT-ID"
},
{
"type": "serviceRef",
"ref": {
"service_type": "platform_service",
"account_id": "ACCOUNT-ID"
},
{
"type": "serviceRef",
"ref": {
"service_name": "iam-groups",
"account_id": "ACCOUNT-ID"
}
],
"excluded": []
}
}





 Creating network zones by using the CLI 

You can use the cbr-zone-create command to add network locations, VPCs, and service references to network zones. For more information, see the CBR [CLI reference](https://cloud.ibm.com/docs/account?topic=account-cbr-plugin). Add Security and Compliance Center to network zones as a service reference to allow Security and Compliance Center to access resources and services in your account that are the subject of a rule.

To find a list of available service refs, run the ibmcloud cbr service-ref-targets[command](https://cloud.ibm.com/docs/account?topic=account-cbr-plugincbr-cli-service-ref-targets-command). The service_name for SCC is compliance.

Example command to add the compliance service to a network zone.

ibmcloud cbr zone-create --name example-zone-1 --description "Example zone 1" --service-ref service_name=compliance
* An [IBM Cloud®](https://cloud.ibm.com/docs/account?topic=account-account-getting-started) account{: external}.
* A valid RHEL for SAP Applications or RHEL for SAP Solutions subscription is required to enable the repositories that you need to install SAP HANA and the resource agents for HA configurations.
* Virtual server instances need to fulfill the hardware and resource requirements for the SAP instances in scope. Follow the guidelines on instance types, storage, and memory sizing in the [Planning the Deployment](https://cloud.ibm.com/docs/sap?topic=sap-power-vs-planning-items) document.
* This information describes a setup that uses shareable storage volumes accessible on both cluster nodes. Certain file systems are created on shareable storage volumes so that they can be mounted on both cluster nodes. This setup applies to both instance directories.



* /usr/sap/<SID>/ASCS<Inst> of the ASCS instance.
* /usr/sap/<SID>/ERS<Inst> of the ERS instance.



Make sure that the storage volumes that were created for those file systems are attached to both virtual server instances. During SAP instance installation and RHEL HA Add-On cluster configuration, each instance directory must be mounted on its appropriate node. HA-LVM makes sure that each of the two instance directories is mounted on only one node at a time.

Different storage setups for the instance directories, for example, NFS mounts, are possible. Which means that the general storage setup steps and creation of cluster file system resources must be adjusted.
* The virtual hostname for ASCS instance and ERS instance must meet the requirements as documented in [Hostnames of SAP ABAP Platform servers](https://me.sap.com/notes/611361). Make sure that the virtual IP addresses for the SAP instances are assigned to a network adapter and that they can communicate in the network.
"instanceId":"fd692647-43d0-4699-9f83-f39a54b1327b"
},
"dataEvent":true,
"saveServiceCopy":true,
"correlationId":"ef56e7ed-abf5-4da4-bbf1-ac0d381891fd",
"logSourceCRN":"crn:v1:bluemix:public:kms:us-south:a/a12333e9bd28461a8c92385628efac9f:fd692647-43d0-4699-9f83-f39a54b1327b::"
}
Show more

This event shows the updated volume after a successful key rotation:

{
"payload": {
"id": "496cbc9b-3758-4eff-bc7d-f71a51be0e1d",
"eventTime": "2020-06-10T17:27:24.81+0000",
"action": "is.volume.volume.update",
"outcome": "success",
"message": "Block Storage for VPC: update volume my-encrypted-volume1",
"initiator": {
"id": "keyreact",
"typeURI": "service/security/account/user",
"name": "",
"host": {
"address": "192.0.2.0/24172",
"agent": "grpc-go/1.22.1"
},
"credential": {
"type": "token"
}
},
"target": {
For more information, see [Storage types](https://cloud.ibm.com/docs/hpc-spectrum-scale?topic=hpc-spectrum-scale-storage-types).





 Why are there two different resource group parameters that can be specified in the IBM Cloud catalog tile? 

The first resource group parameter entry in the Configure your workspace section in the IBM Cloud catalog applies to the resource group where the Schematics workspace is provisioned on your IBM Cloud account. The value for this parameter can be different than the one used for the second entry in the Parameters with default values section in the catalog. The second entry applies to the resource group where VPC resources are provisioned.





 Where are the Terraform files used by the IBM Spectrum Scale tile located? 

The Terraform-based templates can be found in this [GitHub repository](https://github.com/IBM/ibm-spectrum-scale-ibm-cloud-schematics).





 Where can I find the custom image name to image ID mappings for each cloud region? 

The mappings can be found in the image-map.tf file in this [GitHub repository](https://github.com/IBM/ibm-spectrum-scale-ibm-cloud-schematics).





 Can I use my own custom image in the Spectrum Scale cluster by specifying the image name in the deployment value bootstrap_osimage_name? 

No, you can't use your own custom image for the bootstrap node at this time. The bootstrap node image is configured with all of the required functions to set up the Spectrum Scale compute and storage resources.





 Can I connect directly through SSH to the bootstrap, compute, or storage nodes from a system external to IBM Cloud? 

No, any SSH connection to the bootstrap, compute, or storage nodes is only possible through the bastion node for security reasons. You would use the following command to connect to your bootstrap, compute, or storage nodes (the IP address is specific to your particular node): ssh -J ubuntu@<bastion_IP_address> vpcuser@<IP_address>





 Can I establish an SSH connection between compute and storage nodes?
Enabling automated registration of secondary instance 

You need to set the parameter AUTOMATED_REGISTER according to your operational requirements. If you want to keep the ability to revert to the state of the previous primary SAP HANA instance, then AUTOMATED_REGISTER=false avoids an automatic registration of the previous primary as a new secondary.

If you experience an issue with the data after a takeover that was triggered by the cluster, you can manually revert if AUTOMATED_REGISTER is set to false.

If AUTOMATED_REGISTER is set to true, the previous primary SAP HANA instance automatically registers as secondary, and cannot be activated on its previous history. The advantage of AUTOMATED_REGISTER=true is that high-availability capability is automatically reestablished after the failed node reappears in the cluster.

For now, it is recommended to keep AUTOMATED_REGISTER on default value false until the cluster is fully tested and that you verify that the failover scenarios work as expected.

The pcs resource update command is used to modify resource attributes and pcs resource update SAPHana_${SID}_${INSTNO} AUTOMATED_REGISTER=true sets the attribute to true.







 Testing SAP HANA System Replication cluster 

It is vital to thoroughly test the cluster configuration to make sure that the cluster is working correctly. The following information provides a few sample failover test scenarios, but is not a complete list of test scenarios.

For example, the description of each test case includes the following information.



* Component that is being tested
* Description of the test
* Prerequisites and the cluster state before you start the failover test
* Test procedure
* Expected behavior and results
* Recovery procedure





 Test1 - Testing failure of the primary database instance 

Use the following information to test the failure of the primary database instance.



 Test1 - Description 

Simulate a crash of the primary HANA database instance that is running on NODE1.





 Test1 - Prerequisites 



* A functional two-node RHEL HA Add-On cluster for HANA system replication.
* Both cluster nodes are active.
* Cluster that is started on NODE1 and NODE2.
* Cluster Resource SAPHana_${SID}_${INSTNO} that is configured with AUTOMATED_REGISTER=false.
* Check SAP HANA System Replication status:
View the job details of the last server instance capture 

ibmcloud pi instance-capture-show INSTANCE_ID [--json]



* INSTANCE_ID: The unique identifier or name of the instance.



Options



* --json: Format output in JSON



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







 ibmcloud pi instance-create 



 Create a server instance 

ibmcloud pi instance-create INSTANCE_NAME --image IMAGE [--memory MEMORY] <--network "NETWORK1 [IP1]"> [--processors PROCESSORS] [--processor-type PROC_TYPE] [--volumes "VOLUME1 VOLUMEn"] [--key-name NAME] [--sys-type TYPE] [--storage-type STORAGE_TYPE] [--storage-connection STORAGE_CONNECTION] [--storage-pool STORAGE_POOL] [--storage-affinity STORAGE_AFFINITY_POLICY] [--storage-affinity-instance INSTANCE] [--storage-affinity-volume VOLUME] [--storage-anti-affinity-instances "INSTANCE1 INSTANCEn]"] [--storage-anti-affinity-volumes "VOLUME1 VOLUMEn]"] [--replicants NUMBER] [--replicant-scheme SCHEME] [--replicant-affinity-policy AFFINITY_POLICY] [--pin-policy POLICY] [--IBMiCSS-license] [--IBMiDBQ-license] [--IBMiPHA-license] [--IBMiRDS-users NUMBER-USERS] [--placement-group GROUP_ID] [--shared-processor-pool SHARED_PROCESSOR_POOL] [--deployment-type TYPE] [--json]



* INSTANCE_NAME: The name of the instance.



Options



* --image value: Operating system image identifier or name.
* --memory value: Amount of memory (GB) to allocate to the instance. Default value is 2GB.
* networks value: (deprecated - replaced by network) Space-separated list of identifiers or names of the networks to associate with the instance.
Using Spectrum Scale storage 

IBM® Spectrum Scale is a cluster file system that provides simultaneous access to a single file system from multiple compute nodes. In the IBM Spectrum LSF offering, Spectrum Scale applications running in static compute cluster nodes with high-performance access to a shared data space. For more information, see the [IBM Spectrum Scale](https://www.ibm.com/docs/en/spectrum-scale/5.1.2) product documentation.

The IBM Spectrum LSF offering uses IBM Cloud VPC virtual server instance profiles that are provisioned with [instance storage](https://cloud.ibm.com/docs/vpc?topic=vpc-instance-storage) for the Spectrum Scale storage nodes. By virtue of being on instance storage, this storage option can be used for scratch data use cases. When a storage node virtual server instance is rebooted, the data is preserved. However, when the instance is deleted, the instance storage data is lost. There is no automatic replication to persistent storage, for example, IBM Cloud Object Storage, that is provided in the current implementation, but you can add it on your own if required.

Zoom

![Architecture diagram](https://cloud.ibm.com/docs-content/v1/content/74a831a53989757bd05bd0dea7bb42c9ede61d0f/ibm-spectrum-lsf/images/hpccluster_lsf_scale_architecture.svg)

Figure 1. Architecture diagram of an IBM Spectrum LSF cluster using Spectrum Scale storage on IBM Cloud



 Before you begin 

Before you begin, make sure to complete the steps for [Getting started with IBM Spectrum LSF](https://cloud.ibm.com/docs/ibm-spectrum-lsf?topic=ibm-spectrum-lsf-getting-started-tutorial).





 Configuring Spectrum Scale storage 

To configure and use Spectrum Scale storage, the spectrum_scale_enabled[deployment value](https://cloud.ibm.com/docs/ibm-spectrum-lsf?topic=ibm-spectrum-lsf-deployment-values) must be set to "true".
Plans can share APIs, but whether subscription approval is required depends upon the Plan itself. Additionally, you can enforce rate limits through Plans or through operations within a Plan's APIs that override the Plan's rate limit.

Plans can also specify billing costs for customers who use your Products. For example, you can define three different Plans for a single Product. Each Plan can have a different subscription cost and a different rate limit that targets different customers.





 Products 

Plans and APIs are grouped in Products. Through Products, you can manage the availability and visibility of APIs and Plans. Use the API Designer to create, edit, and stage your Product. Use the API Manager to manage the lifecycle of your Product.

The following diagram demonstrates how Products, Plans, and APIs relate to one another. Note how Plans belong to only one Product, can possess different APIs to other Plans within the same Product, and can share APIs with Plans from any Product. Figure to show the hierarchy of Products, Plans, and APIs. ![Figure to show the hierarchy of Products, Plans, and APIs.](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/images/plan_product_hierarchy.png)

You can create Plans only within Products, and these Products are then published in a Catalog. A lifecycle manager can then control the availability and visibility of APIs and Plans through the API Manager. Through the Developer Portal, the customer is then able to subscribe to one of the Plans that is available to them, as determined in the API Manager. If it is a Plan with billing, the customer must provide credit card information when subscribing. The user can subscribe to one Plan from a specific Product. Multiple Plans within a single Product are useful in that they can fulfill similar purposes but with differing levels of performance and cost. For example, you might have a "Demo Plan", which makes a single API available, and a "Full Plan", which makes several available.
Billing 

You can give users access to update account settings, view subscriptions, view offers, apply subscription and feature codes, update spending limits, and track usage by using the Billing service.



Table 3. Roles and example actions for the Billing service

 Roles Actions 

 Viewer View account feature settings<br><br>View subscriptions in account<br><br>View account name<br><br>View subscription balances and track usage 
 Operator View account feature settings<br><br>View subscriptions in account<br><br>View and change account name 
 Editor View and update account feature settings<br><br>View subscriptions in account<br><br>View offers in account<br><br>View and apply subscription and feature codes<br><br>View and change account name<br><br>View and update spending limits<br><br>Set spending notifications<br><br>View subscription balances and track usage 
 Administrator View and update account feature settings<br><br>View subscriptions in account<br><br>View offers in account<br><br>View and apply subscription and feature codes<br><br>View and change account name<br><br>View and update spending limits<br><br>Set spending notifications<br><br>View subscription balances and track usage<br><br>Create an enterprise 



It's possible to view subscription balances and usage from the Account settings page, but you can't view the Account settings page with the Viewer or Operator roles. To access the Account settings page and your subscription information from that page, you need the Editor role or higher.





 Catalog management 

You can give users access to view private catalogs and catalog filters, create private catalogs, add software to private catalogs, and set catalog filters.



Table 4. Roles and example actions for the catalog management service

 Roles Actions 

 Viewer View account-level filters set for the IBM Cloud catalog<br><br>View private catalogs 
 Operator Create private catalogs<br><br>Set filters for private catalogs<br><br>Add and update software<br><br>View account-level filters