<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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@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;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* 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;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></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="ZH-CN" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US">Boris<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> I think you in fact covered two topic, one is if use db or rpc for communication. This has been discussed a lot. But I didn’t find the conclusion. From the discussion, seems the key thing is the fan out messages.
I’d suggest you to bring this to scheduler sub meeting.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><a href="http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-06-11-14.59.log.html">http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-06-11-14.59.log.html</a><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><a href="http://www.mail-archive.com/openstack-dev@lists.openstack.org/msg00070.html">http://www.mail-archive.com/openstack-dev@lists.openstack.org/msg00070.html</a><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><a href="http://comments.gmane.org/gmane.comp.cloud.openstack.devel/23">http://comments.gmane.org/gmane.comp.cloud.openstack.devel/23</a>
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> The second topic is adding extra tables to compute nodes. I think we need the lazy loading for the compute node, and also I think with object model, we can further improve it if we utilize the compute node object.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Thanks<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">--jyh<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;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""> Boris Pavlovic [mailto:boris@pavlovic.me]
<br>
<b>Sent:</b> Friday, July 19, 2013 10:07 AM<br>
<b>To:</b> OpenStack Development Mailing List<br>
<b>Subject:</b> Re: [openstack-dev] [Nova] New DB column or new DB table?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US">Hi all, <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">We have to much different branches about scheduler (so I have to repeat here also).<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">I am against to add some extra tables that will be joined to compute_nodes table on each scheduler request (or adding large text columns).<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Because it make our non scalable scheduler even less scalable. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Also if we just remove DB between scheduler and compute nodes we will get really good improvement in all aspects (performance, db load, network traffic, scalability )<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">And also it will be easily to use another resources provider (cinder, ceilometer e.g..) in Nova scheduler. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">And one more thing this all could be really simple implement in current Nova, without big changes <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <a href="https://docs.google.com/document/d/1_DRv7it_mwalEZzLy5WO92TJcummpmWL4NWsWf0UWiQ/edit?usp=sharing" target="_blank">https://docs.google.com/document/d/1_DRv7it_mwalEZzLy5WO92TJcummpmWL4NWsWf0UWiQ/edit?usp=sharing</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Best regards,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Boris Pavlovic <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Mirantis Inc.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US">On Fri, Jul 19, 2013 at 8:44 PM, Dan Smith <<a href="mailto:dms@danplanet.com" target="_blank">dms@danplanet.com</a>> wrote:<o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US">> IIUC, Ceilometer is currently a downstream consumer of data from<br>
> Nova, but no functionality in Nova is a consumer of data from<br>
> Ceilometer. This is good split from a security separation point of<br>
> view, since the security of Nova is self-contained in this<br>
> architecture.<br>
><br>
> If Nova schedular becomes dependant on data from ceilometer, then now<br>
> the security of Nova depends on the security of Ceilometer, expanding<br>
> the attack surface. This is not good architecture IMHO.<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US">Agreed.<o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US"><br>
> At the same time, I hear your concerns about the potential for<br>
> duplication of stats collection functionality between Nova &<br>
> Ceilometer. I don't think we neccessarily need to remove 100% of<br>
> duplication. IMHO probably the key thing is for the virt drivers to<br>
> expose a standard API for exporting the stats, and make sure that<br>
> both ceilometer & nova schedular use the same APIs and ideally the<br>
> same data feed, so we're not invoking the same APIs twice to get the<br>
> same data.<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US">I imagine there's quite a bit that could be shared, without dependency<br>
between the two. Interfaces out of the virt drivers may be one, and the<br>
code that boils numbers into useful values, as well as perhaps the<br>
format of the JSON blobs that are getting shoved into the database.<br>
Perhaps a ceilo-core library with some very simple primitives and<br>
definitions could be carved out, which both nova and ceilometer could<br>
import for consistency, without a runtime dependency?<br>
<span style="color:#888888"><br>
--Dan</span><o:p></o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US"><br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><o:p></o:p></span></p>
</div>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>