Bug 1393718

Summary: Consistent handling of addresses.
Product: Red Hat OpenStack Reporter: Leonid Natapov <lnatapov>
Component: opstools-ansibleAssignee: Lars Kellogg-Stedman <lars>
Status: CLOSED CURRENTRELEASE QA Contact: Leonid Natapov <lnatapov>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 10.0 (Newton)CC: fdinitto, mmagr, oblaut
Target Milestone: ---Keywords: Tracking
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-11-08 11:39:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Leonid Natapov 2016-11-10 08:39:45 UTC 
Proposal that for all of our services, we define the following variables:

<servicename>_port:
<servicename>_listen_addresses:
<servicename>_server_address:

A service binds to addresses in <servicename>_listen_addresses on <servicename>_port. Clients of the service connect to <servicename>_server_address (on <servicename>_port). So instead of e.g., the senu module having sensu_redis_server, the sensu module would depend on the redis module and would use redis_server_address.

This will in general require separating role defaults from the actual implementation (so, having both a redis role that sets the defaults, and a redis/server role that performs the actual configuration)
Comment 2 Martin Magr 2017-11-08 11:39:45 UTC 
We have consistent parameters naming already. Reusing of some of the parameters cannot be done, because that lower module flexibility.