[OASIS Issue Tracker] Updated: (SAF-14) Syndrome/Protocol generictemplate (with substitutable parameters)

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ http://tools.oasis-open.org/issues/browse/SAF-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeffrey Vaught updated SAF-14:
------------------------------

    Proposal: 
1.	First, I provide a use case where this template idea is required:
Detect symptom A & B where A.hostname=B.hostname and A.instancename='Blah'.  Fyi - A might be an application?
It would be great to allow "Blah" to be populated by the syndrome implementer.  
So, the syndrome might be published into the catalog by a Cloud provider as follows:
          Detect symptom A & B where A.hostname=B.hostname and A.instancename=?.

2.	Next, how would we support this notion in the spec:
We would need some wildcard character (such as the ?) to designate to the authoring tools that this value should be substituted.


> Syndrome/Protocol generic template (with substitutable parameters)
> ------------------------------------------------------------------
>
>                 Key: SAF-14
>                 URL: http://tools.oasis-open.org/issues/browse/SAF-14
>             Project: OASIS Symptoms Automation Framework (SAF) TC
>          Issue Type: Task
>            Reporter: Jeffrey Vaught
>            Assignee: Jeffrey Vaught
>
> Syndromes signature & Protocol directives could be generic in nature, containing substitutable parameters.
> For example, signature could be (in English, not xpath/xquery): if blah occurs {0} times within {1} minutes.
> The Syndrome/Protocol would be effectively instantiated by substituting meaningful values, such as "if blah occurs 3 times within 5 minutes.
> This is critical from the collaboration perspective, ie: Cloud provider could publish generic Syndromes, while consumers could instantiate those Syndromes per above.
> Notes
> Might require no changes to the spec.  Interfaces might better support this?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira