Hi all
I haven't been following the progress in this group for quite a while,
as a matter of fact I do not even know if this channel is still official.
I've been asked by Greg from UKRI STFC in UK (in CC) about the status of
the Open Enumerations registry at
https://github.com/OGF-GLUE/Enumerations
I recall David Meredith was taking care of merging pull requests but I
do not see any updated procedure anywhere and I think he is no longer
actively doing the merges.
I wonder how we should go about it. Right now most of my research group
is on vacation and I do not know how much NorduGRID/ARC is interested in
being part of this. If Greg and UKRI STFC are interested in maintaining
the registry I will gladly give them rights to approve merge requests.
My only complaint after a quick look at the current pull requests
https://github.com/OGF-GLUE/Enumerations/pulls
Is that some of the new strings are not all lowercase. I would prefer
they are all lowercase at least, to be consistent with the rest of
GLUE2. But I do not know what happened in GLUE2.1 and how much you kept
consistency. I must sadly say I lost interest long ago in the group
activities mainly for the lack of consistency in some that I believe
were critical decisions so my enthusiasm about the subject is low.
About the pending merge requests, I think the namespaces in the pull
requests are all well formed, one should check case by case how much
they conform to the expected values and how good the descriptions are, I
remember we had different opinions about these details as well but I
forgot what it was about.
I have the feeling the word ServiceType is overused as there is some
confusion about what is a GLUE2 ServiceType and what is a GOCDB
servicetype, but as said I've been far from this and lost track.
I'd say from my side as long as it doesn't affect ARC/NorduGRID
negatively I don't really care about which strings end up in this registry.
I think the main point is, was there ever consensus on this document
which defines formats and other similar things?
http://redmine.ogf.org/dmsf_files/13224?download=
Clearly not since the document suggest scheduled venues for the merges
that clearly never happened. Sad. But partly also my bad for not
following up.
Would be nice to update such document and the information on github with
the actual procedure including pull requests.
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 A, Rum A403
Office Tel: 046-2220272
Email: florido.paganelli(a)REMOVE_THIShep.lu.se
Homepage: http://www.hep.lu.se/staff/paganelli
==================================================
We are making progress on learning to use GitBook for document production. It’s a bit of a manual process, but features have been improving and we have worked out a pretty straightforward importing process.
I've taken the latest draft I could find with edits suggested by Jens’s and Björn's feedback posted here: https://redmine.ogf.org/boards/43/topics/506?r=522 (cf. Shiraz’z notes from the
GLUE WG teleconference, Tuesday, November 12, 2019 sent November 13, 2019) and built a test document in Word to use for import testing. Note in this test document, I have accepted all changes and suppressed comments; we can start from another version if desired. Note also that GitBook has its own branching and merging functions as well as the ability to edit, and there is an integration that we have turned on to GitHub that should allow for pull requests and issues in addition to the GitBook draft and merge functionality.
The GitBook version of this test document is at the following link:
https://open-grid-forum.gitbook.io/glue-2-1-test/
This should be readable by anyone and editable by anyone in the GitBook OGF-GLUE team from within GitBook.
The GitHub synchronized copy is at the following link:
https://github.com/OpenGridForum/OGF-GLUE-2.1-test
The navigation there is by “slug” (the page/section label used within GitBook) and so the document does not display as prettily in GitHub, but should be navigable and suitable for branching, editing, and pull requests as well as discussion of issues in the GitHub setting. this repository is readable and clone-able by anyone in the OGF-GLUE GitHub team (https://github.com/orgs/OpenGridForum/teams/ogf-glue/members) which at this point is different from the GitBook teams. but I or JP should be able to add members with write or other levels of editing and maintaining privileges to either team, or both.
Documentation on use of GitBook is available at the following link.
https://docs.gitbook.com
Please try this out (you won’t be harming anything permanent as this is a test copy) and let me know if we can do anything further to help move the GLUE group to this new document production process.
Thanks,
Alan
Hi all,
GOCDB has received a request to add a new service type for Dynafed, see below.
There is a GGUS ticket open here: https://ggus.eu/index.php?mode=ticket_info&ticket_id=148559 to track the discussion around this request if anyone on this list has any comment on it.
Thanks
Greg
From: Gocdb-admins <gocdb-admins-bounces(a)mailman.egi.eu> On Behalf Of Greg Corbett - UKRI STFC via Gocdb-admins
Sent: Tuesday, 8 September 2020 11:31
To: 'is-approvals(a)cern.ch' <is-approvals(a)cern.ch>; 'noc-managers(a)mailman.egi.eu' <noc-managers(a)mailman.egi.eu>; 'infosys-discuss(a)cern.ch' <infosys-discuss(a)cern.ch>
Cc: Corbett, Greg (STFC,RAL,SC) <greg.corbett(a)stfc.ac.uk>; 'Operations Team' <operations(a)egi.eu>; 'GOCDB Admins Discussion' <gocdb-admins(a)mailman.egi.eu>
Subject: [Gocdb-admins] Request for new GOCDB service type: ch.cern.dynafed
Hi all,
GOCDB has received a request to add a new service type, summarised below. As per the EGI lightweight review process, please raise any concerns about this proposal on its GGUS ticket by the end of Tuesday 22nd September: https://ggus.eu/index.php?mode=ticket_info&ticket_id=148559
* name of service: ch.cern.dynafed
* high-level description of the service functionality: Dynafed systems expose, via HTTP and WebDAV, a dynamic name space built on the fly by merging and caching metadata items taken from a number of (remote) endpoints.
* project/community/organization maintaining the software: Data Management Clients Development team - CERN
* scope of deployment: Increasing number of Dynafed endpoints across the Grid
Thanks
Greg
This email and any attachments are intended solely for the use of the named recipients. If you are not the intended recipient you must not use, disclose, copy or distribute this email or any of its attachments and should notify the sender immediately and delete this email from your system. UK Research and Innovation (UKRI) has taken every reasonable precaution to minimise risk of this email or any attachments containing viruses or malware but the recipient should carry out its own virus and malware checks before opening the attachments. UKRI does not accept any liability for any losses or damages which the recipient may sustain due to presence of any viruses. Opinions, conclusions or other information in this message and attachments that are not related directly to UKRI business are solely those of the author and do not represent the views of UKRI.
