Difference: CreamGlue2 (14 vs. 15)

Revision 152011-09-14 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 157 to 157
 

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

Added:
>
>
  • 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 GlueCEPolicyMaxWallClockTime should be published in Glue2 as MaxWallTime (ComputingShare objectclass)
  • The value published in Glue1 as GlueCEPolicyAssignedJobSlots should be published in Glue2 as ???
  • The value published in Glue1 as GlueCEStateStatus should be published in Glue2 as ServingState (ComputingShare objectclass)
  • 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 ???

 

0.0.1 Work to be done in the LSF information provider

Added:
>
>
  • 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 GlueCEPolicyMaxWallClockTime should be published in Glue2 as MaxWallTime (ComputingShare objectclass)
  • The value published in Glue1 as GlueCEPolicyMaxRunningJobs should be published in Glue2 as MaxRunningJobs (ComputingShare objectclass)
  • The value published in Glue1 as GlueCEStateFreeJobSlots should be published in Glue2 as FreeSlots (ComputingShare objectclass)
    • 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)
  • 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 ???
    • But the same value is published by the generic provider ...
  • The value published in Glue1 as GlueCEPolicyPriority should be published in Glue2 as ???
 

0.0.1 Work to be done in the generic dynamic scheduler

Changed:
<
<		GlueCEInfoLRMSVersion (pbs-CE, lsf-CE) GlueCEInfoTotalCPUs (pbs-CE, lsf-CE) GlueCEPolicyAssignedJobSlots (pbs-CE, lsf-CE) GlueCEPolicyMaxCPUTime (pbs-CE) GlueCEPolicyMaxRunningJobs (lsf-CE) GlueCEPolicyMaxCPUTime (lsf-CE) GlueCEPolicyMaxWallClockTime (pbs-CE, lsf-CE) GlueCEPolicyPriority (lsf-CE) GlueCEStateEstimatedResponseTime (genericpbs-VoView, genericpbs-CE, genericlsf-Voview, genericlsf-ce) GlueCEStateFreeCPUs (pbs-CE, lsf-CE, genericpbs-VoView, genericpbs-CE, genericlsf-ce) GlueCEStateFreeJobSlots (lsf-CE, genericpbs-VoView, genericpbs-CE, genericlsf-voview, genericlsf-ce) GlueCEStateTotalJobs (genericpbs-VoView, genericpbs-CE, genericlsf, voview, genericlsf-CE) GlueCEStateRunningJobs (genericpbs-VoView, genericpbs-CE, genericlsf-voview, genericlsf-ce) GlueCEStateStatus (pbs-CE, lsf-CE) GlueCEStateWaitingJobs (genericpbs-VoView, genericpbs-CE, genericlsf-VOview, genericlsf-ce) GlueCEStateWorstResponseTime (genericpbs-VoView, genericpbs-CE, genericlsf-voview, genericlsf-ce)
>
>
  • The value published in Glue1 as GlueCEStateFreeJobSlots for the GlueCE objectclass should be published in Glue2 as FreeSlots (ComputingShare objectclass)
    • But the same value is published by the LSF provider ...
  • 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 ???
    • But the same value is published by the generic provider ...

  • 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 ??
 

1 Relevant RFCs

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