Example layer 3 routed environment configuration limits VIP to POD1

Bug #1718188 reported by Jonathan Rosser
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Confirmed
Medium
Jimmy McCrory

Bug Description

- [x] This doc is inaccurate in this way:

The lb_vip_address is defined as 172.29.236.9. The POD1 management network is 172.29.236.0/24.

Therefore, I don't think it is possible for the vip to be served by services running on the other two infra nodes in the 239 and 242 sub-nets as it can't float into those network ranges.

I'm not sure that the proposed network setup works with haproxy as deployed by OSA - it may imply an external load balancer. If this is the case the docs/config should be amended to detail this.

-----------------------------------
Release: 16.0.1.dev3 on 2017-09-14 21:37
SHA: f9aa9e3152947793dfdfbc5e0315ceb9f9fd6ef8
Source: https://git.openstack.org/cgit/openstack/openstack-ansible/tree/doc/source/app-config-pod.rst
URL: https://docs.openstack.org/project-deploy-guide/openstack-ansible/pike/app-config-pod.html

Revision history for this message
Jean-Philippe Evrard (jean-philippe-evrard) wrote :

Please also check our bug triage conversation of today for the context.

Changed in openstack-ansible:
status: New → Confirmed
importance: Undecided → Medium
Changed in openstack-ansible:
assignee: nobody → Jimmy McCrory (jimmy-mccrory)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.