Adding more details to Figure 2.1 such as typical interface names (e.g., eth0) and lines connecting the interfaces would provide better visualization of the basic architecture. Additionally, a second diagram including a network node and associated details would provide a better visualization for those implementing Neutron. The diagrams and/or network interface configuration segments should also indicate which interfaces can support a default gateway (at least initially) to enable remote configuration (e.g., SSH) from another network.
-----------------------------------
Built: 2013-11-06T10:34:15 00:00
git SHA: 875931e322773a4b370fe7902777958be7073ccb
URL: http://docs.openstack.org/trunk/install-guide/install/apt/content/basics-networking.html
source File: file:/home/jenkins/workspace/openstack-install-deploy-guide-ubuntu/doc/install-guide/ch_basics.xml
xml:id: basics-networking
Which basic architecture generally obtains the best results from this guide? When implementing Neutron, the following three-node configuration has worked best for me:
1) One controller node with two network interfaces (internal management and external access)
2) One network node with three network interfaces (internal management, instance tunnels, and br-ex)
3) One compute node with two network interfaces (internal management and instance tunnels)
What's the possibility of standardizing on one architecture for at least the basic services to help streamline the documentation?