[gold-users] allocation deactivations
Scott Jackson
scott at clusterresources.com
Mon Jan 7 11:31:13 MST 2008
On Thu, 2008-01-03 at 16:42 -0500, Kevin Van Workum wrote:
> Scott,
>
> A question about how allocation deactivations work. After an
> allocation expires, Gold deactivates the allocation and creates a
> Transaction against that allocation with the Delta = -(Amount at time
> of expiration). I see this transaction when I do a glstxn -i ID.
> However, the amount in the allocation does not seem to be affected by
> this transaction. For example, below you can see the Deactivate at the
> end of the list of transactions, but the amount of allocation 241 is
> still -161150. It seems to me that it should be 0 rather than the
> amount at the time of expiration. Am I correct or just not
> understanding?
>
> Kevin
>
Allocations may exist which are not currently active. Only active
allocations contribute towards a user's balance. For example, one can
create quarterly allocations for a year with each allocation being
active only during its respective quarter. Let's say we are in quarter
2. The quarter 3 and 4 allocations exist with positive balances, but
they are not active and do not count as credits yet. The quarter 1
allocation has expired and is no longer active. When we enter quarter 3,
quarter 2 will expire and quarter 3 will become active. This will be
seen as a debit for the amount of credits that expired as well as a
credit for the number of credits that became active.
So for your case, you had an allocation 241 that actually became
negative (contributing negatively towards people's balances). When it
expired, this negative allocation no longer contributed negatively
toward their balance, thus the Allocation Deactivation was seen as a net
credit. The allocation continues to exist with the negative balance, but
is no longer impinging against their balance. If, in the future, you
chose to reactivate that allocation (change the expiration time for
example), that negative balance would again impact the users' balances
and a debit would be recorded for the appropriate account in an
Allocation Activation event.
Make sense?
Scott
> [root at jman tmp]# glstxn -i 241
> Id Object Action Name JobId Amount Delta Account
> Project User Allocation Count Description
> ------ ---------- ---------- ----- ------------ ------ ------ -------
> ------- ---- ---------- ----- -----------
> 184363 Account Deposit 49 0 0 49
> 241 1
> 184390 Job Charge 36659 49030.jman 150 -150 49
> vanw vanw 241 1 STDIN
> 184395 Job Charge 36660 test.jman 10000 -10000 49
> vanw vanw 241 1 test
> 184400 Job Charge 36661 test.jman 10000 -10000 49
> vanw vanw 241 1 test
> 184405 Job Charge 36662 n583100.jman 10000 -10000 49
> vanw vanw 241 1 n583100
> 184410 Job Charge 36663 n583101.jman 10000 -10000 49
> vanw vanw 241 1 n583101
> 184415 Job Charge 36664 n583102.jman 10000 -10000 49
> vanw vanw 241 1 n583102
> 184420 Job Charge 36665 n583103.jman 10000 -10000 49
> vanw vanw 241 1 n583103
> 184425 Job Charge 36666 n583104.jman 10000 -10000 49
> vanw vanw 241 1 n583104
> 184430 Job Charge 36667 n583105.jman 10000 -10000 49
> vanw vanw 241 1 n583105
> 184435 Job Charge 36668 n583106.jman 10000 -10000 49
> vanw vanw 241 1 n583106
> 184440 Job Charge 36669 n583107.jman 10000 -10000 49
> vanw vanw 241 1 n583107
> 184445 Job Charge 36670 n583108.jman 10000 -10000 49
> vanw vanw 241 1 n583108
> 184450 Job Charge 36671 n583109.jman 10000 -10000 49
> vanw vanw 241 1 n583109
> 184455 Job Charge 36672 n583110.jman 10000 -10000 49
> vanw vanw 241 1 n583110
> 184460 Job Charge 36673 n583111.jman 10000 -10000 49
> vanw vanw 241 1 n583111
> 184465 Job Charge 36674 n583112.jman 10000 -10000 49
> vanw vanw 241 1 n583112
> 184470 Job Charge 36675 n583113.jman 10000 -10000 49
> vanw vanw 241 1 n583113
> 184478 Job Charge 36676 49032.jman 1000 -1000 49
> vanw vanw 241 1 STDIN
> 184482 Allocation Deactivate 241 161150 49
> 241 1
>
> [root at jman tmp]# glsalloc -i 241
> Id Account Active StartTime EndTime Amount CreditLimit
> Deposited Description
> --- ------- ------ ---------- ------------------- ------- -----------
> --------- -----------
> 241 49 False 2008-01-01 2008-01-03 15:50:00 -161150 36000000
> 0
>
>
> --
> Kevin Van Workum, Ph.D.
> Tsunamic Technologies Inc.
> Vice President
> www.clusterondemand.com
> ONLINE COMPUTER CLUSTERS
> _______________________________________________
> gold-users mailing list
> gold-users at supercluster.org
> http://www.supercluster.org/mailman/listinfo/gold-users
More information about the gold-users
mailing list