Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Glue2 support in CREAM | ||||||||
Changed: | ||||||||
< < | CREAM CE provided with EMI-1 provides some initial support for glue2, that needs to be finalized | |||||||
> > | CREAM CE provided with EMI-1 provides some initial support for glue2, that has been finalized in EMI-2 | |||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Glue2 support in CREAM | ||||||||
Line: 451 to 451 | ||||||||
| ||||||||
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) | |||||||
| ||||||||
Line: 463 to 463 | ||||||||
| ||||||||
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) | |||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Glue2 support in CREAM | ||||||||
Line: 430 to 430 | ||||||||
0.0.1 Work to be done in the PBS/Torque information provider (done)
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
0.0.1 Work to be done in the LSF information provider (done)
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Line: 451 to 454 | ||||||||
0.0.1 Work to be done in the SGE information provider
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Glue2 support in CREAM | ||||||||
Line: 68 to 68 | ||||||||
| ||||||||
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 | |||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
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) | |||||||
| ||||||||
Line: 434 to 434 | ||||||||
| ||||||||
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) | |||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Glue2 support in CREAM | ||||||||
Line: 93 to 93 | ||||||||
0.0.1 ComputingEndpoint
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Line: 118 to 119 | ||||||||
| ||||||||
Changed: | ||||||||
< < | Todo: start time ? | |||||||
> > | ||||||||
0.0.0.1 Policy for the ComputingEndPoint |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Glue2 support in CREAM | ||||||||
Line: 110 to 110 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
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 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Glue2 support in CREAM | ||||||||
Line: 485 to 485 | ||||||||
| ||||||||
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 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Glue2 support in CREAM | ||||||||
Line: 36 to 36 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Line: 64 to 64 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
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.
| |||||||
0.0.1 ApplicationHandle |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Glue2 support in CREAM | ||||||||
Line: 59 to 59 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Line: 145 to 144 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Line: 162 to 161 | ||||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Glue2 support in CREAM | ||||||||
Line: 143 to 143 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Line: 160 to 160 | ||||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < | TODO: link to computingendpoint | |||||||
> > | ||||||||
0.0.0.1 MappingPolicy for the ComputingShare
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Glue2 support in CREAM | ||||||||
Line: 157 to 157 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Line: 170 to 170 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
0.0.1 ComputingManager |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
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 | |||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Glue2 support in CREAM | ||||||||
Line: 247 to 247 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
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)
| |||||||
Added: | ||||||||
> > |
| |||||||
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
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.
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Line: 233 to 232 | ||||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
TBC | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > | ||||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Glue2 support in CREAM | ||||||||
Line: 28 to 28 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > | * AccessPolicy for ComputingEndPoint (done) | |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Line: 51 to 52 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Line: 59 to 60 | ||||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Line: 155 to 157 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > | 0.0.0.1 MappingPolicy for the ComputingEndPoint
| |||||||
0.0.1 ComputingManager | ||||||||
Line: 170 to 180 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
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: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < | TBD | |||||||
> > | ||||||||
0.0.1 ApplicationEnvironment |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Glue2 support in CREAM | ||||||||
Line: 68 to 68 | ||||||||
| ||||||||
Changed: | ||||||||
< < | The EndpointId is hostname + "_org.glite.ce.CREAM" . | |||||||
> > | ||||||||
0.1 Objectclasses | ||||||||
Line: 94 to 94 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
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. | |||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Glue2 support in CREAM | ||||||||
Line: 69 to 69 | ||||||||
hostname + "_org.glite.ce.CREAM" . | ||||||||
Changed: | ||||||||
< < | xxx | |||||||
> > | ||||||||
0.1 Objectclasses | ||||||||
Line: 84 to 84 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
0.0.1 ComputingEndpoint | ||||||||
Line: 115 to 117 | ||||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
Todo: start time ?
0.0.0.1 Policy for the Computing EndPoint | ||||||||
Line: 127 to 131 | ||||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
0.0.1 ComputingShare | ||||||||
Line: 149 to 154 | ||||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
TODO: link to computingendpoint | ||||||||
Line: 234 to 245 | ||||||||
1 Batch system dynamic information | ||||||||
Changed: | ||||||||
< < | 0.1 Torque/PBS | |||||||
> > | 0.1 Current Glue 1 scenario0.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: 0and 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: 0and 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 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Glue2 support in CREAM | ||||||||
Line: 18 to 18 | ||||||||
1 Target scenario | ||||||||
Added: | ||||||||
> > | 0.1 CREAM CE in no cluster modeWe 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:
0.2 CREAM CE in cluster modeSites 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:
hostname + "_org.glite.ce.CREAM" .
xxx | |||||||
0.1 ObjectclassesThis section reports the most significant information concerning the implementation of the Glue 2 objectclasses wrt the CREAM CE0.1.1 ComputingService | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Line: 175 to 228 | ||||||||
TBD | ||||||||
Deleted: | ||||||||
< < | 0.1 CREAM CE in no cluster modeWe 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:
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 modeSites 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: | ||||||||
< < |
| |||||||
Deleted: | ||||||||
< < |
hostname + "_org.glite.ce.CREAM" . | |||||||
1 Batch system dynamic information | ||||||||
Line: 415 to 421 | ||||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
-- MassimoSgaravatto - 2011-06-21 \ No newline at end of file |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Glue2 support in CREAM | ||||||||
Line: 97 to 97 | ||||||||
| ||||||||
Added: | ||||||||
> > | TODO: link to computingendpoint | |||||||
0.0.1 ComputingManager |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
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
| |||||||
TBD
0.0.1 ApplicationEnvironment |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
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 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Line: 37 to 36 | ||||||||
0.0.1 ComputingEndpoint | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Line: 55 to 54 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
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 | |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Deleted: | ||||||||
< < | Todo: start time ? | |||||||
0.0.1 ComputingShareA 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 | |||||||
> > |
| |||||||
0.0.1 ComputingManager | ||||||||
Changed: | ||||||||
< < | TBD | |||||||
> > |
| |||||||
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:
| |||||||
0.0.1 ExecutionEnvironment | ||||||||
Line: 312 to 349 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Deleted: | ||||||||
< < | ||||||||
0.0.1 Work to be done in the LSF information provider
| ||||||||
Line: 347 to 379 | ||||||||
0.0.1 Work to be done in the generic dynamic scheduler | ||||||||
Deleted: | ||||||||
< < | ||||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Glue2 support in CREAM | ||||||||
Line: 48 to 48 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
0.0.0.1 Policy for the Computing EndPointFor each ComputingEndpoint, there are as many as policies as the policy rules that must be defined
| |||||||
0.0.1 ComputingShare |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Glue2 support in CREAM | ||||||||
Line: 26 to 26 | ||||||||
0.0.1 ComputingService
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
0.0.1 ComputingEndpoint | ||||||||
Added: | ||||||||
> > |
| |||||||
TBD
0.0.1 ComputingShare |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Glue2 support in CREAMCREAM CE provided with EMI-1 provides some initial support for glue2, that needs to be finalized | ||||||||
Added: | ||||||||
> > |
| |||||||
1 IntroductionThe 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 | ||||||||
| ||||||||
Added: | ||||||||
> > | 0.0.1 Work to be done in the SGE information provider
| |||||||
0.0.1 Work to be done in the generic dynamic scheduler | ||||||||
Line: 278 to 311 | ||||||||
| ||||||||
Deleted: | ||||||||
< < | 0.0.1 Work to be done in the SGE information provider | |||||||
Deleted: | ||||||||
< < | TBD | |||||||
1 Relevant RFCs |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
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: ProductionThe 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 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
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 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Glue2 support in CREAM | ||||||||
Line: 216 to 216 | ||||||||
0.0.1 Work to be done in the PBS/Torque information provider | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
* For all the ComputingShares referring to that batch system queue | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Line: 229 to 229 | ||||||||
0.0.1 Work to be done in the LSF information provider | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
0.0.1 Work to be done in the generic dynamic scheduler | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
0.0.1 Work to be done in the SGE information provider |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Glue2 support in CREAMCREAM CE provided with EMI-1 provides some initial support for glue2, that needs to be finalized | ||||||||
Added: | ||||||||
> > | 1 IntroductionThe Glue 2.0 specification is available here. | |||||||
1 Target scenario | ||||||||
Added: | ||||||||
> > | 0.1 ObjectclassesThis section reports the most significant information concerning the implementation of the Glue 2 objectclasses wrt the CREAM CE0.1.1 ComputingService
0.1.2 ComputingEndpointTBD0.1.3 ComputingShareA 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) TBC0.1.4 ComputingManagerTBD0.1.5 BenchmarkTBD0.1.6 ExecutionEnvironmentTBD0.1.7 ApplicationEnvironmentTBD0.1.8 ApplicationHandleTBD0.1.9 ComputingActivityWe don't implement the ComputingActivity objectclass, since we don't publish information regarding jobs0.1.10 ToStorageServiceTBD | |||||||
0.1 CREAM CE in no cluster modeWe 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 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < | * For all the ComputingShares referring to that batch system queue
| |||||||
> > | * For all the ComputingShares referring to that batch system queue | |||||||
| ||||||||
Changed: | ||||||||
< < | * For all the ComputingShares referring to that batch system queue
| |||||||
> > |
| |||||||
Line: 174 to 231 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
0.0.1 Work to be done in the generic dynamic scheduler | ||||||||
Deleted: | ||||||||
< < |
| |||||||
| ||||||||
Line: 208 to 250 | ||||||||
| ||||||||
Added: | ||||||||
> > | 0.0.1 Work to be done in the SGE information provider | |||||||
Added: | ||||||||
> > | TBD | |||||||
1 Relevant RFCs |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Glue2 support in CREAM | ||||||||
Line: 219 to 219 | ||||||||
Added: | ||||||||
> > | 1 TestbedThe following machines are being used for testing
| |||||||
-- MassimoSgaravatto - 2011-06-21 \ No newline at end of file |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Glue2 support in CREAM | ||||||||
Line: 159 to 159 | ||||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > | * For all the ComputingShares referring to that batch system queue
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > | * For all the ComputingShares referring to that batch system queue
| |||||||
Line: 171 to 174 | ||||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
0.0.1 Work to be done in the generic dynamic scheduler | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Glue2 support in CREAM | ||||||||
Line: 157 to 157 | ||||||||
0.0.1 Work to be done in the PBS/Torque information provider | ||||||||
Added: | ||||||||
> > |
| |||||||
0.0.1 Work to be done in the LSF information provider | ||||||||
Added: | ||||||||
> > |
| |||||||
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) | |||||||
> > |
| |||||||
1 Relevant RFCs |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
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 publication0.1.1 Work to be done in the PBS/Torque information provider0.1.2 Work to be done in the LSF information provider0.1.3 Work to be done in the generic dynamic schedulerGlueCEInfoLRMSVersion (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 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Glue2 support in CREAM | ||||||||
Line: 58 to 58 | ||||||||
| ||||||||
Changed: | ||||||||
< < | The EndpointId! is hostname + "_org.glite.ce.CREAM". | |||||||
> > | The EndpointId is hostname + "_org.glite.ce.CREAM" .
1 Batch system dynamic information1.1 Torque/PBSThe 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: ProductionThe 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: 0and 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 LSFThe 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: ProductionThe 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: 0and 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 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Glue2 support in CREAM | ||||||||
Line: 67 to 67 | ||||||||
Added: | ||||||||
> > | ||||||||
-- MassimoSgaravatto - 2011-06-21 \ No newline at end of file |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Glue2 support in CREAM | ||||||||
Line: 62 to 62 | ||||||||
1 Relevant RFCs | ||||||||
Added: | ||||||||
> > | ||||||||
Added: | ||||||||
> > | ||||||||
Added: | ||||||||
> > | ||||||||
-- MassimoSgaravatto - 2011-06-21 \ No newline at end of file |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Glue2 support in CREAM | ||||||||
Line: 14 to 14 | ||||||||
These objectclasses are: | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Line: 42 to 42 | ||||||||
If a CREAM CE is configured in cluster mode:
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Line: 51 to 51 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Glue2 support in CREAM | ||||||||
Line: 30 to 30 | ||||||||
| ||||||||
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 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
1 Relevant RFCs |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Glue2 support in CREAM | ||||||||
Line: 47 to 47 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Glue2 support in CREAM | ||||||||
Line: 42 to 42 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
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: | ||||||||
< < |
| |||||||
> > |
| |||||||
Added: | ||||||||
> > |
| |||||||
1 Relevant RFCs |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
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:
COMPUTING_SERVICE_ID (if specified). Otherwise it is ${CE_HOST}_ComputingElement . | |||||||
0.1 CREAM CE in cluster mode | ||||||||
Line: 28 to 47 | ||||||||
| ||||||||
Added: | ||||||||
> > | 1 Relevant RFCs | |||||||
-- MassimoSgaravatto - 2011-06-21 \ No newline at end of file |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
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: | |||||||
| ||||||||
Changed: | ||||||||
< < | ||||||||
> > |
| |||||||
-- MassimoSgaravatto - 2011-06-21 \ No newline at end of file |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
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 modeIf instead the CREAM CE is configured in cluster mode: | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Deleted: | ||||||||
< < | 1 Items that need to be done/fixed: | |||||||
-- MassimoSgaravatto - 2011-06-21 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
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: | |||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Added: | ||||||||
> > |
Glue2 support in CREAMCREAM CE provided with EMI-1 provides some initial support for glue2, that needs to be finalized1 Target scenario1.1 CREAM CE in no cluster modeIf 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 modeIf instead the CREAM CE is configured in cluster mode:
1.3 Items that need to be done/fixed: |