Difference: CreamGlue2 (18 vs. 19)

Revision 192011-09-19 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 216 to 216
 

0.0.1 Work to be done in the PBS/Torque information provider

Changed:
<
<
  • 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)
>
>
  • The value published in Glue1 as GlueCEInfoLRMSVersion should be published in Glue2 as GLUE2ManagerProductVersion (ComputingManager objectclass)
  • The value published in Glue1 as GlueCEPolicyMaxCPUTime should be published in Glue2 as GLUE2ComputingShareMaxCPUTime (ComputingShare objectclass)
 
    • For all the ComputingShares referring to that batch system queue
Changed:
<
<
  • The value published in Glue1 as GlueCEPolicyMaxWallClockTime should be published in Glue2 as MaxWallTime (ComputingShare objectclass)
>
>
  • The value published in Glue1 as GlueCEPolicyMaxWallClockTime should be published in Glue2 as GLUE2ComputingShareMaxWallTime (ComputingShare objectclass)
  * For all the ComputingShares referring to that batch system queue
Changed:
<
<
  • The value published in Glue1 as GlueCEStateStatus should be published in Glue2 as ServingState (ComputingShare objectclass)
>
>
  • The value published in Glue1 as GlueCEStateStatus should be published in Glue2 as GLUE2ComputingShareServingState (ComputingShare objectclass)
 
    • For all the ComputingShares referring to that batch system queue

Line: 229 to 229
 

0.0.1 Work to be done in the LSF information provider

Changed:
<
<
  • 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)
>
>
  • The value published in Glue1 as GlueCEInfoLRMSVersion should be published in Glue2 as GLUE2ManagerProductVersion (ComputingManager objectclass)
  • The value published in Glue1 as GlueCEPolicyMaxCPUTime should be published in Glue2 as GLUE2ComputingShareMaxCPUTime (ComputingShare objectclass)
 
    • For all the ComputingShares referring to that batch system queue
Changed:
<
<
  • The value published in Glue1 as GlueCEPolicyMaxWallClockTime should be published in Glue2 as MaxWallTime (ComputingShare objectclass)
>
>
  • The value published in Glue1 as GlueCEPolicyMaxWallClockTime should be published in Glue2 as GLUE2ComputingShareMaxWallTime (ComputingShare objectclass)
 
    • For all the ComputingShares referring to that batch system queue
Changed:
<
<
  • The value published in Glue1 as GlueCEPolicyMaxRunningJobs should be published in Glue2 as MaxRunningJobs (ComputingShare objectclass)
>
>
  • The value published in Glue1 as GlueCEPolicyMaxRunningJobs should be published in Glue2 as GLUE2ComputingShareMaxRunningJobs (ComputingShare objectclass)
 
    • For all the ComputingShares referring to that batch system queue
Changed:
<
<
  • The value published in Glue1 as GlueCEStateStatus should be published in Glue2 as ServingState (ComputingShare objectclass)
>
>
  • The value published in Glue1 as GlueCEStateStatus should be published in Glue2 as GLUE2ComputingShareServingState (ComputingShare objectclass)
 
    • For all the ComputingShares referring to that batch system queue

0.0.1 Work to be done in the generic dynamic scheduler

Changed:
<
<
  • 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)
>
>
  • The value published in Glue1 as GlueCEStateRunningJobs for the VOView objectclass should be published in Glue2 as GLUE2ComputingShareRunningJobs (ComputingShare objectclass)
  • The value published in Glue1 as GlueCEStateWaitingJobs for the VOView objectclass should be published in Glue2 as GLUE2ComputingShareWaitingJobs (ComputingShare objectclass)
  • The value published in Glue1 as GlueCEStateTotalJobs for the VOView objectclass should be published in Glue2 as GLUE2ComputingShareTotalJobs (ComputingShare objectclass)
  • The value published in Glue1 as GlueCEStateFreeJobSlots for the VOView objectclass should be published in Glue2 as GLUE2ComputingShareFreeSlots (ComputingShare objectclass)
  • The value published in Glue1 as GlueCEStateEstimatedResponseTime for the VOView should be published in Glue2 as GLUE2ComputingShareEstimatedAverageWaitingTime (ComputingShare objectclass)
  • The value published in Glue1 as GlueCEStateWorstResponseTime for the VOView should be published in Glue2 as GLUE2ComputingShareEstimatedWorstWaitingTime (ComputingShare objectclass)
 

0.0.1 Work to be done in the SGE information provider

 
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