, view all tags
The aim of this topic is to describe which BDII information is taken into account and how that information is composed to create the classad representation insertend in ISM, namely used while the WMS performs the matchmaking.

The current gLite 3.1 version of the bdii purchaser acquires information about computing resources by querying the BDII for the following objectclasses:

  • gluecesebind
  • gluece
  • gluevoview
  • gluecluster
  • gluesubcluster

A prototype version of the gLite 3.1 bdii purchaser has been patched in order to support gluelocation information (task 6650)


Describes the association class between a computing element (CE) and storage elements (SE). The bind information is inserted in the classad representing the computing element as a list:

GlueCESEBindGroupSEUniqueID =

In order to require that the computing element eligible for executing the job at is bound to a given storage element, the user should use the classad member function while defining the requirement expression within the relevant JDL:

requirements = member(other.GlueCESEBindGroupSEUniqueID , "se01.somewhere.in_the.world");


A cluster is an aggregation entity for representing a complex computing resource in terms of the SubCluster and Computing Element entities. A cluster is a heterogeneous set of resources.

All the attributes beloging to this objectclass are flattened, mantaining the same name (GlueCluster*) into the classad representation of the relevant CE.


The SubCluster entity provides details of a homogeneous set of hosts as regards the selected attributes. Host entities within the SubCluster provide the set which describes the charactheristics of the resources belonging to the subcluster:

All the attributes beloging to these objectclasses are flattened, mantaining the same name (GlueSubcluster*, GlueHost*) into the classad representation of the relevant CE. In order to match such attributes, at matchmaking time, the user should refers to them by symply adding the classad attribute reference other. followed by the name of the attribute as published in the objectclass it belongs to:

requiremts = other.GlueHostMainMemoryRAMSize > 2048;

It should be reminded that an attribute defaults to multivalued unless it is explicitly made single-valued, that is, by adding the SINGLE-VALUE keyword after the SYNTAX section in the schema specification. Multivalued attributes such as GlueHostApplicationSoftwareRuntimeEnvironment are represented in classad as lists, and thus, in order to match a given value, the user should use the classad member function:

requiremts = member(other.GlueHostApplicationSoftwareRuntimeEnvironment, "GLITE-3_1_0");


Provides a set of attributes which describe the static characteristics (GlueCEInfo*), a status changing frequently (GlueCEState*), a general use policy (GlueCEPolicy*), a set of authorized users or groups (GlueCEAccessControlBase*). The entities Info, State, Policy and AccessControlBase were present in the first GLUE Schema as individual objectclasses, then they have been merged into the gluece. For backward compatibility, at LDIF representation level, the entity name is included in the attribute name in order to enable the maintenance of a consistent mapping onto concrete data models.

All the attributes beloging to this objectclass are flattened, mantaining the same name (GlueCE*) into the classad representation of the relevant CE.


The gluevoview entity was meant for reporting the state information specific to a group or a virtual organization. Basically the attributes published within this objectclass are the same within gluece but assigned with different values.

For a given computing element all the VOView-related information is processed. In order to maintain the same space of authorization rules, the splitting of the classad representation of the CE into its "views" is performed by computing the set intersection of the GlueCEAccessControlBaseRules information: SET_INTERSECTION(.GlueCEACBR, .GlueCEACBR) where is the ClassAd representing the CE and is the i-th view defined for such a CE. Any ACBR which has not been mapped is inserted within an additional computing element classad in ISM.

All the attributes beloging to this objectclass mantaining the same name (GlueCE*) into the classad representation of the relevant CE.

-- SalvatoreMonforte - 20 May 2008

Edit | Attach | PDF | History: r2 < r1 | Backlinks | Raw View | More topic actions...
Topic revision: r1 - 2008-05-20 - SalvatoreMonforte
  • Edit
  • Attach
This site is powered by the TWiki collaboration platformCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback