<div dir="ltr">Hi Simon<div><br></div><div style>The criteria is that every thing to be consumed by OpenNebula should be in the Template, so the user can not modify it. Otherwise it may lead to OpenNebula incorrectly manage the object (e.g. remove or modify an attribute from the DISK section) or a security threat (e.g. a user modifying the SOURCE attribute to access someone else's image ) That is the main reason to place the system generated information in the TEMPLATE section, including monitoring info (you may bypass a billing system based on a probe).</div>
<div style><br></div><div style>You are right that ERROR should be moved to USER TEMPLATE. The user may want to delete the error once she is notified... I've opened an issue for this [1]</div><div style><br></div><div style>
Now the other probes. This is for historical reasons. First versions of OpenNebula 1.0 (4 years ago!) did not have the functionality that we have now, and that lead to some inconsistencies in the data model. Probably CPU, NETRX... and the other probe results should be placed probably under a MONITOR section. During the development of the project we've opted to keep backwards compatibility over a more consistent data model. Probably we are wrong, but trying to keep the ecosystem and other adaption working from one release to other has been a priority for us.</div>
<div style><br></div><div style>You've raised other interesting issue. First, we are sorry if we failed to engage in any discussion about the implementation of new issues. This is by no means because of a lack of interest but for the trillions of things we have to deal with. Your feedback is very valuable for us and always considered internally even if we fail to answer it. </div>
<div style><br></div><div style>I'd say that comments to issues in redmine is a good place to link the discussions to specific features, new things and general aspects should go to the mailing list. </div><div style>
<br>
</div><div style>However, this is probably not as fluent and agile as it should. We've done in the past IRC meetings that we may restore plan a regular hangout for example. We'll work on this and send a proposal to the mailing list.</div>
<div style><br></div><div style>Thank you very much for feedback!</div><div style><br></div><div style>[1] <a href="http://dev.opennebula.org/issues/1955">http://dev.opennebula.org/issues/1955</a></div><div style><br></div>
<div style><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Apr 24, 2013 at 4:24 PM, Simon Boulet <span dir="ltr"><<a href="mailto:simon@nostalgeek.com" target="_blank">simon@nostalgeek.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>Custom monitoring attributes (extra attributes returned by the IM MONITOR or VMM POLL) are currently being added under the TEMPLATE section of the VM definition (from vm/VirtualMachine.cc:3165)</div>
<div><br></div><div>Perhaps I'm wrong, but I am seeing the TEMPLATE section a block that containt the "static" definition of the VM (number of CPU, maximum memory, attached NICs, Disks, etc.). Ex. one could cache the information found in the TEMPLATE section on their frontend for a certain period of time. And it starts to make even more sense now that we have a USER_TEMPLATE section (since OpenNebula 4.0).<br>
</div><div><br></div><div>Also errors are added under the TEMPLATE section.</div><div><div><br></div><div>Wouldn't it make more sense if the custom monitoring attributes (and errors) were being reported directly under the VM section (just like the other monitoring attributes NETRX, NETTX, etc. are being reported).</div>
<div> <br></div><div>PS. Not sure if the ecosystem list is the right place for this. In the past I used the users list as well as the bug tracker to submit technical questions and discussions. And I find it difficult to be informed, sharing the vision and debating some implementations of upcoming features in OpenNebula.</div>
</div><div><br></div><div>Simon</div></div>
<br>_______________________________________________<br>
Ecosystem mailing list<br>
<a href="mailto:Ecosystem@lists.opennebula.org">Ecosystem@lists.opennebula.org</a><br>
<a href="http://lists.opennebula.org/listinfo.cgi/ecosystem-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/ecosystem-opennebula.org</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Ruben S. Montero, PhD<br>Project co-Lead and Chief Architect<br>OpenNebula - The Open Source Solution for Data Center Virtualization<br><a href="http://www.OpenNebula.org" target="_blank">www.OpenNebula.org</a> | <a href="mailto:rsmontero@opennebula.org" target="_blank">rsmontero@opennebula.org</a> | @OpenNebula
</div>