<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#333333">
Hi Gabriel,<br>
<br>
thanks for follwoing this thread and having a look on wireframes.
Regarding the term 'resource class', the naming is what we got into
during our initial intents. It's not final version, so if there are
concerns, there is no problem in finding more accurate one (we just
couldn't find better). As for resource class definition, I tried to
explain it a bit more in reply to Rob's mail (in this thread), so if
you get that one, I hope it will help to answer and explain the
concept of classes a little bit more.<br>
<br>
If you still have any concerns, let me know I will try to be more
explicit.<br>
-- Jarda<br>
<br>
<div class="moz-cite-prefix">On 2013/25/09 02:03, Gabriel Hurley
wrote:<br>
</div>
<blockquote
cite="mid:1dd06b9ae48c44b4bea02cc5a359b54b@BN1PR05MB169.namprd05.prod.outlook.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 14 (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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 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";
color:#333333;}
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";
color:#333333;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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:309094510;
mso-list-type:hybrid;
mso-list-template-ids:217096844 -1034258526 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:27.0pt;
text-indent:-.25in;
font-family:"Calibri","sans-serif";
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;
margin-left:63.0pt;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:99.0pt;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:135.0pt;
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;
margin-left:171.0pt;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:207.0pt;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:243.0pt;
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;
margin-left:279.0pt;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:315.0pt;
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]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Really
digging a lot of that. Particularly the
inter-rack/inter-node communication stuff around page 36ish
or so.<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">I’m
concerned about using the term “Class”. Maybe it’s just me
as a developer, but I couldn’t think of a more generic, less
inherently meaningful word there. I read through it and I
still only vaguely understand what a “Class” is in this
context. We either need better terminolody or some serious
documentation/user education on that one.<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">Also,
I can’t quite say how, but I feel like the “Class” stuff
ought to be meshed with the Resource side of things. The
separation seems artificial and based more on the API
structure (presumably?) than on the most productive user
flow when interacting with that system. Maybe start with the
question “if the system were empty, what would I need to do
and how would I find it?”<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">Very
cool though.<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="MsoListParagraph"
style="margin-left:27.0pt;text-indent:-.25in;mso-list:l0
level1 lfo1">
<!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";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">Gabriel<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 style="border:none;border-left:solid blue 1.5pt;padding:0in
0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">
Jaromir Coufal [<a class="moz-txt-link-freetext" href="mailto:jcoufal@redhat.com">mailto:jcoufal@redhat.com</a>]
<br>
<b>Sent:</b> Tuesday, September 24, 2013 2:04 PM<br>
<b>To:</b> OpenStack Development Mailing List<br>
<b>Subject:</b> [openstack-dev] [Tuskar] [UI]
Introducing POC Wireframes<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Hey folks,<br>
<br>
I want to introduce our direction of Tuskar UI, currently
described with POC wireframes. Keep in mind, that wireframes
which I am sending were made for purpose of proof of concept
(which was built and released in August) and there are
various changes since then, which were already adopted.
However, basic concepts are staying similar. Any updates for
wireframes and future direction will be sent here to the
dev-list for feedback and reviews.<br>
<br>
<a moz-do-not-send="true"
href="http://people.redhat.com/%7Ejcoufal/openstack/tuskar/2013-07-11_tuskar_poc_wireframes.pdf">http://people.redhat.com/~jcoufal/openstack/tuskar/2013-07-11_tuskar_poc_wireframes.pdf</a><br>
<br>
Just quick description of what is happening there:<br>
* 1st step implementation - Layouts (page 2)<br>
- just showing that we are re-using all Horizon
components and layouts<br>
* Where we are heading - Layouts (page 8)<br>
- possible smaller improvements to Horizon concepts<br>
- majority just smaller CSS changes in POC timeframe
scope<br>
* Resource Management - Flavors (page 15) - ALREADY REMOVED<br>
- these were templates for flavors, which were part of
selection in resource class creation process<br>
- currently the whole flavor definition moved under
compute resource class completely (templates are no longer
used)<br>
* Resource Management - Resources (page 22)<br>
- this is rack management<br>
- creation workflow was based on currently obsolete data
(settings are going to be changed a bit)<br>
- upload rack needs to make sure that we know some
standard csv file format (can we specify some?)<br>
- detail page of rack and node, which are going through
enhancement process<br>
* Resource Management - Classes (page 40)<br>
- resource class management<br>
- few changes will happen here as well regarding
creation workflow<br>
- detail page is going through enhancements as well as
racks/nodes detail pages<br>
* Graphic Design<br>
- just showing the very similar look and feel as
OpenStack Dashboard<br>
<br>
If you have any further questions, just follow this thread,
I'll be very happy to answer as much as possible.<br>
<br>
Cheers,<br>
-- Jarda <o:p></o:p></p>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>