Cisco OpenStack Edition: Folsom Manual Install

From DocWiki

(Difference between revisions)
Jump to: navigation, search
m (Created page with "= OpenStack Folsom Manual Installation = == Introduction == The are two common ways of installing OpenStack: 1) Manually 2) Automated.  There is much focus on the full aut...")
Line 1: Line 1:
-
= OpenStack Folsom Manual Installation =
+
= OpenStack Folsom Manual Installation =
-
== Introduction ==
+
== Introduction ==
-
The are two common ways of installing OpenStack: 1) Manually 2) Automated.  There is much focus on the full automation of OpenStack deployment using automation tools such as Puppet, Chef, JuJu and others and while these offer great advantages over manual configuration, they do hide the underworkings from those who need to learn what is really happening during an OpenStack setup.  This document can be used by those who want to learn a bit more about OpenStack installation on the Folsom release using the following OpenStack components:
+
The are two common ways of installing [http://docs.openstack.org/ OpenStack], manually or via automation.  There is much focus on the full automation of OpenStack deployment using automation tools such as [http://puppetlabs.com/ Puppet], [http://www.opscode.com/chef/ Chef], [https://juju.ubuntu.com/ JuJu] and others and while these offer great advantages over manual configuration, they do hide the underworkings from those who need to learn what is really happening during an OpenStack setup.  This document can be used by those who want to learn a bit more about OpenStack installation process on the Folsom release using the following OpenStack components:  
-
*Nova Compute
+
<br>
-
*Keystone
+
 
-
*Horizon
+
*[http://nova.openstack.org/ Nova]&nbsp;(Compute Service)
-
*Glance
+
*[http://glance.openstack.org/ Glance]&nbsp;(Image Service)
-
*Quantum
+
*[http://keystone.openstack.org/ Keystone]&nbsp;(Identity Service)
 +
*[http://horizon.openstack.org/ Horizon]&nbsp;(OpenStack Dashboard Web User Interface)
 +
*[http://docs.openstack.org/developer/quantum/ Quantum]&nbsp;(Network Service)
 +
 
 +
== Dependencies  ==
 +
 
 +
=== Operating System  ===
 +
 
 +
The operating system used for this installation is&nbsp;Ubuntu 12.04 LTS (Precise).
 +
 
 +
=== Nodes  ===
 +
 
 +
This document uses three physical servers (Cisco UCS B or C-series) to serve the roles of Controller, Compute, Network Controller. &nbsp;While, physical servers are being used in the instructions, there is nothing preventing you from using three virtual machines running on your virtualization/hypervisor of choice. &nbsp;The three distinct node types that are used in this document are:
 +
 
 +
*Controller Node
 +
**Runs Nova API, Nova Cert, Nova Consoleauth, Nova Novncproxy, Nova Scheduler, Novnc, Quantum Server, Quantum Plugin OVS, Quantum API/registry, and Keystone services
 +
**Provides control plane functionality for managing the OpenStack environment
 +
*Compute Node
 +
**Runs Nova Compute, Quantum Plugin OVS, and OVS Plugin Agent services
 +
**Provides the hypervisor role for running Nova instances (Virtual Machines)
 +
*Network Controller Node
 +
**Runs Quantum DHCP, Quantum L3 Agent, Quantum Plugin OVS, OVS Plugin Agent, DNSMASQ Base and Util services
 +
**Provides network services such as DHCP, network access and routing for Nova instances running on the Compute node
 +
 
 +
=== Network  ===
 +
 
 +
The network design referenced in this document has three physically or logically (VLAN) seperate networks. &nbsp;In this document, the three networks will be seperated logicially using VLANs. &nbsp;The networks are defined below:
 +
 
 +
*Management and CIMC (Cisco Integrated Management Controller for UCS) Network<br>
 +
**This network is used to perform management functions against the node. Examples include SSH to the nodes, the controller node hosting Horizon would listen for incoming connections on this network.
 +
**An IP address for each node is required for this network.
 +
**This network typically employs private ([http://tools.ietf.org/html/rfc1918 RFC1918]) IP addressing.
 +
*Public/API Network
 +
**This networking is used for assigning Floating IP addresses to instances for communicating outside of the OpenStack Cloud
 +
**The Metaservice that is used for injecting information into instances (i.e. SSH keys) is attached to this network on the Controller node
 +
**The Controller node and Network node will have an interface attached to this network
 +
**An IP address for the Controller node is required for this network
 +
**This network typically employs publicly routable IP addressing if no external NATs are used upstream towards the Internet edge
 +
*Data Network (AKA: Private Network)
 +
**This network is used for providing connectivity to OpenStack Intances (Virtual Machines)
 +
**In this document an IP address for each node is assigned
 +
**This network typically employs private ([http://tools.ietf.org/html/rfc1918 RFC1918]) IP addressing
 +
 
 +
<br>

Revision as of 15:42, 7 December 2012

Contents

OpenStack Folsom Manual Installation

Introduction

The are two common ways of installing OpenStack, manually or via automation.  There is much focus on the full automation of OpenStack deployment using automation tools such as Puppet, Chef, JuJu and others and while these offer great advantages over manual configuration, they do hide the underworkings from those who need to learn what is really happening during an OpenStack setup.  This document can be used by those who want to learn a bit more about OpenStack installation process on the Folsom release using the following OpenStack components:


Dependencies

Operating System

The operating system used for this installation is Ubuntu 12.04 LTS (Precise).

Nodes

This document uses three physical servers (Cisco UCS B or C-series) to serve the roles of Controller, Compute, Network Controller.  While, physical servers are being used in the instructions, there is nothing preventing you from using three virtual machines running on your virtualization/hypervisor of choice.  The three distinct node types that are used in this document are:

  • Controller Node
    • Runs Nova API, Nova Cert, Nova Consoleauth, Nova Novncproxy, Nova Scheduler, Novnc, Quantum Server, Quantum Plugin OVS, Quantum API/registry, and Keystone services
    • Provides control plane functionality for managing the OpenStack environment
  • Compute Node
    • Runs Nova Compute, Quantum Plugin OVS, and OVS Plugin Agent services
    • Provides the hypervisor role for running Nova instances (Virtual Machines)
  • Network Controller Node
    • Runs Quantum DHCP, Quantum L3 Agent, Quantum Plugin OVS, OVS Plugin Agent, DNSMASQ Base and Util services
    • Provides network services such as DHCP, network access and routing for Nova instances running on the Compute node

Network

The network design referenced in this document has three physically or logically (VLAN) seperate networks.  In this document, the three networks will be seperated logicially using VLANs.  The networks are defined below:

  • Management and CIMC (Cisco Integrated Management Controller for UCS) Network
    • This network is used to perform management functions against the node. Examples include SSH to the nodes, the controller node hosting Horizon would listen for incoming connections on this network.
    • An IP address for each node is required for this network.
    • This network typically employs private (RFC1918) IP addressing.
  • Public/API Network
    • This networking is used for assigning Floating IP addresses to instances for communicating outside of the OpenStack Cloud
    • The Metaservice that is used for injecting information into instances (i.e. SSH keys) is attached to this network on the Controller node
    • The Controller node and Network node will have an interface attached to this network
    • An IP address for the Controller node is required for this network
    • This network typically employs publicly routable IP addressing if no external NATs are used upstream towards the Internet edge
  • Data Network (AKA: Private Network)
    • This network is used for providing connectivity to OpenStack Intances (Virtual Machines)
    • In this document an IP address for each node is assigned
    • This network typically employs private (RFC1918) IP addressing


Rating: 4.6/5 (5 votes cast)

Personal tools