Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 645909

Summary: Update condor_configure_pool docs
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: high Docs Contact:
Priority: high    
Version: 1.3CC: iboverma, jneedle, lbrindle, matt, 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:18:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 663805    

Description Robert Rati 2010-10-22 20:54:45 UTC 
Description of problem:
BZ628741 made changes to the condor_configure_pool tool and added 2 new commands: edit and insert.  The insert command will insert features at the highest priority.  The edit command which will dump the group/node data into a file in YAML format and open an editor similar to how the store tool works.

Also, need to change and references of -a|--add to mention appending at lowest priority.


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


How reproducible:


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


Expected results:


Additional info:
Comment 1 Lana Brindley 2010-12-16 22:01:27 UTC 
Adding to tracker bug for 1.3.2.

LKB
Comment 2 Alison Young 2011-01-19 23:24:46 UTC 
Robert can you please clarify this bug? Do the insert and edit commands need to be documented? Are the -a|-add commands still correct and just need the note about appending at lowest priority?

Thanks, 
Alison
Comment 3 Robert Rati 2011-01-21 13:38:19 UTC 
It looks like the wording changes for -a, -e, and -i are already in the documentation.  I'm assuming Lana did it if you didn't.  The only thing I see missing is a note that -e will open an editor and uses an editor.  See 4.1 Configuring the store using condor_configure_store, step 1 for an example of the type of info I'm talking about.  Mention it uses $EDITOR, reference the metadata section, etc.
Comment 5 Tomas Rusnak 2011-02-10 11:00:30 UTC 
Requested part included in Revision 7.14

[citation]
Adding entities into the configuration store will invoke a text editor for entering and editing metadata about them. The text editor is defined in $EDITOR, and will default to vi. See Editing metadata for information about using the editor. 
[/citation]

>>> VERIFIED