[overlord-issues] [JBoss JIRA] (SRAMP-171) Enable WSLA artifacts to be associated with a service

Kurt Stam (JIRA) jira-events at lists.jboss.org
Fri May 31 14:33:54 EDT 2013


    [ https://issues.jboss.org/browse/SRAMP-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778539#comment-12778539 ] 

Kurt Stam commented on SRAMP-171:
---------------------------------

Example:

<?xml version="1.0"?>
<!--
    Service Deployment Information for a Condition Evaluation Service
    Authors: Heiko Ludwig, hludwig at us.ibm.com
             Richard P. King, rpk at us.ibm.com
    Date: December 6, 2001
-->
<SDIConditionEvaluationService
     xmlns="http://www.ibm.com/wsla"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://www.ibm.com/wsla WSLASDI.xsd"
     name="DemoSLA123" >
<!-- Definition of the Involved Parties, the signatory parties as well as
    the supporting ones -->
 <Party name="ZAuditing" xsi:type="SupportingParty"
        role=”ConditionEvaluationService”>
    <Action name="notification" partyName="YMeasurement"
                  xsi:type="wsla:WSDLGetPostActionDescriptionType">
      <Address>http://localhost:8080/wsla/
                      servlet/Condlet?com.ibm.wsla.cm.WSNotifier</Address>
    </Action>
 <Party>
 <Action name="notification"
                partyName="ZAuditing"
                xsi:type="WSDLSOAPActionDescriptionType">
           <WSDLFile>notification.wsdl</WSDLFile>
           <SOAPBindingName>soapnotification</SOAPBindingName>
           <SOAPOperationName>notification</SOAPOperationName>
        </Action>
 <Action name="notification"
                partyName="ZAuditing"
                xsi:type="WSDLSOAPActionDescriptionType">
           <WSDLFile>notification.wsdl</WSDLFile>
           <SOAPBindingName>soapnotification</SOAPBindingName>
           <SOAPOperationName>notification</SOAPOperationName>
        </Action>
<SLAParameter name="ResponseTimeThroughPutRatio"
                        type="float"
                        unit="milisconds / transactions">
        <Metric>ResponseTimeThroughPutRatioMetric</Metric>
</SLAParameter>
<SLAParameter name="TransactionRate"
                        type="float"
                        unit="transactions / hour">
        <Metric>Transactions</Metric>
</SLAParameter>
<SLAParameter name="Availability_CurrentDownTime"
type="long"
                        unit="minutes">
        <Metric>CurrentDownTime</Metric>
        <Communication>
          <Service>YMeasurement</Service>
          <Push>ZAuditing</Push>
        </Communication>
</SLAParameter>
<SLAParameter name="Availability_UpTimeRatio"
                        type="float"
                        unit="">
        <Metric>UpTimeRatio</Metric>
        <Communication>
          <Service>YMeasurement</Service>
          <Push>ZAuditing</Push>
        </Communication>
</SLAParameter>
<Obligations>
    <ServiceLevelObjective name="g1">
      <Obliged>ACMEProvider</Obliged>
      <Validity>
          <Start>2001-11-30T14:00:00.000-05:00</Start>
          <End>2001-12-31T14:00:00.000-05:00</End>
      </Validity>
      <Expression>
        <Or>
          <Expression>
            <Predicate xsi:type="Less">
              <SLAParameter>ResponseTimeThroughPutRatio</SLAParameter>
              <Value>0.5</Value>
            </Predicate>
          </Expression>
          <Expression>
            <Predicate xsi:type="Greater">
              <SLAParameter>TransactionRate</SLAParameter>
              <Value>10000</Value>
            </Predicate>
          </Expression>
        </Or>
      </Expression>
      <EvaluationEvent>NewValue</EvaluationEvent>
    </ServiceLevelObjective>
    <ServiceLevelObjective name="ga1">
      <Obliged>ACMEProvider</Obliged>
      <Validity>
          <Start>2001-11-30T14:00:00.000-05:00</Start>
          <End>2001-12-31T14:00:00.000-05:00</End>
      </Validity>
  <Expression>
    <Predicate xsi:type="Greater">
      <SLAParameter>Availability_UpTimeRatio</SLAParameter>
      <Value>0.97</Value>
    </Predicate>
  </Expression>
  <EvaluationEvent>NewValue</EvaluationEvent>
</ServiceLevelObjective>
<ServiceLevelObjective name="ga2">
  <Obliged>ACMEProvider</Obliged>
  <Validity>
      <Start>2001-11-30T14:00:00.000-05:00</Start>
      <End>2001-12-31T14:00:00.000-05:00</End>
  </Validity>
  <Expression>
    <Predicate xsi:type="Less">
      <SLAParameter>Availability_CurrentDownTime</SLAParameter>
      <Value>10</Value>
    </Predicate>
  </Expression>
  <EvaluationEvent>NewValue</EvaluationEvent>
</ServiceLevelObjective>
<ActionGuarantee name="ga3">
  <Obliged>ZAuditing</Obliged>
  <Expression>
    <Predicate xsi:type="Violation">
      <ServiceLevelObjective>ga1</ServiceLevelObjective>
    </Predicate>
  </Expression>
  <EvaluationEvent>NewValue</EvaluationEvent>
  <QualifiedAction>
    <Party>XInc</Party>
    <Action actionName="notification" xsi:type="Notification">
      <NotificationType>Violation</NotificationType>
      <CausingGuarantee>ga1</CausingGuarantee>
      <SLAParameter>Availability_UpTimeRatio</SLAParameter>
    </Action>
  </QualifiedAction>
  <ExecutionModality>Always</ExecutionModality>
</ActionGuarantee>
<ActionGuarantee name="ga4">
  <Obliged>ZAuditing</Obliged>
  <Expression>
    <Predicate xsi:type="Violation">
      <ServiceLevelObjective>ga2</ServiceLevelObjective>
    </Predicate>
  </Expression>
  <EvaluationEvent>NewValue</EvaluationEvent>
  <QualifiedAction>
    <Party>XInc</Party>
    <Action actionName="notification" xsi:type="Notification">
      <NotificationType>Violation</NotificationType>
      <CausingGuarantee>ga2</CausingGuarantee>
      <SLAParameter>Availability_CurrentDownTime</SLAParameter>
    </Action>
  </QualifiedAction>
  <ExecutionModality>Always</ExecutionModality>
</ActionGuarantee>
<ActionGuarantee name="g2">
  <Obliged>YAuditing</Obliged>
  <Expression>
    <Predicate xsi:type="Violation">
      <ServiceLevelObjective>g1</ServiceLevelObjective>
107
WSLA Language Specification Version 1.0
</Predicate>
      </Expression>
      <EvaluationEvent>NewValue</EvaluationEvent>
      <QualifiedAction>
        <Party>XInc</Party>
        <Action actionName="notification" xsi:type="Notification">
          <NotificationType>Violation</NotificationType>
          <CausingGuarantee>g2</CausingGuarantee>
          <SLAParameter>ResponseTimeThroughPutRatio
TransactionRate</SLAParameter>
        </Action>
      </QualifiedAction>
      <ExecutionModality>Always</ExecutionModality>
    </ActionGuarantee>
    <ActionGuarantee name="g3">
      <Obliged>YAuditing</Obliged>
      <Expression>
          <Predicate xsi:type="Greater">
            <SLAParameter>ResponseTimeThroughPutRatio</SLAParameter>
            <Value>0.4</Value>
          </Predicate>
      </Expression>
      <EvaluationEvent>NewValue</EvaluationEvent>
      <QualifiedAction>
        <Party>XInc</Party>
        <Action actionName="notification" xsi:type="Notification">
          <NotificationType>Information</NotificationType>
          <CausingGuarantee>g3</CausingGuarantee>
          <SLAParameter>ResponseTimeThroughPutRatio</SLAParameter>
        </Action>
      </QualifiedAction>
      <ExecutionModality>Always</ExecutionModality>
    </ActionGuarantee>
</Obligations>
</SDIConditionEvaluationService>
                
> Enable WSLA artifacts to be associated with a service
> -----------------------------------------------------
>
>                 Key: SRAMP-171
>                 URL: https://issues.jboss.org/browse/SRAMP-171
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Gary Brown
>            Assignee: Kurt Stam
>             Fix For: 0.3.0 - JBPM6 Integration
>
>         Attachments: WSLASpecV1-20030128.pdf
>
>
> WSLA will be used to represent the service level agreement properties related to response time and availability for a service. Therefore it should be possible to represent these documents in the repository and establish a relationship between them and the service contracts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the overlord-issues mailing list