Hi all, Yesterday I tested the changes mandated by the new version of the LDAP document in a test environment and I didn't see any issue. I didn't see any bad error in slapd logs, and the objects that were affected by changes are published as expected. I attach the latest schema and kindly ask Maria and Paul to test the impact on their products: GLUE20.schema.20140508 A list of diffs between the current distributed version of the schema (2.0rc5) against the new version (2.0rc6) that is included in this email: distro2.0rc5_diff_2.0rc6.changes I suggest you check them with some nice editor that colors things up so you can easily spot differences. I pushed the source schemas in my git-hub area temporarily, if we're fine with that I will push it to the official repos: https://github.com/floridop/LDAPWIP I would say that we should put recommendations in the release notes that I added in the README files on git-hub. I didn't do it yet, but the issues I can imagine we should add are the following: 1) ABSTRACT classes to be in sync with XML realisation: Objects like Entity, Resource, Share, Policy have been declared ABSTRACT to be in sync with the XML schema. This means these cannot be instantiated as is; only their specialization can (i.e. Computing- Storage- or others like Benchmark etc.) are objects that can be published. 2) Boolean type changed to DirectoryString This means that if the boolean values that are mandatory in the schema are not defined, the information providers MUST publish them and MUST present the value "undefinedvalue"; GFD.147 Appendix B.17. These are: ExecutionEnvironment.ConnectivityIn ExecutionEnvironment.ConnectivityOut If you spot any problem, let me know. Regards, Florido -- ================================================== Florido Paganelli ARC Middleware Developer - NorduGrid Collaboration System Administrator Lund University Department of Physics Division of Particle Physics BOX118 221 00 Lund Office Location: Fysikum, Hus B, Rum B313 Office Tel: 046-2220272 Email: florido.paganelli@REMOVE_THIShep.lu.se Homepage: http://www.hep.lu.se/staff/paganelli ==================================================
Hi Florido, Quite busy with other priorities in the next two weeks. I hope I can try this in June. I´ll keep you informed. Sorry, Maria
-----Original Message----- From: Florido Paganelli [mailto:florido.paganelli@hep.lu.se] Sent: 08 May 2014 17:58 To: Maria Alandes Pradillo; glue-wg@ogf.org; Paul Millar Subject: Progress on LDAP schema
Hi all,
Yesterday I tested the changes mandated by the new version of the LDAP document in a test environment and I didn't see any issue. I didn't see any bad error in slapd logs, and the objects that were affected by changes are published as expected.
I attach the latest schema and kindly ask Maria and Paul to test the impact on their products: GLUE20.schema.20140508
A list of diffs between the current distributed version of the schema (2.0rc5) against the new version (2.0rc6) that is included in this email: distro2.0rc5_diff_2.0rc6.changes
I suggest you check them with some nice editor that colors things up so you can easily spot differences.
I pushed the source schemas in my git-hub area temporarily, if we're fine with that I will push it to the official repos:
https://github.com/floridop/LDAPWIP
I would say that we should put recommendations in the release notes that I added in the README files on git-hub. I didn't do it yet, but the issues I can imagine we should add are the following:
1) ABSTRACT classes to be in sync with XML realisation: Objects like Entity, Resource, Share, Policy have been declared ABSTRACT to be in sync with the XML schema. This means these cannot be instantiated as is; only their specialization can (i.e. Computing- Storage- or others like Benchmark etc.) are objects that can be published.
2) Boolean type changed to DirectoryString This means that if the boolean values that are mandatory in the schema are not defined, the information providers MUST publish them and MUST present the value "undefinedvalue"; GFD.147 Appendix B.17. These are: ExecutionEnvironment.ConnectivityIn ExecutionEnvironment.ConnectivityOut
If you spot any problem, let me know.
Regards, Florido -- ================================================== Florido Paganelli ARC Middleware Developer - NorduGrid Collaboration System Administrator Lund University Department of Physics Division of Particle Physics BOX118 221 00 Lund Office Location: Fysikum, Hus B, Rum B313 Office Tel: 046-2220272 Email: florido.paganelli@REMOVE_THIShep.lu.se Homepage: http://www.hep.lu.se/staff/paganelli ==================================================
Dear all, Sorry for the late feedback on this. I finally managed to test the new LDAP schema version in the BDII. In principle I think it´s OK. I have compared for instance the number of DNs published with the old schema version and the new one, and there is a different of 100 DNs, which for the BDII could be in principle OK since there are many things getting published and deleted, it´s very dynamic. The number of sites is the same and also the number of endpoints is roughly the same. I don´t know what else I could test. Any ideas? Regards, Maria
-----Original Message----- From: Maria Alandes Pradillo Sent: 14 May 2014 11:53 To: Florido Paganelli; glue-wg@ogf.org; Paul Millar Subject: RE: Progress on LDAP schema
Hi Florido,
Quite busy with other priorities in the next two weeks. I hope I can try this in June. I´ll keep you informed.
Sorry, Maria
-----Original Message----- From: Florido Paganelli [mailto:florido.paganelli@hep.lu.se] Sent: 08 May 2014 17:58 To: Maria Alandes Pradillo; glue-wg@ogf.org; Paul Millar Subject: Progress on LDAP schema
Hi all,
Yesterday I tested the changes mandated by the new version of the LDAP document in a test environment and I didn't see any issue. I didn't see any bad error in slapd logs, and the objects that were affected by changes are published as expected.
I attach the latest schema and kindly ask Maria and Paul to test the impact on their products: GLUE20.schema.20140508
A list of diffs between the current distributed version of the schema (2.0rc5) against the new version (2.0rc6) that is included in this email: distro2.0rc5_diff_2.0rc6.changes
I suggest you check them with some nice editor that colors things up so you can easily spot differences.
I pushed the source schemas in my git-hub area temporarily, if we're fine with that I will push it to the official repos:
https://github.com/floridop/LDAPWIP
I would say that we should put recommendations in the release notes that I added in the README files on git-hub. I didn't do it yet, but the issues I can imagine we should add are the following:
1) ABSTRACT classes to be in sync with XML realisation: Objects like Entity, Resource, Share, Policy have been declared ABSTRACT to be in sync with the XML schema. This means these cannot be instantiated as is; only their specialization can (i.e. Computing- Storage- or others like Benchmark etc.) are objects that can be published.
2) Boolean type changed to DirectoryString This means that if the boolean values that are mandatory in the schema are not defined, the information providers MUST publish them and MUST present the value "undefinedvalue"; GFD.147 Appendix B.17. These are: ExecutionEnvironment.ConnectivityIn ExecutionEnvironment.ConnectivityOut
If you spot any problem, let me know.
Regards, Florido -- ================================================== Florido Paganelli ARC Middleware Developer - NorduGrid Collaboration System Administrator Lund University Department of Physics Division of Particle Physics BOX118 221 00 Lund Office Location: Fysikum, Hus B, Rum B313 Office Tel: 046-2220272 Email: florido.paganelli@REMOVE_THIShep.lu.se Homepage: http://www.hep.lu.se/staff/paganelli ==================================================
Maria Alandes Pradillo [mailto:Maria.Alandes.Pradillo@cern.ch] said:
I don´t know what else I could test. Any ideas?
You could check that no object types or attribute names have vanished - something like grep objectClass | sort | uniq grep ^GLUE2 | cut -d: -f1 | sort | uniq (I haven't tested those so the syntax may not be quite right). Also I assume you checked for errors in the log? The only specific change is for Boolean attributes, so you could look for those and check they're the same. You could also perhaps try injecting the correct value, e.g. "true" rather than "TRUE". Stephen
Dear Stephen,
You could check that no object types or attribute names have vanished - something like
grep objectClass | sort | uniq
grep ^GLUE2 | cut -d: -f1 | sort | uniq
That seems to be fine: ldapsearch -x -LLL -h localhost -p 2170 -b o=glue | grep objectClass | sort | uniq | wc -l 32 [root@standard-top-bdii ~]# ldapsearch -x -LLL -h lcg-bdii -p 2170 -b o=glue | grep objectClass | sort | uniq | wc -l 32 [root@standard-top-bdii ~]# ldapsearch -x -LLL -h localhost -p 2170 -b o=glue | grep ^GLUE2 | cut -d: -f1 | sort | uniq | wc -l 223 [root@standard-top-bdii ~]# ldapsearch -x -LLL -h lcg-bdii -p 2170 -b o=glue | grep ^GLUE2 | cut -d: -f1 | sort | uniq | wc -l 223
(I haven't tested those so the syntax may not be quite right). Also I assume you checked for errors in the log? The only specific change is for Boolean attributes, so you could look for those and check they're the same. You could also perhaps try injecting the correct value, e.g. "true" rather than "TRUE".
There are no errors in the log. I can still see many "TRUE" and "FALSE" being published, but no "true" or "false". Should I tell the developers that they should be publishing "true" or "false" instead? ldapsearch -x -LLL -h localhost -p 2170 -b o=glue | grep TRUE | sort | uniq -c 36 GLUE2ComputingManagerHomogeneous: TRUE 39 GLUE2ComputingManagerWorkingAreaShared: TRUE 131 GLUE2EntityOtherInfo: ArgusEnabled=TRUE 106 GLUE2ExecutionEnvironmentConnectivityIn: TRUE 433 GLUE2ExecutionEnvironmentConnectivityOut: TRUE 42 GLUE2ExecutionEnvironmentVirtualMachine: TRUE ldapsearch -x -LLL -h localhost -p 2170 -b o=glue | grep FALSE | sort | uniq -c 7 GLUE2AdminDomainDistributed: FALSE 51 GLUE2ComputingManagerBulkSubmission: FALSE 15 GLUE2ComputingManagerHomogeneous: FALSE 49 GLUE2ComputingManagerWorkingAreaGuaranteed: FALSE 10 GLUE2ComputingManagerWorkingAreaShared: FALSE 269 GLUE2EntityOtherInfo: ArgusEnabled=FALSE 357 GLUE2ExecutionEnvironmentConnectivityIn: FALSE 30 GLUE2ExecutionEnvironmentConnectivityOut: FALSE Regards, Maria
Maria Alandes Pradillo [mailto:Maria.Alandes.Pradillo@cern.ch] said:
I can still see many "TRUE" and "FALSE" being published, but no "true" or "false". Should I tell the developers that they should be publishing "true" or "false" instead?
Not yet, we have to wait until all the site and top BDIIs have upgraded to the new schema. Stephen
Thanks Maria, Stephen. I also think that the Boolean change is the only thing we should be worried about. With respect to this, there is two mandatory boolean fields: ExecutionEnvironment.ConnectivityIn ExecutionEnvironment.ConnectivityOut if these are not set, the change to DirectoryString will prevent the attribute from publishing (A DirectoryString cannot be empty), which breaks a bit the schema. To be fully compliant, if these are not set the infoproviders should publish the special GLUE2 value "undefinedvalue". This might be also useful to code in the validator. Cheers, Florido On 2014-06-18 11:22, stephen.burke@stfc.ac.uk wrote:
Maria Alandes Pradillo [mailto:Maria.Alandes.Pradillo@cern.ch] said:
I can still see many "TRUE" and "FALSE" being published, but no "true" or "false". Should I tell the developers that they should be publishing "true" or "false" instead?
Not yet, we have to wait until all the site and top BDIIs have upgraded to the new schema.
Stephen
-- ================================================== Florido Paganelli ARC Middleware Developer - NorduGrid Collaboration System Administrator Lund University Department of Physics Division of Particle Physics BOX118 221 00 Lund Office Location: Fysikum, Hus B, Rum B313 Office Tel: 046-2220272 Email: florido.paganelli@REMOVE_THIShep.lu.se Homepage: http://www.hep.lu.se/staff/paganelli ==================================================
Dear Florido,
With respect to this, there is two mandatory boolean fields:
ExecutionEnvironment.ConnectivityIn ExecutionEnvironment.ConnectivityOut
if these are not set, the change to DirectoryString will prevent the attribute from publishing (A DirectoryString cannot be empty), which breaks a bit the schema.
To be fully compliant, if these are not set the infoproviders should publish the special GLUE2 value "undefinedvalue".
This might be also useful to code in the validator.
This seems to be published with values TRUE/FALSE. Regards, Maria
Hi all, As a follow up from June 3rd's meeting, I corrected the schema with the requested changes. All the entities but Entity are of type STRUCTURAL now. To ease Paul and Maria's work, I resend the new schema changes and in attachment: GLUE20.schema.20140603 distro2.0rc5_diff_2.0rc7.changes with a kind request of testing it with their latest software. The complete version of the schema in the tarball can also be used Shiraz and JP can integrate it into the LDAP realisation document. But mind that I will change the version in the final content to put it in the official git-hub (it is now 2.0rc7, I plan to change it to 2.0), so we will need an additional iteration. The development schema is in my github: http://github.com/floridop/LDAPWIP I will send a pull request to the OGF git-hub master repository when we are sure this is final, and it will be publicly available on the official OGF repository. Cheers, Florido On 2014-05-08 17:57, Florido Paganelli wrote:
Hi all,
Yesterday I tested the changes mandated by the new version of the LDAP document in a test environment and I didn't see any issue. I didn't see any bad error in slapd logs, and the objects that were affected by changes are published as expected.
I attach the latest schema and kindly ask Maria and Paul to test the impact on their products: GLUE20.schema.20140508
A list of diffs between the current distributed version of the schema (2.0rc5) against the new version (2.0rc6) that is included in this email: distro2.0rc5_diff_2.0rc6.changes
I suggest you check them with some nice editor that colors things up so you can easily spot differences.
I pushed the source schemas in my git-hub area temporarily, if we're fine with that I will push it to the official repos:
https://github.com/floridop/LDAPWIP
I would say that we should put recommendations in the release notes that I added in the README files on git-hub. I didn't do it yet, but the issues I can imagine we should add are the following:
1) ABSTRACT classes to be in sync with XML realisation: Objects like Entity, Resource, Share, Policy have been declared ABSTRACT to be in sync with the XML schema. This means these cannot be instantiated as is; only their specialization can (i.e. Computing- Storage- or others like Benchmark etc.) are objects that can be published.
2) Boolean type changed to DirectoryString This means that if the boolean values that are mandatory in the schema are not defined, the information providers MUST publish them and MUST present the value "undefinedvalue"; GFD.147 Appendix B.17. These are: ExecutionEnvironment.ConnectivityIn ExecutionEnvironment.ConnectivityOut
If you spot any problem, let me know.
Regards, Florido
_______________________________________________ glue-wg mailing list glue-wg@ogf.org https://www.ogf.org/mailman/listinfo/glue-wg
-- ================================================== Florido Paganelli ARC Middleware Developer - NorduGrid Collaboration System Administrator Lund University Department of Physics Division of Particle Physics BOX118 221 00 Lund Office Location: Fysikum, Hus B, Rum B313 Office Tel: 046-2220272 Email: florido.paganelli@REMOVE_THIShep.lu.se Homepage: http://www.hep.lu.se/staff/paganelli ==================================================
Hi Florido, I will try to test this in the upcoming days and get back to you. Regards, Maria
-----Original Message----- From: glue-wg-bounces@ogf.org [mailto:glue-wg-bounces@ogf.org] On Behalf Of Florido Paganelli Sent: 04 June 2014 13:43 To: glue-wg@ogf.org Subject: Re: [glue-wg] Progress on LDAP schema
Hi all,
As a follow up from June 3rd's meeting, I corrected the schema with the requested changes. All the entities but Entity are of type STRUCTURAL now.
To ease Paul and Maria's work, I resend the new schema changes and in attachment: GLUE20.schema.20140603 distro2.0rc5_diff_2.0rc7.changes
with a kind request of testing it with their latest software.
The complete version of the schema in the tarball can also be used Shiraz and JP can integrate it into the LDAP realisation document. But mind that I will change the version in the final content to put it in the official git-hub (it is now 2.0rc7, I plan to change it to 2.0), so we will need an additional iteration.
The development schema is in my github:
http://github.com/floridop/LDAPWIP
I will send a pull request to the OGF git-hub master repository when we are sure this is final, and it will be publicly available on the official OGF repository.
Cheers, Florido
On 2014-05-08 17:57, Florido Paganelli wrote:
Hi all,
Yesterday I tested the changes mandated by the new version of the LDAP document in a test environment and I didn't see any issue. I didn't see any bad error in slapd logs, and the objects that were affected by changes are published as expected.
I attach the latest schema and kindly ask Maria and Paul to test the impact on their products: GLUE20.schema.20140508
A list of diffs between the current distributed version of the schema (2.0rc5) against the new version (2.0rc6) that is included in this email: distro2.0rc5_diff_2.0rc6.changes
I suggest you check them with some nice editor that colors things up so you can easily spot differences.
I pushed the source schemas in my git-hub area temporarily, if we're fine with that I will push it to the official repos:
https://github.com/floridop/LDAPWIP
I would say that we should put recommendations in the release notes that I added in the README files on git-hub. I didn't do it yet, but the issues I can imagine we should add are the following:
1) ABSTRACT classes to be in sync with XML realisation: Objects like Entity, Resource, Share, Policy have been declared ABSTRACT to be in sync with the XML schema. This means these cannot be instantiated as is; only their specialization can (i.e. Computing- Storage- or others like Benchmark etc.) are objects that can be published.
2) Boolean type changed to DirectoryString This means that if the boolean values that are mandatory in the schema are not defined, the information providers MUST publish them and MUST present the value "undefinedvalue"; GFD.147 Appendix B.17. These are: ExecutionEnvironment.ConnectivityIn ExecutionEnvironment.ConnectivityOut
If you spot any problem, let me know.
Regards, Florido
_______________________________________________ glue-wg mailing list glue-wg@ogf.org https://www.ogf.org/mailman/listinfo/glue-wg
-- ================================================== Florido Paganelli ARC Middleware Developer - NorduGrid Collaboration System Administrator Lund University Department of Physics Division of Particle Physics BOX118 221 00 Lund Office Location: Fysikum, Hus B, Rum B313 Office Tel: 046-2220272 Email: florido.paganelli@REMOVE_THIShep.lu.se Homepage: http://www.hep.lu.se/staff/paganelli ==================================================
participants (3)
-
Florido Paganelli -
Maria Alandes Pradillo -
stephen.burke＠stfc.ac.uk