[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (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:all-tabpanel ] Tom Rutt updated CAMP-9: ------------------------ Proposal: https://www.oasis-open.org/apps/org/workgroup/camp/download.php/49894/camp-spec-v1.1-wd15-issue-9-v7.doc (was: https://www.oasis-open.org/apps/org/workgroup/camp/download.php/49892/camp-spec-v1.1-wd15-issue-9-v5.doc) Updated UML figures to reflect sensors and operations resources, ans posted v7 proposal > 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 > Priority: Critical > > 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]