Reference Architecture: Red Hat Enterprise Linux OpenStack Platform 7

Transcription

1 Reference Architecture: Red Hat Enterprise Linux OpenStack Platform 7 Last update: 11 March 2016 Version 1.1 Provides both economic and high performance options for cloud workloads Describes Lenovo E v3 rack servers, networking, and systems management software Describes architecture for high availability and distributed functionality Includes validated and tested deployment and sizing guide for quick start Kai Huang Yixuan Huang Srihari Angaluri

2 Table of Contents 1 Introduction Business problem and business value Business problem Business value Requirements Functional requirements Non-functional requirements Architectural overview Component model Core OpenStack components Other components Red Hat Enterprise Linux OpenStack Platform 7 specific enhancements Operational model Hardware Rack servers Network switches Implementing an OpenStack cluster Compute pool Storage pool Controller cluster Deployment server Support services Systems management Deployment model Deployment example : Full rack system Deployment Example: Minimal Pilot Systems Deployment considerations ii

3 7.1 Server configurations Performance and sizing considerations Networking Expansion and scaling Multiple rack expansion Storage scale out Best practices Conclusions Appendix: Lenovo Bill of Materials Resources iii

4 1 Introduction OpenStack continues to gain significant traction in the industry because of the growing adoption of cloud usage and the flexibility OpenStack offers as an open source development environment. This document describes the reference architecture (RA) for OpenStack from Red Hat Enterprise Linux OpenStack Platform with Lenovo hardware. Red Hat Enterprise Linux OpenStack Platform is an innovative, cost-effective cloud management solution that also includes automation, metering, and security. Red Hat Enterprise Linux OpenStack Platform provides the foundation to build a private or public Infrastructure-as-a-Service (IaaS) cloud on top of Red Hat Enterprise Linux and offers a scalable, highly available platform for the management of cloud-enabled workloads. Red Hat Enterprise Linux OpenStack Platform version 7 is based on the OpenStack Kilo release and includes other features, such as the Red Hat Enterprise Linux OpenStack Platform 7 Director, which can deploy cloud environment to bare metal, and provides support for high availability (HA). It also benefits from the improved overall quality of the open source Kilo release. The Lenovo hardware platform provides an ideal infrastructure solution for cloud deployments. The Lenovo x86 server portfolio spans a broad spectrum of Intel based systems form factors, offering ThinkServer, System x, Flex System, NeXtScale, and BladeCenter product lines. These systems provide the full range of features and functions that are necessary to meet the needs of small businesses all the way up to large enterprises. Lenovo also uses industry standards in systems management on all these platforms, which enables seamless integration into cloud management tools, such as OpenStack. Lenovo also provides data center network switches that are designed specifically for robust, scale-out servers configurations and converged storage interconnect fabrics. This document describes the Lenovo reference architecture (RA) for Red Hat Enterprise Linux OpenStack Platform 7. The target environments include Managed Service Providers (MSPs), Cloud Service Providers (CSPs), and enterprise private clouds that require a complete solution for cloud IaaS deployment and management based on OpenStack. This document also features planning, design considerations, and reference configurations for implementing Red Hat Enterprise Linux OpenStack Platform on the Lenovo hardware platform. The RA enables organizations to easily adopt OpenStack to simplify the system architecture, reduce deployment and maintenance costs, and address the lack of convergence in infrastructure management. The reference architecture focuses on achieving optimal performance and workload density by using Lenovo hardware while minimizing procurement costs and operational overhead. OpenStack and other Red Hat branded software are deployed on the Lenovo hardware platform to instantiate compute, network, storage, and management services. The Lenovo XClarity Administrator software is used to consolidate systems management across multiple Lenovo servers that span the data center. XClarity increases IT productivity and efficiency by visualizing, automating, and streamlining complex, repetitive infrastructure management tasks via out-of-band, scalable management of hundreds of servers. XClarity enables automation of firmware updates on servers via compliance policies, patterns for system configuration settings, hardware inventory, baremetal OS and hypervisor provisioning, and continuous hardware monitoring. XClarity can be easily extended via the published REST API to upwardly integrate into other management tools, such as OpenStack. 1

5 The intended audience for this document is IT professionals, technical architects, sales engineers, and consultants. Readers are expected to have a basic knowledge of Red Hat Enterprise Linux and OpenStack. 2

6 2 Business problem and business value The following sections outline the value proposition of the Red Hat Enterprise Linux OpenStack Platform with Lenovo hardware. 2.1 Business problem Virtualization and cloud achieved tremendous growth on x86 server hardware in recent years. Initially, virtualization provided immediate relief to server sprawl by enabling consolidation of multiple workloads onto a single server. As the hypervisor space evolved and cloud proved to be a more cost-effective means for deploying IT, independent software vendors (ISVs) moved up the software stack as a means of differentiating themselves while driving customer lock-in and profit. MSPs and CSPs face intense challenges that drive them to look for economic but scalable cloud solutions that enable them to offer cost-effective IT services while easily expanding capacity to meet user demand. OpenStack provides an open source alternative for cloud management that is increasingly used to build and manage cloud infrastructures to support enterprise operations. The OpenStack free license also significantly reduces the initial acquisition and expansion costs. However, IT Administrators require deep skills to build a robust cloud service that is based on OpenStack because it is flexible and offers various deployment and configuration options. Moreover, scale out of such a cloud cluster introduces risk of an unbalanced infrastructure, which might lead to performance issues, insufficient network bandwidth, or increased exposure to security vulnerabilities. 2.2 Business value The Red Hat Enterprise Linux OpenStack Platform reference architecture solves the problems described in section 2.1 by providing a blueprint for accelerating the design, piloting, and deployment process of an enterprise-level OpenStack cloud environment on Lenovo hardware. This reference architecture provides the following benefits: Consolidated and fully integrated hardware resources with balanced workloads for compute, network, and storage. An aggregation of compute and storage hardware, which delivers a single, virtualized resource pool that can be customized to different compute and storage ratios to meet the requirements of various solutions. Ease of scaling (vertical and horizontal) based on business requirements. Compute and storage resources can be extended at runtime. Elimination of single points of failure in every layer, which delivers continuous access to virtual machines (VMs). Hardware redundancy and full utilization. Rapid OpenStack cloud deployment, including updates, patches, security, and usability enhancements with enterprise-level support from Red Hat and Lenovo. Unified management and monitoring for kernel-based VMs (KVMs). 3

7 The reference architecture reduces the complexity of OpenStack by outlining a validated configuration that scales and delivers an enterprise level of redundancy across servers, storage, and networking to help enable HA. In this reference architecture, VMs can be migrated among clustered host servers to support resource rebalancing and scheduled maintenance, which allows IT operations staff to minimize service downtime and deployment risks. 4

8 3 Requirements The functional and non-functional requirements for a robust cloud implementation are described in this section. 3.1 Functional requirements Table 1 lists the functional requirements for a cloud implementation. Table 1. Functional requirements Requirement Description Supported by Mobility Resource provisioning Management portal Multi-tenancy Metering Workload is not tied to any physical location Physical servers, virtual machines, virtual storage, and virtual network can be provisioned on demand Web-based dashboard for workloads management Resources are segmented based on tenancy Collect measurements of used resources to allow billing Enabled VM is booted from distributed storage and runs on different hosts Live migration of running VMs Rescue mode support for host maintenance OpenStack compute service OpenStack block storage service OpenStack network service OpenStack bare-metal provisioning service OpenStack dashboard (Horizon) for most routine management operations Built-in segmentation and multi-tenancy in OpenStack OpenStack metering service (Ceilometer) 3.2 Non-functional requirements Table 2 lists the non-functional requirements for MSP or CSP cloud implementation. Table 2. Non-functional requirements Requirement Description Supported by OpenStack environment Supports the current OpenStack edition OpenStack Kilo release through Red Hat Enterprise Linux OpenStack Platform 7 Scalability Solution components can scale for growth Compute nodes and storage nodes can be scaled independently within a rack or across racks without service downtime 5

9 Requirement Description Supported by Load balancing High availability Mobility Workload is distributed evenly across servers Single component failure will not lead to whole system unavailability VM can be migrated or evacuated to different hosting server Network interfaces are teamed and load balanced Use of OpenStack scheduler for balancing compute and storage resources Data blocks are distributed across storage nodes and can be rebalanced on node failure Hardware architecture ensures that computing service, storage service, and network service are automatically switched to remaining components Controller node, compute node, and storage node are redundant Data is stored on multiple servers and accessible from any one of them; therefore, no single server failure can cause loss of data Virtual machines are persistent on shared storage service VM migration VM evacuation Physical footprint Compact solution Lenovo System x server, network devices, and software are integrated into one rack with validated performance and reliability Provides 1U compute node option Ease of installation Reduced complexity for solution deployment A dedicated deployment server with web-based deployment tool and rich command line provide greater flexibility and control over how you deploy OpenStack in your cloud Optional deployment services 6

10 Requirement Description Supported by Support Available vendor support Hardware warranty and software support are included with component products Separately available commercial support from Red Hat for OpenStack issues Flexibility Robustness Security High performance Solution supports variable deployment methodologies Solution continuously works without routine supervision Solution provides means to secure customer infrastructure Solution components are high-performance Hardware and software components can be modified or customized to meet various unique customer requirements Provides local and shared storage for workload Red Hat Enterprise Linux OpenStack Platform 7 is integrated and validated on Red Hat Enterprise Linux 7 Integration tests on hardware and software components Security is integrated in the Lenovo System x hardware with System x Trusted Platform Assurance, an exclusive set of industry-leading security features and practices Networks are isolated by virtual LAN (VLAN) and virtual extensible LAN (VxLAN) for virtual networks Provides medium workloads (2 vcpu, 6 GB vram, 100 GB disk) per host 7

11 4 Architectural overview The Red Hat Enterprise Linux OpenStack Platform 7 is based on the OpenStack Kilo release. This platform offers the innovation of the OpenStack community project and provides the security, stability, and enterprisereadiness of a platform that is built on Red Hat Enterprise Linux. Red Hat Enterprise Linux OpenStack Platform supports the configuration of data center physical hardware into private, public, or hybrid cloud platforms and includes the following benefits: Fully distributed object storage Persistent block-level storage VM provisioning engine and image storage Authentication and authorization mechanisms Integrated networking A web-based GUI for users and administration Figure 1 shows the main components in Red Hat Enterprise Linux OpenStack Platform, which is a collection of interacting services that control the compute, storage, and networking resources. Administrators use a webbased interface to control, provision, and automate OpenStack resources. Also, programmatic access to the OpenStack infrastructure is facilitated through an extensive REST API, which enables a rich set of add-on capabilities. Figure 1. Overview of Red Hat Enterprise Linux OpenStack platform 8

12 5 Component model The section describes the components that are used in OpenStack, specifically the Red Hat Enterprise Linux OpenStack Platform distribution. 5.1 Core OpenStack components Figure 2 shows the core components of Red Hat Enterprise Linux OpenStack Platform. It does not include some optional add-on components, which are listed in the Other components section in this document. Figure 2. Components of Red Hat Enterprise Linux OpenStack platform Table 3 lists the core components of Red Hat Enterprise Linux OpenStack Platform as shown in Figure 2. Table 3. Core components Component Code name Description Compute service Nova Provisions and manages VMs, which creates a redundant and horizontally scalable cloud computing platform. It is hardware and hypervisor independent and has a distributed and asynchronous architecture that provides HA and tenant-based isolation. 9

13 Component Code name Description Block storage service Cinder Provides persistent block storage for VM instances. The ephemeral storage of deployed instances is non-persistent; therefore, any data that is generated by the instance is destroyed after the instance is terminated. Cinder uses persistent volumes that are attached to instances for data longevity, and instances can boot from a Cinder volume rather than from a local image. Networking service Neutron OpenStack Networking is a pluggable networking as a service framework for managing networks and IP addresses. This framework supports several flexible network models, including Dynamic Host Configuration Protocol (DHCP) and VLAN. Image storage service Glance Provides discovery, registration, and delivery services for virtual disk images. The images can be stored on multiple back-end storage units and are cached locally to reduce image staging time. Object storage service Swift Cloud storage software that is built for scale and optimized for durability, availability, and concurrency across the entire data set. It can store and retrieve lots of data with a simple API, and is ideal for storing unstructured data that can grow without bound. (Ceph is used in this Reference Architecture, instead of Swift, to provide object storage service.) Identity service Keystone Provides a central and unified authorization mechanism for all OpenStack users and services across all projects. It supports integration with existing authentication services, such as Lightweight Directory Access Protocol (LDAP). Telemetry service Ceilometer Provides infrastructure to collect measurements within OpenStack. Delivers a unique point of contact for billing systems to acquire all of the needed measurements to establish customer billing across all current OpenStack core components. An administrator can configure the type of collected data to meet operating requirements. Dashboard service Horizon An extensible, web-based application that runs as a Hypertext Transfer Protocol (HTTP) service, which enables cloud administrators and users to control and provision compute, storage, and networking resources. Table 4 lists the optional components in the Red Hat Enterprise Linux OpenStack Platform release. Choose whether and how to use them based on the actual use cases of their cloud deployments. 10

14 Table 4. Optional core components Component Code name Description Bare-metal provisioning service Ironic Originally a Nova bare-metal driver, and now an integrated OpenStack program to provision physical servers and interact with vendor specific hardware. Orchestration Heat An orchestration engine to start multiple composite cloud applications that are based on templates in the form of text files. Other templates also can be started, such as AWS CloudFormation. OpenStack on OpenStack Database as a Service TripleO Trove A program aimed at installing, upgrading and operating OpenStack clouds using OpenStack's own cloud facilities as the foundations Provides a scalable and reliable cloud database as a service provisioning functionality for relational and non-relational database engines. OpenStack defines the concepts that are listed in Table 5 to help the administrator further manage the tenancy or segmentation in a cloud environment. Table 5. OpenStack tenancy concepts Name Tenant Availability Zone Host Aggregate Region Description The OpenStack system is designed to have multi-tenancy on a shared system. Tenants (or projects, as they are also called) are isolated resources that consist of separate networks, volumes, instances, images, keys, and users. Quota controls can be applied to these resources on a per-tenant basis. In OpenStack, an availability zone allows a user to allocate new resources with defined placement. The instance availability zone defines the placement for allocation of VMs, and the volume availability zone defines the placement for allocation of virtual block storage devices. A host aggregate further partitions an availability zone. It consists of key-value pairs that are assigned to groups of machines and can be used in the scheduler to enable advanced scheduling. Regions segregate the cloud into multiple compute deployments. Administrators can use regions to divide a shared-infrastructure cloud into multiple sites with separate API endpoints without coordination between sites. Regions share the Keystone identity service, but each has a different API endpoint and a full Nova compute installation. 11

15 5.2 Other components The following components also are available: Red Hat Ceph Storage is a distributed object store and file system that provides a robust, highly scalable block and object storage platform for enterprises deploying public or private clouds. MariaDB is open source database software that is shipped with Red Hat Enterprise Linux as a replacement for MySQL. MariaDB Galera cluster is a synchronous multi-master cluster for MariaDB. It uses synchronous replication between every instance in the cluster to achieve an active-active multimaster topology, which means every instance can accept data retrieving and storing requests and the failed nodes do not affect the function of the cluster. RabbitMQ is a robust open source messaging system that is based on the AMQP standard. 5.3 Red Hat Enterprise Linux OpenStack Platform 7 specific enhancements Red Hat Enterprise Linux OpenStack Platform 7 offers a better and easier OpenStack based cloud management and platform that is built on Red Hat Enterprise Linux, which includes three years of production support, divided into two sequential phases: Phase 1 (1 year) and Phase 2 (2 years). For more details on Red Hat Enterprise Linux OpenStack Platform lifecycle, please see: Compared with previous Red Hat Enterprise Linux OpenStack Platform edition, Red Hat Enterprise Linux OpenStack Platform 7 offers a more secure, stable and enterprise-ready cloud computing environment for customer deployments. Including: Simplified deployment and management. When compared with Foreman, the new Red Hat Enterprise Linux OpenStack Director provides a simplified and automated cloud installation tool. This comes with system-wide health checking and easy daily operational management and resource provisioning for cloud operators. This is achieved by OpenStack bare-metal resource provisioning simplifying hardware resources deployment and re-purposing on an on-demand basis. Red Hat Enterprise Linux OpenStack Director also integrates with other Red Hat products such as: Red Hat Ceph Storage, Red Hat Satellite 6 and other Red Hat Cloud Infrastructure products (Red Hat CloudForms and Red Hat Enterprise Virtualization). High availability workloads on OpenStack. Red Hat Enterprise Linux OpenStack 7 introduces compute host node HA through Red Hat Enterprise Linux (RHEL) integrated, automated monitoring and failover services. It monitors host nodes and can automatically evacuate virtual machines (VM) from failing hosts. Greater security control. The newly introduced Neutron modular layer 2 (ML2) and Open vswitch (OVS) port security mechanisms allows greater granularity and control over network traffic ports at the VM level,, while allowing virtualized network function (VNF) traffic through each virtual machine, as necessary. 12

16 Incremental Backup. Storage administrators will benefit from faster block storage backups and reduced capacity needs with support for snapshot-based backups by backing up only the incremental changes since the last full state backup. 13

17 6 Operational model Because OpenStack provides a great deal of flexibility, the operational model for OpenStack normally depends upon a thorough understanding of the requirements and needs of the cloud users to design the best possible configuration to meet the requirements. For more information, see the OpenStack Operations Guide. This section describes the Red Hat Enterprise Linux OpenStack Platform operational model that is verified with Lenovo hardware and software. It concludes with some example deployment models that use Lenovo servers and Lenovo RackSwitch network switches. 6.1 Hardware The OpenStack software was validated to run on Lenovo System x3650 M5 and x3550 M5 servers. Lenovo ThinkServer RD650 and RD550 servers listed in this section offer an alternative to System x. This reference architecture guide focuses on the Red Hat OpenStack Platform that is deployed on the Lenovo System x3650 M5 and Lenovo System x3550 M5 servers that are installed with the Red Hat Enterprise Linux 7 operating system and Red Hat Enterprise Linux OpenStack Platform version 7. The network configuration consists of the Lenovo RackSwitch network switches Rack servers Following sections describe the server options for OpenStack. Lenovo System x3650 M5 The Lenovo System x3650 M5 server (as shown in Figure 3 and Figure 4) is an enterprise class 2U twosocket versatile server that incorporates outstanding reliability, availability, and serviceability (RAS), security, and high efficiency for business-critical applications and cloud deployments. It offers a flexible, scalable design and simple upgrade path to inch hard disk drives (HDDs) or solid-state drives (SSDs), or inch HDDs, with doubled data transfer rate via 12 Gbps serial-attached SCSI (SAS) internal storage connectivity and up to 1.5TB of TruDDR4 Memory. Its onboard Ethernet solution provides four standard embedded Gigabit Ethernet ports and two optional embedded 10 Gigabit Ethernet ports without occupying PCIe slots. Combined with the Intel Xeon processor E v3 product family, the Lenovo x3650 M5 server offers a high density of workloads and performance that is targeted to lower the total cost of ownership (TCO) per VM. Its flexible, pay-as-you-grow design and great expansion capabilities solidify dependability for any kind of virtualized workload, with minimal downtime. The Lenovo x3650 M5 server provides internal storage density of up to 100 TB (with up to 26 x 2.5-inch drives) in a 2U form factor with its impressive array of workload-optimized storage configurations. The x3650 M5 offers easy management and saves floor space and power consumption for the most demanding storage virtualization use cases by consolidating the storage and server into one system. 14

18 Figure 3. Lenovo x3650 M5 (with inch disk bays) Figure 4. Lenovo x3650 M5 (with 3.5" disk bays) For more information, see the following websites: System x3650 M5 Overview System x3650 M5 Product Guide Lenovo System x3550 M5 The Lenovo System x3550 M5 server (as shown in Figure 5) is a cost- and density-balanced 1U two-socket rack server. The x3550 M5 features a new, innovative, energy-smart design with up to two Intel Xeon processors of the high-performance E v3 product family of processors; up to 1.5TB of faster, energyefficient TruDDR4 memory; up to 12 12Gb/s SAS drives; and up to three PCI Express (PCIe) 3.0 I/O expansion slots in an impressive selection of sizes and types. The improved feature set and exceptional performance of the x3550 M5 is ideal for scalable cloud environments. Figure 5. Lenovo x3550 M5 For more information, see the following websites: System x3550 M5 - Overview System x3550 M5 Product Guide Lenovo ThinkServer RD550 The Lenovo ThinkServer RD550 (as shown in Figure 6) is a 1U two-socket server that features Intel Xeon E v3 processors and supports up to 768 GB of DDR4 memory, 18 cores, and 36 threads per socket. It offers the capability to support mix and match internal HDD and SSD storage with up to inch drive bays, 140 GbE networking capability, up to eight hot-swap dual rotor fans, hot-swap redundant power supplies, and a dedicated Gigabit Ethernet out-of-band management port in a dense 1U design. 15

19 Figure 6. Lenovo ThinkServer RD550 For more information, see the Lenovo ThinkServer RD550 Product Guide. Lenovo ThinkServer RD650 The Lenovo ThinkServer RD650 (as shown in Figure 7) is a 2U, two-socket storage-rich server that provides up to 74 TB of storage capacity. It features a unique Lenovo AnyBay design that allows a unique hybrid option with nine 3.5-inch and six 2.5-inch front-access drive bays in the front and two 2.5-inch drive bays in the back and the standard 3.5-inch and 2.5-inch HDD chassis, which is ideal for creating a tiered storage environment. The RD650 provides Lenovo AnyRAID technology, which is a mid-plane RAID adapter design that connects directly to the drive backplane without the use of a PCIe slot. SD card options are available to enable flexible boot-drive choices. Figure 7. Lenovo ThinkServer RD650 For more information, see the Lenovo ThinkServer RD650 Product Guide Network switches Following sections describe the TOR switches options that can be used in this reference architecture. The 10Gb switch is used for the internal and external network of Red Hat Enterprise Linux OpenStack Platform cluster, and 1Gb switch is used for out-of-band server management. Lenovo RackSwitch G8124E The Lenovo RackSwitch G8124E (as shown in Figure 8) delivers exceptional performance that is lossless and low-latency. It provides HA and reliability with redundant power supplies and fans as standard. The RackSwitch G8124E also delivers excellent cost savings and a feature-rich design when it comes to virtualization, Converged Enhanced Ethernet (CEE)/Fibre Channel over Ethernet (FCoE), Internet Small Computer System Interface (iscsi), HA, and enterprise-class Layer 2 and Layer 3 functionality. Figure 8. Lenovo RackSwitch G8124E 16

20 With support for 10 Gb, this 24-port switch is designed for clients who are using 10 Gb Ethernet or plan to do so. The G8124E supports Lenovo Virtual Fabric, which provides the ability to dynamically allocate bandwidth per virtual network interface card (vnic) in increments of 100 MB, while adjusting over time without downtime. For more information, see the RackSwitch G8124E Product Guide. Lenovo RackSwitch G8264 Designed with top performance in mind, Lenovo RackSwitch G8264 (as shown in Figure 9) is ideal for today s big data, cloud, and optimized workloads. The G8264 switch offers up to Gb SFP+ ports in a 1U form factor and can be used in the future with four 40 Gb QSFP+ ports. It is an enterprise-class and full-featured data center switch that delivers line-rate, high-bandwidth switching, filtering, and traffic queuing without delaying data. Large data center grade buffers keep traffic moving. Redundant power and fans and numerous high-availability features equip the switches for business-sensitive traffic. Figure 9: Lenovo RackSwitch G8264 The G8264 switch is ideal for latency-sensitive applications, such as client virtualization. It supports Virtual Fabric to help clients reduce the number of I/O adapters to a single dual-port 10 Gb adapter, which helps reduce cost and complexity. The G8264 switch supports the newest protocols, including Data Center Bridging/Converged Enhanced Ethernet (DCB/CEE) for support of FCoE, iscsi, and NAS. For more information, see the RackSwitch G8264 Product Guide. Lenovo RackSwitch G7028 The Lenovo RackSwitch G7028 (as shown in Figure 10) is a 1 Gb top-of-rack switch that delivers line-rate Layer 2 performance at an attractive price. G7028 has 24 10/100/1000BASE-T RJ45 ports and four 10 Gb Ethernet SFP+ ports. It typically uses only 45 W of power, which helps improve energy efficiency. Figure 10. Lenovo RackSwitch G7028 For more information, see the RackSwitch G7028 Product Guide. 17

21 Lenovo RackSwitch G8052 The Lenovo System Networking RackSwitch G8052 (as shown in Figure 11) is an Ethernet switch that is designed for the data center and provides a virtualized, cooler, and simpler network solution. The Lenovo RackSwitch G8052 offers up to 48 1 GbE ports and up to four 10 GbE ports in a 1U footprint. The G8052 switch is always available for business-sensitive traffic by using redundant power supplies, fans, and numerous high-availability features. Figure 11: Lenovo RackSwitch G8052 For more information, see the RackSwitch G8052 Product Guide. 18

22 6.2 Implementing an OpenStack cluster Figure 12 shows how the components and concepts that are described in Page 7 Component model are related to each other and how they form an OpenStack cluster. Figure 12: Deployment model for Red Hat Enterprise Linux OpenStack Platform The deployment node is responsible for the initial deployment of the controller node, compute node, and storage node leveraging the OpenStack bare metal provisioning service. It also performs the service configuration and physical wiring between all deployed nodes. The deployment node also adds additional nodes to the OpenStack cluster. Red Hat Enterprise Linux OpenStack 7 is organized around two main concepts: an Undercloud and an Overcloud. The Undercloud is the single-system OpenStack deployment node that provides environment planning, bare metal system control, installation and configuration of the Overcloud. While the Overcloud is the resulting Red Hat Enterprise Linux OpenStack Platform Infastructure As a Service environment created by the Undercloud. 19

23 The controller node is implemented as a cluster of three instances. The nodes act as a central entrance for processing all internal and external cloud operation requests. The controller nodes also manage the lifecycle of all VM instances that are running on the compute nodes and provide essential services, such as authentication and networking to the VM instances. The controller nodes rely on some support services, such as DHCP, DNS, and NTP. The Nova-Compute and Open vswitch agents run on the compute nodes. The agents receive instrumentation requests from the controller node via RabbitMQ messages to manage the compute and network virtualization of instances that are running on the compute node. Compute nodes can be aggregated into pools of various sizes for better management, performance, or isolation. A Ceph-based storage cluster is created on the storage node, which is largely self-managed and is supervised by the Ceph monitor that is installed on the controller node. The Ceph cluster provides block data storage for Glance image store and for VM instances via the Cinder service Compute pool The compute pool (as shown on the lower-right side of Figure 12) consists of multiple compute servers that are virtualized by OpenStack Nova to provide a redundant and scalable cloud computing environment. Red Hat Enterprise Linux OpenStack Platform provides Nova drivers to enable virtualization on standard x86 servers (such as the x3550 M5 and the x3650 M5) and offers support for multiple hypervisors. Network addresses are automatically assigned to VM instances. Compute nodes inside the compute pool can be grouped into one or more host aggregates according to business need Storage pool A storage pool (as shown on the lower-left side of Figure 12) consists of multiple storage servers that provide persistent block storage resources from their local drives. Ceph is open source software from Red Hat that provides Exabyte-level scalable object, block, and file storage from a completely distributed computer cluster with self-healing and self-managing capabilities. Ceph virtualizes the pool of the block storage devices and stripes the virtual storage as objects across the servers. Ceph is well integrated with OpenStack in the Juno release. The OpenStack Cinder storage component and Glance image services can be implemented on top of the Ceph distributed storage. OpenStack users and administrators can use the Horizon dashboard or the OpenStack command-line interface to request and use the storage resources without requiring knowledge of where the storage is deployed or how the block storage volume is allocated in a Ceph cluster. The Nova, Cinder, Swift, and Glance services on the controller and compute nodes use the Ceph driver as the underlying implementation for storing the actual VM or image data. Ceph divides the data into placement groups to balance the workload of each storage device. Data blocks within a placement group are further distributed to logical storage units called Object Storage Devices (OSDs), which often are physical disks or drive partitions on a storage node. The OpenStack services can use a Ceph cluster in the following ways: VM Images: OpenStack Glance manages images for VMs. The Glance service treats VM images as immutable binary blobs and can be uploaded to or downloaded from a Ceph cluster accordingly. 20

24 Volumes: OpenStack Cinder manages volumes (that is, virtual block devices), which can be attached to running VMs or used to boot VMs. Ceph serves as the back-end volume provider for Cinder. Object Storage: OpenStack Swift manages the unstructured data that can be stored and retrieved with a simple API. Ceph serves as the back-end volume provider for Swift. VM Disks: By default, when a VM boots, its drive appears as a file on the file system of the hypervisor. Alternatively, the VM disk can be in Ceph and the VM is started by using the boot-fromvolume functionality of Cinder or directly started without the use of Cinder. The latter option is advantageous because it enables maintenance operations to be easily performed by using the livemigration process, but only if the VM uses the RAW disk format. If the hypervisor fails, it is convenient to trigger the Nova evacuate function and almost seamlessly run the VM machine on another server. When the Ceph back end is enabled for both Glance and Nova, there is no need to cache an image from Glance to a local file, which saves time and local disk space. In addition, Ceph can implement a copy-on-write feature, so that starting an instance from a Glance image does not actually use any disk space. In this reference architecture, all data are stored in a single Ceph cluster for simplicity and ease of management. For better performance and security consideration, multiple Ceph clusters can be created for each OpenStack service or for different tenants. Figure 13 shows the details of the integration between the OpenStack services and Ceph. Figure 13. Ceph and OpenStack services integration 21

25 Ceph uses a write-ahead mode for local operations; a write operation hits the file system journal first and from there it is copied to the backing file store. Therefore, SSDs are used here for the journal data to improve the storage performance. Note: Hardware RAID should not be used because Ceph provides software-based data protection by object replication and data striping Controller cluster The controller nodes (as shown on the upper-left side of Figure 12) are central administrative servers where users can access and provision cloud-based resources from a self-service portal. The HA of services that are running on controllers is primarily provided by using redundant controller nodes, as shown in Figure 14. Odd number of controller nodes are used (minimum of 3) because most HA capability is based on a quorum-based system; for a three node controller cluster, if two controllers disagree, the third is used as the arbiter. Figure 14: Controller cluster The controller cluster also hosts proxy and message broker services for scheduling compute and storage pool resources and provides the data store for cloud environment settings. In addition, the controller servers act as network nodes that provide Software Defined Networking (SDN) functionality to the VMs. Network nodes are responsible for managing the virtual networking that is needed for administrators to create public or private networks and uplink VMs into external networks, which form the only ingress and egress points for instances that are running on top of OpenStack. Each service location is referred to by using a Virtual IP (VIP) and the mapping between physical IP and VIP is automatically managed by Pacemaker; therefore, switching a service provider between different controller nodes is transparent to service consumers. For a three-node controller cluster, each service needs three physical IP addresses and one virtual IP address. 22

26 Because all OpenStack API services are stateless, the user can choose an active/passive HA model or an active/active HA model with HAProxy to achieve load balancing. However, session stickiness for the Horizon web application must be enabled. RabbitMQ and Ceph include built-in clustering capabilities. MariaDB database uses the Galera library to achieve HA deployment Deployment server The Red Hat Enterprise Linux OpenStack Platform 7 uses Red Hat Enterprise Linux OpenStack Platform Director as the toolset for installing and managing an OpenStack environment, as opposed to Foreman used in Red Hat Enterprise Linux OpenStack Platform 6. The Red Hat Enterprise Linux OpenStack Platform Director is based primarily on the OpenStack TripleO project, which uses a minimal OpenStack installation to deploy a fully operational OpenStack environment, including controller nodes, compute nodes, and storage nodes as shown in the diagrams. The Ironic component enables bare metal server deployment and management.. This tool simplifies the process of installing and configuring the Red Hat Enterprise Linux OpenStack Platform while providing a means to scale in the future Support services Support services (as shown on the upper-right side of Figure 12), such as Domain Name System (DNS), Dynamic Host Configuration Protocol (DHCP), and Network Time Protocol (NTP) are needed for cloud operations. These services can be installed on the same deployment server or reused from the customer s environment. 23

27 6.3 Systems management Lenovo XClarity Administrator is a centralized resource management solution that reduces complexity, speeds up response, and enhances the availability of Lenovo server systems and solutions. The Lenovo XClarity Administrator provides agent-free hardware management for Lenovo s System x rack servers and Flex System compute nodes and components, including the Chassis Management Module (CMM) and Flex System I/O modules. Figure 15 shows the Lenovo XClarity administrator interface, where Flex System components and rack servers are managed from the dashboard. Lenovo XClarity Administrator is a virtual appliance that is quickly imported intoopenstack environment. Figure 15: XClarity Administrator interface 24

28 6.4 Deployment model There are many models for deploying an OpenStack environment. To achieve the highest usability and flexibility, you can assign each node a specific role and place the corresponding OpenStack components on it. The controller node has the following roles in supporting OpenStack: The controller node acts as an API layer and listens to all service requests (Nova, Glance, Cinder, and so on).the requests first land on the controller node. Then, the requests are forwarded to a compute node or storage node through messaging services for underlying compute workload or storage workload. The controller node is the messaging hub in which all messages follow and route through for crossnode communication. The controller node acts as the scheduler to determine the placement of a particular VM, which is based on a specific scheduling driver. The controller node acts as the network node, which manipulates the virtual networks that are created in the cloud cluster. However, it is not mandatory that all four roles are on the same physical server. OpenStack is a naturally distributed framework by design. Such all-in-one controller placement is used for simplicity and ease of deployment. In production environments, it might be preferable to move one or more of these roles and relevant services to another node to address security, performance, or manageability concerns. On the compute nodes, the installation includes the essential OpenStack computing service (openstacknova-compute), along with the neutron-openvswitch-agent, which enables software-defined networking. An optional metering component (Ceilometer) can be installed to collect resource usage information for billing or auditing. On a storage node, the Ceph OSD service is installed. It communicates with the Ceph monitor services that are running on controller nodes and contributes its local disks to the Ceph storage pool. The user of the Ceph storage resources exchanges data objects with the storage nodes through its internal protocol. 25

29 Table 6 lists the placement of major services on physical servers. Table 6. Components placement on physical servers Role Host Name Services Red Hat Enterprise Linux OpenStack Platform 7 Director server (Undercloud) Controller node deployer controller01 - controller03 openstack-nova-* (Undercloud) openstack-glance-* (Undercloud) openstack-keystone(undercloud) openstack-dashboard(undercloud) neutron-* (Undercloud) openstack-ceilometer-*( Undercloud) openstack-heat-* (Undercloud) openstack-ironic-* (Undercloud) rabbitmq-server(undercloud) opevswitch(undercloud) mariadb(undercloud) openstack-cinder-api openstack-cinder-backup openstack-cinder-scheduler openstack-cinder-volume openstack-glance-api openstack-glance-registry openstack-keystone openstack-nova-api openstack-nova-cert openstack-nova-conductor openstack-nova-consoleauth openstack-nova-novncproxy openstack-nova-scheduler neutron-dhcp-agent neutron-13-agent neutron-metadata-agent neutron-openvswitch-agent neutron-server openstack-ceilometer-alarm-evaluator openstack-ceilometer-alarm-notifier openstack-ceilometer-api openstack-ceilometer-central openstack-ceilometer-collector ceph-monitor rabbitmq, mariadb, mongodb 26

30 Role Host Name Services Compute node compute01 - compute18 neutron-openvswitch-agent openstack-ceilometer-compute openstack-nova-compute Storage node storage01 - storage03 ceph-osd 27

31 6.4.1 Deployment example : Full rack system The Lenovo System x3650 M5 and Lenovo System x3550 M5 previously described in Section can be combined into a full rack of Red Hat Enterprise Linux OpenStack Platform cluster. Figure 16 shows a balanced configuration of compute, storage, networking, and power. The VM capacity is calculated on a perhost density basis. For more information about how to estimate the VM density, see "Performance and sizing considerations" on page 31. Components Capacity Rack Layout Networking VM capacity 10 GbE >760 (mixed workload) KVM and Monitor 1 Controller nodes 3 Compute nodes 14 Storage nodes 3 Deployment server 1 Local storage 86 TB (RAID-10) Local IOPS >100 External storage 108 TB (with 2 replicas) Figure 16. Deployment example 1: Full rack system 28

32 Because it is impractical to take into account every possible combination of these options, this configuration can be modified in a real scenario to best fit the workloads that are running on the target cloud environment Deployment Example: Minimal Pilot Systems OpenStack node Server configuration non- HA HA Deployment server Controller node Lenovo System x3550 M5 with single Xeon E v3 processor, 16 GB RAM, and two 1.2TB 2.5-inch HDDs Lenovo System x3550 M5 with two Xeon E v3 processors, 16 GB RAM, and two 1.2TB 2.5-inch HDDs Compute node Lenovo System x3650 M5 with single Xeon E v3 processors, 16 GB RAM, and two 900 GB 2.5-inch HDDs 1 or more 1 or more Storage node Lenovo System x3650 M5 with single Xeon E v3 processor, 16 GB RAM, two SSDs as cache, and up to twelve 3.5-inch 6TB HDDs 1 3 For a pilot private cloud project, a proof-of-concept infrastructure can be setup with a entry level configuration. It utilizes minimum hardware to demonstrate the setup and functionality of the Lenovo OpenStack reference architecture. For non-ha scenario, single Lenovo System x server is used for each role in OpenStack cluster. Storage node is optional if compute node is configured to use local storage to store VM files. For HA scenario, three controller nodes and three storage nodes should be minimal configuration. Instance which run on compute node will be located at storage nodes to achieve high availability. 29

33 7 Deployment considerations This section describes the performance, sizing, and networking considerations for a Red Hat Enterprise Linux OpenStack Platform deployment. 7.1 Server configurations Table 7 lists three server configurations for OpenStack compute nodes that meet different performance and density needs. Table 7. Compute node configurations Compute node Standard configuration Enhanced configuration Advanced configuration Server configuration System x3650 M5 with dual Xeon E v3 processors, 256 GB RAM, and GB 2.5-inch HDDs in 2U server System x3550 M5 with dual Xeon E v3 processors, 256 GB RAM, and eight 1.2 TB 2.5-inch HDDs plus two 200GB SSDs in RAID array in 1U server System x3650 M5 with dual Xeon E v3 processors, 384 GB RAM, and TB 2.5-inch HDDs plus two 400GB SSDs in RAID array in 2U server The standard configuration uses a System x3650 M5 dual-socket 2U rack server (with 2.5-inch disk bays) and is configured for general workloads in this reference architecture. Such configuration features balanced computing, memory, and storage, and is cost-competitive on a per-vm basis. Memory or drives can be added to accommodate workloads that require more capacity. The enhanced configuration uses a System x3550 M5 server dual-socket 1U server and is configured for I/O intensive workloads to maximize storage performance. Two Lenovo S3700 SSDs are used with LSI MegaRAID CacheCade Pro 2.0 as a dedicated pool of RAID controller cache to improve the read/write performance of the disk array of a server s eight HDDs. The Lenovo S3710 Enterprise Performance SATA SSDs for System x use Intel NAND flash memory with high endurance technology and provide an efficient solution with industry-leading performance. These SSDs can be fully rewritten up to 10 times per day throughout their entire five-year life expectancy. This technology offers an ideal combination of capacity and high performance. The advanced configuration uses a System x3650 M5 dual-socket 2U rack server and is suited to compute heavy workloads. This server has faster processors, more memory, and higher available IOPS. Table 8 lists the server configurations for the other types of nodes that are required for building an OpenStack cloud. 30

34 Table 8. OpenStack node configurations OpenStack node Deployment server Controller node Storage node Server configuration System x3550 M5 with a single Xeon E v3 processor, 16 GB RAM, and two 900GB 2.5-inch HDDs System x3650 M5 with dual Xeon E v3 processors, 64 GB RAM, and two 900GB 2.5-inch HDDs System x3650 M5 with a single Xeon E v3 processor, 64 GB RAM, two 2.5-inch SSDs, and up to twelve 3.5 6TB HDDs The Storage Node uses a System x3650 M5 (with 3.5-inch disk bays) server. It has up to 65 TB of storage capacity with inch HDDs and is ideal to fulfil requirements for external storage. The storage capacity is shared by multiple compute nodes by making available its local disks through Ceph storage system and the OpenStack Cinder service. To achieve optimal performance, the two 2.5-inch SSDs in the rear are partitioned for the operating system and storing the Ceph journal data. For more information about server configurations and a Bill of Materials, see "Appendix: Lenovo Bill of Materials" on page Performance and sizing considerations The expected performance of the OpenStack clusters relies on the actual workload that is running in the cloud and the correct sizing of each component. This section provides a sizing guide for different workloads and scenarios. Table 9 lists the assumptions for the workload characteristics. The mixed workload consists of 45% small, 40% medium, and 15% large VMs. This information serves as a baseline only to measure the user s real workload and is not necessarily meant to represent any specific application. In any deployment scenario, workloads are unlikely to have the same characteristics, and workloads might not be balanced between hosts. An appropriate scheduler with real performance measurement of a workload must be used for compute and storage to meet the target service level agreement (SLA). Table 9. VM workloads characteristics vcpu vram Storage IOPS Small 1 2 GB 20 GB 15 Medium 2 6 GB 60 GB 35 Large 6 12 GB 200 GB 100 When sizing the solution, calculate the amount of required resources that is based on the amount of workload expected. Then, multiply that amount by the maximum size of the workload and add a 10% buffer for management overhead. 31

35 For better resource utilization, consider putting similar workloads on the same guest OS type in the same host to use memory or storage de-duplication, as shown in the following examples: Virtual CPU (vcpu) = Physical Cores * CPU allocation ratio 1 (6:1) Virtual Memory (vram) = Physical Memory * (RAM allocation ratio 2 ) * (100% - OS reserved) By using these formulas, usable virtual resources can be calculated from the hardware configuration of compute nodes, as shown in Table 10. Table 10. Virtual resource Standard configuration Enhanced configuration Server System x3650 M5 System x3550 M5 vcpu 20 Cores*6 = 120 vcpu 20 Cores*6 = 120 vcpu vram 256 GB*150%*(100% - 10%) = 345 GB 256 GB*150%*(100% - 10%) = 345 GB Storage Space 16*900GB with RAID-10 = 6.6 TB 8*1.2TB with RAID-10 + SSD Cache = 4.8TB By using a mixed workload requirement that was generated from Table 9 in which each VM requires 2 vcpu, 6 GB vram, 80 GB local disk, and 100 IOPS, it is easy to calculate the expected VM density (the smallest number determines the number of VMs that can be supported per compute server). Table 11 shows 57 VMs per host for the standard and enhanced configurations. Table 11. Resource-based VM density for mixed workload CPU Memory Storage Space IOPS (67% read ops + 33% write ops) Standard configuration 120/2 = /6 = T/80 GB = 82 3~8000/100 = 80 Enhanced configuration 120/2 = /6 = T/80 GB = 60 3 ~20000/100 = 200 However, the actual user experience of I/O performance is largely dependent on workload pattern and OpenStack configuration; for example, the number of concurrent running VM instances and the cache mode. By applying the calculated density of a single compute host, this reference architecture can be tailored to fit various sizes of cloud cluster. 1 CPU allocation ratio indicates the number of virtual cores that can be assigned to a node for each physical core. 6:1 is a balanced choice for performance and cost effectiveness on models with Xeon E v3 series processors. 2 RAM allocation ratio is to allocate virtual resources in excess of what is physically available on a host through compression or deduplication technology. The hypervisor uses it to improve infrastructure utilization of the RAM allocation ratio = (virtual resource/physical resource) formula. 3 IOP estimates for standard and enhanced configurations are derived from measurements performed by using the FIO performance tool. 32

36 7.3 Networking Combinations of physical and virtual isolated networks are configured at the host, switch, and storage layers to meet isolation, security, and quality of service (QoS) requirements. Different network data traffic is physically isolated into different switches according to the physical switch port and server port assignments. There are five onboard 1 GbE Ethernet interfaces (including one dedicated port for the IMM) and an installed dual-port 10 GbE Ethernet device for each physical host (x3550 M5 or x3650 M5). The 1 GbE management port (dedicated for the Integrated Management Module, or IMM) is connected to the 1GbE RackSwitch G7028 for out-of-band management, while the other 1 GbE ports are not connected. The corresponding Red Hat Enterprise Linux 7 Ethernet devices eno[0-9] are not configured. Two G8124E 24- port 10GbE Ethernet switches are used in pairs to provide redundant networking for the controller nodes, compute nodes, storage nodes, and deployment server. The dual port 10G Emulex Virtual Fabric Adapter delivers virtual I/O by supporting vnics, with which two ports can be divided into eight virtual NICs. Administrators can create dedicated virtual pipes between the 10 GbE network adapter and the TOR switch for optimal performance and better security. Linux NIC bonding is then applied to the vnics to provide HA to the communication networks. Ethernet traffic is isolated by type through the use of virtual LANs (VLANs) on the switch. Table 12 lists the six logical networks in a typical OpenStack deployment. Table 12. OpenStack Logical Networks Network VLAN Description BMC Network 1 Used for out-of-band management of hosts and switches via IMM. Management Network 2 The network where OpenStack APIs are shown to the users and the message hub to connect various services inside OpenStack. The OpenStack Installer also uses this network for host discovery and initial deployment. Internal Network 3 This is the subnet from which the VM private IP addresses are allocated. Through this network, the VM instances can talk to each other. External Network 4 This is the subnet from which the VM public IP addresses are allocated. It is the only network where external users can access their VM instances. Storage Network 5 The front-side storage network where Ceph clients (through Glance API, Cinder API, or Ceph CLI) access the Ceph cluster. Ceph Monitors also operate on this network. Data Cluster Network 6 The back-side storage network to which Ceph routes its heartbeat, object replication, and recovery traffic. vnic0 and vnic4 are used to create 'bond0', and vnic1 and vnic5 are used to create 'bond1', and so on. The 20 Gb bandwidth from dual 10 Gb connections are dynamically allocated to four vnic bonds, and can adjust as required in increments of 100 Mb without downtime. 33

37 Figure 17 shows the recommended network topology diagram with VLANs and vnics. Figure 17. Network topology diagram Table 13 lists the recommended VLAN and bandwidth that is used by each type of node in an OpenStack deployment. The bandwidth of each logical network is for general-purpose workloads only. These recommendations can be adjusted accordingly at runtime for the actual workload without service interruption. 34

38 Table 13. Recommended VLAN usage by OpenStack nodes Role Logical Network Usage Bandwidth VLAN Controller Node Bond0 Management Network 2 Gb/s 2 Bond1 Internal Network 2 Gb/s 3 Bond2 Storage Network 12 Gb/s 4 Bond3 External Network 4 Gb/s 6 Compute Node Bond0 Management Network 2 Gb/s 2 Bond1 Internal Network 6 Gb/s 3 Bond2 Storage Network 12 Gb/s 4 Bond3 Reserved 0 Gb/s N/A Storage Node Bond0 Management Network 2 Gb/s 2 Bond1 Reserved 0 Gb/s N/A Bond2 Storage Network 12 Gb/s 4 Bond3 Data Cluster Network 8 Gb/s 5 Deployment Server (no bonding) Management Network 1 Gb/s 2 The Emulex VFA5 adapter is used to offload packet encapsulation for VxLAN networking overlays to the adapter, which results in higher server CPU effectiveness and higher server power efficiency. Open vswitch (OVS) is a fully featured, flow-based implementation of a virtual switch and can be used as a platform in software-defined networking. Open vswitch supports VxLAN overlay networks, and serves as the default OpenStack network service in this reference architecture. Virtual Extensible LAN (VxLAN) is a network virtualization technology that addresses scalability problems that are associated with large cloud computing deployments by using a VLAN-like technique to encapsulate MAC-based OSI layer 2 Ethernet frames within layer 3 UDP packets. 35

39 7.4 Expansion and scaling This section describes multi-rack expansion and storage scale out Multiple rack expansion If the workload demands exceed the capacity of one rack, span the OpenStack cloud across multiple racks to increase capacity. A common practice is to deploy controller nodes that are running separate sets of APIs and scheduler services that are managing the compute and storage nodes in each rack. Sharing controller nodes that are running a single instance of authentication (Keystone) and dashboard (Horizon) services are shared across all racks for centralized management, as shown in Figure 18. Figure 18. Multiple rack deployment example Each rack has its own Power Distribution Unit (PDU) and TOR switches and can operate separately, regardless of the health status of other racks. The two G8124E switches and one G7028 switch that were used in the previous full-rack example can manage up to 20 servers in a Red Hat Enterprise Linux OpenStack Platform networking environment. If the expected size of the Red Hat Enterprise Linux OpenStack Platform cloud exceeds 20 servers, the switches should be substituted with the G8264 and G8052, respectively, because they have more ports and can manage up to 40 servers Storage scale out To increase shared storage space, add storage nodes to the cluster and duplicate the configuration of the storage node, or add drives to a storage node. Then, run the ceph osd create Ceph management command to notify the monitors. The monitors automatically discover increased storage capacity and add it to the storage pool without any administrative effort or rebooting the storage service. 36