This is a guest post by Steve Shultz (firstname.lastname@example.org)
The new z/VM Cloud Manager Appliance offers vendors several different choices for how to support OpenStack on z/VM:
- Get z/VM OpenStack plug-ins for Nova, Neutron and Ceilometer at:
These are continually kept current with the OpenStack community and, as a result, can be built into any OpenStack-based tooling. They allow z/VM compute and networking resources to be leveraged directly from the aforementioned tooling. In this case, no OpenStack code runs within the z/VM product itself. All the OpenStack code runs within the OpenStack-based tooling. This the the way that SUSE OpenStack Cloud 6 is enabled to manage z/VM resources.
- Drive the OpenStack Controller such that the Nova compute node code runs within the z/VM product. All other OpenStack code runs within the OpenStack-based tooling. This enables z/VM to participate in a hybrid environment, where multiple compute nodes on potentially multiple architectures run within a single OpenStack cloud or region.
The Nova code within z/VM is at the Liberty level of OpenStack and supports all the Nova API that can leverage z/VM resources. In addition, the Nova code within z/VM transparently provides enterprise market compute functionality that cannot be accessed via the z/VM OpenStack plug-ins. This allows customers with existing z/VM infrastructures to leverage that infrastructure within an OpenStack context.
- Drive the OpenStack API for all of the following OpenStack projects such that all code for these projects runs within the z/VM product:
All of these projects are at the Liberty level of OpenStack and support all the API that can leverage z/VM resources. Utilizing z/VM OpenStack enablement in this way transparently maximizes the amount of enterprise market functionality that can be exploited within an OpenStack context. This is the way that VMWare’s vRealize Automation is enabled to manage z/VM resources.
- Drive Remote Keystone Support. This enables z/VM to participate in a multi-region configuration, where each CMA (or other fully enabled OpenStack core) constitutes a single cloud or region. In this case, OpenStack-based tooling includes and runs the OpenStack Keystone/Horizon code, while driving the OpenStack API for all the other OpenStack projects listed above. All the code for the OpenStack projects except for Keystone/Horizon runs within the z/VM product. Utilizing z/VM OpenStack enablement in this way allows the OpenStack-based tooling to maintain control of identity/security, while allowing z/VM to otherwise maximally leverage enterprise market functionality transparently within an OpenStack context. This is the way that IBM Cloud Orchestrator is enabled to manage z/VM resources.
For further information on all these options (and lots more information about z/VM’s OpenStack enablement!) see this page.