> On Jun 16, 2014, at 10:56 AM, Eoghan Glynn wrote:
>
> >
> > Apologies for the top-posting, but just wanted to call out some
> > potential confusion that arose on the #os-ceilometer channel earlier
> > today.
> >
> > TL;DR: the UI shouldn't assume a 1:1 mapping between alarms and
> > r
On Jun 16, 2014, at 10:56 AM, Eoghan Glynn wrote:
>
> Apologies for the top-posting, but just wanted to call out some
> potential confusion that arose on the #os-ceilometer channel earlier
> today.
>
> TL;DR: the UI shouldn't assume a 1:1 mapping between alarms and
> resources, since thi
Apologies for the top-posting, but just wanted to call out some
potential confusion that arose on the #os-ceilometer channel earlier
today.
TL;DR: the UI shouldn't assume a 1:1 mapping between alarms and
resources, since this mapping does not exist in general
Background: See ML post[1]
D
the alarms that have
occurred".
Hope it helps
Cheers,
H
From: Liz Blanchard [mailto:lsure...@redhat.com]
Sent: Monday, June 9, 2014 2:36 PM
To: Eoghan Glynn
Cc: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Horizon] [UX] Design for A
Hi all,
Thanks again for the great comments on the initial cut of wireframes. I’ve
updated them a fair amount based on feedback in this e-mail thread along with
the feedback written up here:
https://etherpad.openstack.org/p/alarm-management-page-design-discussion
Here is a link to the new versi
Thanks for the excellent feedback on these, guys! I’ll be working on making
updates over the next week and will send a fresh link out when done. Anyone
else with feedback, please feel free to fire away.
Best,
Liz
On Jun 4, 2014, at 12:33 PM, Eoghan Glynn wrote:
>
> Hi Liz,
>
> Two further th
Hi Liz,
Two further thoughts occurred to me after hitting send on
my previous mail.
First, is the concept of alarm dimensioning; see my RDO Ceilometer
getting started guide[1] for an explanation of that notion.
"A key associated concept is the notion of dimensioning which defines the set
of ma
:lsure...@redhat.com]
> Sent: Tuesday, June 3, 2014 3:41 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: [openstack-dev] [Horizon] [UX] Design for Alarming and Alarm
> Management
>
>
>
>
> Hi All,
>
>
>
>
>
> I’ve
Hi Liz,
Looks great!
Some thoughts on the wireframe doc:
* The description of form:
"If CPU Utilization exceeds 80%, send alarm."
misses the time-window aspect of the alarm definition.
Whereas the boilerplate default descriptions generated by
ceilometer itself:
"cpu_util >
d [mailto:lsure...@redhat.com]
Sent: Tuesday, June 3, 2014 3:41 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [Horizon] [UX] Design for Alarming and Alarm Management
Hi All,
I've recently put together a set of wireframes[1] around Alarm Management
Hi All,
I’ve recently put together a set of wireframes[1] around Alarm Management that
would support the following blueprint:
https://blueprints.launchpad.net/horizon/+spec/ceilometer-alarm-management-page
If you have a chance it would be great to hear any feedback that folks have on
this direc
11 matches
Mail list logo
