Jump to: navigation, search

Difference between revisions of "Documentation/InstallGuideChanges"

(Created page with "The new OpenStack Networking Guide will be taking content from the Install and Cloud Admin Guides, which means the content of those two guides is going to be "beefed up" to pr...")
 
 
(8 intermediate revisions by 3 users not shown)
Line 4: Line 4:
  
 
Preface
 
Preface
 +
 
Document change history
 
Document change history
  
1. Architecture
+
1 Architecture
Conceptual architecture
+
:# Conceptual architecture
Logical architecture
+
:# Logical architecture
Example architectures
+
:# Example architectures
 +
 
 +
2 Basic operating system configuration
 +
:# Before you begin
 +
:# Networking
 +
:# Network Time Protocol (NTP)
 +
:# Passwords
 +
:# MySQL database
 +
:# OpenStack packages
 +
:# Messaging server
 +
 
 +
3 Configure the Identity Service
 +
 
 +
4 Configure the Image Service
 +
 
 +
5 Configure Compute services
 +
:# Compute service
 +
:# Install Compute controller services
 +
:# Configure a Compute node
 +
:# Enable Networking
 +
:# Launch an instance
 +
 
 +
6 Add the dashboard
 +
 
 +
7 Add the Block Storage Service
 +
 
 +
8 Add Object Storage
 +
 
 +
9 Install the Networking service
 +
:# Networking considerations
 +
:# Neutron concepts
 +
:# Install Networking services
 +
:# Neutron deployment use cases
 +
 
 +
10 Add the Orchestration service
 +
 
 +
11 Add the Telemetry service
 +
 
 +
'''Proposed changes'''
 +
 
 +
Preface
 +
 
 +
Document change history
 +
 
 +
1 Architecture
 +
:# Conceptual architecture
 +
::# Provide general explanation of "core" nodes... controller, network, and compute.
 +
::# Provide general explaination of "additional" nodes... storage.
 +
::# Explain general hardware requirements of nodes... cpu, disk, and memory.
 +
:# Logical architecture
 +
:# Example core architectures
 +
::# Two-node with Nova networking (two interfaces per node)
 +
:::# Provide diagrams containing services on each node and physical/logical connectivity (e.g., network interfaces with usable IP addresses)
 +
::# Three-node with Neutron networking (two interfaces per node except network which has three)
 +
:::# Provide diagrams containing services on each node and physical/logical connectivity (e.g., network interfaces with usable IP addresses)
 +
::# Indicate requirements for "surrounding" network components (e.g., do not use DHCP, external network should offer more than 1 IP address to support floating IPs etc.)
 +
::# Provide links to additional networking information (book?)
 +
:# Example architecture with additional nodes
 +
::# Add storage nodes to either of the core architectures
 +
:# Condensed archectectures
 +
::# Explain option to "condense" architectures with fewer nodes or network interfaces with the caveat that it makes troubleshooting more difficult and probably doesn't reflect a production environment (maybe?)
 +
 
 +
2 Basic operating system configuration
 +
:# Before you begin
 +
::# Prefer use of "base" installations rather than "everything" installations
 +
::# Provide recommended partition sizes and filesystem types? (maybe?)
 +
:# Networking
 +
::# Explain firewall situation (depends on distribution)
 +
::# Configuration for two-node arch (broken up by node)
 +
:::# Provide recommended entries for /etc/hosts or DNS
 +
:::# Note importance of key-based SSH authentication when considering multiple compute nodes with migration
 +
:::# Provide connectivity tests
 +
::# Configuration for three-node arch (broken up by node)
 +
:::# Provide recommended entries for /etc/hosts or DNS
 +
:::# Note importance of key-based SSH authentication when considering multiple compute nodes with migration
 +
:::# Provide connectivity tests
 +
::# Configuration for additional nodes (although I'm wondering if we should move these details to their associated chapters... e.g., swift)
 +
:# Install additional base services and useful troubleshooting tools
 +
::# ntp, wget, tcpdump...
 +
:# Passwords
 +
:# MySQL database
 +
::# Recommend further restricting grants before moving into production
 +
:# Messaging server (moved before OpenStack packages since the OpenStack repos don't provide these packages)
 +
:# OpenStack packages
 +
 
 +
3 Configure the Identity Service
 +
:# Add a "demo" tenant and user so that Neutron doesn't break
 +
:# Explain openrc files and how to use them (mostly covered in "Install the OpenStack command-line clients" chapter)
 +
 
 +
4 Configure the Image Service
  
2. Basic operating system configuration
+
5 Configure Compute services
Before you begin
+
:# Compute service
Networking
+
::# Change to "concepts" like the other services
Network Time Protocol (NTP)
+
:# Install Compute controller services
Passwords
+
:# Configure a Compute node
MySQL database
 
OpenStack packages
 
Messaging server
 
  
3. Configure the Identity Service
+
6 Configure networking
  
4. Configure the Image Service
+
:# Networking strategy
 +
:# Networking considerations
 +
:# Configure Nova networking
 +
::# Which use case(s)?
 +
:# Neutron concepts
 +
::# ML2
 +
::# Open vSwitch
 +
::# GRE
 +
::# VXLAN
 +
:# Configure Neutron networking
 +
::# ML2 with... GRE or VXLAN?
 +
:# Install Networking services
 +
::# Install Networking services on a dedicated network node
 +
::# Install networking support on a dedicated compute node
 +
::# Install networking support on a dedicated controller node
 +
::# Create the base Neutron networks
 +
:# Neutron deployment use cases
 +
::# Single flat network
 +
::# Provider router with private networks
 +
::# Per-tenant routers with private networks
  
5. Configure Compute services
+
7 Add the dashboard
Compute service
+
:# When complete, jump to launch an instance or continue configuring additional services. We could launch an instance before the dashboard, but I think people feel GUIs provide a more polished experience. If we feel the dashboard is important, we should include screen shots for creating and launching an instance.
Install Compute controller services
+
:# Note that Cinder is required for the Dashboard to work
Configure a Compute node
 
Enable Networking
 
Launch an instance
 
  
6. Add the dashboard
+
8 Add the Block Storage Service
 +
:# When compete, jump to launch an instance or continue configuring additional services
  
7. Add the Block Storage Service
+
9 Add Object Storage
 +
:# When compete, jump to launch an instance or continue configuring additional services
  
8. Add Object Storage
+
10 Add the Orchestration service
 +
:# When compete, jump to launch an instance or continue configuring additional services
  
9. Install the Networking service
+
11 Add the Telemetry service
Networking considerations
+
:# When compete, jump to launch an instance or continue configuring additional services
Neutron concepts
 
Install Networking services
 
Neutron deployment use cases
 
  
10. Add the Orchestration service
+
12 Launch an Instance
  
11. Add the Telemetry service
+
[[Category:Documentation]]

Latest revision as of 23:59, 21 February 2014

The new OpenStack Networking Guide will be taking content from the Install and Cloud Admin Guides, which means the content of those two guides is going to be "beefed up" to provide more context for users so that they get a good understanding of what's going on, rather than just a series of steps. We are also considering moving nova-network to be with Neutron, rather than Nova. This is the target outline, of the relevant chapters.

NOTE: this is the current version, put here as a reference for us to work from.

Preface

Document change history

1 Architecture

  1. Conceptual architecture
  2. Logical architecture
  3. Example architectures

2 Basic operating system configuration

  1. Before you begin
  2. Networking
  3. Network Time Protocol (NTP)
  4. Passwords
  5. MySQL database
  6. OpenStack packages
  7. Messaging server

3 Configure the Identity Service

4 Configure the Image Service

5 Configure Compute services

  1. Compute service
  2. Install Compute controller services
  3. Configure a Compute node
  4. Enable Networking
  5. Launch an instance

6 Add the dashboard

7 Add the Block Storage Service

8 Add Object Storage

9 Install the Networking service

  1. Networking considerations
  2. Neutron concepts
  3. Install Networking services
  4. Neutron deployment use cases

10 Add the Orchestration service

11 Add the Telemetry service

Proposed changes

Preface

Document change history

1 Architecture

  1. Conceptual architecture
  1. Provide general explanation of "core" nodes... controller, network, and compute.
  2. Provide general explaination of "additional" nodes... storage.
  3. Explain general hardware requirements of nodes... cpu, disk, and memory.
  1. Logical architecture
  2. Example core architectures
  1. Two-node with Nova networking (two interfaces per node)
  1. Provide diagrams containing services on each node and physical/logical connectivity (e.g., network interfaces with usable IP addresses)
  1. Three-node with Neutron networking (two interfaces per node except network which has three)
  1. Provide diagrams containing services on each node and physical/logical connectivity (e.g., network interfaces with usable IP addresses)
  1. Indicate requirements for "surrounding" network components (e.g., do not use DHCP, external network should offer more than 1 IP address to support floating IPs etc.)
  2. Provide links to additional networking information (book?)
  1. Example architecture with additional nodes
  1. Add storage nodes to either of the core architectures
  1. Condensed archectectures
  1. Explain option to "condense" architectures with fewer nodes or network interfaces with the caveat that it makes troubleshooting more difficult and probably doesn't reflect a production environment (maybe?)

2 Basic operating system configuration

  1. Before you begin
  1. Prefer use of "base" installations rather than "everything" installations
  2. Provide recommended partition sizes and filesystem types? (maybe?)
  1. Networking
  1. Explain firewall situation (depends on distribution)
  2. Configuration for two-node arch (broken up by node)
  1. Provide recommended entries for /etc/hosts or DNS
  2. Note importance of key-based SSH authentication when considering multiple compute nodes with migration
  3. Provide connectivity tests
  1. Configuration for three-node arch (broken up by node)
  1. Provide recommended entries for /etc/hosts or DNS
  2. Note importance of key-based SSH authentication when considering multiple compute nodes with migration
  3. Provide connectivity tests
  1. Configuration for additional nodes (although I'm wondering if we should move these details to their associated chapters... e.g., swift)
  1. Install additional base services and useful troubleshooting tools
  1. ntp, wget, tcpdump...
  1. Passwords
  2. MySQL database
  1. Recommend further restricting grants before moving into production
  1. Messaging server (moved before OpenStack packages since the OpenStack repos don't provide these packages)
  2. OpenStack packages

3 Configure the Identity Service

  1. Add a "demo" tenant and user so that Neutron doesn't break
  2. Explain openrc files and how to use them (mostly covered in "Install the OpenStack command-line clients" chapter)

4 Configure the Image Service

5 Configure Compute services

  1. Compute service
  1. Change to "concepts" like the other services
  1. Install Compute controller services
  2. Configure a Compute node

6 Configure networking

  1. Networking strategy
  2. Networking considerations
  3. Configure Nova networking
  1. Which use case(s)?
  1. Neutron concepts
  1. ML2
  2. Open vSwitch
  3. GRE
  4. VXLAN
  1. Configure Neutron networking
  1. ML2 with... GRE or VXLAN?
  1. Install Networking services
  1. Install Networking services on a dedicated network node
  2. Install networking support on a dedicated compute node
  3. Install networking support on a dedicated controller node
  4. Create the base Neutron networks
  1. Neutron deployment use cases
  1. Single flat network
  2. Provider router with private networks
  3. Per-tenant routers with private networks

7 Add the dashboard

  1. When complete, jump to launch an instance or continue configuring additional services. We could launch an instance before the dashboard, but I think people feel GUIs provide a more polished experience. If we feel the dashboard is important, we should include screen shots for creating and launching an instance.
  2. Note that Cinder is required for the Dashboard to work

8 Add the Block Storage Service

  1. When compete, jump to launch an instance or continue configuring additional services

9 Add Object Storage

  1. When compete, jump to launch an instance or continue configuring additional services

10 Add the Orchestration service

  1. When compete, jump to launch an instance or continue configuring additional services

11 Add the Telemetry service

  1. When compete, jump to launch an instance or continue configuring additional services

12 Launch an Instance