Versions Compared

Old Version 17

changes.mady.by.user Murali Reddy

Saved on

compared with

New Version 18

changes.mady.by.user John Kinsella

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Usage/billing engines: a 3rd party Cloud Usage solution can implement a plug-in to CloudStack that subscribes to  CloudStack events and generates usage data, that is consumed by their usage software
  • AMQP plugin can put all the events on the a message queue, a AMQP message broker then can provide topic based notification to subscribers
  • pub/sub notification service can be implemented as Pluggable service in to CloudStack that provides rich API for event notifications (topics based subscription and notification) and deal with multi-tenancy, authentication&authorization issues

Discussion topics

  • Google Guava Event bus library which is under Apache License 2.0 seems to be good fit for implementing event bus in CloudStack. Its light-wieght and has simple interface but very powerful. But any other alternatives could be evaluated
  • If there is clustered management server setup then subscribers need to be present on the both management servers. Using a messaging queue servers like RabbitMQ can be used for event bus, but i thinks will add complexity into CloudStack. Are there any scenarios where having in-process event bus proposed will fall short in clustered management server setups?