<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle18
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1462504478;
mso-list-type:hybrid;
mso-list-template-ids:-1606635418 793802608 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1
{mso-list-id:1564674741;
mso-list-type:hybrid;
mso-list-template-ids:-828893746 1863643944 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Here my feedback regarding the designs:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Page 2:
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo2"><![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I think that the admin would probably want to filter alarms per user, project, name, meter_name, current_alarm_state(“ok”=”alarm ready”; “insufficient
data” = “alarm not ready”; “alarm” =”alarm triggered”), but we don’t have all that columns on the table. Maybe it will be better just to add columns for those fields, or have another tables or tabs that could allow the admin to see the alarms based on that
parameters.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo2"><![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I would add a “delete alarm” button as a table action<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo2"><![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><u><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Nice to have</span></u><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">: if we are thinking about “combining alarms”,
maybe having a “combine alarm” button as table action that gets activated when the admin selects two or more alarms.
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l1 level2 lfo2">
<![if !supportLists]><span style="font-size:11.0pt;font-family:"Courier New";color:#1F497D"><span style="mso-list:Ignore">o<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">When the button is clicked, it should show something like the “Add Alarm” dialog, allowing the user to create a new combined alarm, based on their
previous alarm selection<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Page 3-5:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo2"><![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Love the workflow!<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo2"><![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">A couple of things related to the “Alarm When” setup:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l1 level2 lfo2">
<![if !supportLists]><span style="font-size:11.0pt;font-family:"Courier New";color:#1F497D"><span style="mso-list:Ignore">o<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Depending on the resource that is “selected” (from page 2) you would have a list of the possible meters to be considered. For example, if your resource
is an instance, you would have the following list of meters: number of instances, cpu time used, Average CPU utilization, memory, etc. This will also affect the “threshold” unit to be used. In the design, there is a textbox that has a percentage label (“%”)
right next to it. The thing is that this “threshold” could be a percentage (for example, CPU utilization), but it could be a flat number as well (for example, number of instances on the project).<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l1 level2 lfo2">
<![if !supportLists]><span style="font-size:11.0pt;font-family:"Courier New";color:#1F497D"><span style="mso-list:Ignore">o<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">(Related to your point 5) There are two things related to combined alarms that we need to consider.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-.25in;mso-list:l1 level3 lfo2">
<![if !supportLists]><span style="font-size:11.0pt;font-family:Wingdings;color:#1F497D"><span style="mso-list:Ignore">§<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">1) the combination can be between any type of alarm: you could combine alarms associated to different resources, meters, users? (Ceilometer expert
will know). You even could combine combined alarms with other alarms as well. The AND and OR operation between the alarms can be used for combined alarms. For instance, combine two alarms with an OR operator<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-.25in;mso-list:l1 level3 lfo2">
<![if !supportLists]><span style="font-size:11.0pt;font-family:Wingdings;color:#1F497D"><span style="mso-list:Ignore">§<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">2) Adding two rules to match to a single alarm is not supported by Ceilometer. For that, you use combined alarms
</span><span style="font-size:11.0pt;font-family:Wingdings;color:#1F497D">J</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">. The idea of adding triggering rules to the alarm creation dialog is great for me, but I’m not
sure if Ceilometer supports that.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Page 6:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo2"><![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Really liked the way that actions and state could be set, but we should see how the notifications will be handled. Maybe these actions could be set
“by default” in our first version and after that, start thinking about setting custom actions for alarm states in the future (same for email add-on at the user settings)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Page 7: “Viewing Alarm History” A.K.A: the alarms that have occurred.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Same as page 2: I think that the admin would probably want to filter alarms per user, project, name, meter_name, etc. (for instance, to see what alarms
have being triggered on the project “X”), but we don’t have that columns on the table. Maybe it will be better just to add columns for those fields, or have another tables or tabs that could allow the admin to see the alarms based on that parameters.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Is the alarm date column referring to the date in which the alarm was created or the date in which the alarm was triggered?
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Is the alarm name content a link or a simple text? What would happen when the admin selects an alarm? Is It going to show the “update alarm dialog”?
Are there any actions associated to the rows?<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Maybe changing the name of the tab to “Activated alarms” or smth that actually it’s interpreted as “in here you can see the alarms that have occurred”.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hope it helps<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Cheers,<br>
H<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> Liz Blanchard [mailto:lsurette@redhat.com]
<br>
<b>Sent:</b> Monday, June 9, 2014 2:36 PM<br>
<b>To:</b> Eoghan Glynn<br>
<b>Cc:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> Re: [openstack-dev] [Horizon] [UX] Design for Alarming and Alarm Management<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">Hi all, </span>
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">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:
</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><a href="https://etherpad.openstack.org/p/alarm-management-page-design-discussion">https://etherpad.openstack.org/p/alarm-management-page-design-discussion</a></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">Here is a link to the new version:
</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="http://people.redhat.com/~lsurette/OpenStack/Alarm%20Management%20-%202014-06-05.pdf">http://people.redhat.com/~lsurette/OpenStack/Alarm%20Management%20-%202014-06-05.pdf</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">And a quick explanation of the updates that I made from the last version:
</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">1) Removed severity.</span><o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">2) Added Status column. I also added details around the fact that users can enable/disable alerts.</span><o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">3) Updated Alarm creation workflow to include choosing the project and user (optionally for filtering the resource list), choosing resource, and allowing for choose of amount of time to monitor
for alarming. </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""> -Perhaps we could be even more sophisticated for how we let users filter down to find the right resources that they want to monitor for alarms?
</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">4) As for notifying users…I’ve updated the “Alarms” section to be “Alarms History”. The point here is to show any Alarms that have occurred to notify the user. Other notification ideas could
be to allow users to get notified of alerts via e-mail (perhaps a user setting?). I’ve added a wireframe for this update in User Settings. Then the Alarms Management section would just be where the user creates, deletes, enables, and disables alarms. Do you
still think we don’t need the “alarms” tab? Perhaps this just becomes iteration 2 and is left out for now as you mention in your etherpad.
</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">5) Question about combined alarms…currently I’ve designed it so that a user could create multiple levels in the “Alarm When…” section. They could combine these with AND/ORs. Is this going far
enough? Or do we actually need to allow users to combine Alarms that might watch different resources?</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">6) I updated the Actions column to have the “More” drop down which is consistent with other tables in Horizon.
</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">7) Added in a section in the “Add Alarm” workflow for “Actions after Alarm”. I’m thinking we could have some sort of If State is X, do X type selections, but I’m looking to understand more
details about how the backend works for this feature. Eoghan gave examples of logging and potentially scaling out via Heat. Would simple drop downs support these events?
</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">8) I can definitely add in a “scheduling” feature with respect to Alarms. I haven’t added it in yet, but I could see this being very useful in future revisions of this feature.
</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">9) Another though is that we could add in some padding for outlier data as Eoghan mentioned. Perhaps a setting for “This has happened 3 times over the last minute, so now send an alarm.”? </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">A new round of feedback is of course welcome :)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Best,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Liz<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Jun 4, 2014, at 1:27 PM, Liz Blanchard <<a href="mailto:lsurette@redhat.com">lsurette@redhat.com</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">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.<br>
<br>
Best,<br>
Liz<br>
On Jun 4, 2014, at 12:33 PM, Eoghan Glynn <<a href="mailto:eglynn@redhat.com">eglynn@redhat.com</a>> wrote:<br>
<br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><br>
Hi Liz,<br>
<br>
Two further thoughts occurred to me after hitting send on<br>
my previous mail.<br>
<br>
First, is the concept of alarm dimensioning; see my RDO Ceilometer<br>
getting started guide[1] for an explanation of that notion.<br>
<br>
"A key associated concept is the notion of dimensioning which defines the set of matching meters that feed into an alarm evaluation. Recall that meters are per-resource-instance, so in the simplest case an alarm might be defined over a particular meter applied
to all resources visible to a particular user. More useful however would the option to explicitly select which specific resources we're interested in alarming on. On one extreme we would have narrowly dimensioned alarms where this selection would have only
a single target (identified by resource ID). On the other extreme, we'd have widely dimensioned alarms where this selection identifies many resources over which the statistic is aggregated, for example all instances booted from a particular image or all instances
with matching user metadata (the latter is how Heat identifies autoscaling groups)."<br>
<br>
We'd have to think about how that concept is captured in the<br>
UX for alarm creation/update.<br>
<br>
Second, there are a couple of more advanced alarming features <br>
that were added in Icehouse:<br>
<br>
1. The ability to constrain alarms on time ranges, such that they<br>
would only fire say during 9-to-5 on a weekday. This would<br>
allow for example different autoscaling policies to be applied<br>
out-of-hours, when resource usage is likely to be cheaper and<br>
manual remediation less straight-forward.<br>
<br>
2. The ability to exclude low-quality datapoints with anomolously<br>
low sample counts. This allows the leading edge of the trend of<br>
widely dimensioned alarms not to be skewed by eagerly-reporting<br>
outliers.<br>
<br>
Perhaps not in a first iteration, but at some point it may make sense<br>
to expose these more advanced features in the UI.<br>
<br>
Cheers,<br>
Eoghan<br>
<br>
[1] <a href="http://openstack.redhat.com/CeilometerQuickStart">http://openstack.redhat.com/CeilometerQuickStart</a><br>
<br>
<br>
<br>
----- Original Message -----<br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><br>
Hi Liz,<br>
<br>
Looks great!<br>
<br>
Some thoughts on the wireframe doc:<br>
<br>
* The description of form:<br>
<br>
"If CPU Utilization exceeds 80%, send alarm."<br>
<br>
misses the time-window aspect of the alarm definition.<br>
<br>
Whereas the boilerplate default descriptions generated by<br>
ceilometer itself:<br>
<br>
"cpu_util > 70.0 during 3 x 600s"<br>
<br>
captures this important info.<br>
<br>
* The metric names, e.g. "CPU Utilization", are not an exact<br>
match for the meter names used by ceilometer, e.g. "cpu_util".<br>
<br>
* Non-admin users can create alarms in ceilometer:<br>
<br>
"This is where admins can come in and<br>
define and edit any alarms they want<br>
the environment to use."<br>
<br>
(though these alarms will only have visibility onto the stats<br>
that would be accessible to the user on behalf of whom the<br>
alarm is being evaluated)<br>
<br>
* There's no concept currently of alarm severity.<br>
<br>
* "Should users be able to enable/dis-able alarms."<br>
<br>
Yes, the API allows for disabled (i.e. non-evaluated) alarms.<br>
<br>
* "Should users be able to own/assign alarms?"<br>
<br>
Only admin users can create an alarm on behalf of another<br>
user/tenant.<br>
<br>
* "Should users be able to acknowledge, close alarms?"<br>
<br>
No, we have no concept of ACKing an alarm.<br>
<br>
* "Admins can also see a full list of all Alarms that have<br>
taken place in the past."<br>
<br>
In ceilometer terminology, we refer to this as alarm history<br>
or alarm change events.<br>
<br>
* "CPU Utilization exceeded 80%."<br>
<br>
Again good to capture the duration in that description of the<br>
event.<br>
<br>
* "Within the Overview section, there should be a new tab that allows the<br>
user to click and view all Alarms that have occurred in their<br>
environment."<br>
<br>
Not sure really what "environment" means here. Non-admin tenants only<br>
have visibility to their own alarm, whereas admins have visibility to<br>
all alarms.<br>
<br>
* "This list would keep the latest alarms."<br>
<br>
Presumably this would be based on querying the alarm-history API,<br>
as opposed to an assumption that Horizon is consuming the actual<br>
alarm notifications?<br>
<br>
Cheers,<br>
Eoghan<br>
<br>
----- Original Message -----<br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal" style="margin-bottom:12.0pt">Hi All,<br>
<br>
I’ve recently put together a set of wireframes[1] around Alarm Management<br>
that would support the following blueprint:<br>
<a href="https://blueprints.launchpad.net/horizon/+spec/ceilometer-alarm-management-page">https://blueprints.launchpad.net/horizon/+spec/ceilometer-alarm-management-page</a><br>
<br>
If you have a chance it would be great to hear any feedback that folks have<br>
on this direction moving forward with Alarms.<br>
<br>
Best,<br>
Liz<br>
<br>
[1]<br>
<a href="http://people.redhat.com/~lsurette/OpenStack/Alarm%20Management%20-%202014-05-30.pdf">http://people.redhat.com/~lsurette/OpenStack/Alarm%20Management%20-%202014-05-30.pdf</a><br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><o:p></o:p></p>
</blockquote>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><o:p></o:p></p>
</blockquote>
</blockquote>
<p class="MsoNormal"><o:p> </o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>