Planning your deployment

Before you begin

To help make sure that your first deployment is a success, read Fast path of IBM Power Virtual Servers including the following sections:

• IBM Power Systems Infrastructure environment introduction for the basic understanding about the environment.
• Connectivity options within the IBM Power Virtual Server network, connection through IBM Cloud
• Sample storage configurations on IBM Power Infrastructure

Prerequisites

Review the following prerequisites.

1. You need sufficient IBM Cloud IAM permissions to create all required elements.

   • Create services from IBM Cloud catalog.
   • Create and modify IBM Cloud VPC services, virtual server instances, networks, network prefixes, storage volumes, ssh keys, and security groups of this VPC.
   • Create and modify Power® Virtual Server services, virtual server instances, networks, storage volumes, ssh keys of this Power® Virtual Server.
   • Create and modify IBM Cloud direct links and IBM transit gateways.
   • Access existing {site{.data.keyword.cos_short}} services.

2. Make sure that you have an SSH key that you can use for authentication. This key is used to log in to all virtual server instances that you create. For more information about creating SSH keys, see SSH keys.

3. Upload SAP software installation packages and SAP maintenance planer XML files to an existing {site{.data.keyword.cos_short}} bucket. To configure access to these software packages from a running virtual server instance, you need following information:

   • {site{.data.keyword.cos_short}} endpoint
   • Object Storage bucket name
   • Object Storage HMAC access key
   • Object Storage HMAC secret access key

   For more information about configuring API access in IBM Cloud Object Storage Getting started with IBM Cloud Object Storage and Service credentials.

4. Choose a Linux operating system for your deployments. We recommend that you use the same OS release for all the hosts in the environment. When you use the same operating system version and release, it simplifies the operations management of the whole landscape. In this tutorial, Linux is used on all management components that run in your landscape. SAP solutions can run on Linux or on AIX.

5. Read OS for IBM Power Virtual Servers to learn about supported operating systems for SAP workloads on Power® Virtual Server.

6. Design the network layout for your landscape. Specify the IP address ranges in the subnets to prevent IP address conflicts between all subnets in the landscape, including external subnets (subnets in your on-premises environment), and any other subnets.

   All IP address ranges in the subnets must be unique.

   The following private networks are created. You need to specify IP address ranges for them.

   Private networks IP address ranges

   Service	Private network	IP address ranges
   Management VPC	Address prefix for VPC management network VPC management network for virtual server instances	172.10.0.0/16 172.10.1.0/24
   Workload VPC	Address prefix for VPC workload network VPC management network for virtual server instances	172.11.0.0/16 172.11.2.0/24
   Edge VPC	Address prefix for VPC edge network VPC edge network for virtual server instances	172.12.0.0/16 172.11.1.0/24
   Power VS workspace	Power VS management network PowerVS backup network Separate network for each SAP system on Power VS and each SAP system or SAP component group on VPC SAP S4/HANA PRD SAP S4/HANA QA1 SAP Web Dispatchers on edge VPC	10.10.10.0/24 10.10.11.0/24 10.10.20.0/24 10.10.21.0/24

7. Define hostnames for all the virtual server instances and services that you deploy in the landscape. Map the hostnames to the IP addresses. Also, it's possible to deploy the virtual server instances and assign the IP address dynamically. Make sure that you clear DNS/IP picture before you start. You can use a DNS service of your choice. The only requirement is that this service must be reachable from the Virtual Private Cloud. In the example, IBM Cloud DNS service is used with the following hostname / IP address mappings.

   Example host name and IP address mappings

   Deployed virtual server instance and services	Hostname	IP address
   Access host	access.example.com	172.10.1.4
   Basic management services	basic.service.example.com	172.11.1.4
   Critical management services	critical.service.example.com	172.11.1.5
   Power VS shared file system	power.service.mgmt.example.com	10.10.10.4
   Example virtual server instance host for SAP HANA DB	db.mgmt.prd.example.com	10.10.10.5
   Example SAP HANA DB host	db.prd.example.com	10.10.20.5
   Example virtual server instance host for SAP NetWeaver	app1.mgmt.prd.example.com	10.10.10.6
   Example SAP NetWeaver application server host	app1.prd.example.com	10.10.20.6

8. Each Unix OS user has a UID and GUID. These IDs are used to specify file system ownership and become a part of file system metadata. In the management scenarios, where file system is backed up on one host and restored on another, both hosts must use the same UID and GUID for the same users. For the best experience, make sure that you use central user management for SAP users. In the example deployment, LDAP client setup was used on the virtual server instances that are running on Power® Virtual Server.

9. You need an overview about the ports that must be opened for communication between SAP workloads that run on IBM Power Systems Virtual Servers (such as SAP NetWeaver or SAP HANA), in VPC (such as SAP Web Dispatcher, SAP Solution Manager) and outside of the environment (such as clients in public internet or in on-premises environment).

10. Determine the size parameters for each SAP workload that you plan to deploy. The most important parameters are memory size (especially for SAP HANA) and the number of SAPs. Most of the other configurations can be derived from these two key metrics.

For more information, see Sizing process for SAP Systems and see SAP Sizing.

For deployment of each Power VS instance, you must be aware of following sizing parameters:

• Memory size
• Number of CPUs
• Sharing type of CPUs (on Power® Virtual Server, for certain SAP workloads such as SAP NetWeaver)
• Certified SAP t-shirt size as combination of memory and number of CPUs (for certain SAP workloads such as SAP HANA)
• Needed file systems, each with file system size
• Swap space size (for certain SAP workloads, such as SAP NetWeaver)