vania-janet/multiturn-rag-retrieval-data huggingface dataset:
What can I evaluate? 

With IBM Cloud® Security and Compliance Center, you can evaluate the resources that run on IBM Cloud and other cloud providers for compliance. The environments that can be evaluated differ depending on how the configuration information is obtained.



 Environments that can be evaluated 

With Security and Compliance Center you can evaluate IBM Cloud.





 IBM Cloud components that can be evaluated 

You can evaluate your organization’s current security and compliance posture by validating the configuration of your resources in the following components.



* [Activity Tracker](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-getting-started)*
* [App ID](https://cloud.ibm.com/docs/appid?topic=appid-getting-started)*
* Bare Metal Servers
* [Cloudant](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-getting-started-with-cloudant)*
* [Cloud Databases](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-about)*



* Elasticsearch
* etcd
* MongoDB
* PostgreSQL
* Redis



* [Cloud Internet Services (CIS)](https://cloud.ibm.com/docs/cis?topic=cis-getting-started)
* Cloud Monitoring*
* [IBM Cloud Platform](https://cloud.ibm.com/docs/overview?topic=overview-whatis-platform)



* Billing
* Catalog Management
* IAM Access Groups
* IAM Identity Service



* [Cloud Shell](https://cloud.ibm.com/docs/cloud-shell?topic=cloud-shell-getting-started)*
* [Cloud Object Storage](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-getting-started-cloud-object-storage)*
* [Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-getting-started)*
Getting started with Content Delivery Network (CDN) 

You can use IBM Cloud® Content Delivery Network (CDN) for various industry solutions, including media, entertainment, software, gaming, banking, and e-commerce, to meet the needs of your businesses. IBM Cloud has partnered with Akamai to offer the most comprehensive Content Delivery Network features, while maintaining affordability. This partnership features Edge servers in over [50 countries](https://cloud.ibm.com/docs/CDN?topic=CDN-list-of-edge-serverslist-of-edge-servers) to bring the content closest to where you need it most--your users.



  Before you begin 

Before you begin using IBM Cloud Content Delivery Network, you'll first need an [IBMid](https://www.ibm.com/account/us-en/signup/register.html). You can then order your Content Delivery Network service through the [IBM Cloud CDN console](https://cloud.ibm.com/catalog/infrastructure/cdn-powered-by-akamai).

If you need assistance in obtaining an account to use IBM Cloud Content Delivery Network, you can [contact your IBM sales representative](https://www.ibm.com/cloud/contact-us/) for additional guidance on getting started.





  Next step 

[Order your CDN](https://cloud.ibm.com/docs/CDN?topic=CDN-order-a-cdn).
VMware Solutions infrastructure domain 

The IBM Cloud® for VMware Solutions infrastructure domain holds the resource objects and user accounts for the administration of the VMware vCenter Server® instance only. Using this domain to hold resource objects and user accounts for your workload VMs is not recommended.

Within the vCenter Server design, the IBM Cloud for VMware Solutions infrastructure Active Directory™ (AD) domain is used for:



* DNS - The appliances provisioned as part of the services have DNS entries in the AD. These entries enable the functions of the vCenter Server instance to use FQDN and do name lookups.
* Authentication services - An AD security group is added, and a number of accounts are added to enable the automation.



In IBM Cloud for VMware Solutions, every primary instance deploys a forest root domain and configures the site topology. The IBM Cloud for VMware Solutions AD/DNS is always going to be its own forest and domain, you cannot remove this forest or domain because it might break the IBM Cloud for VMware Solutions automation. You can't migrate the users and resources to one of your existing domains or create a new domain, as you can't create the credentials for the IBM user named automation.

During the ordering process of a vCenter Server instance, the hostname prefix and the domain name are collected from the user that is pertinent to the Active Directory Domain Services (AD DS) and DNS configuration.

These values are then used to generate the username and server names of the instance. For more information, see [Ordering vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_orderinginstance-req).



 Domain controllers 

All AD domain controllers that are used in the IBM Cloud® for VMware Solutions infrastructure domain are exclusively yours and nothing is shared with other customers. You must provide operational management to monitor, update, back up, and recover these domain controllers.

These domain controllers are authoritative for the domain name that you selected for your instance. Ensure that you select a domain name that is unique within your domain space so that the DNS responsibility can be delegated completely to these controllers.
[IBM Cloud® Object Storage](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-getting-started-cloud-object-storage) You can use IBM Cloud Object Storage to store unstructured data in the IBM Cloud. [Platform metrics](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-mm-cos-integration&programming_language=Console) 







 VMware as a Service 

The following table lists Cloud services that are enabled for IBM Cloud Monitoring:



Table 12. VMware as a Service

 Service Description Metrics 

 [VMware as a Service](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-single-tenant-monitoring) Deploys a comprehensive portfolio of automated and on-demand services for VMware workloads to the cloud. [Platform metrics](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-single-tenant-monitoringsingle-tenant-monitoring-metrics) 







 VMware Shared 

The following table lists Cloud services that are enabled for IBM Cloud Monitoring:



Table 13. VMware Shared

 Service Description Metrics 

 [VMware Shared](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared-monitor) Provides standardized and customizable deployment choices of VMware® virtual data center environments. [Platform metrics](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared-monitorshared-monitor-metrics) 







 VPC 

With IBM Cloud® Virtual Private Cloud (VPC), you can provision a VPC in the IBM Cloud to run an isolated environment within the public cloud. VPC gives you the security of a private cloud, with the agility and ease of a public cloud. The VPC infrastructure contains a number of Infrastructure-as-a-Service (IaaS) offerings, including Virtual Servers for VPC.
Get started 

IBM Cloud® for SAP is the continuation of a 50+ year IBM-SAP alliance across hardware, software, and services.

With over 60 IBM data centers worldwide, the IBM Cloud® SAP-Certified Infrastructure gives you the flexibility to run your SAP workloads in the IBM Cloud when and where you need them. You can quickly address issues such as:



* Rapidly expanding or contracting capacity
* Moving SAP workloads to the cloud
* Supplementing an existing private cloud architecture.



The following documentation provides design considerations and guidance for provisioning the infrastructure to support SAP workloads, including:



* SAP Business Applications such as SAP S/4HANA or SAP BW/4HANA
* SAP Technical Applications such SAP HANA database server and SAP NetWeaver application server



You can use this information to help planning your SAP installation and running your SAP workloads on IBM Cloud.

The following documentation does not replace any SAP implementation-related documentation.



 Before you begin 

Before you can install SAP software components on IBM Cloud, you need an:



* SAP S-User ID to review relevant SAP documentation and download SAP installation media
* IBM ID to create an IBM Cloud account



This information is covered in the Pre-Requisites for SAP Workloads topic group, under [Necessary account credentials for SAP and IBM Cloud](https://cloud.ibm.com/docs/sap?topic=sap-necessary-credentials).





 Summary of an SAP landscape installation onto Cloud IaaS 

This table summarizes the SAP landscape installation steps for you and your team:



Table 1. Overview of your SAP landscape installation steps

 Task Details 

 Read the [Overview of IBM Cloud® for SAP](https://cloud.ibm.com/docs/sap?topic=sap-overview) Identify the various offerings that are available for your SAP landscape. Provides a high-level comparison of your options.
* [Set up VMware Update Manager (VUM)](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vum-intro) through a Public Gateway to obtain VMware updates.
* If applicable, set up vSAN through a proxy to maintain the vSAN Hardware Compatibility List (HCL) database.
* Plan regular maintenance for VMware components that are not supported by VUM. For example, VMware vCenter, PSC, and NSX.
* Review vSphere Enhanced vMotion Compatibility (EVC) configuration. Your cluster might not be configured with EVC enabled if the current version of vSphere does not support EVC for your hardware level.







 Monitoring 

Ensure to plan for and implement the following solutions for monitoring your instance and instance components:



* A logging server that includes log forwarding or collection for all instance components and adequate log retention. The [VMware Aria Operations and VMware Aria Operations for Logs](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vrops_overview) offering can help you with log management and visibility.
* An alert infrastructure, including configuration of the SMTP server and short message service (SMS) gateway, as needed.
* Proactive monitoring of hosts, drives, management software, and network, including vSAN monitoring if applicable. The [VMware Aria Operations on IBM Cloud](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vrops_overview) offering can help you operate and monitor the performance, health, and capacity of your VMware environment.
* Monitoring your backup infrastructure and backup jobs.
* vSphere Distributed Switch Health Check is enabled by default. It can generate a significant number of MAC addresses for testing team policy, MTU size, and VLAN configuration, which results in extra network traffic. Disable this health check and re-enable only as needed for network troubleshooting.
This capability is supported by the beta release of IBM Cloud Partner Center and our previously general availability release of private catalog capabilities. For more information, see [Onboarding a virtual server image with Terraform](https://cloud.ibm.com/docs/third-party?topic=third-party-vsimage-register).







 April 2021 



 21 April 2021 

Delivering notifications by using webhooks
: You can now easily add webhooks to the notification distribution list in addition to adding email addresses. You can register a webhook with your account on the [Notification distribution list page](https://cloud.ibm.com/account/notifications-distribution-list) to receive all account notifications. Administrators can use webhooks to configure an application to receive asynchronous notifications whenever an event occurs on the IBM Cloud platform. Any registered webhook must support HTTP POST requests and accept the notification as a JSON.

For more information, see [Adding webhooks to a distribution list](https://cloud.ibm.com/docs/account?topic=account-adding-webhooks-to-a-distribution-list).





 19 April 2021 

Upcoming changes to the user invitation flow
: Starting June 01 2021, to enhance security and user protection, all users will be required to accept an invitation to become an active user within a new account. The new invitation flow will have an impact only on inviting existing IBM Cloud® users. Existing users are currently being automatically onboarded to each new account as they are invited. After this change, these users will need to accept an invitation in their notifications, by email, or by using the CLI to onboard to a new account.

Concerned about how this change will impact your automation? To avoid any disruption to on-going workflows, you need to check your scripts:



* To accept invitations in the CLI, existing members of IBM Cloud® must use the [ibmcloud login](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_cliaccept-invitation-to-join-a-new-account-) command.
Check out [Troubleshooting Ingress](https://cloud.ibm.com/docs/containers?topic=containers-ingress-debug) and [Troubleshooting load balancers](https://cloud.ibm.com/docs/containers?topic=containers-cs_loadbalancer_fails).





 Add app storage 



1. Storage basics: Start by understanding the [basics of Kubernetes storage](https://cloud.ibm.com/docs/containers?topic=containers-kube_concepts).
2. Requirements: Determine your [requirements for a storage solution](https://cloud.ibm.com/docs/containers?topic=containers-storage-plan).
3. Choose a solution: Using your storage requirements, choose a storage solution by comparing [your options](https://cloud.ibm.com/docs/containers?topic=containers-storage-plan).



Need help? Check out the troubleshooting page for your persistent storage solution.





 Add integrations 

Enhance app capabilities by integrating various external services and catalog services in your cluster with your app.



1. Review supported integrations:



* [All supported integrations](https://cloud.ibm.com/docs/containers?topic=containers-supported_integrationssupported_integrations)
* [IBM Cloud Kubernetes Service partners](https://cloud.ibm.com/docs/containers?topic=containers-service-partners)
* [IBM Cloud services and third-party integrations](https://cloud.ibm.com/docs/containers?topic=containers-ibm-3rd-party-integrations)



2. Add services to your cluster: Ask your cluster administrator to [add the integration to your cluster](https://cloud.ibm.com/docs/containers?topic=containers-learning-path-adminadmin_integrate).
3. Access services from your app: Ensure that your app can access the service.
[MQ on Cloud](https://cloud.ibm.com/docs/mqcloud?topic=mqcloud-mqoc_getting_started) MQ on IBM Cloud enables you to quickly and easily deploy queue managers in the cloud and connect your applications to them, for reliable data transfer between different parts of your enterprise application landscape. [More info](https://cloud.ibm.com/docs/mqcloud?topic=mqcloud-logdna_logs) 



To see the list of IBM Log Analysis locations where these services send logs, see [Integration services](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-cloud_services_locationscs_locations_integration).





 VPC services 

The following table lists Cloud services that send logs to IBM Log Analysis:



Table 7. List of IBM Cloud VPC services

 Service Description More info Message IDs 

 [Dedicated host](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-dedicated-hosts-instances) You can create a dedicated host to carve out a single-tenant compute node, free from users outside of your organization. [More info](https://cloud.ibm.com/docs/vpc?topic=vpc-logging) [Message IDs](https://cloud.ibm.com/docs/vpc?topic=vpc-loggingdedicated-host) 
 [Flow Log Collector](https://cloud.ibm.com/docs/vpc?topic=vpc-flow-logs) This service is used to collect and store information regarding the Internet Protocol (IP) traffic going to and from network interfaces within your Virtual Private Cloud (VPC) [Viewing flow log objects](https://cloud.ibm.com/docs/vpc?topic=vpc-fl-analyze) [Message IDs](https://cloud.ibm.com/docs/vpc?topic=vpc-logginglogging-flow-log-collector_msgs)
Using IBM Cloud Object Storage File Access 

IBM Cloud Object Storage File Access is a software-defined solution providing an SMB and NFS protocol interface for applications to store and retrieve infrequently used files on IBM Cloud Object Storage. This solution is an excellent choice for archiving, retention, and active archiving use cases as it also provides a built-in capability to discover and migrate files form existing file systems to IBM Cloud Object Storage.

IT administrators can use Cloud Object Storage File Access to discover and migrate cold and infrequently used files from multiple enterprise NAS, Windows, or Linux file servers to Cloud Object Storage. This enables administrators to free up storage space on their filer systems or completely eliminate file infrastructure that is used solely for infrequently used file data, such as backup and active archiving workloads and file repositories.

Multiple enterprise applications can access one or more unified file systems on Cloud Object Storage through SMB and NFS protocol interfaces provided by Cloud Object Storage File Access without any rewrite. It is a highly secure and available solution that is easy to install, use, and manage. It can be integrated with Active Directory to provide authentication and access control to file data stored on Cloud Object Storage.

IBM Cloud Object Storage File Access runs as a pair of active-passive gateway virtual appliances (VMware, Hyper-V, or KVM). Configuration and maintenance operations are performed using a browser pointing to a portal that also runs in another pair of active-active virtual appliances (VMware, Hyper-V, or KVM).



 Requirements 



 Hardware requirements 

Recommended minimum server hardware configuration for the VMware ESXi, Microsoft Hyper-V, or Red Hat® Enterprise Linux hypervisor that will run the IBM Cloud Object Storage File Access Gateway VM:



* CPU x64 (4+ cores)
* RAM 8 GB
* Cache disk Up to 8 TB, SSD or NVMe preferred (2 TB minimum)
* Network 10 Gigabit
* Network switch (At least 2 for redundancy)



Recommended minimum server hardware configuration for the VMware ESXi or Red Hat Enterprise Linux hypervisor that will run the IBM Cloud Object Storage File Access Portal VM:



* CPU x64 (12+ cores)
* RAM 40+ GB
For more information about R1Soft and IBM Cloud, see [R1Soft Server Backup Manager](https://www.ibm.com/cloud/backup-and-restore?mhq=R1Soft%20Server%20Backup%20Manager&mhsrc=ibmsearch_a). Veeam Backup and Replication combines automated backup along with restore and replication capabilities. Veeam also provides advanced monitoring, reporting, and capacity planning. For more information about Veeam Backup and Replication, see [Veeam overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-veeam_considerations). VMware vCenter automates deployment of the underlying VMware vSphere and VMware vCenter Server layers that you need for a flexible and customizable VMware solution. For more information about vCenter on IBM Cloud, see [About vCenter Server on IBM Cloud](https://www.ibm.com/download/cas/L7RKPZND?mhq=vmware%20vcentermhsrc=ibmsearch_a). 
 Control panel software If you select monthly billing, you can add a control panel for web hosting. 
 Database software You can select a database software to install. IBM Cloud supports any database software that is deployed during the provisioning process. You can also install your own database software after the server is deployed. 
 Services Some services are automatically selected for you, depending on your billing and image selections. You can choose from any of the remaining service add-ons for your instance. 
 Provision script Provisioning scripts are commonly used to apply a customer-specific configuration to a server and to aid in automation of your scaling strategy. Provisioning scripts can be any file that the operating system (OS) can run, including combined binary files or any OS-supported language. Provisioning scripts can't be used on cloud-init images. For more information, see [Provisioning scripts](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-provisioning-scripts).
IBM Cloud services and third-party integrations 

You can use IBM Cloud® platform and infrastructure services, and other third-party integrations to add extra capabilities to your cluster.



 IBM Cloud services 

Review the following information to see how IBM Cloud platform and infrastructure services are integrated with Red Hat OpenShift on IBM Cloud and how you can use them in your cluster.



 IBM Cloud platform services 

All IBM Cloud platform services that support service keys can be integrated by using Red Hat OpenShift on IBM Cloud [service binding](https://cloud.ibm.com/docs/openshift?topic=openshift-service-binding).

Service binding is a quick way to create service credentials for an IBM Cloud service and store these credentials in a Kubernetes secret in your cluster. The Kubernetes secret is automatically encrypted in etcd to protect your data. Your apps can use the credentials in the secret to access your IBM Cloud service instance.

Services that don't support service keys usually provide an API that you can directly use in your app.





 IBM Cloud classic infrastructure services 

Because Red Hat OpenShift on IBM Cloud lets you create a cluster on IBM Cloud classic infrastructure, some classic infrastructure services, such as Virtual Servers, Bare Metal Servers, or VLANs are fully integrated into Red Hat OpenShift on IBM Cloud. You create and work with these service instances by using the Red Hat OpenShift on IBM Cloud API, CLI, or console.

Supported persistent storage solutions, such as IBM Cloud File Storage for Classic, IBM Cloud Block Storage, or IBM Cloud® Object Storage are integrated as Kubernetes flex drivers and can be set up by using [Helm charts](https://cloud.ibm.com/docs/openshift?topic=openshift-helm). The Helm chart automatically sets up Kubernetes storage classes, the storage provider, and the storage driver in your cluster. You can use the storage classes to provision persistent storage by using persistent volume claims (PVCs). For more information, see [Planning highly available persistent storage](https://cloud.ibm.com/docs/openshift?topic=openshift-storage-plan).
With Red Hat OpenShift 4.4, you get access to Kubernetes version 1.17 APIs that enable features such as [key management service (KMS)](https://cloud.ibm.com/docs/openshift?topic=openshift-encryptionkeyprotect) integration. For more information, see the [IBM Cloud blog](https://www.ibm.com/cloud/blog/announcements/openshift-version-44-now-available-in-red-hat-openshift-on-ibm-cloud).





 20 July 2020 

Master versions
: Master fix pack update change log documentation is available.
: Red Hat OpenShift [4.3.28_1532_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4328_1532) and [3.11.232_1559_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311232_1559).

Worker node versions
: Worker node fix pack update change log documentation is available.
: Red Hat OpenShift [4.3.29_1532_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4329_1532) and [3.11.232_1558_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311232_1558).





 16 July 2020 

Ingress ALB change log
: Updated the [nginx-ingress image build to 645 and the ingress-auth image build to 420](https://cloud.ibm.com/docs/containers?topic=containers-cluster-add-ons-changelogkube_ingress_changelog).

Pod and service subnets