EMC STORAGE SOLUTIONS WITH MIRANTIS OPENSTACK

Transcription

1 EMC STORAGE SOLUTIONS WITH MIRANTIS OPENSTACK Managing EMC Storage Arrays with OpenStack Juno EMC Solutions May 2015

2 Copyright 2015 EMC Corporation. All Rights Reserved. Published May 2015 EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. Copyright 2015 Mirantis, Inc. All rights reserved. "Mirantis" and "FUEL" are registered trademarks of Mirantis, Inc. All other trademarks used herein are the property of their respective owners. Part Number H

3 Table of contents Reference architecture overview... 5 Document purpose... 5 Audience... 5 Solution purpose... 5 Business challenge... 5 Technology solution... 6 Solution architecture... 7 Architecture diagrams... 7 Hardware resources... 8 Software resources... 9 Storage protocols... 9 Key components Introduction VNX unified storage platform XtremIO flash-based storage platform ScaleIO storage management software OpenStack OpenStack technology overview Introduction OpenStack components Compute (Nova) Object Storage (Swift) Block Storage (Cinder) Networking (Neutron) Dashboard (Horizon) Identity Service (Keystone) Orchestration (Heat) Telemetry (Ceilometer) (optional when deploying Mirantis OpenStack) Image Service (Glance) Data Processing (Sahara) (optional when deploying Mirantis OpenStack) Catalog service (Murano) (optional when deploying Mirantis OpenStack) CentOS Requirements Server and networking requirements VNX requirements iscsi requirements

4 Fibre Channel requirements XtremIO requirements iscsi requirements Fibre Channel requirements Multipath requirements ScaleIO requirements OpenStack requirements Installation Server hardware preparation Network preparation Fabric setup Mirantis Fuel installation OpenStack controller node deployment OpenStack compute node deployment Configuration VNX XtremIO ScaleIO Cinder high availability Managing storage volumes Support Conclusion References EMC documentation Mirantis documentation OpenStack documentation

5 Reference architecture overview Document purpose This reference architecture guide describes a solution for managing storage volume life cycles using EMC storage technologies and Mirantis OpenStack Juno distribution. The document introduces the main features and functionality of the solution, the solution architecture and components, and the validated hardware and software environments. This document describes the reference architecture and provides guidance on integrating the components and functionality of Mirantis OpenStack software and EMC storage systems. This document is not a comprehensive guide to every aspect of the solution. Audience Solution purpose Business challenge This reference architecture guide is for cloud architects, cloud operators, and general IT administrators who want to manage EMC storage with Mirantis OpenStack. Readers should be familiar with OpenStack, Linux, EMC storage technologies, and general IT functions. The purpose of this solution is to build an enterprise-class, scalable, and multitenant cloud infrastructure that integrates EMC storage technologies with Mirantis OpenStack software. This solution is built on EMC VNX, EMC XtremIO, and EMC ScaleIO storage platforms managed by OpenStack Juno and Mirantis Fuel 6.0. The difficulty of creating a cloud solution has given rise to several cloud software vendors who have built proprietary technology and business models specifically catering to the requirements of standardization, agility, control, and reliability. Several new open source technologies also are available to assist in creating a cloud solution, but customers need to know how to best use these technologies to drive standardization, integrate open source and proprietary systems, minimize cost, and support service-level agreements. Many organizations are also under pressure to provide enterprise-quality service levels without paying enterprise prices. As a result, IT departments must implement cost-effective alternatives to proprietary cloud software and services. These alternatives need to include features such as data protection, disaster recovery, and guaranteed service levels. This solution enables customers to build an open-source cloud environment and validate the environment for performance, scalability, and functionality. With EMC storage solutions and Mirantis OpenStack, customers gain the following benefits: A virtual infrastructure that can be deployed quickly with Mirantis Fuel Reduced licensing and operating costs Compatibility with multiple hardware and software vendors Increased cloud solution portability and agility because of reduced dependence on proprietary systems 5

6 Technology solution This solution demonstrates how to use EMC storage systems, Mirantis OpenStack, and Cinder block storage drivers to provide the storage resources for a robust OpenStack environment. This solution incorporates the following components: EMC VNX EMC ScaleIO EMC XtremIO Mirantis OpenStack Juno release Mirantis Fuel Cinder drivers for EMC VNX and XtremIO (part of Juno release) Cinder drivers for EMC ScaleIO (available from EMC Support) 6

7 Solution architecture Architecture diagrams The diagrams in this section depict the architecture used to deploy Mirantis OpenStack with EMC storage systems and Cinder drivers. The deployment involves building an OpenStack environment and integrating it with VNX, XtremIO, or ScaleIO, as well as integrating the new features of these systems to provide a highperformance and cost-effective storage solution. Figure 1 depicts the overall physical architecture of the solution. Figure 1. EMC with Mirantis OpenStack reference architecture 7

8 Figure 2 depicts the network architecture of the solution. Figure 2. EMC with Mirantis OpenStack network architecture Hardware resources Table 1 lists the hardware used in this solution. Table 1. Solution hardware Hardware Quantity Connectivity Firmware version EMC VNX iscsi and FC 5.33 EMC XtremIO Generation 2 Cisco UCS B200 M2 Blade Server 1 iscsi and FC N/A N/A Brocade 6510 Switch 2 FC fabric v

9 Software resources Table 2 lists the OpenStack and cloud infrastructure software used in this solution. Table 2. OpenStack and cloud infrastructure software Software Version Description OpenStack Juno Open-source cloud computing software platform Mirantis Fuel 6.0 OpenStack deployment and management software CentOS 6.5 (kernel ) Operating system for the cloud environment KVM N/A Hypervisor in the CentOS kernel DM-Multipath N/A Multipathing software Table 3 lists the EMC storage software used in this solution. Table 3. EMC storage software Software Version Description EMC Unisphere Management software for VNX storage EMC Navisphere CLI (Linux x64) CLI for OpenStack Cinder driver EMC VNX Operating Environment EMC XtremIO Operating environment for VNX block storage Operating environment for XtremIO EMC ScaleIO 1.31 Software-defined storage Cinder block driver OpenStack Juno Block storage driver Storage protocols Table 4 lists the storage protocols used in this solution. Table 4. Storage protocols Protocol iscsi Fibre Channel EMC ScaleIO Data Client (SDC) Bandwidth 10 Gb Ethernet 8 Gb Fibre Channel Driver that exposes shared storage as a global block device, serving local I/O requests on each server 9

10 Key components Introduction VNX unified storage platform This section briefly describes the following key components used in this solution: EMC VNX storage platform EMC ScaleIO storage management EMC XtremIO flash array OpenStack cloud computing software platform The VNX family delivers a choice of systems ranging from affordable entry-level solutions to high-performance, petabyte-capacity configurations servicing the most demanding application requirements. The VNX family includes the following: The VNX series is designed to meet the high-performance, high-scalability requirements of midsize and large enterprises. It includes the VNX8000, VNX7600, VNX5800, VNX5600, VNX5400, and the VNX5200 systems. The VNXe series is designed for small- and medium-sized businesses. This entry-level series includes the VNXe3200 system. XtremIO flashbased storage platform ScaleIO storage management software OpenStack XtremIO is a scale-out clustered design that grows capacity and performance linearly to meet any requirement. XtremIO arrays are created from building blocks called X-Bricks that are each a high-availability, high-performance, fully active/active storage system with no single point of failure. The XtremIO arrays include the Starter X-Brick, 1 X-Brick, 2 X-Brick cluster, 4 X-Brick cluster, and 6 X-Brick cluster. ScaleIO is a software-only server-based storage area network (SAN) that combines storage and compute resources to form a single-layer, enterprise-grade storage product. ScaleIO storage is elastic and delivers linear scalable performance. Its scale-out storage architecture can grow from a few servers to thousands of servers. OpenStack is a cloud computing software platform that controls large pools of compute, storage, and networking resources in a data center, all managed through a dashboard that gives administrators control while enabling users to provision resources through a web interface. OpenStack supports several hypervisors, including KVM, and a wide range of hardware. 10

11 OpenStack technology overview Introduction OpenStack components OpenStack is a cloud computing software platform that controls large pools of compute, storage, and networking resources throughout a data center, all managed through a dashboard that gives administrators control while empowering their users to provision resources through a web interface. The following OpenStack components create a virtual computing environment. Compute (Nova) OpenStack Compute (Nova) is a cloud computing fabric controller. It is designed to manage and automate pools of computer resources and can work with widely available virtualization technologies as well as bare metal and high-performance computing (HPC) configurations. Compute can use several hypervisor technologies, including KVM. Nova's architecture is designed to scale horizontally on standard hardware with no proprietary hardware or software requirements and to integrate with legacy systems and third-party technologies. Object Storage (Swift) OpenStack Object Storage (Swift) is a scalable redundant storage system. Objects and files are written to multiple disk drives spread throughout servers in the data center, with the OpenStack software responsible for ensuring data replication and integrity across the cluster. You can scale storage clusters horizontally simply by adding new servers. If a server or hard drive fails, OpenStack replicates its content from other active nodes to new locations in the cluster. Because OpenStack uses software logic to ensure data replication and distribution across different devices, inexpensive commodity hard drives and servers can be used. Enterprise storage options include EMC Elastic Cloud Storage and the EMC Isilon platform. Both options provide storage that is compatible with Swift and that can be accessed using the Object Storage API. Block Storage (Cinder) OpenStack Block Storage (Cinder) provides persistent block-level storage devices for use with OpenStack compute instances. Block storage volumes are fully integrated into OpenStack Compute and the Dashboard, enabling cloud users to manage their own storage needs. VNX and XtremIO drivers are included with Cinder in the Juno release. In addition to local Linux server storage, OpenStack Block Storage can use storage platforms such as VNX, ScaleIO, and XtremIO. OpenStack Block Storage is appropriate for performance-sensitive scenarios such as database storage and expandable file systems, or providing a server with access to raw block-level storage. Snapshot management provides powerful functionality for backing up data stored on block storage volumes. Snapshots can be restored or used to create a new block storage volume. 11

12 Networking (Neutron) OpenStack Networking is a service for managing networks and IP addresses. OpenStack Networking ensures that the network is not a bottleneck or limiting factor in a cloud deployment, and gives users self-service capability, even over network configurations. OpenStack Networking provides networking models for different applications or user groups. Standard models include flat networks or VLANs that separate servers and traffic. OpenStack Networking manages IP addresses, allowing for dedicated static IP addresses or DHCP. Floating IP addresses let traffic be dynamically rerouted to any resources in the IT infrastructure, so users can redirect traffic during maintenance or in case of a failure. Users can create their own networks, control traffic, and connect servers and devices to one or more networks. Administrators can use software-defined networking (SDN) technology like OpenFlow to support high levels of multitenancy and massive scale. OpenStack Networking provides an extension framework that can deploy and manage additional network services such as intrusion detection systems, load balancing, firewalls, and virtual private networks. Dashboard (Horizon) OpenStack Dashboard (Horizon) provides administrators and users a graphical interface to access, provision, and automate cloud-based resources. The design accommodates third-party products and services, such as billing, monitoring, and additional management tools. OpenStack Dashboard is also brandable for service providers and other commercial vendors. OpenStack Dashboard is one of several ways users can interact with OpenStack resources. Identity Service (Keystone) OpenStack Identity Service (Keystone) provides a central directory of users mapped to the OpenStack services they can access. It acts as a common authentication system across the cloud platform and can integrate with existing back-end directory services like LDAP. It supports multiple forms of authentication including standard username and password credentials, token-based systems, and Amazon Web Services (AWS)-style logins. The Keystone catalog provides a queryable list of all of the services deployed in an OpenStack cloud in a single registry. Users and third-party tools can programmatically determine which resources can be accessed. Orchestration (Heat) Heat is a service to orchestrate multiple composite cloud applications using templates, through both a REST API that is native to OpenStack and a Query API that is compatible with AWS CloudFormation. Telemetry (Ceilometer) (optional when deploying Mirantis OpenStack) OpenStack Telemetry (Ceilometer) provides a single point of contact for billing systems, providing all the counters needed to establish customer billing, across all current and future OpenStack components. The delivery of counters is traceable and 12

13 auditable, the counters must be easily extensible to support new projects, and agents doing data collections should be independent of the overall system. Image Service (Glance) OpenStack Image Service (Glance) provides discovery, registration, and delivery services for disk and server images. Stored images can be used as a template. Image Service can also be used to store and catalog an unlimited number of backups. Image Service can store disk and server images in a variety of back ends, including OpenStack Object Storage. The Image Service API provides a standard REST interface for querying information about disk images and lets clients stream the images to new servers. Glance is the OpenStack Image Service module. It is a compute module, and it does not store images, variations, or instances. It catalogs them and holds their metadata from Swift or a storage back-end datastore. Other modules must communicate with the image s metadata through Glance. Also, Nova can present information about the images and configure a variation on an image to produce an instance. However, Glance is the only module that can add, delete, share, or duplicate images. Data Processing (Sahara) (optional when deploying Mirantis OpenStack) OpenStack Sahara enables users to provision Hadoop clusters by specifying parameters such as Hadoop version, cluster topology, and node hardware details. Sahara provides the means to scale an already-provisioned cluster by adding or removing worker nodes on demand. Sahara provides the following: Fast provisioning of Hadoop clusters on OpenStack for development and QA Utilization of unused compute power from a general-purpose OpenStack infrastructure-as-a-service cloud Analytics as a service for ad-hoc or bursty analytic workloads The data processing capability introduced in the Juno release automates provisioning and management of big data clusters using Hadoop and Spark. Big data analytics are a priority for many organizations and a popular use case for OpenStack, and this service lets OpenStack users provision resources more quickly. Catalog service (Murano) (optional when deploying Mirantis OpenStack) Murano is an application catalog for OpenStack. It enables application developers and cloud administrators to publish various cloud-ready applications in a browsable and categorized catalog. Cloud users can use the catalog to easily create reliable application environments. CentOS Community Enterprise Operating System (CentOS) is a Linux distribution that provides a free, enterprise-class, community-supported computing platform that aims to be functionally compatible with its upstream source, Red Hat Enterprise Linux (RHEL). In January 2014, the CentOS Project announced the official joining of CentOS with Red Hat, while staying independent from RHEL under a new CentOS governing board. 13

14 Requirements This section outlines specific requirements that must be met before Mirantis OpenStack can be used with EMC storage solutions. Refer to the Mirantis OpenStack version 6.0 Planning Guide for Mirantis OpenStack and Fuel system requirements. Server and networking requirements The server hardware and networking requirements for this OpenStack solution comply with the EMC Simplified Support Matrix. The solution currently supports only IPv4. IPv6 has not been tested. This solution uses standard EMC-supported storage system connectivity options, including the following: Management interface: 10 Gb Ethernet iscsi storage network: 10 Gb Ethernet 8 Gb/s Fibre Channel VNX requirements The use of iscsi requires network connectivity from all OpenStack controller and compute nodes to the VNX management network and the VNX iscsi network. You must configure VNX storage and storage pools using EMC Unisphere or Naviseccli. You must manually register host iscsi and FC initiators on the VNX unless the cinder.conf configuration file specifies automatic host initiator registration. iscsi requirements The iscsi-initiator-utils package is not installed on OpenStack controller nodes during the Mirantis OpenStack deployment. Certain Cinder functions require iscsi-initiatorutils on OpenStack controllers. 1. Type the following command to install the iscsi initiator utils package: yum -y install iscsi-initiator-utils Additional packages are required to enable VNX iscsi device multipathing. Do the following to configure an environment for iscsi multipathing: 2. Download and install each of the following packages from device-mapper-multipath-libs el6.x86_64.rpm kpartx el6.x86_64.rpm device-mapper-multipath el6.x86_64.rpm 3. Ensure the following value is set in the libvirt section of nova.conf on all compute nodes: iscsi_use_multipath = True Fibre Channel requirements For FC connections, all controller and compute nodes must have zoning entries to the required ports on the VNX array unless the OpenStack Brocade FC Zone Manager is being used. The Brocade FC Zone Manager enables automatic FC zoning of hosts from 14

15 OpenStack. To enable use of FC LUNs with Cinder, install additional required packages as follows: 1. Type the following command to install the required packages for FC: yum install sysfsutils sg3_utils 2. Verify that libaio is installed on each node. If it is not, install it by typing the following command: yum install libaio 3. Download and install each of the following packages from device-mapper-multipath-libs el6.x86_64.rpm kpartx el6.x86_64.rpm device-mapper-multipath el6.x86_64.rpm XtremIO requirements Network connectivity is required from the OpenStack controller and compute nodes to both the XtremIO management network and, in the case of iscsi, from the XtremIO iscsi network. iscsi requirements XtremIO deployments using iscsi require manual installation of the iscsi-initiatorutils package on all OpenStack controller nodes following the deployment of the OpenStack environment. 1. Type the following command to install the iscsi initiator utils package: yum -y install iscsi-initiator-utils Additional packages are required to enable device multipathing with iscsi. Do the following to configure an environment for iscsi multipathing: 2. Manually download and install each of the following packages from device-mapper-multipath-libs el6.x86_64.rpm kpartx el6.x86_64.rpm device-mapper-multipath el6.x86_64.rpm 3. Ensure the following value is set in the libvirt section of nova.conf on all compute nodes: iscsi_use_multipath = True Fibre Channel requirements For FC connections, all controller and compute nodes must have zoning entries to the required ports on the XtremIO array. To enable use of FC LUNs with Cinder, install additional required packages as follows: 1. Type the following command to install the required packages for FC: 15

16 yum install sysfsutils sg3_utils 2. Verify that libaio is installed on each node. If it is not, install it by typing the following command: yum install libaio 3. Download and install each of the following packages from device-mapper-multipath-libs el6.x86_64.rpm kpartx el6.x86_64.rpm device-mapper-multipath el6.x86_64.rpm Multipath requirements Multipath requirements apply to VNX and XtremIO for both FC and iscsi protocols. For all OpenStack nodes where native Linux multipathing software is installed, specify the following in the /etc/multipath.conf file so that Cinder volume attach and detach commands function correctly: defaults { user_friendly_names no flush_on_last_del yes } ScaleIO requirements In this architecture, the ScaleIO management components, including ScaleIO Meta Data Manager, Callhome, Tie-Breaker, and Gateway, are installed on the OpenStack controller nodes. The ScaleIO Data Server (SDS) and ScaleIO Data Client (SDC) components are installed on all OpenStack compute nodes. Additionally, the ScaleIO SDC component must be installed on all OpenStack controller nodes for Cinder operations such as Copy Image to Volume. ScaleIO SDS nodes require dedicated local storage, either hard-disk drives or flash drives, to provide SDS storage for the ScaleIO cluster. An additional package is required on all hosts to enable the use of ScaleIO volumes with Cinder. Type this command to install the required package for ScaleIO: yum install sysfsutils Note: Ensure that the dedicated disks for ScaleIO SDS storage are not selected by Fuel during OpenStack deployment. EMC recommends using dual 10 GbE networks for all ScaleIO deployments. When deploying ScaleIO with Mirantis OpenStack, ensure that both 10 GbE networks are being used for ScaleIO to ensure optimal ScaleIO performance. For all other ScaleIO requirements, refer to the EMC ScaleIO V1.31 User Guide. The Cinder drivers for ScaleIO are not included in the Mirantis OpenStack distribution and must be obtained from EMC. Obtain the ScaleIO software packages and Cinder driver files from EMC Online Support. Refer to the EMC ScaleIO V1.31 User Guide for instructions on installing and configuring ScaleIO in an OpenStack environment. 16

17 Note: If you plan to use the scaleio_install.py installation script for the Cinder driver for ScaleIO, download and install the Python ConfigObj config file reader and writer with this command: pip install configobj OpenStack requirements This architecture is designed to be used with Mirantis Fuel 6.0 and OpenStack Juno running on CentOS 6.5. Dedicated Cinder nodes are not required and should not be specified during the deployment of OpenStack nodes when Cinder block storage is being provided by VNX, XtremIO, or ScaleIO. This architecture supports only the default Cinder option in the Mirantis Fuel environment setup. The architecture does not support Ceph. Cinder drivers for both VNX and XtremIO are installed as part of the OpenStack deployment with Mirantis Fuel. ScaleIO drivers are not installed with the Mirantis OpenStack deployment and must be obtained from EMC Online Support. 17

18 Installation Refer to the following Mirantis OpenStack guides for the latest detailed information for deploying and configuring OpenStack in your environment: Mirantis OpenStack version 6.0 Planning Guide Mirantis OpenStack version 6.0 User Guide Mirantis OpenStack version 6.0 Operations Guide Server hardware preparation Prepare server hardware as detailed in the Mirantis OpenStack guides. Additional steps for VNX and XtremIO include verifying network connectivity to the array s management network and, where iscsi is being used, to the array s iscsi network. For FC, all nodes must have physical access to the FC fabric. Fabric setup describes additional FC requirements. The requirements specified in Network preparation and Fabric setup are the same for both VNX and XtremIO. Network preparation The Mirantis OpenStack guides detail the physical and virtual network preparation. This architecture uses OpenStack tenant VLANs. Follow these guidelines: When deploying OpenStack environments with VNX or XtremIO arrays, ensure that all nodes are assigned an address on the public network in the Mirantis Fuel deployment settings. In the case of either XtremIO or VNX, network connectivity is required from all OpenStack nodes to the management network of the VNX or XtremIO array. For iscsi on either VNX or XtremIO, network connectivity is required from all OpenStack nodes to the iscsi network or networks on the VNX or XtremIO array. Fabric setup Mirantis Fuel installation OpenStack controller node deployment FC zoning entries are required between all nodes and the VNX or XtremIO arrays unless the Brocade FC Zone Manager for OpenStack is configured. The Brocade FC Zone Manager provides automatic host-to-array zoning for both OpenStack controller and compute nodes. Refer to the Mirantis OpenStack version 6.0 Planning Guide and the Mirantis OpenStack version 6.0 User Guide for Mirantis Fuel installation steps. Dedicated Cinder nodes are not required and should not be specified during the deployment of OpenStack nodes when Cinder block storage is being provided by VNX, XtremIO, or ScaleIO. Refer to the Mirantis OpenStack version 6.0 Planning Guide and the Mirantis OpenStack version 6.0 User Guide for controller node deployment steps. For VNX and XtremIO configuration, all nodes must have a public network address assigned during configuration of the OpenStack environment. Only the Multi-Node HA deployment, which is the recommended deployment option, was tested with Mirantis OpenStack. 18

19 Note: A simple deployment should also work, but that deployment was not tested. OpenStack compute node deployment Refer to the Mirantis OpenStack version 6.0 Planning Guide and the Mirantis OpenStack version 6.0 User Guide for controller node deployment steps. For VNX and XtremIO configuration, all compute nodes must have a public network address assigned during configuration of the OpenStack environment. 19

20 Configuration This section includes links to specific configuration steps required to enable Cinder drivers for VNX, XtremIO, and ScaleIO. VNX The Cinder driver for VNX is installed as part of the Mirantis OpenStack deployment process. For VNX Cinder driver requirements and configuration steps, refer to the EMC VNX direct driver guide for Juno. Figure 3 shows the VNX with iscsi deployment architecture. Figure 3. VNX with iscsi deployment architecture 20

21 Figure 4 shows the VNX with Fibre Channel deployment architecture. Figure 4. VNX with Fibre Channel deployment architecture The VNX Cinder driver provides support for all operations outlined in Table 5. The driver also offers support for the following features: Cinder volume support for VNX Fully automated Storage Tiering (FAST) Cinder volume support for VNX Fast Cache Creation of thin, thick, compressed, and deduplicated volumes Note: OpenStack Cinder support for deduplicated volumes will be available in VNX Block Operating Environment Storage-assisted volume migration Creation of read-only Cinder volumes Multiple back ends Multiple VNX storage pools Fibre Channel auto-zoning XtremIO The Cinder driver for XtremIO is installed as part of the Mirantis OpenStack deployment process. You can find XtremIO Cinder driver requirements and configuration steps in the EMC XtremIO OpenStack Block Storage driver guide for Juno. 21

22 Figure 5 shows the XtremIO with iscsi deployment architecture. Figure 5. XtremIO with iscsi deployment architecture Figure 6 shows the XtremIO with Fibre Channel deployment architecture. Figure 6. XtremIO with Fibre Channel deployment architecture 22

23 XtremIO offers native thin-provisioned volumes, inline data compression, data deduplication, and full support for multiple Cinder back ends. Table 5 lists all supported Cinder commands. ScaleIO ScaleIO can be deployed in an existing Mirantis OpenStack environment using the OpenStack controller and compute nodes. Servers that provide ScaleIO SDS require additional local disks. Mirantis assigns the first disk in each node as the operating system disk by default. Any other local hard-disk drives can be used for SDS storage. For ScaleIO driver requirements and configuration steps for OpenStack, refer to the EMC ScaleIO V1.31 User Guide. You can configure ScaleIO to run on the existing networks that are created by Mirantis Fuel during the environment deployment. For optimal performance, EMC recommends using dual 10 GbE networks with ScaleIO. Figure 7 shows the ScaleIO deployment architecture. Figure 7. ScaleIO deployment architecture In addition to the Cinder functions outlined in Table 5, ScaleIO offers the following Cinder functionality: Native data obfuscation Support for multiple protection domains and storage pools Creation of thick and thin-provisioned Cinder volumes Cinder high availability You can achieve high availability for Cinder drivers only if you deploy a Multi-Node with HA OpenStack environment. In this case, Cinder management services are installed on each controller and provide high availability in case of a controller reboot or loss. Mirantis HA does not, however, provide HA for Cinder volumes. If a controller is lost, volumes that are owned by that controller can still be used for user application I/O but cannot be modified through Cinder actions such as snapshot, detach, delete, and clone. 23

24 Managing storage volumes The Mirantis OpenStack version 6.0 Operations Guide and the OpenStack Admin User Guide provide the latest detailed information for managing storage volumes in your environment. Table 5 summarizes supported volume operations for each platform. Table 5. Cinder volume operations for OpenStack Juno VNX XtremIO ScaleIO Create Cinder volume Create Cinder volume Create Cinder volume List Cinder volumes List Cinder volumes List Cinder volumes Delete Cinder volume Delete Cinder volume Delete Cinder volume Snapshot Cinder volume Snapshot Cinder volume Snapshot Cinder volume List volume snapshots List volume snapshots List volume snapshots Delete volume snapshots Delete volume snapshots Delete volume snapshots Attach volume Attach volume Attach volume Detach volume Detach volume Detach volume Create volume from snapshot Create volume from snapshot Create volume from snapshot Copy image to volume Copy image to volume Copy image to volume Copy volume to image Copy volume to image Copy volume to image Clone volume Clone volume Clone volume Extend volume Extend volume Extend volume Configure multiple storage back ends Configure multiple storage back ends Migrate volume Retype volume Get volume stats Create Cinder volume consistency groups Delete Cinder volume consistency groups Create Cinder consistency group snapshots List Cinder consistency group snapshots Delete Cinder consistency group snapshots 24

25 Support Refer to the EMC Simple Support Matrices for links to tables of hardware and software supported by EMC products. For support for EMC with OpenStack environments, you can use TSANet.org. TSANet allows companies to transfer support cases without a support agreement. Contact EMC Online Support for issues with EMC storage solutions. Contact Mirantis support for issues with Mirantis OpenStack. 25

26 Conclusion Reducing IT operational expenditures while simultaneously increasing the level of security and software capabilities is a top priority for many companies. Cost, security, reliability, and ease of use are often key considerations when an enterprise evaluates new technology solutions. OpenStack provides inexpensive and flexible storage and virtualization software. Using OpenStack with EMC storage solutions enables IT organizations to meet or exceed their needs to save money and maintain secure and reliable service with a storage system that is both easy to deploy and manage. With Mirantis OpenStack and EMC storage solutions, customers realize the following benefits: Decreased costs associated with environment scalability More choices in supported hardware Greater flexibility in cloud migration Lower operational and maintenance costs 26

27 References EMC documentation Mirantis documentation OpenStack documentation The following documents, located on the EMC.com, provide additional and relevant information. Access to these documents depends on your login credentials. If you do not have access to a document, contact your EMC representative: Introduction to the EMC VNX2 Series: VNX5200, VNX5400, VNX5600, VNX5800, VNX7600, & VNX8000 A Detailed Review EMC Unisphere: Unified Storage Management Solution for the New VNX Series: VNX5200, VNX5400, VNX5600, VNX5800, VNX7600, and VNX8000 A Detailed Review EMC VNX2 FAST VP VNX 5200, VNX 5400, VNX5600, VNX5800, VNX7600, & VNX8000 A Detailed Review EMC VNX2 Multicore FAST Cache: VNX5200, VNX5400, VNX5600, VNX5800, VNX7600, & VNX8000 A Detailed Review EMC VNX2 Deduplication and Compression: VNX5200, VNX5400, VNX5600, VNX5800, VNX7600, & VNX8000 Maximizing effective capacity utilization Solution Overview: EMC ScaleIO For Development and Testing Solution Overview: EMC ScaleIO For High-Performance Computing Introduction to the EMC XtremIO Storage Array A Detailed Review The following Mirantis documents, located on the Mirantis website, also provide useful information: Mirantis OpenStack version 6.0 Planning Guide Mirantis OpenStack version 6.0 User Guide Mirantis OpenStack version 6.0 Operations Guide Mirantis OpenStack version 6.0 Reference Architecture The following OpenStack documents, located on the OpenStack website, also provide useful information: OpenStack Installation Guide for Red Hat Enterprise Linux 7, CentOS 7, and Fedora 20 OpenStack High Availability Guide OpenStack Security Guide 27