Bug 1232439 - Isolated networks should allow a specific range of IPs
Summary: Isolated networks should allow a specific range of IPs
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
Target Milestone: ga
: Director
Assignee: Tomas Sedovic
QA Contact: Eran Kuris
Depends On:
TreeView+ depends on / blocked
Reported: 2015-06-16 18:34 UTC by Dan Sneddon
Modified: 2015-08-05 13:53 UTC (History)
8 users (show)

Fixed In Version: openstack-tripleo-heat-templates-0.8.6-13.el7ost
Doc Type: Enhancement
Doc Text:
With this release, a new enhancement allows allocating specific IP address ranges for isolated networks. As a result, it is now possible to specify IP address allocation by setting the following parameters in the Overcloud Orchestration template: * InternalApiAllocationPools * StorageAllocationPools * StorageMgmtAllocationPools * TenantAllocationPools * ExternalAllocationPools
Clone Of:
Last Closed: 2015-08-05 13:53:57 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
OpenStack gerrit 191169 None None None Never
OpenStack gerrit 192349 None None None Never
Red Hat Product Errata RHEA-2015:1549 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform director Release 2015-08-05 17:49:10 UTC

Description Dan Sneddon 2015-06-16 18:34:47 UTC
Description of problem:
When creating isolated networks for the overcloud, there is no way to specify what range of IP addresses the hosts should be assigned. 

Version-Release number of selected component (if applicable):
openstack-tripleo-heat-templates  0.8.6-2.el7ost
(any poodle/puddle cut before June 16, 2015)

How reproducible:

Steps to Reproduce:
1. Enable network isolation

Actual results:
There is no way to set the IP address range for isolated networks.

Expected results:
You should be able to set an IP address range for the isolated networks.

Additional info:
We just merged a patch downstream to enable this functionality. We need to test a deployment with multiple networks, and make sure that all the assigned IPs were within the range specified. This can be done by adding the following to the environment file where we enable isolated networks:

  InternalApiAllocationPools: [{'start': '', 'end': ''}]
  StorageAllocationPools: [{'start': '', 'end': ''}]
  StorageMgmtAllocationPools: [{'start': '', 'end': ''}]
  TenantAllocationPools: [{'start': '', 'end': ''}]
  ExternalAllocationPools: [{'start': '', 'end': ''}]

Comment 3 Dan Sneddon 2015-06-16 18:36:34 UTC
I just discovered a bug that will prevent this from working with the external net. We can remove the ExternalAllocationPools definition from the above and test the other networks, or wait for a new poodle to get cut that includes this patch: https://review.openstack.org/#/c/192349/

Comment 6 Eran Kuris 2015-07-02 13:25:52 UTC
I need to get more info about step to reproduce .

Comment 7 Dan Sneddon 2015-07-02 18:42:16 UTC
This was fixed when we added the AllocationPools to the network environment file. I have validated it, and all deploys are now using the <network>AllocationPools parameters.

If you are deploying via virt (and just using the -e includes for network-isolation.yaml and single-nic-with-vlans.yaml), you should see that the IP addresses of the overcloud begin at .4. There are some problems with virt deploys, so it doesn't need to get to CREATE_COMPLETE, just far enough that you can log in to the overcloud nodes and see that their IPs on the isolated networks (not the ctlplane) start at .4 (because of the default AllocationPools defined in the network definitions in the 'network' directory of T-H-T).

If you are deploying on bare metal, something similar to this should appear in your network-environment.yaml (with different IPs). The IPs selected for the overcloud should start at .10, since all the AllocationPools start at .10:

  # Customize the IP subnets to match the local environment
  InternalApiAllocationPools: [{'start': '', 'end': ''}]
  StorageAllocationPools: [{'start': '', 'end': ''}]
  StorageMgmtAllocationPools: [{'start': '', 'end': ''}]
  TenantAllocationPools: [{'start': '', 'end': ''}]
  ExternalAllocationPools: [{'start': '', 'end': ''}]
  InternalApiNetworkVlanID: 201
  StorageNetworkVlanID: 204
  StorageMgmtNetworkVlanID: 203
  TenantNetworkVlanID: 205
  ExternalNetworkVlanID: 104
  # Specify the gateway on the external network.
  # Customize bonding options
      "bond_mode=balance-tcp lacp=active other-config:lacp-fallback-ab=true"

I have also validated that this is working on bare metal.

Comment 8 Eran Kuris 2015-07-05 06:25:45 UTC
Verified on RHEL-OSP director puddle 7.0 RC puddle 2015-06-29-1
[stack@instack ~]$ . stackrc 
[stack@instack ~]$ neutron subnet-list 
| id                                   | name                | cidr          | allocation_pools                               |
| 236a2c40-4f1f-449f-9435-41154714ba07 | storage_subnet      | | {"start": "", "end": ""} |
| 2bc81643-3d6a-4500-b25e-be13e6dbd6dd | internal_api_subnet | | {"start": "", "end": ""} |
| 2d036047-c1da-46b5-b7a2-d2ca9fd14b2c | storage_mgmt_subnet | | {"start": "", "end": ""} |
| 52b5cb2d-8622-4c44-9f43-8008105604d2 |                     |  | {"start": "", "end": ""}    |
| 67def19c-dd9f-4e4c-be3b-05288ce89e50 | tenant_subnet       | | {"start": "", "end": ""} |
| 7f12b52e-b348-42be-b202-0bbd918dfe7e | external_subnet     |   | {"start": "", "end": ""}     |
[stack@instack ~]$ rpm -qa | grep openstack-tripleo-heat
[stack@instack ~]$

Comment 10 errata-xmlrpc 2015-08-05 13:53:57 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.