[Bioclusters] Cluster ChargeBack Schemes

[Steve Pittard]

Thanks. We actually have SGE N1 in place. I guess didn't explain my 
interest very well. Its more related to policies than it is to load 
management software. I know that I have lots of flexibility in how to 
setup and manage queues but I'm more interested in what others have 
found  to be popular *policies* amongst users. What types of chargeback 
policies have been perceived as being "good" (or not) ? How are you 
handling priorities in terms of power users vs the average user. Are 
you using prime vs non prime policies. Again. I know that I can 
implement lots of different schemes in SGE, PBS, LSF, etc (I've been 
doing this for quite some time). I'm just looking for feedback on how 
people are establishing use and priority policies and how well received 
those policies have been. Thanks

On Monday, January 17, 2005, at 10:10 AM, Rayson Ho wrote:

> The supported version of SGE 6.0 has a new feature called the ARCo
> (Accounting and Reporting Console).
>
> http://www.sun.com/software/gridware/index.xml
>
> "... ARCo that feeds accounting information into a relational external
> database. (Supported Databases are Oracle and PostgreSQL).
>
> Management and users can run the ARCo tool to generate usage reports
> per Department, Project, User, Host and make sure the computer
> resources match the business needs."
>
> Rayson
>
>
> --- Steve Pittard <wsp at emory.edu> wrote:
>> Hello, I'm interested in one of the more boring aspects of high
>> throughput
>> cluster computing which is that of implementing chargeback schemes
>> and
>> organizing queue systems to insure, for example, that a user who
>> might
>> have bought %40 of a cluster (in terms of nodes) is always assured
>> priority
>> access (on 40% of the nodes). Now. I use Sun Grid Engine and have
>> used it
>> to establish priorities and queues though I'm curious how other
>> people manage
>> this problem.
>>
>> Users who actually buy nodes to add on to the cluster are
>> particularly conerned about being able to use "their" nodes whenver
>> they submit a job. Of course
>> I explain and show them to them how the queuing system (Sun Grid
>> Engine) works
>> and while that helps them to understand what is going on underneath
>> the hood
>> its a common problem that I have to deal with perceptions (mostly
>> from power
>> users) that they can indeed get "their share".
>>
>> How are others setting things up in terms of policies ? Are you
>> creating
>> subscriptions based on anticipated usage ? Weighted queues to reflect
>> someone's investment in the cluster ? A straight , one-class  queue
>> system ? Prime vs non-prime ? Post job accounting records for
>> chargeback ?
>> I've come to understand that many academic centers are blissfully
>> free from
>> having to do any type of chargeback (lucky people indeed) though some
>> aren't. Any one want to share their views and experiences ?
>>
>>
>>
>> Steve Pittard	 | http://www.bimcore.emory.edu
>> Emory University | wsp at emory.edu, wsp at bimcore.emory.edu
>> BIMCORE Support	 | Phone +1 404 727 0038 FAX +1 404 727 5512
>>
>> _______________________________________________
>> Bioclusters maillist  -  Bioclusters at bioinformatics.org
>> https://bioinformatics.org/mailman/listinfo/bioclusters
>>
>
>
>
> 		
> __________________________________
> Do you Yahoo!?
> Take Yahoo! Mail with you! Get it on your mobile phone.
> http://mobile.yahoo.com/maildemo
> _______________________________________________
> Bioclusters maillist  -  Bioclusters at bioinformatics.org
> https://bioinformatics.org/mailman/listinfo/bioclusters