Why OpenStack for PowerVC?

One of the big differences between PowerVC and other management solutions is the use of OpenStack as a foundation. Like many of you, I wondered why IBM chose OpenStack, so I asked someone who was intimately involved in that decision–Mike Williams, distinguished engineer for IBM Cloud Systems Software.

The overall goal for PowerVC was to provide robust management for clouds built on IBM Power Systems. Managing a cloud-computing infrastructure requires a different approach than managing a traditional IT infrastructure. IBM identified several key architectural requirements for this product:

  • The management software had to encompass servers, storage, and networking. The management silos of the past simply did not meet the needs of a cloud environment.
  • The management architecture needed to be flexible, reliable, and scalable. A management architecture based on a loosely coupled service-oriented architecture with well-defined interfaces fulfills this requirement well. The general concept was a kernel of core services surrounded by plug-in modules to provide management of specific resources. The management application also needed to scale both vertically and horizontally.
  • The architecture had to be adaptable to allow expansion to new resource types and new management operations without requiring changes to the underlying architecture.

OpenStack fits these requirements well. OpenStack has the concept of drivers to support different resources (plug-ability), a built in foundation of middleware (service-oriented architecture) and well defined APIs tying everything together. There is an extensive open source community around OpenStack and it has a well-established governance model, and design tenets based on a loosely coupled, resilient architecture that scales horizontally.

There was another pragmatic reason for IBM to use OpenStack as the base for PowerVC: by building on OpenStack, IBM was able to get PowerVC to the market much more quickly and spent more energy working on capabilities with higher client value rather than building infrastructure “plumbing”. 


It is important to note that PowerVC is a solution based on OpenStack, it is not OpenStack.

IBM built PowerVC based on the OpenStack architecture using OpenStack components, but IBM also provides enhancements and components that are not part of OpenStack, such as the management user interface and the Platform Enterprise Grid Optimizer (Platform EGO).

These extensions are designed to provide additional capability for our clients compared to the base capabilities provided by OpenStack. IBM  contributes to the OpenStack community, but some of our enhancements will remain proprietary to IBM.

openstack_powervcPowerVC is more than just OpenStack for Power. While other companies have delivered OpenStack offerings that are just big bags of technology, IBM built PowerVC on OpenStack technology to deliver a virtualization management solution for Power Systems.

As they say, “the proof is in the pudding” By building PowerVC on OpenStack, IBM has been able to deliver two releases in one year. This would have been impossible building it from scratch.


About Jay Kruemcke

Jay has had more than twenty years of experience in the information technology industry. Starting from a rather humble beginning at IBM, Jay became a mainframe systems support programmer. Eventually Jay joined the AIX operating systems development team early in that product's development. Jay leveraged technical skills that he built in systems management to establish himself as a member of the IBM Austin Executive Briefing Center. His expertise in systems management with the SAP ERP system enabled his first product management role, as the owner of the Tivoli management product for SAP. Over the next three years he established that product as a success with the help of a strong development team. Jay returned to AIX in a product management position initially focusing on managing new requirements for the AIX operating system. Jay established himself as a subject manager expert in AIX and Power Systems virtualization and became a frequent guest at conferences around the world. Jay succumbed to the dark side and spent four years in IBM marketing in which he introduced AIX version 6 and AIX version 7 and many product innovations including the first every open beta program for an AIX release and a significant restructuring of the AIX offering structure and prices. Jay was part of the cloud software development organization and and focused on managing development engagements for clients deploying clouds using Power Systems servers with PowerVC and related products. In March of 2016, Jay retired from IBM and started in a new role as a product manager for SUSE, the Open Software company. Jay new focus is on enterprise Linux for POWER and ARM processor based systems. The postings on this site solely reflect the personal views of the author and do not necessarily represent the views, positions, strategies or opinions of my employer. Follow me on twitter @mr_sles, @cloudrancher and @chromeaix.
This entry was posted in AIX & Power Systems Blogroll, Cloud. Bookmark the permalink.

2 Responses to Why OpenStack for PowerVC?

  1. Pingback: Why OpenStack for IBM PowerVC? | Storage CH Blog

  2. Pingback: The Power of OpenStack - Mindtrek 2016 Mindtrek 2016

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s