5 Things OpenStack Horizon Falls Short on. Spoiler: Visibility

Jun 12 2014 | by Eran Abramson

65 Flares Twitter 0 Facebook 0 LinkedIn 65 Email -- Filament.io 65 Flares ×

The OpenStack platform is making headway with improved releases, growing adoption and a positive vision ahead. With a clear potential of OpenStack for enterprises, true value is still difficult to reach per lack of proper visibility. While updates are released, they are still not user-friendly, rather user hostile, and thus aren’t allowing deployment optimization for efficiency. Below we will touch on the lack of data aggregation within the Openstack horizon dashboard with additional posts on other OpenStack visibility issues in the future.

Knowledge is power; information alone isn’t
The OpenStack dashboard is extremely basic, making it difficult to gain real insight and generate real value. Currently available:

  • High level: a lot of data without knowledge of what to do with it.
  • Data dump: lack of organization, filtering customization, separate performance dashboard.
  • User hostile: no data aggregation nor orchestration.

Having access to data without insights and direction is useless, for you don’t have the knowledge to improve and optimize your deployment.

Basic needs
To improve cloud efficiency, there are foundational requirements such as usage metrics, filtering options, alerts, reporting and overall aggregated data in one dashboard.

  • Usage metrics: seeing and understanding cloud usage provides immense value to enhance performance. Without so, it is unknown what is running properly and what isn’t. For example, an instance may be “active” yet isn’t being used in reality; knowing such things is crucial as to reallocate resources and avoid throwing money away.
  • Filtering options: when deploying a few instances, it is easy to keep track and associate each with its user, department, project and even costs. But when running hundreds, thousands or even more, there is no easy way to see the status of any specific item, thus the benefits of filtering capabilities and breakdowns are immense.
  • Alerts: with alerts (default or custom) in place, IT can be notified per anomalies, inefficiencies, peaks, usage trends and more, so adjustments, repairs or updates may be done accordingly.
  • Aggregation: having all such availabilities and data aggregated in one place is a dream. Besides the obvious time saving by having all info in one place, finally a real and insightful high level overview is within grasp. Entire deployment can be seen from the top down, thus areas of interest are easier to find…and delved deep into each separately.

Horizon update
OpenStack is continuing to improve with updated releases, and Horizon will as well. Still, data view improvements do not mean users will gain extra knowledge, hence reaching potential value is still out of reach.

Cloudyn’s solution grants real visibility into your OpenStack deployment, across different projects, instances and usage, also combining additional vendors for an even higher view of your organization’s deployment.

Learn more about Cloudyn’s tools for OpenStack and sign up for the beta today.

Login

Forgot Password?

No account yet? Register.

65 Flares Twitter 0 Facebook 0 LinkedIn 65 Email -- Filament.io 65 Flares ×