Bug 720782

Summary: Re-organize Remote Configuration installation sections
Product: Red Hat Enterprise MRG Reporter: Robert Rati <rrati>
Component: Grid_User_GuideAssignee: Alison Young <alyoung>
Status: CLOSED CURRENTRELEASE QA Contact: Tomas Rusnak <trusnak>
Severity: unspecified Docs Contact:
Priority: medium    
Version: DevelopmentCC: jneedle, lbrindle, matt, trusnak
Target Milestone: 2.1   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-26 19:18:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 733205, 733324    
Bug Blocks:    

Description Robert Rati 2011-07-12 18:21:42 UTC
Description of problem:
Currently, the instructions for installing remote configuration are spread out over 2 sections (4.1 and 4.2) and there's no indication in the index that multiple sections need to be read for installation/configuration to be complete.  We should create a section that entails the installation/configuration of the feature that is separate from the details.  This section should probably be placed before 4.1, but after the brief introduction and explanation of the parts to remote configuration.

The new section should contain the content from:
4.1 Installing and initializing the configuration store
4.2 Installing and configuring the remote configuration client

Suggested new section wording:
Installing and initializing the configuration store

    Install the following packages with the yum command:
        wallaby
        wallaby-utils
        condor-wallaby-base-db
        condor-wallaby-tools 

    Note: The configuration store should only be installed on 1 node in the pool

    # yum install wallaby wallaby-utils condor-wallaby-base-db condor-wallaby-tools

    Configure wallaby:
    Wallaby's configuration file is located at /etc/sysconfig/wallaby-agent.  The default configuration will work without modification if wallaby is installed on the node that is running qpid with stock configuration.  If the broker is on another machine, or has been secured, then the following parameters may need to be added or edited in wallaby's configuration file:

WALLABY_BROKER_HOST - The hostname or IP address of the machine running the broker
WALLABY_BROKER_PORT - The port on WALLABY_BROKER_HOST where the broker is listening
WALLABY_BROKER_MECHANISM - Space separated list of authentication methods (Available options are ANONYMOUS, PLAIN, GSSAPI)
WALLABY_BROKER_USER - The username used when authenticating with the broker
WALLABY_BROKER_PASSWORD - The password used when authenticating with the broker

    Start the wallaby service:

    # service wallaby start

    Initialize the store with the default database for condor:

    $ wallaby load /var/lib/condor-wallaby-base-db/condor-base-db.snapshot

    The default database contains some common parameters and features with default values that can be used to build a condor pool.
    For more information about the metadata associated with various features used in the remote configuration feature, see Appendix C, Feature Metadata. 


Installing and configuring the remote configuration client

    To allow a machine to be managed with remote configuration, install the following package with the yum command:
        condor-wallaby-client 

    Note: All machine's that are to be managed with remote configuration must have condor-wallaby-client installed

    # yum install condor-wallaby-client

    The remote configuration client needs to be told the location of the broker that is communicating with the configuration store. Open the condor local configuration directory and create or edit a configuration file with the following parameter, and the IP address or hostname of the machine running the broker:

    QMF_BROKER_HOST = wallaby_broker

    Additional parameters can be added to the configuration file if the configd needs to communicate with a secured broker:

    QMF_BROKER_AUTH_MECHANISM - Space separated list of authentication methods (Available options are ANONYMOUS, PLAIN, GSSAPI)
    CONFIGD_ARGS - A list of arguments to pass to the configd:
       -U|--user - The username used when authenticating with the broker
       -P|--password - The password used when authenticating with the broker

    Restart condor before attempting to configure nodes. 


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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 6 Tomas Rusnak 2011-11-14 12:27:32 UTC
Change confirmed in all chapters after 4.1. Configuration Store Installation.

Revision 1-19	Wed Nov 02 2011	Alison Young
BZ#720782 - Remote Configuration updates

Revision info updated.

>>> VERIFIED

Comment 7 Lana Brindley 2012-01-26 19:18:01 UTC
This book is now available on redhat.com/docs. Please raise a new bug if you spot any issues.

Thanks,
LKB