Share this post:
Recently, we finalized our latest release of IBM Blue Box Cloud based on Mitaka, the latest release of OpenStack. Since IBM Blue Box manages OpenStack private clouds on behalf of our customers, we’ve initiated the upgrade process to Mitaka for customers, bringing them the latest and greatest.
Maintenance downtime is costly for any cloud customer—we get it, time is money. As a result, IBM Blue Box has invested heavily in tools, teams, and processes–plus our experience with hundreds of OpenStack upgrades–to ensure the in-place upgrade to Mitaka is a non-event for customers. We expect to have the majority of our customer clouds running on Mitaka by the end of July.
New features with Mitaka release
Mitaka brings a lot of new capabilities; allow me to highlight my top three:
IBM Blue Box has been working with the community to realize the vision since we discussed the topic in Vancouver last year. So, it’s extremely gratifying to be able to provide production ready Keystone-to-Keystone Federated Identity to our customers. With this new capability, customers can use the same credentials to access their cloud resources across multiple authorized OpenStack clouds. For customers with multiple OpenStack clouds, Keystone-to-Keystone Federated Identity enables administrators to enable single sign on without having to provision additional identities across all their clouds.
Modern cloud native applications are API driven, declarative and elastic. Many customers use Heat templates as the framework to deploy and orchestrate cloud native applications. With Heat supporting LBaaS v2 API in Mitaka, customers can deploy cloud native applications that auto-scale resources via Heat templates and autoscaling groups.
OpenStack Dashboard and Client
While there are DevOps ninjas that never need to use OpenStack Dashboard and Client, mere mortals depend on these tools to get work done. Dashboard adds new capabilities (such as LBaaS support for customers) plus intuitiveness around attaching volumes and networks, while Client aggregates access to all OpenStack services in one seamless interface. This level of fit and finish is necessary to ensure that users get maximum utility from their OpenStack cloud.
Two delivery models, one cloud experience
As illustrated above, IBM Blue Box offers a single cloud experience across two different delivery models. In order to maintain a consistent experience between IBM Blue Box Local and Dedicated, we have to keep the OpenStack services identical and provide the same set of infrastructure building blocks. Only when there is a common cloud substrate can the top benefits of hybrid cloud (workload portability, elasticity, single sign-on and orchestration) be truly realized.
To that end, we are now bringing the same capabilities available on Dedicated to Local, namely:
Two new compute node choices
- IO Optimized is a new compute node type meant to support applications with high memory and high speed storage access requirements such as application caches.
- High Storage Capacity provides a significant amount of ephemeral storage to support storage hungry workloads such as logging databases.
Additional block storage option
- Hybrid Block Storage solution increases storage capacity fourfold while delivering exceptional IOPS.
In addition, Local supports POWER Compute Nodes (Habañero) to allow customers to deploy compatible applications.
IBM Blue Box just celebrated our one-year anniversary of being part of the IBM Cloud family. We feel that the Mitaka release is fitting way to celebrate.