Bug 1393718 - Consistent handling of addresses.
Summary: Consistent handling of addresses.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: opstools-ansible
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Lars Kellogg-Stedman
QA Contact: Leonid Natapov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-10 08:39 UTC by Leonid Natapov
Modified: 2017-11-08 11:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-08 11:39:45 UTC
Target Upstream Version:


Attachments (Terms of Use)

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.


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