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

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

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

Tobias Kunze  commented on CAMP-9:
----------------------------------

I support this cause, but favor (a) keeping the exact specification of attributes to expose entirely outside of the spec and (b) extending this capability to both ACs and PCs. IOW, we should leave the set of metrics that are exposed as well as their naming, representation and semantics (documentation) entirely outside of CAMP. As far as extending this to ApplicationComponents, a use case would be an application logging to log server X at log level Y. Exposing the sink and level in the AC could enable administrators to change those values in runtime.

Interestingly, this brings up the issue that we should specify a realtime write/notify API on the backside (facing the Component Implementation) that both PlatformComponents and ApplicationComponents can use, e.g. by registering a callback


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