<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" id="owaParaStyle"></style>
</head>
<body style="word-wrap:break-word" fpstyle="1" ocsi="0">
<div style="direction: ltr;font-family: Courier New;color: #000000;font-size: 10pt;">
Ugh, sorry, burned again by outlook web. Let me continue ...
<div><br>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<div id="divRpF305306" style="direction: ltr; "><span class="Apple-style-span" style="font-family: 'Courier New'; font-size: 13px; ">I'm still stewing on this but at first blush this seems like an artificial abstraction. What do we really gain from having another
layer above the service api's? Can't they just live at the service api?</span></div>
<div>
<div style="direction:ltr; font-family:Courier New; color:#000000; font-size:10pt">
<div><br>
</div>
<div>For example:</div>
<div><br>
</div>
<div>nova.compute.api:create_instance()</div>
<div><br>
</div>
<div>vs. </div>
<div><br>
</div>
<div>nova.business_layer:create_instance()</div>
<div><br>
</div>
<div>What's the real win here? </div>
<div><br>
</div>
<div>I agree that the heavy lifting logic should be removed from the os/ec2 api layers and only be doing parameter checking ... but they may also do mapping/translations to the underlying service api's.</div>
<div><br>
</div>
<div>Perhaps the issue is that the lower level (nova.[service].api) doesn't have a formal enough definition and is getting pulled in two directions by ec2/os api? Perhaps making this layer have a clear contract is what we're missing?</div>
<div><br>
</div>
<div>-S<br>
<br>
</div>
<div><br>
</div>
<br>
<div style="font-family:Times New Roman; color:#000000; font-size:16px">
<hr tabindex="-1">
<div id="divRpF624151" style="direction:ltr"><font face="Tahoma" size="2" color="#000000"><b>From:</b> Lorin Hochstein [lorin@isi.edu]<br>
</font></div>
<div id="divRpF624151" style="direction:ltr"><font face="Tahoma" size="2" color="#000000"><br>
</font></div>
<div>
<div>
<div>I think it actually looks more like this right now: </div>
<div><br>
</div>
</div>
<br>
<div><span class="Apple-style-span" style="font-family:'Courier New'">EC2 Client OS Client</span></div>
<div>
<div><font class="Apple-style-span" face="'Courier New'"> | |</font></div>
<div><font class="Apple-style-span" face="'Courier New'">EC2 API OS API</font></div>
<div><font class="Apple-style-span" face="'Courier New'"> \ /</font></div>
<div><font class="Apple-style-span" face="'Courier New'"> [nova-*] service APIs</font></div>
</div>
<div><br>
</div>
<div>There isn't really a single back-end API for the front-end APIs to call into. Instead, each of them makes calls to the multiple service APIs (e.g., scheduler, network, compute). </div>
<div><br>
</div>
<div>I would advocate for something more like this:</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div><span class="Apple-style-span" style="font-family:'Courier New'">EC2 Client OS Client</span></div>
<div>
<div><font class="Apple-style-span" face="'Courier New'"> | |</font></div>
<div><font class="Apple-style-span" face="'Courier New'">EC2 API OS API</font></div>
<div><font class="Apple-style-span" face="'Courier New'"> \ /</font></div>
<div><font class="Apple-style-span" face="'Courier New'"> internal nova API</font></div>
</div>
</div>
<div><font class="Apple-style-span" face="'Courier New'"> |</font></div>
<div><font class="Apple-style-span" face="'Courier New'">
<div style="font-family:Helvetica">
<div><font class="Apple-style-span" face="'Courier New'"> [nova-*] service APIs</font></div>
<div><font class="Apple-style-span" face="'Courier New'"><br>
</font></div>
<div><font class="Apple-style-span" face="'Courier New'"><br>
</font></div>
</div>
</font></div>
<div><font class="Apple-style-span" face="'Courier New'">
<div style="font-family:Helvetica">This is a single, unified API that is meant only for internal use. This would reduce the coupling between front-end and back-end. It would make it easier for someone with less expertise in the code (hello!) to find the location
in the code that answers questions like: "What does nova do when a user requests that an instance is launched?" They would just look at the internal API and find the appropriate method. It would also make it easier to add additional front-ends, if there's
ever any interest in that.</div>
<div style="font-family:Helvetica"><br>
</div>
<div style="font-family:Helvetica"><br>
</div>
</font></div>
</div>
</div>
</div>
<style type="text/css">
<!--
-->
</style><style type="text/css">
<!--
-->
</style></div>
</div>
</div>
</div>
<style type="text/css">embed[type*="application/x-shockwave-flash"],embed[src*=".swf"],object[type*="application/x-shockwave-flash"],object[codetype*="application/x-shockwave-flash"],object[src*=".swf"],object[codebase*="swflash.cab"],object[classid*="D27CDB6E-AE6D-11cf-96B8-444553540000"],object[classid*="d27cdb6e-ae6d-11cf-96b8-444553540000"],object[classid*="D27CDB6E-AE6D-11cf-96B8-444553540000"]{ display: none !important;}</style><style type="text/css">embed[type*="application/x-shockwave-flash"],embed[src*=".swf"],object[type*="application/x-shockwave-flash"],object[codetype*="application/x-shockwave-flash"],object[src*=".swf"],object[codebase*="swflash.cab"],object[classid*="D27CDB6E-AE6D-11cf-96B8-444553540000"],object[classid*="d27cdb6e-ae6d-11cf-96b8-444553540000"],object[classid*="D27CDB6E-AE6D-11cf-96B8-444553540000"]{ display: none !important;}</style>
<font face="monospace">This email may include confidential information. If you received it in error, please delete it.</font></body>
</html>