You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

Problem Statement

There are multiple parties like event-driven workflows systems, monitoring system, usage & billing system would be interested in getting notification of a events in the cloud in near instantaneous manner. In CloudStack event could be state change of virtual or psychical resources, an action performed by user (action events), policy based events (alerts). Currently CloudStack has no notification mechanism to let the interested parties know of the occurrence of an event. Polling by invoking listEvents and listAlerts is the only way to know occurrence of events. Also there are no externsion hooks one can implement to get the event notification. Though there is StateListener interface which has both pre and post state transition event call back methods, only user VM resource has state listener implemented. Most of the resorces volume, network, nic, etc has states but does not have state machine and StateListener. So for a component interested getting notification need to get tightly coupled into orchestration workflow. For e.g, code to generate usage date (usage events) is spread across the orchestration components.

Proposal

This proposal is to introduce an in-process event bus in the management server and by which achieve event notifications. Scope of the event bus is only with in the management server, so only CloudStack components and extension plug-in's can be subscribers to the events. Goal of this proposal is to have bare minimum mechanism in the CloudStack code, using which more powerful notification mechanism (like SMS, email etc) can be built as CloudStack extensions.

Ideal requirements for such event bus is to be

  • light weight (a library)
  • provide simple interface
  • decouple the publisher and subscriber so that they need not be aware of other
  • powerful enough to provide filters for events of a type to wildcard (all events)

In order for CloudStack be able to generate rich set of events and have clean mechanism to generate events, its important to have state machine associated with every resource that is managed by CloudStack. So another goal of this proposal is to associate with every resource (User VM, Volume, Nic, Network, public IP, snapshot, template etc) with a state machine and generate events as part of the state change.

So the publisher in CloudStack will become that StateListeners associated with the resource.

  • introduce a state machine for all the virtual and physical resources which CloudStack manages and generate an event on state transition

Use cases

  • Usage/billing engines
  • AMQP
  • CMDB
  • pub/sub notification service

Discussion topics

Implementation

  • No labels