Difference: CreamGlue2 (1 vs. 48)

Revision 472012-03-23 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 20 to 20
 

0.1 CREAM CE in no cluster mode

Changed:
<
<
We assume that a CREAM CE is configured in cluster mode if that is the only CREAM CE available in the site. I.e. sites with multiple CREAM CEs (submitting to the same batch system) should always have a cluster node and therefore be configured in cluster mode.
>
>
We assume that a CREAM CE is configured in cluster mode if that is not the only CREAM CE available in the site. Sites with multiple CREAM CEs (submitting to the same batch system) should always have a cluster node and therefore be configured in cluster mode.
  If a CREAM CE is configured in no cluster mode, all the Glue2 object classes are published by the resource BDII running on the CREAM CE.

Revision 462012-02-01 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 451 to 451
 
  • 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
Changed:
<
<

0.0.1 Work to be done in the SGE information provider

>
>

0.0.1 Work to be done in the SGE information provider (done)

 
  • 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 GLUE2ComputingShareDefaultCPUTime ( ComputingShare objectclass)
Line: 463 to 463
 
  • 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
Changed:
<
<

0.0.1 Work to be done in the generic dynamic scheduler

>
>

0.0.1 Work to be done in the generic dynamic scheduler (done)

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

Revision 452011-12-17 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 430 to 430
 

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

  • The value published in Glue1 as GlueCEInfoLRMSVersion should be published in Glue2 as GLUE2ManagerProductVersion ( ComputingManager objectclass)
Changed:
<
<
  • The value published in Glue1 as GlueCEPolicyMaxCPUTime should be published in Glue2 as GLUE2ComputingShareMaxCPUTime ( ComputingShare objectclass)
>
>
  • The value published in Glue1 as GlueCEPolicyMaxCPUTime should be published in Glue2 as GLUE2ComputingShareDefaultCPUTime ( 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 GLUE2ComputingShareMaxWallTime ( ComputingShare objectclass) * For all the ComputingShares referring to that batch system queue
>
>
  • The value published in Glue1 as GlueCEPolicyMaxObtainableCPUTime should be published in Glue2 as GLUE2ComputingShareMaxCPUTime ( ComputingShare objectclass)
    • For all the ComputingShares referring to that batch system queue
  • The value published in Glue1 as GlueCEPolicyMaxWallClockTime should be published in Glue2 as GLUE2ComputingShareDefaultWallTime ( ComputingShare objectclass) * For all the ComputingShares referring to that batch system queue
  • The value published in Glue1 as GlueCEPolicyMaxObtainableWallClockTime should be published in Glue2 as GLUE2ComputingShareMaxWallTime ( ComputingShare objectclass) * For all the ComputingShares referring to that batch system queue
 
  • 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 LSF information provider (done)

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

0.0.1 Work to be done in the SGE information provider

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

Revision 442011-12-11 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 68 to 68
 
    • EndPoint for RTEPublihser (done)
      • "Child" of ComputingService
Added:
>
>
Actually it is necessary to publish also the ComputingService, since otherwise the resource bdii of the CREAM CE will not be able to publish the ComputingEndpoint
 
  • The ServiceId is the the one specified by the yaim variable COMPUTING_SERVICE_ID which is such scenario is mandatory. This variable must have the same value in all the relevant nodes (in the cluster node and in all the CREAM CEs)

Revision 432011-12-11 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 425 to 425
 

0.1 Work to be done to support Glue2 publication

Changed:
<
<

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

>
>

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

 
  • 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)
Line: 434 to 434
 
  • 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
Changed:
<
<

0.0.1 Work to be done in the LSF information provider

>
>

0.0.1 Work to be done in the LSF information provider (done)

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

Revision 422011-12-06 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 93 to 93
 

0.0.1 ComputingEndpoint

  • GLUE2EndpointID is <hostname> + "_org.glite.ce.CREAM"
Changed:
<
<
  • GLUE2EntityCreationTime is the timestamp when the ldif file was created
>
>
  • GLUE2EntityCreationTime is the timestamp when the ldif file was created. This value is then overwritten by the dynamic plugin
  • Glue2EndpointStartTime is the timestamp when the ldif file was created. This value is then overwritten by the dynamic plugin
 
  • GLUE2EntityName is the EndPointId
  • GLUE2EntityOtherInfo includes the host DN, the EMI middleware version, information if the CREAM CE is using Argus, and information concerning the info provider
  • GLUE2EndpointURL is the endpoint URL of the CREAM CE, that is: "https://" + <host> + "8443/ce-cream/services"
Line: 118 to 119
 
  • GLUE2ComputingEndpointJobDescription is glite:jdl
  • GLUE2EndpointServiceForeignKey is the value ComputingServiceId in /etc/glite-ce-glue2/glite-ce-glue2.conf. This value is the one specified by the yaim variable COMPUTING_SERVICE_ID, if specified (this variable is mandatory in cluster mode). Otherwise it is =${CE_HOST}_ComputingElement
  • GLUE2ComputingEndpointComputingServiceForeignKey is the same as GLUE2EndpointServiceForeignKey
Changed:
<
<
Todo: start time ?
>
>
 

0.0.0.1 Policy for the ComputingEndPoint

Revision 412011-12-06 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 110 to 110
 
  • GLUE2EndpointQualityLevel=s is =production
  • GLUE2EndpointHealthState is unknown in the ldif static file; it is overwritten by the glite-ce-glue2-endpoint-dynamic plugin (which check the glite-info-service-test output and the status of the tomcat service)
  • GLUE2EndpointHealthStateInfo is N/A in the ldif static file; it is overwritten by the glite-ce-glue2-endpoint-dynamic plugin (which check the glite-info-service-test output)
Changed:
<
<
  • GLUE2EndpointServingState
    • Now is a static value, read from /etc/glite-ce-glue2/glite-ce-glue2.conf (attribute ServingState). This value is the one specified by the yaim variable CREAM_CE_STATE
    • Target scenario: is a value provided by a dynamic plugin; it is checked if submissions are disabled (by the limiter, or explicitly by the admin). If so, it is published draining (see also http://savannah.cern.ch/bugs/?69854). Otherwise the value is read from /etc/glite-ce-glue2/glite-ce-glue2.conf (attribute ServingState), which is initially filled by yaim considering the yaim variable CREAM_CE_STATE. The admin can edit this file if he wants to publish a specific value without reconfiguring.
>
>
  • GLUE2EndpointServingState is a value provided by a dynamic plugin; it is checked if submissions are disabled (by the limiter, or explicitly by the admin). If so, it is published draining (see also http://savannah.cern.ch/bugs/?69854). Otherwise a static value is used. It is read from /etc/glite-ce-glue2/glite-ce-glue2.conf (attribute ServingState), which is initially filled by yaim considering the yaim variable CREAM_CE_STATE. The admin can edit this file if he wants to publish a specific value without reconfiguring.
 
  • GLUE2EndpointIssuerCA is found with a "openssl x509 -issuer -noout -in" on the host certificate
  • GLUE2EndpointTrustedCA is IGTF
  • GLUE2EndpointDownTimeInfo is "See the GOC DB for downtimes: https://goc.egi.eu"
Line: 487 to 485
 

1 Raw notes (for Massimo use)

Deleted:
<
<
Create a command which checks if submission is disabled
 
Added:
>
>
Dynamic batch system info:
 
Changed:
<
<
select submissionEnabled from db_info;

(0=disabilitate; 1=abilitate)

Use this command in the glue1 dynamic plugin. Replace production with Draining (to be checked) if submissions are disabled

Use this command also for the servingstate of endpoint (see above target scenario)

>
>
* For a CE in no cluster mode: both glue1 and glue2 * For a CE in cluster mode with cluster not deployed in that cream ce host: yes glue1 but not glue2 * For a CE in cluster mode with cluster deployed in that cream ce host: yes glue1 but not glue2 (glue2 is printed by cluster) * For a cluster (doesn't matter if on the same node there is also a cream ce): yes glue2 but no glue1
 -- MassimoSgaravatto - 2011-06-21 \ No newline at end of file

Revision 402011-11-28 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 485 to 485
 
  • cream-29.pd.infn.it (LSF)
  • cream-18.pd.infn.it (gLite-cluster node)
Added:
>
>

1 Raw notes (for Massimo use)

Create a command which checks if submission is disabled

select submissionEnabled from db_info;

(0=disabilitate; 1=abilitate)

Use this command in the glue1 dynamic plugin. Replace production with Draining (to be checked) if submissions are disabled

Use this command also for the servingstate of endpoint (see above target scenario)

 -- MassimoSgaravatto - 2011-06-21 \ No newline at end of file

Revision 392011-11-18 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 36 to 36
 
  • ExecutionEnvironment (done)
  • Benchmark (done)
  • ToStorageService (done)
Changed:
<
<
  • ApplicationEnvironment (todo)
>
>
  • ApplicationEnvironment (done)
 
  • EndPoint for RTEPublihser (done)
    • "Child" of ComputingService
  • EndPoint for CEMon (done)
Line: 64 to 64
 
    • ExecutionEnvironment (done)
    • Benchmark (done)
    • ToStorageService (done)
Changed:
<
<
    • ApplicationEnvironment (todo)
>
>
    • ApplicationEnvironment (done)
 
    • EndPoint for RTEPublihser (done)
      • "Child" of ComputingService
Line: 291 to 291
 

0.0.1 ApplicationEnvironment

Changed:
<
<
TBD
>
>
For each ExecutionEnvironment, a single objectclass is created for each software tag of that ExecutionEnvironment. These software tags are the ones defined during configuration (yaim variables CE_RUNTIMEENV (for no cluster mode) and SUBCLUSTER_xxx_HOST_ApplicationSoftwareRunTimeEnvironment for gLite cluster) plus the ones published by VO admins in /opt/edg/var/info and /opt/glite/var/info.

These are published using a gip provider.

  • GLUE2ApplicationEnvironmentId is concatenation of the name of the software tag and the ExecutionEnvironment ID
  • GLUE2EntityCreationTime is the timestamp when the provider script is run
  • GLUE2EntityValidity is 3600
  • GLUE2EntityOtherInfo includes information concerning the info provider
  • GLUE2ApplicationEnvironmentAppName is the name of the software tag
  • GLUE2ApplicationEnvironmentComputingManagerForeignKey is the name of the ComputingManager
 

0.0.1 ApplicationHandle

Revision 382011-11-16 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 59 to 59
 
  • All the other objectclasses are published by the resource BDII running on the gLite-CLUSTER node:
    • ComputingService (done)
    • ComputingManager (done)
Changed:
<
<
    • ComputingShare (todo)
      • MappingPolicy for ComputingShare (todo)
    • MappingPolicy (todo)
>
>
    • ComputingShare (done)
      • MappingPolicy for ComputingShare (done)
 
    • ExecutionEnvironment (done)
    • Benchmark (done)
    • ToStorageService (done)
Line: 145 to 144
 
  • GLUE2EntityCreationTime is the timestamp when the ldif file was created
  • GLUE2EntityOtherInfo includes the CEId(s) (read from the /etc/glite-ce-glue2/glite-ce-glue2.conf= conf file) and information concerning the info provider
  • GLUE2ShareDescription is "Share of <queuename> for <VO>"
Changed:
<
<
  • GLUE2ComputingShareMappingQueue is the batch system queue name
>
>
  • GLUE2ComputingShareMappingQueue is the batch system queue name. It is read from the /etc/glite-ce-glue2/glite-ce-glue2.conf= conf file)
 
  • GLUE2ComputingShareMaxWallTime is 999999999 in the ldif static file; it is supposed to be overwritten by the batch system specific dynamic plugin
  • GLUE2ComputingShareMaxCPUTime is 999999999 in the ldif static file; it is supposed to be overwritten by the batch system specific dynamic plugin
  • GLUE2ComputingShareMaxRunningJobs is 999999999 in the ldif static file; it is supposed to be overwritten by the batch system specific dynamic plugin
Line: 162 to 161
 
  • GLUE2ComputingShareExecutionEnvironmentForeignKey the same as GLUE2ShareResourceForeignKey
  • GLUE2ShareEndpointForeignKey is the link to the EndPoints. The value is read from the /etc/glite-ce-glue2/glite-ce-glue2.conf.
    • For a CREAM CE in no cluster mode this is the hostname + _org.glite.ce.CREAM
Added:
>
>
    • For a gLite cluster this is the list of hostname + _org.glite.ce.CREAM considering which cluster is associated to that queue, and which CEs are defined for that cluster
 
  • GLUE2ComputingShareComputingEndpointForeignKey is the same as GLUE2ComputingShareComputingEndpointForeignKey
  • GLUE2ShareServiceForeignKey is the value ComputingServiceId in /etc/glite-ce-glue2/glite-ce-glue2.conf. This value is the one specified by the yaim variable COMPUTING_SERVICE_ID, if specified (this variable is mandatory in cluster mode). Otherwise it is =${CE_HOST}_ComputingElement
  • GLUE2ComputingShareComputingServiceForeignKey is the same as GLUE2ShareServiceForeignKey

Revision 372011-11-15 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 143 to 143
 
  • GLUE2ShareID is concatenation of queue name + owner + ServiceId
  • GLUE2EntityCreationTime is the timestamp when the ldif file was created
Changed:
<
<
  • GLUE2EntityOtherInfo includes the CEId and information concerning the info provider
>
>
  • GLUE2EntityOtherInfo includes the CEId(s) (read from the /etc/glite-ce-glue2/glite-ce-glue2.conf= conf file) and information concerning the info provider
 
  • GLUE2ShareDescription is "Share of <queuename> for <VO>"
  • GLUE2ComputingShareMappingQueue is the batch system queue name
  • GLUE2ComputingShareMaxWallTime is 999999999 in the ldif static file; it is supposed to be overwritten by the batch system specific dynamic plugin
Line: 160 to 160
 
    • for a CREAM CE in no-cluster mode this is the link to the the first (and unique) element of the attribute ExecutionEnvironments in /etc/glite-ce-glue2/glite-ce-glue2.conf (which is the hostname of the CREAM-CE)
    • for a gLite cluster: this is the link to the first ExecutionEnvironment (i.e. first element of ExecutionEnvironments in /etc/glite-ce-glue2/glite-ce-glue2.conf)
  • GLUE2ComputingShareExecutionEnvironmentForeignKey the same as GLUE2ShareResourceForeignKey
Added:
>
>
  • GLUE2ShareEndpointForeignKey is the link to the EndPoints. The value is read from the /etc/glite-ce-glue2/glite-ce-glue2.conf.
    • For a CREAM CE in no cluster mode this is the hostname + _org.glite.ce.CREAM
  • GLUE2ComputingShareComputingEndpointForeignKey is the same as GLUE2ComputingShareComputingEndpointForeignKey
 
  • GLUE2ShareServiceForeignKey is the value ComputingServiceId in /etc/glite-ce-glue2/glite-ce-glue2.conf. This value is the one specified by the yaim variable COMPUTING_SERVICE_ID, if specified (this variable is mandatory in cluster mode). Otherwise it is =${CE_HOST}_ComputingElement
  • GLUE2ComputingShareComputingServiceForeignKey is the same as GLUE2ShareServiceForeignKey
Changed:
<
<
TODO: link to computingendpoint
>
>
 

0.0.0.1 MappingPolicy for the ComputingShare

  • GLUE2PolicyID is ComputingShareId plus "_policy
  • GLUE2EntityCreationTime is the timestamp when the ldif file was created
  • GLUE2PolicyScheme is org.glite.standard
Changed:
<
<
  • GLUE2PolicyRule is the list of ACBRs for this share (read from /etc/glite-ce-glue2/glite-ce-glue2.conf=)
>
>
  • GLUE2PolicyRule is the list of ACBRs for this share (read from /etc/glite-ce-glue2/glite-ce-glue2.conf)
 
  • GLUE2PolicyUserDomainForeignKey is the owner (read from /etc/glite-ce-glue2/glite-ce-glue2.conf)
  • GLUE2MappingPolicyShareForeignKey is the ComputingShareId

Revision 362011-11-15 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 157 to 157
 
  • GLUE2ComputingShareEstimatedWorstWaitingTime is 2146660842 in the ldif static file; it is supposed to be overwritten by the generic dynamic scheduler plugin
  • GLUE2ComputingShareFreeSlots is 0 in the ldif static file; it is supposed to be overwritten by the generic dynamic scheduler plugin
  • GLUE2ShareResourceForeignKey
Changed:
<
<
    • for a CREAM CE in cluster mode this is the link to the first ExecutionEnvironment (i.e. first element of ExecutionEnvironments in /etc/glite-ce-glue2/glite-ce-glue2.conf)
>
>
    • for a CREAM CE in no-cluster mode this is the link to the the first (and unique) element of the attribute ExecutionEnvironments in /etc/glite-ce-glue2/glite-ce-glue2.conf (which is the hostname of the CREAM-CE)
 
    • for a gLite cluster: this is the link to the first ExecutionEnvironment (i.e. first element of ExecutionEnvironments in /etc/glite-ce-glue2/glite-ce-glue2.conf)
  • GLUE2ComputingShareExecutionEnvironmentForeignKey the same as GLUE2ShareResourceForeignKey
  • GLUE2ShareServiceForeignKey is the value ComputingServiceId in /etc/glite-ce-glue2/glite-ce-glue2.conf. This value is the one specified by the yaim variable COMPUTING_SERVICE_ID, if specified (this variable is mandatory in cluster mode). Otherwise it is =${CE_HOST}_ComputingElement
Line: 170 to 170
 
  • GLUE2PolicyID is ComputingShareId plus "_policy
  • GLUE2EntityCreationTime is the timestamp when the ldif file was created
  • GLUE2PolicyScheme is org.glite.standard
Changed:
<
<
  • GLUE2PolicyRule is = the ACBR (read from /etc/glite-ce-glue2/glite-ce-glue2.conf=)
  • GLUE2PolicyUserDomainForeignKey is the owner (read from /etc/glite-ce-glue2/glite-ce-glue2.conf=)
>
>
  • GLUE2PolicyRule is the list of ACBRs for this share (read from /etc/glite-ce-glue2/glite-ce-glue2.conf=)
  • GLUE2PolicyUserDomainForeignKey is the owner (read from /etc/glite-ce-glue2/glite-ce-glue2.conf)
 
  • GLUE2MappingPolicyShareForeignKey is the ComputingShareId

0.0.1 ComputingManager

Revision 352011-10-13 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 165 to 165
  TODO: link to computingendpoint
Changed:
<
<

0.0.0.1 MappingPolicy for the ComputingEndPoint

>
>

0.0.0.1 MappingPolicy for the ComputingShare

 
  • GLUE2PolicyID is ComputingShareId plus "_policy
  • GLUE2EntityCreationTime is the timestamp when the ldif file was created

Revision 342011-10-11 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 247 to 247
 
    • For a CREAM CE in no-cluster mode this is the value of the yaim variable CE_LOGCPU
    • For a gLite-cluster mode this is the value of the yaim variable SUBCLUSTER_xxx_SUBCLUSTER_LogicalCPUs
  • GLUE2ExecutionEnvironmentCPUMultiplicity is: + "cpu" + "-" . + "core"
Changed:
<
<
>
>
    • is "single" if (SmpSize == (LogicalCPUs / PhysicalCPUs)). It is "multi" otherwise
    • is "single" if (PhysicalCPUs == LogicalCPUs). It is "multi" otherwise
 
  • GLUE2ExecutionEnvironmentCPUVendor is read from config_cream_gip_glue2 (attribute ExecutionEnvironment_xxx_ProcessorVendor)
    • For a CREAM CE in no-cluster mode this is the value of the yaim variable CE_CPU_VENDOR
    • For a gLite-cluster mode this is the value of the yaim variable SUBCLUSTER_xxx_HOST_ProcessorVendor
  • GLUE2ExecutionEnvironmentCPUModel is read from config_cream_gip_glue2 (attribute ExecutionEnvironment_xxx_ProcessorModel)
    • For a CREAM CE in no-cluster mode this is the value of the yaim variable CE_CPU_MODEL
    • For a gLite-cluster mode this is the value of the yaim variable = SUBCLUSTER_xxx_HOST_ProcessorModel=
Added:
>
>
  • GLUE2ExecutionEnvironmentCPUClockSpeed is read from config_cream_gip_glue2 (attribute ExecutionEnvironment_xxx_ProcessorClockSpeed)
    • For a CREAM CE in no-cluster mode this is the value of the yaim variable CE_CPU_SPEED
    • For a gLite-cluster mode this is the value of the yaim variable SUBCLUSTER_xxx_HOST_ProcessorClockSpeed
  • GLUE2ExecutionEnvironmentMainMemorySize is read from config_cream_gip_glue2 (attribute ExecutionEnvironment_xxx_MainMemoryRAMSize)
    • For a CREAM CE in no-cluster mode this is the value of the yaim variable CE_MINPHYSMEM
    • For a gLite-cluster mode this is the value of the yaim variable SUBCLUSTER_xxx_HOST_MainMemoryRAMSize
  • GLUE2ExecutionEnvironmentVirtualMemorySize is read from config_cream_gip_glue2 (attribute ExecutionEnvironment_xxx_MainMemoryVirtualSize)
    • For a CREAM CE in no-cluster mode this is the value of the yaim variable CE_MINVIRTMEM
    • For a gLite-cluster mode this is the value of the yaim variable SUBCLUSTER_xxx_HOST_MainMemoryVirtualSize
  • GLUE2ExecutionEnvironmentOSFamily is read from config_cream_gip_glue2 (attribute ExecutionEnvironment_xxx_OperatingSystemFamily)
    • For a CREAM CE in no-cluster mode this is the value of the yaim variable CE_OS_FAMILY
    • For a gLite-cluster mode this is the value of the yaim variable CE_OS_FAMILY
  • GLUE2ExecutionEnvironmentOSName is read from config_cream_gip_glue2 (attribute ExecutionEnvironment_xxx_OperatingSystemName)
    • For a CREAM CE in no-cluster mode this is the value of the yaim variable CE_OS
    • For a gLite-cluster mode this is the value of the yaim variable SUBCLUSTER_xxx_HOST_OperatingSystemName
  • GLUE2ExecutionEnvironmentOperatingSystemRelease is read from config_cream_gip_glue2 (attribute ExecutionEnvironment_xxx_OperatingSystemRelease)
    • For a CREAM CE in no-cluster mode this is the value of the yaim variable CE_OS_RELEASE
    • For a gLite-cluster mode this is the value of the yaim variable SUBCLUSTER_xxx_HOST_OperatingSystemRelease
  • GLUE2ExecutionEnvironmentConnectivityIn is read from config_cream_gip_glue2 (attribute ExecutionEnvironment_xxx_NetworkAdapterInboundIP)
    • For a CREAM CE in no-cluster mode this is the value of the yaim variable CE_INBOUNDIP
    • For a gLite-cluster mode this is the value of the yaim variable SUBCLUSTER_xxx_HOST_NetworkAdapterInboundIP)
  • GLUE2ExecutionEnvironmentConnectivityOut is read from config_cream_gip_glue2 (attribute ExecutionEnvironment_xxx_NetworkAdapterOutboundIP)
    • For a CREAM CE in no-cluster mode this is the value of the yaim variable CE_OUTBOUNDIP
    • For a gLite-cluster mode this is the value of the yaim variable SUBCLUSTER_xxx_HOST_NetworkAdapterOutboundIP
  • GLUE2ResourceManagerForeignKey is the ManagerId (i.e. "ServiceID" + "_Manager")
  • GLUE2ExecutionEnvironmentComputingManagerForeignKey is the same as GLUE2ResourceManagerForeignKey
 

Deleted:
<
<
TBC

 

0.0.1 ApplicationEnvironment

Line: 275 to 292
 

0.0.1 ApplicationHandle

Changed:
<
<
TBD
>
>
We don't implement the ApplicationHandle objectclass
 

0.0.1 ComputingActivity

Line: 283 to 300
 

0.0.1 ToStorageService

Changed:
<
<
TBD
>
>
There is a ToStorageService objectclass for each SE close to the considered CE

In the configuration file config_cream_gip_glue2 this is represented by the attribute CloseSEs which has the following format:

# Format: CloseSEs = (closeSE1, closeSE2, ..., closeSEn)
# Format of closeSEi: (StorageServiceid LocalPath RemotePath)

  • Each StorageServiceid is an element of the yaim variable SE_LIST
  • For LocalPath and RemotePath the values of SE_MOUNT_INFO_LIST are used
 
Added:
>
>
  • GLUE2ToStorageServiceID is the concatenation of ServiceId and StorageServiceId (the latter is read from config_cream_gip_glue: first attribute of a CloseSEs)
  • GLUE2EntityCreationTime is the timestamp when the ldif file was created
  • Glue2EntityName is the same as GLUE2ToStorageServiceID
  • GLUE2EntityOtherInfo includes information concerning the info provider
  • GLUE2ToStorageServiceLocalPath is read from config_cream_gip_glue (second attribute of a CloseSEs)
  • GLUE2ToStorageServiceRemotePath is read from config_cream_gip_glue (third attribute of a CloseSEs)
  • GLUE2ToStorageServiceComputingServiceForeignKey is the ServiceId
  • GLUE2ToStorageServiceStorageServiceForeignKey is the StorageServiceId (read from config_cream_gip_glue: first attribute of a CloseSEs)
 

Revision 332011-10-11 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 224 to 224
 For a gLite-Cluster there is one ExecutionEnvironment for each subcluster. However please note that, because of the current behavior in the WMS matchmaking, a ComputingShare can refer to a single ExecutionEnvironment. If there are multiple ExecutionEnvironments, the first one is chosen for such association.

  • GLUE2ResourceID
Changed:
<
<
    • for a CREAM CE in no-cluster mode, this is the first (and unique) element of the attribute ExecutionEnvironments in /etc/glite-ce-glue2/glite-ce-glue2.conf
hostname of the CREAM-CE
>
>
    • for a CREAM CE in no-cluster mode, this is the first (and unique) element of the attribute ExecutionEnvironments in /etc/glite-ce-glue2/glite-ce-glue2.conf (which is the hostname of the CREAM-CE)
 
    • for gLite-cluster this is an element of the attribute ExecutionEnvironments in /etc/glite-ce-glue2/glite-ce-glue2.conf, Each element of ExecutionEnvironments is a subcluster-identifier
  • GLUE2EntityCreationTime is the timestamp when the ldif file was created
  • GLUE2EntityName is the ResourceID
Line: 233 to 232
 
    • the smpsize: this is read from config_cream_gip_glue2 (attribute ExecutionEnvironment_xxx_SmpSize)
      • For a CREAM CE in no-cluster mode this is the value of the yaim variable CE_SMPSIZE
      • for a gLite-cluster this is the value of the yaim variable SUBCLUSTER_<subcluster-identifier>_HOST_ArchitectureSMPSize
Added:
>
>
    • the number of cores: this is read from config_cream_gip_glue2 (attribute ExecutionEnvironment_xxx_Cores)
      • For a CREAM CE in no cluster mode this is taken from the yaim variable CE_OTHERDESCR
      • For a gLite-cluster this is taken from the yaim variable SUBCLUSTER_xxx_HOST_ProcessorOtherDescription)
    • the info provider
  • GLUE2ExecutionEnvironmentPlatform is read from config_cream_gip_glue2 (attribute ExecutionEnvironment_xxx_ArchitecturePlatformType
    • For a CREAM CE in no-cluster mode this is the value of the yaim variable CE_OS_ARCH
    • For a gLite-cluster this is taken from the yaim variable SUBCLUSTER_xxx_HOST_ArchitecturePlatformType
  • GLUE2ExecutionEnvironmentTotalInstances is GLUE2ExecutionEnvironmentLogicalCPUs (see below) divide SmpSize (published in LUE2EntityOtherInfo, see above)
  • GLUE2ExecutionEnvironmentPhysicalCPUs is read from config_cream_gip_glue2 (attribute ExecutionEnvironment_xxx_PhysicalCPUs)
    • For a CREAM CE in no-cluster mode this is the value of the yaim variable CE_PHYSCPU
    • For a gLite-cluster mode this is the value of the yaim variable SUBCLUSTER_xxx_SUBCLUSTER_PhysicalCPUs
  • GLUE2ExecutionEnvironmentLogicalCPUs is read from config_cream_gip_glue2 (attribute ExecutionEnvironment_xxx_LogicalCPUs)
    • For a CREAM CE in no-cluster mode this is the value of the yaim variable CE_LOGCPU
    • For a gLite-cluster mode this is the value of the yaim variable SUBCLUSTER_xxx_SUBCLUSTER_LogicalCPUs
  • GLUE2ExecutionEnvironmentCPUMultiplicity is: + "cpu" + "-" . + "core"
  • GLUE2ExecutionEnvironmentCPUVendor is read from config_cream_gip_glue2 (attribute ExecutionEnvironment_xxx_ProcessorVendor)
    • For a CREAM CE in no-cluster mode this is the value of the yaim variable CE_CPU_VENDOR
    • For a gLite-cluster mode this is the value of the yaim variable SUBCLUSTER_xxx_HOST_ProcessorVendor
  • GLUE2ExecutionEnvironmentCPUModel is read from config_cream_gip_glue2 (attribute ExecutionEnvironment_xxx_ProcessorModel)
    • For a CREAM CE in no-cluster mode this is the value of the yaim variable CE_CPU_MODEL
    • For a gLite-cluster mode this is the value of the yaim variable = SUBCLUSTER_xxx_HOST_ProcessorModel=

  TBC
Changed:
<
<
    • the number of cores: this is read from config_cream_gip_glue2 (attribute ExecutionEnvironment_xxx_Cores; for a CREAM CE in no-cluster mode this is the taken from the yaim variable CE_OTHERDESCR)
    • the info provider
  • GLUE2ExecutionEnvironmentPlatform is read from config_cream_gip_glue2 (attribute ExecutionEnvironment_xxx_ArchitecturePlatformType; for a CREAM CE in no-cluster mode this is the value of the yaim variable CE_OS_ARCH)
>
>

 

Revision 322011-10-03 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 28 to 28
 
  • ComputingService (done)
  • ComputingEndPoint (done)
Changed:
<
<
  • AccessPolicy (done)
>
>
* AccessPolicy for ComputingEndPoint (done)
 
  • ComputingManager (done)
  • ComputingShare (done)
Added:
>
>
    • MappingPolicy for ComputingShare (done)
 
  • MappingPolicy (done)
  • ExecutionEnvironment (done)
  • Benchmark (done)
Line: 51 to 52
 
  • The resource BDII running on the CREAM CE publishes just the following objectclasses:
    • ComputingEndpoint (done)
Changed:
<
<
    • AccessPolicy (done)
>
>
      • AccessPolicy for ComputingEndpoint (done)
 
    • EndPoint for CEMon (done)
      • "Child" of ComputingService
      • Published only if CEMon is deployed
Line: 59 to 60
 
    • ComputingService (done)
    • ComputingManager (done)
    • ComputingShare (todo)
Added:
>
>
      • MappingPolicy for ComputingShare (todo)
 
    • MappingPolicy (todo)
    • ExecutionEnvironment (done)
    • Benchmark (done)
Line: 155 to 157
 
  • GLUE2ComputingShareEstimatedWorstWaitingTime is 2146660842 in the ldif static file; it is supposed to be overwritten by the generic dynamic scheduler plugin
  • GLUE2ComputingShareFreeSlots is 0 in the ldif static file; it is supposed to be overwritten by the generic dynamic scheduler plugin
  • GLUE2ShareResourceForeignKey
Changed:
<
<
    • for a CREAM CE in cluster mode this is the link to the first (and unique) ExecutionEnvironment (i.e. first element of ExecutionEnvironments in /etc/glite-ce-glue2/glite-ce-glue2.conf)
    • for a gLite cluster: TODO
>
>
    • for a CREAM CE in cluster mode this is the link to the first ExecutionEnvironment (i.e. first element of ExecutionEnvironments in /etc/glite-ce-glue2/glite-ce-glue2.conf)
    • for a gLite cluster: this is the link to the first ExecutionEnvironment (i.e. first element of ExecutionEnvironments in /etc/glite-ce-glue2/glite-ce-glue2.conf)
 
  • GLUE2ComputingShareExecutionEnvironmentForeignKey the same as GLUE2ShareResourceForeignKey
  • GLUE2ShareServiceForeignKey is the value ComputingServiceId in /etc/glite-ce-glue2/glite-ce-glue2.conf. This value is the one specified by the yaim variable COMPUTING_SERVICE_ID, if specified (this variable is mandatory in cluster mode). Otherwise it is =${CE_HOST}_ComputingElement
  • GLUE2ComputingShareComputingServiceForeignKey is the same as GLUE2ShareServiceForeignKey

TODO: link to computingendpoint

Added:
>
>

0.0.0.1 MappingPolicy for the ComputingEndPoint

  • GLUE2PolicyID is ComputingShareId plus "_policy
  • GLUE2EntityCreationTime is the timestamp when the ldif file was created
  • GLUE2PolicyScheme is org.glite.standard
  • GLUE2PolicyRule is = the ACBR (read from /etc/glite-ce-glue2/glite-ce-glue2.conf=)
  • GLUE2PolicyUserDomainForeignKey is the owner (read from /etc/glite-ce-glue2/glite-ce-glue2.conf=)
  • GLUE2MappingPolicyShareForeignKey is the ComputingShareId
 

0.0.1 ComputingManager

Line: 170 to 180
 
  • GLUE2EntityCreationTime is the timestamp when the ldif file was created
  • GLUE2EntityName is: "Computing Manager on <host>"
  • GLUE2EntityOtherInfo includes information concerning the info provider
Changed:
<
<
  • GLUE2ManagerProductName is the value CE_BATCH_SYS in /etc/glite-ce-glue2/glite-ce-glue2.conf. This value is the one specified by the yaim variable CE_BATCH_SYS=
>
>
  • GLUE2ManagerProductName is the value CE_BATCH_SYS in /etc/glite-ce-glue2/glite-ce-glue2.conf. This value is the one specified by the yaim variable CE_BATCH_SYS
 
  • GLUE2ManagerProductVersion in the ldif file is the value BATCH_VERSION in /etc/glite-ce-glue2/glite-ce-glue2.conf. This value is the one specified by the yaim variable BATCH_VERSION. It is supposed to be overwritten by the batch system specific dynamic plugin

Line: 209 to 219
 

0.0.1 ExecutionEnvironment

Changed:
<
<
For a CREAM CE configured in no cluster mode there is a single ExecutionEnvironment.
>
>
For a CREAM CE configured in no cluster mode there is a single ExecutionEnvironment.
 
Changed:
<
<
For a gLite-Cluster there is one ExecutionEnvironment for each subcluster. However please note that, because of the current behavior in the WMS matchmaking, a ComputingShare can refer to a single ExecutionEnvironment. If there are multiple ExecutionEnvironments, the first one is chosen for such association.
>
>
For a gLite-Cluster there is one ExecutionEnvironment for each subcluster. However please note that, because of the current behavior in the WMS matchmaking, a ComputingShare can refer to a single ExecutionEnvironment. If there are multiple ExecutionEnvironments, the first one is chosen for such association.
 
Changed:
<
<
  • GLUE2ResourceID: for a CREAM CE in no-cluster mode, this is the hostname of the CREAM-CE
>
>
  • GLUE2ResourceID
    • for a CREAM CE in no-cluster mode, this is the first (and unique) element of the attribute ExecutionEnvironments in /etc/glite-ce-glue2/glite-ce-glue2.conf
hostname of the CREAM-CE
    • for gLite-cluster this is an element of the attribute ExecutionEnvironments in /etc/glite-ce-glue2/glite-ce-glue2.conf, Each element of ExecutionEnvironments is a subcluster-identifier
 
  • GLUE2EntityCreationTime is the timestamp when the ldif file was created
Changed:
<
<
>
>
  • GLUE2EntityName is the ResourceID
 
  • GLUE2EntityOtherInfo includes information concerning
Changed:
<
<
    • the smpsize: this is read from config_cream_gip_glue2 (attribute ExecutionEnvironment_xxx_SmpSize; for a CREAM CE in no-cluster mode this is the value of the yaim-variable CE_SMPSIZE)
>
>
    • the smpsize: this is read from config_cream_gip_glue2 (attribute ExecutionEnvironment_xxx_SmpSize)
      • For a CREAM CE in no-cluster mode this is the value of the yaim variable CE_SMPSIZE
      • for a gLite-cluster this is the value of the yaim variable SUBCLUSTER_<subcluster-identifier>_HOST_ArchitectureSMPSize

TBC

 
    • the number of cores: this is read from config_cream_gip_glue2 (attribute ExecutionEnvironment_xxx_Cores; for a CREAM CE in no-cluster mode this is the taken from the yaim variable CE_OTHERDESCR)
    • the info provider
  • GLUE2ExecutionEnvironmentPlatform is read from config_cream_gip_glue2 (attribute ExecutionEnvironment_xxx_ArchitecturePlatformType; for a CREAM CE in no-cluster mode this is the value of the yaim variable CE_OS_ARCH)
Changed:
<
<
TBD
>
>
 

0.0.1 ApplicationEnvironment

Revision 312011-10-03 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 68 to 68
 
      • "Child" of ComputingService

  • The ServiceId is the the one specified by the yaim variable COMPUTING_SERVICE_ID which is such scenario is mandatory. This variable must have the same value in all the relevant nodes (in the cluster node and in all the CREAM CEs)
Changed:
<
<
The EndpointId is hostname + "_org.glite.ce.CREAM".
>
>
 

0.1 Objectclasses

Line: 94 to 94
 
  • GLUE2EndpointID is <hostname> + "_org.glite.ce.CREAM"
  • GLUE2EntityCreationTime is the timestamp when the ldif file was created
  • GLUE2EntityName is the EndPointId
Changed:
<
<
  • GLUE2EntityOtherInfo includes the host DN, the EMI middleware version, and information concerning the info provider
>
>
  • GLUE2EntityOtherInfo includes the host DN, the EMI middleware version, information if the CREAM CE is using Argus, and information concerning the info provider
 
  • GLUE2EndpointURL is the endpoint URL of the CREAM CE, that is: "https://" + <host> + "8443/ce-cream/services"
  • GLUE2EndpointCapability is executionmanagement.jobexecution
  • GLUE2EndpointTechnology is webservice

Revision 302011-09-29 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 209 to 209
 

0.0.1 ExecutionEnvironment

Changed:
<
<
For a CREAM CE configured in no cluster mode there is a single ExecutionEnvironment
>
>
For a CREAM CE configured in no cluster mode there is a single ExecutionEnvironment.

For a gLite-Cluster there is one ExecutionEnvironment for each subcluster. However please note that, because of the current behavior in the WMS matchmaking, a ComputingShare can refer to a single ExecutionEnvironment. If there are multiple ExecutionEnvironments, the first one is chosen for such association.

 
  • GLUE2ResourceID: for a CREAM CE in no-cluster mode, this is the hostname of the CREAM-CE
  • GLUE2EntityCreationTime is the timestamp when the ldif file was created

Revision 292011-09-28 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 69 to 69
 
  • The ServiceId is the the one specified by the yaim variable COMPUTING_SERVICE_ID which is such scenario is mandatory. This variable must have the same value in all the relevant nodes (in the cluster node and in all the CREAM CEs)
The EndpointId is hostname + "_org.glite.ce.CREAM".
Changed:
<
<
xxx
>
>
 

0.1 Objectclasses

Line: 84 to 84
 
  • GLUE2ServiceCapability is executionmanagement.jobexecution
  • GLUE2ServiceType is org.glite.ce.CREAM
  • GLUE2ServiceQualityLevel is production
Changed:
<
<
  • GLUE2ServiceComplexity indicates the number of endpoints (2 or 3: one for CREAM, one for the RTEPublisher and one for CEMon, if deployed), the number of shares, and the number of resources (i.e. the number of Execution Environments)
>
>
  • GLUE2ServiceComplexity indicates the number of endpoints, the number of shares, and the number of resources
    • For a CREAM CE in no-cluster mode: endpoints (2 or 3: one for CREAM, one for the RTEPublisher and one for CEMon, if deployed),
    • For a gLite-cluster TODO: endpoints should consider the total number of CREAM endpoints (how to find this ?) the total number of CEMon (how to find this ???) and the RTEPublisher
 
  • GLUE2ServiceAdminDomainForeignKey is the value of SiteId in /etc/glite-ce-glue2/glite-ce-glue2.conf. This value is the one specified by the yaim variable SITE_NAME

0.0.1 ComputingEndpoint

Line: 115 to 117
 
  • GLUE2EndpointDownTimeInfo is "See the GOC DB for downtimes: https://goc.egi.eu"
  • GLUE2ComputingEndpointStaging is staginginout
  • GLUE2ComputingEndpointJobDescription is glite:jdl
Added:
>
>
  • GLUE2EndpointServiceForeignKey is the value ComputingServiceId in /etc/glite-ce-glue2/glite-ce-glue2.conf. This value is the one specified by the yaim variable COMPUTING_SERVICE_ID, if specified (this variable is mandatory in cluster mode). Otherwise it is =${CE_HOST}_ComputingElement
  • GLUE2ComputingEndpointComputingServiceForeignKey is the same as GLUE2EndpointServiceForeignKey
 Todo: start time ?

0.0.0.1 Policy for the Computing EndPoint

Line: 127 to 131
 
  • GLUE2PolicyScheme is org.glite.standard
  • GLUE2PolicyRule is an element of ACBR in /etc/glite-ce-glue2/glite-ce-glue2.conf (e.g. VO:cms). It is ALL if there are no policies
  • GLUE2PolicyUserDomainForeignKey is an element of Owner in /etc/glite-ce-glue2/glite-ce-glue2.conf (e.g. cms)
Added:
>
>
  • GLUE2AccessPolicyEndpointForeignKey is the EndpointId (<hostname> + "_org.glite.ce.CREAM")
 

0.0.1 ComputingShare

Line: 149 to 154
 
  • GLUE2ComputingShareEstimatedAverageWaitingTime is 2146660842 in the ldif static file; it is supposed to be overwritten by the generic dynamic scheduler plugin
  • GLUE2ComputingShareEstimatedWorstWaitingTime is 2146660842 in the ldif static file; it is supposed to be overwritten by the generic dynamic scheduler plugin
  • GLUE2ComputingShareFreeSlots is 0 in the ldif static file; it is supposed to be overwritten by the generic dynamic scheduler plugin
Added:
>
>
  • GLUE2ShareResourceForeignKey
    • for a CREAM CE in cluster mode this is the link to the first (and unique) ExecutionEnvironment (i.e. first element of ExecutionEnvironments in /etc/glite-ce-glue2/glite-ce-glue2.conf)
    • for a gLite cluster: TODO
  • GLUE2ComputingShareExecutionEnvironmentForeignKey the same as GLUE2ShareResourceForeignKey
  • GLUE2ShareServiceForeignKey is the value ComputingServiceId in /etc/glite-ce-glue2/glite-ce-glue2.conf. This value is the one specified by the yaim variable COMPUTING_SERVICE_ID, if specified (this variable is mandatory in cluster mode). Otherwise it is =${CE_HOST}_ComputingElement
  • GLUE2ComputingShareComputingServiceForeignKey is the same as GLUE2ShareServiceForeignKey
  TODO: link to computingendpoint
Line: 234 to 245
 

1 Batch system dynamic information

Changed:
<
<

0.1 Torque/PBS

>
>

0.1 Current Glue 1 scenario

0.1.1 Torque/PBS

  The PBS dynamic plugin for Glue1 publishes for each batch system queue something like:
Line: 249 to 262
 GlueCEStateStatus: Production
Deleted:
<
<
The generic dynamic scheduler plugin, for Glue1 publishes for each VOView something like:

dn: GlueVOViewLocalID=alice,GlueCEUniqueID=cream-38.pd.infn.it:8443/cream-pbs-creamtest1,mds-vo-name=resource,o=grid
GlueVOViewLocalID: alice
GlueCEStateRunningJobs: 0
GlueCEStateWaitingJobs: 0
GlueCEStateTotalJobs: 0
GlueCEStateFreeJobSlots: 5
GlueCEStateEstimatedResponseTime: 0
GlueCEStateWorstResponseTime: 0

and for each queue publishes something like:

 
Deleted:
<
<
dn: GlueCEUniqueID=cream-38.pd.infn.it:8443/cream-pbs-creamtest1,mds-vo-name=resource,o=grid
GlueCEStateFreeJobSlots: 5
GlueCEStateFreeCPUs: 5
GlueCEStateRunningJobs: 0
GlueCEStateWaitingJobs: 0
GlueCEStateTotalJobs: 0
GlueCEStateEstimatedResponseTime: 0
GlueCEStateWorstResponseTime: 0
 
Changed:
<
<

0.1 LSF

>
>

0.0.1 LSF

  The LSF dynamic plugin for Glue1 publishes for each batch system queue something like:
Line: 293 to 282
 GlueCEStateStatus: Production
Deleted:
<
<
The generic dynamic scheduler plugin, for Glue1 publishes for each VOView something like:

dn: GlueVOViewLocalID=alice,GlueCEUniqueID=cream-29.pd.infn.it:8443/cream-lsf-creamcert1,mds-vo-name=resource,o=grid
GlueVOViewLocalID: alice
GlueCEStateRunningJobs: 0
GlueCEStateWaitingJobs: 0
GlueCEStateTotalJobs: 0
GlueCEStateFreeJobSlots: 216
GlueCEStateEstimatedResponseTime: 0
GlueCEStateWorstResponseTime: 0

and for each queue publishes something like:

dn: GlueCEUniqueID=cream-29.pd.infn.it:8443/cream-lsf-creamcert1,mds-vo-name=resource,o=grid
GlueCEStateFreeJobSlots: 216
GlueCEStateFreeCPUs: 216
GlueCEStateRunningJobs: 0
GlueCEStateWaitingJobs: 0
GlueCEStateTotalJobs: 0
GlueCEStateEstimatedResponseTime: 0
GlueCEStateWorstResponseTime: 0
 
Changed:
<
<

0.1 SGE

>
>

0.0.1 SGE

  The SGE dynamic plugin for Glue1 publishes for each batch system queue something like:
Line: 336 to 300
 GlueCEStateStatus: Production
Added:
>
>

0.0.1 Generic dynamic scheduler

 The generic dynamic scheduler plugin, for Glue1 publishes for each VOView something like:
Changed:
<
<
dn: GlueVOViewLocalID=biomed,GlueCEUniqueID=sa3-ce.egee.cesga.es:8443/cream-sge-biomed,mds-vo-name=resource,o=grid GlueVOViewLocalID: biomed
>
>
dn: GlueVOViewLocalID=alice,GlueCEUniqueID=cream-38.pd.infn.it:8443/cream-pbs-creamtest1,mds-vo-name=resource,o=grid GlueVOViewLocalID: alice
 GlueCEStateRunningJobs: 0 GlueCEStateWaitingJobs: 0 GlueCEStateTotalJobs: 0
Changed:
<
<
GlueCEStateFreeJobSlots: 1
>
>
GlueCEStateFreeJobSlots: 5
 GlueCEStateEstimatedResponseTime: 0 GlueCEStateWorstResponseTime: 0
Line: 352 to 320
 and for each queue publishes something like:
Changed:
<
<
dn: GlueCEUniqueID=sa3-ce.egee.cesga.es:8443/cream-sge-biomed,mds-vo-name=resource,o=grid GlueCEStateFreeJobSlots: 1 GlueCEStateFreeCPUs: 1
>
>
dn: GlueCEUniqueID=cream-38.pd.infn.it:8443/cream-pbs-creamtest1,mds-vo-name=resource,o=grid GlueCEStateFreeJobSlots: 5 GlueCEStateFreeCPUs: 5
 GlueCEStateRunningJobs: 0 GlueCEStateWaitingJobs: 0 GlueCEStateTotalJobs: 0

Revision 282011-09-28 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 18 to 18
 

1 Target scenario

Added:
>
>

0.1 CREAM CE in no cluster mode

We assume that a CREAM CE is configured in cluster mode if that is the only CREAM CE available in the site. I.e. sites with multiple CREAM CEs (submitting to the same batch system) should always have a cluster node and therefore be configured in cluster mode.

If a CREAM CE is configured in no cluster mode, all the Glue2 object classes are published by the resource BDII running on the CREAM CE.

These objectclasses are:

  • ComputingService (done)
  • ComputingEndPoint (done)
  • AccessPolicy (done)
  • ComputingManager (done)
  • ComputingShare (done)
  • MappingPolicy (done)
  • ExecutionEnvironment (done)
  • Benchmark (done)
  • ToStorageService (done)
  • ApplicationEnvironment (todo)
  • EndPoint for RTEPublihser (done)
    • "Child" of ComputingService
  • EndPoint for CEMon (done)
    • "Child" of ComputingService
    • Published only if CEMon is deployed

0.2 CREAM CE in cluster mode

Sites with multiple CREAM CEs (submitting to the same batch system) should always have a cluster node and therefore be configured in cluster mode.

If a CREAM CE is configured in cluster mode:

  • The resource BDII running on the CREAM CE publishes just the following objectclasses:
    • ComputingEndpoint (done)
    • AccessPolicy (done)
    • EndPoint for CEMon (done)
      • "Child" of ComputingService
      • Published only if CEMon is deployed
  • All the other objectclasses are published by the resource BDII running on the gLite-CLUSTER node:
    • ComputingService (done)
    • ComputingManager (done)
    • ComputingShare (todo)
    • MappingPolicy (todo)
    • ExecutionEnvironment (done)
    • Benchmark (done)
    • ToStorageService (done)
    • ApplicationEnvironment (todo)
    • EndPoint for RTEPublihser (done)
      • "Child" of ComputingService

  • The ServiceId is the the one specified by the yaim variable COMPUTING_SERVICE_ID which is such scenario is mandatory. This variable must have the same value in all the relevant nodes (in the cluster node and in all the CREAM CEs)
The EndpointId is hostname + "_org.glite.ce.CREAM". xxx
 

0.1 Objectclasses

This section reports the most significant information concerning the implementation of the Glue 2 objectclasses wrt the CREAM CE

0.1.1 ComputingService

Changed:
<
<
  • GLUE2ServiceID is the value ComputingServiceId in /etc/glite-ce-glue2/glite-ce-glue2.conf. This value is the one specified by the yaim variable COMPUTING_SERVICE_ID, if specified (this variable is mandatory in cluster mode, see below). Otherwise it is ${CE_HOST}_ComputingElement
>
>
  • GLUE2ServiceID is the value ComputingServiceId in /etc/glite-ce-glue2/glite-ce-glue2.conf. This value is the one specified by the yaim variable COMPUTING_SERVICE_ID, if specified (this variable is mandatory in cluster mode). Otherwise it is ${CE_HOST}_ComputingElement
 
  • GLUE2EntityCreationTime is the timestamp when the ldif file was created
  • GLUE2EntityName is "Computing Service on <host>"
  • GLUE2EntityOtherInfo includes information concerning the info provider
Line: 175 to 228
  TBD
Deleted:
<
<

0.1 CREAM CE in no cluster mode

We assume that a CREAM CE is configured in cluster mode if that is the only CREAM CE available in the site. I.e. sites with multiple CREAM CEs (submitting to the same batch system) should always have a cluster node and therefore be configured in cluster mode.

If a CREAM CE is configured in no cluster mode, all the Glue2 object classes are published by the resource BDII running on the CREAM CE.

These objectclasses are:

  • ComputingService (done)
  • ComputingEndPoint (done)
  • AccessPolicy (done)
  • ComputingManager (done)
  • ComputingShare (done)
  • MappingPolicy (done)
  • ExecutionEnvironment (done)
  • Benchmark (done)
  • ToStorageService (done)
  • ApplicationEnvironment (todo)
  • EndPoint for RTEPublihser (done)
    • "Child" of ComputingService
  • EndPoint for CEMon (done)
    • "Child" of ComputingService
    • Published only if CEMon is deployed
The ComputingServiceId is the one specified by the yaim variable COMPUTING_SERVICE_ID (if specified). Otherwise it is ${CE_HOST}_ComputingElement..

The EndpointId! is hostname + "_org.glite.ce.CREAM".

0.2 CREAM CE in cluster mode

Sites with multiple CREAM CEs (submitting to the same batch system) should always have a cluster node and therefore be configured in cluster mode.

 
Deleted:
<
<
If a CREAM CE is configured in cluster mode:
 
Deleted:
<
<
  • The resource BDII running on the CREAM CE publishes just the following objectclasses:
    • ComputingEndpoint (done)
    • AccessPolicy (done)
  • All the other objectclasses are published by the resource BDII running on the gLite-CLUSTER node:
    • ComputingService (done)
    • ComputingManager (done)
    • ComputingShare (todo)
    • MappingPolicy (todo)
    • ExecutionEnvironment (done)
    • Benchmark (done)
    • ToStorageService (done)
    • ApplicationEnvironment (todo)
    • EndPoint for RTEPublihser (done)
      • "Child" of ComputingService
 
Deleted:
<
<
  • The ServiceId is the the one specified by the yaim variable COMPUTING_SERVICE_ID which is such scenario is mandatory. This variable must have the same value in all the relevant nodes (in the cluster node and in all the CREAM CEs)
The EndpointId is hostname + "_org.glite.ce.CREAM".
 

1 Batch system dynamic information

Line: 415 to 421
 
  • cream-38.pd.infn.it (Torque)
  • cream-29.pd.infn.it (LSF)
Added:
>
>
  • cream-18.pd.infn.it (gLite-cluster node)
  -- MassimoSgaravatto - 2011-06-21 \ No newline at end of file

Revision 272011-09-27 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 97 to 97
 
  • GLUE2ComputingShareEstimatedWorstWaitingTime is 2146660842 in the ldif static file; it is supposed to be overwritten by the generic dynamic scheduler plugin
  • GLUE2ComputingShareFreeSlots is 0 in the ldif static file; it is supposed to be overwritten by the generic dynamic scheduler plugin
Added:
>
>
TODO: link to computingendpoint
 

0.0.1 ComputingManager

Revision 262011-09-26 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 143 to 143
 

0.0.1 ExecutionEnvironment

Added:
>
>
For a CREAM CE configured in no cluster mode there is a single ExecutionEnvironment

  • GLUE2ResourceID: for a CREAM CE in no-cluster mode, this is the hostname of the CREAM-CE
  • GLUE2EntityCreationTime is the timestamp when the ldif file was created
  • GLUE2EntityName is the ResourceID
  • GLUE2EntityOtherInfo includes information concerning
    • the smpsize: this is read from config_cream_gip_glue2 (attribute ExecutionEnvironment_xxx_SmpSize; for a CREAM CE in no-cluster mode this is the value of the yaim-variable CE_SMPSIZE)
    • the number of cores: this is read from config_cream_gip_glue2 (attribute ExecutionEnvironment_xxx_Cores; for a CREAM CE in no-cluster mode this is the taken from the yaim variable CE_OTHERDESCR)
    • the info provider
  • GLUE2ExecutionEnvironmentPlatform is read from config_cream_gip_glue2 (attribute ExecutionEnvironment_xxx_ArchitecturePlatformType; for a CREAM CE in no-cluster mode this is the value of the yaim variable CE_OS_ARCH)
 TBD

0.0.1 ApplicationEnvironment

Revision 252011-09-23 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 13 to 12
  The Glue 2.0 specification can also be found here.
Changed:
<
<
The GLUE v. 2.0 Reference Implementation of an LDAP Schema document can be found here.
>
>
The GLUE v. 2.0 – Reference Implementation of an LDAP Schema document can be found here.
  Glue 2.0 schema in SVN
Line: 27 to 26
 
  • GLUE2ServiceID is the value ComputingServiceId in /etc/glite-ce-glue2/glite-ce-glue2.conf. This value is the one specified by the yaim variable COMPUTING_SERVICE_ID, if specified (this variable is mandatory in cluster mode, see below). Otherwise it is ${CE_HOST}_ComputingElement
  • GLUE2EntityCreationTime is the timestamp when the ldif file was created
Changed:
<
<
  • GLUE2EntityName is "Computing Service on =host="
>
>
  • GLUE2EntityName is "Computing Service on <host>"
 
  • GLUE2EntityOtherInfo includes information concerning the info provider
  • GLUE2ServiceCapability is executionmanagement.jobexecution
  • GLUE2ServiceType is org.glite.ce.CREAM
Line: 37 to 36
 

0.0.1 ComputingEndpoint

Changed:
<
<
  • GLUE2EndpointID is hostname + "_org.glite.ce.CREAM"
>
>
  • GLUE2EndpointID is <hostname> + "_org.glite.ce.CREAM"
 
  • GLUE2EntityCreationTime is the timestamp when the ldif file was created
  • GLUE2EntityName is the EndPointId
  • GLUE2EntityOtherInfo includes the host DN, the EMI middleware version, and information concerning the info provider
Changed:
<
<
  • GLUE2EndpointURL is the endpoint URL of the CREAM CE, that is: "https://" + host + "8443/ce-cream/services"
>
>
  • GLUE2EndpointURL is the endpoint URL of the CREAM CE, that is: "https://" + <host> + "8443/ce-cream/services"
 
  • GLUE2EndpointCapability is executionmanagement.jobexecution
  • GLUE2EndpointTechnology is webservice
  • GLUE2EndpointInterfaceName is org.glite.ce.CREAM
  • GLUE2EndpointInterfaceVersion is read from the CREAM configuration file (attribute cream_interface_version)
Changed:
<
<
  • GLUE2EndpointWSDL is got from the service itself, i.e. "https://" + host + ":8443/ce-cream/services/CREAM2?wsdl";
>
>
  • GLUE2EndpointWSDL is got from the service itself, i.e. "https://" + <host> + ":8443/ce-cream/services/CREAM2?wsdl";
 
  • GLUE2EndpointSupportedProfile is http://www.ws-i.org/Profiles/BasicProfile-1.0.html
  • GLUE2EndpointSemantics is the link to the CREAM user guide
  • GLUE2EndpointImplementor is gLite
Line: 55 to 54
 
  • GLUE2EndpointQualityLevel=s is =production
  • GLUE2EndpointHealthState is unknown in the ldif static file; it is overwritten by the glite-ce-glue2-endpoint-dynamic plugin (which check the glite-info-service-test output and the status of the tomcat service)
  • GLUE2EndpointHealthStateInfo is N/A in the ldif static file; it is overwritten by the glite-ce-glue2-endpoint-dynamic plugin (which check the glite-info-service-test output)
Changed:
<
<
  • GLUE2EndpointServingState is the value ServingState in /etc/glite-ce-glue2/glite-ce-glue2.conf. This value is the one specified by the yaim variable CREAM_CE_STATE
    • Todo: see bug #69854
>
>
  • GLUE2EndpointServingState
    • Now is a static value, read from /etc/glite-ce-glue2/glite-ce-glue2.conf (attribute ServingState). This value is the one specified by the yaim variable CREAM_CE_STATE
    • Target scenario: is a value provided by a dynamic plugin; it is checked if submissions are disabled (by the limiter, or explicitly by the admin). If so, it is published draining (see also http://savannah.cern.ch/bugs/?69854). Otherwise the value is read from /etc/glite-ce-glue2/glite-ce-glue2.conf (attribute ServingState), which is initially filled by yaim considering the yaim variable CREAM_CE_STATE. The admin can edit this file if he wants to publish a specific value without reconfiguring.
 
  • GLUE2EndpointIssuerCA is found with a "openssl x509 -issuer -noout -in" on the host certificate
  • GLUE2EndpointTrustedCA is IGTF
  • GLUE2EndpointDownTimeInfo is "See the GOC DB for downtimes: https://goc.egi.eu"
  • GLUE2ComputingEndpointStaging is staginginout
  • GLUE2ComputingEndpointJobDescription is glite:jdl
Changed:
<
<
>
>
Todo: start time ?
 

0.0.0.1 Policy for the Computing EndPoint

Changed:
<
<
For each ComputingEndpoint, there are as many as policies as the policy rules that must be defined
>
>
For each ComputingEndpoint, there are as many as policies as the policy rules that must be defined
 
  • GLUE2EntityCreationTime is the timestamp when the ldif file was created
Changed:
<
<
  • "GLUE2EntityName is "Access control rules for Endpoint EndPointId"
>
>
  • "GLUE2EntityName is "Access control rules for Endpoint EndPointId"
 
  • GLUE2EntityOtherInfo includes information concerning the info provider
  • GLUE2PolicyScheme is org.glite.standard
Changed:
<
<
  • GLUE2PolicyRule is an element of ACBR in /etc/glite-ce-glue2/glite-ce-glue2.conf (e.g. VO:cms). It is ALL if there are no policies
>
>
  • GLUE2PolicyRule is an element of ACBR in /etc/glite-ce-glue2/glite-ce-glue2.conf (e.g. VO:cms). It is ALL if there are no policies
 
  • GLUE2PolicyUserDomainForeignKey is an element of Owner in /etc/glite-ce-glue2/glite-ce-glue2.conf (e.g. cms)
Deleted:
<
<
Todo: start time ?
 

0.0.1 ComputingShare

A ComputingShare corresponds to a Glue1 VOView.

If needed, besides the VOViews we will also represent batch system queues as ComputingShares (this will have some impact on the WMS matchmaker)

Changed:
<
<
TBC
>
>
  • GLUE2ShareID is concatenation of queue name + owner + ServiceId
  • GLUE2EntityCreationTime is the timestamp when the ldif file was created
  • GLUE2EntityOtherInfo includes the CEId and information concerning the info provider
  • GLUE2ShareDescription is "Share of <queuename> for <VO>"
  • GLUE2ComputingShareMappingQueue is the batch system queue name
  • GLUE2ComputingShareMaxWallTime is 999999999 in the ldif static file; it is supposed to be overwritten by the batch system specific dynamic plugin
  • GLUE2ComputingShareMaxCPUTime is 999999999 in the ldif static file; it is supposed to be overwritten by the batch system specific dynamic plugin
  • GLUE2ComputingShareMaxRunningJobs is 999999999 in the ldif static file; it is supposed to be overwritten by the batch system specific dynamic plugin
  • GLUE2ComputingShareServingState is production in the ldif static file; it is supposed to be overwritten by the batch system specific dynamic plugin
  • GLUE2ComputingShareTotalJobs is 0 in the ldif static file; it is supposed to be overwritten by the generic dynamic scheduler plugin
  • GLUE2ComputingShareRunningJobs is 0 in the ldif static file; it is supposed to be overwritten by the generic dynamic scheduler plugin
  • GLUE2ComputingShareWaitingJobs is 444444 in the ldif static file; it is supposed to be overwritten by the generic dynamic scheduler plugin
  • GLUE2ComputingShareEstimatedAverageWaitingTime is 2146660842 in the ldif static file; it is supposed to be overwritten by the generic dynamic scheduler plugin
  • GLUE2ComputingShareEstimatedWorstWaitingTime is 2146660842 in the ldif static file; it is supposed to be overwritten by the generic dynamic scheduler plugin
  • GLUE2ComputingShareFreeSlots is 0 in the ldif static file; it is supposed to be overwritten by the generic dynamic scheduler plugin
 

0.0.1 ComputingManager

Changed:
<
<
TBD
>
>
  • GLUE2ManagerID is ServiceId + "_Manager"
  • GLUE2EntityCreationTime is the timestamp when the ldif file was created
  • GLUE2EntityName is: "Computing Manager on <host>"
  • GLUE2EntityOtherInfo includes information concerning the info provider
  • GLUE2ManagerProductName is the value CE_BATCH_SYS in /etc/glite-ce-glue2/glite-ce-glue2.conf. This value is the one specified by the yaim variable CE_BATCH_SYS=
  • GLUE2ManagerProductVersion in the ldif file is the value BATCH_VERSION in /etc/glite-ce-glue2/glite-ce-glue2.conf. This value is the one specified by the yaim variable BATCH_VERSION. It is supposed to be overwritten by the batch system specific dynamic plugin

 

0.0.1 Benchmark

Changed:
<
<
TBD
>
>
For each ExecutionEnvironment, a Benchmark objectclass is created for each benchmark that must be represented.

In /etc/glite-ce-glue2/glite-ce-glue2.conf (filled by yaim) the following is defined:

ExecutionEnvironment_<ExecutionEnvironmentId>_Benchmarks = (Benchmark1, Benchmark2, .., Benchmarkn)

where the format of Benchmarki is: (Type Value)

This is then used to produce the ldif file with the Benchmark objectclasses.

The benchmark that are now represented are:

  • specfp2000 (using the yaim variable CE_SF00)
  • specint2000 (using the yaim variable CE_SI0)
  • HEP-SPEC06 (if the yaim variable CE_OTHERDESCR reports the value for this benchmark)

  • GLUE2BenchmarkID is the concatenation of ResourceId and type of benchmark
  • GLUE2EntityCreationTime is the timestamp when the ldif file was created
  • Glue2EntityName is "Benchmark" + the type of bechmark
  • GLUE2EntityOtherInfo includes information concerning the info provider
  • GLUE2BenchmarkType is the type of benchmark (specfp2000, specint2000, ..)
  • GLUE2BenchmarkValue is the value for that benchmark
 

0.0.1 ExecutionEnvironment

Line: 312 to 349
 
  • 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 GLUE2ComputingShareMaxWallTime (ComputingShare objectclass) * For all the ComputingShares referring to that batch system queue
>
>
  • 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
 
  • 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

Deleted:
<
<
 

0.0.1 Work to be done in the LSF information provider

  • The value published in Glue1 as GlueCEInfoLRMSVersion should be published in Glue2 as GLUE2ManagerProductVersion (ComputingManager objectclass)
Line: 347 to 379
 

0.0.1 Work to be done in the generic dynamic scheduler

Deleted:
<
<
 
  • 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)

Revision 242011-09-20 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 48 to 48
 
  • GLUE2EndpointInterfaceVersion is read from the CREAM configuration file (attribute cream_interface_version)
  • GLUE2EndpointWSDL is got from the service itself, i.e. "https://" + host + ":8443/ce-cream/services/CREAM2?wsdl";
  • GLUE2EndpointSupportedProfile is http://www.ws-i.org/Profiles/BasicProfile-1.0.html
Changed:
<
<
  • GLUE2EndpointSemantics is the link to the CREAM user guide (to be fixed)
TBD
>
>
  • GLUE2EndpointSemantics is the link to the CREAM user guide
  • GLUE2EndpointImplementor is gLite
  • GLUE2EndpointImplementationName is CREAM
  • GLUE2EndpointImplementationVersion is read from the CREAM configuration file (attribute cream_service_version)
  • GLUE2EndpointQualityLevel=s is =production
  • GLUE2EndpointHealthState is unknown in the ldif static file; it is overwritten by the glite-ce-glue2-endpoint-dynamic plugin (which check the glite-info-service-test output and the status of the tomcat service)
  • GLUE2EndpointHealthStateInfo is N/A in the ldif static file; it is overwritten by the glite-ce-glue2-endpoint-dynamic plugin (which check the glite-info-service-test output)
  • GLUE2EndpointServingState is the value ServingState in /etc/glite-ce-glue2/glite-ce-glue2.conf. This value is the one specified by the yaim variable CREAM_CE_STATE
    • Todo: see bug #69854
  • GLUE2EndpointIssuerCA is found with a "openssl x509 -issuer -noout -in" on the host certificate
  • GLUE2EndpointTrustedCA is IGTF
  • GLUE2EndpointDownTimeInfo is "See the GOC DB for downtimes: https://goc.egi.eu"
  • GLUE2ComputingEndpointStaging is staginginout
  • GLUE2ComputingEndpointJobDescription is glite:jdl

0.0.0.1 Policy for the Computing EndPoint

For each ComputingEndpoint, there are as many as policies as the policy rules that must be defined

  • GLUE2EntityCreationTime is the timestamp when the ldif file was created
  • "GLUE2EntityName is "Access control rules for Endpoint EndPointId"
  • GLUE2EntityOtherInfo includes information concerning the info provider
  • GLUE2PolicyScheme is org.glite.standard
  • GLUE2PolicyRule is an element of ACBR in /etc/glite-ce-glue2/glite-ce-glue2.conf (e.g. VO:cms). It is ALL if there are no policies
  • GLUE2PolicyUserDomainForeignKey is an element of Owner in /etc/glite-ce-glue2/glite-ce-glue2.conf (e.g. cms)

Todo: start time ?

 

0.0.1 ComputingShare

Revision 232011-09-20 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 26 to 26
 

0.0.1 ComputingService

  • GLUE2ServiceID is the value ComputingServiceId in /etc/glite-ce-glue2/glite-ce-glue2.conf. This value is the one specified by the yaim variable COMPUTING_SERVICE_ID, if specified (this variable is mandatory in cluster mode, see below). Otherwise it is ${CE_HOST}_ComputingElement
Added:
>
>
  • GLUE2EntityCreationTime is the timestamp when the ldif file was created
  • GLUE2EntityName is "Computing Service on =host="
  • GLUE2EntityOtherInfo includes information concerning the info provider
 
  • GLUE2ServiceCapability is executionmanagement.jobexecution
  • GLUE2ServiceType is org.glite.ce.CREAM
Added:
>
>
  • GLUE2ServiceQualityLevel is production
  • GLUE2ServiceComplexity indicates the number of endpoints (2 or 3: one for CREAM, one for the RTEPublisher and one for CEMon, if deployed), the number of shares, and the number of resources (i.e. the number of Execution Environments)
 
  • GLUE2ServiceAdminDomainForeignKey is the value of SiteId in /etc/glite-ce-glue2/glite-ce-glue2.conf. This value is the one specified by the yaim variable SITE_NAME

0.0.1 ComputingEndpoint

Added:
>
>
  • GLUE2EndpointID is hostname + "_org.glite.ce.CREAM"
  • GLUE2EntityCreationTime is the timestamp when the ldif file was created
  • GLUE2EntityName is the EndPointId
  • GLUE2EntityOtherInfo includes the host DN, the EMI middleware version, and information concerning the info provider
  • GLUE2EndpointURL is the endpoint URL of the CREAM CE, that is: "https://" + host + "8443/ce-cream/services"
  • GLUE2EndpointCapability is executionmanagement.jobexecution
  • GLUE2EndpointTechnology is webservice
  • GLUE2EndpointInterfaceName is org.glite.ce.CREAM
  • GLUE2EndpointInterfaceVersion is read from the CREAM configuration file (attribute cream_interface_version)
  • GLUE2EndpointWSDL is got from the service itself, i.e. "https://" + host + ":8443/ce-cream/services/CREAM2?wsdl";
  • GLUE2EndpointSupportedProfile is http://www.ws-i.org/Profiles/BasicProfile-1.0.html
  • GLUE2EndpointSemantics is the link to the CREAM user guide (to be fixed)
 TBD

0.0.1 ComputingShare

Revision 222011-09-20 - MassimoSgaravatto

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

Glue2 support in CREAM

CREAM CE provided with EMI-1 provides some initial support for glue2, that needs to be finalized

Added:
>
>
 

1 Introduction

The Glue 2.0 specification document is available here.

Line: 231 to 234
  The generic dynamic scheduler plugin, for Glue1 publishes for each VOView something like:
Changed:
<
<
xyz
>
>
dn: GlueVOViewLocalID=biomed,GlueCEUniqueID=sa3-ce.egee.cesga.es:8443/cream-sge-biomed,mds-vo-name=resource,o=grid
GlueVOViewLocalID: biomed
GlueCEStateRunningJobs: 0
GlueCEStateWaitingJobs: 0
GlueCEStateTotalJobs: 0
GlueCEStateFreeJobSlots: 1
GlueCEStateEstimatedResponseTime: 0
GlueCEStateWorstResponseTime: 0
  and for each queue publishes something like:
Changed:
<
<
xyz
>
>
dn: GlueCEUniqueID=sa3-ce.egee.cesga.es:8443/cream-sge-biomed,mds-vo-name=resource,o=grid
GlueCEStateFreeJobSlots: 1
GlueCEStateFreeCPUs: 1
GlueCEStateRunningJobs: 0
GlueCEStateWaitingJobs: 0
GlueCEStateTotalJobs: 0
GlueCEStateEstimatedResponseTime: 0
GlueCEStateWorstResponseTime: 0
 
Deleted:
<
<
TBC
 

0.1 Work to be done to support Glue2 publication

Line: 268 to 289
 
    • For all the ComputingShares referring to that batch system queue
Added:
>
>

0.0.1 Work to be done in the SGE information provider

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

Line: 278 to 311
 
  • 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)
Deleted:
<
<

0.0.1 Work to be done in the SGE information provider

 
Deleted:
<
<
TBD
 

1 Relevant RFCs

Revision 212011-09-20 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 213 to 213
 

0.1 SGE

Changed:
<
<
TBD
>
>
The SGE dynamic plugin for Glue1 publishes for each batch system queue something like:

dn: GlueCEUniqueID=sa3-ce.egee.cesga.es:8443/cream-sge-ops,mds-vo-name=resource,o=grid
GlueCEInfoLRMSVersion: 6.1u3
GlueCEPolicyAssignedJobSlots: 1
GlueCEPolicyMaxRunningJobs: 1
GlueCEInfoTotalCPUs: 1
GlueCEStateFreeJobSlots: 1
GlueCEStateFreeCPUs: 1
GlueCEPolicyMaxCPUTime: 4320
GlueCEPolicyMaxWallClockTime: 9000
GlueCEStateStatus: Production

The generic dynamic scheduler plugin, for Glue1 publishes for each VOView something like:

xyz

and for each queue publishes something like:

xyz

TBC

 

0.1 Work to be done to support Glue2 publication

Revision 202011-09-19 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 6 to 6
 

1 Introduction

Changed:
<
<
The Glue 2.0 specification is available here.
>
>
The Glue 2.0 specification document is available here.
 
Added:
>
>
The Glue 2.0 specification can also be found here.
 
Added:
>
>
The GLUE v. 2.0 Reference Implementation of an LDAP Schema document can be found here.

Glue 2.0 schema in SVN

 

1 Target scenario

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

Revision 182011-09-16 - MassimoSgaravatto

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

Glue2 support in CREAM

CREAM CE provided with EMI-1 provides some initial support for glue2, that needs to be finalized

Added:
>
>

1 Introduction

The Glue 2.0 specification is available here.

 

1 Target scenario

Added:
>
>

0.1 Objectclasses

This section reports the most significant information concerning the implementation of the Glue 2 objectclasses wrt the CREAM CE

0.1.1 ComputingService

  • GLUE2ServiceID is the value ComputingServiceId in /etc/glite-ce-glue2/glite-ce-glue2.conf. This value is the one specified by the yaim variable COMPUTING_SERVICE_ID, if specified (this variable is mandatory in cluster mode, see below). Otherwise it is ${CE_HOST}_ComputingElement
  • GLUE2ServiceCapability is executionmanagement.jobexecution
  • GLUE2ServiceType is org.glite.ce.CREAM
  • GLUE2ServiceAdminDomainForeignKey is the value of SiteId in /etc/glite-ce-glue2/glite-ce-glue2.conf. This value is the one specified by the yaim variable SITE_NAME

0.1.2 ComputingEndpoint

TBD

0.1.3 ComputingShare

A ComputingShare corresponds to a Glue1 VOView.

If needed, besides the VOViews we will also represent batch system queues as ComputingShares (this will have some impact on the WMS matchmaker)

TBC

0.1.4 ComputingManager

TBD

0.1.5 Benchmark

TBD

0.1.6 ExecutionEnvironment

TBD

0.1.7 ApplicationEnvironment

TBD

0.1.8 ApplicationHandle

TBD

0.1.9 ComputingActivity

We don't implement the ComputingActivity objectclass, since we don't publish information regarding jobs

0.1.10 ToStorageService

TBD

 

0.1 CREAM CE in no cluster mode

We assume that a CREAM CE is configured in cluster mode if that is the only CREAM CE available in the site. I.e. sites with multiple CREAM CEs (submitting to the same batch system) should always have a cluster node and therefore be configured in cluster mode.

Line: 152 to 209
 

0.1 SGE

Added:
>
>
TBD
 

0.1 Work to be done to support Glue2 publication

Line: 159 to 218
 
  • 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)
Changed:
<
<
>
>
    • For all the ComputingShares referring to that batch system queue
 
  • The value published in Glue1 as GlueCEPolicyMaxWallClockTime should be published in Glue2 as MaxWallTime (ComputingShare objectclass)
Changed:
<
<
* For all the ComputingShares referring to that batch system queue
  • The value published in Glue1 as GlueCEPolicyAssignedJobSlots should be published in Glue2 as ??? Nowhere ??
>
>
* For all the ComputingShares referring to that batch system queue
 
  • The value published in Glue1 as GlueCEStateStatus should be published in Glue2 as ServingState (ComputingShare objectclass)
Changed:
<
<
* 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 ??
>
>
    • For all the ComputingShares referring to that batch system queue

 
Line: 174 to 231
 
  • 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)
Changed:
<
<
>
>
    • For all the ComputingShares referring to that batch system queue
 
  • The value published in Glue1 as GlueCEPolicyMaxWallClockTime should be published in Glue2 as MaxWallTime (ComputingShare objectclass)
Changed:
<
<
>
>
    • For all the ComputingShares referring to that batch system queue
 
  • 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 ???
    • But the same value is published by the generic provider ...
>
>
    • For all the ComputingShares referring to that batch system queue
 
  • 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 ?? 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 ...
  • The value published in Glue1 as GlueCEPolicyPriority should be published in Glue2 as ??? Nowhere ??
>
>
    • For all the ComputingShares referring to that batch system queue
 

0.0.1 Work to be done in the generic dynamic scheduler

Deleted:
<
<
  • 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 ...
  • 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 ...
 
  • 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)
Line: 208 to 250
 
  • 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)
Added:
>
>

0.0.1 Work to be done in the SGE information provider

 
Added:
>
>
TBD
 

1 Relevant RFCs

Revision 172011-09-16 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 219 to 219
 
Added:
>
>

1 Testbed

The following machines are being used for testing

  • cream-38.pd.infn.it (Torque)
  • cream-29.pd.infn.it (LSF)
  -- MassimoSgaravatto - 2011-06-21 \ No newline at end of file

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)
 

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

Revision 142011-09-14 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 78 to 78
 GlueCEStateStatus: Production
Changed:
<
<
The dynamic scheduler plugin, for Glue1 publishes for each VOView something like:
>
>
The generic dynamic scheduler plugin, for Glue1 publishes for each VOView something like:
 
dn: GlueVOViewLocalID=alice,GlueCEUniqueID=cream-38.pd.infn.it:8443/cream-pbs-creamtest1,mds-vo-name=resource,o=grid
Line: 124 to 124
 
Changed:
<
<
The dynamic scheduler plugin, for Glue1 publishes for each VOView something like:
>
>
The generic dynamic scheduler plugin, for Glue1 publishes for each VOView something like:
 
dn: GlueVOViewLocalID=alice,GlueCEUniqueID=cream-29.pd.infn.it:8443/cream-lsf-creamcert1,mds-vo-name=resource,o=grid
Line: 153 to 153
 

0.1 SGE

Added:
>
>

0.1 Work to be done to support Glue2 publication

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

0.1.2 Work to be done in the LSF information provider

0.1.3 Work to be done in the generic dynamic scheduler

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)

 

1 Relevant RFCs

Revision 132011-09-14 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 58 to 58
 
  • The ServiceId is the the one specified by the yaim variable COMPUTING_SERVICE_ID which is such scenario is mandatory. This variable must have the same value in all the relevant nodes (in the cluster node and in all the CREAM CEs)
Changed:
<
<
The EndpointId! is hostname + "_org.glite.ce.CREAM".
>
>
The EndpointId is hostname + "_org.glite.ce.CREAM".

1 Batch system dynamic information

1.1 Torque/PBS

The PBS dynamic plugin for Glue1 publishes for each batch system queue something like:

dn: GlueCEUniqueID=cream-38.pd.infn.it:8443/cream-pbs-creamtest1,mds-vo-name=resource,o=grid
GlueCEInfoLRMSVersion: 2.5.7
GlueCEInfoTotalCPUs: 5
GlueCEPolicyAssignedJobSlots: 5
GlueCEStateFreeCPUs: 5
GlueCEPolicyMaxCPUTime: 2880
GlueCEPolicyMaxWallClockTime: 4320
GlueCEStateStatus: Production

The dynamic scheduler plugin, for Glue1 publishes for each VOView something like:

dn: GlueVOViewLocalID=alice,GlueCEUniqueID=cream-38.pd.infn.it:8443/cream-pbs-creamtest1,mds-vo-name=resource,o=grid
GlueVOViewLocalID: alice
GlueCEStateRunningJobs: 0
GlueCEStateWaitingJobs: 0
GlueCEStateTotalJobs: 0
GlueCEStateFreeJobSlots: 5
GlueCEStateEstimatedResponseTime: 0
GlueCEStateWorstResponseTime: 0

and for each queue publishes something like:

dn: GlueCEUniqueID=cream-38.pd.infn.it:8443/cream-pbs-creamtest1,mds-vo-name=resource,o=grid
GlueCEStateFreeJobSlots: 5
GlueCEStateFreeCPUs: 5
GlueCEStateRunningJobs: 0
GlueCEStateWaitingJobs: 0
GlueCEStateTotalJobs: 0
GlueCEStateEstimatedResponseTime: 0
GlueCEStateWorstResponseTime: 0

1.2 LSF

The LSF dynamic plugin for Glue1 publishes for each batch system queue something like:

dn: GlueCEUniqueID=cream-29.pd.infn.it:8443/cream-lsf-creamcert2,mds-vo-name=resource,o=grid
GlueCEInfoLRMSVersion: 7 Update 5
GlueCEInfoTotalCPUs: 216
GlueCEPolicyAssignedJobSlots: 216
GlueCEPolicyMaxRunningJobs: 216
GlueCEPolicyMaxCPUTime: 9999999999
GlueCEPolicyMaxWallClockTime: 9999999999
GlueCEPolicyPriority: -20
GlueCEStateFreeCPUs: 6
GlueCEStateFreeJobSlots: 216
GlueCEStateStatus: Production

The dynamic scheduler plugin, for Glue1 publishes for each VOView something like:

dn: GlueVOViewLocalID=alice,GlueCEUniqueID=cream-29.pd.infn.it:8443/cream-lsf-creamcert1,mds-vo-name=resource,o=grid
GlueVOViewLocalID: alice
GlueCEStateRunningJobs: 0
GlueCEStateWaitingJobs: 0
GlueCEStateTotalJobs: 0
GlueCEStateFreeJobSlots: 216
GlueCEStateEstimatedResponseTime: 0
GlueCEStateWorstResponseTime: 0

and for each queue publishes something like:

dn: GlueCEUniqueID=cream-29.pd.infn.it:8443/cream-lsf-creamcert1,mds-vo-name=resource,o=grid
GlueCEStateFreeJobSlots: 216
GlueCEStateFreeCPUs: 216
GlueCEStateRunningJobs: 0
GlueCEStateWaitingJobs: 0
GlueCEStateTotalJobs: 0
GlueCEStateEstimatedResponseTime: 0
GlueCEStateWorstResponseTime: 0

1.3 SGE

 

1 Relevant RFCs

Revision 122011-09-12 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 67 to 67
 
Added:
>
>
 

-- MassimoSgaravatto - 2011-06-21 \ No newline at end of file

Revision 112011-09-08 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 62 to 62
 

1 Relevant RFCs

Added:
>
>
 
Added:
>
>
 
Added:
>
>
 -- MassimoSgaravatto - 2011-06-21 \ No newline at end of file

Revision 102011-07-28 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 14 to 14
  These objectclasses are:
Changed:
<
<
  • ComputingService
  • ComputingEndPoint
  • AccessPolicy
  • ComputingManager
  • ComputingShare
  • MappingPolicy
  • ExecutionEnvironment
  • Benchmark
  • ToStorageService
  • ApplicationEnvironment
  • EndPoint for RTEPublihser
>
>
  • ComputingService (done)
  • ComputingEndPoint (done)
  • AccessPolicy (done)
  • ComputingManager (done)
  • ComputingShare (done)
  • MappingPolicy (done)
  • ExecutionEnvironment (done)
  • Benchmark (done)
  • ToStorageService (done)
  • ApplicationEnvironment (todo)
  • EndPoint for RTEPublihser (done)
 
    • "Child" of ComputingService
Changed:
<
<
  • EndPoint for CEMon
>
>
  • EndPoint for CEMon (done)
 
    • "Child" of ComputingService
    • Published only if CEMon is deployed
Line: 42 to 42
 If a CREAM CE is configured in cluster mode:

  • The resource BDII running on the CREAM CE publishes just the following objectclasses:
Changed:
<
<
    • ComputingEndpoint
    • AccessPolicy
>
>
    • ComputingEndpoint (done)
    • AccessPolicy (done)
 
  • All the other objectclasses are published by the resource BDII running on the gLite-CLUSTER node:
    • ComputingService (done)
    • ComputingManager (done)
Line: 51 to 51
 
    • MappingPolicy (todo)
    • ExecutionEnvironment (done)
    • Benchmark (done)
Changed:
<
<
    • ToStorageService (todo)
>
>
    • ToStorageService (done)
 
    • ApplicationEnvironment (todo)
Changed:
<
<
    • EndPoint for RTEPublihser (todo)
>
>
    • EndPoint for RTEPublihser (done)
 
      • "Child" of ComputingService

  • The ServiceId is the the one specified by the yaim variable COMPUTING_SERVICE_ID which is such scenario is mandatory. This variable must have the same value in all the relevant nodes (in the cluster node and in all the CREAM CEs)

Revision 92011-07-28 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 30 to 30
 
    • "Child" of ComputingService
    • Published only if CEMon is deployed
Changed:
<
<
The ComputingServiceId is the one specified by the yaim variable COMPUTING_SERVICE_ID (if specified). Otherwise it is ${CE_HOST}_ComputingElement.
>
>
The ComputingServiceId is the one specified by the yaim variable COMPUTING_SERVICE_ID (if specified). Otherwise it is ${CE_HOST}_ComputingElement..

The EndpointId! is hostname + "_org.glite.ce.CREAM".

 

0.1 CREAM CE in cluster mode

Line: 53 to 56
 
    • EndPoint for RTEPublihser (todo)
      • "Child" of ComputingService

Changed:
<
<
  • The ServiceId is the the one specified by the yaim variable COMPUTING_SERVICE_ID which is such scenario is mandatory. This variable must have the same value in all the relevant nodes (in the cluster node and in all the CREAM CEs)
>
>
  • The ServiceId is the the one specified by the yaim variable COMPUTING_SERVICE_ID which is such scenario is mandatory. This variable must have the same value in all the relevant nodes (in the cluster node and in all the CREAM CEs)

The EndpointId! is hostname + "_org.glite.ce.CREAM".

 

1 Relevant RFCs

Revision 82011-07-27 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 47 to 47
 
    • ComputingShare (todo)
    • MappingPolicy (todo)
    • ExecutionEnvironment (done)
Changed:
<
<
    • Benchmark (todo)
>
>
    • Benchmark (done)
 
    • ToStorageService (todo)
    • ApplicationEnvironment (todo)
    • EndPoint for RTEPublihser (todo)

Revision 72011-07-27 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 42 to 42
 
    • ComputingEndpoint
    • AccessPolicy
  • All the other objectclasses are published by the resource BDII running on the gLite-CLUSTER node:
Changed:
<
<
    • ComputingService
    • ComputingManager

    • ComputingShare
    • MappingPolicy
    • ExecutionEnvironment
    • Benchmark
    • ToStorageService
    • ApplicationEnvironment
    • EndPoint for RTEPublihser
>
>
    • ComputingService (done)
    • ComputingManager (done)
    • ComputingShare (todo)
    • MappingPolicy (todo)
    • ExecutionEnvironment (done)
    • Benchmark (todo)
    • ToStorageService (todo)
    • ApplicationEnvironment (todo)
    • EndPoint for RTEPublihser (todo)
 
      • "Child" of ComputingService

  • The ServiceId is the the one specified by the yaim variable COMPUTING_SERVICE_ID which is such scenario is mandatory. This variable must have the same value in all the relevant nodes (in the cluster node and in all the CREAM CEs)

Revision 62011-07-26 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 9 to 8
 

0.1 CREAM CE in no cluster mode

Changed:
<
<
We assume that a CREAM CE is configured in cluster mode if that is the only CREAM CE available in the site. I.e. sites with multiple CREAM CEs (submitting to the same batch system) should always have a cluster node and therefore be configured in cluster mode.
>
>
We assume that a CREAM CE is configured in cluster mode if that is the only CREAM CE available in the site. I.e. sites with multiple CREAM CEs (submitting to the same batch system) should always have a cluster node and therefore be configured in cluster mode.
  If a CREAM CE is configured in no cluster mode, all the Glue2 object classes are published by the resource BDII running on the CREAM CE.
Line: 42 to 38
  If a CREAM CE is configured in cluster mode:
Changed:
<
<
  • The resource BDII running on the CREAM CE publishes just the Endpoint and the AccessPolicy objectclasses
  • All the other objectclasses are published by the resource BDII running on the gLite-CLUSTER node
  • The ServiceId is the the one specified by the yaim variable COMPUTING_SERVICE_ID which is such scenario is mandatory. This variable must have the same value in all the relevant nodes (in the cluster node and in all the CREAM CEs)
>
>
  • The resource BDII running on the CREAM CE publishes just the following objectclasses:
    • ComputingEndpoint
    • AccessPolicy
  • All the other objectclasses are published by the resource BDII running on the gLite-CLUSTER node:
    • ComputingService
    • ComputingManager

    • ComputingShare
    • MappingPolicy
    • ExecutionEnvironment
    • Benchmark
    • ToStorageService
    • ApplicationEnvironment
    • EndPoint for RTEPublihser
      • "Child" of ComputingService
 
Added:
>
>
  • The ServiceId is the the one specified by the yaim variable COMPUTING_SERVICE_ID which is such scenario is mandatory. This variable must have the same value in all the relevant nodes (in the cluster node and in all the CREAM CEs)
 

1 Relevant RFCs

Revision 52011-06-22 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 14 to 14
  If a CREAM CE is configured in no cluster mode, all the Glue2 object classes are published by the resource BDII running on the CREAM CE.
Changed:
<
<
The ServiceId is the one specified by the yaim variable COMPUTING_SERVICE_ID (if specified). Otherwise it is ${CE_HOST}_ComputingElement.
>
>
These objectclasses are:

  • ComputingService
  • ComputingEndPoint
  • AccessPolicy
  • ComputingManager
  • ComputingShare
  • MappingPolicy
  • ExecutionEnvironment
  • Benchmark
  • ToStorageService
  • ApplicationEnvironment
  • EndPoint for RTEPublihser
    • "Child" of ComputingService
  • EndPoint for CEMon
    • "Child" of ComputingService
    • Published only if CEMon is deployed

The ComputingServiceId is the one specified by the yaim variable COMPUTING_SERVICE_ID (if specified). Otherwise it is ${CE_HOST}_ComputingElement.

 

0.1 CREAM CE in cluster mode

Line: 28 to 47
 
  • The ServiceId is the the one specified by the yaim variable COMPUTING_SERVICE_ID which is such scenario is mandatory. This variable must have the same value in all the relevant nodes (in the cluster node and in all the CREAM CEs)
Added:
>
>

1 Relevant RFCs

 -- MassimoSgaravatto - 2011-06-21 \ No newline at end of file

Revision 42011-06-22 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 9 to 9
 

0.1 CREAM CE in no cluster mode

Changed:
<
<
If the CREAM CE is configured in no cluster mode, all the Glue2 object classes are published by the resource BDII running on the CREAM CE.
>
>
We assume that a CREAM CE is configured in cluster mode if that is the only CREAM CE available in the site. I.e. sites with multiple CREAM CEs (submitting to the same batch system) should always have a cluster node and therefore be configured in cluster mode.

If a CREAM CE is configured in no cluster mode, all the Glue2 object classes are published by the resource BDII running on the CREAM CE.

  The ServiceId is the one specified by the yaim variable COMPUTING_SERVICE_ID (if specified). Otherwise it is ${CE_HOST}_ComputingElement.

0.1 CREAM CE in cluster mode

Changed:
<
<
If instead the CREAM CE is configured in cluster mode:
>
>
Sites with multiple CREAM CEs (submitting to the same batch system) should always have a cluster node and therefore be configured in cluster mode.

If a CREAM CE is configured in cluster mode:

 
  • The resource BDII running on the CREAM CE publishes just the Endpoint and the AccessPolicy objectclasses
  • All the other objectclasses are published by the resource BDII running on the gLite-CLUSTER node
Changed:
<
<
>
>
  • The ServiceId is the the one specified by the yaim variable COMPUTING_SERVICE_ID which is such scenario is mandatory. This variable must have the same value in all the relevant nodes (in the cluster node and in all the CREAM CEs)
 

-- MassimoSgaravatto - 2011-06-21 \ No newline at end of file

Revision 32011-06-21 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 11 to 11
  If the CREAM CE is configured in no cluster mode, all the Glue2 object classes are published by the resource BDII running on the CREAM CE.
Changed:
<
<
The ServiceId is ${CE_HOST}_ComputingElement.
>
>
The ServiceId is the one specified by the yaim variable COMPUTING_SERVICE_ID (if specified). Otherwise it is ${CE_HOST}_ComputingElement.
 

0.1 CREAM CE in cluster mode

If instead the CREAM CE is configured in cluster mode:

Changed:
<
<
  • The resource BDII running on the CREAM CE shoudl publish just the Endpoint and the AccessPolicy objectclasses
  • All the other objectclasses should be published by the resource BDII running on the gLite-CLUSTER node
>
>
  • The resource BDII running on the CREAM CE publishes just the Endpoint and the AccessPolicy objectclasses
  • All the other objectclasses are published by the resource BDII running on the gLite-CLUSTER node
 
Deleted:
<
<

1 Items that need to be done/fixed:

 -- MassimoSgaravatto - 2011-06-21

Revision 22011-06-21 - MassimoSgaravatto

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

Glue2 support in CREAM

Line: 10 to 11
  If the CREAM CE is configured in no cluster mode, all the Glue2 object classes are published by the resource BDII running on the CREAM CE.
Added:
>
>
The ServiceId is ${CE_HOST}_ComputingElement.
 

0.1 CREAM CE in cluster mode

Line: 20 to 23
 
Changed:
<
<

0.1 Items that need to be done/fixed:

>
>

1 Items that need to be done/fixed:

 

Revision 12011-06-21 - MassimoSgaravatto

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

Glue2 support in CREAM

CREAM CE provided with EMI-1 provides some initial support for glue2, that needs to be finalized

1 Target scenario

1.1 CREAM CE in no cluster mode

If the CREAM CE is configured in no cluster mode, all the Glue2 object classes are published by the resource BDII running on the CREAM CE.

1.2 CREAM CE in cluster mode

If instead the CREAM CE is configured in cluster mode:

  • The resource BDII running on the CREAM CE shoudl publish just the Endpoint and the AccessPolicy objectclasses
  • All the other objectclasses should be published by the resource BDII running on the gLite-CLUSTER node

1.3 Items that need to be done/fixed:

-- MassimoSgaravatto - 2011-06-21

 
This site is powered by the TWiki collaboration platformCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback