Bug 1029422
Summary: | oo-install should support user set up activemq replicants and datastore replicants. | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Johnny Liu <jialiu> |
Component: | Node | Assignee: | Luke Meyer <lmeyer> |
Status: | CLOSED DEFERRED | QA Contact: | libra bugs <libra-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2.0.0 | CC: | bleanhar, libra-onpremise-devel, mmasters |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-11-19 14:15:02 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: | |
Embargoed: |
Description
Johnny Liu
2013-11-12 11:28:06 UTC
Looks like datastore replicants can not be set up totally automatically, while activemq replicants could. So change the summary. CONF_DATASTORE_REPLICANTS should totally automate configuration of datastore replicants. Is there a bug report for its failure to do so? I think the bug is that currently oo-install's OSE workflow never asks the user if they would like to set that value. This could simply be something we don't support for now given that oo-install main focus for OSE is configuring demos environments right now. Does oo-install's OSE workflow ask the user if they would like to set the value for ActiveMQ replicants then? To my knowledge all of the default values in openshift.sh are assumed. (In reply to Miciah Dashiel Butler Masters from comment #3) > CONF_DATASTORE_REPLICANTS should totally automate configuration of datastore > replicants. Is there a bug report for its failure to do so? Check openshift.sh, you will see the following codes: configure_datastore() { <--snp--> if ! [[ ${datastore_replicants} =~ , ]] then # This mongod will _not_ be part of a replicated setup. configure_datastore_add_users fi } That means user need do "configure_datastore_add_users" manually when datastore replicants is set if my understanding is right. (In reply to Miciah Dashiel Butler Masters from comment #5) > Does oo-install's OSE workflow ask the user if they would like to set the > value for ActiveMQ replicants then? No, oo-install's OSE workflow does not ask user currently, that is the point of this bug. Ah, yes, one must run (for example) `openshift.sh datastore_replicants=datastore01.example.com,datastore02.example.com,datastore03.example.com actions=configure_datastore_add_replicants,configure_datastore_add_users` on one of the replicants after they are all installed and running. This feature is captured in a Trello card: https://trello.com/c/f4T9Amo5 |