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
| ... | ... |
@@ -261,15 +261,18 @@ controller node. |
| 261 | 261 |
|
| 262 | 262 |
## Neutron Networking options used to create Neutron Subnets |
| 263 | 263 |
|
| 264 |
- FIXED_RANGE="10.1.1.0/24" |
|
| 264 |
+ FIXED_RANGE="203.0.113.0/24" |
|
| 265 | 265 |
PROVIDER_SUBNET_NAME="provider_net" |
| 266 | 266 |
PROVIDER_NETWORK_TYPE="vlan" |
| 267 | 267 |
SEGMENTATION_ID=2010 |
| 268 | 268 |
|
| 269 | 269 |
In this configuration we are defining FIXED_RANGE to be a |
| 270 |
-subnet that exists in the private RFC1918 address space - however |
|
| 271 |
-in a real setup FIXED_RANGE would be a public IP address range, so |
|
| 272 |
-that you could access your instances from the public internet. |
|
| 270 |
+publicly routed IPv4 subnet. In this specific instance we are using |
|
| 271 |
+the special TEST-NET-3 subnet defined in `RFC 5737 <http://tools.ietf.org/html/rfc5737>`_, |
|
| 272 |
+which is used for documentation. In your DevStack setup, FIXED_RANGE |
|
| 273 |
+would be a public IP address range that you or your organization has |
|
| 274 |
+allocated to you, so that you could access your instances from the |
|
| 275 |
+public internet. |
|
| 273 | 276 |
|
| 274 | 277 |
The following is a snippet of the DevStack configuration on the |
| 275 | 278 |
compute node. |