- graap-wg - lists.ogf.org

[Fwd: Fwd: [members] Proposed Charter for OASIS Web Services Calendar (WS-Calendar) TC]
by Philipp Wieder 06 Jan '10

06 Jan '10

Dear All, related to our discussions on an Advance Reservation profile this might be of interest. Best regards, Philipp. ------- Forwarded message ------- From: "Mary McRae" <mary.mcrae(a)oasis-open.org> To: members(a)lists.oasis-open.org, tc-announce(a)lists.oasis-open.org Cc: oasis-charter-discuss(a)lists.oasis-open.org Subject: [members] Proposed Charter for OASIS Web Services Calendar (WS-Calendar) TC Date: Wed, 06 Jan 2010 13:12:26 +0900 To OASIS Members: A draft TC charter has been submitted to establish the Web Services Calendar (WS-Calendar) Technical Committee (below). In accordance with the OASIS TC Process Policy section 2.2: (http://www.oasis-open.org/committees/process-2009-07-30.php#formation) the proposed charter is hereby submitted for comment. The comment period shall remain open until 11:45 pm ET on 19 January 2010. OASIS maintains a mailing list for the purpose of submitting comments on proposed charters. Any OASIS member may post to this list by sending email to: mailto:oasis-charter-discuss@lists.oasis-open.org. All messages will be publicly archived at: http://lists.oasis-open.org/archives/oasis-charter-discuss/. Members who wish to receive emails must join the group by selecting "join group" on the group home page: http://www.oasis-open.org/apps/org/workgroup/oasis-charter-discuss/. Employees of organizational members do not require primary representative approval to subscribe to the oasis-charter-discuss e-mail. A telephone conference will be held among the Convener, the OASIS TC Administrator, and those proposers who wish to attend within four days of the close of the comment period. The announcement and call-in information will be noted on the OASIS Charter Discuss Group Calendar. We encourage member comment and ask that you note the name of the proposed TC (WS-Calendar) in the subject line of your email message. Regards, Mary Mary P McRae Director, Standards Development Technical Committee Administrator OASIS: Advancing open standards for the information society email: mary.mcrae(a)oasis-open.org web: www.oasis-open.org twitter: @fiberartisan #oasisopen phone: 1.603.232.9090 ----- Web Services Calendar (WS-Calendar) Technical Committee 1. Normative Information a. Name Web Services Calendar (WS-Calendar) Technical Committee b. Statement of Purpose One of the most fundamental components of negotiating services is agreeing when something should occur, and in auditing when they did occur. Short running services have traditionally been handled as if they were instantaneous, and thereby dodged this requirement through just-in-time requests. Longer running processes may require significant lead times. When multiple long-running services participate in the same business process, it may be more important to negotiate a common completion time than a common start time. Central coordination of such services reduces interoperability as it requires the coordinating agent to know the lead time of each service. Other processes may have multiple and periodic occurrence. Identical processes may need to be requested on multiple schedules. Other processes must be requested to coincide with or avoid human interactions. An example is a process that occurs on the first Tuesday of every month. Others may need to be completed on schedules that vary by local time zone. Physical processes are now being coordinated by web services. Building systems and industrial processes are operated using oBIX, BACnet/WS, LON-WS, OPC XML, and a number of proprietary specifications including TAC-WS, Gridlogix EnNet, and MODBUS.NET. Energy use in buildings can be reduced while improving performance if building systems are coordinated with the schedules of the buildings occupants. An increasing number of specifications envision synchronization of processes through mechanisms including broadcast scheduling. Efforts to build an intelligent power grid (or smart grid) rely on coordinating processes in homes, offices, and industry with projected and actual power availability, including different prices at different times. Two active OASIS Technical Committees require a common means to specify schedule and interval: Energy Interoperation (EITC) and Energy Market Information Exchange (EMIX). Emergency management coordinators wish to inform geographic regions of future events, such as a projected tornado touchdown, using EDXL. These efforts would benefit from a common standard for transmitting schedule and interval. For human interactions and human scheduling, the well-known iCalendar format is used. Today, there is no equivalent standard for web services. As an increasing number of physical processes are managed by web services, the lack of a similar standard for scheduling and coordination of services becomes critical. The goal of WS-Calendar is to adapt the existing specifications for calendaring and apply them to develop a standard for how schedule and event information is passed between and within services. The standard should adopt the semantics and vocabulary of iCalendar for application to the completion of web service contracts. A calendar event without an associated contract is of little use. WS-Calendar will be a micro-specification, and then a micro-standard. WS-Calendar is unlikely to be used by itself. WS-Calendar will instead be used inside other specifications and standards, bringing a common scheduling function to diverse interactions in different domains. c. Scope of Work of the WS-Calendar Technical Committee The Committee will start work with the canonical XML serialization of the updated iCalendar (IETF RFC 5545), hereafter referred to as iCalendar XML, as developed by the Calendaring and Scheduling Consortium (CalConnect.org) This work will provide the vocabulary for use in this web service component. The committee will also use as a starting point the forthcoming calendaring web service specifications being developed by the CalConnect. This specification provides the basic mechanism for creating, updating, and deleting calendar events that are common to all calendars and schedules. The committee expects that use cases and requirements will be contributed by other groups, including the NAESB task forces on smart grid prices and schedules for DR/DER as well as the work done within the oBIX TC to schedule building systems. These use cases will test the completeness and functionality of the specification. The committee will develop additional Calendar functionality in later work, both in revisions and new specifications. The committee will also accept additional use cases for profile development, centralizing profile development to ensure consistency and interoperation of the additional schedule- and interval-related components. d. A list of deliverables, with projected completion dates. The committee will deliver a standard schema and semantics for schedule and interval information for use in other web services. This specification will be derived from and compatible the existing iCalendar XML specification and offer some or all of the functionality of that specification. The completed specification should include a standard for referring to instances of iCalendar XML within a larger payload, as well as a means to refer to objects external to the iCalendar XML instances. A single calendar object may be referenced by multiple contracts. A series of calendar events may reference a single contract. The committee will deliver a specification for creating, retrieving, updating, and deleting calendar events on a schedule. This specification will be based on the forthcoming calendar web service specifications developed by the CalConnect. Geoposition is an optional component of the iCalendar XML structure. Several of the use cases would benefit from geo-location. Some benefit more from a point, and some from a region or polygon. The committee work will include recommendations on how to reference geospatial information, both point and polygon, from within schedule and interval components. Preference will be given to specifications promulgated by the Open Geospatial Consortium (OGC, http://www.opengeospatial.org/ ). The committee will encourage members and others to develop reference implementations of the schedule components necessary to support the NAESB and oBIX use cases as described above. These implementations will test the completeness and functionality of the specification. These profiles will be donated to the EMIX, EITC, and oBIX Technical Committees at completion of the initial version of WS-Calendar. The committee may choose to incorporate additional use cases from other sources into its initial work. Version 1 of the specification and reference implementation for building systems and smart grid interactions are anticipated to be complete six months after the initial meeting. This is an aggressive schedule, in support of the NIST smart grid priority actions, (http://collaborate.nist.gov/twiki-sggrid/bin/view/SmartGrid/PAP04Schedules) and dependent on aggressive results from the other priorities as well. The committee will add additional functionality to later versions of the specification as agreed upon by the committee. The committee will also address additional use cases from additional domains for reference implementation, with a goal of to ensuring consistency and interoperation of any additional Calendar and Schedule-related components. e. IPR Mode for the Committee The Committee will operate under the OASIS Non-Assert mode. f. Anticipated audience or users of the WS-Calendar specification i. oBIX plans to use the scheduling specification for exchange of information with enterprise and external services. There is a natural and easy use case for oBIX that looks like "Conference room scheduled for 17 people at 3:00, tell building systems to establish temperature/humidity/warm up equipment by 3:00 Ventilation adequate for 17 people and continue to do so for the full hour" (www.oasis-open.org/committees/obix/) ii. Collaborative energy presents a number of use cases for coordinating Demand Response (DR), Distributed Energy Resources (DER), and other transactions associated with the power grid. These economic transactions need scheduling both for time of day pricing and for scheduled power generation and use. This work is being done in the Energy Interoperation TC (EITC) (www.oasis-open.org/committees/energyinterop/) Current EITC work plans anticipate incorporating this work. iii. Schedule & interval are critical parts of energy product definition, for both current and forward energy markets. This work is being done in the Energy Market Information Exchange (EMIX) TC (www.oasis-open.org/committees/emix/) Current EMIX work plans anticipate incorporating this work. iv. Emergency management would like to be able to transmit warnings and predictions of upcoming events. A common scheduling component would aid in cross-domain communications. A schedule component has been anticipated for future EDXL communications (http://www.oasis-emergency.org/committees) v. BPEL does not currently have any good way to handle the repeating event or several time coordinated events. A specification for scheduling could be incorporated in future versions of BPEL and its offshoot BPEL4People (www.oasis-open.org/committees/bpel4people/) vi. The OSCRE developed specification for the exchange of service work orders would benefit from the addition of a common scheduling and coordination function, including one which supports repetitive scheduling. Such a specification could also be used to specify windows during which the performance of work would minimally inconvenience building occupants. Alignment of building performance and tenant activity may become part of new business interactions such as Green Leases. Further work in this area would be developed by PISCES (http://web.pisces.co.uk/) vii. Electronic medical records and shared medical services are receiving growing attention. Many medical services are provided by many service providers working, occasionally, in concert. A common calendaring function would aid in coordinating these services across organizational boundaries to the patients benefit. viii. HAVE (Hospital Availability Exchange) could be improved if equipment availability and maintenance schedules could easily be shared in advance. HAVE is part of the OASIS Emergency Interoperability suite section (http://www.oasis-emergency.org/committees) ix. The Green Grid (www.TheGreenGrid.org) is concerned with the interactions between data centers and the critical resources that support them. These resources symmetrically share availability and planned maintenance information with the data center. x. The OASIS Technical Committee for WS-Device Discovery and Device Profiles (WS-DD) includes members with an interest in devices of concern to the oBIX, Demand-Response, and Green Grid. A schedule and interval specification could add an availability component to the Device Profile. g. Language of the Technical Committee The language of the committee shall be English. 2. Non-Normative Information on WS-Calendar a. Similar Work being done in OASIS or Other Organizations The definitive work on schedule and interval is the IETF standards iCalendar RFC2445, iTIP RFC2446, and iMIP RFC2447. Those standards are being updated for extensibility by the Calendar and Scheduling Consortium (www.calconnect.org) as RFC 5546, a draft updated ITIP, and an updated iMIP. CalConnect plans to contribute a canonical XML serialization of iCalendar to the technical committee. Standards for Calendaring, or for specifying schedule, and interval include but are not limited to: i. iCalendar, also known as RFC 5545 (http://www.ietf.org/rfc/rfc5545.txt) iCalendar describes the base semantics and vocabulary to be delivered. The committee may choose to limit the functionality included to a subset of that offered by iCalendar. ii. hCalendar is a simple, open, distributed calendaring and events format, based on RFC 2445, (http://microformats.org/wiki/hcalendar) suitable for embedding in HTML or XHTML. There are concerns and incompatibilities surrounding the use of hCalendar. See http://www.sitepoint.com/blogs/2008/06/25/bbc-rejects-hcalendar-microformat… iii. HTML 5.0 defines microdata, including a calendar component (http://www.w3.org/TR/html5/microdata.html#vevent) The vevent is a fork off an earlier version of iCalendar. Currently, we anticipate that HTML 5.0 will instead reference the iCalendar XML specification. iv. Open Building Information Exchange (oBIX) has worked since May 2008 to solve this problem within an OASIS TC. This work is incomplete. (http://lists.oasis-open.org/archives/obix/) v. The Open Knowledge Initiative (OKI) has developed an Open Service Interface Definition (OSID) for Scheduling. The Scheduling OSID provides a means of associating Agents with specific activities (ScheduleItems). This OSID provides a way for an application to integrate or use an external calendaring system, such as an existing Enterprise calendar system. http://www.mirrorservice.org/sites/download.sourceforge.net/pub/sourceforge… vi. CalDAV is a protocol to access server-based schedules and calendars by means of extensions to the WEBDAV protocol. CalDAV is also referred to as RFC 4791 (http://www.ietf.org/rfc/rfc4791.txt) vii. Microsoft offers the WS-Exchange functions for calendaring. http://msdn.microsoft.com/en-us/library/aa564001(EXCHG.80).aspx http://msdn.microsoft.com/en-us/library/aa564690(EXCHG.80).aspx viii. Google calendar defines an XML API for calendar activity with growing use in devices such as Android phones. Interoperating with this API is incorporated into the mission of CalConnect. (http://code.google.com/apis/calendar/data/2.0/developers_guide_protocol.htm…) As well as these schedule and interval, the iCalendar format includes a Geo-position element, which has been limited to a point. Several of the use cases for WS-Calendar would benefit from geo-location. Some would benefit more from a point, and some from region or polygon. This suggests that an additional source of IP for WS-Calendar would be at: ix. The Open Geospatial Consortium (OGC) offers standards for the interchange of geospatial data. The OGC is the preferred source for micro-specifications of geospatial data by WS-Calendar. (http://www.opengeospatial.org/) The committee would reach out to the Consortium for advice as to which geospatial standards to use. b. Date and Time of the First Meeting The first meeting will be February 26 at 2pm US Eastern Time. The meeting will be by teleconference sponsored by CalConnect. c. On-Going Meeting Schedule We anticipate the committee will meet weekly by teleconference sponsored by CalConnect or other TC members. d. Contact Information for TC Supporters David Thewlis, Dave.Thewlis(a)calconnect.org, CalConnect David Wollman, david.wollman(a)nist.gov , NIST David Holmberg, david.holmberg(a)nist.gov , NIST Ron Bernstein, ron(a)lonmark.org , LonMark International Jeremy Roberts, jeremy(a)lonmark.org , LonMark International David Burke, dburke(a)tibco.com, TIBCO Software Inc Larry Lackey, llackey(a)tibco.com , TIBCO Software Inc Derek LaSalle, derek.n.lasalle(a)jpmorgan.com , JP MorganChase Marquart Franz, marquart.franz(a)siemens.com , Siemens Bob Old, bob.old(a)siemens.com , Siemens Michel Kohanim, michel(a)universal-devices.com William Cox, wtcox(a)coxsoftwarearchitects.com Toby Considine, Toby.Considine(a)unc.edu , University of North Carolina e. Name, Email Address, and Statement of Support from Primary Representatives of Organizational Members * David Thewlis, (Dave.Thewlis(a)calconnect.org) CalConnect: The Calendaring and Scheduling Consortium supports the formation of the OASIS WS-Calendar Technical Committee. * NIST: David Flater (dflater(a)nist.gov ): NIST supports the formation of the OASIS WS-Calendar Technical Committee. * LonMark International: Ron Bernstein (ron(a)lonmark.org ): We are in full support. * TIBCO Software Inc: David Burke (dburke(a)tibco.com ): TIBCO will support the WS-Calendar initiative. * JPMorganChase: Derek LaSalle (derek.n.lasalle(a)jpmorgan.com ): As head of Information Architecture at the JPMorgan Investment Bank, I support the formation of the OASIS WS-Calendar Technical Committee. * Siemens AG: Marquardt Franz (marquart.franz(a)siemens.com ): As Siemens AG primary OASIS representative, Siemens can be a supporter of OASIS WS-Calendar TC. * University of North Carolina: Toby Considine (Toby.Considine(a)unc.edu) The University of North Carolina supports the formation of the WS-Calendar Technical Committee as described in the WS-Calendar draft charter. f. Committee Convener David Thewlis, Calendaring and Scheduling Consortium g. Member Section WS-Calendar expects to affiliate with the OASIS Blue Member Section h. List of Contributors of Existing Technical Work The TC will base its work on the IETF iCalendar RFCs. Other contributions are pending. i. Draft Frequently Asked Questions None. j. Proposed Working Title and Acronym for the Specification(s) to be Developed by the TC OASIS Common Scheduling. --------------------------------------------------------------------- This email list is used solely by OASIS for official consortium communications. Opt-out requests may be sent to member-services(a)oasis-open.org, however, all members are strongly encouraged to maintain a subscription to this list. -- Andreas Savva Fujitsu Laboratories Ltd

1 0

Time Constraints Profile
by Dominic Battre 10 Dec '09

10 Dec '09

Dear GRAAP members, we have seen in various discussions that there seems to be a frequent desire for a standardized term language to express when a service shall be delivered. Examples are: - Making a hardware reservation of a cluster for interactive use - Co-allocation of resources of various types (hardware, network, licenses, ...) - Defining a deadline for the completion of a job We have had a discussion about this in Banff after which Oliver and I have prepared a proposal for a Time Constraints Profile for WS-Agreement. This proposal has been uploaded here: https://forge.gridforum.org/sf/go/doc15832?nav=1 We would be eager to hear your comments. - Is the proposal clear? - Is the proposal complete? - Does the proposal satisfy your needs? Best regards, Dominic

6 9

RV: Time Constraints Profile
by Carlos Müller Cejás 10 Dec '09

10 Dec '09

Hello Costas and Dominic, I am Carlos Müller (University of Seville) we have been working in proposals with WS-Agreement since 2007 and after reading your emails, I think that you may find interesting our proposal to extend the temporal-awareness of WS-Agreement presented at the International Conference on Service Oriented Computing celebrated (Vienna, Austria, 2007). In such work we proposed a DSL or an XML schema (showed as an UML class diagram) to specify any kind of validity period disjoint or not, and periodical or not. Moreover, we give a concrete way to include such validity periods for any agreement element of a WS-Agreement document by using the extension points of WS-Agreement specification. You can take the paper and the XML schema from http://www.isa.us.es/wsag/, in the section "TEMPORAL-AWARE WS-AGREEMENT", which is the first button above. If you have any question or comment, please feel free to contact me by my email, phone or even by this list (I have just joined few minutes ago because a colleague has said to me the discussion of this topic). Best Regards. Carlos Müller cmuller(a)us.es University of Seville. (+34 954 553 868) (+34 609 865 920) mobile phone ---------- Forwarded message ---------- From: Dominic Battre <mailinglists(a)battre.de> Date: Thu, Dec 10, 2009 at 7:13 PM Subject: Re: [GRAAP-WG] Time Constraints Profile To: "Constantinos (Costas) Kotsokalis" <ckotso(a)admin.grnet.gr> Cc: GRAAP-WG <graap-wg(a)gridforum.org> Hello Costas, I thought about this for time. My point of view is the following: I can use my calendar application and define appointments for "every day from now until next Friday, 9am-5pm". After entering this appointment and going to the calendar view, I see one appointment each day. So "every day from now until next Friday, 9am-5pm" was just an intensional description of what can be expressed by an extensional description as well (see http://en.wikipedia.org/wiki/Intensional_definition) So what are the advantages and disadvantages of an intensional description? 1) Positive: compact representation 2) Negative: difficult to model, negotiate and evaluate adherence 3) Positive: can be used to model infinite number of repetitions (every day until the end of the world) I think that 3) has no real usecase as contracts should contain a well defined end. Considering 1) and 2) I am still in favor of the extensional description. "every day from now until next Friday, 9am-5pm" becomes just "2009/12/10 9am-5pm, 2009/12/11 9am-5pm, ..., 2009/12/18 9am-5pm". When the user enters an SLA its GUI can still present "every day from now until next Friday, 9am-5pm" but just render it as an extensional set. Each individual time frame could be modeled as one SDT+GT. I think the extensional description has the same expressiveness (as mentioned, I don't see 3) as a usecase for us) but is easier to handle and creates a leaner specification. Best regards, Dominic On 12/07/2009 05:17 PM, Constantinos (Costas) Kotsokalis wrote: > Hi Dominic, > > Recurring patterns for service usage is something that is needed in many > cases, even if not allowed by current technology/service providers. In > an example scenario where someone rents VMs to execute enterprise > operations s/w on them, (s)he would certainly prefer to load-balance > over a number of them available during working hours, and half or less > that number outside working hours, to save money. I know this is not > something that current cloud providers offer (to the extent I'm aware > of, at least) but I believe it's a realistic need, and fits with fully > dynamic scaling scenarios. > > On the same time, I do agree that it increases complexity, especially if > one is willing to include constructs such as "on the first Monday of > every month" etc. > > Just my E0.02. > > Best regards, > > Costas > > > On 7 Dec 2009, at 14:39, Dominic Battre wrote: > >> Hello Costas, >> >> it would certainly be a possible extension. >> >> The question is do we want it? If we end up translating ical to XML we >> come to a specification that is extremely powerful but very difficult >> to implement. >> >> Our idea was to use the simplest language that would be useful. >> Therefore, I would like to ask you and the others: Do you need >> something like "every day, 9am-5pm"? >> >> Best regards, >> >> Dominic >> >> Constantinos (Costas) Kotsokalis wrote: >>> Hi Dominic, >>> Would you see fit to augment this also with some construct for >>> defining periodic durations? E.g. to be able to say "every day, >>> 9am-5pm", or things like that. >>> Best regards, >>> Costas >>> On 7 Dec 2009, at 13:43, Dominic Battre wrote: >>>> Dear GRAAP members, >>>> >>>> we have seen in various discussions that there seems to be a frequent >>>> desire for a standardized term language to express when a service shall >>>> be delivered. >>>> >>>> Examples are: >>>> >>>> - Making a hardware reservation of a cluster for interactive use >>>> >>>> - Co-allocation of resources of various types (hardware, network, >>>> licenses, ...) >>>> >>>> - Defining a deadline for the completion of a job >>>> >>>> We have had a discussion about this in Banff after which Oliver and I >>>> have prepared a proposal for a Time Constraints Profile for >>>> WS-Agreement. This proposal has been uploaded here: >>>> >>>> https://forge.gridforum.org/sf/go/doc15832?nav=1 >>>> >>>> We would be eager to hear your comments. >>>> >>>> - Is the proposal clear? >>>> >>>> - Is the proposal complete? >>>> >>>> - Does the proposal satisfy your needs? >>>> >>>> Best regards, >>>> >>>> Dominic >>>> -- >>>> graap-wg mailing list >>>> graap-wg(a)ogf.org >>>> http://www.ogf.org/mailman/listinfo/graap-wg >> > > -- graap-wg mailing list graap-wg(a)ogf.org http://www.ogf.org/mailman/listinfo/graap-wg

1 0

OGF 27 Minutes and Status Quo
by Philipp Wieder 13 Nov '09

13 Nov '09

Dear All, please find the minutes from OGF 27 here [1]. I would like to thank all participants for the intense discussion (which even resulted in scheduling a fourth session). The public comment period of our WS-Agreement document has ended. The document and the comments can be found here [2]. We will address the comments asap and return the document to the OGF editorial process. Last but not least we (finally) make good progress regarding the specification of the WS-Agreement Negotiation specification. Based on the discussion at OGF 27 we had this Tuesday an informal meeting in Sankt Augusin, Germany. I would say we converge. The upated material will be published soon. We also have two stakeholders, the SmartLM [3] and the SLA4D-Grid [4] projects, which support specification and implementation of the (draft) specification. More soon ... Best regards, Philipp. [1] http://forge.gridforum.org/sf/go/doc15811?nav=1 [2] http://www.ogf.org/gf/docs/?archived [3] http://www.smartlm.org/ [4] http://www.sla4d-grid.de/

1 0

WS-Agreement experience document in public comment now
by Wolfgang Ziegler 02 Oct '09

02 Oct '09

Dear GRAAPians, as the subject says the WS-Agreement experience document has finally found its way to the public comments web-page http://www.ogf.org/gf/docs/?public_comment The deadline for comments is October 30, please take the opportunity to review and comment this document. Don't forget that not only comments proposing modifications are welcome but comments saying this document is fine are also useful. This is one of the final steps before WS-Agreement can transition from a proposed recommendation to a full recommendation. Given the wide range of implementations and public awareness the spec has already achieved this transition is actually overdue ;-) Hope to meet many of you in two weeks in Banff where we probably will have already received first comments. Best regards Wolfgang -- Wolfgang Ziegler www.scai.fraunhofer.de/ziegler.html Fraunhofer-Institute for Algorithms and Scientific Computing (SCAI) Schloss Birlinghoven, D-53754 Sankt Augustin, Germany Tel: +49 2241 14 2258; Fax: +49 2241 14 42258 SmartLM - Software License Technology for Grids, Clouds, SOA: www.smartlm.eu CoreGRID Network of Excellence www.coregrid.net Institute on Resource Management and Scheduling www.coregrid.net/irms

1 0

Final version of the experience document and last call
by Wolfgang Ziegler 31 Aug '09

31 Aug '09

Dear GRAAPians, the last editing is now finished and the experience document is ready to be submitted to the OGF editor to enter the public comment period. The last version can be found in the GRAAP gridforge space: https://forge.gridforum.org/sf/docman/do/downloadDocument/projects.graap-wg… Before submission the working group has one week time to send last comments to be considered before submission to the OGF editor. Please send you comments before Tuesday, September 8. Best regards Wolfgang -- Wolfgang Ziegler www.scai.fraunhofer.de/ziegler.html Fraunhofer-Institute for Algorithms and Scientific Computing (SCAI) Schloss Birlinghoven, D-53754 Sankt Augustin, Germany Tel: +49 2241 14 2258; Fax: +49 2241 14 42258 SmartLM - Software License Technology for Grids, Clouds, SOA: www.smartlm.eu CoreGRID Network of Excellence www.coregrid.net Institute on Resource Management and Scheduling www.coregrid.net/irms

1 0

GRAAP sessions at OGF 27
by Wolfgang Ziegler 27 Aug '09

27 Aug '09

Dear GRAAPians, as promised here my proposal for 3 sessions during OGF 27 Session#1 State of the WG Activities since last OGF State of the Experience Document Presentation of the SmartLM implementation Discussion Session#2 Presentation(s) Discussion of Negotiation and re-Negotiation Work on Negotiation Session#3 Work on the Negotiation specification Assignment of contributions Planning until OGF 28 Please let me know - whether you want to add/remove something to/from the agenda or modify the sequence - if you are interested in presenting own work on negotiation and/or re-negotiation which you feel should be included into the OGF specification The deadline for session requests is tomorrow (August 28). Thus, please send your comments before tomorrow 14:00 CST. Best regards Wolfgang -- Wolfgang Ziegler www.scai.fraunhofer.de/ziegler.html Fraunhofer-Institute for Algorithms and Scientific Computing (SCAI) Schloss Birlinghoven, D-53754 Sankt Augustin, Germany Tel: +49 2241 14 2258; Fax: +49 2241 14 42258 SmartLM - Software License Technology for Grids, Clouds, SOA: www.smartlm.eu CoreGRID Network of Excellence www.coregrid.net Institute on Resource Management and Scheduling www.coregrid.net/irms

1 0

Group status update
by Wolfgang Ziegler 21 Aug '09

21 Aug '09

Dear GRAAPians, as the next OGF meeting in Banff is approaching I take the opportunity to update you on the status of the WG. First of all the experience document is almost complete, please check out the document here https://forge.gridforum.org/sf/docman/do/downloadDocument/projects.graap-wg… and comment. It needs a bit of editorial polishing and then it will be sent to the list again for a last call for comments. Our objective is to send it to the OGF editor before the next OGF. We expect WS-Agreement to become a full recommendation of the OGF by end the year. Thanks again to all who contributed to the document. The second point is the further work on adding negotiation and re-negotiation capabilities to the WS-Agreement spec v1.0. We made some progress on this during the last OGF and between and already have an implementation for the proposed negotiation extension. This will be presented at OGF in Banff. Philipp is currently working on putting a GFD together with the proposed extensions, more to come. Third, we plan 3 GRAAP-WG sessions in Banff, all with a focus on the planned negotiation and re-negotiation extensions. I will send a proposal for the sessions next week and also request the sessions end of next week. Finally, I am about to change our living charter to better reflect the current activities towards negotiation. Best regards Wolfgang -- Wolfgang Ziegler www.scai.fraunhofer.de/ziegler.html Fraunhofer-Institute for Algorithms and Scientific Computing (SCAI) Schloss Birlinghoven, D-53754 Sankt Augustin, Germany Tel: +49 2241 14 2258; Fax: +49 2241 14 42258 SmartLM - Software License Technology for Grids, Clouds, SOA: www.smartlm.eu CoreGRID Network of Excellence www.coregrid.net Institute on Resource Management and Scheduling www.coregrid.net/irms

1 0

OGF 26 session
by Philipp Wieder 29 May '09

29 May '09

Dear GRAAP members, please find the minutes and a number of slides from the GRAAP session at Chapel Hill here: http://forge.ogf.org/sf/go/projects.graap-wg/docman.root.meeting_materials_…. We have a number of document work and actions. For that, we will set up tasks on GridForge and contact the responsible persons. Best regards, Philipp.

2 3

Call for Papers: Service Level Agreements in Grids Workshop 2009
by Wolfgang Ziegler 09 May '09

09 May '09

Dear GRAAPians, as in the previous years we are organising the annual SLA in Grids Workshop as part of the IEEE Grid conferences. This year Grid 2009 will he co-located with OGF27 in Banff, which allows to participate in both events without additional travel effort and expenses. Please consider submitting a paper to the workshop and distribute this call among your colleagues. Accepted papers will be published in the CoreGRID Springer Series. Thanks & best regards Wolfgang -- Wolfgang Ziegler www.scai.fraunhofer.de/ziegler.html Fraunhofer-Institute for Algorithms and Scientific Computing (SCAI) Schloss Birlinghoven, D-53754 Sankt Augustin, Germany Tel: +49 2241 14 2258; Fax: +49 2241 14 42258 SmartLM - Software License Technology for Grids, Clouds, SOA: www.smartlm.eu CoreGRID Network of Excellence www.coregrid.net Institute on Resource Management and Scheduling www.coregrid.net/irms -------------------------------------------------------------------------------- Call for Papers Service Level Agreements in Grids Workshop October 13, 2009 Banff, Canada http://www.coregrid.net/mambo/content/view/786/1/ to be held in conjunction with The 10th IEEE International Conference on Grid Computing (Grid 2009) October 13 - 15, 2009 Banff, Canada http://www.grid2009.org/ -------------------------------------------------------------------------------- DESCRIPTION As Grids and service-oriented architectures evolved to a common infrastructure for providing and consuming services in research and commercial environments, mechanisms are needed to agree on the objectives and the quality of such service provision. There is a clear trend to use electronic contracts between service consumers and one or more service providers, in order to achieve the necessary reliability and commitment on both sides. Service Level Agreements (SLAs) are the means to model and manage such contracts in a unified way. This workshop will provide a forum to present current research and up-to-date solutions from research and business communities. The workshop considers Grids but also generic models for SLA management. That is, market-economic strategies, negotiation, or monitoring are also of interest. TOPICS OF INTEREST Topics of interest for the Service Level Agreement in Grids workshop include but are not limited to: * Areas benefiting from SLAs * Languages to express SLAs (e.g. SLOs, BLOs, QoS, Guarantees, Penalties) * Protocols to conclude and negotiate SLAs * Technologies for management and observation of SLAs * Static vs. Dynamic SLAs * Business models & Grid economy * Negotiation and agreement protocols and strategies * Validation techniques for SLA parameters * Comparison and matchmaking of SLA and policy descriptions * Managing user expectations via SLAs * Multi-party SLAs and SLA chaining * SLA-based resource discovery, co-scheduling and resource reservation * Registry Services and repositories for SLA * SLA-based trust management including VOs * Monitoring, provisioning, enforcement of SLAs PROCEEDINGS Accepted papers will be published in the CoreGRID Springer Series. PAPER SUBMISSIONS Authors are invited to submit manuscripts reporting original unpublished research and recent developments on the topics of interest. Submitted papers should be formatted according to the CoreGRID Springer style format (please see http://www.coregrid.net/mambo/content/view/360/332) and should not exceed 10 pages including figures and references. Papers should be submitted electronically in PDF format by sending it as an e-mail attachment to sla-workshop2009(a)scai.fraunhofer.de. All papers will be peer reviewed and the comments will be provided to the authors. IMPORTANT DATES Submissions due: July 26, 2009 Notification of acceptance: August 24, 2009 Camera Ready: September 30, 2009 Workshop: October 13, 2009 PROGRAM CHAIRS Philipp Wieder, Dortmund University of Technology, Germany Ramin Yahyapour, Dortmund University of Technology, Germany Wolfgang Ziegler, Fraunhofer Institute SCAI, Germany PROGRAM COMMITTEE Christiana Amza, University of Toronto, Canada Dominic Battré, TU Berlin, Germany Frances Brazier, Vrije University, Amsterdam, The Netherlands Asit Dan, IBM, US Wolfgang Gentzsch, DEISA, Germany Liviu Joita, Cardiff University, UK Bastian Koller, HLRS, Stuttgart, Germany Ioannis Kotsiopoulos, University of Manchester, UK Gregor von Laszewski, Rochester Institute of Technology, US Heiko Ludwig, IBM, US Toshi Nakata, NEC Research, Japan Julian Padget, Bath University, UK Shamima Paurobally, University of Westminster, London, UK Thomas Quillinan, VU University Amsterdam Omer Rana, Cardiff University, GB Igor Rosenberg, ATOS Origin, Spain Rizos Sakellariou, University of Manchester, UK Luigi Telesca, Create-Net, Italy Daniel Veit, University of Mannheim, Germany Oliver Wäldrich, Fraunhofer Institute SCAI, Germany Steven Willmott, UPC, Barcelona, Spain ADDITIONAL INFORMATION For further information send an email to sla-workshop2009(a)scai.fraunhofer.de Information about registration, accommodation and other relevant information regarding the Grid 2009 conference can be found at http://www.grid2009.org/.

1 0