
Hi, I have updated the glue-schema package and the BDII to use GLUE2.0. If any one is interested the packages can be found at the following URLs. http://etics-repository.cern.ch:8080/repository/download/registered/org.glit... http://etics-repository.cern.ch:8080/repository/download/registered/org.glit... An instance with the examples has been installed on glue-bdii.cern.ch ldapsearch -x -h glue-bdii -p 2170 -b o=glue It it currently under testing and if all goes smoothly we will submit an EGEE patch on Monday to include it in the gLite release. Laurence

Hi Laurence,
http://etics-repository.cern.ch:8080/repository/download/registered/org.glit...
I ran a spell checker over /opt/glue/schema/openldap-2.1/GLUE20.schema and found these issues: LRMS<E2> dedicated<E2> job<E2> storge The first 3 indicate the presence of control characters, as far as ASCII is concerned, e.g. UTF-8. Indeed: ---------------------------------------------------------------------- $ cat -v GLUE20.schema | grep -i "LRMS[^. );'][^a-z]" | fold -w 70 DESC 'Number of jobs waiting in the underlying computing manag ers (i.e., Local Resource Manager System or LRMSM-bM-^@M-^Ys) ' DESC 'Number of jobs waiting in the underlying computing manag ers (i.e., Local Resource Manager System or LRMSM-bM-^@M-^Ys) ' DESC 'Number of jobs waiting in the underlying computing manag ers (i.e., LRMSM-bM-^@M-^Ys) submitted via any type of interface (loca l and Grid)' DESC 'Number of jobs waiting in the underlying computing manag ers (i.e., LRMSM-bM-^@M-^Ys) submitted via a local interface' ---------------------------------------------------------------------- $ cat -v GLUE20.schema | grep -i "dedicated[^. );']" | fold -w 70 DESC 'Local ID common to the storage shares which use the same storage share capacities (M-bM-^@M-^XdedicatedM-bM-^@M-^Y is a reserv ed term and means that the storage share capacities are not shared wit h other storage share capacities part of different storage shares)' ---------------------------------------------------------------------- $ cat -v GLUE20.schema | grep "job[^s. );']" | fold -w 70 DESC 'The Grid identity of the jobM-bM-^@M-^Ys owner; in case of anonymity is required, the value CONFIDENTIAL should be advertised' DESC 'The local user name to which the jobM-bM-^@M-^Ys owner is mapped into' ---------------------------------------------------------------------- I think the file should only contain standard ASCII characters. Next: ---------------------------------------------------------------------- $ grep storge GLUE20.schema | fold -w 70 DESC 'Abstracted of a sufficiently homogeneous storage device providing a storage capacity, managed by a local software component (s torage manager), part of a storage service, reachable via one or more endpoints and having one or more shares defined on it. A storge resour ce refers to a category with summary information on the capacity' ---------------------------------------------------------------------- Furthermore, in that last item "Abstracted" should be "Abstraction" and what does that last sentence mean? Also, 3 other items use "homogenous" instead of "homogeneous". We should check the contents of all descriptions... Thanks, Maarten

Laurence Field wrote:
http://etics-repository.cern.ch:8080/repository/download/registered/org.glit...
I also do not like the very long lines in GLUE20.schema: the longest has 1702 characters! Does an LDAP schema have a way to fold lines?

I have justed checked and we can wrap lines in the schema files. Laurence Maarten Litmaath wrote:
Laurence Field wrote:
http://etics-repository.cern.ch:8080/repository/download/registered/org.glit...
I also do not like the very long lines in GLUE20.schema: the longest has 1702 characters!
Does an LDAP schema have a way to fold lines?
participants (2)
-
Laurence Field
-
Maarten Litmaath