Description of problem: The description of the Configuration Store and Wallaby in this section seem to overlap and are confusing. It seems that Wallaby and the Configuration store are one. But in 4.3, after having assumed that Wallaby is made up of three components including a configuration store, we are suddenly introduced to Wallaby and it's tools. Wallaby sounds suspiciously like the configuration store. I'd suggest someone read over this entire chapter and see if the information is still accurate (see comment below) and then also edit it so that the descriptions make more sense to a reader. Comment: There may be another bug here that is not a doc. bug. If The condor_config_store still exists then why not roll the wallaby commands into it. Are all these commands still there? Has this consolidation already happened? Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
*** Bug 633589 has been marked as a duplicate of this bug. ***
How much of the content to be addressed by this bug has been included in updates for https://bugzilla.redhat.com/show_bug.cgi?id=658867 and to some extent https://bugzilla.redhat.com/show_bug.cgi?id=670617? What is still to be added and addressed in the review?
Pushing to 2.1 due to time and resource constraints.
Deadline for this needinfo set to 30 June 2011 due to its inclusion in the 2.1 release. May change pending planning deadlines for MRG 2.1.
Can Will look at this? As I said "I'd suggest someone read over this entire chapter and see if the information is still accurate "
Rob, can you please read over the remote configuration chapter and advise of what changes are going to be required to clarify things. Needinfo deadline set for 2wks.
Please provide a better distinction between wallaby the service and wallaby the tools early in the docs. It's assumed that the reader understands that the Configuration Store is Wallaby the service but it is not explicitly explained. Also in the tools section it seems that the wallaby tool is the same name as the service - or is the same thing. This is confusing. i.e. wallaby load is the service. Right?
To better call out the difference between the wallaby service and the tool, as well as the different tool types, I suggest the following changes: Ch 4 4.1 Suggest a rewording of the first paragraph to something like the following: The configuration store is a central repository for configuration data. It contains several types of configuration entities which can be combined to form MRG Grid configurations for a node or group of nodes. The configuration store also provides revision control through snapshots. The wallaby service performs the duties of the configuration store. A configuration is not pushed out to managed nodes unless it has been activated. This means that a node could be running a different configuration than is reflected in the configuration store. When the store receives an activation request it will validate the state of the current configuration, and if successful the store will notify managed nodes that are affected that they should check in to receive a new configuration. Replace 'The configuration store records configurations as a series of entries in a database. Each entry contains certain elements, which can be paired with metadata. The elements are: ' with: The configuration entities contained within the store are: Parameters, Features, Nodes, Groups, and Subsystems. Each entity type has metadata associated with it for purposes of identifying and documenting a specific entity. Move installation section as described in BZ720782. Need to better indent the metadata for each entity type. It should be a subsection under the entity type like: Feature <desc> metadata for x <desc> metadata Nodes Replace text with: A node represents a physical machine that will have configurations applied to it. Node entities in the configuration store are often referred to as Managed Nodes. All Managed Nodes are part of the Internal Default Group, and be can be part of any number of additional groups. From 4.2 add (thus remove from 4.2): Managed nodes are considered either provisioned or unprovisioned. Nodes explicitly added to the store using remote tools are provisioned nodes. Nodes that have checked in with the store but have not explicitly been added are unprovisioned nodes. Unprovisioned nodes are managed the same way as provisioned nodes. They can be configured and added to groups just like provisioned nodes. A node must be explicitly added to the store (even if it already exists in the store) in order to change from unprovisioned to provisioned. Nodes are represented by their fully qualified domain names, and each node name in the store must be unique. Groups "A group is a group of nodes that will have parameters and features applied to it" -> A group is an entity that can have features and parameters applied to it, and while multiple nodes may be a part of. A group provides all member nodes the same configuration parameters. "Values for explicity-set group parameters will take priority over values for feature parameters" -> "Parameters that are explicitly set on a group will take priority over values from features set on that group." Snapshot Add: A snapshot can be created regardless of the validity of the configuration in the configuration store. As a result when a snapshot is loaded it must be explicitly activated before any configuration changes the snapshot contains will be pushed out to managed nodes. 4.3 "remote configuration tool" -> "remote configuration feature" Before "condor_configure_store" add: Section title "Guided tools" These tools are user-interactive tools that will step users through creating valid configurations and managing entities in the configuration store. These tools provide guidance specific to MRG Grid. Wallaby Tools -> "Non-Guided tools" The wallaby tool, which is part of the wallaby-utils rpm, provides a non-interactive interface for interacting with the configuration store. These tools are bare-bones and provide no MRG Grid specific knowledge.
*** Bug 742378 has been marked as a duplicate of this bug. ***
Additionally, to improve the flow and improve clarify suggest the following re-organization of the chapter: 1) Remote Configuration Introduction (Section 4.0) 2) Wallaby Service/Store explanation (Section 4.1 minus 'Configuring the store using condor_configure_store', 'Installing and initializing the configuration store', & 'Editing metadata sections') 3) Installation A) 4.1 Installing and initializing the configuration store B) Info covered in BZ720782 C) First paragraph from 4.2 (The condor-wallaby-client is installed ...) D) 4.2 Installing and configuring the remote configuration client 4) Overview of the tools (Section 4.3) 5) Details of condor_configure_store and condor_configure_pool tools A) 4.1 Configuring the store using condor_configure_store B) 4.2 Applying configurations to a node with condor_configure_pool C) 4.1 Editing metadata section 6) Example (Section 4.4)
Remote configuration chapter checked. Configuration store and wallaby are distinguished correctly in manual. >>> VERIFIED
reopen one small issue found: In chapter '4.1.3. Installing and configuring the remote configuration client' the name of file /etc/condor/config.d/40QMF should be changed to /etc/condor/config.d/40QMF.config as it is in Management Console Installation Guide. Sorry, I missed that earlier.
Verified on Revision 1-31 Name of configuration file /etc/condor/config.d/40QMF.config was changed properly. >>> VERIFIED
This book is now available on redhat.com/docs. Please raise a new bug if you spot any issues. Thanks, LKB