rackspace.com/cloud/private

Transcription

1 rackspace.com/cloud/private

2 Rackspace Private Cloud Software v 3.0 ( ) Copyright 2013 Rackspace All rights reserved. This guide is intended to assist Rackspace customers in downloading and installing Rackspace Private Cloud Software, powered by OpenStack. The document is for informational purposes only and is provided AS IS. RACKSPACE MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, AS TO THE ACCURACY OR COMPLETENESS OF THE CONTENTS OF THIS DOCUMENT AND RESERVES THE RIGHT TO MAKE CHANGES TO SPECIFICATIONS AND PRODUCT/SERVICES DESCRIPTION AT ANY TIME WITHOUT NOTICE. RACKSPACE SERVICES OFFERINGS ARE SUBJECT TO CHANGE WITHOUT NOTICE. USERS MUST TAKE FULL RESPONSIBILITY FOR APPLICATION OF ANY SERVICES MENTIONED HEREIN. EXCEPT AS SET FORTH IN RACKSPACE GENERAL TERMS AND CONDITIONS AND/OR CLOUD TERMS OF SERVICE, RACKSPACE ASSUMES NO LIABILITY WHATSOEVER, AND DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO ITS SERVICES INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT. Except as expressly provided in any written license agreement from Rackspace, the furnishing of this document does not give you any license to patents, trademarks, copyrights, or other intellectual property. Rackspace, Rackspace logo, Fanatical Support, and OpenCenter are either registered trademarks or trademarks of Rackspace US, Inc. in the United States and/or other countries. OpenStack is either a registered trademark or trademark of the OpenStack Foundation in the United States and/or other countries. Third-party trademarks and tradenames appearing in this document are the property of their respective owners. Such third-party trademarks have been printed in caps or initial caps and are used for referential purposes only. We do not intend our use or display of other companies tradenames, trademarks, or service marks to imply a relationship with, or endorsement or sponsorship of us by, these other companies. License Information OpenCenter is Copyright 2013 by Rackspace US, Inc. OpenCenter is licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. This version of OpenCenter includes Rackspace trademarks and logos, and in accordance with Section 6 of the License, the provision of commercial support services in conjunction with a version of OpenCenter which includes Rackspace trademarks and logos is prohibited. OpenCenter source code and details are available at: or upon written request. You may obtain a copy of the License at and a copy, including this notice, is available in the LICENSE.TXT file accompanying this software. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. ii

3 Table of Contents 1. Overview... 1 Intended Audience... 1 Document Change History... 1 Additional Resources... 1 Contact Rackspace About Rackspace Private Cloud Software... 3 What is Rackspace Private Cloud Software?... 3 About OpenCenter... 3 The Rackspace Private Cloud Configuration... 4 Supported OpenStack Features... 4 Unsupported OpenStack Features... 5 Rackspace Private Cloud Support Installation Prerequisites and Concepts... 6 Hardware Requirements... 6 OpenCenter and Chef Server Requirements... 6 Cluster Node Requirements... 6 Deploying OpenCenter in an All-VM Environment... 7 Software Requirements... 7 Network Requirements... 7 Preparing For the Installation... 7 Node Access Considerations... 8 Instance Access Considerations... 8 High Availability Concepts... 9 Availability Zone Concepts Installing Rackspace Private Cloud Software Prepare the Nodes Install OpenCenter Server, Agent, and User Interface Install OpenCenter Server Install the OpenCenter User Interface Install OpenCenter Agent Verify Environment Access the Operator GUI Create Chef Server Create a Nova Cluster Upload Glance Images Configure Cluster for High Availability Create Additional Availability Zones Evacuating a Host Troubleshooting the Installation Installing Rackspace Private Cloud Software on a Single Device with Virtual Machines Prepare the Device and VMs Create the OpenCenter Environment Accessing the Cloud Accessing the Controller Node Accessing the Dashboard Restoring the Default OpenStack Dashboard Using Your Logo In the OpenStack Dashboard iii

4 Accessing the Graphite Monitoring Tool OpenStack Client Utilities Viewing and Setting Environment Variables Creating an Instance in the Cloud Image Management Create a Project Generate an SSH Keypair Update the Default Security Group Create an Instance Accessing the Instance Logging In to the Instance Accessing the Instance By SSH on the Compute Node Managing Floating IP Addresses What's next? Configuring OpenStack Image Storage Local File Storage Rackspace Cloud Files Swift Storage Glossary of Terms iv

5 1. Overview Rackspace has developed Rackspace Private Cloud Software, a fast, free, and easy way to deploy a Rackspace Private Cloud powered by OpenStack in any data center. Rackspace Private Cloud Software is suitable for anyone who wants to install a stable, tested, and supportable OpenStack private cloud, and can be used for all scenarios from initial evaluations to production deployments. Rackspace Private Cloud Software v 3.0 supports the Folsom release of OpenStack. Intended Audience This guide is intended for anyone who wants to deploy an OpenStack-powered cloud that has been tested and optimized by the OpenStack experts at Rackspace. This document includes an overview of Rackspace Private Cloud Software and instructions for downloading and deploying Rackspace Private Cloud Software in the data center of your choice. To use the product and this document, you should have prior knowledge of OpenStack and cloud computing, basic Linux administration skills, and a side of bacon. :) Document Change History This version of the Rackspace Private Cloud Software replaces and obsoletes all previous versions. The most recent changes are described in the table below: Revision Date Summary of Changes August 15, 2012 Release of Rackspace Private Cloud Software v 1.0. November 15, 2012 Release of Rackspace Private Cloud Software v 2.0. Added information about Folsom implementation, OpenStack Block Storage, changing the Horizon dashboard, proxy settings, changing rate limits, updating the cookbooks, and configuring OpenStack Image Storage to use Rackspace Cloud Files. March 6, 2013 Release of Rackspace Private Cloud Software v 3.0. Additional Resources OpenCenter deployment and management framework introduced. Rackspace Private Cloud Software Knowledge Center OpenStack Manuals OpenStack API Reference OpenStack - Nova Developer Documentation OpenStack - Glance Developer Documentation OpenStack - Keystone Developer Documentation OpenStack - Horizon Developer Documentation OpenStack - Cinder Developer Documentation 1

6 Contact Rackspace For more information about sales and support, contact us at For feedback on the product and the documentation, contact us at For the documentation, you can also leave a comment at the Knowledge Center. For more troubleshooting information and user discussion, you can also inquire at the Rackspace Private Cloud Support Forum at the following URL: privatecloudforums.rackspace.com 2

7 2. About Rackspace Private Cloud Software This chapter describes the Rackspace Private Cloud configuration and support offerings. What is Rackspace Private Cloud Software? Rackspace Private Cloud Software enables users to quickly deploy an OpenStack cluster configured according to the recommendations of Rackspace OpenStack specialists, using the OpenCenter deployment and management framework. Previous versions of Rackspace Private Cloud Software were packaged in an ISO that contained a full Ubuntu OS and a Chef server running on a virtual machine. While the ISO was a convenient and simple package, it did not allow a deployment at scale. The user also had no choice of host operating system and Chef server running on a virtual machine was resource-intensive. Rackspace Private Cloud Software now implements a new deployment approach that enables users to create an OpenStack cluster on Ubuntu, CentOS, or RHEL, and create a dedicated server for Chef. The new version uses install scripts to install Debian or RPM packages on servers, creating a more traditional application experience for the Linux system administrator. It also offers a framework that is capable of being updated without downloading and deploying a whole new ISO. About OpenCenter OpenCenter enables cloud administrators to manage the architecture of their OpenStack private cloud through a GUI, command line interface (CLI), or API. With OpenCenter, you can perform the following tasks: Create a Chef server that will manage multiple OpenStack nodes. Deploy Controller nodes and hypervisors directly to Ubuntu, CentOS, or RHEL servers or virtual machines. Deploy and manage an OpenStack cluster in an environment. Enable high availability. OpenCenter is compatible with the following operating systems: Ubuntu CentOS 6.3 RHEL 6.3 or 6.4 OpenCenter has three components: OpenCenter Server: The server manages the OpenCenter environment. 3

8 OpenCenter Agent: The agent is installed on each node that will be managed by OpenCenter. OpenCenter GUI: A web interface for using OpenCenter. Note Rackspace recommends that you run OpenCenter behind a firewall, as it is not considered secure at this time. The Rackspace Private Cloud Configuration Rackspace Private Cloud Software v 3.0 uses the Folsom release of OpenStack, and includes Compute (Nova), Image Service (Glance), Dashboard (Horizon), and Identity (Keystone). Virtual Network Service (Quantum) is not supported at this time. Supported OpenStack Features Rackspace supports integration with the other components of OpenStack, as well as features such as floating IP address management, security groups, availability zones, and the python-novaclient command line client. The following OpenStack features are also supported in OpenStack clusters deployed with OpenCenter: Single and dual NIC configurations NFS and ISCSI file storage as backing stores for VM storage VNC Proxy KVM hypervisor Nova Multi Scheduler instead of Filter Schedule Keystone integrated authentication Glance integrated image service Horizon dashboard Linux and Windows guests to the extent to which they accept handoff from KVM and boot Single metadata server running on each device Cloud management through OpenStack APIs High availability for all Nova service components and APIs, Cinder, and Keystone, as well as the scheduler, rabbitmq, and mysql. The following OpenStack features are not deployed with OpenCenter, but can be manually configured with Rackspace Private Cloud Software Chef cookbooks: Cinder block storage service, documented in Rackspace Private Cloud Software: OpenStack Block Storage Swift object storage service, documented in Rackspace Private Cloud Software: OpenStack Object Storage Rackspace Private Cloud Software also supports the use of Rackspace Cloud Files as a backend for OpenStack Image Storage. 4

9 Unsupported OpenStack Features The following features are not supported: Nova object store Nova volumes Boot-from-volume for guest VMs Clustered file system solutions xpvnc Xen and other hypervisors Centralized metadata servers Any other OpenStack project, extension or configuration not explicitly listed in the supported features or installed components sections Rackspace Private Cloud Software is an evolving product and we will continue to develop and enhance it. Rackspace Private Cloud Support Rackspace Private Cloud Software is offered primarily as a "do it yourself" package, free of charge. You can also access the Rackspace Private Cloud Support Forum, a Rackspaceprovided user forum, at the following URL: The forum is open to all Rackspace Private Cloud users and is moderated and maintained by Rackspace personnel and OpenStack specialists. Rackspace offers 365x24x7 support for Rackspace Private Cloud Software. If you are interested in purchasing Rackspace Private Cloud Escalation Support or Core Support, or you plan to install on more than 20 nodes, please us at <opencloudinfo@rackspace.com>. 5

10 3. Installation Prerequisites and Concepts This chapter discusses the prerequisites for installing Rackspace Private Cloud Software. Hardware Requirements Rackspace has tested two hardware-based scenarios for Rackspace Private Cloud Software deployment, with different hardware requirements. A physical device for each required node: an OpenCenter server, a Chef server, an OpenStack Nova Controller node, and additional physical machines with OpenStack Nova Compute nodes as required. One physical device with VMs configured for the OpenCenter Server and Chef server, and the OpenStack Nova Controller node installed on the host, and additional physical machines for the OpenStack Nova Compute nodes as required. For information about this configuration, refer to "Installing OpenCenter in a Virtual Machine Configuration". OpenCenter and Chef Server Requirements Rackspace recommends that the OpenCenter server meets the following minimum requirements: 8 GB RAM 144 GB disk space Dual socket CPU with dual core. A dual socket CPU with a hex core (for a total of 6-12 cores) will provide better performance. The Chef server hardware should meet the following requirements: 16 GB RAM 144 GB disk space Dual socket CPU with dual core, or single socket quad core Cluster Node Requirements Each node in the cluster will have the OpenCenter agent installed on it. The hardware requirements vary depending on the purpose of the node. Each device should support VT-x. Refer to the following table for detailed requirements. Node Type Nova Controller Nova Compute Requirements 16 GB RAM 144 GB disk space Dual socket CPU with dual core, or single socket quad core 32 GB RAM 144 GB disk space Dual socket CPU with dual core, or single socket quad core CPU overcommit is set at 16:1 VCPUs to cores, and memory overcommit is set to 1.5:1. Each physical core can support up to 16 virtual cores; for example, one dual-core processor 6

11 can support up to 32 virtual cores. If you require more virtual cores, adjust your sizing appropriately. Deploying OpenCenter in an All-VM Environment For testing purposes, it is also possible to deploy Rackspace Private Cloud Software on a group of virtual machines, such as a group of Rackspace Cloud Servers. The virtual machines should meet specifications similar to the standard hardware specifications, though it is possible for the Chef server, Controller, and Compute nodes to be as small as 8 GB if you are only doing proof-of-concept tests. Software Requirements The device on which OpenCenter Server is installed and all OpenCenter-managed devices must be using one of the following operating systems: Ubuntu CentOS 6.3 RHEL 6.3 or 6.4 The GUI package can also be installed on OS X. Network Requirements Internet access is required to complete the installation, so ensure that the devices that you use have internet access to download the installation files. Rackspace Private Cloud Software creates a FlatDHCP network in multi_host mode, in which nova-network software is installed and configured on each server that is running nova-compute. Further conceptual information about Flat DHCP networking is available in the OpenStack Compute Administration Manual. Refer to the following topics: Configuring flat DHCP networking Libvirt Flat DHCP Networking Preparing For the Installation Before you begin, have the following networking information prepared and available: The Nova public network in CIDR format. The Nova public network interface (such as eth0). The Nova VM network bridge (such as br100). Optional NAT exclusion CIDR range or ranges for networks configured with a DMZ, The name of the Nova cluster. A password for an admin OpenStack user. 7

12 Nova management network address in CIDR format. The interface of the VM network for the Compute notes (such as eth1). The name of the default availability zone. The VM network CIDR range. The Nova internal network CIDR range that you want to assign to each Controller and Compute node. Node Access Considerations All nodes within the OpenCenter environment must be able to access one another. Provided that the nodes on which the agent is installed have outbound connectivity to the OpenCenter server, the nodes can be physically located anywhere. All communication between the server and agent runs from the agent to the server. Currently, if you delete the agent from a node, you will have to manually delete the node from the server with the opencentercli node delete command in the command line interface. Instance Access Considerations By default, the instances that you create in the OpenStack cluster can only be publicly accessed via NAT by assigning floating IP addresses to them. Before you assign a floating IP address to an instance, you must have a pool of addresses to choose from. Your network security team must provision an address range and assign it to your environment. These addresses need to be publicly accessible. Floating IP addresses are not specified during the installation process; once the Controller node is operational, you can add them with the nova-manage floating create --ip_range command. Refer to "Managing Floating IP Addresses". 8

13 You can also make the instances accessible to other hosts in the network by default by configuring the cloud with a network DMZ. The network DMZ range cannot be the same as the nova fixed network range. Specifying a DMZ enables NAT-free network traffic between the virtual machine instances and resources outside of the nova fixed network. For example, if the nova fixed network is /16 and you specify a DMZ of /12, any devices or hosts in that range will be able to communicate with the instances on the nova fixed network. To use the DMZ, you must have at least two NICs on the deployment servers. One NIC must be dedicated to the VM instances. High Availability Concepts Rackspace Private Cloud Software has the ability to implement support for high availability for all Nova service components and APIs, Cinder, and Keystone, and Glance, as well as the scheduler, rabbitmq, and mysql. HA functionality is powered by Keepalived and HAProxy. High Availability is implemented when you create two Controller nodes in a Nova cluster. When the second node is created, it discovers the IP address of the first node and begins replication; in turn, when Chef client runs on the first node, it discovers the second and begins replication. Availability Zone Concepts Availability zones enable you to manage and isolate different nodes within the environment. For example, you may want to isolate different sets of Compute nodes to provide different resources to customers. If one availability zone experiences downtime, other zones in the cluster will not be affected. 9

14 When you create a Nova cluster with OpenCenter, it is created with a default availability zone, and all Compute nodes will be assigned to that zone. You can create additional availabilty zones within the cluster as needed. 10

15 4. Installing Rackspace Private Cloud Software This chapter discusses the process for installing Rackspace Private Cloud Software and using OpenCenter to deploy an OpenStack cluster. Prepare the Nodes Each node in the OpenCenter environment must have Ubuntu 12.04, CentOS 6.3, or RHEL 6.3 or 6.4 installed. Before you begin, ensure that the OS is up to date on the devices. Log into each device and run the appropriate update for the OS and the package manager. Install OpenCenter Server, Agent, and User Interface Your OpenCenter environment must have an OpenCenter server and have the OpenCenter agent installed on every node that will be managed by the server, and you must install the GUI component to manage the environment through the GUI. You must install the server first. Agent installations in the environment will ping the server and indicate that they are available for further configuration. Instead of the ISO that was used in previous versions, installation is now performed via a curl command that launches an installation script. The script downloads the packages from packages.opencenter.rackspace.com and uses the packages to install the OpenCenter components. Install OpenCenter Server Execute the following curl command on the device that will become the OpenCenter server: $ curl -s -L \ sudo bash -s server When the installation is complete, you will receive a confirmation message indicating that OpenCenter server has been installed correctly. You will also receive a message notifying you of where you can find the default server admin user name and password, which you will use to log into the dashboard and set the endpoint environment variable in the CLI. If you need to change the username and password, you will also need to edit the agent endpoint with the new username and password. 11

16 Before you can use the CLI, you must set the OPENCENTER_ENDPOINT variable in your environment. You will need the admin username and password from the server installation. Run the following command: $ export OPENCENTER_ENDPOINT= If you change the admin username and password in the OpenCenter configuration file, you will need to set your endpoint environment variable again. At this time you can run the opencentercli node list command to view the current node configuration. $ opencentercli node list id name task adventure attrs facts workspace None None {} {u'backends': [u'container... 2 unprovisioned None None {} {u'parent_id': 1, u'backen... 3 support None None {} {u'parent_id': 1, u'backen... By default, the OpenCenter server is created with three nodes: workspace: The "master" parent container for the OpenCenter environment. unprovisioned: The parent container for all nodes that have the OpenCenter agent installed, but that have not been assigned a role yet. support: The parent container for all nodes that are used to maintain the OpenCenter environment infrastructure and for external resources. The Chef server is automatically assigned to the support node as soon as it is configured. You will need the IP address of the OpenCenter server to proceed with the installation of the OpenCenter agent. This can be obtained with the ifconfig command. Install the OpenCenter User Interface You can install the OpenCenter GUI on any device from which you want to manage your environment, but first you should install it on the server node. When the OpenCenter server installation is complete, execute the following curl command on the server node: $ curl -s -L \ sudo bash -s dashboard <OpenCenter-server-IP> You can now use your web browser to access the OpenCenter GUI via the IP address of the device on which you installed the GUI. For example, if you installed it on a server with the IP address , you would access the GUI via browser at Log in with the username and password from the server installation. Install OpenCenter Agent Run the following curl command on each node that will be managed with OpenCenter: 12

17 $ curl -s -L \ sudo bash -s agent <OpenCenter-server-IP> When the installation is complete, you will receive a confirmation message indicating that OpenCenter agent has been installed correctly. You will receive a message notifying you of the current agent endpoint settings, incorporating the username and password from the server installation. You will need to change these settings if you change the OpenCenter admin username and password. Repeat this process on each node. Verify Environment After the agent has been installed on each managed server, you can verify the environment either via GUI or the CLI. To view the GUI, simply use your web browser to access the GUI as described in "Install the OpenCenter User Interface". To use the CLI. run the opencentercli node list command on the OpenCenter server to view the OpenCenter environment. The newly configured nodes will appear in the list. The node names are the names that were assigned when you originally installed and configured the operating system on those nodes. $ opencentercli node list id name task adventure attrs facts workspace None None {...} {u'backends':... 2 unprovisioned None None {...} {u'parent_id':... 3 support None None {...} {u'parent_id':... 4 chef-server None None {...} {u'parent_id':... 5 controller None None {...} {u'parent_id':... 6 compute None None {...} {u'parent_id':... Access the Operator GUI When you first log into the GUI, you will see a collection of available nodes, as well as the OpenCenter server in the Service Nodes container. Your environment is now ready for configuration. By clicking on the cog icon next to a section or node name, you can perform the actions available to that node. The following table describes the features and containers of the operator GUI. Workspace Available Nodes Service Nodes Feature/Container Description The overview of the OpenCenter environment. Each node on which the OpenCenter agent has been installed but which has not been configured will appear in this section. Contains the nodes that manage the environment. The OpenCenter server will be included in this container. Do not attempt to move it out of this container. 13

18 NovaCluster Feature/Container Description When the Chef server is created, it will be added to this section. Does not appear until after you have created a Chef server and created a Nova cluster. NovaCluster is the default name; you can edit it when you create the cluster. When created, contains two sub-containers: An Infrastructure container, where the Controller node is located. A Compute container, where the availability zones and Compute nodes are located. Create Chef Server The first node that you will create is a Chef server, which is required to manage the OpenStack nodes. Do not create more than one Chef server in your environment. Follow these steps to use OpenCenter to create a Chef server. 1. Select an available node and click on the cog icon. 2. In the drop-down menu that appears, select Install Chef Server. The Chef server installation will take about five minutes. In the Tasks pane (hidden by default at the bottom of the UI) system will stream a log to show the status of the installation, and you can also monitor the progress by logging into the node and using the tail -f command to monitor /var/log/opencenter/trans_n.log. When the installation is complete, the new Chef server will appear in the Service Nodes group. You can also view the Chef server management console in your browser at Most users will not need to use this feature, but in the event that you do, refer to the Opscode Chef Management Console documentation for more information about the management console. At any time, you can download the latest cookbooks, but this is done automatically during the installation process. If in the future you want to ensure that you have the latest cookbooks, follow this procedure. 1. Click on the cog icon on the Chef server node. 2. In the drop-down menu that appears, select Download Chef Cookbooks. The Chef server will download the latest cookbooks. You can monitor the progress by logging into the node and using the tail -f command to monitor /var/log/ opencenter/trans_n.log. Note The Subscribe Cookbook Channel option is reserved for future use. 14

19 Create a Nova Cluster To use OpenStack in your environment, you need to create a Nova cluster and move one or more available nodes into the cluster. 1. At the top of the Workspace, click on the cog icon. In the drop-down menu that appears, select Create Nova Cluster. 2. In the dialog box, enter your network environment information: The Nova public network in CIDR format. The Nova public network interface (such as eth0). The Nova VM network bridge (such as br100). Optional NAT exclusion CIDR range or ranges for networks configured with a DMZ, The name of the Nova cluster. A password for an admin OpenStack user. Nova management network address in CIDR format. The interface of the VM network for the Compute notes (such as eth1). The name of the default availability zone. The VM network CIDR range. The Nova internal network CIDR range that you want to assign to each Controller and Compute node. The OpenCenter server will run for a few minutes. When the process is complete, the Nova cluster container will appear in the workspace. It will include an Infrastructure container, a Compute container, and an AZ Nova (availability zone) container. 3. Select and drag an available node into the Infrastructure container. OpenCenter installs Chef client on the node and then runs Chef to apply the hacontroller1 role to the node. This role ensures that Nova infrastructure services are deployed, including mysql, Horizon, and rabbitmq. This process takes about minutes. In the Tasks pane (hidden by default at the bottom of the UI) system will stream a log to show the status of the installation, and you can also monitor the progress by logging into the node and using the tail -f command to monitor /var/log/opencenter/ trans_n.log. 4. When the Controller deployment is complete, you can drag another available node into the AZ Nova container. OpenCenter installs Chef client on the node and then runs Chef to apply the singlecompute role to the node. This process takes about 5-10 minutes. 15