vania-janet/multiturn-rag-retrieval-data huggingface dataset:
s390x

s390x with secure execution



Table 3. Compute profiles options for s390x instances
Compute profiles options for IBM Z or LinuxONE s390x virtual server instances.

 Instance profile vCPU Cores GiB RAM Bandwidth Cap (Gbps) 

 cz2-2x4 2 1 4 2 
 cz2-4x8 4 2 8 8 
 cz2-8x16 8 4 16 16 
 cz2-16x32 16 8 32 32 







 Memory 

Memory profiles are best for memory intensive workloads, such as large caching workloads, intensive database applications, or in-memory analytics workloads with 8 GiB of memory for every 1 vCPU of compute. The following table shows all Memory profiles available for the IBM Z or LinuxONE (s390x architecture) processors.

Ensure that you select a secure execution enabled profile (for example, mz2e-2x16) when you enable the Run your workload with an OS and a profile protected by Secure Execution toggle (to activate support for secure execution image). Selecting any profile that is not secure execution enabled will cause the deployment of the virtual instance to fail.

s390x

s390x with secure execution



Table 4. Memory profiles options for s390x instances
Memory profiles options for IBM Z or LinuxONE s390x virtual server instances.

 Instance profile vCPU Cores GiB RAM Bandwidth Cap (Gbps) I 

 mz2-2x16 2 1 16 4 
 mz2-4x32 4 2 32 8 
 mz2-8x64 8 4 64 16 
 mz2-16x128 16 8 128 32 







 How the bandwidth is allocated using the UI 

Instance bandwidth is allocated between volume bandwidth and networking bandwidth. The bandwidth capacity (Bandwidth Cap) is determined by the virtual server profile that you select during instance provisioning. For example, a bx2-2x8 balanced server profile allows a bandwidth cap of 4 Gbps. The initial volume and network bandwidth allocation depends on the bandwidth set by the instance profile you selected. You can also see the bandwidth allocations in the profile information during instance creation in the UI.
For example, you can upgrade a stand-alone VPN server (one subnet) to a High Availability (HA) VPN server (two subnets in different zones). You can also detach a subnet to downgrade an HA VPN server to a stand-alone deployment, or change an attached subnet after your VPN server is provisioned. For more information, see [Upgrading to an HA VPN server](https://cloud.ibm.com/docs/vpc?topic=vpc-vpn-client-to-site-change-server-types).





 16 November 2021 

New Very High Memory and Ultra High Memory instance profile family for dedicated host (LA)
: Very High Memory with instance storage and Ultra High Memory with instance storage profiles are now available for dedicated host.
: Very High Memory profiles offer a core to RAM ratio of 1 vCPU to 14 GiB of RAM. This family is hosted exclusively on the latest generation Intel® Xeon® Platinum Cascade Lake server hosts and is best for OLAP workloads and SAP-related services, such as SAP NetWeaver. Very High Memory profiles are available in the US South (Dallas), US East (Washington DC), Canada (Toronto), United Kingdom (London), EU Germany (Frankfurt), Japan (Tokyo), Japan (Osaka), and Australia (Sydney) regions. For more information, see [Very High Memory with instance storage profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-dh-profilesvhm-is-dh-pr).
: Ultra High Memory profiles offer a core to RAM ratio of 1 vCPU to 28 GiB of RAM. This family is hosted exclusively on the latest generation Intel® Xeon® Platinum Cascade Lake server hosts and is optimized for running memory intensive applications and in-memory database such as SAP HANA, Memcached, or Redis. Ultra High Memory profiles are available in the US South (Dallas) and EU Germany (Frankfurt) regions. For more information, see [Ultra HIgh Memory with instance storage profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-dh-profilesuhm-is-dh-pr).





 12 November 2021
The spread option should result in a mostly even distribution of virtual server instances on the hosts, while the pack option could result in one dedicated host being mostly empty.

See the following example set of specified variables to enable dedicated hosts:

cluster_prefix = lsf-demo
worker_node_min_count = 10
worker_node_instance_type = cx2-32x64
dedicated_host_enabled = true
dedicated_host_placement = spread

Zoom

![Dedicated host](https://cloud.ibm.com/docs-content/v1/content/74a831a53989757bd05bd0dea7bb42c9ede61d0f/ibm-spectrum-lsf/images/dedicated-host-vpc.png)

Figure 1. Dedicated hosts for VPC example

With these example variables, ten cx2-32x64 instances are provisioned as static compute nodes on three dedicated hosts using the cx2-host-152x304 profile. The dedicated host profile is automatically selected. You can see provisioned dedicated hosts with the IBM Cloud CLI or the IBM Cloud console.

The spread placement policy tries to evenly distribute worker nodes and so lsf-demo-dh-0 consumed 128 vCPUs (32 * 4 virtual server instances) and lsf-demo-dh-1 and lsf-demo-dh2 each consumed 96 vCPUs (32 * 3 virtual server instances). If you use the pack placement, it allocates four virtual server instances on two dedicated hosts and two virtual server instances on the third dedicated host.
audit-log.vsi.reload An event is generated when an initiator performs an operating system (OS) reload for an instance. 
 audit-log.vsi.boot An event is generated when an initiator boots an instance from an image. 
 audit-log.vsi.reclaim An event is generated when an initiator cancels an instance. 
 audit-log.vsi.pause An event is generated when an initiator pauses an instance. 







 Viewing events 

The Activity Tracker events are available in the Activity Tracker account domain that is available in the IBM Cloud region where the events are generated. For more information, see [Viewing account events](https://cloud.ibm.com/docs/Activity-Tracker-with-LogDNA?topic=Activity-Tracker-with-LogDNA-manage_events).

Activity Tracker events are automatically forwarded to the Activity Tracker service in the same region where the action happens.
For more information about the available block and file storage classes you use with each of the supported storage solutions, see the table of Storage requirements under Information you need to complete this task on the page "Installing Watson Speech services" in [Watson Speech services on IBM Cloud Pak for Data](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=services-watson-speech).

Additional information about provisioning a service instance
: The documentation now includes information about creating a service instance programmatically. It also includes examples of listing service instances and deleting a service instance. For more information, see Creating a Watson Speech services instance in the Post-installation setup documentation in [Watson Speech services on IBM Cloud Pak for Data](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=services-watson-speech).

Server-side encryption is enabled for the MinIO datastore
: The Speech services have now enabled server-side encryption for object storage in the MinIO datastore. No action is required on your part.

Change to audit webhooks
: The Speech services have now removed the audit webhook dependency. The services now write audit events directly to the server. After upgrading to version 4.6.2, some webhook resources might remain until all services can remove the dependency. The remaining resources will be removed in a future release. No action is required on your part.

New Netherlands Dutch next-generation multimedia model
: The service now offers a next-generation multimedia model for Netherlands Dutch: nl-NL_Multimedia. The new model supports low latency and is generally available. It also supports language model customization and grammars. For more information about next-generation models and low latency, see



* [Next-generation languages and models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-models-ng)
* VMware Aria Operations for Logs instance in the other instances as a result of event forwarding (MZR configuration)



For more information, see [VMware Aria Operations for Logs design](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-opsmgmt-vrli).





 Backup server 

This server is a Linux® VM that is manually deployed to provide a location for file-based backups. It is used by the vCenter Server Appliance to perform a file-based backup of the vCenter Server core configuration, inventory, and historical data. Similarly, NSX controller backups are done to this server.





 Caveonix server 

The Caveonix RiskForesight service manages cyberrisk and compliance risk with proactive monitoring and automated defense controls to protect against threats and to meet industry or government regulations.







 Gateway cluster 

No vSphere management components are deployed to the gateway cluster. The tooling in the management cluster is used to manage the gateway cluster ESXi hosts.





 Workload cluster 

THe NSX-T gateway cluster VMs that house the Tier-0 and Tier-1 routers are on the workload clusters. No vSphere management components are deployed to the workload cluster. The tooling in the management cluster is used to manage the workload cluster ESXi hosts.





 Related links 



* [IBM Cloud compliance programs](https://www.ibm.com/cloud/compliance)
* SUSE Linux Enterprise Server is now supported as an operating system stock image when you provision an x86-64 virtual server. For more information, see [x86-64 virtual server images](https://cloud.ibm.com/docs/vpc?topic=vpc-about-images).









 August 2022 



 31 August 2022 

Configuration governance
: New VPC config rules for the Image service and Virtual Servers are now available with the Security and Compliance Center. For more information, see [Governing VPC Resource configuration](https://cloud.ibm.com/docs/vpc?topic=vpc-manage-security-compliancegovern-vpc) in [Managing security and compliance with VPC Infrastructure Services](https://cloud.ibm.com/docs/vpc?topic=vpc-manage-security-compliance).





 30 August 2022 

IBM Cloud Hyper Protect Virtual Server for IBM Cloud® Virtual Private Cloud
: You can now create IBM Cloud Hyper Protect Virtual Server for IBM Cloud VPC instances on LinuxONE (s390x processor architecture) in United Kingdom (London) region, in additional to Brazil (São Paulo), Canada (Toronto), Japan (Tokyo), and US East (Washington DC) regions. To create IBM Cloud Hyper Protect Virtual Server for IBM Cloud VPC instances on LinuxONE (s390x processor architecture), see [Creating virtual server instances](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers), and [IBM Hyper Protect Container Runtime image](https://cloud.ibm.com/docs/vpc?topic=vpc-vsabout-imageshyper-protect-runtime). A valid contract is required for creating an instance. For more information, see [About the contract](https://cloud.ibm.com/docs/vpc?topic=vpc-about-contract_se&interface=ui).





 23 August 2022 

Additional user tag support for boot and data volumes
: You can now add user tags to boot and data volumes when provisioning a virtual server instance or creating an instance template.
Using dedicated hosts 

Dedicated hosts enable you to deploy your virtual server instances on single-tenant compute hosts. Workloads under dedicated hosts can avoid noisy neighbor issues (for example, performance interference due to other users' workloads) that they might encounter on public virtual server instances. When you use a dedicated host, you are billed by the usage of the host, not vCPUs or RAM associated with your virtual instances.

This offering can deploy static compute nodes on dedicated hosts. The number of dedicated hosts and the profile names for dedicated hosts are calculated from worker_node_min_count and worker_node_instance_type.

Spectrum LSF still dynamically provisions compute nodes as public instances, and dedicated hosts are used only for static compute nodes that are provisioned at the time that the cluster is created.



 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 dedicated hosts 

When you [create your workspace](https://cloud.ibm.com/docs/ibm-spectrum-lsf?topic=ibm-spectrum-lsf-creating-workspace), you need to set two variables for dedicated hosts. Set dedicated_host_enabled to be 'true' and dedicated_host_placement to be spread or pack (spread is the default).

The variable dedicated_host_placement specifies the placement policy for static workers. The pack option deploys instances on one dedicated host until it's full before moving on to the next dedicated host. The spread option deploys instances in round-robin fashion across all of the dedicated hosts. The spread option should result in a mostly even distribution of virtual server instances on the hosts, while the pack option could result in one dedicated host being mostly empty.

See the following example set of specified variables to enable dedicated hosts:

cluster_prefix = lsf-demo
worker_node_min_count = 10
worker_node_instance_type = cx2-32x64
dedicated_host_enabled = true
dedicated_host_placement = spread

Zoom

!
<br><br> * Allow customer to choose operating system from two most widely used commercial Linux operating system offerings<br> * Support new OS releases<br><br><br> Linux operating system Red Hat Enterprise Linux (RHEL) SUSE Linux Enterprise Server(SLES) 
 <br><br> * Create a virtual server instance that can act as an internet proxy server<br><br><br> Proxy server VPC instance Create a Linux VPC instance that can act as a proxy server. Preconfigure ACL and security group rules to allow public internet traffic over proxy that uses default proxy ports (3828) Configure application load balancer to act as proxy server manually 
 <br><br> * Create a virtual server instance as the only management access point to the landscape<br><br><br> Bastion host VPC instance Create a Linux VPC instance that acts as a bastion host. Configure ACL and security group rules to allow SSH connectivity (port 22). Add a public IP address to the VPC instance. Allow connectivity from a restricted and limited number of public IP addresses. Allow connectivity from IP addresses of the Schematics engine nodes 
 <br><br> * Create a virtual server instance to host basic management services like DNS, NTP, NFS<br><br><br> Management services VPC instance Create a Linux VPC instance that can host management components. Configure ACL and security group rules to allow communication for basic management components. Modify number of virtual server instances and allowed ports in preset or perform the modifications manually 
 <br><br> * Ensure financial services compliancy for VPC services<br> * Perform network setup of all created services<br> * Perform network isolation of all created services<br> * Ensure all created services are interconnected<br><br><br> Secure landing zone components Create a minimum set of required components for a secure landing zone Create a modified set of required components for a secure landing zone in preset 







 PowerVS workspace architecture decisions 



Table 2. PowerVS workspace architecture decisions

 Requirement Component Choice Alternative choice
Intel x86-64



Table 4. Compute profile options for x86-64 instances
Compute profiles options for Intel x86-64 virtual server instances.

 Instance profile vCPU Cores GiB RAM Bandwidth Cap (Gbps) Instance Storage (GB) 

 cx2-2x4 2 1 4 4 <br><br> * <br><br><br> 
 cx2d-2x4 2 1 4 4 1x75 
 cx2-4x8 4 2 8 8 <br><br> * <br><br><br> 
 cx2d-4x8 4 2 8 8 1x150 
 cx2-8x16 8 4 16 16 <br><br> * <br><br><br> 
 cx2d-8x16 8 4 16 16 1x300 
 cx2-16x32 16 8 32 32 <br><br> * <br><br><br> 
 cx2d-16x32 16 8 32 32 1x600 
 cx2-32x64 32 16 64 64 <br><br> * <br><br><br> 
 cx2d-32x64 32 16 64 64 2x600 
 cx2-48x96 48 24 96 80 <br><br> * <br><br><br> 
 cx2d-48x96 48 24 96 80 1x900 
 cx2-64x128 64 32 128 80 <br><br> * <br><br><br> 
 cx2d-64x128 64 32 128 80 2x1200 
 cx2-96x192 96 48 192 80 <br><br> * <br><br><br> 
 cx2d-96x192 96 48 192 80 2x1800 
 cx2-128x256 128 64 256 80 <br><br> * <br><br><br> 
 cx2d-128x256 128 64 256 80 2x2400 







 Memory
For more information, see [Getting started with IBM Cloud IBM Power Systems Virtual Server](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-getting-started).

All instances of an SAP system must run in the same service. Multiple systems can be distributed through different services, in which case IT operations teams must ensure that latency is acceptable for their scenarios.







 IBM Power CPU type - dedicated or shared 

For shared processors, you choose the number of CPUs that the new server is entitled to use. This number should correspond to the number of CPUs that were the result of your sizing. The entitled CPUs should be sufficient for normal production operation and to cover workload during peak time. Don't count on additional CPUs that you might get out of the shared processor pool for uncapped processors.

For dedicated processors, the number of dedicated CPUs should correspond to the number of CPUs that were the result of your sizing.

For more information about shared and dedicated processors, see [Assigning the appropriate processor entitled capacity](https://www.ibm.com/support/pages/assigning-appropriate-processor-entitled-capacity) and [Power Virtual Servers processor types](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-power-iaas-faqsprocessor).

Depending on the SAP workload, supported processor options are restricted. For more information, see [SAP Note 2855850](https://launchpad.support.sap.com//notes/2855850).





 SAP HANA and IBM Power Virtual Server 

See [SAP Note 2947579 - SAP HANA on IBM Power Virtual Servers](https://launchpad.support.sap.com//notes/2947579) for SAP HANA support on IBM Power Virtual Servers.

SAP HANA workloads that use IBM Power Virtual Servers run on IBM Power System E980, with Block Storage powered by [IBM FlashSystem family](https://www.ibm.com/it-infrastructure/storage) connected through the Fibre Channel protocol.
Depending on your order, the server is available for use within one to four hours after the order is submitted. You can check Device Details from the IBM Cloud console (Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > Resource List > Devices) for the status of the provisioning steps. Click the Device Name that matches your device's hostname and domain to see its status.





 Bring your own license 

If you have your own operating system license, you install it on your Bare Metal Servers based on the vendor's instructions. For more information, see [The no OS option](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-bm-no-osbm-no-os).





 Access your server 

Use a public IP for remote access so that you can connect to your server through a Remote Desktop (RDP) client (for example, Microsoft Windows’ MSTSC). The public IP address is displayed in the Device List for your device. The administrator password for your server is also displayed. Click Show Password to see the password.





 Partitioning and file systems 

For the single-node example, a server with one logical disk (on RAID 1) was ordered. The operating system (OS) has one mirrored disk, with one large file system equal to the total size of the ordered disk.

The server does not require any further installation steps for storage.







 Step 2: Provisioning 192 GB and 32 GB servers for a three-tier environment 

A three-tier environment is a more complex scenario that uses a 192 GB server as the database server and a 32 GB server as the SAP NetWeaver application server.



 Ordering your SAP NetWeaver Application Server 

Follow the steps in the [Provisioning a 32 GB server for a single-host environment](https://cloud.ibm.com/docs/sap?topic=sap-quickstudy-bm-netweaver-winsprovisioning_single_host) to order the SAP NetWeaver Application Server.





 Ordering your Database Server 

Use the following steps to order an SAP-certified server as your database server.



1.
Related links 



* [vCenter Server single site](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_vcenterserveroverview)
* [vCenter Server multisite](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_multisite)
* [Regulated workloads - single site](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vrw-overview)
vx2d-44x616 IBM Cloud Virtual Server <br><br> * [OLAP Record](https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN//solutions?filters=iaas&id=s:2603)<br> * [OLTP Record](https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN//solutions?filters=iaas&id=s:2623)<br><br><br> 
 vx2d-88x1232 IBM Cloud Virtual Server <br><br> * [OLAP Record](https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN//solutions?filters=iaas&id=s:2604)<br> * [OLTP Record](https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN//solutions?filters=iaas&id=s:2622)<br><br><br> 
 vx2d-144x2016 IBM Cloud Virtual Server <br><br> * [OLAP Record](https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN//solutions?filters=iaas&id=s:2605)<br> * [OLTP Record](https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN//solutions?filters=iaas&id=s:2621)<br><br><br>
mh1-125x22500 IBM Power Virtual Server <br><br> * [OLTP Record](https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN//solutions?filters=iaas&id=s:2540)<br><br><br> 
 umh-4x960 IBM Power Virtual Server <br><br> * [OLTP Record](https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN//solutions?filters=iaas&id=s:2385)<br><br><br> 
 umh-16x3840 IBM Power Virtual Server <br><br> * [OLTP Record](https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN//solutions?filters=iaas&id=s:2360)<br><br><br> 
 umh-60x14400 IBM Power Virtual Server <br><br> * [OLTP Record](https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN//solutions?filters=iaas&id=s:2386)<br><br><br> 
 ush1-4x128 IBM Power Virtual Server <br><br> * [OLTP Record](https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN//solutions?filters=iaas&id=s:2546)<br><br><br> 
 ush1-4x512 IBM Power Virtual Server <br><br> * [OLTP Record](https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN//solutions?filters=iaas&id=s:2547)<br><br><br>
* [Security and regulation compliance](https://cloud.ibm.com/docs/codeengine?topic=codeengine-responsibilities-cesecurity-compliance)
* [Disaster recovery](https://cloud.ibm.com/docs/codeengine?topic=codeengine-responsibilities-cedisaster-recovery)









 Understanding high availability and disaster recovery for Code Engine 

[Understanding high availability and disaster recovery for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-ha-drha-dr)



* [Code Engine regions](https://cloud.ibm.com/docs/codeengine?topic=codeengine-ha-drha-dr-regions)
* [Availability of Code Engine instances](https://cloud.ibm.com/docs/codeengine?topic=codeengine-ha-drha-dr-availability)
* [Disaster Recovery for Code Engine instances](https://cloud.ibm.com/docs/codeengine?topic=codeengine-ha-drha-dr-disaster)
* [Backing up your Code Engine instances](https://cloud.ibm.com/docs/codeengine?topic=codeengine-ha-drha-dr-backup)







 Supported IBM Cloud and third-party integrations 

[Supported integrations for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-supported-integrationssupported-integrations)



* [IBM Cloud integrations](https://cloud.ibm.com/docs/codeengine?topic=codeengine-supported-integrationssupported-cloud-integrations)
* [Third-party integrations](https://cloud.ibm.com/docs/codeengine?topic=codeengine-supported-integrationssupported-third-integrations)



[Running jobs with Lithops framework](https://cloud.ibm.com/docs/codeengine?topic=codeengine-lithopslithops)