Comment 61 for bug 1656378

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-manuals (master)

Reviewed: https://review.openstack.org/466135
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=aeb0c2e1e7d8f0b305aa26ac797b29373f30008f
Submitter: Jenkins
Branch: master

commit aeb0c2e1e7d8f0b305aa26ac797b29373f30008f
Author: Akihiro Motoki <email address hidden>
Date: Fri May 19 11:31:13 2017 +0900

    [networking] RFC 5737 compliance: service subnets

    Replace non-compliant subnets in:

    config-dns-int.rst

    Subnet mappings are as follows:
    - 172.24.4.0/24 -> 198.51.100.93/24
    - 172.24.5.0/24 -> 203.0.113.0/24
    - 10.0.0.0/24 -> 192.0.2.0/26
    - 10.0.1.0/24 -> 192.0.2.64/26
    - 55.114.111.93/24 -> 192.0.2.224/27

    The documentation address ranges are selected
    based on the following policy:
    - The size of the first two subnets must be 24
      because ipv4_ptr_zone_prefix_size is 24.
    - Address range of 192.0.2.0/25 are assigned to
      private subnets.
    - 192.0.2.224/27 is assigned to a subnet for designate API.

    Change-Id: If0084baca1fa723480c2f059d15dca2c93778be2
    Partial-Bug: #1656378