Open Stack

Chris,
Use case point well taken :-)

I'll  propose something via a spec to ceilometer for sensor naming which 
will
include the ability to support the new health sensor information.

 From a use case perspective, I want to provide the health of every 
platform
so an administrator can be notified when a platforms health drops below 
100%.
I also want to provide an administrator the ability to investigate exactly
what components in the platform are not working correctly if health is
reported at less than 100%.

With the current sensor information, the use case I was interested in 
was the
graphical display of individual platform sensor information.

Do you happen to know what some of the use cases are for the current 
reporting
of sensor information?

Thanks,
Jim

On 10/20/2014 11:14 AM, Chris Dent wrote:
> On Mon, 20 Oct 2014, Jim Mankovich wrote:
>> On 10/20/2014 6:53 AM, Chris Dent wrote:
>>> On Fri, 17 Oct 2014, Jim Mankovich wrote:
>>>> See answers inline. I don't have any concrete answers as to how to 
>>>> deal
>>>> with some of questions you brought up, but I do have some more detail
>>>> that may be useful to further the discussion.
>>>
>>> That seems like progress to me.
>
> And thanks for keeping it going some more. I'm going to skip your
> other (very useful) comments and go (almost) straight (below) to
> one thing which goes to the root of the queries I've been making.
>
> Most of the rest of what you said makes sense and we seem to be
> mostly in agreement. I suppose the next step would be propose a
> spec? https://github.com/openstack/ceilometer-specs
>
>> We have 2 use cases,
>> Get all the sensors within a given platform (based on ironic node id)
>> Get all the sensors of a given "type/name". independent of platform
>> Others?
>
> These are not use cases, these are tasks. That's because these say
> nothing about the thing you are actually trying to achieve. "Get all
> the sensors with a given platform" is a task without a purpose.
> You're not just going to stop there are you? If so why did you get
> the information in the first place.
>
> A use case could be:
>
> * I want to get all the sensors of a given platform so I can <do
>   something>.
>
> Or even better something like:
>
> * I want to <do something>.
>
> And the way to do that would just so happen to be getting all the
> sensors.
>
> I realize this is perhaps pedantic hair-splitting, but I think it
> can be useful at least some of the time. I know that from my own
> experience I am very rarely able to get the Ceilometer API to give
> me the information that I actually want (e.g. "How many vcpus are
> currently in action). This feels like the result of data availability
> driving the query engine rather than vice versa.
>