openstack
/
fuel-docs
Code Issues Proposed changes

Correct and improve Neutron L2 and L3 requirements 

- corrected wrong requirement about admin tenant network
- improved requirements in case of tunneling segmentation
- improved description for VMs attached to the external network

Change-Id: I62322dd5797ad39edf451c2652e4d0a013ff26ad
Closes-Bug: #1590149
Related-Bug: #1586332
This commit is contained in:
Giuseppe Cossu 2016-06-07 23:25:32 +02:00
parent 91653314cb
commit 3e2bea05a7
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
userdocs/fuel-install-guide/sysreq/sysreq_network_requirements.rst
View File

@ -152,14 +152,15 @@ The requirements for Public, Storage, and Management networks are:
Neutron L2 and L3 requirements are:
* Each project's network requires one unique VLAN ID.
* Internal network must be isolated from both private and public networks
for security reasons.
* Each project's network requires one unique VLAN ID (using VLAN segmentation) or
unique segmentation ID (using GRE or VxLAN)
* Admin project network is isolated from both private and public networks for
security reasons.
* For floating network each defined project, including the Admin project,
requires one IP address from the floating IP address range.
This IP address goes to the virtual interface of the project's virtual router.
* Each VM instance connected to the external network requires one IP address
from the floating IP range.
* Direct connection to the external network requires one IP address from the
floating IP range for each VM.
* The floating IP address range should not intersect with the Public network
address ranges.
* Specify addresses for the guest OS DNS servers if you do not want to use