<html><head></head><body bgcolor="#FFFFFF"><div>Stated...</div><div><br></div><div>1: Thanks to everyone for contextual examples</div><div><br></div><div>Proposed...</div><div><br></div><div>1: Additional capability descriptors should always be at a group level... a group can exist of one but most use cases will have more than one</div><div>2: API should be created to access this info allowing implementation to come from anywhere (config file, chef, rpath, metadata from hypervisors, etc)</div><div>3: Default implementation should pull data from well known and uniform location... which is? (do chime in)</div><div><br></div><div>I totally grok the need for host decorators but also need the source of the decorators to be configurable based on my specific environment around openstack.</div><div><br></div><div>JanMan</div><div><br></div><div>...after rockin' a night with Devin. Any fuzziness of communication is merely a temporary side effect. If required, just squint a bit and I should make better sense.</div><div><br></div><div><br></div><div><br>On Apr 3, 2012, at 6:45 AM, "Day, Phil" <<a href="mailto:philip.day@hp.com">philip.day@hp.com</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div><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:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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:0cm;
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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{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:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:968050580;
mso-list-type:hybrid;
mso-list-template-ids:1392540194 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
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;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
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:-18.0pt;
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;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
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:-18.0pt;
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;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l1
{mso-list-id:1608196251;
mso-list-type:hybrid;
mso-list-template-ids:351846708 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
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:-18.0pt;
font-family:"Courier New";}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
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:-18.0pt;
font-family:"Courier New";}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l2
{mso-list-id:1722899809;
mso-list-type:hybrid;
mso-list-template-ids:-2093682958 -989928154 134807555 134807557 134807553 134807555 134807557 134807553 134807555 134807557;}
@list l2:level1
{mso-level-start-at:2;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-font-family:Calibri;}
@list l2:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l2:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l2:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l2:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l2:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l2:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l2:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l2:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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">Hi John,<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">Maybe the problem with host aggregates is that it too quickly became something that was linked to hypervisor capability, rather than being the more general mechanism of which one form of aggregate could be linked to hypervisor capabilities ?<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">Should we have a “host aggregates 2.0” session at the Design Summit ?<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">Phil<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"><o:p> </o:p></span></p><div><div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"><p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> John Garbutt [mailto:John.Garbutt@citrix.com] <br><b>Sent:</b> 03 April 2012 11:43<br><b>To:</b> Day, Phil; Jan Drake; Lorin Hochstein<br><b>Cc:</b> <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br><b>Subject:</b> RE: [Openstack] Limit flavors to specific hosts<o:p></o:p></span></p></div></div><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">+1 to REST API and nova cli support<o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">+1 to exposing Glance metadata to the scheduler. The main reason I thought about this was a multi-hypervisor cloud (matching images to the correct hypervisor). But some images may require more than 1GB RAM, etc. <o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I see an aggregate is a groups of compute hosts within a single availability zone (assumed to have similar capabilities). With XenServer, it does build up a resource pool as you add hosts into the aggregate (you could add a flag to stop that happening, if that isn’t required in your cloud).<o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I always expected to look at making the scheduler aware of the host-aggregate metadata. That would allow different groups of hosts, across multiple availability zones, to have the same extra capabilities. You could add a similar metadata service on individual hosts. Then you could look at cascading aggregate metadata and adding using the host metadata as an override to create an overall set of metadata for the scheduler, but that might be gilding the lily a bit…<o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Also, maybe flavor is not expressive enough for the billing and scheduling, maybe we need some concept like “server requirements”.<o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">It might be something like:<o:p></o:p></span></p><p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l1 level1 lfo2"><!--[if !supportLists]--><span lang="EN-US" 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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">User requests an image and flavor, and perhaps particular networking configuration<o:p></o:p></span></p><p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l1 level1 lfo2"><!--[if !supportLists]--><span lang="EN-US" 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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Glance meta for the image is collected<o:p></o:p></span></p><p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt;mso-list:l1 level2 lfo2"><!--[if !supportLists]--><span lang="EN-US" 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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Could tell you that a flavor is not valid for this image<o:p></o:p></span></p><p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt;mso-list:l1 level2 lfo2"><!--[if !supportLists]--><span lang="EN-US" 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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Could tell you extra requirements, like: requires XenServer, or requires KVM<o:p></o:p></span></p><p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l1 level1 lfo2"><!--[if !supportLists]--><span lang="EN-US" 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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">This builds up some “service requirements” for this instance<o:p></o:p></span></p><p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt;mso-list:l1 level2 lfo2"><!--[if !supportLists]--><span lang="EN-US" 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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Union of info from users request and image meta-data<o:p></o:p></span></p><p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt;mso-list:l1 level2 lfo2"><!--[if !supportLists]--><span lang="EN-US" 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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">These “server requirements” can be used for the billing, instead of just flavor id<o:p></o:p></span></p><p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l1 level1 lfo2"><!--[if !supportLists]--><span lang="EN-US" 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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Host metadata collected<o:p></o:p></span></p><p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt;mso-list:l1 level2 lfo2"><!--[if !supportLists]--><span lang="EN-US" 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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">use capabilities (including those added in config file)<o:p></o:p></span></p><p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt;mso-list:l1 level2 lfo2"><!--[if !supportLists]--><span lang="EN-US" 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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">aggregate metadata<o:p></o:p></span></p><p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt;mso-list:l1 level2 lfo2"><!--[if !supportLists]--><span lang="EN-US" 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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">disabled flag, (+ host metadata overrides?)<o:p></o:p></span></p><p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l1 level1 lfo2"><!--[if !supportLists]--><span lang="EN-US" 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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Scheduler then filters out hosts that can’t satisfy the service requirements<o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Good points:<o:p></o:p></span></p><p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo4"><!--[if !supportLists]--><span lang="EN-US" 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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">a clear catalog of service offerings to choose from<o:p></o:p></span></p><p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo4"><!--[if !supportLists]--><span lang="EN-US" 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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">stops the number of different flavors ballooning (with/without GPU, XenServer or KVM, 1GB or 2GB, etc)<o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Bad points:<o:p></o:p></span></p><p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo4"><!--[if !supportLists]--><span lang="EN-US" 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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">billing is more complicated<o:p></o:p></span></p><p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level2 lfo4"><!--[if !supportLists]--><span lang="EN-US" 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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">no longer get flavors => price<o:p></o:p></span></p><p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo4"><!--[if !supportLists]--><span lang="EN-US" 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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">seems too complex<o:p></o:p></span></p><p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level2 lfo4"><!--[if !supportLists]--><span lang="EN-US" 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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">probably means there are some useful simplifications we could make<o:p></o:p></span></p><p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level2 lfo4"><!--[if !supportLists]--><span lang="EN-US" 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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">could just use flavor, but you get a ballooning of the number of flavors (GPU vs no GPU, XenServer vs KVM, 1GB vs 2GB)<o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">John<o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-US" 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:0cm 0cm 0cm 4.0pt"><div><div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"><p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <a href="mailto:openstack-bounces+john.garbutt=eu.citrix.com@lists.launchpad.net">openstack-bounces+john.garbutt=eu.citrix.com@lists.launchpad.net</a> <a href="mailto:[mailto:openstack-bounces+john.garbutt=eu.citrix.com@lists.launchpad.net]">[mailto:openstack-bounces+john.garbutt=eu.citrix.com@lists.launchpad.net]</a> <b>On Behalf Of </b>Day, Phil<br><b>Sent:</b> 03 April 2012 10:33<br><b>To:</b> Jan Drake; Lorin Hochstein<br><b>Cc:</b> <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br><b>Subject:</b> Re: [Openstack] Limit flavors to specific hosts<o:p></o:p></span></p></div></div><p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Yes - Its more generic that hypervisor capabilities – my main problem with Host Aggregates is that it limits it to some specific 1:1 groupings based on hypervisor functionality.<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">Use cases I want to be able to cover include:<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="text-indent:-18.0pt;mso-list:l2 level1 lfo6"><!--[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">Rolling new hardware through an existing cluster, and limiting some new flavors (which might for example provide higher network bandwidth) to just those servers<o:p></o:p></span></p><p class="MsoListParagraph"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p><p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l2 level1 lfo6"><!--[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">Providing a range of flavours that are dependent on specific hardware features (GPU)<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="text-indent:-18.0pt;mso-list:l2 level1 lfo6"><!--[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">There may be a further group that couples flavour and/or images to host groups – for example it’s possible to imagine a scenario where an image is only licensed to some specific subset of servers, or where a subset of nodes are running LXC (in which case the image is in effect pre-defined). In this case the image metadata could, for example, specify the flavors that it can be used with, and those flavors are in turn limited to specific hosts. I don’t really like this model of linking Glance objects (images) to Nova Objects (flavors), but I’m not sure what an alternative would be.<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">On the config file vs REST API for configuration debate (maybe this needs to be a Design Summit subject in its own right), I agree that we should make a distinction between items that are deploy time configuration (which hypervisor to use, network driver, etc) and items that could change whilst the system is running (rate limits is a good example). I don’t however see this as being an REST API vs config file issue - more a configuration repository issue. I’d also add that anything which is going to be configured via a REST API needs to also provide a command line tool to drive that interface – so that out of the box the system can be installed and configured via the tools and scripts shipped with 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">Phil<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"><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 #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"><p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <a href="mailto:openstack-bounces+philip.day=hp.com@lists.launchpad.net">openstack-bounces+philip.day=hp.com@lists.launchpad.net</a> <a href="mailto:[mailto:openstack-bounces+philip.day=hp.com@lists.launchpad.net]">[mailto:openstack-bounces+philip.day=hp.com@lists.launchpad.net]</a> <b>On Behalf Of </b>Jan Drake<br><b>Sent:</b> 03 April 2012 02:23<br><b>To:</b> Lorin Hochstein<br><b>Cc:</b> <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br><b>Subject:</b> Re: [Openstack] Limit flavors to specific hosts<o:p></o:p></span></p></div></div><p class="MsoNormal"><o:p> </o:p></p><div><p class="MsoNormal">If I understand this correctly, the motivation is to be able to provide a hint to schedulers on host-level appropriateness based on information external to that found in the hyperviser. <o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal">Right/Wrong/Close?<o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal">It would help to have a real-world example of where basic host resource evalution for scheduling would cause a situation requiring the host-level hard-coding of what is essentially a flavor-constraint.<o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal">I'll hold further thoughts for downstream.<o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal" style="margin-bottom:12.0pt">Jan<o:p></o:p></p></div><div><p class="MsoNormal" style="margin-bottom:12.0pt"><br>On Apr 2, 2012, at 6:06 PM, Lorin Hochstein <<a href="mailto:lorin@nimbisservices.com">lorin@nimbisservices.com</a>> wrote:<o:p></o:p></p></div><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><div><div><p class="MsoNormal">Just created a blueprint for this:<o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal"><a href="https://blueprints.launchpad.net/nova/+spec/host-capabilities-api">https://blueprints.launchpad.net/nova/+spec/host-capabilities-api</a><o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><p class="MsoNormal"><o:p> </o:p></p><div><div><div><div><p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif";color:black">Take care,<o:p></o:p></span></p></div><div><p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif";color:black"><o:p> </o:p></span></p></div><div><p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif";color:black">Lorin<o:p></o:p></span></p></div><div><p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif";color:black">--<o:p></o:p></span></p></div><div><p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif";color:black">Lorin Hochstein<o:p></o:p></span></p></div><div><p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif";color:black">Lead Architect - Cloud Services<o:p></o:p></span></p></div><div><p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif";color:black">Nimbis Services, Inc.<o:p></o:p></span></p></div><div><p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif";color:black"><a href="https://www.nimbisservices.com/">www.nimbisservices.com</a><o:p></o:p></span></p></div><div><p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif";color:black"><o:p> </o:p></span></p></div></div><p class="MsoNormal"><o:p> </o:p></p></div><p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p></div><p class="MsoNormal"><o:p> </o:p></p><div><div><p class="MsoNormal">On Apr 2, 2012, at 3:29 PM, Jay Pipes wrote:<o:p></o:p></p></div><p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p><div><p class="MsoNormal" style="margin-bottom:12.0pt">Can I add a feature request to the below thoughtstream? Can we make it so that the management of these things can be done outside of config files? i.e. via a REST API with some simple middleware exposing the particular scheduler nodes' understanding of which capabilities/filters it is using to apply its scheduling algorithm?<br><br>Making changes to configuration files works OK for simple uses and testing, not so much for on-demand operations :) I say this after grumbling about similar configuration obstacles with ratelimits.<br><br>Best,<br>-jay<br><br>On 04/02/2012 02:37 PM, Chris Behrens wrote:<o:p></o:p></p><p class="MsoNormal">I have some plans for being able to set arbitrary "capabilities" for<o:p></o:p></p><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">hosts via nova.conf that you can use to build scheduler filters.<o:p></o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal"><o:p> </o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">Right now, there are capabilities, but I believe we're only creating<o:p></o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">these from hypervisor stats. You can filter on those today. What I'm<o:p></o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">planning on adding is a way to specify additional keyname/value pairs in<o:p></o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">nova.conf to supplement the capabilities we build from hypervisor stats.<o:p></o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">You could set things like this in your nova.conf:<o:p></o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal"><o:p> </o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">--host_capabilities=instance_type_ids=1,2,3;keyX;keyY=something<o:p></o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal"><o:p> </o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">etc. Since capabilities are already passed to scheduler rules, you could<o:p></o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">add some basic filters that do:<o:p></o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal"><o:p> </o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">if 'instance_type_ids' in capabilities and instance_type.id not in<o:p></o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">capabilities['instance_type_ids']:<o:p></o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">return False<o:p></o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal"><o:p> </o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">Since host_capabilities are just arbitrary keyname/value pairs, you can<o:p></o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">pretty much add anything you want to --host_capabilities and then write<o:p></o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">some matching scheduler filter rules.<o:p></o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal"><o:p> </o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">That's the basic idea, anyway. The exact same behavior will apply to<o:p></o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">'cells' and the cells scheduler as well. (Except you'll have<o:p></o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">cells_capabilities= somewhere (prob nova.conf for the cells service).<o:p></o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal"><o:p> </o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">- Chris<o:p></o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal"><o:p> </o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal"><o:p> </o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">On Apr 2, 2012, at 10:36 AM, Day, Phil wrote:<o:p></o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal"><o:p> </o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">Hi Folks,<o:p></o:p></p></blockquote></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">I’m looking for a capability to limit some flavours to some hosts. I<o:p></o:p></p></blockquote></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">want the mapping to be as flexible as possible, and work within a<o:p></o:p></p></blockquote></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">zone/cell (I don’t want to add zones just to get this mapping). For<o:p></o:p></p></blockquote></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">example I want to express something like:<o:p></o:p></p></blockquote></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">Host_1 supports flavours A, C<o:p></o:p></p></blockquote></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">Host_2 supports flavours A, B<o:p></o:p></p></blockquote></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">Host_3 supports flavours A, B, C<o:p></o:p></p></blockquote></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">Host_4 supports flavours D<o:p></o:p></p></blockquote></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">Ideally there would be some form of grouping to sets of flavours:<o:p></o:p></p></blockquote></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">Flavour_A is part of Flavour_Sets 1, 2, 3<o:p></o:p></p></blockquote></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">Flavour_B is part of Flavour_Sets 2, 3<o:p></o:p></p></blockquote></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">Flavour_C is part of Flavour_Sets 1, 3, 4<o:p></o:p></p></blockquote></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">Host_1 supports flavour Set 1<o:p></o:p></p></blockquote></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">Host_2 supports flavour Set 2<o:p></o:p></p></blockquote></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">Host_3 supports flavour Set 3<o:p></o:p></p></blockquote></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">Host_4 supports flavour Set 4<o:p></o:p></p></blockquote></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">>From the Essex design summit I thought that host aggregates was going to give this sort of capability, but having looked through the code that seems to be quite tightly coupled with specific hypervisor functionality, whereas this is purely a scheduler feature.<o:p></o:p></p></blockquote></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">I can see that I could define flavour group membership through the<o:p></o:p></p></blockquote></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">instanace_type_extra_specs, but not how to then associate these with<o:p></o:p></p></blockquote></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">specific hosts.<o:p></o:p></p></blockquote></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">I know I’m a tad behind some of the recent changes – so before<o:p></o:p></p></blockquote></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">suggesting a design summit session on this I thought I’d ask - is<o:p></o:p></p></blockquote></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">there something that already does this type of mapping ?<o:p></o:p></p></blockquote></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">Cheers,<o:p></o:p></p></blockquote></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">Phil<o:p></o:p></p></blockquote></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">_______________________________________________<o:p></o:p></p></blockquote></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">Mailing list:https://launchpad.net/~openstack<o:p></o:p></p></blockquote></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">Post to :<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><o:p></o:p></p></blockquote></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal"><<a href="mailto:openstack@lists.launchpad.net">mailto:openstack@lists.launchpad.net</a>><o:p></o:p></p></blockquote></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">Unsubscribe :<a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><o:p></o:p></p></blockquote></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">More help :<a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><o:p></o:p></p></blockquote></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal"><o:p> </o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal"><o:p> </o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal"><o:p> </o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">_______________________________________________<o:p></o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><o:p></o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><o:p></o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><o:p></o:p></p></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><o:p></o:p></p></blockquote><p class="MsoNormal"><br>_______________________________________________<br>Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><o:p></o:p></p></div></div><p class="MsoNormal"><o:p> </o:p></p></div></blockquote><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><div><p class="MsoNormal">_______________________________________________<br>Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><o:p></o:p></p></div></blockquote></div></div></div></blockquote></body></html>