vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Given the division of skills in traditional on-premises data center implementations of SAP workloads during previous decades, there were multiple tasks handled by the Data Center Provider. It is suggested to consider the skills of your SAP Partners in the following areas because the Cloud Service Provider is not responsible for those activities previously fullfilled by the Data Center Provider:



* Cloud account and IAM setup
* Networking setup (including security)
* Storage setup
* Infrastructure sizing for SAP
* OS configuration (including security)



Further information on [Moving SAP Workloads](https://cloud.ibm.com/docs/sap?topic=sap-faq-moving-sap-workloads) is described in the FAQ.







 Compute considerations 

Depending on the business requirements and risk acceptance, the primary decision for any Cloud IaaS running SAP workloads is which Cloud Tenancy model to use:



* Single-tenant infrastructure, dedicated compute resources that are accessed with a private logical network within the cloud provider network backbone that uses:



* Bare metal
* Virtual servers on dedicated hosts
* VMware SDDC



* Multi-tenant infrastructure, shared compute resources that are accessed with a private logical network within the cloud provider network backbone that uses virtual servers



After you decide on the Cloud Tenancy model that meets your business and IT risk needs, the focus is then on sizing and throughput requirements:



* Output of your [SAP sizing activities](https://cloud.ibm.com/docs/sap?topic=sap-sizingsizing-methodology)
* Benchmark metric "SAPS", which demonstrates the total transactional throughput of the infrastructure



More information that compares different infrastructure types is in [Comparing the different SAP-certified IaaS offerings](https://cloud.ibm.com/docs/sap?topic=sap-overviewiaas-offerings-compare-summary) with more detail under [Infrastructure certified for SAP](https://cloud.ibm.com/docs/sap?topic=sap-iaas-offerings). All SAPS benchmarks are listed for each profile under each infrastructure type that is offered in the IBM Cloud® for SAP portfolio.





 SAP HANA considerations
We provide a set of example [Calico private network policies](https://github.com/IBM-Cloud/kube-samples/tree/master/calico-policies/private-network-isolation) that further restrict public/private network traffic on cluster workers. These policies allow the traffic that is necessary for the cluster to function, and block certain other traffic.

These policies are not meant to block everything, nor do they necessarily meet any compliance requirements on their own. They are intended as a starting point and must be edited to meet your unique use cases. For more information, see the [README](https://github.com/IBM-Cloud/kube-samples/tree/master/calico-policies).

Whenever new locations for Red Hat OpenShift on IBM Cloud and other IBM Cloud are enabled, the subnets for these locations are added to the Calico policies. Be sure to [watch the GitHub repository](https://github.com/IBM-Cloud/kube-samples/tree/master/calico-policies/public-network-isolation) for any updates to these policies.

When you apply the egress pod policies that are in this policy set, only network traffic to the subnets and ports that are specified in the pod policies is permitted. All traffic to any subnets or ports that are not specified in the policies is blocked for all pods in all namespaces. Because only the ports and subnets that are necessary for the pods to function in IBM Cloud Kubernetes Service are specified in these policies, your pods can't send network traffic over the private network until you add or change the Calico policy to allow them to.

Before you begin, [install and configure the Calico CLI, and set the context for your cluster to run Calico commands](https://cloud.ibm.com/docs/openshift?topic=openshift-network_policiescli_install).



1. Clone the IBM-Cloud/kube-samples repository.

git clone https://github.com/IBM-Cloud/kube-samples.git
2. Go to the private policy directory for the region that your cluster is in.
A list of all SAP Partners is maintained on the [SAP Partner Finder tool](https://www.sap.com/partner/find/search-tool.html). The list has more information about SAP Partners, including:



* Partnership category (for example, Consulting & Implementation Services)
* Partnership level (for example, Platinum, Gold, Silver)



Awards for these SAP Partners are shown on the [SAP Partners information page](https://www.sap.com/partner/find.html).

These choices particularly affect how your SAP S/4HANA "AnyPremise" Edition on Cloud IaaS is deployed, operated, and maintained. For example, a GSI has exceeding depth of experience in implementation, functional configuration and development - with the flexibility to create a bespoke solution for the business requirements. However, the GSI has less experience in maintenance. Conversely, an MSP has more restrictions on the implementation to ensure more successful maintenance.

Given the division of skills in traditional on-premises data center implementations of SAP workloads during previous decades, there were multiple tasks handled by the Data Center Provider. It is suggested to consider the skills of your SAP Partners in the following areas because the Cloud Service Provider is not responsible for those activities previously fullfilled by the Data Center Provider:



* Cloud Account and IAM setup
* Networking setup (including security)
* Storage setup
* Infrastructure Sizing for SAP
* OS Configuration (including security)



Further information on [Moving SAP Workloads](https://cloud.ibm.com/docs/sap?topic=sap-faq-moving-sap-workloads) is described in the FAQ.







 Compute considerations 

Depending on the business requirements and risk acceptance, the primary decision for any Cloud IaaS running SAP workloads which Cloud Tenancy model to use:



* Single-Tenant infrastructure, dedicated compute resources that are accessed with a private logical network within the Cloud provider network backbone that uses:



* Bare Metal
* Virtual Servers on Dedicated Hosts
* VMware SDDC



* Multi-Tenant infrastructure, shared compute resources that are accessed with a private logical network within the Cloud provider network backbone that uses Virtual Servers
Getting certified in IBM Cloud 

Are you looking to get certified in IBM Cloud®? Whether your job role is technical or nontechnical, the IBM Center for Cloud Training has a no-cost, [role-based learning path](https://www.ibm.com/training/cloud/jobroles) to help guide you toward achieving certification. Start or continue building your cloud knowledge and skills today with training and certification from IBM.



 IBM Cloud Advocate 

Complete your [IBM Certified Advocate - Cloud v1](https://www.ibm.com/training/path/ibmcloudadvocate2022) training and gain a foundational knowledge of cloud computing, from core concepts, definition, and history to emerging trends. Areas of learning include cloud service and deployment models as well as key elements of cloud architecture.





 IBM Cloud Technical Advocate 

Training for all technical roles starts with [IBM Certified Technical Advocate - Cloud v3](https://www.ibm.com/training/path/ibmcloudtechnicaladvocate-q12022). Learn how to discuss and use IBM Cloud to solve business and technology transformation challenges. This learning path is recommended for all technical job roles and features practice exercises in a virtual lab environment.





 IBM Cloud Professional Architect 

As an [IBM Certified Professional Architect - Cloud v5](https://www.ibm.com/training/path/ibmcloudprofessionalarchitect) technical professional, you have the skills and knowledge to define and design complex technical solutions for large-scale environments. Extensive course updates reflect the latest technologies and best practices for IBM Cloud architecture.





 IBM Cloud Advanced Architect 

Designed for professionals with three or more years of experience working as cloud architects, [IBM Certified Advanced Architect - Cloud v1](https://www.ibm.com/training/path/ibmcloudadvancedarchitect) extends and validates your capabilities. This interactive curriculum offers a deeper exploration of the latest IBM technologies and best practices.





 IBM Cloud Professional Developer 

Gain the skills and knowledge that is required to build cloud services and large-scale business applications as an [IBM Certified Professional Developer - Cloud](https://www.ibm.com/training/path/ibmcloudprofessionaldeveloper) technical professional.
System entities 

Learn about system entities that are provided by IBM for you to use out of the box. These built-in utility entities help your assistant recognize terms and references that are commonly used by customers in conversation, such as numbers and dates.

System entities return an interpretation property. The information that is included by this property offers better date and time understanding and can classify mentions with more precision.

If you used an earlier product version and imported skills, review any dialog skills that use system entities. See if you can improve their detection capabilities by leveraging the new interpretation property.

For information about how to add system entities to your dialog skill, see [Creating entities](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-entitiesentities-enable-system-entities).

For information about how to use contextual entities to identify people and location names, see the [Detecting Names And Locations With Watson Assistant](https://medium.com/ibm-watson/detecting-names-and-locations-with-watson-assistant-e3e1fa2a8427) blog post on Medium.



 @sys-currency entity 

The @sys-currency system entity detects mentions of monetary currency values in user input. The currency can be expressed with a currency symbol or currency-specific terms. In either case, a number is returned.



 Recognized formats 



* 20 cents
* Five dollars
* $10







 Attributes 



* .literal: Exact phrase in input that is interpreted to be a currency mention.
* .numeric_value: Canonical numeric value as an integer or a double, in base units.
* .location: Lists the index element values of the first and last letters in the text string for the phrase that is interpreted to be a currency mention.
* .unit: Base unit of currency specified as a 3-letter ISO currency code. For example, USD or EUR.



The following table illustrates the information that each attribute captures from the user input.



@sys-currency examples

 Attribute Type Example (input = twenty dollars) Example (input = $1,234.56) 

 @sys-currency string 20 1234.56
* ACLs are applied at the level of the VPC subnet. If one cluster uses multiple subnets, rules are required to ensure that the subnets can communicate with each other. If you create multiple clusters that use the same subnets in one VPC, you can't use ACLs to control traffic between the clusters because they share the same subnets.
* With an ACL, you must explicitly allow traffic in both directions for a connection to succeed.



Regardless of which security option you choose, be sure to follow the instructions for [security groups](https://cloud.ibm.com/docs/containers?topic=containers-vpc-security-group) or [ACLs](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-acls) to allow the subnets and ports that are required for necessary traffic to reach your cluster.
* ACLs are applied at the level of the VPC subnet. If one cluster uses multiple subnets, rules are required to ensure that the subnets can communicate with each other. If you create multiple clusters that use the same subnets in one VPC, you can't use ACLs to control traffic between the clusters because they share the same subnets.
* With an ACL, you must explicitly allow traffic in both directions for a connection to succeed.



Regardless of which security option you choose, be sure to follow the instructions for [security groups](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-security-group) or [ACLs](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-acls) to allow the subnets and ports that are required for necessary traffic to reach your cluster.
Run migrate.sh as many times as necessary to fully back up your data.

Snapshots are incremental, so the first snapshot takes longer than the rest.

Once your COS bucket has all the necessary snapshots, stop any writes to the source. Then, run migrate.sh one more time to take a final snapshot and restore it to the target. All of your data is now in the target. Point your applications to the target database and your upgrade is complete.





 Retrieve and update user passwords 

If you're restoring to Elasticsearch 7.17 as an update from an earlier version, existing user passwords will be invalidated and must be reset after the restore. For more information, see [Retrieve and update user passwords](https://cloud.ibm.com/docs/databases-for-elasticsearch?topic=databases-for-elasticsearch-upgrading&interface=uiesupgrade-retrieve-update-user-passwords).
* Replace ${POSTGRES_POD} with the name of one of the Postgres pods from the previous step.



8. Stop the store deployment by scaling the store deployment down to 0 replicas:

oc scale deploy ibm-watson-assistant-operator -n ${OPERATOR_NS} --replicas=0
oc get deployments -l component=store

Make a note of how many replicas there are in the store deployment:

oc scale deployment ${STORE_DEPLOYMENT} --replicas=0
9. Initiate the execution of a remote command in the Postgres pod:

oc exec -it ${POSTGRES_POD} /bin/bash
10. Run the pgmig tool:

cd /controller/tmp/bu
export PG_CA_FILE=/controller/tmp/bu/ca.crt
./pgmig --resourceController resourceController.yaml --target postgres.yaml --source <backup-file-name.dump>



* Replace <backup-file-name.dump> with the name of the file that you created for your downloaded data.



For more command options, see [Postgres migration tool details](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-backupbackup-pgmig-details).

As the script runs, you are prompted for information that includes the instance on the target cluster to which to add the backed-up data. The data on the instance you specify will be removed and replaced. If there are multiple instances in the backup, you are prompted multiple times to specify the target instance information.
11. Scale the store deployment back up:

oc scale deployment ${STORE_DEPLOYMENT} --replicas=${ORIGINAL_NUMBER_OF_REPLICAS}
oc scale deploy ibm-watson-assistant-operator -n ${OPERATOR_NS} --replicas=1

You might need to wait a few minutes before the skills you restored are visible from the web interface.
12. After restoring the data, you have to train the backend model.
These objects include the ESXi hosts that deliver compute and storage resources to the user workloads. The IaaS security administrator is also afforded necessary access to the IBM Cloud console to deploy and manage network gateway devices. The IaaS security administrator might play a role in managing NSX-T security objects if those objects impact the security of the management and edge layers of the IBM Cloud for VMware Regulated Workloads. It is recommended that consideration is given to whether enabling the IaaS security administrator access to the NSX-T platform introduces unacceptable risk.
* IaaS network administrator - The IaaS network administrator scope is limited to the underlay networking necessary for operation of the management plane, edge services layer, and the hardware that delivers compute and storage resources to the workloads. The IaaS network administrator is provided necessary access to the IBM Cloud console to fulfill the assigned duties of the role. The IaaS network administrator has no access to the NSX-T portal.
* NSX-T administrators - The NSX-T administrators' access is limited to the NSX-T portal. The scope of duties of the NSX-T administrator is broad enough to create any necessary global network and security objects that are required to allow the necessary traffic flows. These flows must fully support the requirements of the workloads that use the network resources. The NSX-T administrator has no role in the networking or security of the management or edge layers of the IBM Cloud for VMware Regulated Workloads platform. The NSX-T network administrator might define more limited scopes for application or business group network administrators that can create network objects necessary for particular requirements.



The NSX-T administrator role can be separated into the following roles:



* NSX-T network super admin - responsible for deployment and operation of necessary shared network objects, such as T0 routers or edge gateways for the workloads.
* NSX-T network security admin - dedicated security admin that has responsibility that is limited to the firewall and security aspects of NSX-T.
* Tenant NSX-T admin - where wanted, scope that is limited to a function/application/business unit as applicable to manage resources with such limited scope. Would include deployment of T1 routers for example.







 Management cluster
When applications deploy to production, they get deployed to both US South and US East regions, and deployment validation testing is performed in dark mode (in the backup MZR). The testing can be just enough to validate that the app is ready should it be necessary to fail over.
7. There is currently no feature set in IBM Cloud Code Engine to replicate the configuration of one project to another one in a different region. Therefore, the customer team needs to ensure that all necessary configuration changes to the IBM Cloud Code Engine projects in all the regions are enforced.



Zoom

![Network architecture](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/overview/images/BCDR-Architecture-Diagram-Page-16.svg)

Figure 3. An architecture diagram for network architecture

Something to consider in hybrid architecture is the flow of traffic to the public internet. If there are no public VLANs or other direct connectivity to the public internet from IBM Cloud, all traffic to and from IBM Cloud to the public internet gets routed through your on premises network.

Therefore, any workload running in the US East region must traverse the IBM private network all the way from Washington DC to the west coast. In many instances, there might be multiple trips that are needed to complete requests to on premises systems. Latency is a factor that should be considered to achieve true active/active workload between US South and US East regions in this model.





 Application profiles 

One approach is to build a set of architecture profiles that represent most apps. These profiles include options for various classes of service, compute requirements, and all the other components that are listed.

Zoom

![Sample application architecture](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/overview/images/BCDR-Architecture-Diagram-image4_sample_architecture.svg)

Figure 4. An architecture diagram showing a sample application architecture



 Continuous availability profile
cloud_setup [-I | G | C] [-v]

-I: Install the necessary RPMs for universal CLI (supports COS).
-G: Install the necessary RPMs for gsutil CLI (Google Cloud Storage).
-C: Install the necessary RPMs for cloud-init.
-v: Enable debug output.



1. To begin, copy the file to the system that requires AWS and give it execute permission.
2. Enter the cloud_setup -I command to install the AWS CLI and all of the dependant RPMs.
3. After the installation is complete, you must configure awscli for access to COS and provide the correct region (where your bucket COS is defined) in the aws --endpoint-url s3 command. In the following example, the us-east region is used:



 export PATH=$PATH:/opt/freeware/bin

 aws configure
AWS Access Key ID [None]: d197axxxxxxxxxxxxxxxxxxxxxxxxxxxa4
AWS Secret Access Key [None]: f52a5xxxxxxxxxxxxxxxxxxxxxxx001a33b74d8
Default region name [None]: us-east
Default output format [None]: json

 aws --endpoint-url https://s3.us-east.cloud-object-storage.appdomain.cloud s3 ls
2019-01-28 13:32:40 poweriaastest

 aws --endpoint-url https://s3.us-east.cloud-object-storage.appdomain.cloud s3 ls s3://poweriaastest
2019-01-28 13:33:42 6832 nimstat.sh
2019-01-28 15:05:25 1380725 yum-3.4.3-5.aix6.1.noarch.rpm







 Additional backup strategies 

The additional backup strategies that you can use are as follows:
Oracle RAC, MS Exchange, and MS-SQL clusters are examples of applications where two or more VMs participate in a cluster that requires shared disk across all VMs or cluster nodes. The VMware® multi-writer flag needs to be enabled on all of the VM nodes for disks that are part of the application cluster (non-OS virtual disks). VMs with the multi-writer flag enabled for any virtual disk are not supported.

Review the following information about migrating a multi-writer virtual disk enabled cluster:



* vMotion is used, as the original VM disk and UUID mappings are maintained.
* The cluster remains up in a degraded state (single node) during migration.
* The cluster incurs downtime before the start of the migration and after the migration is complete to reassemble the multi-writer configuration across cluster VMs.



To migrate a multi-writer disk enabled cluster, complete the following steps:



1. Power off the cluster and all nodes per the application best practice.
2. Take note of the disk order, if the application requires it, in each node VM for the multi-writer configured virtual disks.
3. For Oracle and any other application that uses the virtual disk UUID feature, log in to an ESXi host and run the command vmkfstools -J getuuid /vmfs/volumes/datastore/VM/vm.vmdk. This command gets the UUID of each virtual disk file that requires the multi-writer flag set for the cluster. This step is necessary if best practice aligns disk orders with how the path is displayed in the operating system. vMotion can reorder the disks (disk1, disk2, disk3) but the UUIDs remain the same. When the migration is complete, use the noted UUID to map the disk information to re-create the disk naming order and the SCSI ID if necessary. This information can be useful for troubleshooting when an Oracle instance has many virtual disks that are mapped.
4. Remove the virtual disks from all cluster VMs except the one deemed primary.
5. Remove the multi writer-flag from the primary cluster VM (the only one that owns the cluster disks).