From d72b839b7f15a8065d2f7bcceff0a9299ea9c901 Mon Sep 17 00:00:00 2001 From: "Sean M. Collins" Date: Thu, 18 Jun 2015 12:40:09 -0400 Subject: [PATCH] Docs: Use RFC5737 for Provider Networking That'll make things more clear that with the provider networking feature in DevStack, FIXED_RANGE will be a routed IPv4 subnet that gives routed IPv4 addresses to instances without using floating IPs. Change-Id: Ie26d75ac5ff285a25762c4f61fd9800b0382886b --- doc/source/guides/neutron.rst | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/doc/source/guides/neutron.rst b/doc/source/guides/neutron.rst index bdfd3a4afa..40a5632b86 100644 --- a/doc/source/guides/neutron.rst +++ b/doc/source/guides/neutron.rst @@ -261,15 +261,18 @@ controller node. ## Neutron Networking options used to create Neutron Subnets - FIXED_RANGE="10.1.1.0/24" + FIXED_RANGE="203.0.113.0/24" PROVIDER_SUBNET_NAME="provider_net" PROVIDER_NETWORK_TYPE="vlan" SEGMENTATION_ID=2010 In this configuration we are defining FIXED_RANGE to be a -subnet that exists in the private RFC1918 address space - however -in a real setup FIXED_RANGE would be a public IP address range, so -that you could access your instances from the public internet. +publicly routed IPv4 subnet. In this specific instance we are using +the special TEST-NET-3 subnet defined in `RFC 5737 `_, +which is used for documentation. In your DevStack setup, FIXED_RANGE +would be a public IP address range that you or your organization has +allocated to you, so that you could access your instances from the +public internet. The following is a snippet of the DevStack configuration on the compute node.