Difference: CreamGlue2 (15 vs. 16)

Revision 162011-09-14 - MassimoSgaravatto

Line: 1 to 1
 
META TOPICPARENT name="CreamInformationService"

Glue2 support in CREAM

Line: 159 to 159
 
  • The value published in Glue1 as GlueCEInfoLRMSVersion should be published in Glue2 as ProductVersion (ComputingManager objectclass)
  • The value published in Glue1 as GlueCEPolicyMaxCPUTime should be published in Glue2 as MaxCPUTime (ComputingShare objectclass)
Added:
>
>
 
  • The value published in Glue1 as GlueCEPolicyMaxWallClockTime should be published in Glue2 as MaxWallTime (ComputingShare objectclass)
Changed:
<
<
  • The value published in Glue1 as GlueCEPolicyAssignedJobSlots should be published in Glue2 as ???
>
>		 * For all the ComputingShares referring to that batch system queue
  • The value published in Glue1 as GlueCEPolicyAssignedJobSlots should be published in Glue2 as ??? Nowhere ??
 
  • The value published in Glue1 as GlueCEStateStatus should be published in Glue2 as ServingState (ComputingShare objectclass)
Changed:
<
<
  • The value published in Glue1 as GlueCEInfoTotalCPUs should be published in Glue2 as ???
  • The value published in Glue1 as GlueCEInfoFreeCPUs should be published in Glue2 as ???
>
>		 * For all the ComputingShares referring to that batch system queue
  • The value published in Glue1 as GlueCEInfoTotalCPUs should be published in Glue2 as ??? Nowhere ??
  • The value published in Glue1 as GlueCEInfoFreeCPUs should be published in Glue2 as ??? Nowhere ??
 
Line: 171 to 174
 
  • The value published in Glue1 as GlueCEInfoLRMSVersion should be published in Glue2 as ProductVersion (ComputingManager objectclass)
  • The value published in Glue1 as GlueCEPolicyMaxCPUTime should be published in Glue2 as MaxCPUTime (ComputingShare objectclass)
Added:
>
>
 
  • The value published in Glue1 as GlueCEPolicyMaxWallClockTime should be published in Glue2 as MaxWallTime (ComputingShare objectclass)
Added:
>
>
 
  • The value published in Glue1 as GlueCEPolicyMaxRunningJobs should be published in Glue2 as MaxRunningJobs (ComputingShare objectclass)
Changed:
<
<
  • The value published in Glue1 as GlueCEStateFreeJobSlots should be published in Glue2 as FreeSlots (ComputingShare objectclass)
>
>
  • The value published in Glue1 as GlueCEStateFreeJobSlots should be published in Glue2 as ???
 
    • But the same value is published by the generic provider ...
  • The value published in Glue1 as GlueCEStateStatus should be published in Glue2 as ServingState (ComputingShare objectclass)
Changed:
<
<
  • The value published in Glue1 as GlueCEPolicyAssignedJobSlots should be published in Glue2 as ??
  • The value published in Glue1 as GlueCEInfoTotalCPUs should be published in Glue2 as ???
  • The value published in Glue1 as GlueCEInfoFreeCPUs should be published in Glue2 as ???
>
>
  • The value published in Glue1 as GlueCEPolicyAssignedJobSlots should be published in Glue2 as ?? Nowhere ??
  • The value published in Glue1 as GlueCEInfoTotalCPUs should be published in Glue2 as ??? Nowhere ??
  • The value published in Glue1 as GlueCEInfoFreeCPUs should be published in Glue2 as ??? Nowhere ??
 
    • But the same value is published by the generic provider ...
Changed:
<
<
  • The value published in Glue1 as GlueCEPolicyPriority should be published in Glue2 as ???
>
>
  • The value published in Glue1 as GlueCEPolicyPriority should be published in Glue2 as ??? Nowhere ??
 

0.0.1 Work to be done in the generic dynamic scheduler

Changed:
<
<
  • The value published in Glue1 as GlueCEStateFreeJobSlots for the GlueCE objectclass should be published in Glue2 as FreeSlots (ComputingShare objectclass)
>
>
  • The value published in Glue1 as GlueCEStateFreeJobSlots for the GlueCE objectclass should be published in Glue2 as ?? Nowhere ??
 
    • But the same value is published by the LSF provider ...
Changed:
<
<
  • The value published in Glue1 as GlueCEStateRunningJobs for the GlueCE objectclass should be published in Glue2 as RunningJobs (ComputingShare objectclass)
  • The value published in Glue1 as GlueCEStateWaitingJobs for the GlueCE objectclass should be published in Glue2 as WaitingJobs (ComputingShare objectclass)
  • The value published in Glue1 as GlueCEStateTotalJobs for the GlueCE objectclass should be published in Glue2 as TotalJobs (ComputingShare objectclass)
  • The value published in Glue1 as GlueCEStateEstimatedResponseTime for the GlueCE should be published in Glue2 as EstimatedAverageWaitingTime (ComputingShare objectclass)
  • The value published in Glue1 as GlueCEStateWorstResponseTime for the GlueCE should be published in Glue2 as EstimatedWorstWaitingTime (ComputingShare objectclass)
  • The value published in Glue1 as GlueCEInfoFreeCPUs for the GlueCE objectclass should be published in Glue2 as ???
>
>
  • The value published in Glue1 as GlueCEStateRunningJobs for the GlueCE objectclass should be published in Glue2 as ?? Nowhere ??
  • The value published in Glue1 as GlueCEStateWaitingJobs for the GlueCE objectclass should be published in Glue2 as ?? Nowhere ??
  • The value published in Glue1 as GlueCEStateTotalJobs for the GlueCE objectclass should be published in Glue2 as ?? Nowhere ??
  • The value published in Glue1 as GlueCEStateEstimatedResponseTime for the GlueCE should be published in Glue2 as ?? Nowhere ??
  • The value published in Glue1 as GlueCEStateWorstResponseTime for the GlueCE should be published in Glue2 as ?? Nowhere ??
  • The value published in Glue1 as GlueCEInfoFreeCPUs for the GlueCE objectclass should be published in Glue2 as ??? Nowhere ??
 
    • But the same value is published by the generic provider ...

Changed:
<
<
  • The value published in Glue1 as GlueCEStateRunningJobs for the VOView objectclass should be published in Glue2 as ??
  • The value published in Glue1 as GlueCEStateWaitingJobs for the VOView objectclass should be published in Glue2 as ??
  • The value published in Glue1 as GlueCEStateTotalJobs for the VOView objectclass should be published in Glue2 as ??
  • The value published in Glue1 as GlueCEStateFreeJobSlots for the VOView objectclass should be published in Glue2 as ??
  • The value published in Glue1 as GlueCEStateEstimatedResponseTime for the VOView should be published in Glue2 as ??
  • The value published in Glue1 as GlueCEStateWorstResponseTime for the VOView should be published in Glue2 as ??
>
>
  • The value published in Glue1 as GlueCEStateRunningJobs for the VOView objectclass should be published in Glue2 as RunningJobs (ComputingShare objectclass)
  • The value published in Glue1 as GlueCEStateWaitingJobs for the VOView objectclass should be published in Glue2 as WaitingJobs (ComputingShare objectclass)
  • The value published in Glue1 as GlueCEStateTotalJobs for the VOView objectclass should be published in Glue2 as TotalJobs (ComputingShare objectclass)
  • The value published in Glue1 as GlueCEStateFreeJobSlots for the VOView objectclass should be published in Glue2 as FreeSlots (ComputingShare objectclass)
  • The value published in Glue1 as GlueCEStateEstimatedResponseTime for the VOView should be published in Glue2 as EstimatedAverageWaitingTime (ComputingShare objectclass)
  • The value published in Glue1 as GlueCEStateWorstResponseTime for the VOView should be published in Glue2 as EstimatedWorstWaitingTime (ComputingShare objectclass)
 
View topic | History: r48 < r47 < r46 < r45 | More topic actions...
 
This site is powered by the TWiki collaboration platformCopyright © 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback