NetworkingGuide/TOC
< NetworkingGuide
Revision as of 13:11, 8 August 2014 by Shaun McCance (talk | contribs)
This is the proposed TOC for the Networking Guide. (Blueprint located at https://blueprints.launchpad.net/openstack-manuals/+spec/create-networking-guide .)
NOTE: This is the initial "import" from the install and admin guides, as a starting point.
Resources:
- Grizzly Networking Administration Guide
- Networking section of Install Guide for Red Hat, SUSE, Debian, Ubuntu
- Networking section of Cloud Admin Guide
- Networking section of Operators Guide
- Networking section of Security Guide
- Networking section of Config Reference
- Network API Reference
Persona (Target Audience)
This guide targets OpenStack administrators seeking to deploy and manage neutron.
Preface
Document change history
Networking
- Introduction to networking
- Explanation of layers
- Switches
- Routers
- Firewalls
- Tunnel (segmentation) technologies
- Layer 2
- VLAN
- Layer 3
- GRE
- VXLAN
- Layer 2
- Namespaces
- Neutron data model (how above networking concepts are done in Neutron)
- Networks
- Subnets
- Ports
- Extensions
- Networking (neutron) architecture
- Overview/concepts
- Service/component hierarchy
- Neutron server -> Plug-in -> Agents
- Example architectures (possibly take from use cases in Grizzly Network Guide)
- Example 1
- Controller / Network node
- Server
- Plug-in
- Agents
- Compute node
- Plug-in
- Agents
- Controller / Network node
- Example 2
- Controller node
- Server
- Plug-in
- Network node
- Plug-in
- Agents
- Compute nodes
- Plug-in
- Agents
- Controller node
- Example 1
- Service/component hierarchy
- Server
- Overview/concepts (provides API, manages database, etc.)
- Configuration file (particularly core_plugin and service_plugins)
- Plug-in
- Overview/concepts (manages agents)
- Configuration file (generic location... /etc/neutron/plugins/*)
- Agents
- Overview/concepts (provide layer 2/3 connectivity to instances, handle physical-virtual network transition, handle metadata, etc.)
- Layer 2 (Ethernet/Switching)
- Linux Bridge
- Overview/concepts
- Configuration file (generally within plug-in configuration)
- OVS
- Overview/concepts
- Configuration file (generally within plug-in configuration)
- Layer 3 (IP/Routing)
- L3
- Overview/concepts
- Configuration file
- DHCP
- Overview/concepts
- Configuration file
- L3
- Miscellaneous
- Metadata
- Overview/concepts
- Configuration file
- Metadata
- Linux Bridge
- Overview/concepts
4. Plug-ins
1. ML2 1. Overview 1. Architecture 2. Configuration file organization, relationships, etc. 2. Network type drivers 1. Flat 2. VLAN 3. GRE 4. VXLAN 3. Tenant network types 1. Local 2. VLAN 1. VLAN ID ranges 3. GRE 1. Tunnel ID ranges 4. VXLAN 1. VNI ID ranges 4. Mechanisms 1. Linux Bridge 1. Option stanza/section 2. OVS 1. Option stanza/section 3. Open Daylight 4. L2 Population 5. Proprietary (vendor) 5. Security 1. Options 2. Proprietary (vendor)
5. Deployment
1. Example architecture (three-node) 1. Controller node 1. Functions (provides API) 2. Network node 1. Functions (handles routing, nat, floating IPs, etc.) 3. Compute nodes 1. Functions (implements security groups) 2. Scenarios (provide configuration, diagrams, and flow of communication when launching an instance) 1. Linux bridge using VLAN 2. Linux bridge using GRE 3. Linux bridge using VXLAN 4. OVS with VLAN 5. OVS with GRE 6. OVS with VXLAN 7. Mixed Linux Bridge and OVS
6. Scalability and high availability
1. DHCP agents 2. L3 Agents 3. DVR (Juno)
7. Advanced configuration
1. Provider networks
8. Advanced operational features
1. Logging
9. Advanced services
1. LBaaS 2. FWaaS 3. VPNaaS 4. Service Chaining (regXboi)
10. Group policy (regXboi)
1. How it differs from legacy neutron data model
11. Debugging
1. Neutron-debug command