X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C85917.23416071@onstor-exch02.onstor.net>; Thu, 17 Jan 2008 07:42:09 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: Resource Scheduler Gateways
Date: Thu, 17 Jan 2008 07:42:07 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E07AE2744@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E07AE2601@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Resource Scheduler Gateways
Thread-Index: AchYm/Gco6tBOX63TLSIaCAITt8TogACtHIwAABlSyAAAEV7YAAbam6g
References: <BB375AF679D4A34E9CA8DFA650E2B04E07AE25D4@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E07AE25E2@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E07AE2601@onstor-exch02.onstor.net>
From: "Brian Bliem" <IMCEAEX-_O=ONSTOR_OU=FIRST+20ADMINISTRATIVE+20GROUP_CN=RECIPIENTS_CN=BRIAN+2EBLIEM@onstor.com>
To: "Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>,
	"Tim Gardner" <tim.gardner@onstor.com>,
	"Andy Sharp" <andy.sharp@onstor.com>
Cc: "John Rogers" <john.rogers@onstor.com>,
	"Amit Bothra" <amit.bothra@onstor.com>,
	"John VanderWerf" <john.vanderwerf@onstor.com>,
	"dl-Engineering" <dl-engineering@onstor.com>

The gun should go in the resource scheduler.

-----Original Message-----
From: Maxim Kozlovsky=20
Sent: Wednesday, January 16, 2008 5:46 PM
To: Tim Gardner; Andy Sharp
Cc: John Rogers; Amit Bothra; John VanderWerf; dl-Engineering
Subject: RE: Resource Scheduler Gateways


There are several basic ways of solving the problem:

1) Fair scheduling - the guns are rotated between the employers
2) American democratic - we elect a committee which assigns the guns,
the committee is reelected every so often
3) Russian democratic - we elect a committee which assigns the guns, the
committee elects the next committee every so often
4) First in first out scheduling - who comes to work first gets the gun
5) Last in first out scheduling - who comes to work first makes the
filer reservation, who comes last gets the gun
6) Posix scheduling - the way the guns are assigned is completely
unspecified and depends on the implementation, each pair decides it
through a cage match as Larry suggested.



>-----Original Message-----
>From: Tim Gardner
>Sent: Wednesday, January 16, 2008 5:31 PM
>To: Maxim Kozlovsky; Andy Sharp
>Cc: John Rogers; Amit Bothra; John VanderWerf; dl-Engineering
>Subject: RE: Resource Scheduler Gateways
>
>This is the same concept behind Extreme Programming.
>"You are not working hard enough!" BAM
>But how do we decide which of the pair gets the gun?
>
>
>> -----Original Message-----
>> From: Maxim Kozlovsky
>> Sent: Wednesday, January 16, 2008 5:24 PM
>> To: Andy Sharp
>> Cc: John Rogers; Amit Bothra; John VanderWerf; dl-Engineering
>> Subject: RE: Resource Scheduler Gateways
>>
>> Don't forget about those who are not using the filers they have
reserved,
>> which is even worse offence. The engineering will be split in teams
of
>> two, one working on a filer, the other one watching him over. The one
>> watching over will be provided with a hand gun which he is obliged to
use
>> if a violation of the reservation is detected. (I heard this is
called
>> pair programming in some circles.)
>>
>> >-----Original Message-----
>> >From: Andy Sharp
>> >Sent: Wednesday, January 16, 2008 4:00 PM
>> >To: Maxim Kozlovsky
>> >Cc: John Rogers; Amit Bothra; John VanderWerf; dl-Engineering
>> >Subject: Re: Resource Scheduler Gateways
>> >
>> >Wall mounted machine guns will be installed to deal with anyone
using
>> >an unreserved filer.  Aim will be tested by making Amit the first
>> >target.  Anyone sitting near him may be affected by "collateral
damage"
>> >until the aim is perfected.
>> >
>> ></duck>
>> >
>> >On Wed, 16 Jan 2008 15:54:54 -0800 "Maxim Kozlovsky"
>> ><maxim.kozlovsky@onstor.com> wrote:
>> >
>> >> Absolutely agree. Being able to reserve a filer for 6 months is
>> >> outrageous. Everybody should start their working day with renewing
>> >> their reservation, which will expire at 9:00am sharp. This way we
>> >> will be able to detect the filers being unused with unmatched
>> >> precision and not a moment of precious hardware time will be lost.
>> >>
>> >>
>> >>
>> >> ________________________________
>> >>
>> >> From: John Rogers
>> >> Sent: Wednesday, January 16, 2008 3:51 PM
>> >> To: Amit Bothra; John VanderWerf; dl-Engineering
>> >> Subject: RE: Resource Scheduler Gateways
>> >>
>> >>
>> >>
>> >> Well, we'll have to put an end to that.
>> >>
>> >>
>> >>
>> >> ________________________________
>> >>
>> >> From: Amit Bothra
>> >> Sent: Wednesday, January 16, 2008 3:02 PM
>> >> To: John VanderWerf; John Rogers; dl-Engineering
>> >> Subject: RE: Resource Scheduler Gateways
>> >>
>> >>
>> >>
>> >> I reserved my filer for 12 months and the resource scheduler did
not
>> >> complain.
>> >>
>> >>
>> >>
>> >> Thanks,
>> >>
>> >> Amit
>> >>
>> >>
>> >>
>> >> ________________________________
>> >>
>> >> From: John VanderWerf
>> >> Sent: Wednesday, January 16, 2008 2:56 PM
>> >> To: John Rogers; dl-Engineering
>> >> Subject: RE: Resource Scheduler Gateways
>> >>
>> >>
>> >>
>> >> Correction:  Reservations currently have a maximum of 6 months.
>> >>
>> >>
>> >>
>> >> --John
>> >>
>> >>
>> >>
>> >> ________________________________
>> >>
>> >> From: John Rogers
>> >> Sent: Wednesday, January 16, 2008 2:52 PM
>> >> To: dl-Engineering
>> >> Subject: Resource Scheduler Gateways
>> >>
>> >>
>> >>
>> >> Please make sure the gateway you are using is reserved in Resource
>> >> Scheduler. We will be adding cougars into the Resource Scheduler
soon
>> >> and will send out announcements to individual users of those
>> >> resources. Stay tuned for further announcements regarding new
>> >> resources added to resource scheduler as well.
>> >>
>> >>
>> >>
>> >> It is important to note that reservations have a maximum of 3
months.
>> >> It's a good idea to check your reservation frequently to make sure
it
>> >> is up to date.
>> >>
>> >>
>> >>
>> >> Thank you.
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> John Rogers
>> >> Engineering Lab Manager
>> >>
>> >> ONStor, Inc.
>> >> office: 408.963.2480
>> >> mobile: 408.981.5313
>> >>
>> >> john.rogers@onstor.com <mailto:john.rogers@onstor.com>
>> >> http://www.onstor.com <http://www.onstor.com>
>> >>
>> >>
>> >>
>> >>
>> >>
