Difference between revisions of "NovaNetNeutronParity"
m (→Nova Networking Parity) |
|||
| Line 2: | Line 2: | ||
== Documentation == | == Documentation == | ||
| + | |||
| + | * [https://docs.google.com/document/d/1E9CiG8fmcn0FMI15zpE0dRQ1CcFhXV8TxL7mU7vgWv8/edit?usp=sharing Early Parity Discussion Document] | ||
== Quality of Default Implementation == | == Quality of Default Implementation == | ||
| + | |||
| + | * [https://etherpad.openstack.org/p/icehouse-summit-qa-neutron Icehouse Summit QA Neutron session etherpad] | ||
| + | * [https://etherpad.openstack.org/p/icehouse-summit-qa-multi-node Icehouse Summit on testing with mulitple nodes] | ||
| + | * [https://etherpad.openstack.org/p/icehouse-summit-qa-negative-tests Icehouse Summit on negative testing] | ||
=== Performance === | === Performance === | ||
| Line 15: | Line 21: | ||
== API Integration == | == API Integration == | ||
| + | |||
| + | === Points to Look For === | ||
| + | |||
| + | * Throwing exceptions across the API boundary that differ than those thrown by alternate implementations may be a parity issue. (e.g. validate_networks in neutron throws in the presence of multiple networks, nova-network does not) | ||
| + | * NotImplemented may be a significant parity issue. Even if addressed through alternate mechanisms, this is a testing /api binary compatible mismatch | ||
== Functional Parity == | == Functional Parity == | ||
| + | |||
| + | === Network Manager Types === | ||
| + | |||
| + | [[NovaNetNeutronRecipes]] | ||
| + | |||
| + | The FlatNetworkManager (thanks rkukura for spelling this out!): | ||
| + | |||
| + | * [http://openstack.redhat.com/forum/discussion/comment/2363#Comment_2363] | ||
| + | * [http://openstack.redhat.com/forum/discussion/comment/2394#Comment_2394] | ||
| + | |||
| + | (would this work for FlatDHCPNetworkManager as well?) | ||
| + | |||
| + | |||
| + | === Multi-Host === | ||
| + | |||
| + | * [https://etherpad.openstack.org/p/Distributed-Virtual-Router Icehouse summit Distributed Router] (possible multi-host approach) | ||
Revision as of 20:30, 9 December 2013
Contents
Making Parity Happen
Documentation
Quality of Default Implementation
- Icehouse Summit QA Neutron session etherpad
- Icehouse Summit on testing with mulitple nodes
- Icehouse Summit on negative testing
Performance
Configuration
Communication
Scalability
HA Options
API Integration
Points to Look For
- Throwing exceptions across the API boundary that differ than those thrown by alternate implementations may be a parity issue. (e.g. validate_networks in neutron throws in the presence of multiple networks, nova-network does not)
- NotImplemented may be a significant parity issue. Even if addressed through alternate mechanisms, this is a testing /api binary compatible mismatch
Functional Parity
Network Manager Types
The FlatNetworkManager (thanks rkukura for spelling this out!):
(would this work for FlatDHCPNetworkManager as well?)
Multi-Host
- Icehouse summit Distributed Router (possible multi-host approach)
