HPE Helion OpenStack Accelerator Environment Readiness Guide HPE Helion OpenStack Professional Services

Reference guide

Reference guide

Contents Introduction ................................................................................................................................................................................................................................................................................................................................................... 3

Server preparation ............................................................................................................................................................................................................................................................................................................................ 3 HPE Helion OpenStack networking .................................................................................................................................................................................................................................................................................. 3 HPE Helion OpenStack server specifications .......................................................................................................................................................................................................................................................... 4 HPE Helion OpenStack storage ........................................................................................................................................................................................................................................................................................... 4 HPE Helion OpenStack installation checklist ........................................................................................................................................................................................................................................................... 4

HPE Helion OpenStack networking overview ............................................................................................................................................................................................................................................................... 5 IPMI network .......................................................................................................................................................................................................................................................................................................................................... 6 Cloud management network ................................................................................................................................................................................................................................................................................................... 6 Service network ................................................................................................................................................................................................................................................................................................................................... 6 External network ................................................................................................................................................................................................................................................................................................................................ 7 External API network ..................................................................................................................................................................................................................................................................................................................... 7 Operator network (optional) ................................................................................................................................................................................................................................................................................................... 7 Network Time Protocol ................................................................................................................................................................................................................................................................................................................ 7 Domain Name Services ................................................................................................................................................................................................................................................................................................................ 7 Networking verifications ............................................................................................................................................................................................................................................................................................................. 8

Generalized Helion OpenStack server configuration .............................................................................................................................................................................................................................................. 8 Servers ......................................................................................................................................................................................................................................................................................................................................................... 9 Deployer (optional) ......................................................................................................................................................................................................................................................................................................................... 9 All servers (except for the optional deployer host) ........................................................................................................................................................................................................................................... 9 Control plane hosts ...................................................................................................................................................................................................................................................................................................................... 10

Storage .......................................................................................................................................................................................................................................................................................................................................................... 11 StoreVirtual VSA hosts (optional) .................................................................................................................................................................................................................................................................................. 11 Swift scale-out object hosts (optional) ...................................................................................................................................................................................................................................................................... 11 Swift scale-out proxy hosts (optional) ....................................................................................................................................................................................................................................................................... 12 Client-defined storage array (optional) ..................................................................................................................................................................................................................................................................... 12 General-purpose example Helion starter cloud rack diagram ............................................................................................................................................................................................................. 13

Reference guide Page 3

Introduction HPE Helion OpenStack® is an open and extensible scale-out cloud platform for building on-premises private clouds with the option of participating in a hybrid cloud when business needs demand it. Helion OpenStack is a hardened commercial-grade product designed to deliver an outstanding open source cloud computing technology in a resilient, maintainable, and an easy-to-install solution when the necessary data has been organized ahead of time.

Client Environment Readiness Guide: This guide is intended to be used as a “checklist” for project managers, solutions architects, and account teams to verify customer infrastructure preparedness prior to having an on-site installation specialist visit the customer site to deploy Helion OpenStack. This document’s checklist is organized for a Helion OpenStack installation that is not performed remotely, but at a customer’s premises. It may also be distributed to customers preparing their data center environments for an HPE Helion OpenStack deployment.

This guide is written for solutions architects and implementation staff preparing for an HPE Helion deployment. This guide assumes knowledge of enterprise data center administration challenges and familiarity with data center configuration and deployment best practices, primarily with regard to network systems. It also assumes that the reader appreciates the infrastructure configuration requirements, system dependencies, challenges, and benefits open source solutions can bring.

Server preparation 1. All systems must be set to the correct date and time.

2. All servers should have “Boot Option” set to “UEFI mode” in BIOS.

3. Make sure that each system is configured in the BIOS to stay powered off in the event of being shutdown rather than automatically restarting.

4. Disable network cards not being used.

5. All servers except the Lifecycle Manager should be configured in BIOS such that only one network interface is enabled for PXE and “Network Boot.”

a. For all other NIC interfaces, set their network boot option to “Disabled.”

6. Except Lifecycle Manager, the boot order on each server should be configured with network or PXE boot as the first option.

7. Disable USB-embedded user partition.

Review the most recent updates to BIOS and iLO settings at docs.hpcloud.com/

HPE Helion OpenStack networking This section covers the network requirements needed for Helion OpenStack. HPE Helion OpenStack uses the following networks for its operations:

• IPMI/iLO network (untagged), connected to the HLM deployer and the IPMI/iLO ports of all servers.

• OS/Install network (untagged) connected to a dedicated NIC on each server used to install the operating system and install and configure Helion. Each bare metal host needs to have a static IP address on this network. We recommend that the user have an IP range on this network reserved for such static IPs. IP range should be sized according to the maximum number of physical servers in deployment.

• A pair of bonded NICs which are used by the following networks:

– External API (untagged or tagged): This is the network that users will use to make requests to the cloud.

– External VM (untagged or tagged): This is the network that will be used to provide access to VMs (via floating IP addresses).

– Provider (tagged)

– Guest VLAN—tagged: This network carries traffic between VMs on private networks within the cloud; control plane and compute nodes are on this VLAN.

– Guest (VXLAN): This is the network that will carry traffic between VMs on private networks within the cloud.

Reference guide Page 4

– Cloud management (untagged): This is the network that will be used for all internal traffic between the cloud services. HOS allocates virtual IPs to cloud services on this network. If the cloud management and OS/Install network are combined on the same untagged VLAN, they may share the same subnet. The IP range for cloud management network can be specified in the configuration file and should not conflict with the static IP range reserved for OS/Installation network.

– Service (tagged): The service network is used for platform services communication such as load balancer as a service (LBAAS), database as a service (DBAAS), and so on. This network must be routed externally to the cloud and be reachable via the management network (i.e., using an external router).

HPE Helion OpenStack server specifications This section describes the requirements and prerequisites of the Helion OpenStack server hardware and primitive software configuration. We will cover the following:

There are three physical servers to support the control plane and optional servers as follows:

• One deployer host (Optional): This server deploys the control plane via Helion Lifecycle Manager (HLM).

• Three controllers: The controllers provide the highly available Helion OpenStack control plane components.

• Between one and ten compute nodes: This server runs the end-user workloads. This is for the standard service delivery. Additional nodes can be enabled optionally with additional or custom services.

• (Optional) Up to three VSA nodes with 3x512 GB disks (or enough space to create three logical drives with that amount of space). Swift must be included if VSA or HPE 3PAR is omitted from the deployment to support glance.

• Optional additional compute or object storage for additional end-user compute and storage capacity.

HPE Helion OpenStack storage If you are using HPE 3PAR StoreServ Storage for back-end block storage, it’s necessary to complete this section.

If there is another back-end block storage in place besides HPE 3PAR StoreServ Storage, this section should be used to describe all elements of the specific client environment storage configuration. Ensure that the storage domain design is understood by the installation team and that its use with Helion OpenStack is investigated. This will include specifics on Fibre Channel use and whether any SAN switches are being used, as well as requirements for an administrative user name and password.

When a Nova compute host is using KVM with Neutron DVR and a floating IP is assigned, communication is made directly to the compute host. Forwarding behavior may differ when using other software-defined networking topologies or hypervisors. If a floating IP is not assigned to a tenant instance, Neutron provides Source Network Address Translation (SNAT) through the controller for outbound external access.

HPE Helion OpenStack installation checklist The following detailed administration guide and checklist items are provided to ensure that the infrastructure needed to perform a HPE Helion OpenStack Installation environment is validated before the installation is attempted on-site:

1. Validate that all the below prerequisites for a generalized Helion OpenStack installation have been completed.

2. Collect and document all information required to perform the installation.

3. Use the data in this document to begin the needed configuration.

Infrastructure item Requirement description Date ready

HPE Helion OpenStack networking

Intelligent platform management interface (IPMI) network

This is a separate, low-traffic network assigned for use with HPE Integrated Lights-Out (iLO).

Management network This is a separate untagged management network that is attached to all servers in the Helion configuration.

Service network This is required for HPE Helion Development Platform and is a tagged network that is connected to controller nodes and compute nodes.

Reference guide Page 5

Infrastructure item Requirement description Date ready

External network This is a tagged network that is used for enabling cloud end-users to access their instances.

Operator network This network is used to enable operations staff access to the Helion environment if direct access to the management network is not possible.

Network Time Protocol (NTP) A protocol server (NTP server) that is required by Helion OpenStack during installation and for operation.

Domain Name Services (DNS) A technology server (DNS server) that is required by Helion OpenStack requires during installation and for operation.

Server specifications

Deployer (optional) host specifications This server hosts Helion OpenStack deployment. It serves as the configuration host for Helion Lifecycle Manager (HLM).

Additional compute hosts These are configuration features and specific information that are required as prerequisites for additional compute capabilities.

HPE Helion OpenStack storage

HPE StoreVirtual Virtual Storage Array (VSA) (optional)

StoreVirtual VSA Cinder performance can be influenced by the choice of drives in the StoreVirtual VSA server.

Swift object storage scale-out hosts (optional)

This is object storage drive selection and configuration information to support archival, low-access, or frequently accessed data needs.

Swift scale-out proxy hosts (optional) This is object storage drive selection and configuration information to support archival, low-access, or frequently accessed data needs.

HPE 3PAR StoreServ Storage array (optional)

This is HPE 3PAR StoreServ configuration information such as administrative user credentials, Fibre Channel and SAN switch information.

Client-defined storage array (optional) This section should be used to describe all of the specific aspects of the client environment storage configurations.

HPE Helion OpenStack networking overview HPE Helion OpenStack installations require the networking shown in Figure 1.

Figure 1. HPE Helion OpenStack networking overview

Reference guide Page 6

• HPE Helion OpenStack networks are composed of untagged and tagged networks.

• IP router used to connect service, IPMI, and management (often can be done in the switches that the servers are attached to).

• Bonded NICs must participate in external switch LACP; otherwise, mode 6 adaptive load balancing will be used.

• Operator access if the customer is not running proof of concept (POC) and requires access to the management network.

• External firewalls—protects the external network, especially if it is attached to the Internet.

• Optional: Use a reverse proxy to enable access to API and Horizon in place of a firewall.

Note This service does not support the design or creation of firewall rules, LBaaS, VPNaaS or security group definition or creation. These functions may be enabled with optional services.

IPMI network This is a separate, low-traffic network assigned for use with iLOs.

Item Value

Network is untagged

Routable to the management network

IP subnet:

Customer router IP address used for default route:

Cloud management network This is a separate untagged management network that is attached to all servers in the Helion configuration. It is a high-traffic network that needs to be secured due to sensitive traffic.

Item Value

No Dynamic Host Configuration Protocol (DHCP) servers other than Helion are on the network

Switch port default VLAN ID (PVID) used to map any “internal” VLANs to untagged network

IP subnet:

Customer router IP address used for default route:

Access to all hosts and HTTPS access to all the iLOs

Service network This is required for HPE Helion Development Platform. This is a tagged network that is connected to cloud controller nodes and compute nodes.

Item Value

VLAN tag assigned to the service network:

IP subnet:

Customer router IP address used for default route:

Reference guide Page 7

External network This is a tagged network that is used for enabling cloud end-users to access their instances. This network is not included in the customer router.

Item Value

VLAN tag assigned to the external network:

IP subnet:

Customer router IP address used for default route:

Is network dedicated to Helion OpenStack?

If not, IPv4 address range for Helion OpenStack:

External API network This is a tagged network that is used for enabling cloud end-users to access their instances. This network is not included in the customer router.

Item Value

VLAN tag assigned to the external network:

IP subnet:

Customer router IP address used for default route:

Operator network (optional) This network is used to enable operations staff access to the Helion environment if direct access to the management network is not possible (not directly configured in Helion).

Item Value

VLAN tag assigned to the external network:

IP subnet:

Customer router IP address used for default route:

Network Time Protocol Helion OpenStack requires a Network Time Protocol (NTP) server during installation and for operation. Consider which system with connectivity can act as an NTP time source. If no access to an NTP time source is possible, use the deployer or controller host’s local clock.

Item Value

NTP time source:

Domain Name Services Helion OpenStack requires a Domain Name Services (DNS) server during installation and for operation. Consider which system with connectivity can act as a DNS server.

Item Value

DNS server:

Cloud domain name

Use self-signed External Certificate Authority (ECA)?

If not, will provide signing certificate authority and private key

Reference guide Page 8

Networking verifications Verifying the items in this section will help ensure a smooth installation process for Helion OpenStack.

• (Optional) Can you access the Internet from the management network? Ensure that the deployer host can access the public Internet. This will be necessary for updating packages as part of the installation.

• Can the deployer host be accessed from the installation location? Ensure full access to the deployer host from the location where the installation will take place.

• Is access to the IPMI network available from the installation location? Access to the IPMI network (via the virtual private network [VPN] or other means) can be helpful during installation in case any hardware or hardware configuration issues are encountered.

• Verify IPMI routing. From the management network, you should be able to ping the IPMI interfaces on the servers. This is required for the installer to function.

• Are all nodes (3X cloud controller, optional VSA, optional Swift, and IPMI controller) connected to the same network?

• Any existing client DHCP servers must not assign addresses to the nodes. This can cause a conflict with the installer process and incorrect addresses may be assigned, resulting in orphaned nodes.

Generalized Helion OpenStack server configuration Figure 2 presents a generalized HPE Helion OpenStack configuration that includes support for Cinder via StoreVirtual VSA and scale-out Swift. An HPE Helion OpenStack deployment may be a subset of this configuration.

Figure 2. Generalized Helion OpenStack server configuration

Use Figure 2 as a basis for your Helion infrastructure design.

Reference guide Page 9

Servers Ensure that any servers to be used are supported by Helion, and that they are racked and stacked with adequate power before any Helion OpenStack software installation is attempted. An example rack configuration can be found at the end of this document. Note that the HPE hardware shown in the example is not the only HPE hardware that could be used for a Helion OpenStack installation.

Collect the following information for each of the server roles. Use the information at docs.hpcloud.com/#helion/hardware.html to ensure that your servers are certified for use with Helion OpenStack and that they meet the minimum standards (disk, memory, CPU, and networking) for their Helion server role. The following checklist must be completed for every server that is planned for use with Helion.

Deployer (optional)

Item Value

Single, large, bootable (over 1 TB) volume created for Ubuntu 14.04 boot

iLO IP address:

iLO user/password:

Memory size (MiB):

CPU thread count:

Disk size (GiB):

Assigned IP address from the management network:

Default route IP address:

Ubuntu user name/password (provided on-site):

All servers (except for the optional deployer host)

Item

The primary NIC is enabled for PXE boot on the management network.

PXE boot is the only boot option in BIOS (all others are disabled).

All hardware in the server not directly used by Helion is disabled.

Reference guide Page 10

Control plane hosts The control plane hosts are as follows:

• 1 Deployer (optional). See docs.hpcloud.com/#helion/hardware.html for updates

• Three cloud controllers

Item: Controllers

• Disk—1 x 600 GB (minimum)—operating system drive

• 2 x 600 GB (minimum)—data drive

• 2 x 10-core 2.66 GHz

• 96–128 GB RAM

iLO IP address:

iLO user/password:

Name NIC1 MAC address iLO user name/password iLO IP address CPU/memory/disk Location

Deployer

Cloud controller 1

Cloud controller 2

Cloud controller 3

Compute hosts

Item

Disks 2 X 600 GB (minimum)

iLO IP address:

iLO user/password:

Name NIC1 MAC address iLO user name/password iLO IP address CPU/memory/disk Location

Cloud controller 1

Cloud controller 2

Cloud controller 3

Cloud controller 4

Cloud controller 5

Cloud controller 6

Cloud controller 7

Cloud controller 8

Cloud controller 9

Cloud controller 10

Reference guide Page 11

Storage StoreVirtual VSA hosts (optional) Note: StoreVirtual VSA Cinder performance can be influenced by the choice of drives in the StoreVirtual VSA server. For high-level Cinder performance, use the Adaptive Optimization feature in StoreVirtual VSA to spread data over SSD and non-SSD drives (refer to StoreVirtual VSA documentation for more details).

Item

One large volume using either RAID 10 or RAID 5 configured for boot

At least one secondary large RAID 5 volume for use as StoreVirtual VSA data

iLO IP address:

iLO user name/password (provided on-site):

Number/size (GiB) of additional volumes for use as StoreVirtual VSA data:

Name NIC1 MAC address iLO user name/password iLO IP address CPU/memory/disk Additional volumes

Swift scale-out object hosts (optional)

Note Servers with slower-drive technologies are adequate for Swift workloads, which are predominately archival or low access in nature. Use higher-specification drives for frequently accessed and modified data.

Note For higher-performance Swift proxy operations, use SSD drives to locate container and account rings.

Item

One volume using either RAID 10 or RAID 5 configured for boot

iLO IP address:

iLO user name (password provided on-site):

Name NIC1 MAC address iLO user name/password iLO IP address CPU/memory/disk Location

Reference guide Page 12

Swift scale-out proxy hosts (optional)

Note For higher-performance Swift proxy operations, use SSD drives to locate container and account rings.

Item

One volume using either RAID 10 or RAID 5 configured for boot

iLO IP address:

iLO user name (password provided on-site):

Name NIC1 MAC address iLO user name/password iLO IP address CPU/memory/disk location

HPE 3PAR StoreServ Storage array (optional)

Item Value

Ensure the firmware level on the HPE 3PAR StoreServ array is supported.

Ensure that the HPE 3PAR StoreServ domain design is understood and that its use with Helion is investigated and is supported by HPE Helion OpenStack.

If Fibre Channel is used, each server has only single pathing enabled.

If booting from SAN, SAN switches are used (“Flat SAN” is not supported).

Appropriate CPGs are created within the HPE 3PAR StoreServ Storage array.

Windows® Web Services API (WWSAPI) IP address:

CLI IP address:

HPE 3PAR StoreServ administrative user name and password:

Client-defined storage array (optional) • If there is another form of back-end block storage in place besides HPE 3PAR StoreServ, this section should be used to describe the client’s or

customer’s entire storage environment.

• Ensure that the storage domain design is understood by the installation team and its use with Helion OpenStack is investigated. This will include specifics on Fibre Channel use and whether any SAN switches are being used, as well as requirements for administrative user name and password.

Reference guide Page 13

General-purpose example Helion starter cloud rack diagram HPE offers a wide range of server, storage, and networking hardware that when combined with the appropriate HPE Helion OpenStack software configuration can provide OpenStack cloud solutions that address unique requirements for compute, networking, and storage.

One possible HPE Helion OpenStack deployment could use a combination of HPE ProLiant DL360 and DL380 Gen9 severs.

• Three Control Plane nodes where Lifecycle Manager resides on one node (optionally on a separate HLM deployer node).

• 1–10 KVM compute nodes

• Three StoreVirtual VSA Cinder nodes

Figure 3. Example storage environment

Reference guide

Sign up for updates

© Copyright 2016–2017 Hewlett Packard Enterprise Development LP. The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.

Intel Xeon is a trademark of Intel Corporation in the U.S. and other countries. Windows is either a registered trademark or trademark of Microsoft Corporation in the United States and/or other countries. The OpenStack Word Mark is either a registered trademark/service mark or trademark/service mark of the OpenStack Foundation, in the United States and other countries and is used with the OpenStack Foundation’s permission. We are not affiliated with, endorsed, or sponsored by the OpenStack Foundation or the OpenStack community. Pivotal and Cloud Foundry are trademarks and/or registered trademarks of Pivotal Software, Inc. in the United States and/or other countries. All other third-party trademark(s) is/are property of their respective owner(s).

4AA6-4326ENW, June 2017, Rev. 1

Table 1. Hardware selection highlights

Server role Quantity Server model Processor Memory Storage Network

Control Plane 3 DL380 Gen9

15 LFF configuration

2x12 core 2.6 Ghz Intel® Xeon®

64 GB 2x600 GB 15K rpm SAS LFF + 4x6 TB 7.2K rpm SAS LFF

10Gb dual port FlexibleLOM

KVM compute 4 DL360p Gen9

8 SFF configuration

2x12 core 2.6 Ghz Intel Xeon

256 GB 6x1.2 TB 10K rpm SAS SFF 10Gb dual port FlexibleLOM

VSA 3 DL380 Gen9

26 SFF configuration

1x6 core 3.4 Ghz Intel Xeon

32 GB 12x1.2 TB 10K rpm SAS SFF

10Gb dual port FlexibleLOM

Learn more at hpe.com/helion