Bug 699822

Summary: Update doc for hierarchical accounting groups with latest accountant case-handling rules
Product: Red Hat Enterprise MRG Reporter: Erik Erlandson <eerlands>
Component: Grid_User_GuideAssignee: Alison Young <alyoung>
Status: CLOSED CURRENTRELEASE QA Contact: ecs-bugs
Severity: medium Docs Contact:
Priority: high    
Version: 1.3CC: iboverma, jneedle, jskeoch, matt
Target Milestone: 2.0.1Keywords: Documentation
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-09-07 22:09:25 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: 733588    
Bug Blocks:    

Description Erik Erlandson 2011-04-26 16:54:57 UTC 
Description of problem:
Current documentation does not explain latest case handling rules, and difference between case-handling of accounting groups versus submittors.


Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=675703#c6
Comment 1 Erik Erlandson 2011-04-26 20:11:06 UTC 
Some modifications to grid user guide, section 10:


1) Example 10.1 should include a user name:  'group_physics.mcurie'


2) Right below example 10.1, should remove reference to case insensitive:

"The value for the AccountingGroup attribute is a submitter string. It must be enclosed in double quotation marks.  It may be of arbitrary length, and is case sensitive."


3) below example 10.5, remove this sentence:

"Group names are not case-sensitive and do not require the group_ prefix. However, group names should be unique, to avoid conflicts."


4) Add a new paragraphs under 'Changes caused by group quotas to accounting and negotiation':

The Accountant keeps track of resources used by accounting groups.  Accounting group entries are 'case preserving.'  That is, the Accountant stores each accounting group by the case it first encounters in the GROUP_NAMES configuration variable.  Future occurrences of accounting group are matched against the Accountant's version in a case-insensitive manner.  

Observe that full submitter names are treated as case sensitive, so one might see the following entries stored by the Accountant:

a.user   # full submitter entry
A.user   # full submitter entry, distinguished from 'a.user'
a        # single group entry, matches against 'a' and 'A'
Comment 2 Alison Young 2011-05-03 00:13:34 UTC 
setting to ASSIGNED as work yet to be completed.