OpenStack Branches Out with ‘Messaging as a Service’


It’s a rare enterprise cloud manager today who isn’t already familiar with OpenStack, the open source Infrastructure as a Service (IaaS) cloud computing project for building public, private and hybrid clouds. Included in OpenStack are several key components dedicated to virtual machine provisioning and management, storage, virtual disk management and more, but recently a new service made its debut.

Enter OpenStack Cloud Messaging as a Service, born out of last year’s OpenStack Grizzly Summit in San Diego, is a scalable message bus designed for use in sending and receiving information among applications that run on OpenStack clouds.

Marconi summary“The need for well understood intra-application messaging was one of the signs that new application design patterns beyond just the LAMP stack were needed,” explained Mark Atwood, director of open source engineering for HP Cloud, in a blog post last week.

A Developer Preview

Even as HP was “looking for a way to make its already-under-development application messaging service available to users of the HP Cloud,” Atwood wrote, the OpenStack Message Bus project was born at the San Diego Grizzly Summit in October and code-named Marconi.

“When the Marconi project appeared, HP decided that instead of splitting the developer community in a pointless API standards war, it made more sense to clone and track the public Marconi API and then contribute to the open source Marconi project itself,” he wrote.

Announced in April, HP Cloud Messaging uses the emerging OpenStack Marconi API standard and is now available as a developer preview [] free of charge. Instructions for trying it out are provided in Atwood’s blog post.

A Message Bus for the Cloud

So what is this new service, exactly?

Basically, it’s a project designed to fill OpenStack’s growing need for a “robust, Web-scale message queuing service to support the distributed nature of large Web applications,” as it’s put on the Marconi wiki page. Marconi is defined as a highly available, modular, scalable message bus for the cloud.

“Our aim is to create an open alternative to SQS (producer-consumer) and SNS (pub-sub), for use in applications that run on OpenStack clouds,” the project team adds. “The project will define a clean, RESTful API, use a modular architecture, and will support unified pub-sub and job-queuing semantics.”

Users will be able to customize Marconi toward a wide variety of performance, durability, availability and efficiency goals. Use cases include distributing tasks among multiple workers, forwarding events to data collectors, publishing events to any number of subscribers, sending commands to one or more agents and requesting an action or getting information from an agent.

The video, below, from earlier this month provides a more detailed overview of the Marconi project.

‘A Key Component’

“This messaging service is another example of a key OpenStack component that is evolving quickly as more large enterprise and service providers adopt OpenStack cloud infrastructure,” Jay Lyman, a senior analyst for enterprise software at 451 Research, told

“While the main OpenStack components of compute, networking and storage provide the basics for building cloud computing infrastructure, most users try to integrate these and other OpenStack components with existing, legacy and other infrastructure, tooling, monitoring and management,” Lyman explained. “Identity services, for example, is another component of OpenStack that has progressed and matured relatively quickly with more large users, particularly enterprise organizations.”

Now, this new messaging service is “another example of a key component to these organizations, and I expect it will develop in similar fashion,” Lyman concluded.” frameborder=”0