rackspace.com/cloud/private

Transcription

1 rackspace.com/cloud/private

2 Rackspace Private Cloud Software v 2.0 ( ) Copyright 2012 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 and Fanatical Support 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 OpenStack, LLC in the United States and/or other countries. All other product names and trademarks in this document are for identification purposes only and are property of their respective owners. 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... 2 What is Rackspace Private Cloud Software?... 2 The Rackspace Private Cloud Configuration... 2 Installed Components... 2 Folsom Code Base... 2 Supported OpenStack Features... 3 Unsupported OpenStack Features... 3 Rackspace Private Cloud Support Installation Prerequisites... 5 Software Requirements... 5 Network Requirements... 5 Instance Access Considerations... 5 NIC Considerations... 7 Proxy Considerations... 7 Preparing For the Installation Installing Rackspace Private Cloud Software on Physical Hardware... 9 Hardware Requirements... 9 Download the ISO Install the Controller Node Install the Compute Node Operating System Updates Troubleshooting the Installation Adjusting Rate Limits Accessing the Cloud Accessing the Controller Node Accessing the Dashboard Restoring the Default OpenStack Dashboard Using Your Logo In the OpenStack Dashboard 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 Block Storage iii

4 Block Storage Overview Adding Volume Storage Nodes Node Prerequisites Volume Storage Installation Create a Volume Building a Block Storage All-In-One Node Configuring OpenStack Image Storage Local File Storage Rackspace Cloud Files Swift Storage Rackspace Private Cloud Cookbook Update Procedure Download Current Cookbooks Preparing the Nodes Update the Cookbooks Run chef-client Glossary of Terms iv

5 1. Overview Rackspace has developed Rackspace Private Cloud Software, a fast, free, and easy way to download and install 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 2.0 (Alamo) 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. November 21, 2012 Additional Resources 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. Updated Chapter 6 to reflect Folsom GUI changes. 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 Contact Rackspace For more information about sales and support, contact us at <opencloudinfo@rackspace.com>. For feedback on the product and the documentation, contact us at <RPCFeedback@rackspace.com>. For the documentation, you can also leave a comment at the Knowledge Center. 1

6 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 is a downloadable ISO package that allows you to easily install OpenStack controller, compute, and all-in-one nodes. When the installation process is complete, you will have a working OpenStack cluster configured according to the recommendations of Rackspace OpenStack specialists. The Rackspace Private Cloud Configuration Rackspace Private Cloud Software v 2.0 (Alamo) uses the Folsom release of OpenStack, and includes Compute (Nova), Image Service (Glance), Dashboard (Horizon), Identity (Keystone), and Block Storage (Cinder). Object Storage (Swift) is not included in the ISO wizard, but can be installed manually. Virtual Network Service (Quantum) is not supported at this time. Installed Components The following components are installed by the Rackspace Private Cloud Software: Host OS Ubuntu Hypervisor KVM Nova controller components and APIs, Glance, Horizon, Keystone, rabbitmq, and MySQL. nova-compute, nova-network, and KVM. Opscode Chef server and Rackspace OpenStack cookbooks. Some supported components, such as Cinder volumes and Swift clusters, are not automatically installed by the Rackspace Private Cloud Software installer and must be configured manually. Refer to the appropriate documentation for these features. Folsom Code Base Rackspace Private Cloud Software v 1.0 used the OpenStack Essex code base, and v 2.0 uses the OpenStack Folsom code base. Complete Folsom API updates have not been completed at this time, and Quantum is not included yet; however, nova-volumes is deprecated and Cinder has been implemented in the Rackspace Private Cloud cookbooks. There is no method for a direct upgrade from a v 1.0 cluster to a v 2.0 cluster; instead, you will have to create a new cluster with the Alamo v 2.0 installer. If you want Rackspace assistance in managing and migrating backup images from a v 1.0 cluster to a v2.0 cluster, please us at <opencloudinfo@rackspace.com>. If your OpenStack environment was not installed with Rackspace Private Cloud Software but you still want to use Rackspace Private Cloud cookbooks, you must update your 2

7 environment variables to include a package_component attribute. The attribute should be set to folsom to be compatible with our cookbooks, as in the following example: "default_attributes": { "mysql": { "allow_remote_root": true, "root_network_acl": "%" }, "package_component": "folsom", "floating": "false" }, 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 features are also supported: 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 Scheduler Keystone integrated authentication Glance integrated image service Horizon dashboard Cinder block storage service Swift object storage service 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 Rackspace also supports the use of Rackspace Cloud Files as a backend for OpenStack Image Storage. For information about OpenStack Object Storage, refer to Rackspace Private Cloud OpenStack Object Storage installation. Unsupported OpenStack Features The following features are not supported: Nova high availability Nova object store Nova volumes NFS and ISCSI file storage via volumes for guest VMs Clustered file system solutions xpvnc Xen and other hypervisors Centralized metadata servers Quantum Software Defined Networking 3

8 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 is offered primarily as a "do it yourself" package, free of charge. You can also access the Rackspace Private Cloud Support Forum, a Rackspace-provided 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 Support, or you plan to install on more than 20 nodes, please us at <opencloudinfo@rackspace.com>. 4

9 3. Installation Prerequisites This chapter discusses the networking prerequisites for installing Rackspace Private Cloud Software. Software Requirements Rackspace Private Cloud Software reformats the node on which it is installed and does not have any specific software requirements. Warning During the installation process, the node will be completely reformatted. Do not install Rackspace Private Cloud Software on a node that has any other data on it. Network Requirements Internet access is required to complete the installation, so ensure that the node IP addresses that you use have internet access to download the installation files. Rackspace Private Cloud Software creates a FlatDHCP network, 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 Instance Access Considerations By default, the instances that you create 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". 5

10 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. 6

11 NIC Considerations Rackspace Private Cloud Software v 2.0 supports single- and dual-nic installations and comes with a network bridge defined and configured in advance. During the installation process, you will be prompted to supply NIC information, and if you have more than one NIC, you must designate one as public and one as private. There are several considerations of which you should be aware. OpenStack compute requires NIC ordering to be the same on all hosts in the nova network. For example, when configuring the controller, you may choose eth1 as your public NIC and eth0 as private. When you configure the compute nodes, you must configure their NICs in exactly the same way. You cannot mix single-nic and multi-nic configurations. If you configure the controller with one NIC, all associated compute nodes must also be single-nic. If your server has more than one network card, you cannot perform a single-nic installation, and will be required to select a public and private NIC during the installation process. Proxy Considerations Rackspace Private Cloud Software v 2.0 allows you to enter a proxy gateway address during the installation process. When a proxy is enabled, all internet traffic going to and from the cluster will pass through the proxy, including the Rackspace Private Cloud installation files. After you define the type of node that you want to install, you will be prompted to enter the proxy address. If you do not have one, you can press Enter to leave it blank and skip the step. Proxy settings can only be configured during the installation process. If you need to change the settings, it is recommended that you re-run the ISO. Preparing For the Installation Before you begin, have the following networking information prepared and available: The NIC address or addresses that the nova fixed network will use. If you have more than one NIC address, you must designate one as public and one as private. The IP addresses that you want to assign to each controller and compute node. This can be an IPv4 address in the format xxx.xxx.xxx.xxx or a CIDR range, and it must be able to access the internet to download installation files. Network subnet mask. Network default public gateway. This address is usually a xxx.xxx.xxx.1 address. The IP address of your proxy gateway, if you have one. The address of your nameserver. The server host name. You may be able to define this yourself, or you may need to contact your network administrator for the name. 7

12 Fully-qualified domain name for the host. The address for the nova fixed network, in CIDR format. Instances created in the OpenStack cluster will have IP addresses in this range. Optional DMZ network address and the gateway address in the fixed network that is on the router that routes to the DMZ. The DMZ network address is in CIDR format. A password for an admin OpenStack user. A password for a non-admin OpenStack user, as well as a username if you do not want to use the default of demo. A full real name, username, and password for an operating system user. You must also ensure that the server is configured to boot from an ISO. You can monitor the progress of the installation from a console directly connected to the server or via a remote management tool, such as Dell DRAC or HP Ilo. Finally, you should ensure that the server has virtualization support enabled in the BIOS. 8

13 4. Installing Rackspace Private Cloud Software on Physical Hardware This chapter discusses the process for installing Rackspace Private Cloud Software and tips for troubleshooting the installation. Warning During the installation process, the node will be completely reformatted. Do not install Rackspace Private Cloud Software on a node that has any other data on it. Hardware Requirements Rackspace strongly recommends that you install Rackspace Private Cloud Software on physical hardware nodes (bare metal) for best results. The minimum node footprint is a 2-node installation of one controller node and one compute node. Other compute nodes may be added as needed, up to a total of 20 nodes. An all-in-one installation is available, but it is not recommended that you build a working system on it. Note If you need to install on more than 20 nodes, please contact us at <opencloudinfo@rackspace.com>. The hardware on which Rackspace Private Cloud Software is installed should support VT-x and meet the following recommended minimum hardware specifications: Controller Node: 16 GB RAM 144 GB disk space Dual socket CPU with dual core, or single socket quad core Compute Node: 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 can support up to 32 virtual cores. If you require more virtual cores, adjust your sizing appropriately. 9

14 Download the ISO To download the Rackspace Private Cloud Software ISO, navigate to the product website at the following URL: After you complete and submit the form, you will receive instructions for downloading the ISO. The ISO is a 2 GB file. If you will be copying it to a USB drive; ensure that the drive has sufficient capacity. You will need to make the USB stick bootable. This process has been documented by Ubuntu on their web site. Refer to the procedure that is appropriate for your operating system: Create a bootable USB stick on OS X Create a bootable USB stick on Ubuntu Create a bootable USB stick on Windows Install the Controller Node Before you begin, ensure that you have prepared your network information. When you are ready, follow this procedure to install the controller node. Note You must install the controller node before you install any compute nodes. 1. Boot the ISO on the controller node. 2. After the ISO has launched and loaded, accept the EULA statement. 3. Select Controller. 4. Enter the NIC address. If you have more than one, you must designate one as public and one as private. 5. When prompted, enter the node IP address, subnet mask, gateway, name server, and host name. If you do not enter a fully-qualified domain name for the hostname, you will be prompted to enter a domain name as well. 6. Enter the address for the nova fixed network. 7. If you want to configure a DMZ network, enter the DMZ address and the DMZ gateway address. Be sure that you have at least two NICs on the server. 8. Enter a password for the admin user. You will use this admin username and password to access the API and the dashboard. 9. For the additional non-admin user, accept the default demo or enter your own and provide a password at the prompt. This user will not have admin privileges, but will be able to perform basic OpenStack functions, such as creating instances from images. 10

15 Creating the user will also automatically create a project (also known as a tenant) for this user. 10.Enter the real name, user name, and password for the operating system user account. For example, the user Jane Doe would enter the following information: Full name for the new user: Jane Doe Username for your account: jdoe Password: mysecurepassword At this point, it will take approximately 5-10 minutes for the Ubuntu operating system installation to complete. 11.If you have a proxy, enter the proxy URL at the prompt in the format If you do not have a proxy, press enter to skip this step and leave the proxy information blank. At this point, the installation process will run for approximately 30 minutes without the need for user intervention. The device will reboot during the installation process. You will see a screen with the Rackspace Private Cloud logo, followed by a screen that displays a progress bar; you can use Ctrl+Alt+F2 to toggle between the progress bar screen and a Linux TTY screen (Ctrl+Alt+Fn+F2 on a Mac). You can follow the log during installation by switching to the correct TTY screen and viewing the log in /var/log/ post-install.log. After the installation is complete, you can view the install log by logging into the operating system with the username and password that you configured in Step 9. The log is stored in /var/log/post-install.log. Caution There is no password recovery system. Please do not forget your admin password. Install the Compute Node After the controller node installation is complete, follow this procedure to install the compute node. 1. Boot the ISO on the compute node. 2. After the ISO has launched and loaded, accept the EULA statement. 3. Select Compute. 4. Enter the NIC address. If you have more than one NIC, designate one as public and one as private. Be sure that the ordering of the NICs matches the order that you specified for the controller node. 5. When prompted, enter the node IP address, subnet mask, gateway, name server, and host name. If you do not enter a fully-qualified domain name for the hostname, you will be prompted to enter a domain name as well. 6. Enter the real name, user name, and password for the operating system user account. For example, the user Jane Doe would enter the following information: 11

16 Full name for the new user: Jane Doe Username for your account: jdoe Password: mysecurepassword At this point, it will take approximately 5-10 minutes for the Ubuntu operating system installation to complete. 7. If you have a proxy, enter the proxy URL at the prompt in the format If you do not have a proxy, press enter to skip this step and leave the proxy information blank. 8. Enter the IP address for the controller node. This will add the new compute node to the cluster. At this point, the installation process will run for approximately 20 minutes without the need for user intervention. As with the controller node installation, the device will reboot during the installation process. You will see a screen with the Rackspace Private Cloud logo, followed by a screen that displays a progress bar; you can use Ctrl+Alt+F2 to toggle between the progress bar screen and a Linux TTY screen (Ctrl+Alt+Fn+F2 on a Mac). You can follow the log during installation by switching to the correct TTY screen and viewing the log in /var/log/post-install.log. After the installation is complete, you can view the install log by logging into the operating system with the username and password that you configured during the Controller installation. The log is stored in /var/log/post-install.log. Operating System Updates After you complete the installation, you may get a message notifying you that operating system updates and patches are available. These updates may be safely applied. However, as a best practice in a production environment, Rackspace strongly recommends that you configure a mirror of your production environment in which you apply and test new patches and updates before applying them in production. Troubleshooting the Installation If the installation is unsuccessful, it may be due to one of the following issues. The node does not have access to the Internet. The installation process requires Internet access to download installation files, so ensure that the address for the nodes provides that access and that the proxy information that you entered is correct. You should also ensure that the nodes have access to a DNS server. Your network firewall is preventing Internet access. Ensure the IP address that you assign to the controller is available through the network firewall. Virtualization technology may not be enabled in your server's BIOS. Ensure that virtualization is enabled and restart the installation process. For more troubleshooting information and user discussion, you can also inquire at the Rackspace Private Cloud Support Forum at the following URL: 12

17 Adjusting Rate Limits By default, Rackspace Private Cloud Software sets low values for rate limits, which limit activities such as the number of posts in a minute or the number of servers created in a minute. Depending on your environment, you may need to increase the rate limits. Use the following procedure to adjust the rate limits. 1. Log into the controller node and switch to root access with sudo -i. 2. Issue the following command to edit the environment file. $ knife environment edit rpcs 3. Edit the nova section of the environment file as follows (adjusting the rate limit values as is appropriate to your environment). "nova": { "ratelimit": { "settings": { "changes-since-limit": { "interval": "MINUTE", "limit": "3", "regex": ".*changes-since.*", "uri": "*changes-since*", "verb": "GET" }, "create-servers-limit": { "interval": "DAY", "limit": "50", "regex": "^/servers", "uri": "*/servers", "verb": "POST" }, "generic-delete-limit": { "interval": "MINUTE", "limit": "100", "regex": ".*", "uri": "*", "verb": "DELETE" }, "generic-post-limit": { "interval": "MINUTE", "limit": "10", "regex": ".*", "uri": "*", "verb": "POST" }, "generic-put-limit": { "interval": "MINUTE", "limit": "10", "regex": ".*", "uri": "*", "verb": "PUT" } } 13

18 }, },, 4. Run chef-client to commit the change. $ chef-client 14

19 5. Accessing the Cloud This chapter describes the methods you will use to access your cloud. You should be familiar with the contents of this section before attempting to create an instance or perform other configuration and maintenance tasks. Accessing the Controller Node Rackspace Private Cloud Software also installs the OpenStack client utilities necessary to use the cloud. You can access these features through the command line interface on the controller node. To use them, log in to the controller node via SSH with the OS username and password that you set up during controller node installation. At the shell, switch to root user access. $ sudo -i You can now run the following commands. $ source.novarc $ nova flavor-list You should see output similar to the following: ID Name Memory_MB Disk Ephemeral Swap VCPUs RXTX_Factor m1.tiny m1.small m1.medium m1.large m1.xlarge This is a list of "flavors", different disk sizes that you can assign to images, and is an example of the information that you can access through the python-novaclient command line client. You can also view the status of the controller and compute nodes and the nova components active on each while logged in as the root user. $ nova-manage service list 15

20 You should see output similar to the following: Binary Host Zone Status State Updated_At nova-scheduler ctrl nova enabled :-) :51:34 nova-consoleauth ctrl nova enabled :-) :51:41 nova-network compute1 nova enabled :-) :51:39 nova-compute compute1 nova enabled :-) :51:35 You can also view logs with the tail command. For example, to view nova.log, execute the following command: $ tail /var/log/nova/nova.log All logs are available in the /var/log/ directory and its subdirectories. Accessing the Dashboard In addition to the command line, you can use your web browser to access the controller host. You can use the hostname or the IP address that you provided during installation. You should see the OpenStack dashboard (Horizon) login page. If not, the installation may not be complete. Log in with the admin username and the password that you created during the controller node installation. When the login is successful, you can configure additional users, create and manage images, and launch instances. Restoring the Default OpenStack Dashboard Clusters installed with Rackspace Private Cloud Software v 2.0 will have a Rackspacecustomized dashboard with a similar look and feel to the Rackspace Public Cloud dashboard. If you need to restore the default OpenStack dashboard, follow this procedure. 1. Log into the controller node and switch to root access with sudo -i. 2. Issue the following command to edit the environment file. $ knife environment edit rpcs 3. In the Horizon section of the file, change theme:"rackspace" to "theme: "default". 4. Run chef-client to commit the change. $ chef-client When you reload the dashboard in your web browser, it will now use the default OpenStack style. To revert to the Rackspace theme, follow the same procedure and change the theme: value to "Rackspace". 16

21 You can also use a single knife command to execute the change. $ knife exec -E '@e=chef::environment.load("rpcs"); \ a=@e.default_attributes; To revert the theme, execute the same knife command, substituting "Rackspace" for "default". Using Your Logo In the OpenStack Dashboard After you have switched to the OpenStack default dashboard, you can customize it by adding your own logo. 1. Create a transparent PNG of your logo, sized to fit within a 200-pixel wide by 160-pixel tall space. 2. Name the file logo.png. 3. Save logo.png in the following location: /usr/share/openstack-dashboard/openstack_dashboard/static/ dashboard/img/logo.png 4. If you have not already done so, switch to root access with sudo -i. 5. Open style.css for editing with nano. $ nano /usr/share/openstack-dashboard/openstack_dashboard/static/dashboard/ css/style.css 6. Press Ctrl+w and search for: h1.brand. 7. Replace the entire h1.brand rule with the following: h1.brand a { background: url(../img/logo.png) center center no-repeat; display: block; height: 160px; text-indent: -9999px; margin: 25px auto; } 8. Press Ctrl+X; then press Y to commit the change. 9. Press Return to save style.css and exit the editor. Accessing the Graphite Monitoring Tool The cluster can be monitored via the Graphite monitoring tool. This is automatically enabled in clusters installed with Alamo v