Chapter 2. Deployment host missing network information

[Andreas Krüger]

Chapter 2. Deployment host is missing a short entry, that it needs access to the container vlan you create on target hosts.

Container management: 172.29.236.0/22 (VLAN 10) in the guide.

If this is not configured, the deployment will fail.

[Jesse Pretorius (jesse-pretorius)]

It is recommended that the deployment host be on the same container/management network as the target hosts. This reduces the rate of failure for Ansible connectivity, especially with the volume of connections we use.

[Travis Truman (travis-truman)]

Perhaps the doc could include a note like: Ansible will require ssh access to the container management network from the deployment host.

[Michael Gugino (gugino-michael)]

We should have the containers on the management network. Calling it the 'container management vlan' is confusing.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/290145

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/290145
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=08dd1eb57c0a83c95e590f48361a707018b37a57
Submitter: Jenkins
Branch: master

commit 08dd1eb57c0a83c95e590f48361a707018b37a57
Author: Amy Marrich <email address hidden>
Date: Tue Mar 8 15:28:17 2016 -0600

    Adding Networking Information to Install Guide

    Added explanation and example for deployment host configuration

    Change-Id: Ie0621b63445968591d5bed60b0c71f892ae9c786
    Closes-Bug: #1550044

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/openstack-ansible 13.0.0 release.

[Davanum Srinivas (DIMS) (dims-v)]

This issue was fixed in the openstack/openstack-ansible 13.0.0 release.