 |
 |
It all sounds fine, I just worry about more manual reporting processes. You may wish to look at: http://ganglia.gridpp.rl.ac.uk/cgi-bin/ganglia-fs/fs-page.pl?m=%5Bnone%5D&r=day&s=descending Which is work done by Matt, to publish the MAUI shares through ganglia. I'm sure other sites would find this easy to install. We also have another one done by Matt: http://ganglia.gridpp.rl.ac.uk/cgi-bin/ganglia-cap/cap-page.pl?m=%5Bnone%5D&r=day&s=descending Which publishes our capacity. That one probably has to be propogated throughout the farm, but should otherwise be easy to deploy. Regards Andrew > -----Original Message----- > From: Testbed Support for GridPP member institutes > [mailto:[log in to unmask]]On Behalf Of Coles, J (Jeremy) > Sent: 31 May 2006 11:56 > To: [log in to unmask] > Subject: Re: faireshare tables to fill on the gridpp wiki > > > Hi Andrew > > Olivier addressed your second concern. On the first one I can comment. > We want to find out what sites are *currently* using as fairshares. It > is useful to know which sites have dynamic allocations (and > what forces > the changes). It is also useful to know which sites have no > real policy > implemented at the current time. This whole topic will become more > important once there is real contention for resources; we are > trying to > understand how we can/will meet WLCG commitments before a > problem arises > in this area. > > Going forward this is an area best tracked and managed by the Tier-2s > themselves (the Tier-1 already has an allocation (and implementation > management) process). The Tier-1 is caught up in the request since it > was a blanket request, however I think there is a clear understanding > already of how the Tier-1 works. > > It is not yet clear whether the table will need to be kept up-to-date > but it is likely to be useful for overall management if it can be. We > may (have to) record the allocations in the quarterly reports anyway. > > Jeremy > > > -----Original Message----- > > From: Testbed Support for GridPP member institutes [mailto:TB- > > [log in to unmask]] On Behalf Of Sansum, RA (Andrew) > > Sent: 31 May 2006 11:20 > > To: [log in to unmask] > > Subject: Re: faireshare tables to fill on the gridpp wiki > > > > I have a couple of concerns: > > > > 1) Is it intended that this table is kept up to date - if so how? > > Certainly we change > > our fairshares on occassion - typically every 3 months, but on > ocassion > > in response > > to requests for urgent priority changes. > > > > 2) Why are we worrying about job slots, when we have to > deliver KSI2K > to > > the project, and the > > fairshare algorith is scheduling on elapsed time (as far as I > > understand). > > > > Regards > > Andrew > > > > > -----Original Message----- > > > From: Testbed Support for GridPP member institutes > > > [mailto:[log in to unmask]]On Behalf Of William Hay > > > Sent: 31 May 2006 11:00 > > > To: [log in to unmask] > > > Subject: Re: faireshare tables to fill on the gridpp wiki > > > > > > > > > > Dear All, > > > > > > > > In order to keep track of the faireshare implementation > in the uk > > > > I have created a set of tables to hold that information. > > > > http://www.gridpp.ac.uk/wiki/Current_VO_Fairshares_at_T2/T1 > > > > > > > > Could each site fill in the fairshare percentages that they have > > > > implemented. I have also added a field with the total number of > job > > > > > > The numbers at UCL-CENTRAL change. We run local jobs on the > cluster. > > > The body at UCL that is in charge of making allocations has > > > yet to make > > > a final decision as to the fairshare for LCG vs local projects. > > > At the moment every local project and every LCG VO gets an > > > equal share. > > > This means that as the number of local projects goes up > LCG's share > > > goes down. When a decision is made we will allocate a share > > > to be divided > > > among LCG projects and a share to be divided among local > > > projects which > > > should mean we can tell you the %ages for LCG without having > > > to constantly > > > adjust them. > > > > > > Ben is looking into exactly what was decided when we > joined on this > > > when we joined the LCG project and why. > > > > > > William > > > >