openstack
/
security-doc
Code Issues Proposed changes

Networking services in OpenStack Security Guide - Rewrite for clarity 

Rewrite some sections of the Network services page for clarity.

Fixes bug #1447759

Change-Id: I4720c03b035062d89e18a0921e2d0eed49a0e06f
This commit is contained in:
Arvind Somya 2015-08-11 06:33:04 -04:00
parent 9152567894
commit 1e4cb1ae27
1 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
security-guide/source/networking/services.rst
View File

@ -187,8 +187,11 @@ Overlapping IP addresses
If nodes that run either neutron-l3-agent or neutron-dhcp-agent use
overlapping IP addresses, those nodes must use Linux network
namespaces. By default, the DHCP and L3 agents use Linux network
namespaces. However, if the host does not support these namespaces,
run the DHCP and L3 agents on different hosts.
namespaces and run in their own respective namespaces. However,
if the host does not support multiple namespaces, the DHCP and L3
agents should be run on separate hosts. This is due to the fact that
there is no isloation between the IP addresses created by the L3
agent and the DHCP agent.
If network namespace support is not present, a further limitation of
the L3 agent is that only a single logical router is supported.
@ -196,7 +199,9 @@ Overlapping IP addresses
Multi-host DHCP-agent
OpenStack Networking supports multiple L3 and DHCP agents with load
balancing. However, tight coupling of the location of the virtual
machine is not supported.
machine is not supported. In other words, the default Virtual Machine
scheduler will not take the location of the agents into account when
creating virtual machines.
No IPv6 support for L3 agents
The neutron-l3-agent, used by many plug-ins to implement L3