Cisco OpenStack Edition: Folsom Manual Install

From DocWiki

(Difference between revisions)
Jump to: navigation, search
m
m
Line 44: Line 44:
**The Controller node and Network node will have an interface attached to this network  
**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  
**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  
+
**This network typically employs publicly routable IP addressing if no external NATs are used upstream towards the Internet edge (Note: in this document all IP addressing for all interfaces comes out of various private addressing blocks)
*Data Network (AKA: Private Network)  
*Data Network (AKA: Private Network)  
**This network is used for providing connectivity to OpenStack Intances (Virtual Machines)  
**This network is used for providing connectivity to OpenStack Intances (Virtual Machines)  
Line 50: Line 50:
**This network typically employs private ([http://tools.ietf.org/html/rfc1918 RFC1918]) IP addressing
**This network typically employs private ([http://tools.ietf.org/html/rfc1918 RFC1918]) IP addressing
-
Figure 1 is used to help visualize the setup and to act as a reference for configuration steps later on in the document.  
+
'''Figure 1''' is used to help visualize the setup and to act as a reference for configuration steps later on in the document.  A summary of the network topology is as follows:
-
[[Image:Network-topology-v1.0.png|thumb|left|Reference Topology]]<br>  
+
*Controller Node
 +
** Hostname = control03
 +
** Single physical NIC used to logically separate three networks
 +
***eth0 connects to the Management/CIMC network which is on VLAN220 (VLAN 220 is the Native VLAN on the upstream Layer 2 switch)
 +
****eth0 IP address = 192.168.220.43
 +
***eth0.221 connects to the Public/API network on VLAN221
 +
****eth0.221 IP address = 192.168.221.43
 +
***eth0.223 connects to the Data network
 +
****eth0.223 IP address = 10.0.0.43
 +
***CIMC 0 connects to the Management/CIMC network
 +
****CIMC 0 IP address = 192.168.220.13
 +
*Compute Node
 +
**Hostname = compute01
 +
** Single physical NIC used to logically separate three networks
 +
***eth0 connects to the Management/CIMC network which is on VLAN220 (VLAN 220 is the Native VLAN on the upstream Layer 2 switch)
 +
****eth0 IP address = 192.168.220.51
 +
***eth0.223 connects to the Data network
 +
****eth0.223 IP address = 10.0.0.51
 +
***CIMC 0 connects to the Management/CIMC network
 +
****CIMC 0 IP address = 192.168.220.4
 +
*Network Node
 +
**Hostname = control02
 +
** Single physical NIC used to logically separate three networks
 +
***eth0 connects to the Management/CIMC network which is on VLAN220 (VLAN 220 is the Native VLAN on the upstream Layer 2 switch)
 +
****eth0 IP address = 192.168.220.42
 +
***eth0.221 connects to the Public/API network on VLAN221
 +
****eth0.221 No IP address is set for this interface (see notes later in document on OVS/Quantum setup)
 +
***eth0.223 connects to the Data network
 +
****eth0.223 IP address = 10.0.0.42
 +
***CIMC 0 connects to the Management/CIMC network
 +
****CIMC 0 IP address = 192.168.220.3
 +
 
 +
*Other Network Services
 +
**DNS: In this setup an external DNS server is used for name resolution for OpenStack node resolution and external resolution.
 +
**NTP: In this setup an external NTP server(s) is used for time syncronization
 +
**Physical Network Switches: Each node in this setup is physically attached to a Cisco Nexus switch acting as a Top-of-Rack access layer device.  Trunking is configured on each interface connecting to the eth0 NIC of each node. Note: Upstream routers/aggregation layer switches will most likely be terminating the L3 VLAN interfaces and if they are deployed in a redundant fashion with a First Hop Redundancy Protocol like HSRP or VRRP then you need to be careful what the IP addresses are on the physical L3 switches/routers as they may conflict with the IP address of the Quantum router on the public subnet (usually assigned .3 address). For example, if you are using HSRP and you have .1 as the standby IP address, .2 as the first L3 switch IP and .3 as the second L3 switch IP, you will receive a duplicate IP address error on the second L3 switch.  This can be worked around by using high-order IPs on your upstream L3 device or altering the Quantum subnet configuration at the time of creation (more on this later).
 +
 
 +
 +
 
 +
[[Image:Network-topology-v1.0.png|thumb|left]]<br>  
<br>
<br>

Revision as of 16:09, 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 (Note: in this document all IP addressing for all interfaces comes out of various private addressing blocks)
  • 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

Figure 1 is used to help visualize the setup and to act as a reference for configuration steps later on in the document.  A summary of the network topology is as follows:

  • Controller Node
    • Hostname = control03
    • Single physical NIC used to logically separate three networks
      • eth0 connects to the Management/CIMC network which is on VLAN220 (VLAN 220 is the Native VLAN on the upstream Layer 2 switch)
        • eth0 IP address = 192.168.220.43
      • eth0.221 connects to the Public/API network on VLAN221
        • eth0.221 IP address = 192.168.221.43
      • eth0.223 connects to the Data network
        • eth0.223 IP address = 10.0.0.43
      • CIMC 0 connects to the Management/CIMC network
        • CIMC 0 IP address = 192.168.220.13
  • Compute Node
    • Hostname = compute01
    • Single physical NIC used to logically separate three networks
      • eth0 connects to the Management/CIMC network which is on VLAN220 (VLAN 220 is the Native VLAN on the upstream Layer 2 switch)
        • eth0 IP address = 192.168.220.51
      • eth0.223 connects to the Data network
        • eth0.223 IP address = 10.0.0.51
      • CIMC 0 connects to the Management/CIMC network
        • CIMC 0 IP address = 192.168.220.4
  • Network Node
    • Hostname = control02
    • Single physical NIC used to logically separate three networks
      • eth0 connects to the Management/CIMC network which is on VLAN220 (VLAN 220 is the Native VLAN on the upstream Layer 2 switch)
        • eth0 IP address = 192.168.220.42
      • eth0.221 connects to the Public/API network on VLAN221
        • eth0.221 No IP address is set for this interface (see notes later in document on OVS/Quantum setup)
      • eth0.223 connects to the Data network
        • eth0.223 IP address = 10.0.0.42
      • CIMC 0 connects to the Management/CIMC network
        • CIMC 0 IP address = 192.168.220.3
  • Other Network Services
    • DNS: In this setup an external DNS server is used for name resolution for OpenStack node resolution and external resolution.
    • NTP: In this setup an external NTP server(s) is used for time syncronization
    • Physical Network Switches: Each node in this setup is physically attached to a Cisco Nexus switch acting as a Top-of-Rack access layer device. Trunking is configured on each interface connecting to the eth0 NIC of each node. Note: Upstream routers/aggregation layer switches will most likely be terminating the L3 VLAN interfaces and if they are deployed in a redundant fashion with a First Hop Redundancy Protocol like HSRP or VRRP then you need to be careful what the IP addresses are on the physical L3 switches/routers as they may conflict with the IP address of the Quantum router on the public subnet (usually assigned .3 address). For example, if you are using HSRP and you have .1 as the standby IP address, .2 as the first L3 switch IP and .3 as the second L3 switch IP, you will receive a duplicate IP address error on the second L3 switch. This can be worked around by using high-order IPs on your upstream L3 device or altering the Quantum subnet configuration at the time of creation (more on this later).


Network-topology-v1.0.png


Rating: 4.6/5 (5 votes cast)

Personal tools