Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1599552 - [ref-arch][AWS] Unclear openshift-ansible logging parameter format in "Aggregated Logging" guide
Summary: [ref-arch][AWS] Unclear openshift-ansible logging parameter format in "Aggreg...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Reference Architecture
Version: 3.9.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: scollier
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-10 04:27 UTC by Gaoyun Pei
Modified: 2018-07-17 14:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-17 14:19:04 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Gaoyun Pei 2018-07-10 04:27:10 UTC
Description of problem:
https://access.redhat.com/documentation/en-us/reference_architectures/2018/html/deploying_and_managing_openshift_3.9_on_amazon_web_services/components_and_considerations#aggregated_logging

In the end of this section, we have a openshift-ansible vars list for deploying logging as below:

###
openshift_logging_install_logging=true
openshift_logging_es_pvc_dynamic: true
openshift_logging_es_pvc_size: 100Gi
openshift_logging_es_cluster_size: 3
openshift_logging_es_nodeselector: {"region":"infra"}
openshift_logging_kibana_nodeselector: {"region":"infra"}
openshift_logging_curator_nodeselector: {"region":"infra"}
openshift_logging_es_number_of_replicas: 1
###

But the vars' format were not unified, we should use either "key=value" in ansible static inventory or "key: value" in a variable file. Example vars better to be consistent.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Ryan Cook 2018-07-10 15:39:11 UTC
Resolved in the latest document update


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