vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* MFA for users with an IBMid: Users authenticate by using an IBMid, password, and time-based one-time passcode (TOTP). This option applies to all users or just non-federated users.
* MFA for all users: This option applies to users who are using either an IBMid or an external identity provider (IdP). Users authenticate by using email-based MFA, TOTP MFA, or U2F MFA. The U2F MFA factor is based on the FIDO U2F standard, and it offers the highest level of security.



For more details, see [Enabling MFA for your account](https://cloud.ibm.com/docs/account?topic=account-enablemfa).







 October 2020 



 28 October 2020 

Enhanced Support Center
: The [Support Center](https://cloud.ibm.com/unifiedsupport/supportcenter) is now updated to help improve your experience with creating and managing your support cases. You can refine the scope of your cases by routing them to a specfic resource and provide feedback on your cases. You will also find popular FAQs that are featured based on your specific issue. For more details, see [Announcing the Release of Our New Support Center Enhancements](https://www.ibm.com/cloud/blog/announcements/new-support-center-enhancements).







 September 2020 



 18 September 2020 

Managing IBM Cloud Shell settings and other updates to IBM Cloud Shell
: Account owners or users with Cloud Shell administrator access can manage Cloud Shell settings from the IBM Cloud console. For more information, see [Updating Cloud Shell settings](https://cloud.ibm.com/docs/account?topic=account-shell-settings).

For a complete list of changes, see the [Cloud Shell release notes](https://cloud.ibm.com/docs/cloud-shell?topic=cloud-shell-release-notes-image).

Restricting account access by using IAM account settings
: For increased control over which users can access your account and work with API keys and service IDs, leverage the three new settings that are available on the Manage > Access (IAM) > Settings page in the console.
(https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-customize-from-catalog)[Onboard approved software and deployable architectures to private catalogs You can customize what products are available from the catalog for users in your enterprise to ensure that only approved architectures that adhere to your compliance standards are deployed.](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-onboard-custom)

 Video library 

[![carousel thumbnail](https://cloud.ibm.com/docs-content/v1/content/secure-enterprise//images/landing-Introducing-IBM-Cloud-enterprises.png)<br><br>Introducing IBM Cloud enterprises](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-what-is-enterprisewatch-and-learn)[![carousel thumbnail](https://cloud.ibm.com/docs-content/v1/content/secure-enterprise//images/landing-Getting-Access-Role-Overview.png)<br><br>IBM Cloud Console Guide: Getting Access - Role Overview](https://cloud.ibm.com/docs/account?topic=account-cloudaccesswatch-iamaccess)

 Learn more 

[IBM Developer<br><br>Visit IBM Developer for technical articles, code patterns, tutorials, and more.<br><br>![112-Developer-tools.svg](https://cloud.ibm.com/media/docs/images/homepage/112-Developer-tools.svg)](https://developer.ibm.com/depmodels/cloud/gettingstarted/)[Architecture Center<br><br>Discover the architecture references available for this product.<br><br>!
4 Minimal business impact: An inquiry or non-technical request. Within 1 business day Monday – Friday business hours 



Response Time Objective describes IBM's goals only and do not represent a guarantee of performance.

Business Hours reflect normal country business hours in your time zone. For example, 8:00 AM to 5:00 PM in North America or 9:00 AM to 6:00 PM in some parts of Asia and Europe, Monday through Friday, excluding weekends and national or statutory holidays.

For further details, please refer to the [IBM Support Guide](https://www.ibm.com/support/pages/node/733923)



 MAS-Dedicated Environment Route URLs 

MAS Application Suite Instance:

https://main.home.INSTANCE_NAME.suite.maximo.com/

Admin:

https://maxinst.manage.INSTANCE_NAME.suite.maximo.com/toolsapi

INSTANCE_NAME = Your environment instance identifier found in your Welcome Letter.

Once an environment has been provisioned, the URL can not be changed.





 Database Support and Access 

IBM Maximo Application Suite Dedicated supports DB2 as the database for the Suite. Clients who wish to directly access their data can with the following restrictions or procedures:



* Direct access to the production database is not allowed. If a client wishes to access production data, they must order a data replica and a read only user can be created against this replica. This replica is near real time so it will mirror the production data.
* SSL Connection can be done using JDBC or ODBC. IBM is not responsible for any tool a client selects to make this connection with and it will be the client responsibility to troubleshoot issues connecting their chosen tool to the database. Non-SSL connections are not allowed.



Please note, if a client has been granted write access to a database, and there are issues with data, the SRE team will only restore the database back to the last version. SRE personnel will not troubleshoot queries or data issues in these databases.

A support case must be submitted listing the names and emails of the users needing access. One ticket is required for each database.
: Auditing events for context-based restrictions are published under context-based restrictions IBM Cloud Activity Tracker events [Context-based restrictions rules events](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-events_context_basedrestriction_rules_events). Activity Tracker events related to CBR enforcement are unavailable on private endpoints.



 Configuring the network type 

You can configure Enterprise service instances to be available on the IBM Cloud private, public, or private and public networks. The following information describes how to select and update the required networking type. Public networking is selected by default.



 Prerequisites 

Ensure that you complete the following tasks:



* Create your service instance by using the Enterprise plan. For more information, see [Choosing your plan](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-plan_choose).
* Enable [Virtual Route Forwarding (VRF)](https://cloud.ibm.com/docs/direct-link?topic=direct-link-overview-of-virtual-routing-and-forwarding-vrf-on-ibm-cloud) for your IBM Cloud account.
* Enable service endpoints connectivity by running the following command:

ibmcloud account update --service-endpoint-enable true

To check whether prerequisites are completed, run the following command, and then check whether the following two properties are true:

ibmcloud account show

VRF Enabled: true
Service Endpoint Enabled: true







 Selecting a network configuration during provisioning 

You have a number of options for selecting the network configuration of your Enterprise cluster.



1. Use the IBM Cloud public network. Endpoints are accessible on the public internet. This is the default.
2. Use the IBM Cloud Private network. Endpoints are not visible on the public internet.
3. Use the IBM Cloud public and private network. Endpoints are visible on both the public internet and internally within the IBM Cloud.



You can make this selection at provision time through the Event Streams catalog provisioning page.
[Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) 
 External Service: Manage ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) 
 External Service: View ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) 
 General: Administrator Control ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) !
[Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 External Service: Manage ![Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 External Service: View ![Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 General: Administrator Control ![Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) 
 General: Administrator View ![Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/icons/checkmark-icon.svg) !
4 April 2021 



 New resources New data sources Enhancements 

 <br><br> * [ibm_iam_account_settings](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/iam_account_settings)<br> * [ibm_cm_catalog](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cm_catalog)<br> * [ibm_cm_offering](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cm_offering)<br> * [ibm_cm_offering_instance](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cm_offering_instance)<br> * [ibm_cm_version](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cm_version)<br> * [ibm_enterprise](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/enterprise)<br> * [ibm_enterprise_account](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/enterprise_account)<br> * [ibm_enterprise_account_group](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/enterprise_account_group)<br><br><br> <br><br> * [ibm_iam_account
If you have a single zone cluster, you can choose between the following options in Red Hat OpenShift on IBM Cloud that provide fast access to your data. For higher availability, use a storage option that is designed for geographically distributed data and, if possible for your requirements, create a multizone cluster.

The following image shows the options that you have in Red Hat OpenShift on IBM Cloud to permanently store your data in a single cluster.

Zoom

![Persistent storage options for single zone cluster](https://cloud.ibm.com/docs-content/v1/content/bce0f0917a9eea684d1b4b704ac6343a1f65f446/openshift/images/cs_storage_single_zone.svg)

Figure 2. Persistent storage options for single zone cluster



 Classic File Storage for Classic 

Classic infrastructure



Classic File Storage characteristics

 Characteristics Classic File Storage for Classic 

 Multizone-capable No, as specific to a data center. Data can't be shared across zones, unless you implement your own data replication. 
 Ideal data types All 
 Data usage pattern Random read-write operations, sequential read-write operations, or write-intensive workloads 
 Access Via file system on mounted volume 
 Supported Kubernetes access writes ReadWriteMany (RWX), ReadOnlyMany (ROX), ReadWriteOnce (RWO) 
 Performance Predictable due to assigned IOPS and size. IOPS are shared between the pods that access the volume. 
 Consistency Strong 
 Durability High 
 Resiliency Medium as specific to a data center. File storage server is clustered by IBM with redundant networking. 
 Availability Medium as specific to a data center. 
 Scalability Difficult to extend beyond the data center. You can't change an existing storage tier. 
 Encryption At rest 
 Backup and recovery Set up periodic snapshots, replicate snapshots, duplicate storage, back up data to IBM Cloud Object Storage, or copy data to and from pod and containers. 
 Common use cases Mass or single file storage or file sharing across a single zone cluster. 
 Non-ideal use cases Multizone clusters or geographically distributed data. 







 Classic Block Storage for Classic
Need to statically provision enough capacity to handle peak workload. 
 Persistent connections and state Limited. You cannot keep a persistent connection, except in cases of container caching. Generally, state must be kept in external resource. Same as column (1) Supported. You can keep an open socket or connection for long times and can store state in memory between calls. Supported. You can keep an open socket or connection for long times and can store state in memory between calls. Supported. You can keep an open socket or connection for long times and can store state in memory between calls. 
 Maintenance None. The entire stack is managed by IBM. Significant, depending on the target environment, User must provision hardware, networking, OS, storage, DB, install and maintain OpenWhisk, and so on. None. The entire stack is managed by vendor. Significant. User must create and maintain custom images, deploy and manage containers, connections between containers, and so on. Significant. User must allocate VMs, manage, and scale Java EE servers individually. 
 High Availability (HA) and Disaster Recovery (DR) Inherent or no extra costs Roll your own (RYO) Available at extra cost. Failed containers can be automatically restarted. Available at extra cost, semi-automatic. VMs can be automatically failed over. 
 Security Vendor provided Roll your own (RYO) Mix of RYO and vendor provided Mix of RYO and vendor provided Roll your own (RYO) 
 Developer velocity Highest Highest Highest Average Slow 
 Resource utilization (idle resources that still need to be paid for) Resources are never idle as they are invoked only upon request. When workload is absent, no cost or resource allocation occurs. Because this option is using IaaS or CaaS - similar considerations apply as in columns (4) and (5). Some resources can be idle, and autoscaling helps to eliminate idle resources. A number of running instances must always be present, and are likely to be used at less than 50% of their capacity. Stopped instances do not cost anything. Similar to column (3) Some resources can be idle, but autoscaling is not supported.
SAP HANA with Intel Optane Persistent Memory (PMEM) 

SAP HANA now has a non-volatile in-memory option on Bare Metal servers. Intel Optane™ persistent memory (PMEM) retains its contents like traditional storage options but with speeds similar to main memory.

![Figure 1. SAP HANA Intel Optane PMem](https://cloud.ibm.com/docs-content/v1/content/f89cc64b006ca59b35404693959c83d5747fee3e/sap/images/sap-partners-intel-optane-pmem.svg){: caption="Figure 1. SAP HANA Intel Optane PMem

[1]overview" caption-side="bottom"}

Many systems with large data storage and retrieval needs use DRAM for fast data retrieval. DRAM is costly and data does not persist when the server is rebooted or shutdown. On startup, data must be reloaded from storage.

With Intel Optane PMEM, data is retained in memory during system restarts and power outages, providing faster start times. PMEM provides near-DRAM performance and is also byte-addressable.

Intel Optane PMEM modules are installed with DRAM in the same dual in-line memory module (DIMM) slot. PMEM modules do not function without any DRAM DIMMS installed. The current configurations supports DRAM to PMEM ratios of 1:1, 1:2, and 1:4.

SAP HANA uses App Direct mode, in which the application stores data on the persistent memory. HANA2 SP04 release or higher was co-engineered by SAP and Intel to use the unique dual memory and storage capability of the PMem modules.

In App Direct mode, the applications directly access the memory and control the direct load and store of the PMem and DRAM DIMMs memory resources. In this mode, the PMem acts as byte-addressed persistent memory that is mapped to the system physical address space. App Dir mode uses regions, which are groups of one or more PMem modules that appear to be a single logical virtual address space. Regions are partitioned into one or more namespaces, similar to hard disk partitions.
Block storage is mounted with an RWO access mode. This access allows only one pod to be mounted to the block storage at a time. To back up your data, you must unmount the app pod from the storage, mount it to your backup pod, back up the data, and remount the storage to your app pod.

To make your data even more highly available and protect your app from a zone failure, set up a second Object Storage instance and replicate data across zones. If you need to restore data from your Object Storage instance, use the restore pod that is provided with the Helm chart.





 Copying data to and from pods and containers 

You can use the kubectl cp[command](https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commandscp) to copy files and directories to and from pods or specific containers in your cluster.

[Log in to your account. If applicable, target the appropriate resource group. Set the context for your cluster.](https://cloud.ibm.com/docs/containers?topic=containers-access_cluster)

When you run the kubectl cp command, if you don't specify a container with -c, the command uses the first available container in the pod.

Copy data from your local machine to a pod in your cluster.

kubectl cp <local_filepath>/<filename> <namespace>/<pod>:<pod_filepath>

Copy data from a pod in your cluster to your local machine.

kubectl cp <namespace>/<pod>:<pod_filepath>/<filename> <local_filepath>/<filename>

Copy data from your local machine to a specific container that runs in a pod in your cluster.

kubectl cp <local_filepath>/<filename> <namespace>/<pod>:<pod_filepath> -c <container>







 Storage class reference 

Storage classes that have retain in the title have a reclaim policy of Retain. Example: ibmc-file-retain-bronze. Storage classes that don't have retain in the title have a reclaim policy of Delete.
Backups that are a part of an inactive backup chain are immediately moved to Cloud Object Storage. The restore speed for these inactive backups might be impacted.

You can change how fast the inactive backup chains are moved to Cloud Object Storage by opening an IBM Cloud for VMware Solutions service ticket.





 Related links 



* [VMware Shared overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_overview)
* [Requirements and planning for VMware Shared](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_planning)
* [Ordering virtual data centers](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_ordering)
* [Viewing and managing virtual data centers](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_viewing-vdc-summary)
* [Resizing virtual data centers](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_resize)
* [Operating VMware Shared](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_vcd-ops-guide)
* [Managing Veeam for VMware Shared](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_veeam)
* [Managing Zerto for VMware Shared](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_zerto-portal)
If more than one user created instances, then ask the other users who created instances to log in and check the number they created. You can then add up the total sum of instances for your deployment. Note that not even an administrative user can see instances that were created by others from the web client user interface.







 Backing up data by using the CronJob 

A CronJob named $INSTANCE-store-cronjob is created and enabled for you automatically when you deploy the service. A CronJob is a type of Kubernetes controller. A CronJob creates Jobs on a repeating schedule. For more information, see [CronJob](https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/) in the Kubernetes documentation.

The jobs that are created by the store cron job are called $INSTANCE-backup-job-$TIMESTAMP. Each job deletes old logs and runs a backup of the store Postgres database. Postgres provides a tool that is called pg_dump. The dump tool creates a backup by sending the database contents to stdout where you can write it to a file. The backups are created with the pg_dump command and stored in a persistent volume claim (PVC) named $INSTANCE-store-pvc.

You are responsible for moving the backup to a more secure location after its initial creation, preferrably a location that can be accessed outside of the cluster where the backups cannot be deleted easily. Ensure this happens for all environments, especially for Production clusters.

The following table lists the configuration values that control the backup cron job. You can change the default values for these settings by adding them to the install-override.yaml file and changing their default values when you deploy the service. Or you can edit these settings by editing the cron job after the service is deployed by using the oc edit cronjob $INSTANCE-store-cronjob command.



Cron job variables

 Variable Description Default value 

 store.backup.suspend If True, the cron job does not create any backup jobs. False
* Global benchmarking standards
* Cyber-risk reporting







 Compliance risk 



* Automated compliance monitoring
* Compliance risk score dashboard
* Automated IA controls assessment
* It supports the following global configuration benchmarking standards: PCI, FISMA, FEDRAMP, HIPAA, GLBA, GDPR, NERC CIP Reports Against SCAP, OVAL, and XCCDF.
* Continuously updated and mapped IA controls and standards libraries







 Forensic management 



* Log management
* Log collection from multiple sources
* Event detection, analytics, and visualization
* Graphical visualization of results
* Data aggregation from multiple sources
* Event-based analytics
* Full drill-down capability for events and log-based analysis
* Alerts and notifications







 Related links 



* [Caveonix website](https://www.caveonix.com)