Bug 674700

Summary:	4.2 comments
Product:	Red Hat Enterprise MRG	Reporter:	Robert Rati <rrati>
Component:	Grid_User_Guide	Assignee:	Alison Young <alyoung>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Tomas Rusnak <trusnak>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	1.3	CC:	iboverma, mkudlej, trusnak
Target Milestone:	1.3.2
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-02-14 01:50:06 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Robert Rati 2011-02-02 23:29:17 UTC

Description of problem:
"Unprovisioned nodes receive the configuration defined in the default group." -> Unprovisioned nodes are managed the same as provisioned nodes, and can configured and added to groups just like provisioned nodes.

Applying configurations to a node with condor_configure_pool:
1) Example in step 1 is incorrect. The condor_configure_pool tool does not support --list-all-subsystems. Suggest using --list-all-features instead, which will list all features in the store.

Also, it doesn't list all the metadata. The list-all-<type> commands just list the all the names of the specific types. So --list-all-nodes will list all the names of Nodes in the store, and --list-all-features will list the name of all Features in the store.

To list specific data about a type, you use the list command:
condor_configure_pool -l -f Master,NodeAccess
Which will list all the metadata for the features named Master and NodeAccess.

"Answer y to instruct the tool to begin making the changes." -> After providing values for any parameters that are added by the tool invocation, answer y to instruct the tool to begin making the changes.

"Answer y to confirm and provide a name for the configuration" -> To create a named snapshot answer Y and provide a snapshot name. If a snapshot is not desired, answer N.

"Answer y to instruct the tool to validate the changes and push them out to the pool" -> If the changes are ready to be activated, answer Y otherwise answer N.

Note: A configuration that is successfully activated in this way will create a snapshot if a configuration name was not provided.

"When changes are activated through the -a option" -> When a configuration is activated in the same tool invocation as a configuration change

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

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:

Expected results:

Additional info:

Comment 1 Alison Young 2011-02-03 06:32:15 UTC

*** Bug 667928 has been marked as a duplicate of this bug. ***

Comment 2 Alison Young 2011-02-03 07:49:55 UTC

Changed in revision 7.13 to:

<para>
  Managed nodes are considered either <firstterm>provisioned</firstterm> or <firstterm>unprovisioned</firstterm>. 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 with <command>condor_configure_store</command> (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.
</para>

<para>
  To display entities in the configuration store and their metadata, use the <command>condor_configure_pool</command> command with the <command>--list-all-<replaceable>type</replaceable></command> option. The <command>--list-all-<replaceable>type</replaceable></command> command will list the all the names of the type specified. It is possible to list more than one type by using successive commands:
</para>
<screen>
$ condor_configure_pool --list-all-nodes --list-all-features
</screen>
<para>
  This example will list all the names of <parameter>Nodes</parameter> in the store and all the <parameter>Features</parameter> in the store.
</para>
<para>
  To list specific data about a type, use the list, <command>-l</command>, command:
</para>
<screen>
$ condor_configure_pool -l -f Master,NodeAccess
</screen>
<para>
  This example will list all the metadata for the features named <parameter>Master</parameter> and <parameter>NodeAccess</parameter>.
</para>

<para>
  When adding parameters to a node or group of nodes, the tool will prompt for the parameter values before asking to commit the changes to the configuration store. After providing values for any parameters that are added by the tool invocation, answer <command>Y</command> to instruct the tool to begin making the changes.
</para>

<para>
  Once the changes have been applied, the tool will ask if the configuration should be saved. To create a named snapshot answer <command>Y</command> and provide a snapshot name.  If a snapshot is not desired, answer <command>N</command>.
</para>

<para>
 The tool will ask if the changes should be activated. If the changes are ready to be activated, answer <command>Y</command> otherwise answer <command>N</command>.
</para>
<note>
  <title>Note</title>
  <para>
    A configuration that is successfully activated in this way will create a snapshot if a configuration name was not provided.
  </para>
</note>

<para>
  When a configuration is activated in the same tool invocation as a configuration change, a snapshot is generated. Snapshots can also be taken at any time using the <command>--take-snapshot</command> option with an appropriate name:
</para>

Build: 	Red_Hat_Enterprise_MRG-Grid_User_Guide-1.3-web-en-US-7-13.el5

Comment 3 Robert Rati 2011-02-03 14:53:14 UTC

Applying configurations to a node with condor_configure_pool:
1) There is no metadata displayed when --list-all-type is used, only the names of the types.  "To display entities in the configuration store and their metadata" -> "To display the names of entities in the configuration store"

"all the names of Nodes in the store and all the Features in the store" -> all the names of the Nodes and Features in the store

Comment 4 Alison Young 2011-02-07 10:39:28 UTC

Change made in revision 7.14, build: Red_Hat_Enterprise_MRG-Grid_User_Guide-1.3-web-en-US-7-14.el5

Code snippets:

<para>
To display the names of entities in the configuration store, use the <command>condor_configure_pool</command> command with the <command>--list-all-<replaceable>type</replaceable></command> option. The <command>--list-all-<replaceable>type</replaceable></command> command will list the all the names of the type specified. It is possible to list more than one type by using successive commands:
</para>

<para>
This example will list all the names of <parameter>Nodes</parameter> in the store and <parameter>Features</parameter> in the store.
</para>

Comment 5 Tomas Rusnak 2011-02-10 15:12:15 UTC

All changes included in Revision 7.14.

>>> VERIFIED