- glue-wg - lists.ogf.org

guse.ws-pgrade SE type request
by david.meredith＠stfc.ac.uk 25 Mar '14

25 Mar '14

Dear all, EGI/GOCDB has had a new service type request for 'guse.ws-pgrade' (submitted on behalf WS-PGRADE collaboration). We would also like to agree on this service type for the GLUE2 enum list[1]. FYI: 'gUSE' represents the whole service ecosystem, including WS-PGRADE. There are other components in gUSE (DCI Bridge, WFI) that we expect will be requested later. Can we add this to the agenda for tomorrow's meeting for approval? Cheers, David https://github.com/OGF-GLUE/Enumerations/blob/master/ServiceType_t.csv ========================== David Meredith Scientific Computing Dept Daresbury Laboratory Tel: +44 (0) 1925 603762 Fax: +44 (0) 1925 603100 (Site) Email: david.meredith(a)stfc.ac.uk Skype name: davidismeredith -- Scanned by iCritical.

3 3

Next GLUE WG meetings, March 12 and/or 25?
by Navarro, John-Paul F. 11 Mar '14

11 Mar '14

Greetings GLUE WG, Shiraz and I would like to offer our apologies for the extended GLUE WG meeting holiday, and for not being able to attend OGF-40 in Oxford. It's time to restart our work. We propose two meetings: 1) Wednesday, March 12 at 4 PM Central Europe/9 AM US Central (as an exception to our usual Tuesday) 2) Tuesday, March 25 at the usual time Please reply if you are a regular teleconference participant informing the group which of the above dates you are available. Based on participant availability we will have one or both of these meetings. Proposed agenda for our next meeting: 1) Cloud extensions (Salvatore: 10 minute status update) OGF 40 ACTION: The group agreed to request that the GLUE Specification v 2.1 submitted with Cloud extensions be RE-SUBMITTED by the authors with change tracking enabled so that all the changes with respect to the current Specification v2.0 are clearly visible. All other editing by anyone in the group should be change tracked until the group approves, submits, and officially releases v 2.1. 2) LDAP rendering (JP/Shiraz: 10 minute status update) OGF 40 ACTION: The group agreed that the final editing for comprehensibility should be done by JP and Shiraz: 1. Make sure the purpose of the DIT Appendix is clear and who the target audience (people writing implementation and/or users) 2. Make it clear that the main purpose of the document is to define the LDAP rendering of the schema. Reference to the schema should be included, perhaps in an Appendix. 3. JP and Shiraz should report back to working group with a change tracked version for final review 3) Enumerations (All: 1 hour) Enumerations process, policies, and guidelines. Specific proposed new enumerations. BES/JSDL related enumerations and attributes needs (Andrew) 4) Can we move future meetings to start 30 minutes sooner? (5 minutes) 3:30-5 PM Central Europe 8:30-10 AM US Central Any other suggested topics? Regards, JP and Shiraz

4 3

Update WebDAV proposal
by Paul Millar 06 Mar '14

06 Mar '14

Hi all, Here's an updated version of the proposal: --- A service that supports HTTP or any extension based on HTTP MAY publish StorageAccessProtocol objects to represent this. If a StorageAccessProtocol object is published to represent HTTP access then the Type SHOULD|MUST be 'http'. If a StorageAccessProtocol object is published to represent WebDAV access then the Type SHOULD|MUST be 'webdav'. When publishing an Endpoint that supports HTTP (or any extension based on HTTP) without encryption then the URL SHOULD start 'http://'. If an Endpoint the endpoint supports HTTP (or any extension based on HTTP) with SSL or TLS encryption then the URL SHOULD start 'https://' If the endpoint supports WebDAV then an InterfaceExtension of 'http://www.ietf.org/rfc/rfc4918.txt' SHOULD be published. --- Is this any better? Cheers, Paul.

2 1

Need help setting up OGF teleconference
by Navarro, John-Paul F. 15 Jan '14

15 Jan '14

GLUE WG, I just realized the Shiraz is on holiday thru January 18. I did not travel to Oxford and was planning on participating in GLUE WG sessions via teleconference. Can anyone else attending OGF volunteer their time and laptop to work with me to setup and test teleconference software ahead of time? I will be on Skype (jpnavarro_mac.com) at 12:30 UK time to prepare for the 1:30 PM session. Please reply if you are willing to help from OGF. Our proposed agenda is: 1) LDAP and JSON rendering work status 2) Cloud support changes 3) Other activity status Regards, JP Navarro

2 3

GLUE 2.1 (Cloud extension) for discussion
by Salvatore Pinto 14 Jan '14

14 Jan '14

Dear GLUE-WG members, I attached to this email the last version of the GLUE 2.1 document (addition of cloud extensions), for discussion in tomorrow's OGF session. Unfortunately, I will not be able to attend to the meeting, due to clashing with other meetings, but Stephen Burke will load the discussion on my behalf and Michel Dresher from EGI will join too, providing cloud technology expertise. I hope it will be a fruitful discussion, and you all can comment (and hopefully agree) on the GLUE 2.1 cloud entities conceptual model and the other minor (back-compatible) changes we want to include in GLUE 2.1. My apologies again for not being able to join the face to face. Best Regards, Salvatore Pinto. NOTE: Respect to the document presented in the previous teleconference, the changes I performed (following the previous teleconference discussion) are: * Added document change log * Added PENDING state for a VM * Deleted CloudMiddelware from endpoint (Type attribute is used insthead) * Removed TotalVM information at endpoint level (redundant, not needed) * Rewritten description of CloudComputeShare as generic resource pool (insthead of VO - related group) * Removed Tag attribute from CloudComputeShare (reduntant, not needed) * Updated IDFromEndpoint and MarketPlaceID attributes for CloudComputeInstanceType and CloudComputeImage. Added relation of CloudComputeInstanceType and CloudComputeImage to the endpoint (for users to resolve the Endpoint ID from the MarketPlaceID ) * Updated Conceptual For Cloud Compute model to address changes in relations of CloudComputeInstanceType and CloudComputeImage.

1 0

Documents for discusion in Oxford next week
by Andrew Grimshaw 14 Jan '14

14 Jan '14

Colleagues, After a long gestation period the documents first discussed in Lyon several years ago are ready for discussion. To my GLUE colleagues you are receiving this email because the first document includes the incorporation of GLUE2 into JSDL and BES factory attributes. The documents can be found in the OGSA-BES document area: http://redmine.ogf.org/dmsf/ogsa-bes-wg Andrew Document 1: BES/JSDL 1.1 Extensions The Production Grid Interoperability Working Group identified a number of execution management use cases and requirements in GFD.180. A number of ways to meet these requirements have been extensively discussed. They fall into two categories: 1) define a new set of specifications from scratch to meet the requirements, and 2), profile and minimally extend existing specifications to meet the requirements. The second approach, combining and refining existing production use specifications, has been embraced by the existing OGSA BES and JSDL communities. The approach combines, extends, and profiles five existing specifications to meet the PGI requirements: WS Addressing EndPoint References, OGSA Basic Execution Services (OGSA_BES, or BES) [GFD.108], RNS 1.1 OGSA-WSRF Basic Profile 1.0 [GFD.172], WS-Iterator 1.0 [GFD.188], and OGSA-ByteIO WSRF Basic Profile 1.0 [GFD.98]. The BES/JSDL extensions described in this document are a part of the second approach. Along with the BES Basic Directory Profile (BDP) and the Activity Endpoint Profile (AEP) the BES/JSDL extensions meet the PGI requirements. Profiled JSDL extensions and their corresponding additions to BES factory attributes include: incorporation of GLUE2 [] compute resource properties, arbitrary name/value pair matching parameters, additional file system types, and richer file staging options. The profiled BES extensions include a substate model with a set of "Held" substates and pre-and-post-processing substates, a "ResumeActivities" porttype, and clarified JSDL mechanism to subscribe to notifications. The document is nearing completion. Areas in YELLOW need discussion and decision. Document 2: BES Directory Profile The BES Directory Profile (BDP) is a profile on OGSA Basic Execution Services 1.0 that provides a Unix directory like interface to OGSA BES endpoints that allow the client to examine and modify BES configuration information as well as list, create, and terminate activities. The profile defines no port-types; rather it simply describes what directory elements MUST exist in a compliant implementation and what the semantics are of interacting with those entries. The goal is to provide a simple uniform mechanism to support requirements identified by the Production Grid Interoperability Working Group of the Open Grid Forum [cite]. The mechanism described for the BDP is independent of the OGSA BES specification. Thus, changes in the OGSA BES specification in the future will not impact the usefulness of the BDP. Document 3: Activity Endpoint Profile The Activity Endpoint Profile is a profile on the EndPointReference returned by an OGSA Basic Execution Services CreateActivity call. It defines port-types that the endpoint must support, and values that MUST be returned from calls and values that MAY be returned. The goal is to provide a uniform mechanism to support requirements identified by the Production Grid Interoperability Working Group of the Open Grid Forum [cite].

3 2

NO GLUE WG teleconference, Tuesday, December 17
by JP Navarro 16 Dec '13

16 Dec '13

Due to scheduling conflicts we will NOT have a GLUE WG teleconference, Tuesday, December 17. Our next scheduled meeting may be Tuesday, January 14, or January 15-17 at OGF 40 in Oxford, UK. Best wishes over the holiday break. JP and Shiraz

1 0

Re: [glue-wg] Extending GLUE 2.0 for Cloud services
by Salvatore Pinto 04 Dec '13

04 Dec '13

Dear GLUE WG mailing list, in the context of the EGI Federated Cloud <http://www.egi.eu/solutions/fed-cloud/>, we come across the need for a standard for information discovery in the Cloud ecosystem. We looked at the existing standard of the Cloud/Grid world, and, considering that no current standard seems to meet our requirements, we decided to propose an extension to the GLUE 2.0 schema to cover Cloud Compute and Storage services. The first proposed draft is attached. We would really appreciate your comments and maybe to add a point for discussion in the next WG meeting. Thank you a lot in advance for your support. Best Regards, Salvatore Pinto. -- Salvatore Pinto Cloud Technologist, EGI.eu e-mail:salvatore.pinto@egi.eu skype: salvatore.pinto0 Science Park 140, Amsterdam, The Netherlands On 16/10/2013 22:24, JP Navarro wrote: > Hello Sergio, > > Sounds interesting. > > We'll put it on the agenda for a future meeting once the working group has seen the document and had a chance to review it. Perhaps your colleagues can answer questions as well as propose how to integrate the extensions into GLUE 2.0. > > Regards, > > JP > On Oct 10, 2013, at 10:59 AM, Sergio Andreozzi<sergio.andreozzi(a)egi.eu> wrote: > >> Hi Shiraz, JP, >> >> My colleagues (in copy) have produced extensions to GLUE 2.0 for Cloud in the context of the EGI Federated Cloud activities (http://www.egi.eu/solutions/fed-cloud/) They would like to submit a document to the group so that it could be discussed, agreed and then submitted for publication. >> >> They will join the mailing list and liaise with you for the process. I guess this activity will be of interest given the growing activities around federated clouds. >> >> Cheers, Sergio >> >> -- >> Sergio Andreozzi - Strategy and Policy Manager - EGI.eu >> http://www.egi.eu -skype:sergio.andreozzi.egi

8 21

GLUE2 XSD published (and Cloud extensions)
by david.meredith＠stfc.ac.uk 03 Dec '13

03 Dec '13

Hi all, FYI the GLUE v2.0 XML rendering has been published: http://www.ogf.org/documents/GFD.209.pdf Regarding the cloud extensions: I expect that the abstract entities defined in this XSD (e.g. AbstractService, AbstractEndpoint, AbstractShare, AbstractManager etc...) could be extended to derive the new cloud entities/types in and extension XSD, e.g. CloudComputeService, CloudComputeEndpoint, CloudComputeShare. This could be done in exactly the same way as the existing GLUE 2 concrete entities (ComputingService, ComputingEndpoint, StorageShare and so on). I'm sorry I can't make it to the meeting today. David ========================== David Meredith Scientific Computing Dept Daresbury Laboratory Tel: +44 (0) 1925 603762 Fax: +44 (0) 1925 603100 (Site) Email: david.meredith(a)stfc.ac.uk Skype name: davidismeredith -- Scanned by iCritical.

3 2

Glue1 material?
by Florido Paganelli 03 Dec '13

03 Dec '13

Hi all, We have a problem. I was searching for reference documents to Glue1 today and I couldn't find any. Appartently the one and only: https://forge.ogf.org/sf/go/doc14185 has been removed from sourceforege and never moved to redmine. Anybody who has a copy willing to add it back in redmine? I am also searching for references on how it is used in the current EGI/OpenGrid deployment, probably some of you can give me pointers. 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 Tel: 046-2220272 Email: florido.paganelli(a)REMOVE_THIShep.lu.se Homepage: http://www.hep.lu.se/staff/paganelli ==================================================

3 4