OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

camp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Commented: (CAMP-9) Support sensors and effectors on components via API


    [ http://tools.oasis-open.org/issues/browse/CAMP-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32211#action_32211 ] 

Gilbert Pilz commented on CAMP-9:
---------------------------------

W/regards to SENSORS/METRICS - I am a bit uncomfortable with surfacing dynamic values at the top-level of the resource. The problem with doing this is that it complicates PUT processing. If a resource contains, say, 6 attributes that are changing near continuously, it is effectively impossible to supply a representation of that resource that can legitimately claim to be a "complete replacement" (as HTTP requires).

I would prefer to group sensors/metrics, log entries, etc. in a sub-resource that only supports the GET method.

> Support sensors and effectors on components via API
> ---------------------------------------------------
>
>                 Key: CAMP-9
>                 URL: http://tools.oasis-open.org/issues/browse/CAMP-9
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: New Feature
>          Components: Spec
>            Reporter: Anish Karmarkar
>            Assignee: Alex Heneveld
>
> I'd like to be able to discover and access available sensors (or metrics or attributes) and available effectors (operations) on components in my application.
> For instance a WebServer might expose totalRequests as a sensor and updateWar(url) as an effector. It would be nice to be able to list these, query/subscribe to sensor values, and invoke effectors.
> (I like the autonomic computing terminology -- sensor/effector -- but happy to follow JMX terminology -- attribute/notification/operation -- or others.)
> This was raised by Alex Heneveld and was drupal issue # 1061

-- 
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

        


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]