Home

Using XIV in OpenStack Environments

1. SCSI xiv Other gt OpenStack IBM Storage Driver nodes and for OpenStack infrastructure on Cinder nodes or FC XIV DS8000 IBM Storage System Private network IBM System Storage DS8000 or IBM XIV Storage System t __ Storage resources OpenStack cloud environment a Storage pools LUNs inside the IBM storage system Figure 2 1 OpenStack cloud environment with IBM storage systems The OpenStack software can be installed on multiple supported Linux platforms For more information see the OpenStack website http docs openstack org 2 2 OpenStack installation 14 To successfully implement and test the OpenStack cloud environment by using the IBM Storage Driver for OpenStack follow these steps 1 Install a supported Linux distribution on every node for example any server that is connected to the network where a Nova component will be installed 2 Configure separate networks a management network a storage network and a service network for public access to cloud services 3 Install Network Time Protocol NTP to synchronize OpenStack services across multiple machines Using XIV in OpenStack Environments 4 Configure security as necessary for the cloud environment for example passwords policies and encryption Install and configure a supported database to store credentials and centralized items Install and configure th
2. All Projects gt Owner AllUsers gt vb 00 P xX More Instance Status Cloud Project ITSO cloud2 test BZ ox itso cloud ITSO cloud P41 ITSO boot test A ox itso cloud ITSO cloud P1 RH Bok itso cloud ITSO_project RHEL70 A ox itso cloud Public Windows 10 IE Stopped itso cloud Public cirros instan Ase itso ctoud ox itso cloud Public test for itso ctoud project ubuntu ox itso cloud Public Owner Administrator Administrator Administrator Administrator Administrator Administrator Administrator Administrator Administrator Figure 4 16 Instance view 4 2 4 Creating and attaching a volume to an instance To create a volume from IBM Cloud Manager you need to enable a supported storage system for Cinder on the Cinder node and define it in OpenStack Manager see 3 1 1 Preparing the XIV for OpenStack on page 25 To create a volume click Volumes Click the Create volume icon as highlighted in Figure 4 17 You are in Volumes Cloud itso cloud v Project All Projects a R More Name a Status Project Size GB Type Sttached VM cirros vol Posailable Public 20 XIV_G3_volurr itso_volume_3 In use Public 34 IBMEXI 9 155 Attached to cirros_instance on fdevivdd test Available Public 1 xiv test test2 Available Public 1 xiw test_2 In use Public 34 IBMEXI Y 9 155 Attached to cirros_instance on dev rde ubuntu_wol_2 Available Public 51 XI v_G3_wolurr uburtu volume Porailable Public 34 xiv X
3. This example shows a view of the current projects A user can add a project by clicking Create Project The Create Project window opens as shown in Figure 2 6 The administrator needs to complete the information in three tabs to create the project Create Project Project Info Name j From here you can create a new project to organize users itso project3 Description Enabled Cancel Create Project Figure 2 6 Create Project window Chapter 2 OpenStack environment 21 22 Using XIV in OpenStack Environments Integrating the XIV in the OpenStack environment This chapter highlights the steps to integrate the IBM XIV Storage System into a new OpenStack environment O Copyright IBM Corp 2015 All rights reserved 23 3 1 Integrating the XIV in the OpenStack environment Cinder is the block storage component of the OpenStack storage domain Cinder supports creating attaching and detaching block devices snapshots cloning and backups Both the IBM XIV and DS8000 storage systems are supported beginning with the Havana release of OpenStack by using the IBM Storage Driver for OpenStack Figure 3 1 illustrates how the Cinder driver functions within the OpenStack environment OpenStack Create volume E placement t t capabilities i Cinder driver Cinder driver High performance High capacity Figure 3 1 OpenStack storage flow IBM has enabled Cinder and H
4. With 2 GB RAM you can run one m1 small instance on a node or three m1 tiny instances without memory swapping so 2 GB RAM is the minimum for a test environment compute node Specifically for virtualization on certain hypervisors on the node or nodes running nova compute you need a x86 machine with an AMD processor with SVM extensions also called AMD V or an Intel processor with virtualization technology VT extensions Figure 2 2 on page 18 illustrates an example environment setup with a single node that is connected over Fibre Channel or iSCSI to the XIV Chapter 2 OpenStack environment 17 Nova Single Node Controller Volume Network Compute Node IBM Storage Driver for OpenStack iSCSI attachment Nova Single Node Controller Volume Network Compute Node IBM Storage Driver for OpenStack XQ Fibre Channel Attachment IP 1 XIV Figure 2 2 Nova single node Notice in this illustration in Figure 2 2 that the IBM Storage Driver for OpenStack is installed only on the iSCSl attached node The driver can also be installed on a Fibre Channel attached node Figure 2 3 is another example of a more complex configuration with multiple nodes that are configured over IP and SAN Compute Node Compute Node IBM Storage Driver for OpenStack Storage Node all Storage Node Compute Node Compute Node IBM Storage Driver for OpenStack External Network Controller Nod
5. Select one y Select one Linux 64 bitx86_64 Windows 64 bit x86 z VM All Figure 4 1 IBM Cloud Manager with OpenStack installation files from Fix Central The following prerequisites are necessary for the IBM Cloud Manager with OpenStack installation gt Hardware requirements for the deployment server as listed in Table 4 1 Also the deployment server can be based on a virtual system In our setup we used a physical server Table 4 1 IBM Cloud Manager with OpenStack deployment server requirements Component Minimum hardware Recommended minimum requirements hardware production requirements IBM Cloud Manager with Four CPUs Eight CPUs OpenStack deployment server Free disk space 4 GB for 25 GB free disk space opt ibm cmwo gt 8 GB physical memory Free disk space 4 5 GB of temporary space while installing Chef Server 5 0 GB of free disk space in opt 5 0 GB of free disk space in var 4 GB physical memory Chapter 4 IBM Cloud Manager with OpenStack 33 34 We installed RHEL 6 5 64 bit x86 same as for OpenStack nodes with the minimum installation as used in our setup without the graphical user interface GUI We performed a command line installation We downloaded the IBM Cloud Manager with OpenStack installation packages including the latest service packs and documentation Each node system must have at least two network adapters one network adapter for the date and the other
6. gt Hame rhs Description Image hypervisor type qemu UUID 89dd09d7 36b0 4341 9ce6 dbs1 esObf20b Cloud itso cloud Project Public Disk format QACOW2 Container format OVF Minimum memory MB 2000 Minimum storage GB 20 Base image Yes Owner System Last modified Mon 3 31 PM Version Revision Revision comments Additional Properties 2 Related Images None Log Entries None Close Figure 4 14 Parameters for deploying an image to a VM Name the new instance and click Deploy again You can deploy more than one instance simultaneously if needed The Flavor selection determines the amount of hardware resources that the new instance virtual machine can use Figure 4 15 on page 58 Chapter 4 IBM Cloud Manager with OpenStack 57 Deploy rhs Choose the settings to be applied when the image is deployed Deploy Save as Draft Name rhs Description Project Public New Project Instances max 5 1 a Hardware System OpenStack Flavor Flavor mi medium Flavor details Virtual CPUs 2 Memory MB 4096 Storage GB 40 Swap MB Extra Specifications None Figure 4 15 Choose the settings to be applied when the image is deployed After the instance is deployed the instance shows under the Instance view as illustrated in Figure 4 16 58 Using XIV in OpenStack Environments Cloud All Clouds Project
7. gt Network node One processor 512 MB memory and 5 GB storage gt Compute node One processor 2 GB memory and 10 GB storage You can create this minimal environment with virtual machines VMs and then use this environment to become familiar with the OpenStack environment as well for testing purposes Important Remember that this hardware reference is for a simple environment and the number of VMs or instances that can be deployed will depend on the hardware configuration Using XIV in OpenStack Environments Table 2 1 OpenStack hardware recommendations Nova component Cloud controller node runs network volume API scheduler services and image services Compute nodes run virtual instances Supported 64 bit Linux version CentOS Debian Fedora RHEL openSUSE SLES and Ubuntu Processor 64 bit x86 Memory 12 GB RAM Disk space 30 GB Serial Advanced Technology Attachment SATA serial attached SCSI SAS or solid state drives SSD Volume storage Two disks with 2 TB SATA for volumes that are attached to the compute nodes Network One 1 Gbps network interface card NIC Supported 64 bit Linux version CentOS Debian Fedora RHEL openSUSE SLES and Ubuntu Processor 64 bit x86 Memory 32 GB RAM Disk space 30 GB SATA Network Two 1 Gbps NICs Two NICs are recommended but they are not required A quad core server with 12 GB RAM is more than sufficient for a cloud controller node
8. 1 0 17 GB volume 7d1d0d7b 153 429a aaf3 1102168586ce no d 20 0 34GB A A A 1 volume 8f863667 754f 427c b326 1bb7fb068ecb no d 34 0 34GB volume 98069b74 b374 4447 87c3 c57624a8af5b no d 10 0 17 GB volume 9812c7ed 9961 4745 90f8 29a03d3d680e no d 34 0 34GB volume a8513757 fa60 458a af39 95733e470e3d no d 34 0 34 GB Figure 4 19 Volume created in the XIV pool The created volume is also mapped to the OpenStack cluster as shown in Figure 4 20 Using XIV in OpenStack Environments LUN Mapping for volume 7fbbfb8f 0d53 4339 a25a cbbc309afd26 LUN Host Cluster 105 openstack controller mainz ibm com Figure 4 20 Mapped volume in the XIV GUI The new volume shows in the list of volumes Select Attach to attach it to an instance as illustrated in Figure 4 21 on page 61 Cloud itso cloud Project All Projects 2 ES More Capture Name Attach Status Detach Error ITSO_XIV_PFE2_vol_4 In use RHEL65 xivboot Available Win 20GB Available admin_xiv_PFE2_volume_1 Available boot test RHEL In use cirros vol In use tso volume 3 Available itso volume 4 Available iv rhs volume In use Project admin ITSO project admin Public admin ITSO cloud P4 Public Public Public Public Size GB 34 34 20 20 34 20 20 34 34 4 Type None IBM XIV_9 4 IBM XIV_9 4 xiv IBM XIV_9 4 XIV_G3_volt XIV_G3_wolt IBM XIV_9 4 IBM XI _9 4 xiv Attache
9. 4 4 4 volume a8513757 fa60 458a af39 95733e470e3d 7899 1340010 openstack controller mainz ibm com 34 4 4 4 volune 6f9a7749 a7c2 4292 a12a ad6cc3b375f5 9271 1340010 openstack controller mainz ibm com 34 4 4 4 volune 8f863667 754f 427c b326 1bb7fb068ecb 1151 1340010 openstack controller mainz ibm com Paths NA In Example 3 2 notice the three volumes on the XIV system ID 1340010 with four paths to each volume After the HAK installation completes you are ready to configure a storage pool for the OpenStack environment on the XIV Tip Configure the host where the compute and controller nodes exist to include multi pathing Note When volumes are created with OpenStack on the back end storage the XIV the new volumes appear in the xiv_devlist command output Tip If the xiv_devlist command stops it is easy to recover by restarting the multipathd with the service multipathd restart command 3 1 3 Installing IBM Storage Driver for OpenStack You can download the available version of IBM Storage Driver for OpenStack from the following website http pic dhe ibm com infocenter strhosts ic topic com ibm help strghosts doc nov a homepage html You can download the installation guide which is available in PDF format from the following website http pic dhe ibm com infocenter strhosts ic index jsp topic 2Fcom ibm help strg hosts doc 2Fnova homepage html The current IBM Storage Driver for OpenStack offers the following features gt
10. 6 Inthe topology repository that we used the self service portal was added on the controller node NODE1_HOSTNAME to the example topology that is shown in Example 4 11 7 Example 4 12 shows that the customized topology repository was applied to the configuration Chapter 4 IBM Cloud Manager with OpenStack 39 Example 4 12 Customized topology repository root deployment server itso cloud cat itso cloud topology json name itso cloud_ topology description itso cloud topo environment itso cloud env run_sequentially false nodes fqdn openstack controller mainz ibm com password lt Password gt quit on error true run order number 1 runlist role ibm os allinone kvm role ibm sce node ks fqdn openstack compute mainz ibm com password lt Password gt quit on error true run order number 2 runlist role ibm os compute node kvm root deployment server itso cloud 8 The topology json file repository is easier to use to customize the environment repository Example 4 13 is an example of our environment json file which requires a minimum customization Example 4 13 Customization of the example environment json configuration file root deployment server itso cloud cat itso cloud environment json name itso cloud env lt please customize description Environment for the IBM OpenStack single control
11. 90 ITSO CM PFEZ P1 fibre channel san login your login ID volume driver cinder volume drivers xiv ds8k XIVDS8KDriver xiv ds8k proxy xiv ds8k openstack xiv nova proxy XIVNovaProxy san ip your IP xiv chap disabled Example 3 4 shows the installation process for the test environment that was used for this paper We used Version 1 3 1 1 b261 to install the driver for an XIV system The storage pool to use with the OpenStack environment was previously created and defined for OpenStack during the installation with this script ITSO CM XIVO2 P1 Notice that you can install more than one back end storage device for this driver it is an XIV or the DS8000 with this installation script Also the driver is installed from the OpenStack controller node Example 3 4 Installing the IBM Storage Driver for OpenStack root openstack controller IBM Storage Driver_for_OpenStack_1 3 1 1 b261_rhel6 x install sh Welcome to the IBM Storage Driver for OpenStack v1 3 1 1 b261 installation Press ENTER to proceed Enter the storage array type x xiv for XIV or d ds8k for DS8000 Default x x Enter the IBM XIV Storage System IP address or hostname 9 155 50 90 Enter the username and password for accessing the IBM XIV Storage System Username Default admin itso Password Please specify the required connection type f fc fibre for Fibre Channel or i iscsi for iSCSI Default i f Enter the name of the XIV storage pool to be used
12. B The Nova Node 1 will communicate via the Cinder API over the IP network to the XIV to issue commands such as volume creation snapshots and mapping that are restricted to XIV Domain B Chapter 1 OpenStack and IBM Cloud Manager overview 9 OpenStack Domain Admin Nova Node 2 Figure 1 6 XIV multi tenancy in an OpenStack environment 1 4 IBM Cloud Manager with OpenStack IBM Cloud Manager with OpenStack provides unique additional components to OpenStack which include supporting an enterprise database db2 as an alternative to MYSQL and additional targets including IBM PowerVM IBM z VM and HyperV IBM Cloud Manager is designed to simplify the deployment and management of cloud environments It also hides the underlying infrastructure from the user and shifts the focus to the services that are delivered by the cloud 1 4 1 What is IBM Cloud Manager 10 IBM Cloud Manager is a cloud management solution that is designed to be easy to deploy and simple to use It features a self service portal for balanced provisioning of VMs instances as well as virtualized image management IBM Cloud Manager includes support for deploying resizing and capturing the cloud environment Reporting is available for billing and metering of the individual users in a public cloud as well as the projects tenants of a private cloud It includes author approval policies that require the cloud administrator to approve
13. Create or delete a volume in the XIV Storage System gt Attach an XIV Volume to or detach an XIV Volume from a VM and make the volume accessible via iSCSI or Fibre Channel attachment The iSCSI qualified name IQN is created automatically on the XIV Storage System gt Create a snapshot of a volume Chapter 3 Integrating the XIV in the OpenStack environment 27 28 To install the IBM Storage Driver for OpenStack create a pool on the XIV Storage System for the node In our example we created a pool that is named ITSO CM PFEZ P1 For the driver installation you need the XIV IP address admin name and password To install the IBM Storage Driver for OpenStack see the driver installation guide http pic dhe ibm com infocenter strhosts ic index jsp topic 2Fcom ibm help strg hosts doc 2Fnova homepage html Verify that the IBM Storage Driver for OpenStack is installed correctly by checking the cinder conf file as shown in Example 3 3 In the storage area network SAN parameters you must set the volume driver to cinder volume drivers xiv_ds8k XIVDS8KDriver and the xiv_ds8k_proxy must be set to xiv ds8k openstack xiv nova proxy XIVNovaProxy Example 3 3 The XIV cinder conf stanza for IBM Storage Driver cat etc nova cinder conf IBM XIV 9 155 50 90 ITSO CM PFEZ P1 fibre channel xiv ds8k connection type fibre channel san clustername ITSO CM PFEZ P1 san password YWRtaW5hZG1pbg volume backend name IBM XIV 9 155 50
14. Define policies at the applied when images are deployed project level for additional customization JE Manage Images Manage Instances E Deploy import and customize images Monitor resize and de provision virtual LEl machines Manage Requests a View Activity Reports o Review and approve requests for new El View recent events for cloud resources instances and other actions Figure 4 8 Welcome panel Enter a name for the cloud to manage and choose the type The type of cloud can be OpenStack or VMware In our case we select OpenStack Define a user and password for this cloud and click Add See Figure 4 9 on page 53 Note The cloud configuration can be divided into administrative unit projects which are also known as tenants 52 Using XIV in OpenStack Environments Add Cloud Configuration Name itso Description Type ppenstad v Region RegionOne Qpid Settings Host name itso cloud2 Port 5671 vV Secure the cloud connection using SSL User ID admin Password Confirm password sn nan Cloud timeout minutes 4 a Test Connection Add Cancel Figure 4 9 Cloud configuration parameters 4 2 2 Importing an image Next import an image of a virtual machine or ISO image The ISO image will be used to install an operating system on an attached volume You can download prepared VMs from this website http docs openstack org image guide content ch_obta
15. a z VM system For more information see z VM prerequisites at this website http www ibm com support knowledgecenter SST55W 4 2 0 liaca liacazvm prerequi sites html 4 1 2 Installing IBM Cloud Manager with OpenStack 32 A broad range of documentation is available about the installation of IBM Cloud Manager A quick installation guide helps you to set up a test or evaluation environment rapidly Also detailed documents are provided in which specific sections such as security or the installation of various supported host operating systems are described in detail The documentation and other useful information are available on the IBM developerWorks website https www ibm com devel operworks community wikis home 1ang en wiki W2led5ba0f4 a9 46f4 9626 24cbbb86fbb9 page Documentation The quick installation guide is also at the IBM developerWorks website under the IBM Cloud Manager with OpenStack documentation http ibm co 1lAaiQta Using XIV in OpenStack Environments You can download the installation packages and fix packs from the IBM Fix Central product gateway as shown in Figure 4 1 See Figure 4 1 Find product Select product Select the product below When using the keyboard to navigate the page use the Alt and down arrow keys to navigate the selection lists Product Group Other Software Select from Other Software Cloud Manager with Openstack Installed Version 4103 x Platform
16. com was successful Results for nodes with run order number 2 Deploy of node at openstack compute mainz ibm com was successful Deploy of topology itso cloud_topology json completed in 292 seconds root deployment server itso cloud Using XIV in OpenStack Environments root deployment server knife node list openstack compute mainz ibm com openstack controller mainz ibm com root deployment server After the installation completes successfully you can use the Cloud Management Dashboard web interface on the controller node for cloud operations Assuming that the nodes are defined within a DNS or in etc hosts you can start the GUI interface in a browser by using the fully qualified name FQN https openstack controller mainz ibm com Or you can use the IP address of the controller node https 9 155 51 210 The Cloud Management Dashboard login panel opens as shown in Figure 4 2 Cloud Management Dashboard User Name Password opensta Licensed Materials Property of IBM Corp 5765 SKC Copyright IBM Corp 2010 2014 All Rights Reserved O Copyright 2014 OpenStack Foundation and others Figure 4 2 Cloud Management Dashboard login after deployment Enter the default user credentials User name admin Password admin If you don t see the Cloud Management Dashboard login an issue likely exists with the firewall Review the firewall settings on the controller and compute
17. configure the cloud that IBM Cloud Manager will manage IBM Cloud Manager can manage multiple clouds of different kinds such as VMware and OpenStack but also z VM and PowerKVM are supported through OpenStack technologies This section describes how to configure IBM Cloud Manager and how to deploy virtual machine instances and then how to attach external XIV storage to the created virtual machine instance with IBM Cloud Manager Chapter 4 IBM Cloud Manager with OpenStack 51 4 2 1 Configuring IBM Cloud Manager to manage a cloud Log in to the IBM Cloud Manager server lt ip address gt 18080 cloud web login htm1 Use your provided credentials Configure a cloud to manage with IBM Cloud Manager Select Configure the Cloud from the Welcome panel as shown in Figure 4 8 Note Multiple clouds can be configured and managed with IBM Cloud Manager IBM Cloud Manager with Ope Welcome S s volumes Images ss Configuration You are in Welcome Welcome to IBM Cloud Manager with OpenStack IBM Cloud Manager with OpenStack enables users to provision virtual machines quickly while an administrator maintains oversight of the managed envi an action to get started onfigure the Cloud q Manage Cloud Access dia Enable one or more cloud environments pa Configure projects and users forthe cloud a Set expiration and approval policies for Set user access to images and instances each cloud Define network settings that are through projects
18. customized environment was successfully added Example 4 16 Applying and listing the environment json files root deployment server knife environment from file itso cloud_environment json root deployment server knife environment list _default example ibm os allinone example ibm os single controller n compute example ibm sce itso cloud environment lt customized environment root deployment server 4 Use the knife command to deploy the customized topology as shown in Example 4 17 The deployment steps are applied first to the controller node and then to the compute node This step takes several minutes Ensure that this step completes for both all nodes by verifying the lines that confirm the successful completion You can also verify the deployment to the nodes by using the knife node list command Example 4 17 Deployment of customized topology json and verification that all nodes are added root deployment server f knife os manage deploy topology itso cloud topology json openstack controller mainz ibm com openstack controller mainz ibm com openstack controller mainz ibm com All nodes for environment itso cloud env bootstrapped Deploying bootstrapped nodes with run order number 2 All bootstrapped nodes with run order number 2 deployed Results for deploy of topology itso cloud_topology Results for nodes with run order number 1 Deploy of node at openstack controller mainz ibm
19. de provision virtual machines g Manage Requests 3 View Activity Reports Review and approve requests for new L View recent events for cloud resources instances and other actions li Figure 4 3 IBM Cloud Manager with OpenStack web management interface The additional GUI views are the Chef Server views on the deployment node where you can review most settings As shown in Figure 4 4 log in to the Chef Server GUI which is accessible at this website port 14443 is required to be open at the firewall on the deployment server https 9 155 51 40 14443 users Or you can use the FQDN https deployment server mainz ibm com 14443 users Chapter 4 IBM Cloud Manager with OpenStack 47 48 Chef Server Messages Where do geta Login You dont have access to that please login Any existing Admin level user can create new users To create the first user please login Login with the default admin credential which by defaultis both may be different Username if you ve setitin the application configuration username admin Password password p sswOrd1 Please change the default word Immediately after logging in Copyright 2 e Figure 4 4 Chef Server login panel for further review and changes by using the GUI The default credentials show on the left The user name is admin and the password is p sswOrd1 After the successful login the entry panel that is
20. environments The paper provides guidance in setting up an environment by using XIV as the back end storage in an OpenStack cloud environment This paper is not an official support document Authors This paper was produced by a team of specialists from around the world working at the International Technical Support Organization San Jose Center Bertrand Dufrasne is an IBM Certified Consulting I T Specialist and Project Leader for IBM System Storage disk products at the International Technical Support Organization ITSO San Jose Center He has worked at IBM in various I T areas He has authored many IBM Redbooks publications and has also developed and taught technical workshops Before joining the ITSO he worked for IBM Global Services as an Application Architect He holds a Master s degree in Electrical Engineering Roger Eriksson is an STG Lab Services Consultant based in Stockholm Sweden who works for the European Storage Competence Center in Mainz Germany He is a Senior Accredited IBM Product Service Professional Roger has over 20 years of experience working on IBM servers and storage including Enterprise and Midrange disk network attached storage NAS storage area networks SAN IBM System x IBM System p and IBM BladeCenter He has consulted created proofs of concept and provided education mainly with the XIV product line since December 2008 He has worked with both clients and various IBM teams worldwide He holds
21. examples include the names of individuals companies brands and products All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental COPYRIGHT LICENSE This information contains sample application programs in source language which illustrate programming techniques on various operating platforms You may copy modify and distribute these sample programs in any form without payment to IBM for the purposes of developing using marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written These examples have not been thoroughly tested under all conditions IBM therefore cannot guarantee or imply reliability serviceability or function of these programs Copyright IBM Corp 2015 All rights reserved v Trademarks IBM the IBM logo and ibm com are trademarks or registered trademarks of International Business Machines Corporation in the United States other countries or both These and other IBM trademarked terms are marked on their first occurrence in this information with the appropriate symbol or TM indicating US registered or common law trademarks owned by IBM at the time this information was published Such trademarks may also be registered or common law trademarks in other countries A current list of IBM trademarks is available on the Web a
22. information to non IBM websites are provided for convenience only and do not in any manner serve as an endorsement of those websites The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you Any performance data contained herein was determined in a controlled environment Therefore the results obtained in other operating environments may vary significantly Some measurements may have been made on development level systems and there is no guarantee that these measurements will be the same on generally available systems Furthermore some measurements may have been estimated through extrapolation Actual results may vary Users of this document should verify the applicable data for their specific environment Information concerning non IBM products was obtained from the suppliers of those products their published announcements or other publicly available sources IBM has not tested those products and cannot confirm the accuracy of performance compatibility or any other claims related to non IBM products Questions on the capabilities of non IBM products should be addressed to the suppliers of those products This information contains examples of data and reports used in daily business operations To illustrate them as completely as possible the
23. nodes to ensure that all required ports are defined as open Chapter 4 IBM Cloud Manager with OpenStack 45 46 Example 4 18 lists the open ports in our setup Most of the ports are listed in the json configuration files and also appear in the log files in the directory var 1og for the components such as Keystone Nova and Cinder on the controller or compute node Example 4 18 Controller firewall Opened ports list root openstack controller cat etc sysconfig iptables Firewall configuration written by system config firewal Manual customization of this file is not recommended filter INPUT ACCEPT 0 0 FORWARD ACCEPT 0 0 OUTPUT ACCEPT 0 0 A INPUT m state state ESTABLISHED RELATED j ACCEPT A INPUT p icmp j ACCEPT A INPUT i lo j ACCEPT A INPUT m state state NEW m tcp p tcp dport 22 j ACCEPT A INPUT m state state NEW m tcp p tcp dport 80 j ACCEPT A INPUT m state state NEW m tcp p tcp dport 443 j ACCEPT A INPUT m state state NEW m tcp p tcp dport 53 j ACCEPT A INPUT m state state NEW m udp p udp dport 53 j ACCEPT A INPUT m state state NEW m tcp p tcp dport 16509 j ACCEPT A INPUT m state state NEW m tcp p tcp dport 16514 j ACCEPT A INPUT m state state NEW m tcp p tcp dport 5000 j ACCEPT A INPUT m state state NEW m tcp p tcp dport 8774 j ACCEPT A INPUT m state state NEW m tcp p tcp dport 5671 j ACCEPT
24. path os group sce user sce service enabled false user input authentication name Administrator 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 w PPR o N a OoPODODBbBPpBOOQOhbhrrRRNP O0OR RMNRPONO 2 2 2 o o 2 2 VVVVV VV VV VV VV VV VV VV VV VV VV VV VV OV OCOOWrFRrOWOFRWFRFF O O LO LO O LO 0D 0 OO 0D BER aOOOoOww PWrRrPWOWOOWHRWONKPFPODVRFPKYNON YN BY OY OF FF bobos 38 Using XIV in OpenStack Environments username admin install folder opt ibm prop folder var opt ibm shortcuts root openstack developer mode false release icehouse secret db passwords data bag db passwords key path etc chef encrypted data bag secret secrets data bag secrets service passwords data bag service passwords user passwords data bag user passwords root deployment server itso cloud f 5 Example 4 11 shows the lines that require customization in the json files Example 4 11 The example topology json configuration file name topo CLOUD NAME description topo CLOUD NAME environment CLOUD NAME env run_sequentially false nodes fqdn NODE1 HOSTNAME password lt root_password gt quit on error true run order number 1 runlist role ibm os allinone kvm fqdn NODE2 HOSTNAME password lt root_password gt quit on error true run order number 2 runlist role ibm os compute node kwm
25. shown in Figure 4 5 displays Ensure that you select the environment that you want to review Chef Server enun None Editaccount Logout admin admin Environments Search Status Roles Nodes Cookbooks Databags Clients Users List Create Username admin Edit Delete os management server Edit Delete Figure 4 5 Chef Server Users entry panel As shown in Figure 4 6 you can use the Chef Server Node List to review and edit the configuration of the available nodes in the cloud setup Using XIV in OpenStack Environments Chef Server owen ET Edit account Logout admin admin Environments Search Status ook tabag Clients Users Node List Name openstack compute mainz ibm com Edit Delete openstack controller mainz ibm com Edit Delete Figure 4 6 Chef Server Node List Chapter 4 IBM Cloud Manager with OpenStack 49 Figure 4 7 show the editable node configuration Chef Server Environment cn Editaccount Logout admin admin Environments Search Status Roles Cookbooks Databags Clients Users Node openstack controller mainz ibm com List Create Show Edit Delete Environment default The node s environment ii Fois a xiv_ds8k configure Available Recipes xiv_ds8k install xiv ds8k logging xiv dsBk volume yum yum epel yum erlang solutions Attributes E json apache build essential credentials mysql E opens
26. the cluster as well Figure 3 4 shows the ports from both nodes in the cluster logging in to the XIV 33 ITSO IBM Cloud Manager Cluster 3 openstack compute mainz ibm com Sa 100000051EBCBC17 EE 21000024FFO83AF3 a openstack controller mainz ibm com Sa 100000051EB437C1 S 21000024FF083C4B Figure 3 4 Hosts zoned and logging in to the XIV 3 1 2 Installing the XIV Host Attachment Kit 26 The next step is to install the XIV Host Attachment Kit HAK on the servers because these nodes connect the back end storage to the OpenStack environment The installation of the HAK is the same for any Linux host Follow the installation procedures for the latest HAK which are at this website http pic dhe ibm com infocenter strhosts ic index jsp topic 2Fcom ibm help strg hosts doc 2Fhak homepage html After the HAK is installed successfully it is a good idea to validate connectivity to the back end storage You can attach the XIV volumes to use as additional disk space to help with the disk capacity on the servers If you attach the XIV volumes to use as additional disk space run the HAK xiv devlist command to show the attached volumes as shown in Example 3 2 on page 27 Using XIV in OpenStack Environments Example 3 2 Output from running the xiv_devlist command on the controller node root openstack controller xiv devlist XIV Devices Device Size GB Size GB Paths Vol Name Vol ID XIV ID XIV Host 34
27. together For example nova compute and nova scheduler are two of the Linux services that implement the Compute service Service In this document we use the term service to refer both to Linux and OpenStack services Hypervisor Code names Image Software that allows multiple virtual images to share a single physical machine OpenStack Compute requires a hypervisor and Compute controls the hypervisors through an application programming interface API server The process for selecting a hypervisor usually prioritizes and decides based on budget and resource constraints and the inevitable list of supported features and required technical specifications Most development uses the kernel based virtual machine KVM and Xen based hypervisors For a detailed list of features and support across the hypervisors see this website http wiki openstack org HypervisorSupportMatrix The types of virtualization standards that can be used with Compute include KVM Quick Emulator QEMU VMware ESX ESXi 4 1 update 1 and Xen Every OpenStack service has a code name as described in OpenStack components on page 7 These code names are reflected in the names of configuration files and command line utility programs For example the Keystone Identity service has a configuration file that is called keystone conf Images are disk images that are templates for virtual machine VM file systems The image service Glance is responsibl
28. user interface service portal In our configuration IBM Cloud Manager SCE self service portal can be reached at this website http 9 155 51 210 18080 cloud web Togin html Using XIV in OpenStack Environments Or you can use the FQDN http openstack controller mainz ibm com 18080 cloud web Togin html Figure 4 3 on page 47 shows the management portal where you define the web access and the cloud management for the web The default credentials are the same gt User name admin Password admin IBM Cloud Manager with OpenStack Administrator Instances Volumes Images Access Reports Configuration You are in Welcome Welcome to IBM Cloud Manager with OpenStack 135 IBM Cloud Manager with OpenStack enables users to provision virtual machines quickly while an administrator maintains oversight of the pr as managed environment Click an action to get started Details Ba 1 Configure the Cloud TER Manage Cloud Access gt Enable one or more cloud environments Set F Configure projects and users for the cloud Set Cloud settings meaa expiration and approval policies for each user access to images and instances through cloud Define network settings that are applied projects Define policies at the project level for Instance Summary when images are deployed additional customization Resource Usage e Manage Images Manage Instances Dereon eerie E Deploy import and customize images Monitor resize and
29. 01b30d56 var lib glance images on XIVPFEZ ext4defaultsO 0 root openstack controller 9 You can delete the upload_images section if no Internet connection exists from the controller node or the node where GLANCE was placed to download the images that are listed by the URLs later The MANAGEMENT_INTERFACE is the public interface and the DATA_INTERFACE needs to be a private network separate network port as defined in our setup 10 Now the minimum configuration is complete and you can verify it Tip In the setup and RHEL installation we used a tool package sysfsutils The sysfsutils tool package was not included but the Cinder installation requires it Therefore we installed it manually 42 Using XIV in OpenStack Environments Example 4 15 illustrates how to install the sysfsutils tool and verify the installation based on RHEL 6 5 Example 4 15 Installing and verifying the sysfsutils tool package on RHEL 6 5 root openstack controller yum install sysfsutils Loaded plugins product id security subscription manager dvd 2 9 kB 00 00 ibmos arch 2 9 kB 00 00 ibmos noarch 2 9 kB 00 00 Setting up Install Process Resolving Dependencies gt Running transaction check gt Package sysfsutils x86 64 0 2 1 0 7 e16 will be installed gt Processing Dependency libsysfs so 2 64bit for package sysfsutils 2 1 0 7 e16 x86 64 gt Running transaction check gt Package libsysfs x86 64 0 2
30. 1 0 7 el6 will be installed gt Finished Dependency Resolution Dependencies Resolved Package Arch Version Repository Size Installing sysfsutils x86 64 2 1 0 7 e16 dvd 38 k Installing for dependencies libsysfs x86 64 2 1 0 7 e16 dvd 44 k Transaction Summary Install 2 Package s Total download size 82 k Installed size 256 k Is this ok y N y Downloading Packages Total 3 7 MB s 82 kB 00 00 Running rpm check debug Running Transaction Test Transaction Test Succeeded Running Transaction Warning RPMDB altered outside of yum Installing libsysfs 2 1 0 7 e16 x86 64 1 2 Installing sysfsutils 2 1 0 7 e16 x86 64 2 2 Verifying sysfsutils 2 1 0 7 e16 x86 64 1 2 Verifying libsysfs 2 1 0 7 e16 x86 64 2 2 Installed sysfsutils x86 640 2 1 0 7 el6 Dependency Installed Chapter 4 IBM Cloud Manager with OpenStack 43 44 4 _ libsysfs x86_640 2 1 0 7 el6 Complete root openstack controller yum list sysfsutils Loaded plugins product id security subscription manager Installed Packages sysfsutils x86 64 2 1 0 7 e16 dvd root openstack controller 4 Now the customized environment is added to the configuration and the customized topology definitions the itso cloud_environment json and itso cloud_topology json files are deployed First the environment json file is applied and then verified by listing the available environment json files as shown in Example 4 16 if the
31. 2 root root 4096 14 Aug 07 58 resources root deployment server cmwo_fp3 install cmwo fixpack sh 4 Next install the fix pack by using the install cmwo fixpack sh installation shell script as shown at the bottom of Example 4 6 on page 36 5 After the update completes review the status of the Chef Server by using the command that is shown in Example 4 7 The output lists all processes in the run state Example 4 7 Verifying the Chef Server state root deployment server cmwo_fp3 chef server ctl status run bookshelf pid 1111 635543s run log pid 1105 635543s run chef expander pid 1110 635543s run log pid 1104 635543s run chef server webui pid 1114 635543s run log pid 1100 635543s run chef solr pid 1109 635543s run log pid 1103 635543s run erchef pid 1113 635543s run log pid 1101 635543s run nginx pid 1112 635543s run log pid 1102 635543s run postgresql pid 1115 635543s run log pid 1106 635543s run rabbitmq pid 1118 635543s run log pid 1117 635543s root deployment server cmwo_fp3 In our setup we used three hardware servers One server runs the deployment server chef and the other two nodes are the OpenStack controller node and the OpenStack compute node 36 Using XIV in OpenStack Environments Now we show the steps to prepare for the deployment of those two OpenStack nodes in our setup 1 Log in to the deployment server chef as root and c
32. A INPUT m state state NEW m tcp p tcp dport 18080 j ACCEPT A INPUT m state state NEW m tcp p tcp dport 6080 j ACCEPT A INPUT m state state NEW m tcp p tcp dport 35357 j ACCEPT A INPUT m state state NEW m tcp p tcp dport 8776 j ACCEPT A INPUT m state state NEW m tcp p tcp dport 9292 j ACCEPT A INPUT m state state NEW m tcp p tcp dport 5672 j ACCEPT A INPUT m state state NEW m tcp p tcp dport 6081 j ACCEPT A INPUT m state state NEW m tcp p tcp dport 9696 j ACCEPT A INPUT m state state NEW m tcp p tcp dport 5900 j ACCEPT A INPUT m state state NEW m tcp p tcp dport 5901 j ACCEPT A INPUT m state state NEW m tcp p tcp dport 5902 j ACCEPT A INPUT m state state NEW m tcp p tcp dport 5903 j ACCEPT A INPUT m state state NEW m tcp p tcp dport 5904 j ACCEPT A INPUT m state state NEW m tcp p tcp dport 9973 j ACCEPT A INPUT j REJECT reject with icmp host prohibited A FORWARD j REJECT reject with icmp host prohibited COMMIT root openstack controller 4 Start by reviewing these logs in the directory var log httpd for issues when you try to access the Cloud Management Dashboard gt openstack dashboard error log gt openstack dashboard access log IBM Cloud Manager SCE self service portal is a web browser based GUI view that is designed for cloud service management IBM Cloud Manager SCE self service portal is the
33. ITSO CM PFEZ P1 Would you like to add another IBM storage system Default No yes To cancel adding another back end press CTRL C Enter the storage array type x xiv for XIV or d ds8k for DS8000 Default x Enter the IBM XIV Storage System IP address or hostname 9 155 116 61 Using XIV in OpenStack Environments Enter the username and password for accessing the IBM XIV Storage System Username Default admin itso Password Please specify the required connection type f fc fibre for Fibre Channel or i iscsi for iSCSI Default i f Enter the name of the XIV storage pool to be used ITSO CM XIVO2 P1 Would you like to add another IBM storage system Default No Verifying installation Installation verified successfully Installing IBM Storage Driver for OpenStack Python eggs Stopping OpenStack Volume service Configuring OpenStack with IBM XIV Ds8000 Storage System information Starting OpenStack Volume service Installation of the IBM Storage Driver for OpenStack v1 3 1 1 b261 is complete Press ENTER to exit Chapter 3 Integrating the XIV in the OpenStack environment 29 30 Using XIV in OpenStack Environments IBM Cloud Manager with OpenStack This chapter describes the following topics gt Installing IBM Cloud Manager with OpenStack gt Integrating the IBM XIV Storage System as block storage into IBM Cloud Manager with OpenStack Using IBM Cloud Manager with OpenStack O Copyri
34. T55W 4 1 0 liaca liaca kc welcome html Important Illustrations of commands in this paper are based on the OpenStack Icehouse release This paper focuses on block storage with the XIV by using the Cinder driver Using XIV in OpenStack Environments 1 1 1 Concept The OpenStack cloud connects to the XIV over an iSCSI or Fibre Channel connection Remote cloud users can issue requests for storage resources from the OpenStack cloud These requests are transparently handled by the IBM Storage Driver The IBM Storage Driver communicates with the XIV Storage System and controls the storage volumes on it 1 1 2 Terminology OpenStack introduced a specific terminology to describe its features and functions including these important terms User Role Tenant Project Service Any person user or administrator who wants to use cloud services or administer tenants User administrator or system service within a tenant OpenStack supports the concept of multi tenancy as an organizational structure By this approach resources are managed within a tenant or project and can share services A tenant project offers the ability to correlate usage tracking auditing authorization and so on OpenStack and Linux services have some similarities A Linux service which is also called a daemon is a program that runs in the background and listens to a port to respond to service requests An OpenStack service is a group of Linux services that work
35. Using XIV in OpenStack Environments Introducing OpenStack with XIV in a brief overview Deploying OpenStack with IBM Cloud Manager Integrating XIV with OpenStack Bertrand Dufrasne Roger Eriksson Wenzel Kalabza Lisa Martinez am conte Redpaper International Technical Support Organization Using XIV in OpenStack Environments February 2015 REDP 4971 01 Note Before using this information and the product it supports read the information in Notices on page v Second Edition February 2015 This edition applies to the IBM XIV Storage System with XIV Storage System software Version 11 5 with IBM Cloud Manager and the OpenStack Icehouse release Copyright International Business Machines Corporation 2015 All rights reserved Note to U S Government Users Restricted Rights Use duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp Contents Notices orain a Va ine ESPERE a ia Mae ede Red v Trademarks s SPIN A att do aaa O A vi Preface sus i oe ee ta ee q a A a a ee E vii AULHONS ait A eee ga A a EA E AA AN vii Now you can become a published author too 0 000 eee ee viii Comments welcome o viii Stay connected to IBM Redbooks ooocoocccccocc a ix Summary of changes ccccisc aaa xi February 2015 Second Edition cccccccccis teens xi Chapter 1 OpenStack and IBM Cloud Manager OvervieW 1 1 1 OpenStack overvi
36. XX Available Public 1 xiv Total 8 Selected o 1 10 25 5 Figure 4 17 Volumes view The New Volume panel shows Enter a logical name for the volume Select the cloud configuration If you use projects tenants select the project Figure 4 18 Chapter 4 IBM Cloud Manager with OpenStack 59 60 New Volume Name rhs volume Description Cloud itso cloud Project Public Type xwv v Size GB min 1 2 4 Source No source empty volume Figure 4 18 Creating a volume The type refers to the type of storage system which in our case is XIV The size is the volume size that you want to allocate from the storage pool in the XIV system Click Save to execute the creation process IBM Cloud Manager instructs the Cinder node to use the direct API communications to create the volume in the XIV storage pool The result is depicted in Figure 4 19 ITSO_CM_PFE2_P1 no domain O 7 5 007 0 GB Hard volume 2905f4c3 6efc 4126 9fd8 853e1fa86a06 no d 20 0 34GB volume 3c7e1296 390e 4085 95ac ebcd5ca121d5 no d 51 0 51 GB volume 46c1db29 6644 4167 80f6 e0b31409958c no d 34 0 34 GB volume 567935cd 1e07 4cd0 9309 a18676432331 no d 34 0 34GB volume 5d5c20f3 005b 42b2 be91 6f70d7edcb6f no d 20 0 34 GB volume 6f9a7749 a7c2 4292 a12a a46cc3b375f5 no d 34 0 34 GB volume 7b41546a 4bb6 4ba1 a198 abae89a3easc no d 20 0 34 GB volume 7c55fba6 91f3 4c71 9e32 f2f53c9eb1d9 no d
37. a Technical College Graduation in Mechanical Engineering Wenzel Kalabza is a Certified XIV Product Field Engineer PFE based in the storage competence center in Mainz Germany Wenzel joined IBM in 1998 as Customer Quality Engineer for IBM disk drive failure and performance analysis He joined the Back Office for the high end storage system Enterprise Storage System ESS in June 2002 In 2005 Wenzel started a PFE role for the IBM Disk Storage DS60007M In June 2008 he became a PFE for the XIV storage product Wenzel holds a degree in Electrical Engineering and Power Economy and several storage related certifications Lisa Martinez has worked in the North America Storage Specialty Team formerly ATS as a Storage Consultant since January 2012 Her focus is pre sales support for IBM DS8000 and XIV And she is the Lead Instructor for XIV client based workshops Her prior experience includes roles as a Storage Architect in the Specialty Services Area in GTS a temporary assignment as a Global Support Manager for Cardinal Health and Test Architect in disk storage focusing on system level test for XIV for three years and Copy Services for DS8000 Lisa holds degrees in Computer Science from New Mexico Highlands University and Electrical Engineering from the University of New Mexico She has been employed with IBM for 17 years Copyright IBM Corp 2015 All rights reserved vii Special thanks to Harald Seipp for his help and support in install
38. admin Deployment date No data provided Hypervisor KYM Expiration date None gt Virtual Machine Properties CPUs 1 Memory 2 048 MB v Storage Volumes 1 Total Size 4 096 MB Name a Size MB Server Images None Figure 4 23 Attached volumes Now log in to the instance and rescan to discover the new volume Then mount the new volume to a directory of your choice Chapter 4 IBM Cloud Manager with OpenStack 63 64 Using XIV in OpenStack Environments Related publications The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this paper IBM Redbooks The following IBM Redbooks publications provide additional information about the topic in this document Note that some publications referenced in this list might be available in softcopy only vvvvvvvy IBM XIV Storage System Architecture and Implementation SG24 7659 IBM XIV Storage System Business Continuity Functions SG24 7759 IBM XIV Storage System Multi site Mirroring REDP 5129 XIV Storage System Host Attachment and Interoperability SG24 7904 XIV Storage System SSD Caching Implementation REDP 4842 XIV Storage System in VMware Environments REDP 4965 IBM Hyper Scale for the XIV Storage System REDP 5053 RESTful API Support in XIV REDP 5064 You can search for view download or order these documents and other Redbooks Redpapers Web Docs draft and addi
39. alent product program or service that does not infringe any IBM intellectual property right may be used instead However it is the user s responsibility to evaluate and verify the operation of any non IBM product program or service IBM may have patents or pending patent applications covering subject matter described in this document The furnishing of this document does not grant you any license to these patents You can send license inquiries in writing to IBM Director of Licensing IBM Corporation North Castle Drive Armonk NY 10504 1785 U S A The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND EITHER EXPRESS OR IMPLIED INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF NON INFRINGEMENT MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE Some states do not allow disclaimer of express or implied warranties in certain transactions therefore this statement may not apply to you This information could include technical inaccuracies or typographical errors Changes are periodically made to the information herein these changes will be incorporated in new editions of the publication IBM may make improvements and or changes in the product s and or the program s described in this publication at any time without notice Any references in this
40. anager with OpenStack 00 ccc eee 32 RS IA A ones asec LN Nal oles ee O MM nd IAS Ae pn ONC 32 4 1 2 Installing IBM Cloud Manager with OpenStack 0000e eee 32 4 2 Using IBM Cloud Manager with OpenStack 000 cc eee eee ee 51 4 2 1 Configuring IBM Cloud Manager to manage a cloud 2 0 5 52 d 2 2 IMporting an image ss woe ia a Phd 53 4 2 3 Deploying an instance virtual machine aeaaaee eee eee 55 4 2 4 Creating and attaching a volume to an instance 000 0 eee eeee 59 Related publications 0 aaa 65 IBM RedbookS a a pasa Dan adres ee Rae ERE when Ia bse eat ects Ste ee th ee 65 Copyright IBM Corp 2015 All rights reserved iii iv Other publications ss patins ia sato A nbs sates E T pad a bala awd dE Spa A Online FeSQUICES pass ciais A Seas ha ER haul EA lA A Help from IBM uia real o ete da ie bel heed ee E PAR ee he A a AS q DS DA Using XIV in OpenStack Environments Notices This information was developed for products and services offered in the U S A IBM may not offer the products services or features discussed in this document in other countries Consult your local IBM representative for information on the products and services currently available in your area Any reference to an IBM product program or service is not intended to state or imply that only that IBM product program or service may be used Any functionally equiv
41. and compute node d Modify the etc fstab to add that image location as the yum repository by using the yum config manager as shown in Example 4 2 Example 4 2 RHEL installation image mounted as the repository root openstack controller mount var rhel65dvd RHEL6 5 20131111 0 Server x86 64 DVDl iso on var rhel65dvd mnt type iso9660 rw loop dev loop0 root openstack controller cat etc fstab var rhel65dvd RHEL6 5 20131111 0 Server x86_64 DVD1 iso var rhel65dvd mnt iso9660 loop 0 0 root openstack controller Is 1s var rhel65dvd insgesamt 3763216 8 dr xr xr x 12 root root 8192 11 Nov 2013 mnt 4 drwxr xr x 2 root root 4096 26 Sep 18 14 repodata Using XIV in OpenStack Environments 3763204 rw r r 1 root root 3853516800 26 Sep 17 59 RHEL6 5 20131111 0 Server x86 64 DVDl iso root openstack controller 4 yum config manager add repo var rhel65dvd mnt For more information see the IBM Cloud Manager documentation After you complete the prerequisites you can start the installation of the deployment server Follow these steps for an RHEL 64 bit x86 v6 5 OS based installation 1 Create an installation directory with sufficient capacity for the installation and service pack files as shown in Example 4 3 Untar tar xvf file the compressed packages and change chmode x file the permissions so that the installation files are executable In Example 4 3 the cmwo Cloud Manager with OpenStack fi
42. ce of the controller node DATA_INTERFACE that is eth1 is the data network interface NODE1_IP_ADDRS is the IP address of Node1 controller Chapter 4 IBM Cloud Manager with OpenStack 41 Forthe line filesystem store datadir var lib glance images lt please customize we configured GLANCE to place the images on an XIV volume that was separately created mapped and mounted to the controller node where GLANCE is in our setup So this line was changed to filesystem store datadir var lib glance images on XIVPFEZ The volume on the XIV shows under the xiv_devlist command Example 4 14 on page 42 The volume name is Openstack glance image volume and the volume has approximately 1 5 TB capacity In the output the volume is followed by the etc fstab entry so that the volume is always mapped when the controller needs to be restarted Example 4 14 GLANCE image location modification root openstack controller xiv devlist XIV Devices Device Size GB Paths Vol Name Vol ID XIV ID XIV Host dev mapper mpathr 1514 3 4 4 Openstack_glance_image volume 2572 1340010 openstack controller mainz ibm com root openstack controller cat etc fstab etc fstab Created by anaconda on Thu Sep 18 16 20 29 2014 Accessible filesystems by reference are maintained under dev disk See man pages fstab 5 findfs 8 mount 8 and or blkid 8 for more info He FR SR Se UUID c91989c0 5326 4f5b 82c3 8137
43. comments to IBM Corporation International Technical Support Organization Dept HYTD Mail Station P099 2455 South Road Poughkeepsie NY 12601 5400 Using XIV in OpenStack Environments Stay connected to IBM Redbooks Find us on Facebook http www facebook com IBMRedbooks Follow us on Twitter http twitter com ibmredbooks gt Look for us on LinkedIn http www linkedin com groups home amp gid 2130806 Explore new Redbooks publications residencies and workshops with the IBM Redbooks weekly newsletter https www redbooks ibm com Redbooks nsf subscribe 0penForm gt Stay current on recent Redbooks publications with RSS Feeds http www redbooks ibm com rss html Preface ix x Using XIV in OpenStack Environments Summary of changes This section describes the technical changes made in this edition of the paper and in previous editions This edition might also include minor corrections and editorial changes that are not identified Summary of Changes for Using XIV in OpenStack Environments as created or updated on February 27 2015 February 2015 Second Edition This revision reflects the addition deletion or modification of new and changed information described below New information Deploying the XIV Storage System and OpenStack with IBM Cloud Manager O Copyright IBM Corp 2015 All rights reserved xi xii Using XIV in OpenStack Environments OpenStack and IBM Cloud Manager overvie
44. crosoft Windows Server 2012 EE IBM System z RHEL 6 5 Chapter 1 OpenStack and IBM Cloud Manager overview 11 Table 1 2 Supported operating systems for the controller OpenStack controller node Host operating system Pee i on STO EOI ETE System x amp Pupeflex x Power amp Pureflex Power System z cw fz fem E E e em es Linux Redhat i eee its ee Redhat cached 2013 2014 2013 4013 4013 2014 4013 thd Figure 1 8 Cloud Manager compute node specifications 12 Using XIV in OpenStack Environments OpenStack environment This chapter reviews some of the required steps to install the OpenStack environment Our scenario is a simple installation with a single compute node and a single storage node O Copyright IBM Corp 2015 All rights reserved 13 2 1 Introduction Designing deploying and configuring an OpenStack environment requires an understanding of the logical architecture The following diagram in Figure 2 1 conceptualizes how an IBM storage system the IBM XIV Storage System or DS8000 connects to the OpenStack cloud environment The IBM Storage Driver for OpenStack is installed on the OpenStack Cinder nodes The connection to the IBM storage system is supported over Fibre Channel or iSCSI the XIV only ad Y ID i Cloud users i A i Resources management p ge 1 Request for resources resources i i Management over SSL Nova compute Cinder nodes
45. d VM Attached to RH on dev vdb Attached to Ubuntu 14 04 on fdevihde Attached to ITSO boot teston vda Attached to ubuntu on devirde Attached to ubuntu on fdevivde Attached to Ubuntu 14 04 on dewihde Figure 4 21 Attaching the volume to an instance Select the instance to which the volume must be attached Type the mount point for the volume which in our case is dev vdc Figure 4 22 Chapter 4 IBM Cloud Manager with OpenStack 61 Attach volume to a selected instance Select the instance to attach to the volume Attach the volume as device idevivde Attach to a selected instance gt Instance Status Owner Description RHEL70 OK Administrator Windows 10 IB Stopped Administrator ls cirros_instance a OK Administrator rhs E Stopped Administrator C ubuntu OK Administrator ubuntu precise KA ox Administrator winLite E ox Administrator Total 7 Selected 1 1 Figure 4 22 Attaching the volume to an instance and selecting the mount point Note If the volume is attached to a Microsoft Windows instance use dev vdc To verify that the volume was attached correctly go to the Instance view and click the instance as shown in Figure 4 23 62 Using XIV in OpenStack Environments rhs Status or Running 4 Edit Suspend B Stop Delete More x Hame rhs Description Host name instance 00000030 IP address 10 0 0 22 Cloud itso cloud Project Public Owner Administrator
46. e Controller Node E Note In Figure 2 3 the Cinder Node can reside on a separate server from the compute or controller nodes In this case the Cinder Node communicates to the controller or compute nodes through the private network only Figure 2 3 Nova multiple node 18 Using XIV in OpenStack Environments Important These requirements are provided as is and are based on code that was available at the time of writing this paper For the latest information see the IBM Storage Driver for OpenStack release notes at this web page http pic dhe ibm com infocenter strhosts ic topic com ibm help strghosts doc nova_pdfs html 2 2 2 Installing OpenStack The OpenStack installation is documented thoroughly on the OpenStack website In this section we provide a summary list of the tasks to complete for a block storage device such as the XIV The installation is based on the Icehouse release 1 Install the Linux 64 bit version that you selected We recommend that this installation is a minimal installation VMs can be used for test environments but they are not recommended for the full OpenStack production environment 2 Configure the network interfaces Disable the automated network management tools OpenStack Networking Neutron requires one controller node one network node and at least one compute node 3 Configure NTP We advise that you configure additional nodes in the deployment for time synchronization
47. e 4 12 Importing the image 4 2 3 Deploying an instance virtual machine To deploy an instance from an imported image select the Images tab and click the name of an image that is listed Figure 4 13 on page 56 Chapter 4 IBM Cloud Manager with OpenStack 55 Cloud All Clouds Project All Projects Architecture All Architectures 2 E z More Image a Status Cloud Project Architecture Version Description RHEL 6 5 Box itso cloud Public x86 RHEL70 DK itso cloud Public 26 Image created as a snapshot of instance RH RH_snapshot_201410151 tso cloud ITSO project x86 e li O Failed Per RN taken on 10 18 14 1 06 PM Image created for an SUSENSp2 Failed itso cloud Publ imported image S rtso clou ublic P do SUSE11sp2 started on 10 16 14 1 49 PM Image hypervisor type Ubuntu precise DK itso cloud Public 86 qemu Ubuntu precise Image hypervisor type ox itso cloud ITSO Project2 86 2014 10 15 12 02 30 La 2 qemu Windows 10 Beta DK itso cloud Public x86 Image hypervisor e cirros E ox itso cloud Public x86 ey ty qemu Image hypervisor type rhs Bok itso cloud Public 85 eas w qemu Figure 4 13 Imported images The Deploy image window shows the characteristics of the image to be used Click Deploy as shown in Figure 4 14 on page 57 to see the second Deploy window 56 Using XIV in OpenStack Environments 1 E rhs Status ok gt Deploy Configure 2 Edit Copy More
48. e for the storage and management of images within OpenStack Chapter 1 OpenStack and IBM Cloud Manager overview 5 Instance Instances are the actual VMs that run on physical compute nodes Nova the compute service manages the instances More than one instance can be started from the same image The instance is run from a copy of the base image Snapshots of a running instance can be taken which create a new image based on this running version and can be deployed as a new instance 1 2 OpenStack architecture and components The OpenStack architecture and its components are described in this section Figure 1 4 shows a simple view of how the environment works This view is a diagram illustrating how the deployment interacts with the controller and compute nodes Projects or tenants are deployed by using the Compute environment Controller Compute Compute Compute Figure 1 4 OpenStack Compute environment 1 2 1 What is OpenStack 6 OpenStack is a global collaboration of developers and cloud computing technologists that seek to produce a ubiquitous Infrastructure as a Service laaS open source cloud computing platform for public and private clouds OpenStack consists of many interrelated projects that control resources for compute storage and networking OpenStack is managed by the OpenStack Foundation a non profit organization that oversees both development of the project and building a community around the pro
49. e identity service on the controller node Install and configure the OpenStack clients Configure the image service Configure the compute service gt O ON O 0 0 Add and configure the OpenStack components Network Dashboard Block Storage and Object Storage 11 Create a storage pool for the OpenStack on the XIV Storage System Important The storage pool must be created before you install the storage driver for OpenStack 12 Install IBM Storage Driver for OpenStack Note The IBM Storage Driver is installed on the node that contains Cinder or Cinder with Compute 13 Install and configure the supported hypervisors 14 Build and import the operating system images Installation and configuration Detailed installation and configuration steps for all required components Linux network or storage area network SAN configuration and so on are beyond the scope of this paper In the environment that we used for our examples in this document the OpenStack infrastructure is set up with two servers that are hosted by RedHat 6 5 The following key components were installed and configured Controller node Image node Block storage node Cinder which is installed with the compute node Compute node IBM Storage Driver for OpenStack IBM XIV Storage System Gen3 vvvvvy 2 2 1 OpenStack system requirements Before you deploy the supported infrastructure verify that you have the appropriate hardware Ensure that you ha
50. ew 1 0 0 aaa 2 Aled Concept isis LANGE aes ew eal esas She eae 5 tie TENEO y ARPA ALE alae Seles anes tate uae tae easy real E a 5 1 2 OpenStack architecture and components 0 000 cece eee eee eee 6 1 2 1 What is OpenStack 0 00 e eee 6 1 2 2 OpenStack components ooccccco teens 7 1 3 OpenStack and XIV multi tenancy 0 00 0 ae 8 1 3 1 XIV multi tenancy and domains 0 cee tee 8 1 3 2 OpenStack with XIV multi tenancy 0 0000 e eee 9 1 4 IBM Cloud Manager with OpenStack 00 00 cece eee 10 1 4 1 What is IBM Cloud Manager ooococcccccc 10 Chapter 2 OpenStack environment 00000 c eee ees 13 2A IntrOdUCHON cA A A ese R a eat tase a tence a dala eal a 14 2 2 OpenStack installation 1 2 20 00 14 2 2 1 OpenStack system requirements 00000 cece 15 2 2 2 Installing OpenStack 0 0 0 0 000 eee 19 2 2 3 Creating users roles and projectS 00 00 cece eee 20 Chapter 3 Integrating the XIV in the OpenStack environment 23 3 1 Integrating the XIV in the OpenStack environment 0000 0 ee eee eee 24 3 1 1 Preparing the XIV for OpenStack 0000s 25 3 1 2 Installing the XIV Host Attachment Kit 2 0 0 c eee eee 26 3 1 3 Installing IBM Storage Driver for OpenStack 0000 e eee eee 27 Chapter 4 IBM Cloud Manager with OpenStack 002 eeu 31 4 1 IBM Cloud M
51. ght IBM Corp 2015 All rights reserved 31 4 1 IBM Cloud Manager with OpenStack IBM Cloud Manager with OpenStack formerly IBM SmartCloud Entry is a self service portal for simplified cloud management 4 1 1 Overview With IBM Cloud Manager with OpenStack you can work with virtual machines VMs Self service capabilities simplify the process of executing many common public or private cloud operations Provisioning and de provisioning instances VMs Cloning instances Taking snapshots of instances Starting and stopping instances Resizing existing instances Attaching storage area network SAN storage to instances vvvvvy The new version of IBM Cloud Manager offers the following functions Added support for z VM and PowerKVM virtualization hypervisors through OpenStack technologies gt Chef deployment server IBM Cloud Manager with OpenStack Chef Server provides greater flexibility and control over how you deploy OpenStack in your cloud You can now manage storage volumes for individual VMs with IBM Cloud Manager with the OpenStack self service portal You can create delete edit and attach or detach storage volumes for a corresponding instance An administrator can lock a user account to prevent access to IBM Cloud Manager with the OpenStack self service portal gt Cloud environment management is available from a z VM system You can deploy the z VM appliance to manage your cloud environment from
52. in OpenStack Environments Using XIV in OpenStack Environments Introducing OpenStack with XIV in a brief overview Deploying OpenStack with IBM Cloud Manager Integrating XIV with OpenStack This IBM Redpaper publication provides a brief overview of OpenStack and IBM Cloud Manager with OpenStack It focuses on the use of OpenStack with the IBM XIV Storage System Gen3 The illustration scenario in the paper uses the OpenStack Icehouse release which is installed on RedHat Linux servers and the IBM Storage Driver for OpenStack This paper is intended for clients and cloud administrators who look forward to integrating IBM XIV Storage Systems in OpenStack and using IBM Cloud Manager with OpenStack environments The paper provides guidance in setting up an environment by using XIV as the back end storage in an OpenStack cloud environment This paper is not an official support document REDP 4971 01 I Mu al qu O A E Redpaper INTERNATIONAL TECHNICAL SUPPORT ORGANIZATION BUILDING TECHNICAL INFORMATION BASED ON PRACTICAL EXPERIENCE IBM Redbooks are developed by the IBM International Technical Support Organization Experts from IBM Customers and Partners from around the world create timely technical information based on realistic scenarios Specific recommendations are provided to help you implement IT solutions more effectively in your environment For more information ibm com redbooks
53. ing IBM Cloud Manager Thanks to the following people for their contributions to this project Diane Benjuya Ramy Buechler Rami Elron Theodore Gregg Rony Shapiro Yossi Siles Oded Kellner George Thomas Carlo Saba Stephen Solewin and Mary J Connell IBM Thanks also to the authors of the previous editions Desire Brival Thomas Peralto and Markus Oscheka IBM Now you can become a published author too Here s an opportunity to spotlight your skills grow your career and become a published author all at the same time Join an ITSO residency project and help write a book in your area of expertise while honing your experience using leading edge technologies Your efforts will help to increase product acceptance and customer satisfaction as you expand your network of technical contacts and relationships Residencies run from two to six weeks in length and you can participate either in person or as a remote resident working from your home base Find out more about the residency program browse the residency index and apply online at ibm com redbooks residencies html Comments welcome viii Your comments are important to us We want our papers to be as helpful as possible Send us your comments about this paper or other IBM Redbooks publications in one of the following ways Use the online Contact us review Redbooks form found at ibm com redbooks Send your comments in an email to redbooks us ibm com gt Mail your
54. ining_images html Chapter 4 IBM Cloud Manager with OpenStack 53 To import an image click the Images tab and select Import image as shown in Figure 4 10 Instances volumes Images Reports Configuration a Click an image below to work with the image You are in wages Cloud All Clouds Project All Projects Architecture All Architectures 2 ran z More l Import Image Image ET status Cloud Project Architecture Ubuntu precise A ok itso cloud Public x86 cirros ok itso cloud Public x86 ubuntu trusty Bok itso cloud Public x86 w E ok itso cloud Public x86 Total q Selected o 1 Figure 4 10 Import a VM image Choose an image and its corresponding type of disk format select the hypervisor type and click Import See Figure 4 11 on page 55 In our case we used a RedHatServer installation from KVM in the disk format of qcow2 54 Using XIV in OpenStack Environments Import Image An image can be imported from an image file or a URL Import type URL O File Image file rhs21u2 004 qcou 2 Browse Image name ths Cloud itso cloud Project Public Disk format 2 acow2 Container format OVF v Hypervisor type KVM Architecture x86_64 Minimum memory MB 2 000 Minimum storage GB 20 Figure 4 11 Import parameters Figure 4 12 shows the progress bar for importing the image Uploading image file 1 Figur
55. isk operating system images for VMs that are mostly used in OpenStack Compute It has several components Glance api accepts Image API calls for discovery retrieval and store images Glance registry stores processes and retrieves metadata about images size type and so on A database stores the image metadata A data repository stores the image files Chapter 1 OpenStack and IBM Cloud Manager overview 7 gt Neutron Network provides network connectivity as a service between interface devices that are managed by other OpenStack services most likely Nova The service works by allowing users to create their own networks and then attach interfaces to them gt Ceilometer Telemetry provides a mechanism to collect and configure the necessary data to monitor services and the infrastructure in the OpenStack environment It can also collect custom usage data with additional plug ins gt Heat Orchestration provides a template for creating most OpenStack resource types instances floating IP addresses volumes security groups and users This service enables cloud deployments to integrate with the Orchestration module directly or through custom plug ins gt Trove Database provides a scalable cloud provisioning function for relational and non relational database engines This function enables users to use the database features without dealing with the administrative tasks It also provides resource isola
56. ject OpenStack allows users to deploy VMs attach storage to the VMs create projects for private and public clouds create and manage users for private and public clouds and other tasks for managing a cloud environment It provides a graphical Dashboard as well as a command line interface CLI for the management Using XIV in OpenStack Environments 1 2 2 OpenStack components OpenStack has several components gt Nova Compute provides VMs or instances Nova interacts with several OpenStack services such as Keystone Horizon or Glance The API process can upload and query Glance while nova compute downloads images for use in launching images Nova is the most complex and distributed component of OpenStack Many processes are involved to handle user API requests and launch VMs The following list is a summary of Nova processes The nova api handles user compute API calls synchronizes activities and enforces policy The nova compute process is a daemon that launches and ends VM instances by using the hypervisor s APIs The nova network manages the network by setting up bridges or changes to iptables rules nova schedule which is implemented with RabbitMQ or Qpid determines where instances run based on requests that are in the message queue The SQL database stores items for the cloud The items can be an instance available network a project or another type The nova consoleauth offers a prox
57. le is already untarred and executable however the service packs are not Example 4 3 The cmwo installation package location root deployment server INSTALLER LAUNCH DIR pwd root INSTALLER LAUNCH DIR root deployment server INSTALLER LAUNCH DIR 11 insgesamt 6378424 rwxr xr x 1 root root 692877531 25 Sep 07 59 cmwo410 xlinux install bin rw r r 1 root root 1009412262 25 Sep 08 00 cmwo410 xlinux install pkg Ol tar gz rw r r 1 root root 818247595 25 Sep 08 00 cmwo410 xlinux install pkg 02 tar gz rw r r 1 root root 1073679808 25 Sep 08 01 cmwo410 xlinux install pkg 03 tar gz 2 Start the cmwo installation as shown in Example 4 4 Example 4 4 The cmwo installation root deployment server INSTALLER LAUNCH DIR 4 echo LICENSE ACCEPTED true gt installer rsp root deployment server INSTALLER LAUNCH DIR cat installer rsp LICENSE_ACCEPTED true root deployment server INSTALLER LAUNCH DIR 4 cmwo410_xlinux_install bin f installer rsp If the installation does not succeed review the installation log for problem determination The installation log file location is indicated in Example 4 5 Example 4 5 Installation log file root deployment server INSTALLER LAUNCH DIR Ts 1 opt ibm cmwo _installation Logs rw r 1 root root 306506 26 Sep 06 50 IBM_Cloud_Manager_with_OpenStack_Instal1_09 26 2014 06 45 13 1log 3 Download the latest fix packs At the time of this installation Service Pack 3 f
58. ler 1 compute topology lt please customize openstack endpoints network openvswitch bind_interface MANAGEMENT_INTERFACE lt please customize Hs compute vnc bind bind_interface MANAGEMENT_INTERFACE lt please customize network 40 Using XIV in OpenStack Environments verbose false debug false openvswitch bridge mappings default br ex bridge mapping interface br ex DATA_INTERFACE lt please customize openstack release icehouse region RegionOne endpoints host NODE1_IP_ADDR lt please customize bind host NODE1_IP_ADDR lt please customize mq host NODE1_IP_ADDR lt please customize port 5671 h image verbose false debug false notification_driver messaging filesystem store datadir var lib glance images lt please customize image upload true upload images cirros ubuntu ls upload image ubuntu http cloud images ubuntu com precise current precise server cloudimg amd64 diskl img cirros http download cirros cloud net 0 3 2 cirros 0 3 2 x86_64 disk img For our environment json file the following strings need customization CLOUD_NAME is your unique string to identify the CMWO server instance MANAGEMENT_INTERFACE that is eth0 is the management network interfa
59. lock storage by adding back end migrations with tiered storage environments This capability allows for performance management in heterogeneous environments Because the focus of this paper is around block storage and the Cinder node Figure 1 3 illustrates the flow of the Cinder node which for the XIV and the DS8000 DS8k uses the IBM Storage Driver for OpenStack This driver is available through the following link http www ibm com support fixcentral swg selectFixes parent Enterprise 2BStorage 2BServers amp product ibm Storage Disk XIV StoragetSystemt 282810 2812 29 amp release Al amp platform Al1 amp function al1 XIV DS8000 XSF ro Lad SSL Management closed source Volume driver gt opensource gt O Figure 1 3 IBM Storage OpenStack flow OpenStack also provides a Dashboard for administrators and users to manage the cloud with a graphical user interface GUI In addition IBM offers IBM Cloud Manager with OpenStack which integrates all of the OpenStack Dashboard features into simple to use cloud management software that includes IBM enhancements such as the Chef deployment feature for rapid installation and configuration of a cloud environment a self service portal for workload provisioning virtual image management and monitoring For more information about IBM Cloud Manager with OpenStack see the following website https www 01 ibm com support knowledgecenter SS
60. network adapter for the management network Tip In our restricted lab environment neither of the two network ports provided an Internet connection However Internet access is useful for OS updates Therefore we advise you to procure additional network ports for each node server A fully qualified domain name FQDN is required The FQDN name domain format is required In our setup we modified the etc hosts files of each node with the FQDN information because we did not use a dedicated Domain Name Server DNS For a productive environment a DNS is the preferred solution Example 4 1 illustrates our setup Example 4 1 FQDNs in the etc hosts files are the same for all OpenStack hosts root deployment server f cat etc hosts 127 0 0 1 localhost localdomain localhost 9 155 51 40 deployment server mainz ibm com deployment server 9 155 51 210 openstack controller mainz ibm com openstack controller 9 155 51 97 openstack compute mainz ibm com openstack compute root deployment server 4 The deployment server and the nodes that are planned for deployment must all use the same root password Another prerequisite is a properly configured RHEL YUM repository Because we had no internet connection we used the following steps to create this repository a Create a directory for the RHEL installation image b Copy the image into that location c Mount the RHEL 6 5 DVD installation image on each OpenStack server locally controller
61. nf by following the instructions at this website https www 01 ibm com support knowledgecenter SST55W 4 1 0 liaca liaca configu ring multiple block storage backends htm 3 Upload the xiv ds8k cookbook and follow the instructions in this knowledge base to install the Cinder driver for xiv ds8k https www 01 ibm com support knowledgecenter SST55W_4 1 0 liaca liaca_configu ring_xiv_storage_cookbook htm The openstack driver version file is hardcoded in the script and it must be modified if necessary For our installation we need to modify the installation script to look for the new driver version The installation script is hardcoded for IBM Storage Driver for OpenStack 1 3 1 b211 rhel6 x tar gz We need IBM Storage Driver for OpenStack 1 3 1 1 b261 rhel6 x tar gz to link to the correct file Tip After you change the script perform a full restart of the cinder volume and cinder api services on the compute node see Example 4 19 Example 4 19 Restart Cinder services to see storage in the Cloud Manager root openstack controller cinder service openstack cinder api full restart Stopping openstack cinder api OK Starting openstack cinder api OK root openstack controller cinder service openstack cinder volume full restart Stopping openstack cinder volume OK Starting openstack cinder volume OK 4 2 Using IBM Cloud Manager with OpenStack After you complete the installation of IBM Cloud Manager you must
62. nt repository root deployment server itso cloud knife environment show example ibm sce chef_type environment cookbook_versions apache2 gt 1 9 6 apt gt 2 3 8 aws gt 1 0 0 build essential gt 1 4 2 chef handler gt 1 1 5 database gt 2 0 0 db2 gt 0 2 4 erlang gt 1 4 2 homebrew gt 1 5 4 ibm openstack appliance migration gt 0 1 41 ibm openstack common gt 9 5 7 ibm openstack iaas gateway gt 0 1 4 ibm openstack iptables gt 9 2 1 ibm openstack powervc driver gt 9 2 1 ibm openstack prs gt 0 1 5 ibm openstack roles gt 9 0 1 ibm openstack simple token gt 9 0 0 Chapter 4 IBM Cloud Manager with OpenStack 37 2 ibm openstack yum server ibm openstack zvm driver ibm sce iptables logrotate mysql ntp openssl openstack block storage openstack common openstack compute openstack dashboard openstack identity openstack image openstack network openstack ops database openstack ops messaging openstack orchestration openstack telemetry pacman postgresql python qpid rabbi tmq selinux windows xfs yum yum epel yum erlang_solutions default_attributes description Example environment for stand alone IBM Cloud Manager with OpenStack self service portal json_class Chef Environment name example ibm sce override attributes ibm sce choose license type boolean 0 config prop silent 1 license
63. onment before any configuration The following link provides the instructions for creating users in OpenStack http docs openstack org user guide admin content dashboard manage projects users html dashboard_create_user When you use the Cloud Management Dashboard create users by clicking ADMIN gt Identity Panel gt Users as shown in Figure 2 4 The Users panel is available after the initial installation and configuration of OpenStack and it includes the Dashboard Horizon Cloud Management Dashboard PROJECT ADMIN Users Q re CD Tinte Users system Panel Identity Panel User Name Email User ID Enabled Actions Project heat 21088c3bd703412c909753774be6b5dd True Edit More J gwagent 3738067baec146eb91fe244857c0bc1c True Edt More cinder 440a8367858 143168 186ae9375108f31 True Edit More itso user 4c142407eee34896a7a4b445f5e2ddc5 True Edt More ceilometer 4cT54a17e5b441829190 2de9 1fe149e True Edt More 66ba0046b8943d7 Sface4f20e2564d7 True Edit More admin 76553daaac 3143249047 ae4d IOdecdaa True Edt More neutron bfd80c1340bd47fa9b5117471171b7d0 True Edt More glance d635f1e49dca4cc29fd1dc713843a10e True Edit More Figure 2 4 Users panel in the OpenStack Dashboard Notice the highlighted Create User option in Figure 2 4 Clicking Create User opens a pop up window so that you can create a user and the specific attributes of the user such as the user s role and project OpenStack has specific users
64. or cmwo 4 1 was the current service pack To place the latest fix pack on the server create a dedicated directory for the fix pack file such as cmwo fp3 copy the latest fix pack file into that directory and unpack the fix pack file See Example 4 6 on page 36 Chapter 4 IBM Cloud Manager with OpenStack 35 Example 4 6 Handling cmwo fix packs root deployment server INSTALLER LAUNCH DIR 4 mkdir cmwo fp3 rootedeployment server INSTALLER LAUNCH DIR cd cmwo fp3 root deployment server cmwo_fp3 pwd cmwo_fp3 root deployment server cmwo_fp3 cp root INSTALLER LAUNCH DIR cmwo fixpack 4 1 0 3 tar gz root deployment server cmwo_fp3 11 rw r r 1 root root 1658027768 1 Dez 06 29 cmwo fixpack 4 1 0 3 tar gz rootedeployment server cmwo_fp3 tar xvf cmwo fixpack 4 1 0 3 tar gz install cmwo fixpack sh resources resources set permissions sh resources update chef server sh resources copy chef knife plugins sh resources upload chef resources sh fixpack properties README txt product files product files bin product files license rootedeployment server cmwo_fp3 11 insgesamt 1619212 rw r r 1 root root 1658027768 1 Dez 06 29 cmwo fixpack 4 1 0 3 tar gz r r r 1 root root 672 14 Aug 08 15 fixpack properties r xr xr x 1 root root 15026 14 Aug 07 58 install cmwo fixpack sh drwxrwxrwx 8 root root 4096 14 Aug 08 15 product_files r r r 1 root root 10665 14 Aug 08 15 README txt drwxrwxrwx
65. or deny requests to private and public cloud projects Using XIV in OpenStack Environments IBM Cloud Manager includes a Chef Server that allows for the automation of the deployment process It uses Chef Cookbooks and recipes to customize for the specific hardware that is used at installation IBM Cloud Manager can install OpenStack as well as any necessary drivers such as the IBM Storage Driver for OpenStack in our case Cloud Manager also enables easy hybrid configuration deployments Figure 1 7 depicts the architecture that is used in IBM Cloud Manager IBM Cloud Manager with OpenStack 4 1 architecture amp 20 po Openstack Cloud Admin Cloyd User SCE Cloud openstack Applicaffons Aplications e Ca Do CN SCE API f H User management Project Network mapping Cloud admin oz y VM management Adapter 9 laaS gateway federation Approvals i i Billing accounts Y T Y API stack icehou AS a open i se Bea a Users Projects Tenants Domains Storage configs Network configs Image Repolmgt image Flavors scheduling PowerVC driver i F 4 E f 1 On Power not in CIAO U8 come Figure 1 7 IBM Cloud Manager architecture IBM Cloud Manager like a plain OpenStack environment supports the operating systems that are listed in Table 1 1 Table 1 2 on page 12 and Figure 1 8 on page 12 Table 1 1 Supported operating systems for the Cloud Manager Cloud Manager Host operating system RHEL 6 5 or Mi
66. orizon automation to support the XIV and DS8000 in Horizon automated volume host and initiator creation and contributed to the development of Cinder The rest of this section covers the required steps to integrate the XIV into an OpenStack environment This section assumes that the OpenStack installation is complete and that you are ready to integrate the XIV storage into the cloud For the purposes of this paper the configuration in Figure 3 2 on page 25 is used 24 Using XIV in OpenStack Environments Nova Node 2 Compute Node Fibre Channel Attachment XIV Gen3 Nova Node 1 Controller Horizon Cinder Network Compute Node IBM Storage Driver for OpenStack Fibre Channel Attachment Figure 3 2 OpenStack test configuration The back end storage consists of two XIV Gen3 Storage Systems that connect to the two servers over Fibre Channel for access to the storage Additionally the server that is labeled Nova Node 1 which contains the controller Horizon and Cinder nodes as well as the IBM Storage Driver for OpenStack is able to communicate with the XIV systems over the Internet Protocol IP network to issue commands through the application programming interface API interface The server that is labeled Nova Node 2 is a compute node Both of these nodes servers make up the initial OpenStack environment 3 1 1 Preparing the XIV for OpenStack The IBM Storage Driver for OpenStack requires you to predefine at lea
67. reate a dedicated directory which we named itso cloud for the cloud setup Change the permissions on that directory so that the new directory is the current directory as shown in Example 4 8 on page 37 Example 4 8 Cloud directory root deployment server mkdir itso cloud root deployment server cd itso cloud root deployment server itso cloud Create and modify or customize the sample config json files We will use these files from the deployment server for the deployment of the OpenStack setup and configuration on the OpenStack nodes json file for the environment json file for the topology Examples are shown in the CMOQuickStartGuide for these two json files with instructions to customize the files On the deployment server Chef Server you can list the predefined environment s repository repo files as shown in Example 4 9 Example 4 9 Predefined environment files listed root deployment server itso cloud knife environment list example ibm os allinone example ibm os single controller n compute example ibm sce root deployment server itso cloud You can also use the knife command features to show the content of the environment repo files Example 4 10 shows the content of the IBM predefined example ibm sce repo self service portal file This repo file shows the list of used required packages and their version Example 4 10 Content of the IBM predefined example ibm sce environme
68. s well as hosts which were already available before the 11 5 release Figure 1 5 on page 9 is a simple illustration of how multi tenancy can be set up with an XIV Storage System Illustrated in this example are three domains A B and C and the resources that are associated with those domains This example also shows how hosts or servers can be isolated to pools in a domain or how hosts or servers can see pools for more than one domain The same is true for users that are associated with domains For more information about the XIV multi tenancy see the X V Storage System Architecture and Implementation SG24 7659 Using XIV in OpenStack Environments Figure 1 5 XIV multi tenancy 1 3 2 OpenStack with XIV multi tenancy An OpenStack implementation that uses the XIV as the back end storage does not require XIV multi tenancy However the feature can be incorporated in a cloud environment that is managed by OpenStack to further separate and isolate projects tenants The OpenStack configuration is described in subsequent chapters of this paper For a simple view of how XIV multi tenancy might be used in an OpenStack environment see Figure 1 6 on page 10 In this example the OpenStack nodes are labeled as Nova Node 1 and Nova Node 2 discussed in more detail around Figure 3 2 on page 25 These nodes are both associated with Domain B The OpenStack administrator is also a domain administrator that is associated with Domain
69. st one storage pool on the XIV before the installation The specific pool is required when you run the installation script For this paper we defined a pool on the XIV with 5 TB and named it ITSO_CM_PFE2_P1 on the XIV system that is named XIV PFEZ 1340010 as shown in Example 3 1 Example 3 1 XIV storage pool XIV_PFE2_1340010 gt gt pool_list pool ITSO CM PFE2 P1 Name Size GB Soft Vols GB Snap Size GB Soft Empty GB Hard Size GB ITSO CM PFEZ Pl 5007 0 516 5007 5007 Tip OpenStack requires at least 1 TB of pool capacity Configure the pool on the XIV with adequate capacity for your environment Pools can be resized later however resizing pools later requires reconfiguration in OpenStack Chapter 3 Integrating the XIV in the OpenStack environment 25 The next step is to define the hosts or nodes to attach to the XIV In our case we configured two compute nodes in a cluster to enable moving resources or virtual machines VMs between the compute nodes Figure 3 3 shows the definition of the cluster that is used for this paper Standalone Hosts i6 no domain iT no domain 33 ITSO_ESX_Cluster no domain ITSO do ITSO IBM Cloud Manager Cluster no domain openstack compute mainz ibm com default enstack controller mainz ibm com default Figure 3 3 Cluster definition for OpenStack After the hosts or clusters are defined the zoning is performed on the switch You can perform the zoning before you define
70. support for the open standards in OpenStack in Nova Cinder Swift and Neutron as well as others Workload definition Optimization amp Orchestration Application amp Infrastructure Patterns Resource Abstraction amp Optimization IBM OpenStack Platform IBM Platform Resource Scheduler a openstack IBM IBM IBM Compute Storage Network Figure 1 2 IBM with OpenStack The XIV Storage System with Icehouse the latest versions of OpenStack at the time of writing and referred to as OpenStack in the remainder of this paper offers an open source cloud implementation This implementation allows organizations to deploy cloud computing capabilities on standard hardware Chapter 1 OpenStack and IBM Cloud Manager overview 3 4 OpenStack Storage has support for both object Swift and block Cinder storage capabilities Object storage via the Swift node is a distributed storage system for data such as virtual machine images photographs videos and similar objects or files Block storage via the Cinder node is more traditional type storage that attaches to block devices The volumes for block storage are integrated into the OpenStack Compute and the Dashboard so that users can manager their own storage needs There are several OpenStack releases For the latest information see the following website http www openstack org software The Icehouse release of OpenStack included updates to b
71. t http www ibm com legal copytrade shtm The following terms are trademarks of the International Business Machines Corporation in the United States other countries or both developerWorks PowerVM System Storage DS6000 Redbooks System z DS8000 Redpaper XIV IBMO Redbooks logo O z VM IBM SmartCloud System p The following terms are trademarks of other companies Intel Intel logo Intel Inside logo and Intel Centrino logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries Linux is a trademark of Linus Torvalds in the United States other countries or both Microsoft Windows and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both Other company product or service names may be trademarks or service marks of others vi Using XIV in OpenStack Environments Preface This IBM Redpaper publication provides a brief overview of OpenStack and IBM Cloud Manager with OpenStack It focuses on the use of OpenStack with the IBM XIVO Storage System Gen3 The illustration scenario in the paper uses the OpenStack Icehouse release which is installed on RedHat Linux servers and the IBM Storage Driver for OpenStack This paper is intended for clients and cloud administrators who look forward to integrating IBM XIV Storage Systems in OpenStack and using IBM Cloud Manager with OpenStack
72. tack El block storage E volume create volume group volume group size E xiv ds8k search editor source ee type string a ITSO CM PFE2 P1 Path json openstack block storage xiv_ds8k san_clustername Mode Standard C Autodetect type of attribute Save Attribute san password volume driver xiv chap xiv ds8k connection type verbose identity Emei A JSON hash for default attributes for nodes of this node These attributes will only be applied if the node does not already have a value for the attributes Figure 4 7 Chef Server view of the controller node 50 Using XIV in OpenStack Environments IBM Cloud Manager with OpenStack can be installed on multiple operating system platforms For the scenario in this paper we used a 64 bit RedHat Linux operating environment RHEL 6 5 64 bit x86 To install IBM Cloud Manager with OpenStack on the deployment server follow the steps that are outlined in the Cloud Manager with OpenStack Administration Guide which is available at this website https www ibm com developerworks community wikis home lang ent wiki W2led5ba0f4 a9 46f4 9626 24cbbb86fbb9 page Documentation After the Cloud Manager with OpenStack is installed with the latest fix pack you can configure the cookbook for XIV storage Follow these steps 1 Run from the deployment server The Chef Server manages the installations 2 Configure multiple back ends in cinder co
73. that are added by default These users are necessary for the components that are shown in Figure 2 4 To create and manage roles see the following instructions in the User Administration Guide http docs openstack org user guide admin content section dashboard admin manage roles html Creating a project A project or tenant is set up to isolate resources in a cloud environment for example to ensure that Tenant A does not have access to resources that belong to Tenant B in a private cloud To create and manage projects in OpenStack use the Project section in the User Administration Guide http docs openstack org user guide admin content dashboard manage projects users html Using XIV in OpenStack Environments To create a project in the Cloud Management Dashboard click ADMIN gt Identity Panel gt Projects as shown in Figure 2 5 Cloud Management Dashboard PROJECT x Projects ADMIN Projects Q me Delete Projects System Panel Identity Panel O Name Description Project ID Enabled Actions Projects E admin 4 admin Tenant Ofac5144e5c74b5097148 757937d4fb True Modify Users More Users ITSO project 4 Testproject Ta34dfd55d214ce6b8d30452823c2564 True Modify Users More E Public 4 This is the default project for all existing Cloud resources 8a54e991894b4c7aba0Bb596e16e7d19 True Modify Users More senice Service Tenant 628bdb6323ed40fd918afadee9701d41 True Modity Users More Figure 2 5 Create a project
74. tion and automates tasks such as deployment configuration patching backups restores and monitoring In addition to these core projects there are a number of incubation projects that are being considered for future inclusion in the OpenStack core Information about the future enhancements to OpenStack is available at the following web page http www openstack org software roadmap 1 3 OpenStack and XIV multi tenancy With the release of Version 11 5 software the XIV introduced support for multi tenancy Multi tenancy enables cloud providers to divide and isolate the XIV resources into logical domains which can then be used by tenants without any knowledge of the rest of the system resources From the storage administrator s view it is a simple and quick delegation of resources and user permissions It enables the management of multiple tenants securely and simply in the same XIV 1 3 1 XIV multi tenancy and domains 8 The XIV uses the concept of domains for multi tenancy A domain represents a subset of resources that include users pools volumes hosts and clusters snapshots snapshot groups and mirroring Some of these resources can be shared among multiple domains such as users and hosts clusters Other features that are enabled in the XIV multi tenancy feature include allowing the main storage administrator known as the global administrator to set up a quality of service QoS for domains and pools independently a
75. tional materials at the following website ibm com redbooks Other publications These publications are also relevant as further information sources vvvvvvy IBM XIV Remote Support Proxy Installation and User s Guide GA32 0795 IBM XIV Storage System Application Programming Interface GC27 3916 IBM XIV Storage System Planning Guide GC27 3913 IBM XIV Storage System Product Overview GC27 3912 IBM XIV Storage System User Manual GC27 3914 IBM XIV Storage System Management Tools Version 4 0 User Guide SC27 4230 00 IBM XIV Storage System XCLI Utility User Manual GC27 3915 Online resources These websites are also relevant as further information sources gt IBM XIV Storage System Information Center http www publib boulder ibm com infocenter ibmxiv r2 index jsp IBM XIV Storage System website http www ibm com systems storage disk xiv index html IBM System Storage Interoperability Center SSIC http www ibm com systems support storage config ssic index jsp Copyright IBM Corp 2015 All rights reserved 65 Storage Networking Industry Association SNIA website http www snia org gt IBM Director software download matrix page http www ibm com systems management director downloads html gt IBM Systems Director documentation http www ibm com systems management director Help from IBM IBM Support and downloads ibm com support IBM Global Services ibm com services 66 Using XIV
76. to the controller node Configure the database that is required to store information Install and configure the OpenStack packages Install and configure the Messaging service Install and configure the Identity service ON O 0 A Install and configure the OpenStack clients 9 Install and configure the Image service 10 Install and configure the Compute services 11 Install the Dashboard Horizon 12 Add the Block Storage service Cinder 13 Add the Orchestration service 14 Add the Telemetry service 15 Add the Database service For the full set of installation instructions see the OpenStack documentation website http docs openstack org Now you can configure and launch an instance An instance exists on a node Volumes are created through OpenStack either through the command line or the Dashboard and they are associated with an instance The volumes can then be used by the instance similarly to an external drive Chapter 2 OpenStack environment 19 2 2 3 Creating users roles and projects 20 After OpenStack is installed the next step is to configure users roles and projects or tenants You can configure users roles and projects or tenants before you attach any back end storage such as the XIV as well as prepare operating system disk images to use with the VMs or instances Creating a user Users with associated roles can be created with OpenStack and must be created to manage the envir
77. ve the servers SAN and IP switches that are required to set the environment See Table 2 1 on page 17 For the latest information see the release notes at this website http pic dhe ibm com infocenter strhosts ic topic com ibm help strghosts doc nov a_pdfs html Chapter 2 OpenStack environment 15 16 Hardware specifications There are several ways to implement the Nova OpenStack infrastructure Consider single node and multiple node configurations gt Single node This configuration cannot deliver the performance that most cloud environments require A virtualized environment can be enough to deploy this configuration gt Multiple nodes In this environment Nova components can be distributed across several systems Use this setup for a typical production environment In either case the recommended hardware for the controller and compute nodes is the same as though these nodes were intended to run on standard hardware The minimum deployment recommendations are listed in Table 2 1 on page 17 Verify this information with the latest recommendations which are listed in the OpenStack website http docs openstack org grizzly openstack compute instal1 yum content compute sy stem requirements html Also OpenStack does not require significant resources to create a functional environment At a minimum the following resources can support multiple minimal instances Controller node One processor 2 GB memory and 5 GB storage
78. w This chapter provides a brief overview of the following topics gt OpenStack components and terminology gt OpenStack and the IBM XIV Storage System multi tenancy IBM Cloud Manager with OpenStack Definition and functions O Copyright IBM Corp 2015 All rights reserved 1 1 OpenStack overview 2 With the availability of the IBM Storage Driver for OpenStack the XIV Storage System can offer a range of capabilities that enable more effective storage automation deployments into private or public clouds Enabling OpenStack with the XIV allows for storage to be made available whenever it is needed without the traditional associated costs of highly skilled administrators and infrastructure Cloud computing is defined as the use of computing services and resources hardware and software that are delivered over a network typically Ethernet Cloud computing allows for more economical usage of the data center hardware and software It entrusts remote services with a user s data software and computation OpenStack is being developed as cloud computing project to provide an Infrastructure as a service laaS It is managed by the OpenStack Foundation It was started by Rackspace Hosting and NASA in 2010 Currently more than 200 companies have joined the project including IBM OpenStack is a no charge open source software release under the terms of the Apache license The releases are built around a six month cycle The release that
79. was used for this paper is Icehouse April 2014 The Juno release was October 2014 OpenStack has a modular architecture that encompasses the three pillars of compute storage and networking to make cloud deployment and operations easier as depicted in Figure 1 1 Your Applications OPENSTACK CLOUD OPERATING SYSTEM a OpenStack Dashboard AO a OpenStack Shared Services Standard Hardware Figure 1 1 OpenStack cloud computing Several core projects in OpenStack are listed Compute Nova Networking Neutron Object Storage Swift Block storage Cinder Image service Glance Identity Management Keystone Dashboard Horizon vvvvvvy Using XIV in OpenStack Environments OpenStack Compute Nova is a cloud computing fabric controller the main part of an laaS system Itis written in Python and uses many external libraries such as Eventlet for concurrent programming Kombu for Advanced Message Queuing Protocol communication and SQLAlchemy for database access IBM with the OpenStack community is on a mission to provide scalable elastic cloud computing for both public and private clouds large and small The cloud must be simple to implement and massively scalable OpenStack is a fundamental element in the IBM Software Defined Environment SDE strategy As seen in Figure 1 2 IBM is fully engaged in furthering the OpenStack possibilities As seen here IBM has built
80. y to access the VMs to users Horizon Dashboard provides a modular web based user interface for all the OpenStack services With this web GUI you can perform most operations on your cloud You can create volumes launch an instance assign IP addresses and set access controls gt Keystone Identity provides authentication and authorization for all the OpenStack services It also provides a service catalog of services within a particular OpenStack cloud gt Cinder Block Storage provides persistent block storage to guest VMs This project came out of code that was originally in Nova the nova volume service The IBM Storage Driver for OpenStack which is fully supported by Cinder provides block storage as a service via iSCSI to VMs Cinder virtualizes pools of block storage devices and provides users with a self service API to request and consume storage resources without needing to know where the storage physically resides Cinder replaces the nova volume which was part of the Nova component starting with the Folsom release For more details about Cinder and the IBM Storage Driver for OpenStack see this web page http wiki openstack org Cinder gt Swift Object Store provides object storage and allows users to store or retrieve files ina blob mode It is built for scale out networks and it is ideal for storing unstructured data that can group without bounds gt Glance Image provides a catalog and repository for d

Using XIV in OpenStack Environments

Contents

Download Pdf Manuals

Related Search

Related Contents