> Are there any use-cases for which it make sense to have publishers (that use > CloudStack API to publish) other than CloudStack? If its not overkill we can > have generic mechanism of publish/subscribe as service in CloudStack. I can > think of tenants workload VM's be able to leverage this and publish > something to subscribers.
There will be third party vendors who want to write plugins for CloudStack. I think a requirement for such a system includes - generic events (in practical terms, it shouldn't be done with enums or anything that tie extension into modifications done in the same place). - Provide domain separation between event publishers. (In practical terms, should be done with strings. Like java packages names). - Provide some generic categorization of the events (ALERTs, STATE change, etc) - mechanism to query the Events available - mechanism to subscribe to specific events/categories/domains --Alex
