Open Stack

In response to your questions:


1.       Definitely represent the data graphically (visualizations). There are numerous excellent javascript visualization libraries. My current favorite is d3 (http://d3js.org/) and I’d have no qualms with including it in Horizon.

2.       I think having a “summary” display of ceilometer data on the overview would be great (though there will have to be a fallback if the stack doesn’t deploy ceilometer). I also think that displaying detailed ceilometer data deserves its own panel and probably various tabs/views within it. Perhaps a panel and then a tab for each service?

3.       I definitely see this as primarily an admin function for now. Let’s vet the concept there and if we discover pieces that would be useful and appropriate for an end user we can bring it down to that level. A tenant selector dropdown is easy enough to accomplish for filtering data (you can find similar dropdowns in various places throughout the project).

All the best,


-          Gabriel

From: Brooklyn Chen [mailto:yuanotes at gmail.com]
Sent: Wednesday, December 19, 2012 7:04 AM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [Ceilometer]Ceilometer in Horizon

Hi Matt,

Thank you for your help.  I love visualizations too.

You are right. It's not easy to figure out how to design the UI now and I think I can implement it in text form now and then you can help to do some visualization work. :)

Brooklyn
在 2012-12-19，下午6:04，Matt Joyce <matt.joyce at cloudscaling.com<mailto:matt.joyce at cloudscaling.com>> 写道：


I'd be down to help in my free time.  I love visualizations.  =D

The trick probably is the vis side of things.  Dependency sets in horizon have traditionally been troublesome due to the wide range of variance between supported platforms such as redhat and ubuntu.

Probably worth figuring out what we're going to do in regards to that.

-Matt
On Wed, Dec 19, 2012 at 2:00 AM, Brooklyn Chen <yuanotes at gmail.com<mailto:yuanotes at gmail.com>> wrote:
Hi there,

I am new to ceilometer and I have some experiences in developing Horizon. This is a discussion about how to put ceilometer data in Hoirzon.

!!UX experts are needed to help!!

Related blueprints:
https://blueprints.launchpad.net/horizon/+spec/ceilometer
https://blueprints.launchpad.net/ceilometer/+spec/horizon-plugin

I'd like to implement these blueprints(it's the same) to add ceilometer in Horizon. And there are some designing issues need to be addressed.

1. Displaying data
There are 3 kinds of data:

|    Type    |                  Definition                  |
|------------|----------------------------------------------|
| Cumulative | Increasing over time (instance hours)        |
|------------|----------------------------------------------|
| Gauge      | Discrete items (floating IPs, image uploads) |
|            | and fluctuating values (disk I/O)            |
|------------|----------------------------------------------|
| Delta      | Changing over time (bandwidth)               |

Shall we use chart or just table to show these data?
Table view is easy to implement but it's not intuitive.

2. Where to put these data
As you may know, these data are collected from openstack resources, such as instances, floating ip, vcpu hours, object store... (detail: http://docs.openstack.org/developer/ceilometer/measurements.html)

Shall we put these data on a new panel? Or in the Overview panel?


3. User Console and Admin Console
If we put these data in admin console of Horizon, we need some mechanism to select user and tenant to filter resources.




Many thanks!

Brooklyn

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20121219/37a0462f/attachment.html>