Juno Cloud Setup Guide

OpenStack Sample Architecture

Networking

• Neutron

Adding to RightScale

Cloud Capabilities

When adding an OpenStackOpenStack zone with basic networking and security groups to the RightScale Dashboard, the following cloud capabilities should be set:

• Security Groups: Enabled
• Port Forwarding: Disabled
• Subnets: Disabled
• Multiple Subnets: Disabled

Components

Keystone, Horizon, dnsmasq and MySQL Server

Overview

Runs the Cinder, Swift-Proxy, Glance, Nova-Network and Nova-Manage services. Provides image management, block storage, object storage proxy and compute management. This server has high I/O and network requirements. A RAID5 array provides improved disk I/O while still providing fault tolerance. 10Gb network configuration is recommended for the storage server to reduce instance and snapshot creation time.

Network

• 10Gb Private NIC
• 1-10Gb Public NIC

Disk Configuration

• RAID5

Expansion

• If block storage disk space becomes an issue, additional Cinder nodes can be added to increase space. Adding extra Glance servers can be used to reduce disk and network I/O on each Glance server.

Swift-Object Nodes

Overview

Runs the Cinder, Swift-Proxy, Glance, Nova-Network and Nova-Manage services. Provides image management, block storage, object storage proxy and compute management. This server has high I/O and network requirements. A RAID5 array provides improved disk I/O while still providing fault tolerance. 10Gb network configuration is recommended for the storage server to reduce instance and snapshot creation time.

Network

• 10Gb Private NIC

Disk Configuration

• SSD RAID0

Expansion

Additional hypervisors should be added to a cluster in the event that that VMs cannot be launched due to hypervisor disk or memory capacity. Extra hypervisors can also be added to a cluster if VMs are running slow due to insufficient disk I/O.

Example Hardware Configuration

Services

Common

Juno source:
/etc/apt/sources.list.d/Juno.list
deb http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/Juno main

Keystone

Packages:

• keystone
• python-keystone
• python-keystoneclient

Configuration Files:

• http://privatecloudtools.s3.amazonaw...g/keystone.tgz

Nova

Packages:

• nova-api
• nova-cert
• nova-common
• nova-conductor
• nova-consoleauth
• nova-novncproxy
• nova-scheduler
• python-nova
• python-novaclient

Configuration Files:

• http://privatecloudtools.s3.amazonaw...onfig/nova.tgz

Neutron

Packages:

• python-neutron
• python-neutronclient
• neutron-common
• neutron-dhcp-agent
• neutron-l3-agent
• neutron-metadata-agent
• neutron-plugin-openvswitch
• neutron-plugin-openvswitch-agent
• neutron-server

Configuration Files:

• http://privatecloudtools.s3.amazonaw...ig/neutron.tgz

Glance

Packages:

• glance
• glance-api
• glance-common
• glance-registry
• python-glance
• python-glanceclient

Configuration Files:

• http://privatecloudtools.s3.amazonaw...fig/glance.tgz

Cinder

Packages:

• cinder-api
• cinder-common
• cinder-scheduler
• cinder-volume
• python-cinder
• python-cinderclient

Swift

Packages:

• python-swift
• python-swiftclient
• swift
• swift-proxy

Nova-compute

Packages:

• nova-common
• nova-compute
• nova-compute-kvm
• python-nova
• python-novaclient

Neutron-agent

Package:

• python-neutron
• python-neutronclient
• neutron-common
• neutron-dhcp-agent
• neutron-l3-agent
• neutron-metadata-agent
• neutron-plugin-openvswitch
• neutron-plugin-openvswitch-agent

Swift-object

Packages:

• python-swift
• python-swiftclient
• swift
• swift-account
• swift-container
• swift-object

Monitoring Steps

Zenoss is recommended for OpenStack monitoring, but the OpenStack monitoring script is also compatible with Nagios.

• Download openstack.rb from https://privatecloudtools.s3.amazona...m/openstack.rb and place it in the zenoss libexec directory on the Zenoss server (ususally /opt/zenoss/libexec)
• Create a new monitoring template in Zenoss
• Add a new command data source for the monitoring template
• Fill out name, error severity, cycle time and command template
• Command template should be in the following format: `openstack.rb -h ${dev/manageIp} -u <USER> -p <PASSWORD> -t <TENANTID>` where <USER> and <PASS> are the Keystone credentials to use when checking system status, and <TENANTID> is a tenant id where the user is a member or admin
• Add a data point for each component to be monitored. The script currently supports volume, image, identity, object and compute
• Add thresholds. A value of 1 means the service is functioning, a value of 0 means there is an error
• Add graphing if you would like to keep historical 

OpenStack Configuration Prerequisites

Before registering your OpenStack cloud and adding it to RightScale, you should read these configuration details about our compatibility and support. Check out our OpenStack Reference Architecture page to see details of the architecture we used and tested against.

Note: For Rackspace Private, see Rackspace Private Reference Architecture.

Requirements for RightScale with OpenStack Juno

• OpenStack Juno version
• Public endpoints available for Keystone, Nova, Glance, Cinder, Swift
• Neutron networking is required. Nova-network is not supported by RightScale
• Outbound network connectivity meeting RightScale requirements
• Metadata service available to all instances
• Functioning DNS server available to all instance
• Network connectivity between instances across compute nodes
• One network must be available to cloud account tenant
• Nova Availability Zones and Host Aggregates are not required but if used, they must be managed by instance flavors
• Update the keystone.conf file with the cloud's public endpoint. Note: You will use the same URL later in this tutorial as the "Registration URL" when you register the cloud with RightScale.

..
# The base endpoint URLs for keystone that are advertised to clients
# (NOTE: this does NOT affect how keystone listens for connections)
public_endpoint = <<http://198.101.133.81:5000/>># admin_endpoint = http://localhost:%(admin_port)s/

Supported features in the Dashboard

Nova Compute (Cloud Compute)

• Instances and ServerTemplates
• Firewalls (Security Groups)

• Monitoring, Alerts, Arrays, SSH

• Glance Image Service

Networking

• Static IPs
• Subnets 

Cinder Volumes (Block Storage) 

• Create, Attach, Detach, Delete, Snapshot, Create from Snapshot

Account selection

Be sure to select the desired account with which you would like to register your OpenStack cloud. A cloud can only be registered to one RightScale account. Cloud registration requires "admin role" privileges. Once a cloud has been successfully registered it cannot be registered with another RightScale account unless you delete it.

API EndPoints

RightScale relies on "keystone service catalog" for discovery of these end points. 

In order to ensure proper integration with RightScale, we require that the following OpenStack endpoint URLs be publicly accessible. This means, the publicURL for each of the following services need to have a public IP address.

Please ensure that these publicURL (IP addresses and Port numbers) are accessible to RightScale over the Internet and are properly configured in firewall settings.

1. Compute end point (Nova)
   • v2 supported
   • API endpoint publicURL should look like: http://109.168.247.227:8774/v2/<tenant-id>
2. Identify end point (KeyStone)
   • ​​v2 supported
   • API endpoint publicURL should look like: http://52.24.82.66:5000/v2.0
3. Image end point (Glance)
   • ​​v2 supported
   • API endpoint publicURL should look like: http://109.168.247.227:9292/v2
4. Volume end point (Cinder)
   • ​​v1 supported
   • API endpoint publicURL should look like: http://109.168.247.227:8776/v1/<tenant-id>
5. Object-store (Swift)
   • ​​v1 supported
   • API endpoint publicURL should look like: http://109.168.247.227:8888/v1/<tenant-id>
6. ​​Network (Neutron)
   • ​v2 supported
   • API endpoint publicURL should look like: http://109.168.247.227:9696

Firewall Settings

See About Firewalls for detailed information on configuring your firewall settings for proper use with OpenStack.

Uploading Images

See Upload RightImages to a Private Cloud to get our base images into your OpenStack cloud.

Known Issues

Neutron policy must be changed to allow port creation by non-owners. In /etc/neutron/policy.conf, change '"create_port": "rule:admin_or_network_owner",'  to  '"create_port": "",' 

Support

If you run into any issues during your OpenStack registration process or otherwise, please book a ticket by emailing support@rightscale.com.

Register an OpenStack Private Cloud with RightScale

Register your OpenStack cloud with RightScale to manage your cloud resources.

NOTE: These instructions are also compatible with registering your Rackspace Private Cloud.

Prerequisites

• A completed OpenStack installation.
• Registration requires a RightScale user with 'Admin Role' privileges to the RightScale account.
• A set of OpenStack admin user credentials.
• Update the keystone.conf file with the cloud's public endpoint. Note: You will use the same URL later in this tutorial as the "Registration URL" when you register the cloud with RightScale.

..
# The base endpoint URLs for keystone that are advertised to clients
# (NOTE: this does NOT affect how keystone listens for connections)
public_endpoint = <<http://198.101.133.81:5000/>>
# admin_endpoint = http://localhost:%(admin_port)s/

Steps

Register Cloud

Once you've installed and set up your OpenStack cloud, you need to register the cloud itself with RightScale so that it can be accessed through the RightScale platform.

• Go to Settings > Account Settings > Administered Clouds tab. 

NOTE: If you do not see this tab, your RightScale account is not enabled for adding a private cloud. If you would like to enable this feature, contact your account manager or sales@rightscale.com.

• Under "Register Your Private Cloud," select OpenStack from the dropdown menu.
• Click Register Cloud

Enter Credentials

Next, provide your OpenStack admin credentials to verify you're the administrator of the private cloud.

• OpenStack Releases - Select Juno from the drop down menu.
• Name - Provide a name for your private cloud. Since the name of the cloud will appear in the Dashboard under the Clouds menu, it's recommended that you use a short name.
• Description - Provide a brief description about your private cloud. You might want to include a reference link or contact information.
• Registration URL - This is the URL to reach your cloud controller from the public internet (e.g. http://198.101.133.81:5000/). Retrieve this value when logged in as admin by navigating to Access & Security > Identity.

• Admin Username - The user name used to access the Horizon dashboard.
• Admin Password - The password used to access the Horizon dashboard.
• Region - Region name setup during OpenStack cloud installation. If you are unsure about the name, use "keystone catalog" command from the shell prompt on your cloud controller node to determine the region name.
• Tenant ID - Find the tenant ID by logging into the Horizon dashboard. Retrieve this value when logged in as admin by navigating to Access & Security > Identity > Dowload OpenStack RC File. Open the downloaded RC File and find the value under OS_TENANT_ID.

Click Request Registration to submit your private cloud information for verification purposes. Upon successful registration, you will see the following message: "Cloud Registration succeeded. Cloud is now registered within RightScale."

Next Steps

Since you are the administrator who registered your private cloud with RightScale, you will see the private cloud's Cloud Token, which you can provide to other users so that they can add your private cloud to their RightScale account and use your cloud's resources. See Add an OpenStack Cloud to a RightScale Account.

Add an OpenStack Private Cloud to a RightScale Account

Add your OpenStack Juno cloud with RightScale so that you can use the Dashboard to manage your cloud resources.

NOTE: These instructions are also compatible with adding your Rackspace Private Cloud.

Prerequisites

• (Recommended) A set of non-admin cloud credentials (username, password, tenantID)
• The OpenStack cloud you wish to add must already be registered with a RightScale account.
• A Rightscale account with Admin Role priviledges
• Cloud Token received from the cloud administrator.
• This tutorial uses the Horizon dashboard.

Steps

Connect to Cloud

1. After logging into the Dashboard, go to Settings > Account Settings > Clouds. Click Connect to a Cloud.
2. Next, click Connect to a Private Cloud.

Enter Cloud Token

Next, you will have to enter your Cloud Token.

Enter Credentials

Next, enter values for the following fields:

• Username: The OpenStack username used to log in to the Horizon dashboard (recommended to be the username for a non-Admin OpenStack user).
• Password: The related password.
• Tenant ID: find the tenant ID by logging into the Horizon dashboard. Retrieve this value when logged in as admin by navigating to Access & Security > Identity > Dowload OpenStack RC File. Open the downloaded RC File and find the value under OS_TENANT_ID.

Check the cloud status

On the same Clouds tab or on the Cloud Credentials widget in the Overview tab, you may check the status of your cloud.

• Cloud Controller - Displays the status of your cloud.
• Cloud Account - Displays the status of your cloud credentials.

Both of these items must be valid and active (green) in order to successfully launch cloud server.

Next Steps

Allow RightScale several minutes to populate your account with the appropriate images before launching servers. In the RightScale Dashboard, navigate to Clouds > OpenStack > Images where RightScale queries every few minutes for the images.

To upload RightScale RightImages to your OpenStack cloud, see Upload RightImages to a Private Cloud.

Upload RightImages to an OpenStack Private Cloud

To upload a RightImage to a private cloud so that you can create a custom MCI and use it with a ServerTemplate.

Overview

If you are setting up your own private cloud and want to use RightScale's ServerTemplate model for launching servers, you need to use one of RightScale's published RightImages (machine images). The first step of this process is to upload one or more RightImages to your private cloud. Once the RightImage is available in your private cloud, you can create a MultiCloud Image (MCI) that references the image in that cloud and then add the MCI to your ServerTemplate(s). This tutorial explains the initial step of uploading a RightImage to your private cloud.

Steps

Download OpenStack-related RightImages from RightScale

Our OpenStack (with Horizon) RightImages can be found here.

For Windows based images, please contact RightScale support (support@rightscale.com)

Upload RightImages to an OpenStackOpenStack Private Cloud through Horizon

1. Login to your OpenStack Dashboard
2. Navigate to Images & Snapshots
3. Click Create Image
4. Fill out the necessary information and add your desired image URL in Image Location from our bucket found here.
5. When finished, click Create Image.

Upload RightImages Using Command Line Tools

Note: When an image is loaded on to an OpenStack cloud, you must specify the correct OS type for the image. If the OS type is not specified, it will default to linux.

If you don't have access to the Horizon dashboard, you can use the glance command line tool to upload an image as well by following these steps:

1. Ensure that you have glance client installed correctly.
2. Using glance CLI, you can directly upload the image into glance repository from RightScale's image repository:

# glance image-create --public --copy-from https://rightscale-openstack.s3.amazonaws.com/kvm/centos/5.8/RightImage_CentOS_5.8_x64_v5.8.8.3.qcow2 --name="RightImage_CentOS_6.3 v5.8.8.3"  --container-format=ovf --disk-format=qcow2