GLUE WG teleconference, Tuesday, June 17, 2014

Greetings GLUE WG, Our next GLUE WG teleconference will be: : Tuesday, June 17, 2014 : 15:30-17:00 Central Europe, 8:30-10:00 AM US Central We will try a new teleconference and screen sharing tool: : Web: https://meet.illinois.edu/herrio/V57YV10Q : --> Cancel login dialog, click guest "Sign in here instead", enter name, click "Join the meeting" : Phone: 1-888-983-3631, International 1-217-332-6338 or 1-312-994-8410 : Conference ID: 6759150 If the new teleconference tool doesn't work well, we will revert to our normal tool: : Web: https://webconf.vc.dfn.de/ogf-glue-wg/ (Adobe Connect) : Login as Guest using your real name Meeting materials folder: : http://redmine.ogf.org/dmsf/glue-wg?folder_id=6587 Proposed agenda: 1) LDAP rendering: assess final wg comments and votes and perhaps forward for public comment Previous actions:
Action 1: Florido will send final schema to the list Action 2: JP will merge schema into Appendix following XML example Action 3: JP will add a reference to a standalone schema document in the LDAP rendering document Action 4: JP/Shiraz will send out for final 1 week comment request to glue-wg Action 5: JP/Shiraz will integrate comments and send out a 1 week vote request to glue-wg Action 6: JP/Shiraz will confirm with OGF area lead if we need consensus or majority vote results
Agreed 1: Enumerations are case sensitive as defined by the schema entities that they describe Agreed 2: Prohibit the use of multiple enumerations that only vary in case Action 1: Florido will update document to reflect Agreed 1 & 2 and notify GLUE WG to review and provide feedback odt: https://redmine.ogf.org/dmsf_files/13260?download=
2) Enumerations: approve enumerations process document Previous actions: pdf: https://redmine.ogf.org/dmsf_files/13261?download=
Action 2: GLUE WG to review Florido's revised Action 2: At the next GLUE WG call we will vote on the updated document
3) Cloud Extensions: compare benefits and disadvantages of both approaches
Plan discussion for next meeting.
4) JSON: continue rendering discussions, discuss next steps.
Agreed 1: Use an Associations bag for association references Agreed 2: All association references will use the "ID" suffix We will continue JSON rendering discussion at next call.
5) Future meetings Teleconference OGF 41 sessions July 16 or 17 Regards, JP and Shiraz

Hi John, sorry for this, but unfortunately I have another meeting clashing with the GLUE tomorrow... Would be possible to start the discussion about the cloud entities at 16:30 CET? Stayiing more than 17:00 is not a problem for me... Cheers, Salvatore. On 16/06/2014 16:13, Navarro, John-Paul F. wrote:
Greetings GLUE WG,
Our next GLUE WG teleconference will be: : Tuesday, June 17, 2014 : 15:30-17:00 Central Europe, 8:30-10:00 AM US Central
We will try a new teleconference and screen sharing tool: : Web: https://meet.illinois.edu/herrio/V57YV10Q : --> Cancel login dialog, click guest "Sign in here instead", enter name, click "Join the meeting" : Phone: 1-888-983-3631, International 1-217-332-6338 or 1-312-994-8410 : Conference ID: 6759150
If the new teleconference tool doesn't work well, we will revert to our normal tool: : Web: https://webconf.vc.dfn.de/ogf-glue-wg/ (Adobe Connect) : Login as Guest using your real name
Meeting materials folder: : http://redmine.ogf.org/dmsf/glue-wg?folder_id=6587
Proposed agenda:
Action 1: Florido will send final schema to the list Action 2: JP will merge schema into Appendix following XML example Action 3: JP will add a reference to a standalone schema document in the LDAP rendering document Action 4: JP/Shiraz will send out for final 1 week comment request to glue-wg Action 5: JP/Shiraz will integrate comments and send out a 1 week vote request to glue-wg Action 6: JP/Shiraz will confirm with OGF area lead if we need consensus or majority vote results
Agreed 1: Enumerations are case sensitive as defined by the schema entities that they describe Agreed 2: Prohibit the use of multiple enumerations that only vary in case Action 1: Florido will update document to reflect Agreed 1 & 2 and notify GLUE WG to review and provide feedback odt: https://redmine.ogf.org/dmsf_files/13260?download=
Action 2: GLUE WG to review Florido's revised Action 2: At the next GLUE WG call we will vote on the updated document
Plan discussion for next meeting.
Agreed 1: Use an Associations bag for association references Agreed 2: All association references will use the "ID" suffix We will continue JSON rendering discussion at next call.
1) LDAP rendering: assess final wg comments and votes and perhaps forward for public comment Previous actions: 2) Enumerations: approve enumerations process document Previous actions: pdf: https://redmine.ogf.org/dmsf_files/13261?download= 3) Cloud Extensions: compare benefits and disadvantages of both approaches 4) JSON: continue rendering discussions, discuss next steps. 5) Future meetings Teleconference OGF 41 sessions July 16 or 17
Regards,
JP and Shiraz _______________________________________________ glue-wg mailing list glue-wg@ogf.org https://www.ogf.org/mailman/listinfo/glue-wg
-- Salvatore Pinto Cloud Technologist, EGI.eu e-mail: salvatore.pinto@egi.eu skype: salvatore.pinto0 Science Park 140, Amsterdam, The Netherlands

Salvatore, Let's play it by ear. Warren will not know till tomorrow morning if he's available at 16:30 CET. We'll start the meeting with all the other topics, and if both you and Warren arrive by 16:30 we can have the cloud discussion then. Would that work? Thanks, JP On Jun 16, 2014, at 9:41 AM, Salvatore Pinto <salvatore.pinto@egi.eu> wrote:
Hi John, sorry for this, but unfortunately I have another meeting clashing with the GLUE tomorrow...
Would be possible to start the discussion about the cloud entities at 16:30 CET? Stayiing more than 17:00 is not a problem for me...
Cheers, Salvatore.
On 16/06/2014 16:13, Navarro, John-Paul F. wrote:
Greetings GLUE WG,
Our next GLUE WG teleconference will be: : Tuesday, June 17, 2014 : 15:30-17:00 Central Europe, 8:30-10:00 AM US Central
We will try a new teleconference and screen sharing tool: : Web: https://meet.illinois.edu/herrio/V57YV10Q : --> Cancel login dialog, click guest "Sign in here instead", enter name, click "Join the meeting" : Phone: 1-888-983-3631, International 1-217-332-6338 or 1-312-994-8410 : Conference ID: 6759150
If the new teleconference tool doesn't work well, we will revert to our normal tool: : Web: https://webconf.vc.dfn.de/ogf-glue-wg/ (Adobe Connect) : Login as Guest using your real name
Meeting materials folder: : http://redmine.ogf.org/dmsf/glue-wg?folder_id=6587
Proposed agenda:
Action 1: Florido will send final schema to the list Action 2: JP will merge schema into Appendix following XML example Action 3: JP will add a reference to a standalone schema document in the LDAP rendering document Action 4: JP/Shiraz will send out for final 1 week comment request to glue-wg Action 5: JP/Shiraz will integrate comments and send out a 1 week vote request to glue-wg Action 6: JP/Shiraz will confirm with OGF area lead if we need consensus or majority vote results
Agreed 1: Enumerations are case sensitive as defined by the schema entities that they describe Agreed 2: Prohibit the use of multiple enumerations that only vary in case Action 1: Florido will update document to reflect Agreed 1 & 2 and notify GLUE WG to review and provide feedback odt: https://redmine.ogf.org/dmsf_files/13260?download=
Action 2: GLUE WG to review Florido's revised Action 2: At the next GLUE WG call we will vote on the updated document
Plan discussion for next meeting.
Agreed 1: Use an Associations bag for association references Agreed 2: All association references will use the "ID" suffix We will continue JSON rendering discussion at next call.
1) LDAP rendering: assess final wg comments and votes and perhaps forward for public comment Previous actions: 2) Enumerations: approve enumerations process document Previous actions: pdf: https://redmine.ogf.org/dmsf_files/13261?download= 3) Cloud Extensions: compare benefits and disadvantages of both approaches 4) JSON: continue rendering discussions, discuss next steps. 5) Future meetings Teleconference OGF 41 sessions July 16 or 17
Regards,
JP and Shiraz _______________________________________________ glue-wg mailing list glue-wg@ogf.org https://www.ogf.org/mailman/listinfo/glue-wg
-- Salvatore Pinto Cloud Technologist, EGI.eu e-mail: salvatore.pinto@egi.eu skype: salvatore.pinto0 Science Park 140, Amsterdam, The Netherlands

Hi John, ok, I will try to be as quicker as possible with the other meeting, maybe I manage to join before 16:30.... Cheers, Salvatore. On 16/06/2014 16:57, Navarro, John-Paul F. wrote:
Salvatore,
Let's play it by ear. Warren will not know till tomorrow morning if he's available at 16:30 CET.
We'll start the meeting with all the other topics, and if both you and Warren arrive by 16:30 we can have the cloud discussion then.
Would that work?
Thanks,
JP
On Jun 16, 2014, at 9:41 AM, Salvatore Pinto <salvatore.pinto@egi.eu> wrote:
Hi John, sorry for this, but unfortunately I have another meeting clashing with the GLUE tomorrow...
Would be possible to start the discussion about the cloud entities at 16:30 CET? Stayiing more than 17:00 is not a problem for me...
Cheers, Salvatore.
On 16/06/2014 16:13, Navarro, John-Paul F. wrote:
Greetings GLUE WG,
Our next GLUE WG teleconference will be: : Tuesday, June 17, 2014 : 15:30-17:00 Central Europe, 8:30-10:00 AM US Central
We will try a new teleconference and screen sharing tool: : Web: https://meet.illinois.edu/herrio/V57YV10Q : --> Cancel login dialog, click guest "Sign in here instead", enter name, click "Join the meeting" : Phone: 1-888-983-3631, International 1-217-332-6338 or 1-312-994-8410 : Conference ID: 6759150
If the new teleconference tool doesn't work well, we will revert to our normal tool: : Web: https://webconf.vc.dfn.de/ogf-glue-wg/ (Adobe Connect) : Login as Guest using your real name
Meeting materials folder: : http://redmine.ogf.org/dmsf/glue-wg?folder_id=6587
Proposed agenda:
Action 1: Florido will send final schema to the list Action 2: JP will merge schema into Appendix following XML example Action 3: JP will add a reference to a standalone schema document in the LDAP rendering document Action 4: JP/Shiraz will send out for final 1 week comment request to glue-wg Action 5: JP/Shiraz will integrate comments and send out a 1 week vote request to glue-wg Action 6: JP/Shiraz will confirm with OGF area lead if we need consensus or majority vote results
Agreed 1: Enumerations are case sensitive as defined by the schema entities that they describe Agreed 2: Prohibit the use of multiple enumerations that only vary in case Action 1: Florido will update document to reflect Agreed 1 & 2 and notify GLUE WG to review and provide feedback odt: https://redmine.ogf.org/dmsf_files/13260?download=
Action 2: GLUE WG to review Florido's revised Action 2: At the next GLUE WG call we will vote on the updated document
Plan discussion for next meeting.
Agreed 1: Use an Associations bag for association references Agreed 2: All association references will use the "ID" suffix We will continue JSON rendering discussion at next call.
1) LDAP rendering: assess final wg comments and votes and perhaps forward for public comment Previous actions: 2) Enumerations: approve enumerations process document Previous actions: pdf: https://redmine.ogf.org/dmsf_files/13261?download= 3) Cloud Extensions: compare benefits and disadvantages of both approaches 4) JSON: continue rendering discussions, discuss next steps. 5) Future meetings Teleconference OGF 41 sessions July 16 or 17
Regards,
JP and Shiraz _______________________________________________ glue-wg mailing list glue-wg@ogf.org https://www.ogf.org/mailman/listinfo/glue-wg
-- Salvatore Pinto Cloud Technologist, EGI.eu e-mail: salvatore.pinto@egi.eu skype: salvatore.pinto0 Science Park 140, Amsterdam, The Netherlands
-- Salvatore Pinto Cloud Technologist, EGI.eu e-mail: salvatore.pinto@egi.eu skype: salvatore.pinto0 Science Park 140, Amsterdam, The Netherlands

Information on using Lync on Linux: http://geekyschmidt.com/2013/05/18/microsoft-lync-on-linux
Meeting materials folder: : http://redmine.ogf.org/dmsf/glue-wg?folder_id=6587
Proposed agenda:
1) LDAP rendering: assess final wg comments and votes and perhaps forward for public comment Previous actions:
Action 1: Florido will send final schema to the list Action 2: JP will merge schema into Appendix following XML example Action 3: JP will add a reference to a standalone schema document in the LDAP rendering document Action 4: JP/Shiraz will send out for final 1 week comment request to glue-wg Action 5: JP/Shiraz will integrate comments and send out a 1 week vote request to glue-wg Action 6: JP/Shiraz will confirm with OGF area lead if we need consensus or majority vote results Action 1: Florido will coordinate with Maria to confirm that all the recommended testing was completed Action 2: Once testing is complete, Florido will share a schema document without the release candidate lable Action 3: JP/Shiraz will merge schema into rendering document, e-mail list to vote and approve document for release to public comment
Agreed 1: Enumerations are case sensitive as defined by the schema entities that they describe Agreed 2: Prohibit the use of multiple enumerations that only vary in case Action 1: Florido will update document to reflect Agreed 1 & 2 and notify GLUE WG to review and provide feedback odt: https://redmine.ogf.org/dmsf_files/13260?download=
2) Enumerations: approve enumerations process document Previous actions: pdf: https://redmine.ogf.org/dmsf_files/13261?download=
Action 2: GLUE WG to review Florido's revised Action 2: At the next GLUE WG call we will vote on the updated document We noted that this is a GLUE WG working document, and not a spec per-se, so we will be able change it and approve changes by simple agreement. Action 1: Florido will accept changes and send the document to the list Action 2: DONE: Shiraz/JP will create new versioned wiki pages to contain the material, 1.0 for current document that we will vote on, and 1.1 for the next version http://redmine.ogf.org/projects/glue-wg/wiki/Enumerations_procedures_and_bes... http://redmine.ogf.org/projects/glue-wg/wiki/Enumerations_procedures_and_bes... Action 3: Florido will transfer content to new wiki pages, and notify Shiraz/JP Action 4: Shiraz/JP will announce to the list that this is an official WG process document Action 5: Florido will share Maria's enumeration request and associated discussion with the GLUE WG list
3) Cloud Extensions: compare benefits and disadvantages of both approaches
Plan discussion for next meeting. Action 1: Shiraz/JP ask Andre and OGF steering committee for ideas on resolving two approaches supported by 1 community each
4) JSON: continue rendering discussions, discuss next steps.
Agreed 1: Use an Associations bag for association references Agreed 2: All association references will use the "ID" suffix We will continue JSON rendering discussion at next call. Representing association, a to b, b to a, or both? Option 1: schema allows both directions, rendering document identifies directionality rules that should be followed Option 2: schema requires both directions Option 3: schema requires one direction which we consider to be the best, and in few cases may require both directions (applying should rules in rendering document) Option 4: schema requires one direction which we consider to be the best, the other direction is optional We want to discuss this with David on the call. Stephen pointed out that optional relations are ambiguous: if missing is there no relation or is it a missing relation?
5) Future meetings Next Teleconference Agreed to have next teleconference on July 1. OGF 41 sessions July 16-17 Agreed to have two session at 3 PM UK, 4 PM Central Europe, 10-11:30 AM Eastern Wednesday and Thursday Florido vacation July 11-28
Regards, JP and Shiraz

Hi all, On 2014-06-17 20:47, Navarro, John-Paul F. wrote:
[...] 2) Enumerations: approve enumerations process document [...] Action 2: At the next GLUE WG call we will vote on the updated document We noted that this is a GLUE WG working document, and not a spec per-se, so we will be able change it and approve changes by simple agreement. Action 1: Florido will accept changes and send the document to the list
Done
Action 2: DONE: Shiraz/JP will create new versioned wiki pages to contain the material, 1.0 for current document that we will vote on, and 1.1 for the next version http://redmine.ogf.org/projects/glue-wg/wiki/Enumerations_procedures_and_bes... http://redmine.ogf.org/projects/glue-wg/wiki/Enumerations_procedures_and_bes... Action 3: Florido will transfer content to new wiki pages, and notify Shiraz/JP
Done
Action 4: Shiraz/JP will announce to the list that this is an official WG process document
for you guys to do
Action 5: Florido will share Maria's enumeration request and associated discussion with the GLUE WG list
Done My conclusion is that redmine wiki is not too awkeard to use but it uses yet another notation from other wikis (mediawiki, dokuwiki) and some of the features of its engine texile does not work (i.e. coloring tables and text) The result is an output document with poor graphical design, an annoying small character set and bad interpage linking. The latter is very annoying, means that links to sections of the same page are hardcoded, hence everytime we write a new version one must check the links. veeeeery bad. If any of you finds a solution to this let me know. Cheers, 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 ==================================================

For everybody's information: On 2014-06-17 20:47, Navarro, John-Paul F. wrote:> Information on using Lync on Linux:
This is only about connecting to Lync chat service. In fact it says: "There are some shortcomings to this setup. Audio/Video between a Windows/Mac client to Pidgin does not function. Pidgin to Pidgin is no issue though. For simple text chat you will be fine with the above though." "some shortcomings" == no audio video at all. Actually is also no guest access. The truth is that even the webclient uses windows features that are not present in any linux/OSX machine, and will never be. Let's face it, this is a Windows only thing. Fun facts: On Windows 7 Pro + Office 2013 Lync client, all latest updates, it closes/crashes my Explorer, I am forced to use Firefox to connect! Cheers, 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 ==================================================
participants (3)
-
Florido Paganelli
-
Navarro, John-Paul F.
-
Salvatore Pinto