From Wolfgang.Ziegler at scai.fraunhofer.de  Fri Sep 12 08:58:53 2008
From: Wolfgang.Ziegler at scai.fraunhofer.de (Wolfgang Ziegler)
Date: Fri, 12 Sep 2008 15:58:53 +0200
Subject: [GRAAP-WG] GRAAP sessions at OGF 24 next week
Message-ID: <48CA759D.7030506@scai.fraunhofer.de>

Dear GRAAPians,

as agreed during the last OGF in Barcelona we will have two
sessions at OGF 24:


GRAAP#1 (90 mins)
Wednesday, September 17, 2:15 pm - 3:45 pm, Location: Creation

This session is focussing on the preparation of the experience document.
Agenda:
- Status of the Working group
- Working on the Experience Document


GRAAP#2 (90 mins)
Wednesday, September 17, 4:00 pm - 5:30 pm, Location: Creation
	
This session is dedicated to work on the negotiation protocol
Agenda:
- Result of last meeting and progress since then
- Defining the messages
- Role and handling of constraints



Best regards & see you there

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

              CoreGRID Network of Excellence   www.coregrid.net
                 Collaboration Gateway   www.coregrid.net/cg
    Institute on Resource Management and Scheduling   www.coregrid.net/irms
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 2093 bytes
Desc: S/MIME Cryptographic Signature
Url : http://www.ogf.org/pipermail/graap-wg/attachments/20080912/f23588e4/attachment.bin 

From o.f.rana at cs.cardiff.ac.uk  Tue Sep 16 09:38:48 2008
From: o.f.rana at cs.cardiff.ac.uk (Omer F. Rana)
Date: Tue, 16 Sep 2008 15:38:48 +0100
Subject: [GRAAP-WG] SLA examples
Message-ID: <48CFC4F8.5030004@cs.cardiff.ac.uk>

Dear Colleagues,

I was wondering if you have examples of:

1. Service Level Agreements (SLAs) that you have come across. These do 
not need to be in WS-Agreement format --
    any format would be fine.

2. If you have SLAs that have arisen from your own research/development 
projects that you are willing to share.

3. If you have SLAs that are encoded in WS-Agreement or some other 
commonly used specification.

I would like to create a repository of these, and will be making this 
generally accessible. Would be grateful for
pointers/examples.A personal email to o.f.rana at cs.cardiff.ac.uk would be 
great.

regards
Omer

-- 
http://www.cs.cf.ac.uk/User/O.F.Rana/index.html / work-fax:+44(0)29-2087-4598
work:+44(0)29-2087-5542 / other:+44(0)7956-299981 / distributed collaborative
computing / room n2.14 / school of computer science / cardiff university 
  queen's buildings / newport road / cardiff cf24 3aa / wales / uk 



From Oliver.Waeldrich at scai.fraunhofer.de  Fri Sep 26 03:57:15 2008
From: Oliver.Waeldrich at scai.fraunhofer.de (=?iso-8859-1?Q?Oliver_W=E4ldrich?=)
Date: Fri, 26 Sep 2008 10:57:15 +0200
Subject: [GRAAP-WG] Extension of agreement states for
	WS-Agreement-Negotiation
Message-ID: <001801c91fb5$dfcaeed0$51851a81@gelbwurz>

Dear all,

After the discussion in the GRAAP group concerning the extension of the
AgreementState port type for the negotiation protocol, it turned out that
this is not necessary. It is still possible to define substates for the
states defined in the WS-Agreement recommendation. The important
structures for this are listed below:

    <xs:simpleType name="AgreementStateDefinition">
        <xs:restriction base="xs:string">
            <xs:enumeration value="Pending"/>
            <xs:enumeration value="PendingAndTerminating"/>
            <xs:enumeration value="Observed"/>
            <xs:enumeration value="ObservedAndTerminating"/>
            <xs:enumeration value="Rejected"/>
            <xs:enumeration value="Complete"/>
            <xs:enumeration value="Terminated"/>
        </xs:restriction>
    </xs:simpleType>

AgreementStateDefinition defines the WS-Agreement states as an
enumeration.

    <xs:complexType name="AgreementStateType">
      <xs:complexContent>
        <xs:extension base="wsag:InnerAgreementStateType">
          <xs:sequence>
            <xs:element name="State"
type="wsag:AgreementStateDefinition"/>
          </xs:sequence>
        </xs:extension>
      </xs:complexContent>
    </xs:complexType>

    <xs:complexType name="InnerAgreementStateType">
        <xs:sequence>
            <xs:any minOccurs="0" namespace="##other"
processContents="lax"/>
        </xs:sequence>
    </xs:complexType>

The AgreementStateType defines one element State that can take a value
defined in AgreementStateDefinition. AgreementStateType also extends
InnerAgreementStateType, which allows extending AgreementStateType with an
abritary XML document. Therefore, it is possible to add a document in the
WS-Agreement-Negotiation namespace, which defines e.g. a substate for an
AgreementState.

How these extensions (e.g. substates) are defined, is then part of the
WS-Agreement-Negotiation specification. However, this approach would be a
fully compliant and compatible way to introduce substates in
WS-Agreement-Negotiation with respect to the base WS-Agreement
specification.


Best regards,
Oliver

-----------------------------------------------------------------------
                          Oliver W?ldrich
  Fraunhofer-Institute for Algorithms and Scientific Computing (SCAI)
         Schloss Birlinghoven, D-53754 Sankt Augustin, Germany
             Tel: +49 2241 14 2830; Fax: +49 2241 14 42830
 
           CoreGRID Network of Excellence   www.coregrid.net
Institute on Resource Management and Scheduling   www.coregrid.net/irms

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 4958 bytes
Desc: not available
Url : http://www.ogf.org/pipermail/graap-wg/attachments/20080926/0aaeaeaf/attachment.bin 

From Oliver.Waeldrich at scai.fraunhofer.de  Fri Sep 26 04:16:20 2008
From: Oliver.Waeldrich at scai.fraunhofer.de (=?iso-8859-1?Q?Oliver_W=E4ldrich?=)
Date: Fri, 26 Sep 2008 11:16:20 +0200
Subject: [GRAAP-WG] Example for extending the agreement state for ws
	agreement negotiation
Message-ID: <002201c91fb8$89fef200$51851a81@gelbwurz>

I just attached an example, how an extesion for an agreement state in
WS-Agreement-Negotiation could look like:


<wsag:AgreementState
xmlns:wsag="http://schemas.ggf.org/graap/2007/03/ws-agreement">
	<wsag:State>Terminated</wsag:State>
	<wsag-neg:NegotiationState
xmlns:wsag-neg="http://schemas.ggf.org/graap/2008/10/ws-agreement-negotiat
ion">
		<wsag-neg:SubState>Superseeded</wsag-neg:SubState>
	</wsag-neg:NegotiationState>
</wsag:AgreementState>


We could also allow some additional element here, that points to the new
created agreement.



Best regards,
Oliver

-----------------------------------------------------------------------
                          Oliver W?ldrich
  Fraunhofer-Institute for Algorithms and Scientific Computing (SCAI)
         Schloss Birlinghoven, D-53754 Sankt Augustin, Germany
             Tel: +49 2241 14 2830; Fax: +49 2241 14 42830
 
           CoreGRID Network of Excellence   www.coregrid.net
Institute on Resource Management and Scheduling   www.coregrid.net/irms

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 4958 bytes
Desc: not available
Url : http://www.ogf.org/pipermail/graap-wg/attachments/20080926/34047db4/attachment.bin